Release 8.2 Features

The following features have been added to JUNOS Release 8.2. Following the description is the title of the manual or manuals to consult for further information. For a complete list of manuals, see Table 4.

Hardware

• MX960 Ethernet Services Router—The new MX960 Ethernet Services Router is an Ethernet-optimized edge router that provides both switching and carrier-class Ethernet routing. The MX960 router has a capacity of up to 480 gigabits per second (Gbps) full duplex, high-density Ethernet interfaces, and high-capacity switching throughput. The MX960 router is used in configurations in which Ethernet ports, L2 switches, L2/L3 switch routers, and L3 routers with general-purpose applications are supported for core IP/MPLS routing, intra-POP-IP-MPLS routing, and intra-POP Ethernet switching.

  The MX960 router includes the following hardware features:

  • 14 slots that support up to 12 Dense Port Concentrators (DPCs) with Ethernet ports and two Switch Control Boards (SCBs).
  • Two types of DPCs are supported: Gigabit Ethernet, 40-port and 10-Gigabit Ethernet, 4-port.
  • Each DPC includes four Packet Forwarding Engines.
  • RE-S-1300 and RE-S-2000 Routing Engines.

  The following JUNOS software features are supported:

  • Class of service functionality—The same functionality that runs on all other Juniper Networks routing platforms.
  • Ethernet IQ2 functionality—MAC learning and accounting, MAC filtering, MAC policing, VLAN rewrite options, CCC encapsulation, multiple TPID support, stacked VLAN tags, dual tags, IP service for nonstandard TPID and stacked VLAN tags, and IP rewrite per channel.
  • Firewall filters—The same functionality that runs on all other Juniper Networks routing platforms.
  • IP VPNs—The same functionality that runs on all other Juniper Networks routing platforms.
  • OAM capabilities—Discovery and link monitoring, fault signaling and detection, and remote loopback. For more information, see the “Support for IEEE 802.3ah OAM functionality on all point-to-point Ethernet interfaces on M320, MX960, and T-series routing platforms” feature description under the “Interfaces and Chassis” category in this section.
  • JUNOScope—Configuration capability and management, including element management tools, such as Looking Glass, Configuration Manager, Software Manager, and Inventory Management.
  • LACP—The same functionality that runs on all other Juniper Networks routing platforms.
  • MPLS—The same functionality that runs on all other Juniper Networks routing platforms.
  • Virtual tunnel interfaces—Enables you to create tunnel interfaces on MX960 Ethernet Services routers. The MX960 router DPCs have built-in Ethernet ports and do not support Tunnel Physical Interface Cards (PICs). For more information, see the “Virtual tunnel interface support on the MX960 Ethernet Services Router” feature description under the “Interfaces and Chassis” category in this section.
  • VPLS—The same functionality that runs on all other Juniper Networks routing platforms.

  [JUNOS System Basics and Services Command Reference, JUNOS Network Interfaces Configuration Guide, JUNOS System Basics Configuration Guide, JUNOS VPNs Configuration Guide]

• 8-port 1-Gigabit Ethernet IQ2 (Type 3) PIC support on M320, T320, T640, and TX Matrix routing platforms—This PIC is not oversubscribed but otherwise supports all the features of the Gigabit Ethernet IQ2 PIC family. [JUNOS Network Interfaces Configuration Guide]
• 1-port 10-Gigabit Ethernet IQ2 (Type 3) PIC support on the M120 router—This PIC is now supported on the M120 router. [JUNOS Network Interfaces Configuration Guide]

Software Installation

• Support for bootable PC Card, USB storage device, and LS-120 floppy—For instructions on how to create a bootable PC Card, USB storage device, or LS-120 floppy, see the Install Media README file at the Juniper Networks software download site, http://www.juniper.net/support/csc/swdist-domestic or http://www.juniper.net/support/csc/swdist-ww/.

User Interface and Configuration

• Stylesheet language alternative syntax (SLAX)—SLAX is a language for writing JUNOS commit and operation scripts and is an alternative syntax for the XSLT language. The XSLT language has an XML-based syntax. SLAX has a simple language syntax that follows the style of C and Perl. Compared to XSLT, SLAX provides a more practical and succinct way to code, thus allowing you to create readable, maintainable commit and op scripts. To convert XSLT scripts into SLAX, issue the request system scripts convert xslt-to-slax operational mode command, specifying a source file and a destination. To convert SLAX scripts into XSLT, issue the request system scripts convert slax-to-xslt operational mode command, specifying a source file and a destination. [ JUNOS Configuration and Diagnostic Automation Guide]
• Statement to limit configuration output—Enables you to limit output that appears when you use the show command to display a configuration. Include the apply-flags omit configuration statement at any hierarchy level to omit the containing hierarchy from show command output. This feature is useful for hiding portions of the configuration that include lengthy or redundant configuration statements. [JUNOS CLI User Guide]
• New TACACS+ attribute for configuring user permissions—A new Juniper Networks-specific TACACS+ attribute called user-permissions lets you specify permissions on a per-user basis in the TACACS+ server configuration file. [JUNOS System Basics Configuration Guide]
• Direct system log messages to a remote machine that is identified by an IPv6 address—To enable this feature, include the host statement at the [edit system syslog] hierarchy level. [JUNOS System Log Messages, JUNOS System Basics Configuration Guide]

Interfaces and Chassis

• Virtual tunnel interface support on the MX960 Ethernet Services Router—To create tunnel interfaces on the MX960 router, include the tunnel-services statement at the [edit chassis fpc slot-number pic number] hierarchy level. For fpc slot-number, specify the number of the DPC and for pic number, specify the number of the Packet Forwarding Engine. You can also specify the amount of bandwidth to allocate for tunnel traffic on each Packet Forwarding Engine. Include the bandwidth statement at the [edit chassis fpc slot-number pic number] hierarchy level. [JUNOS System Basics Configuration Guide]
• Integrated voice and data traffic on a single T1/E1 interface on J-series Services Routers—The drop-and-insert multiplexer is now integrated into channelized T1/E1 PIMs on J-series Services Routers. On channelized T1/E1 interfaces partitioned into channels, you can insert time slots from one port directly into the other port on the same PIM, to replace time slots coming through the Routing Engine. To specify whether the channel sends and receives data from the Routing Engine (system) or the named interface, include the data-input [system | interface interface-name] statement at the [edit interfaces ds-pim/0/port:channel] hierarchy level. To avoid slips, both ports must use the same clock source, either the router’s internal clock or an external clock on one of the interfaces. If an external clock source is required, one interface must specify clocking external and the other must specify the same clock with the clocking external interface interface-name statement. [JUNOS Network Interfaces Configuration Guide]
• New show chassis temperature-thresholds operational mode command—The M120 router and the MX960 Ethernet Services Router have per-FRU and per-slot temperature thresholds for setting the fan to high speed and for raising yellow and red alarms. The show chassis temperature-thresholds command displays these settings. [JUNOS System Basics and Services Command Reference]
• Enhancement to the output from the show chassis hardware detail operational mode command—The show chassis hardware detail command now displays when USB flash install media is present in the USB slot for the new RE-A-1000, RE-A-2000, RE-S-1300, and RE-S-2000 Routing Engines. These next-generation Routing Engines use USB flash memory instead of a PC Card. The USB flash install media is prepared in the same way as the PC Card install media, with the exception that the device name is /dev/rda0 instead of /dev/rad3. The RE-A-1000 and RE-A-2000 are supported on the M320, M120, and T-series routing platforms. In addition, the RE-A-1000 is supported on M40e routers. The RE-S-1300 and RE-S-2000 Routing Engines are supported on the new MX960 Ethernet Services Router.[JUNOS System Basics Configuration Guide, JUNOS System Basics and Services Command Reference]
• Display model numbers for field-replaceable units (M-series and T-series routing platforms)—Extends the show chassis hardware command to display the field-replaceable unit (FRU) model number, serial number, part number, and, for components that use ID EEPROM format v2, the Common Language Equipment Identifier (CLEI) code. The CLEI code is not available for components that use ID EEPROM format v1. To display the FRU model number, part number, and serial number, issue the show chassis hardware models command. To display the FRU model number, part number, and CLEI code, issue the show chassis hardware clei-models command. The show chassis hardware frus command is deprecated. [JUNOS System Basics and Services Command Reference]
• Forwarding Engine Board redundancy support (M120 routers only)—Enables you to designate a Forwarding Engine Board (FEB) as a backup for one or more FEBs. You create a redundancy group that includes two or more FEBs and specify which FEB is the backup for the group. Switchover to a backup FEB occurs when a FEB fails. You can also manually enable a switchover from an active FEB to a backup FEB. To enable FEB redundancy, include the redundancy-group statement at the [edit chassis redundancy feb] hierarchy level. To specify which FEBs to include in the redundancy group, include the feb slot-number statement at the [edit chassis redundancy feb redundancy-group group-name] hierarchy level. You must configure one backup FEB by including the feb slot-number backup statement at the [edit chassis redundancy feb redundancy-group group-name] hierarchy level. You can optionally specify a primary FEB by including the feb slot-number primary statement at the [edit chassis redundancy feb redundancy-group group-name] hierarchy level. Automatic FEB failover is enabled by default. To disable automatic FEB failover, include the no-auto-failover statement at the [edit chassis redundancy feb redundancy-group group-name] hierarchy level. To manually switch from an active FEB to the backup FEB, issue the request chassis redundancy feb slot slot-number switch-to-backup operational mode command. To revert to a FEB after a switchover, issue the request chassis feb slot slot-number revert-from-backup ] command. To display the status of configured redundancy groups, issue the show chassis redundancy feb operational mode command. [JUNOS System Basics Configuration Guide, JUNOS System Basics and Services Command Reference]
• SONET or SDH framing on a per-port basis on the 4-port OC192 PIC on T-series routing platforms—Before the introduction of this feature on the 4-port OC48-SFP PIC with JUNOS Release 8.1, SONET or SDH framing could only be configured on a per-PIC basis. The new functionality allows you to mix SONET and SDH modes on interfaces and PICs. For example, incoming SDH links from Europe and outgoing SONET links to the US can be configured on the same PIC. Traffic flowing through other ports on the PIC is not affected. When you change SONET/SDH mode on a port, only the port's framing type is changed. The PIC will not transition offline and back online. When you change the mode, traffic on the affected port might be slightly delayed.

  Note: Automatic Protection Switching (APS) is used by SONET add/drop multiplexers (ADMs) to protect against circuit failures. If APS is configured, and you do not change the SONET/SDH mode on both the working and protection ports, APS support will not function properly. Both the working and protection ports must have the same mode configuration.

  To configure framing on a per-port basis, include the framing (sdh | sonet) statement at the [edit interfaces so-fpc/pic/port] hierarchy level. To view interface information, use the operational mode command show interfaces so-fpc/pic/port. [JUNOS Network Interfaces Configuration Guide, JUNOS Interfaces Command Reference]

• Larger delay buffers for channelized T1/E1 interfaces—By default, interfaces other than channelized T1/E1 interfaces on Services Routers are limited to 100,000 microseconds of delay buffer. On channelized T1/E1 interfaces, the default delay buffer is 500,000 microseconds for clear-channel interfaces, and 1,200,000 microseconds for NxDS0 interfaces. This feature allows you to configure larger delay buffers for the NxDS0 interfaces to avoid congestion and packet dropping that occur when large bursts of traffic are received by slower interfaces. You can configure larger delay buffers for channelized T1/E1 interfaces only. [J-series Services Router Advanced WAN Access Configuration Guide, JUNOS System Basics Configuration Guide]
• 802.1Q VLAN tagging on aggregated Ethernet interfaces—A subset of JUNOS 802.1Q tagging is now supported on aggregated Ethernet interfaces on Gigabit Ethernet IQ PICs. You can now configure stacked VLAN tagging and apply the VLAN rewrite operation to outgoing frames or incoming frames on a logical interface (input VLAN map and output VLAN map). Include the stacked-vlan-tagging statement at the [edit interfaces interface-name] hierarchy level. When you configure stacked VLAN tagging, you must configure dual VLAN tags on a logical interface. To configure dual VLAN tags, include the vlan-tags inner tpid.vlan-id outer tpid.vlan-id statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] and [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number]. To apply the rewrite profile to incoming frames and outgoing frames on the logical interface, include the input-vlan-map and output-vlan-map statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] and [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number]. When you include the input-vlan-map and output-vlan-map statements, you can configure the following rewrite operations:
  • push—Add a new VLAN tag to the top of the VLAN stack. An outer VLAN tag is pushed in front of the existing VLAN tag.
  • pop—Remove a VLAN tag from the top of the VLAN tag stack. The outer VLAN tag of the frame is removed.
  • swap—Replace a VLAN tag. The outer VLAN tag of the frame is overwritten with the user-specified VLAN tag information.

  To display information about aggregated Ethernet interfaces, use the operational mode command show interfaces aenumber. [JUNOS Network Interfaces Configuration Guide, JUNOS Interfaces Command Reference]

  Note: Please contact Juniper Networks support before configuring 802.1Q VLAN tagging on aggregated Ethernet interfaces. [PR/96830]

• Diagnostic optics enhanced for small form-factor pluggable (SFP) transceivers—In addition to XENPAK and DWDM diagnostics optics, you can now display SFP transceiver optics information for the following PICs:
  • OC48c/STM16, 1-port SFP
  • OC48c/STM16, 4-port SFP
  • 1-Gbps Gigabit Ethernet, 2-port SFP
  • 1-Gbps Gigabit Ethernet, 4-port SFP
  • 1-Gbps Gigabit Ethernet, 10-port SFP
  • 1-Gbps Gigabit Ethernet IQ, 1-port SFP
  • 1-Gbps Gigabit Ethernet IQ, 2-port SFP
  • Gigabit Ethernet IQ2 (all)

  Support for diagnostics depends on the SFP transceiver. The SFP toolkit detects the level of diagnostic support provided by the SFP transceiver being queried and displays output accordingly. To view SFP diagnostics, issue the show interfaces diagnostics optics operational mode command. PIC types that do not support diagnostic monitoring will not display output. [JUNOS Interfaces Command Reference]

• Unnumbered Ethernet—This feature enables you to configure IPv4 processing on an Ethernet interface without assigning an explicit IP address to the interface. Using unnumbered interfaces conserves IPv4 address space by enabling many ports to share a single IP address. In addition, unnumbered interfaces simplify bulk configuration of interfaces and provide a way to point a static route to an interface on broadcast media. The Ethernet interface that you configure to be unnumbered borrows an assigned IP interface from another interface, and is therefore referred to as the borrower interface. The interface from which the IP address is borrowed is referred to as the donor interface. In previous JUNOS releases, the borrower (unnumbered) interface could be only a point-to-point interface with PPP encapsulation. To configure an Ethernet interface to be unnumbered, include the unnumbered-address statement at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level. To display that the family is unnumbered, use the show interfaces operational mode command. You can also configure static routes on an unnumbered Ethernet interface by including the qualified-next-hop statement at the [edit routing-options static route destination-prefix] hierarchy level. [JUNOS Network Interfaces Configuration Guide, JUNOS Policy Framework Configuration Guide, JUNOS Interfaces Command Reference]
• Support for IEEE 802.3ah OAM functionality on all point-to-point Ethernet interfaces on M320, MX960, and T-series routing platforms—These operation, administration and management (OAM) capabilities are provided: discovery and link monitoring, fault signaling and detection, remote loopback (supported only for IQ2 Gigabit Ethernet interfaces and 10-Gigabit Ethernet interfaces). To specify 802.3ah OAM support for Ethernet interfaces, include the oam statement at the [edit protocols] hierarchy level. To view the configuration, issue the show oam ethernet link-fault-management interface-name operational mode command. To clear OAM statistics, issue the clear oam ethernet link-fault-management statistics operational mode command. [JUNOS Network Interfaces Configuration Guide, JUNOS Routing Protocols Configuration Guide, JUNOS Interfaces Command Reference]

Services Applications

• Digital certificate support for IKE authentication of IPSec dynamic endpoints—Enables you to configure an IKE access profile that uses a local digital certificate to authenticate remote dynamic peers. For dynamic peers, only main mode is supported. Include the ike-policy policy-name statement at the [edit access profile profile-name client client-name] hierarchy level. For policy-name, specify an IKE policy configured at the [edit services ipsec-vpn ike policy policy-name] hierarchy level. Previously, JUNOS supported only preshared keys for IKE authentication of dynamic endpoints. [JUNOS Services Interfaces Configuration Guide, JUNOS System Basics Configuration Guide]
• USB modems to remotely manage J-series Services Routers—The J-series Services Routers now support the use of USB modems for remote management. You can use Telnet or SSH to connect to the router from a remote location over a telephone network through two modems: the USB modem that is connected to the USB port on the Services Router and a second modem connected to a remote management device such as a PC or laptop computer. The modem connection allows you to manage the Services Router remotely. [JUNOS Network Interfaces Configuration Guide, J-series Services Router Administration Guide]

  Note: We recommend using a Multi-Tech MultiModemUSB MT5634ZBA-USB-V92 USB modem with J-series Services Routers.

• Service rules support source and destination prefix lists as a match condition for stateful firewall, NAT, IDS, and CoS services—To configure this feature, include the source-prefix-list or destination-prefix list statement at the [edit services service-name rule rule-name term term-name from] hierarchy level. You define the prefix list content by including the prefix-list statement at the [edit policy options] hierarchy level. [JUNOS Services Interfaces Configuration Guide, JUNOS Policy Framework Configuration Guide]
• Support for IP ALG in AS PIC service rules—The stateful firewall, NAT, IDS, and CoS services support the JUNOS IP application layer gateway (ALG), which matches for IP traffic. To configure, include the applications junos-ip statement at the [edit services service-name rule rule-name term term-name from] hierarchy level. Rule logs display ip as the application value for the JUNOS IP ALG, which is a stateless unidirectional flow. [[JUNOS Services Interfaces Configuration Guide]
• VoIP support on J4350 and J6350 Services Routers—J4350 and J6350 Services Routers support voice over IP (VoIP) routing with the Avaya IG550 Integrated Gateway. The Avaya IG550 Integrated Gateway consists of the following VoIP modules that can be installed in the slots on the J4350 and J6350 Services Routers:
  • TGM550—Avaya Telephony Gateway Module (TGM) with two analog telephone ports, two analog trunk ports, and one serial port for console access.
  • TIM510—Avaya E1/T1 Telephony Interface Module (TIM) with one T1 or E1 trunk port.
  • TIM514—Avaya Analog TIM with four analog telephone ports and four analog trunk ports.
  • TIM521— Avaya BRI TIM with four RJ-45 ports for ISDN BRI trunk connections.

  The TGM550 is an H.248 media gateway that works with one or more TIMs to connect IP and legacy analog telephones and trunks over IP networks. The telephony services on the TGM550 are controlled by a Media Gateway Controller (MGC)—an Avaya media server running Avaya Communication Manager (CM) call-processing software. The TGM550 is managed by an MGC located at headquarters or in a branch office. When the primary MGC is located at a remote location, the TGM550 uses standard local survivability (SLS) for partial MGC backup if the connection to the primary MGC is lost. [J-series Services Router Advanced WAN Access Configuration Guide]

• MultiServices PICs now support bandwidth oversubscription on LSQ interfaces, COS services, and RPM timestamping—The functionality is identical to that already supported on Adaptive Services PICs. [JUNOS Services Interfaces Configuration Guide]
• MultiServices PICs are now supported on the M120 routing platform—Features include all services that are generally supported across the M-series product line. [JUNOS Services Interfaces Configuration Guide]
• L2TP features are now supported on the M120 router using the AS2-PIC—Features include all services that are generally supported across the M-series product line.

General Routing

• Extended platform support for GRES—Graceful Routing Engine switchover (GRES) support has been extended to the M120 router. [JUNOS System Basics Configuration Guide, JUNOS Feature Guide]
• GRES support for VPLS (M10i, M20, M40e, M320, T320, T640, and TX Matrix platforms)—GRES now supports virtual private LAN service (VPLS). [JUNOS System Basics Configuration Guide, JUNOS Feature Guide, JUNOS VPNS Configuration Guide]

  Note: Please contact Juniper Networks support before implementing GRES for VPLS. [PR/82421]

• Support for an indirect next hop for all routing protocols supporting indirectly connected next hops—This feature is also known as third-party next hops. You can enable JUNOS to consider indirectly connected next hops to improve route convergence time. To enable indirectly connected next hops, include the indirect-next-hop statement at the [edit routing-options forwarding-table] hierarchy level. [JUNOS Routing Protocols Configuration Guide]

Routing Protocols

• Support for BFD over multihop static routes—You can now configure BFD over a Layer 3 path to provide path integrity. You can limit the number of hops by specifying the time to live (TTL). To configure BFD over multihop static routes, include the local-address ip-address and minimum-receive-ttl milliseconds statements at the [edit routing-options static route destination bfd-liveness-detection] hierarchy level. [JUNOS Routing Protocols Configuration Guide]
• BFD liveness detection—New detection-time threshold and transmit-interval threshold configuration statements are available at various levels of the [edit protocols] and [edit routing-options] hierarchy levels. SNMP traps are sent when the detection time or transmit interval exceeds the configured values. With the addition of these statements, the minimum-transmit-interval configuration statement has been deprecated. A new BFD MIB (mib-jnx-bfd.txt) has been added to support the SNMP trap feature. [JUNOS Network Management Configuration Guide, JUNOS Routing Protocols Configuration Guide]
• Selecting a location for BFD processing (M120, M320, and T-series routing platforms)—You can now select either the Packet Forwarding Engine or the Routing Engine to run the periodic packet management process (ppmd). ppmd offloads time-sensitive periodic packet processing from other system processes. When you run ppmd on the Packet Forwarding Engine, Bidirectional Forwarding Detection (BFD) processing is also handled on the Packet Forwarding Engine, which frees up Routing Engine resources for other processing needs. By default, ppmd and BFD run on the Routing Engine. To run ppmd and BFD on the Packet Forwarding Engine, include the delegate-processing statement at the [edit routing-options ppm] hierarchy level. [JUNOS Routing Protocols Configuration Guide]
• New show bfd session operational mode command options—The show bfd session command has been enhanced to include two new options: address session-address and discriminator discriminator-number. [JUNOS Routing Protocols and Policies Command Reference]

MPLS Applications

• Admin Status object for GMPLS—You can set the A-bit in the Admin Status object. When set, this bit indicates the administrative down status for an LSP. This feature is used specifically by non-packet LSPs in the context of GMPLS. It does not affect control path setup or data forwarding for packet LSPs. When an ingress router sends an RSVP PATH message with the Admin Status A-bit set, an external device (not a JUNOS software-based router) can either perform a Layer 1 path setup test or help to bring up an optical cross-connect. To configure the Admin Status object for a GMPLS LSP, include the admin-down statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. [JUNOS MPLS Applications Configuration Guide]
• Preservation of IS reachability information in LSPs—This feature accounts for the fragment number for each item of IS/MT-IS reachability information and regenerates LSPs at the destination with the same reachability information. IP prefixes are preserved in their original packet fragment upon LSP regeneration. [JUNOS MPLS Applications Configuration Guide]

Multicast

• Support for filtering unwanted PIM neighbors—To configure a policy to filter unwanted PIM neighbors, include the neighbor-policy statement at any of the following hierarchy levels:
  • [edit logical-routers logical-router-name protocols pim interface interface-name]
  • [edit logical-routers logical-router-name routing-instances routing-instance-name protocols pim interface interface-name]
  • [edit protocols pim interface interface-name]
  • [edit routing-instances routing-instance-name protocols pim interface interface-name]

  An enhancement to the show pim statistics command displays the total number of hello packets dropped per instance because of the PIM neighbor policy. [JUNOS Multicast Protocols Configuration Guide, JUNOS Routing Protocols and Policies Command Reference]

• Multicast flow maps—A flow map enables you to separately control the forwarding cache timeout value for a group of multicast (S, G) pairs. You can assign the timeout value, in minutes, to be different from the general forwarding cache timeout value, or you can specify the timeout to be never and make the forwarding entries permanent. A new show multicast flow-map command displays the name of the flow map, name of the policies used by each flow map, and the cache timeout value assigned to the (S, G) pairs controlled by each flow map. An enhancement to the show multicast route extensive command displays the value never in the case of permanent forwarding entries. [JUNOS Routing Protocols and Policies Command Reference, JUNOS Multicast Protocols Configuration Guide]

Routing Policy and Firewall Filters

• Support for policers that limit traffic on a logical interface in the ingress or egress direction—To configure a policer on a logical interface using tricolor marking, include the logical-interface-policer and action statements at the [edit firewall three-color-policer three-color-policer-name] hierarchy level. [JUNOS Policy Framework Configuration Guide]
• Support for policers that rate-limit based on a percentage of physical port speed on an interface—To configure a bandwidth policer, include the bandwidth-policer statement at the [edit firewall policer policer-name] hierarchy level. After configuring the bandwidth policer, you can apply the policer to an interface. To apply a bandwidth policer on a logical interface, include the policer policer-name option at the [edit interfaces interface-name unit 0 family] hierarchy level. [JUNOS Policy Framework Configuration Guide]

VPNs

• Aggregated Ethernet interfaces for VPLS routing instances—You can configure aggregated Ethernet interfaces between CE devices and PE routers for VPLS routing instances. Traffic is load-balanced in two ways:
  • If the next hop of VPLS packets to the next CE device is aggregated Ethernet, load balancing is based on the input interface. The router picks one of the child members to forward the flow. By default, load balancing of learned traffic takes place using the input interface.
  • Learned traffic from a different MAC flow originating from the same aggregated Ethernet input interface. In this case, to load balance traffic across all the links on the interface, configure the forwarding-options hash-key source-mac destination-mac statement at the [edit interfaces ae number] hierarchy level.

  In both cases, if one or more links on the interface fails, the traffic is switched to the remaining links.

  To configure an aggregated Ethernet interface for VPLS with VLAN support, include the vlan-id statement and either the encapsulation vlan-vpls, encapsulation extended-vlan-vpls, or encapsulation flexible-ethernet-encaps (IQ and IQ2 PICs only) statement at the [edit interfaces ae number] hierarchy level. Configure a VLAN identifier using the vlan-id statement at the [edit interfaces ae number unit logical-unit-number] hierarchy level.

  If you do not want to configure VLAN support on the interface, configure ethernet-vpls encapsulation. [JUNOS Network Interfaces Configuration Guide, JUNOS VPNs Configuration Guide]

  Note: Please contact Juniper Networks support before configuring aggregated Ethernet interfaces for VPLS routing instances. [PR/96831]

• VPLS without a Tunnel Services PIC supported for the MX960—The JUNOS software supports VPLS without a Tunnel Services PIC on the MX960 router. For more information, see the “Virtual tunnel interface support on the MX960 Ethernet Services Router” feature description under “Interfaces and Chassis” in this section. [JUNOS VPNs Configuration Guide]

Class of Service

• Establish a separate timer for each forwarding class on LSQ interfaces using multiclass MLPPP—To enable this feature, include the drop-timeout statement at the [edit class-of-service fragmentation-maps map-name forwarding-class class-name] hierarchy level. By default, the timer value is based on link speed and cannot be disabled. [JUNOS Class of Service Configuration Guide]
• Distribution of class of service (CoS) schedulers on Ethernet IQ2 PICs—Include the new schedulers statement at the [edit interfaces ge-fpc/pic/port] hierarchy level to distribute the 1024 schedulers available for Ethernet IQ2 PICs. By default, these are evenly distributed in multiples of 4. To display scheduler information, issue the show interfaces ge-fpc/pic/port extensive operational mode command. [JUNOS Class of Service Configuration Guide, JUNOS System Basics and Services Command Reference]
• Support for copying the TOS bits to the outer IP header on GRE tunnel traffic sent by the Routing Engine—To enable this feature, include the copy-tos-to-outer-ip-header statement at the [edit interfaces gr-fpc/pic/port unit logical-unit-number] hierarchy level. [JUNOS Class of Service Configuration Guide]

Network Management

• RFC 2096, IP Forwarding Table MIB— An enterprise specific MIB (mib-jnx-ipforward.txt) is available that extends the ipCidrRouteTable in the IP Forwarding Table MIB (as defined in RFC 2096) to include a tunnel name when the next hop is through an RSVP-signaled LSP. This MIB adds a jnxIpCidrRouteTunnelName attribute to the ipCidrRouteTable.[JUNOS Network Management Configuration Guide]
• Support for an enterprise-specific event MIB (mib-jnx-event.txt)—The event MIB, whose object identifier is {jnxMibs 37}, defines a generic trap that can be generated using an op script or event policy. This MIB provides the ability to specify a system log string and raise a trap if that system log string is found. [JUNOS Network Management Configuration Guide]
• Support for the enterprise-specific Packet Forwarding Engine (PFE) MIB (mib-jnx-pfe.txt)—This MIB provides notification statistics for Packet Forwarding Engines. Information provided by this MIB matches information provided by the show pfe statistics notification operational mode command. [JUNOS Network Management Configuration Guide]
• Support for trap spoofing—You can use the request snmp spoof-trap operational mode command to mimic SNMP trap behavior. The contents of the trap (the values and instances of the objects carried in the trap) can be specified on the command line or they can be spoofed automatically. This feature is useful if you want to trigger SNMP traps from routers and ensure that the traps are processed correctly within your existing network management infrastructure, but find it difficult to simulate the error conditions that trigger many of the traps on the router. [JUNOS Network Management Configuration Guide]
• Support for MIB objects in accounting profiles—You can configure a MIB accounting profile to collect MIB statistics and log them to a file. The MIB profile specifies the SNMP operation and MIB object names for which statistics are collected. To configure a MIB profile, include the mib-profile statement at the [edit accounting-options] hierarchy level. [JUNOS Network Management Configuration Guide]
• Support for Internet draft draft-ieft-bfd-mib-02.txt, Bidirectional Forwarding Detection Management Information Base (as defined under the Juniper Networks enterprise experimental branch)—This MIB provides SNMP trap support for BFD liveness detection. (Support is read-only and includes bfdSessUp and bfdSessDown traps. Support does not include bfdSessPerfTable and bfdSessMapTable objects.) MIB draft-ietf-bfd-mib-02.txt is represented by mib-jnx-bfd-exp.txt and is implemented under the Juniper Enterprise jnxExperiment branch. [JUNOS Network Management Configuration Guide]
• Support for RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer—Includes support for all objects except etherWisDeviceTable, etherWisSectionCurrentTable, and etherWisFarEndPathCurrentTable. [JUNOS Network Management Configuration Guide]

JUNOScope

• Support for configuration revision comparison—For any JUNOScope-managed device, you can tag a configuration revision in the repository as a master and compare it with another archived configuration revision. The comparison can be made with a running configuration or a version from the archive repository. Those devices with configurations different from the master are highlighted and are also reported as system log events. From the JUNOScope main window, click Configuration > Repository > Tag. [JUNOScope Software User Guide]
• Support for global authentication policies—The global authentication policy is used when an authentication policy has not been configured for a user. A user authentication policy is used for all users already configured in JUNOScope. The administrator can create an access list, which specifies which client machines to deny or allow access to the JUNOScope software. From the JUNOScope main window, click Home > Settings > Users > Authentication Policy > Global Authentication Policy to configure the global authentication policy and the Access Control List. [JUNOScope Software User Guide]
• Purge unwanted entries in the Status and Audit Log tables through the user interface—Most JUNOScope operations generate multiple rows of system and status records in the Audit Log and Status tables. These tables grow in size and consume valuable disk space on the JUNOScope software server. The data in these tables are useful only to the JUNOScope administrator. From the JUNOScope main window, click Monitor > Purge > Status to access the Status table purge wizard. Click Monitor > Purge > Audit Log to access the Audit Log table purge wizard. [JUNOScope Software User Guide]
• JUNOScope user groups—The JUNOScope administrator can create user groups consisting of one or more JUNOScope users that have specified permissions and access to devices configured in the JUNOScope software. The administrator can associate devices and device groups to a user group. There are four predefined user groups: administrator, read-write user, read-only user, and nobody. Every user group must be associated with one permission level: superuser, read-write, read-only, and none. From the JUNOScope main window, click Settings > User > Authorization. [JUNOScope Software User Guide]

System Log

The following system log messages are new in this release:

• BFDD_TRAP_STATE_DOWN
• BFDD_TRAP_STATE_UP
• CHASSISD_FASIC_INPUT_DROP
• CHASSISD_FASIC_OUTPUT_DROP
• DCD_PARSE_ERROR_CLOCK
• KMD_PM_PHASE1_POLICY_SEARCH_FAIL
• L2TPD_RPD_ROUTE_PREFIX_TOO_LONG
• LFMD_RTSOCK_OPEN_FAILED
• PFE_FW_IF_DIALER_ERR
• PFED_NOTIFICATION_STATS_FAILED
• UI_INVALID_REMOTE_PERMISSION

[JUNOS System Log Messages Reference]

Copyright © 2007, Juniper Networks, Inc. All Rights Reserved. Trademark Notice.