Release 7.4 Features

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

Hardware

• 10-port Channelized T1 Intelligent Queuing (IQ) PIC, Type 1 (M7i, M10i, M20, M40e, and M320 platforms)—Enables you to configure up to 10 T1 interfaces and 240 DS0 interfaces (the maximum number of DS0 interfaces depends on the platform). [M-series PIC Guide]
• Support for E3 4-port Asynchronous Transfer Mode 2 IQ (ATM2 IQ) Physical Interface Card (PIC) on T-series and TX Matrix platforms—The E3 4-port ATM2 IQ PIC is now supported on T-series and TX matrix platforms. [T-series PIC Guide]
• Monitoring Services III PIC (T-series and M320 routing platforms)—Enables enhanced flow monitoring services, such as dynamic flow capture. See the “Dynamic flow capture” feature description under “Services Applications” in this section. [T-series PIC Guide, M320 PIC Guide]
• Enhanced II Flexible PIC Concentrators (FPCs) are now available on the T-series routing platform. An Enhanced II FPC provides 1 gigabyte (GB) DRAM for scaling enhancements and supports two-rate tricolor marking. See the “Two-rate tricolor marking” feature description under “Class of Service” in this section. The show chassis hardware command lists Enhanced II FPCs as follows:
  • E2-FPC Type 1
  • E2-FPC Type 2
  • E2-FPC Type 3

  [FPC Installation Instructions, Class of Service, System Basics, Command Reference: System Basics and Services]

• G.SHDSL Physical Interface Modules (PIMs) (Annex A/B) on J4300 or J6300 Services Routers—Supports multirate, high-speed, symmetrical digital subscriber line technology for data transfer between a single customer premises equipment (CPE) subscriber and a central office (CO). ITU-T G.991.2 is the officially designated standard describing G.SHDSL. The G.SHDSL PIM supports:
  • ATM-over-G.SHDSL mode only
  • 2-port, 2-wire mode only (Annex A and B)
  • CPE SHDSL transceiver unit-remote [STU-R) operation only

  For information about configuring ATM-over-SHDSL interfaces, see the “ATM-over-SHDSL interfaces on J4300 or J6300 Services Routers” feature description under “Interfaces and Chassis” in this section. [J-series Configuration Guide, J-series Getting Started Guide, Network Interfaces]

• 1-port OC12 PICs are now supported on the T320 routing platform. [T-series PIC Guide]

Software Installation

• Software upgrade enhancements—Add new options to assist with software upgrades:
  • Use the new request system storage cleanup command to free system storage space before performing a software upgrade. With confirmation, this command rotates log files and deletes log files in /var/log that are not currently being written to. This command also deletes temporary files in /var/tmp that have not been touched in two days, and deletes all crash files in /var/crash.
  • On J-series Services Routers, when you upgrade to a new software package from a remote location using the request system software add validate package-name command, the package is removed at the earliest opportunity in order to make room for the installation to be completed. If you copy the software to a local directory on the router and then install the new package, use the new unlink option with the request system software add validate package-name command to achieve the same effect and allow the installation to complete.
  • On M-series and T-series routers, use the unlink option with the request system software add validate package-name command to remove the software package after the upgrade has been successfully completed.

  [System Basics, Command Reference: System Basics and Services]

• Firmware upgrade and downgrade enhancements for J-series Services Routers—The new request system firmware upgrade and request system firmware downgrade operational mode commands enable you to easily install firmware on PIMs on J-series Services Routers. To display firmware information, issue the show system firmware operational mode command. For detailed instructions on how to use these commands, see the J-series Services Router Administration Guide.

Platform and Infrastructure

• RADIUS accounting for user sessions—A Juniper Networks routing platform acting as a RADIUS client can notify the RADIUS server about user activities, such as login and logout information, commands executed, and so on. The framework for RADIUS accounting is described in RFC 2866, RADIUS Accounting. [System Basics]
• Dynamic flow capture system log messages can be configured by including the dfc statement at either or both of the following hierarchy levels:
  • [edit system syslog (console | file filename | host hostname | user username)]
  • [edit system syslog source-address source-address (console | file filename | host hostname | user username)]

  The JUNOS software uses the name dfc for the local1 facility for messages directed to a remote system.

  For a description of system log messages that are generated by the dfc facility, please contact Juniper Networks customer support.

  [System Log Messages Reference]

• Alarm configuration for the M320 router—Support for an entry-level M320 configuration with a minimum number of Switch Interface Boards (SIBs) and Power Entry Modules (PEMs). With this configuration, the router may have fewer than than the four SIBs or fewer than four PEMs. Include the sib minimum and pem minimum statements at the [edit chassis] hierarchy level to prevent unwanted alarms from occurring with this entry-level configuration. [System Basics]
• Enhanced commit configuration—Use the commit synchronize statement at the [edit system] hierarchy level so that when you enter the commit command without any options, the system executes a commit synchronize command by default. [System Basics]
• J-series configuration enhancement—On the J-series Services Router when you press and hold the CONFIG button for 15 seconds or more, all configurations on the router are deleted (including the backup configurations and rescue configuration), and the default factory configuration is loaded and committed. To specify how the CONFIG button works for resets, include the following statements at the [edit chassis] hierarchy level: config-button no-clear (do not reset to the factory-default configuration) and config-button no-rescue (do not reset to rescue configuration). [J-series Configuration Guide, System Basics]
• System time zone enhancement—The default local time zone on the router is UTC (Coordinated Universal Time, formerly known as Greenwich Mean Time). To set the local time zone relative to GMT time, include the time-zone GMT hour-offset statement at the [edit system] hierarchy level, where hour-offset can be in the range from -14 through +12. [System Basics]
• DHCP enhancement for J-series Services Routers—On J-series Services Routers, use the new show system services dhcp global command to display global information about Dynamic Host Configuration Protocol (DHCP). [Command Reference: System Basics and Services]
• Configurable password restrictions—Include the login password statements at the [edit system] hierarchy level to set password restrictions, such as minimum and maximum character length, required character set changes, and so on. You can set separate restrictions for JUNOS software and JUNOS-FIPS software. [System Basics]
• File transfer enhancement—The file copy command has an optional source-address argument that is used for file transfers to and from remote hosts. When you copy files, use the source argument to specify a URL address, or use the source-address argument to specify the source IP host address. The source-address option is useful for specifying the source address of a Session Control Protocol (SCP) file transfer. [Command Reference: System Basics and Services]
• When you load the JUNOS software, parsing errors are treated as errors instead of warnings and the load might fail. If you experience problems loading a configuration on the router, use the best-effort-load option with the request system software add command to perform a partial load and troubleshoot the problem. [Command Reference: System Basics and Services, System Basics]

User Interface and Configuration

• The J-Web graphical user interface provides a new Quick Configuration page that enables you to configure stateless firewall filters for IP version 4 (IPv4) and IP version 6 (IPv6), and to apply these filters to configured interfaces. To configure stateless firewall filters, navigate to Configuration>Quick Configuration>Firewall Filters.

  The discard accounting action is only supported for IPv4 (not IPv6) firewall filters.

  [J-series Configuration Guide]

Interfaces and Chassis

• VRRP enhancement—The new startup-silent-period seconds statement at the [edit protocols vrrp] hierarchy level instructs the system to ignore the Master Down Event when an interface transitions from the disabled state to the enabled state. This option is used to avoid an incorrect error alarm caused by delay or interruption of incoming Virtual Router Redundancy Protocol (VRRP) advertisement packets during the interface startup phase. The range of values, in seconds, is from 1 to 2000. The default value is 4.
• 10-port Channelized T1 IQ PIC, Type 1 (M7i, M10i, M20, M40e, and M320 platforms)—Enables you to configure up to 10 T1 interfaces and 240 DS0 interfaces (depending on the platform). To configure T1 IQ interfaces, include the no-partition interface-type statement at the [edit interfaces ct1-fpc/pic/port] hierarchy level. To configure an NxDS0 IQ interface on a Channelized T1 IQ PIC, you must configure the number of time slots allocated to the NxDS0 IQ interface by including the partition, timeslots, and interface-type statements at the [edit interfaces t1-fpc/pic/port] hierarchy level, specifying the ds interface type. [Network Interfaces]
• ATM-over-SHDSL interfaces on J4300 or J6300 Services Routers—The ATM-over-SHDSL interface is configured on a G.SHDSL PIM on J-series Services Routers only. To configure SHDSL physical interface properties, include the shdsl-options statement at the [edit interfaces at-pim/0/port] hierarchy level. [J-series Configuration Guide, Network Interfaces]
• LMI, error, and DLCI enhancements for Frame Relay networks—Statistics information in a Frame Relay network is maintained through Local Management Interface (LMI) updates. New statistics and data-link connection identifier (DLCI) information is now available. To view statistics, issue the show interfaces interface-name command. [Command Reference: Interfaces]
• ADSL2+ Annex B WAN interfaces for J-series Services Routers—On J-series Services Routers, ADSL2+ operating mode is supported for Annex B. [J-series Configuration Guide, Network Interfaces]

  Please contact Juniper Networks customer support before implementing this feature with DSLAMs other than Paradyne and Ericsson EDA.

• IPv6 and MPLS over PPPoE on J-series Services Routers—Point-to-Point Protocol over Ethernet (PPPoE) interfaces on J-series Services Routers can now support IPv6 and MPLS traffic. [J-series Configuration Guide, Network Interfaces]
• LSQ PIC interchassis failover (M-series platforms, except for M320 routers)—Adaptive Services (AS) PIC link services IQ (LSQ) interfaces that are paired with SONET/SDH PICs can use the Automatic Protection Switching (APS) configuration already available on SONET networks to provide stateless failure recovery. APS must be configured on SONET/SDH PICs in separate chassis, and each SONET/SDH PIC must be paired with an AS PIC running LSQ that is located in the same chassis. To configure the pairing between LSQ and SONET/SDH interfaces, include the trigger-link-failure statement at the [edit lsq-fpc/pic/port lsq-failure-options] hierarchy level. [Services Interfaces]
• LSQ interface enhancement—To inhibit the router from sending PPP termination-request messages to the remote host if the LSQ interface fails, include the no-term-req statement at the [edit interfaces lsq-fpc/pic/port failure-options] hierarchy level. [Services Interfaces]
• Enhancement to the monitor interface traffic command—Interface description information is now displayed when you issue the monitor interface traffic command. [Command Reference: Interfaces]
• CoS RED profiles on LSQ interfaces—Enables you to configure random early detection (RED) on LSQ interfaces as in other class-of-service (CoS) scenarios. To configure, include one or more drop profiles and attach them to a scheduler for a particular forwarding class. The LSQ implementation performs tail RED. It supports a maximum of 256 drop profiles per PIC. Drop profiles are configurable on a per-queue, per-loss priority, and per-Transmission Control Protocol (per-TCP) bit basis. To configure, include the drop-profiles, scheduler-maps, and schedulers statements at the [edit class-of-service] hierarchy level, and include the configured scheduler mapping containing the drop profiles at the [edit class-of-service interfaces lsq-fpc/pic/port] hierarchy level. [Class of Service, Services Interfaces]
• ISDN call and call history information—The new show isdn calls command displays the interfaces configured for calling out, their status, and any calling errors. The new show isdn history command displays the history of ISDN calls, including the calling number, the called number, the interface name, and the duration of the call. [Command Reference: System Basics and Services]
• Please contact Juniper Networks customer support before deploying graceful Routing Engine Switchover when APS is enabled.

Services Applications

• DLSw on J-series routing platforms—Data Link Switching (DLSw) enables you to tunnel System Network Architecture (SNA) traffic over an IP network. To enable DLSw on a router, you must configure a local DLSw peer by including the local-peer statement at the [edit protocols dlsw] hierarchy level. CoS can be used to classify DLSw packets, which are sent to a logical tunnel interface that loops the packets into the Packet Forwarding Engine. The Packet Forwarding Engine classifies and queues the packets based on the configured type-of-service (ToS) value. To configure CoS for DLSw, include the destination-interface destination-interface and type-of-service tos-value statements at the [edit protocols dlsw dlsw-cos] hierarchy level and the dscp default statement at the [edit class-of-service interfaces interface-name unit unit-number classifiers] hierarchy level.

  If the values for the following configuration statements at the [edit protocols dlsw] hierarchy level are modified, any existing DLSw peer connection is torn down when the configuration is committed: connection-idle-timeout, dlsw-cos, local-peer, multicast-address, promiscuous, and receive-initial-pacing. If the remote-peer remote-peer-name statement is added or removed, only that remote peer and its associated circuits are affected. Any changes made to the values for the traceoptions statement do not affect existing peer connections or circuits.

  For information about configuring classifiers, see the Class of Service Configuration Guide. [J-series Configuration Guide, Services Interfaces, Command Reference: System Basics and Services]

• NAT enhancement—Allows you to use dynamic source configuration to translate a large range of addresses to a smaller size pool. The requests from the source address range are assigned to the addresses in the pool until the pool is used up, and any additional requests are rejected. A Network Address Translation (NAT) address assigned to a host is used for all concurrent sessions from that host. The address is released to the pool only after all the sessions for that host expire. This feature enables the router to share a few public IP addresses between several private hosts. Since all the private hosts might not simultaneously create sessions, they can share a few public IP addresses. To configure, include the translation-type source dynamic statement at the [edit services nat rule rule-name term term-name then] hierarchy level. The referenced pool must include a port or address configuration. [Services Interfaces]
• Multilink PPP (MLPPP) support for L2TP shared mode—Enables you to configure many multilink bundles on a single adaptive services interface in Layer 2 Tunneling Protocol (L2TP) shared mode. To configure, include the shared statement at the [edit interfaces sp-fpc/pic/port unit logical-unit-number dial-options] hierarchy level and the tunnel-access-profile and user-access-profile statements at the [edit services l2tp tunnel-group group-name] hierarchy level. [Services Interfaces]
• Dynamic flow capture (T-series and M320 routing platforms)—Enables you to capture packet flows that match a particular filter list and direct them to one or more content destinations using an on-demand control protocol that relays requests from one or more control sources. To configure this feature, include the dynamic-flow-capture statement at the [edit services] hierarchy level. You must specify the identities of the control sources and content destination within the capture-group statement at the [edit services] hierarchy level, and you can optionally set other properties such as system logging, flow thresholds, and notification targets. You can obtain output information using the show interfaces dfc or show services dynamic-flow-capture (content-destination | control-source) commands. You can also clear dynamic flow capture information using the clear services dynamic-flow-capture (criteria | sequence-number) command. To restart processing on the Routing Engine (not PICs that are forwarding traffic), issue the restart dynamic-flow-capture command. [Services Interfaces, Command Reference: System Basics and Services]
• RPM enhancement—Extends support for real-time performance monitoring (RPM) to include TCP, User Datagram Protocol (UDP), and Hypertext Transfer Protocol (HTTP) formats for multiple routing instances. [Services Interfaces]
• IPSec tunnels with dynamic endpoint addresses—Enable you to configure IP Security (IPSec) tunnels using dynamic peer security gateways, in which the remote end of a tunnel does not have a statically assigned IP address. Establishment of the tunnel relies on using Internet Key Exchange (IKE) main mode with preshared global keys. This feature is supported only for next-hop service sets. To configure these tunnels, include the ike statement at the [edit access profile profile-name client client-name] hierarchy level, and include the ike-access-profile statement at the [edit services service-set service-set-name ipsec-vpn-options] hierarchy level. You can configure an interface identifier for a group of dynamic peers by including the ipsec-interface-id statement at the [edit interfaces sp-fpc/pic/port unit logical-unit-number dial-options] hierarchy level. [Services Interfaces, System Basics]
• Enhancement to IPSec match conditions—Enables you to assign a logical interface to the tunnels established as a result of match conditions configured in IPSec rules. To configure this feature, include the ipsec-inside-interface statement at the [edit services ipsec-vpn rule rule-nameterm term-name from] hierarchy level. This statement corresponds to the inside-service-interface statement that you can include at the [edit services service-set service-set-name next-hop-service] hierarchy level. [Services Interfaces]
• SIP application protocol for NAT and stateful firewall services—Enables you to configure the Session Initiation Protocol (SIP), a generalized protocol for communication between endpoints involved in Internet services, such as telephony, fax, videoconferencing, instant messaging, and file exchange. The supported standard is described in RFC 3261, SIP: Session Initiation Protocol, which includes stateful firewall and NAT support for SIP dialogs and UDP IPv4 transport of SIP messages. To configure SIP, include the application-protocol statement at the [edit applications application application-name] hierarchy level. You can clear and display information by issuing the clear services stateful-firewall (sip-call | sip-register) and show services stateful-firewall (sip-call | sip-register) commands, respectively. [Services Interfaces, Command Reference: System Basics and Services]

Routing Protocols

• IS-IS traffic-engineering shortcuts enhancement—The new ignore-lsp-metrics configuration statement at the [edit protocols isis traffic-engineering shortcuts] hierarchy level instructs the system to ignore the metric of the MPLS LSP. This instruction removes the mutual dependency between IS-IS and MPLS for the shortcut computation. If this option is not configured, there may be a short interval during which Intermediate System-to-Intermediate System (IS-IS) prefers the IP hop-by-hop path, even though an MPLS LSP is available.
• Routing table enhancement—To prevent potential routing table inconsistencies, you can limit populating the reverse path forwarding (RPF) inet.2 routing table to only IS-IS routes that use IP addresses—not Multiprotocol Label Switching (MPLS) label-switched paths (LSPs)—as next hops. To do this, include the ipv4-multicast-rpf-routes statement at the [edit protocols isis traffic-engineering] hierarchy level. [Routing]
• OSPF statistics information enhancement—The new show ospf overview command provides information about Open Shortest Path First (OSPF) demand circuit statistics. [Routing Protocols]
• Explicit null option for IPv6-based BGP—Enables you to advertise an explicit null for Border Gateway Protocol (BGP) when using labeled unicast in an IPv6 network. To configure and explicit null, include the explicit-null statement at the [edit protocols bgp group group-name family inet6 labeled-unicast] hierarchy level. [Routing Protocols]
• IS-IS adjacency down reason enhancement—The show isis adjacency extensive command provides output that indicates why an IS-IS adjacency has gone down. The Down-Reason output field indicates that either a hold-time expiration has occurred or a Bidirectional Forwarding Detection (BFD) session down notification has been sent. [Command Reference: Routing and Policies]
• LDP statistics enhancement—The new interfaces keyword that is added to the clear ldp statistics command enables you to clear Label Distribution Protocol (LDP)-related statistics associated with interfaces. [Command Reference: Interfaces]
• BFD version 1 support—The JUNOS implementation of BFD now supports BFD version 1 and automatic version detection. By default, the system is set to automatic detection. To modify the setting, include the bfd-liveness-detection version (0 | 1 | automatic) statement at any of the following hierarchy levels (and at their equivalent [edit logical-routers logical-router-name] hierarchy levels):
  • [edit protocols isis interface interface-name]
  • [edit protocols (ospf | ospf3) area area-id interface interface-name]
  • [edit routing-instances routing-instance-name protocols isis interface interface-name]
  • [edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-id interface interface-name]
  • [edit routing-instances instance-name routing-options rib rib-name static route destination]
  • [edit routing-instances instance-name routing-options rib rib-name static route destination qualified-next-hop next-hop]
  • [edit routing-instances instance-name routing-options static route destination]
  • [edit routing-instances instance-name routing-options static route destinationqualified-next-hop next-hop]
  • [edit routing-options rib rib-name static route destination]
  • [edit routing-options rib rib-name static route destination qualified-next-hop next-hop]
  • [edit routing-options static route destination]
  • [edit routing-options static route destination qualified next-hop next-hop]

    [Routing Protocols]

• Enforce an exact match for advertisement (or restriction) of an area range—To configure this feature, include the exact statement at the [edit protocols ospf area area area-range area-range] or [edit protocols ospf area area area-range area-range restrict] hierarchy level. [Routing Protocols]

MPLS Applications

• Graceful restart for point-to-multipoint LSPs—You can configure graceful restart for point-to-multipoint LSPs. Graceful restart enables a router undergoing a restart to inform its adjacent neighbors of its condition. The restarting router requests a grace period from the neighbor or peer, which can then cooperate with the restarting router. The restarting router can still forward MPLS traffic during the restart period; convergence in the network is not disrupted. The restart is not visible to the rest of the network, and the restarting router is not removed from the network topology. Resource Reservation Protocol (RSVP) graceful restart can be enabled on both transit routers and ingress routers. To enable graceful restart on the router for point-to-multipoint LSPs, include the graceful-restart statement at the [edit routing-options] hierarchy level. [MPLS Applications]
• Routing table enhancement—To prevent the egress router address configured in the to statement at the [edit protocols mpls label-switched-path lsp-path-name] hierarchy level from being added to the inet.3 and inet.0 routing tables, include the no-install-to-address statement at the [edit protocols mpls label-switched-path lsp-path-name] hierarchy level. [MPLS Applications]
• Node and link protection status information enhancements—Several new output fields for existing commands help you evaluate problems related to node protection and link protection. Commands with new output fields include the following: show rsvp session extensive, show rsvp interface extensive, and show rsvp session bypass extensive. [Command Reference: Protocols and Policies]
• Traffic distribution enhancement—By default, when multiple equal-cost RSVP LSPs to the same egress router are available, traffic is distributed equally among the LSPs. You can now distribute traffic unequally among different LSPs. Traffic distribution is proportional to each LSP's configured bandwidth. To distribute traffic among RSVP LSP based on the configured bandwidth, include the load-balance statement with the bandwidth option at the [edit protocols rsvp] hierarchy level. [MPLS Applications]
• LSP subscription enhancement—You can now oversubscribe each class type when configuring a Differentiated-Services-aware traffic engineered LSP. This allows you to configure in excess of the static bandwidth for each class type, making for more efficient network resource utilization for those links. To oversubscribe a class type, include the subscription statement at the [edit protocols rsvp interface interface-name] hierarchy level. You also can now configure automatic bandwidth allocation for a single-class Differentiated-Services-aware traffic engineered LSP. Either the maximum allocation bandwidth constraints model (MAM) or the Russian dolls allocation model (RDM) can be configured. Traffic traversing a single-class Differentiated-Services-aware traffic engineered LSP with automatic bandwidth allocation enabled adjusts its bandwidth in the same manner as a normal LSP with automatic bandwidth allocation enabled. [MPLS Applications]
• RSVP LSP tunnel-in-tunnel capability—You can now tunnel one or more RSVP LSPs into another RSVP LSP. The RSVP LSP tunnel is called a forwarding adjacency (FA) LSP. This LSP must be configured statically and requires that OSPF be configured as the interior gateway protocol (IGP). Fast reroute continues to work for LSPs that traverse an FA LSP. To configure an FA LSP, include the label-switched-path statement at the [edit protocols link-management te-link te-link-name] hierarchy level. [MPLS Applications]

Multicast

• SSM mapping from IGMPv1/IGMPv2 to IGMPv3 PIM—Source-specific multicast (SSM) is supported only on Internet Group Management Protocol version 3 (IGMPv3) hosts; however, not all hosts run IGMPv3. This feature extends SSM support to hosts not running IGMPv3 by translating IGMP version 1/IGMP version 2 (IGMPv1/IGMPv2) reports sent to the router into IGMPv3 reports and using them for defined SSM groups. Both IGMP IPv4 and Multicast Listener Discovery (MLD) IPv6 SSM groups are supported. To configure SSM mapping, include the ssm-map statement at the [edit routing-options multicast] hierarchy level. To apply the SSM mapping to an interface, include the ssm-map ssm-map-name statement at the [edit protocols igmp interface interface-name] or [edit protocols mld interface interface-name] hierarchy level. You also need to configure an SSM map policy at the [edit policy-options policy-statement] hierarchy level. [Multicast]
• Anycast RP for IPv4/IPv6 PIM sparse mode—Multiple rendezvous points (RPs) can be supported with anycast addresses (RPs sharing a single routable IP address). However, implementation has been tied to Multicast Source Discovery Protocol (MSDP), which only works for IPv4. This feature adds anycast RP support using Protocol Independent Multicast (PIM) alone, which allows the method to be used with either IPv4 or IPv6. This feature is compatible with, but does not require, MSDP. To configure anycast RP, include the anycast-pim statement at the [edit protocols pim rp local family inet] or [edit protocols pim rp local family inet6] hierarchy level. [Multicast]

Routing Policy and Firewall Filters

• Enhanced firewall filter matching for IPv6 TCP flag—To match a firewall filter on IPv6 TCP flags, include the tcp-flags statement at the [edit firewall family inet6 filterfilter-name set term term-name from] hierarchy level. [Policy Framework]
• IPv6 port mirroring on M-series and T-series platforms—On T-series platforms and on the M320 router, simultaneous support for both IPv4 and IPv6 port mirroring is provided. On all other M-series routers, either IPv4 or IPv6 port mirroring can be supported at any given time. To configure IPv6 port mirroring, include the inet6 statement at the [edit forwarding-options port-mirroring family] hierarchy level. [Policy Framework]
• Enhanced policy “or longer” match—You can configure prefix qualifiers similar to the ones available for route filters when specifying match criteria in a policy. To configure prefix qualifiers, include the appropriate statement for the qualifier type (exact, longer, or orlonger) at the [edit policy-options policy-statement policy-name policy-name from prefix-list-filter prefix-list-name] hierarchy level. [Policy Framework]

VPNs

• VRF table label support for MLPPP and Multilink Frame Relay (MLFR) interfaces on M-series platforms (except for the M320)—The vrf-table-label statement makes it possible to map the inner label to a specific virtual private network (VPN) routing and forwarding (VRF) routing table. This mapping allows the examination of the encapsulated IP header at an egress VPN router. Include the vrf-table-label statement at the [edit routing-instances instance-name] hierarchy level for MLPPP-encapsulated and MLFR-encapsulated interfaces. The MLPPP-capable or MLFR-capable interface must be configured on a link services intelligent queuing (lsq-fpc/pic/port) interface on an Adaptive Services Module (ASM) or AS PIC on an Enhanced FPC. [Routing Protocols, MPLS Applications]

Class of Service

• Two-rate tricolor marking—For T-series platforms with Enhanced II FPCs, you can configure two-rate tricolor marking (trTCM) as defined in RFC 2698, A Two Rate Three Color Marker. TCM extends the functionality of CoS traffic policing by providing three levels of drop priority instead of two. This capability enables you to provision more granular service-level agreements (SLAs) across the Differentiated Services (DiffServ) domain. You configure TCM by defining tricolor marking policers, and three levels of packet loss priority (PLP) for classifiers, rewrite rules, RED drop profiles, and firewall filters. The color of a packet, as used or set by a tricolor marking policer, corresponds to the packet’s drop precedence (loss priority or PLP). To configure TCM, include the tri-color statement at the [edit class-of-service] hierarchy level. To configure a tri-color marking policer, include the three-color-policer statement at the [edit firewall] hierarchy level. [Class of Service, Policy Framework]
• Large delay buffers for slower interfaces—Enables you to configure larger buffer sizes than were previously supported for DLCIs and T1, E1, and NxDS0 interfaces. Large buffer sizes are supported on the following PICs: 10-port Channelized E1 IQ, Channelized T3 IQ, and Channelized STM1.

  Table 1 lists the maximum scheduler buffer sizes. When large buffer sizes are not enabled, maximum sizes vary by PIC and platform type. When large buffer sizes are enabled, maximum sizes differ by interface type.

  Table 1: JUNOS 7.4 Maximum Scheduler Buffer Sizes

  Platform, PIC, or Interface Type	Maximum Buffer Size
  With Large Buffer Sizes Not Enabled
  T-series and M320	50,000 microseconds
  Other M-series	200,000 microseconds
  IQ PICs on all platforms	100,000 microseconds
  With Large Buffer Sizes Enabled
  Channelized T3 and channelized OC3 DLCIs—Maximum sizes vary by shaping rate:
  With shaping rate from 64,000 through 255,999 bits per second (bps)	4,000,000 microseconds
  With shaping rate from 256,000 through 511,999 bps	2,000,000 microseconds
  With shaping rate from 512,000 through 1,023,999 bps	1,000,000 microseconds
  With shaping rate from 1,024,000 through 2,048,000 bps	500,000 microseconds
  With shaping rate from 2,048,001 through 10 megabits per second (Mbps)	400,000 microseconds
  With shaping rate from 10,000,001 through 20 Mbps	300,000 microseconds
  With shaping rate from 20,000,001 through 30 Mbps	200,000 microseconds
  With shaping rate from 30,000,001 through 40 Mbps	150,000 microseconds
  With shaping rate up to 40,000,001 bps and above	100,000 microseconds
  NxDS0 IQ Interfaces—Maximum sizes vary by channel size:
  1xDS0 through 3xDS0	4,000,000 microseconds
  4xDS0 through 7xDS0	2,000,000 microseconds
  8xDS0 through 15xDS0	1,000,000 microseconds
  16xDS0 through 32xDS0	500,000 microseconds
  Other IQ interfaces	500,000 microseconds

  To enable larger buffer sizes to be configured on an IQ PIC, include the q-pic-large-buffer statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level. To configure buffer sizes, include the buffer-size statement at the [edit class-of-service schedulers scheduler-name] hierarchy level. [Class of Service]

• Extended support for eight queues per port (4-port OC3c/STM1 Type 1 and Type 2 PICs on the M320 router and T-series platforms)—Allows you to configure up to eight queues per port on ports 0 and 2 of the 4-port OC3c/STM1 PIC. When you include the max-queues-per-interface 8 statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level, you can configure up to eight queues on ports 0 and 2. After you commit the configuration, the PIC goes offline and comes back online with only ports 0 and 2 operational. No interfaces can be configured on ports 1 and 3. If you do not include the max-queues-per-interface statement or if you include the max-queues-per-interface 4 statement, you can use all four ports and configure up to four queues per port. [Class of Service, System Basics]

Network Management

• Chassis Management Information Base (MIB) definitions have been updated to support newly released PICs and routing platforms. You can find the enterprise-specific Juniper Networks MIBs at http://www.juniper.net/techpubs/software/index_mibs.html. [Network Management]
• SNMP inform support—Enables you to configure Simple Network Management Protocol (SNMP) informs. SNMP informs are confirmed notifications. Informs are similar to traps, except they are stored and retransmitted at regular intervals until the receiver (target) of the inform returns an acknowledgement to the SNMP agent, or until a specified number of unsuccessful retransmissions are attempted. [Network Management]
• Support for the MPLS Label Switching Router (LSR) MIB as defined in RFC 3813—Read-only access is supported. mplsInterfacePerfTable, mplsInSegmentPerfTable, mplsOutSegmentPerfTable, mplsInSegmentMapTable, mplsXCUp, and mplsXCDown are not supported. [Network Management]
• Enterprise-specific Services PIC MIB—The AS PIC enables you to provide multiple services on a single PIC by configuring a set of services and applications. The Services PIC MIB, whose object identifier is {jnxMibs 32}, sends the current operational status for each AS PIC. [Network Management]
• Enterprise-specific VPN MIB {jnxMibs26}—Includes Layer 2 circuit support. [Network Management]

JUNOScope

• Inventory Management System export to external applications—External inventory applications can connect to the JUNOScope Inventory Management System database and extract Juniper Networks device inventory information via a structured query language (SQL) interface on a MySQL database, an open source relational database management system (RDBMS) that is bundled with the JUNOScope software. The JUNOScope administrator must configure a unique username and password during the JUNOScope software installation to enable read-only access to the Inventory Management System database. The Inventory Management System now includes demo reports and a demo database that are populated with sample data so the user can learn how to use the system without actually scanning for inventory data on the production network. [JUNOScope Software User Guide]
• Multirouter operations labels—The JUNOScope administrator can now create labels that define criteria for a large group of Juniper Networks devices on the network. Operations such as archive configuration and scan inventory can be performed on a large group of routers based on labels. Labels, in free text format, provide a way to define static associations for a group of devices, such as 'Region: North', 'Customer: Important', etc. This complements the existing Groups feature in JUNOScope, which provides a way to define dynamic associations for a group of devices. [JUNOScope Software User Guide]

JUNOS API and Other Scripting

• Table 2 lists the new JUNOScript tags and their corresponding CLI commands.

  Table 2: JUNOS 7.4 JUNOScript Tags and Equivalent CLI Commands

  Request Tag	Response Tag	CLI Command
  <clear-services- dynamic-flow-capture-criteria>	<clear-services- dynamic-flow-capture-criteria>	clear services dynamic-flow-capture criteria
  <clear-services- dynamic-flow-capture-sequence-number>	<clear-services-dynamic-flow-capture- sequence-number-results>	clear services dynamic-flow-capture sequence-number
  <clear-service-set-packet-drop-statistics>	<service-set-packet-drop-statistics>	clear services service-sets statistics packet-drops
  <clear-service-sfw-sip-call-information>	<service-sfw-sip-call-drain-information>	clear services stateful-firewall sip-call
  <clear-service-sfw-sip-register- information>	<service-sfw-sip-register- drain-information>	clear services stateful-firewall sip-register
  <request-system-storage-cleanup>	<system-storage-cleanup-information>	request system storage cleanup
  <get-lm-routing-resource-information>	<lm-resource>	show link-management routing resource
  <get-ospf-overview-information>	<ospf-overview-information>	show ospf overview
  <get-ospf3-overview-information>	<ospf3-overview-information>	show ospf3 overview
  <get-ppoe-interface-information>	<pppoe-interface-information>	show pppoe interfaces
  <get-pppoe-statistics-information>	<pppoe-statistics-information>	show pppoe statistics
  <get-pppoe-version>	<pppoe-version>	show pppoe version
  <get-services-dynamic-flow-capture- content-destination-information>	<services-dynamic-flow-capture-content- destination-information>	show services dynamic-flow-capture content-destination
  <get-services-dynamic-flow-capture- control-source-information>	<services-dynamic-flow-capture- control-source-information>	show services dynamic-flow-capture control-source
  <get-service-set-packet-drop-statistics>	<service-set-packet-drop-statistics>	show services service-sets statistics packet-drops
  <get-service-sfw-sip-call-information>	<service-sfw-sip-call-information>	show services stateful-firewall sip-call
  <get-service-sfw-sip-register-information>	<service-sfw-sip-register-information>	show services stateful-firewall sip-register
  <get-snmp-inform-statistics>	<snmp-inform-statistics>	show snmp inform-statistics
  <get-dhcp-global-information>	<dhcp-global-information>	show system services dhcp global

  [JUNOScript Reference]

• Indicator for configuration identifiers—Client applications can request that the JUNOScript server's response to a <get-configuration> request indicate that a child tag element is an identifier for its parent tag element. As the indicator, the junos:key="key" attribute is included in the opening tag for each identifier tag element. To request the indicator, a JUNOScript client that uses the Perl module provided by Juniper Networks provides the junos_key => 1 parameter to the JUNOS::Device object along with the four parameters required by the object (access, hostname, login, and password). A JUNOScript client that does not use the Perl module includes the junos:key="key" attribute in the opening <junoscript> tag that it emits at the beginning of the JUNOScript session. [JUNOScript Reference]
• JUNOS software configuration commit scripts (J-series, M-series, and T-series platforms)—Enable you to use scripts that run at commit time to enforce custom configuration rules. If a configuration breaks the custom rules, the script can generate actions that the JUNOS software performs. These actions include:
  • Generating custom error messages
  • Generating custom warning messages
  • Generating custom system log messages
  • Making changes to the configuration

  Configuration commit scripts also enable you to create macros, which expand simplified custom aliases for frequently used configuration statements into standard JUNOS configuration statements. Commit scripts are written in Extensible Stylesheet Language Transformations (XSLT). [Configuration Scripting]