Release 7.1 Features

The following features have been added to JUNOS Release 7.1. 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 2.

Changes in Default Behavior and Syntax

• Combinations of PICs—On Juniper Networks routing platforms, you can typically install any combination of Physical Interface Cards (PICs) on a single Enhanced Flexible PIC Concentrator (FPC). On M5, M10, M20, M40, M40e, and M160 routers, there are some combinations of PICs that cannot be installed together on the same Enhanced FPC. The possible combinations for JUNOS Release 7.1 differ from Release 7.0R1. For more information, please consult Technical Bulletin PSN-2004-12-002 on the Juniper Networks Support Web site at http://www.juniper.net/support/.
• Ethernet virtual LAN-tagged (VLAN-tagged) keepalive packets have priority set to 110. Previously, the priority for these packets was 100. [Network Interfaces]
• The show system license command now corresponds to the JUNOScript tag <get-license-summary-information> and the response tag <license-summary-information>. The show system license installed command now corresponds to the <get-license-information> and <license-information> tags. These tags apply on J-series platforms only. [JUNOScript Operational Reference]
• Class-of-service (CoS) scheduler configuration—You can no longer configure both the transmit-rate exact and priority strict-high statements at the [edit class-of-service schedulers] hierarchy level at the same time. This configuration causes conflicting behavior and unexpected results. The restriction applies to all platforms that run the JUNOS software. [Network Interfaces]
• Adaptive Services PIC system log messages—System log messages generated by the Adaptive Services PIC now conform to the standards and procedures used with other types of JUNOS system log messages. Updated documentation for these messages appears in the JUNOS System Log Messages Reference, and replaces the information previously located in the Appendix of the JUNOS Services Interfaces Configuration Guide. Some of the message strings have been revised for conformity with other JUNOS message types, which might require you to update customized search engines. [Services Interfaces, System Log Messages Reference]
• By default, starting with Releases 6.4R3 and 7.0R1, Ethernet VLAN-tagged network-control packets have IEEE 802.1p bits set to 110. Previously, these bits were set to 000 by default. [Network Interfaces]
• Modifications to MLPPP processing on link services (ls-), link services intelligent queuing (IQ) (lsq-), and multilink (ml-) interfaces (Adaptive Services, Link Services, and Multilink Services PICs)—Provides RFC 1990-compliant multilink Point-to-Point Protocol (MLPPP) interoperability with other vendors' equipment. The routing platform now compares the local family maximum transmission unit (MTU) with the maximum received reconstructed unit (MRRU) of the remote peer. If the MRRU value of the peer is lower than the local family MTU value, the routing platform adjusts the family MTU by lowering the bundle link MTU. In addition, the MRRU or MTU values of the remote peer do not overwrite the family MTU value unless the new value is smaller than the current one. The new functionality is available by default when you configure MLPPP on supported interfaces. Previously the MRRU of the remote peer was compared with the local MRRU, and the MRRU or MTU values of the remote peer might have overwritten the family MTU value incorrectly. [Services Interfaces]
• New requirement for graceful Routing Engine switchover—If you enable graceful Routing Engine switchover and include the backup-router or inet6-backup-router statement at the [edit system] hierarchy level, you must now specify a destination address so the default route can be shared between the master Routing Engine and the backup Routing Engine. To configure a destination address on the master Routing Engine, include the destination statement at the [edit system (backup-router | inet6-backup-router) address] hierarchy level and specify the address for the destination. [System Basics]
• When the Layer 2 Tunneling Protocol (L2TP) network server (LNS) is configured with RADIUS authentication, the default behavior is to accept the preferred RADIUS-assigned IP address. Previously, the default behavior was to accept and install the nonzero peer IP address specified in the IP-Address field of the Internet Protocol Control Protocol (IPCP) Configuration Request packet. [System Basics]
• The default behavior of the JUNOS Border Gateway Protocol (BGP) implementation is changed. With the new behavior, the JUNOS software does not advertise the routes learned from one external BGP (EBGP) peer back to the same EBGP peer. In addition, the software does not advertise those routes back to any EBGP peers that are in the same AS as the originating peer, regardless of the routing instance. You can modify this behavior by including the advertise-peer-as statement in the configuration. Additionally, if the as-override statement is included in the configuration, the new default behavior is disabled. To explicitly restore the new default behavior, include the no-advertise-peer-as statement in the configuration. If you include both the as-override and no-advertise-peer-as statements, the no-advertise-peer-as statement is ignored. You can include these statements at multiple hierarchy levels; for a list, see the appropriate statement summary. [Routing Protocols]

Hardware

• Support for copper-based 1000Base-T SFPs—Support for copper-based small form-factor pluggable transceivers (SFPs) is extended to the following PICs and platforms:
  • 1-port Gigabit Ethernet Fixed Interface Card (FIC) on the M7i platform
  • 10-port Gigabit Ethernet PIC on T-series and M320 platforms
  • Gigabit Ethernet IQ PICs on all platforms that currently support Gigabit Ethernet IQ PICs [M-series and T-series PIC Guides]

    Currently shipping copper SFPs (SFP-1GE-T) cause mechanical interference when installed in the 10-port Gigabit Ethernet PIC (PC-10GE-SFP). New copper SFPs will be qualified and faceplate modifications will be made to the 10-port Gigabit Ethernet PIC to resolve this issue. Field Alerts PSN-2005-02-005 and PSN-2005-02-008 will describe the suggested resolution, when available.

• 1-port Channelized OC3 IQ PIC, Type 1 (M7i, M10i, M160, M320, and T320 platforms)—Enables you to configure one OC3 SONET/SDH interface, up to three T3 interfaces, up to 84 T1 interfaces, and DS0 interfaces (the maximum number of DS0 interfaces depends on the platform). To configure interfaces, include the no-partition interface-type statement or the partition, oc-slice, interface-type, and timeslots statements at the [edit interfaces interface-name] hierarchy level. [M-series and T320 PIC Guides, Feature Guide, Network Interfaces]
• Enhancement to the 1-port 10-Gigabit Ethernet PIC—On M320 and T-series routing platforms, extends support for the following optics: XENPAK-SR and XENPAK-ZR. [M-series and T-series PIC Guides, Command Reference: Protocols]
• Support for SONET/SDH PICs on T320, T640, and TX Matrix platforms—The single-mode, intermediate reach, 4-port OC3c/STM1 SONET/SDH PIC is now supported on T640 routing nodes. Also, the multimode, 1-port OC12c/STM4 SONET/SDH PIC is now supported on the T320, T640, and TX Matrix platforms. [T-series PIC Guides]

User Interface and Configuration

• System logging of interactive commands—The JUNOS factory configuration file includes the interactive-commands any statement at the [edit system syslog file interactive-commands] hierarchy level. It creates the file /var/log/interactive-commands and records in it all messages from the interactive-commands facility. The factory configuration becomes active when there is no other configuration available. [System Basics]
• Enhancement to the show version command—For routers with dual Routing Engines, two options are provided to display the hostname and software version. The all-routing-engines option displays information about both Routing Engines. The other-routing-engine option displays information about the other Routing Engine. To use these options, issue the show version invoke-on (all-routing-engines | other-routing-engine) command. [Command Reference: Protocols]
• Enhancement to TACACS+ authorization—By default, the JUNOS software sends an authorization request to the TACACS+ server and asks for the junos-exec service upon authenticating a user. You can specify which service the JUNOS software asks for. To configure, include the service-name statement at the [edit system tacplus-options] hierarchy level. [System Basics]

Interfaces and Chassis

• Key value for GRE tunnels (Adaptive Services PICs on M-series platforms, except the M320 router)—Enables you to assign a key value to identify an individual traffic flow within a generic routing encapsulation (GRE) tunnel, as defined in RFC 2890, Key and Sequence Number Extensions to GRE. To configure, include the key statement at the [edit interfaces interface-name unit logical-unit-number tunnel] hierarchy level. [Network Interfaces, Services Interfaces]
• Enhancement to IPCP—Enables you to configure the IPCP to negotiate IP address assignments and to transmit network-related information such as Windows Name Service (WINS) and Domain Name System (DNS) servers, as defined in RFC 1877, PPP Internet Protocol Control Protocol Extensions for Name Server Addresses. To enable an interface to obtain an IP address from the remote end, include the negotiate-address statement at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level. To configure an interface to be unnumbered, include the unnumbered-interface and destination statements at the [edit interfaces interface-name unit logical-unit-number family inet] hierarchy level. To assign PPP properties to the remote end, include the destination-profile statement at the [edit interfaces interface-name unit logical-unit-number family inet address address] or [edit interfaces interface-name unit logical-unit-number family inet unnumbered-interface interface-name] hierarchy level. [Network Interfaces]
• C2 SONET/SDH overhead byte—SONET/SDH interfaces use the C2 byte to indicate whether the content of the payload inside the frame is scrambled. To configure, include the bytes c2 statement at the [edit interfaces so-fpc/pic/port sonet-options] hierarchy level. [Network Interfaces]
• Extended support for eight egress queues on lower-speed IQ interfaces (E1, lower-speed Frame Relay, NxDS0, and T1 IQ interfaces on M320 and T-series platforms)—Enables you to configure up to eight egress queues on lower-speed IQ interfaces. To configure, include the max-queues-per-interface statement with the 8 option at the [edit chassis fpc slot-number pic pic-number] hierarchy level and the queue statement at the [edit class-of-service forwarding-classes] hierarchy level. [Network Interfaces, System Basics]
• Expanded support for DLCI scheduling and LFI for Link Services and Channelized DS3 IQ PICs (M10i and M20 platforms)—Enables packets entering the Link Services PIC to be fragmented before transmission to the Channelized DS3 IQ PIC. Once the fragmented packets enter the Channelized DS3 IQ PIC, they are scheduled at the data-link connection identifier (DLCI) level, to allow priority transmission for real-time applications. To configure link fragmentation and interleaving (LFI), include the interleave-fragments statement at the [edit interfaces ls-fpc/pic/port unit logical-unit-number] hierarchy level. To enable scheduling on the DS3 interface, include the per-unit-scheduler statement at the [edit interfaces t3-fpc/pic/port] hierarchy level; to associate a scheduler with an interface, include the scheduler-map statement at the [edit class-of-service interfaces t3-fpc/pic/port unit logical-unit-number] hierarchy level; to configure shaping on an interface, include the shaping-rate statement at the [edit class-of-service interfaces t3-fpc/pic/port unit logical-unit-number] hierarchy level. [Network Interfaces]
• Real-Time Performance Monitoring (RPM)—Enables you to configure active probes to track and monitor traffic. Probes are collected on a per-destination and per-application basis, including the following:
  • Ping Internet Control Message Protocol (ICMP) packets
  • User Datagram Protocol and Transmission Control Protocol (UDP/TCP) packets with user-configured ports
  • User-configured, Differentiated Services code point (DSCP) type-of-service (ToS) packets
  • Web Hypertext Transfer Protocol (HTTP)

  RPM provides management information base (MIB) support with extensions to comply with RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations. Both configuration and probe results are supported by the JUNOS command-line interface (CLI) and Simple Network Management Protocol (SNMP). When configured thresholds are exceeded, system log messages are generated, as well as SNMP traps (if configured). [Services Interfaces, Command Reference: Interfaces]

• Expanded macros for flow collection—Enables you to configure the flow-collection feature using additional macros to specify an FTP destination path. The additional macros help you store files in well-organized directories on the external collector machine. [Services Interfaces, Feature Guide]
• Extended support for passive monitoring and flow collection—Passive monitoring and flow collection are now supported on Monitoring Services II PICs installed in T-series and M320 routing platforms. [Services Interfaces, Feature Guide]
• Extended support for the ES PIC—All features of the ES PIC are now supported on T-series and M320 routing platforms, with the exception of the authentication header (AH) security protocol. [System Basics, Services Interfaces, Network Interfaces]
• LFI support on Voice Services PICs—Adds support for LFI when you configure the compressed Real-Time Protocol (RTP) on voice services (vsp) interfaces. By default, LFI is always active when you include the compression rtp statement at the [edit interfaces vsp-fpc/pic/port unit logical-unit-number] hierarchy level. You control the operation of LFI indirectly by setting the fragment-threshold statement on the same logical interface. Additional output is also available for existing show commands. [Services Interfaces, Command Reference: Interfaces]
• PPPoE for J-series Services Routers—When a J-series Services Router functions as customer-premises equipment (CPE), enables you to maintain PPP over Ethernet (PPPoE) sessions between the J-series Services Router and an access concentrator (AC). To configure the underlying Fast Ethernet interface, include the encapsulation ppp-over-ether statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level; to configure the PPPoE logical interface, include the access-concentrator, auto-reconnect, service-name, and underlying-interface statements at the [edit interfaces pp0 unit logical-unit-number] hierarchy level; to get information about a PPPoE interface, issue the show interfaces pp0.logical-unit-number and show pppoe commands. Note that multiple access concentrators on the same physical interfaces are not supported. [J-series Services Router User Guide, Network Interfaces]
• AS PIC service packages (AS PICs on all platforms and the ASM in the M7i platform)—Enables you to configure the Adaptive Services (AS) PIC to support the Layer 2 or Layer 3 service package. In general, the Layer 2 service package includes link services and tunnel services. The Layer 3 service package includes security, accounting, tunnel, LNS, and voice services. The specific services supported in each package differ by PIC and platform type. To configure a service package on an AS PIC or on an Adaptive Services Module (ASM), include the service-package statement at the [edit chassis fpc slot-number pic pic-number adaptive-services] hierarchy level. [System Basics, Network Interfaces, Services Interfaces]
• LSQ interfaces on the AS PIC or ASM (AS PICs on all platforms and the ASM in the M7i platform)—When you configure an AS PIC or ASM to support the Layer 2 service package, enables you to configure link services intelligent queuing (LSQ) interfaces on the PIC. LSQ interfaces support JUNOS software CoS components, LFI (FRF.12), Multilink Frame Relay (MLFR) user-to-network interface (UNI) network-to-network interface (NNI) (FRF.16), and MLPPP, as described in RFC 1990, The PPP Multilink Protocol (MP). To configure, include the service-package statement at the [edit chassis fpc slot-number pic pic-number adaptive-services] hierarchy level, and specify layer-2. For MLPPP, include the bundle lsq-fpc/pic/port.logical-unit-number statement at the [edit interfaces interface-name unit logical-unit-number encapsulation ppp family mlppp] hierarchy level. For FRF.16, include the mlfr-uni-nni-bundles statement at the [edit chassis fpc slot-number pic slot-number] hierarchy level and the bundle lsq-fpc/pic/port:channel statement at the [edit interfaces interface-name unit logical-unit-number family mlfr-uni-nni] hierarchy level. For LSQ interfaces, JUNOS CoS components are fully supported and are handled normally. Additionally, you can configure the percentage of total bundle bandwidth to be set aside for link-layer overhead by including the link-layer-overhead statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level; and you can define fragmentation properties for individual forwarding classes by including the fragmentation-maps statement at the [edit class-of-service] hierarchy level. [Network Interfaces, Services Interfaces, System Basics]

  Please contact Juniper Networks customer support before implementing the LSQ feature.

• Support has been added for the show services stateful-firewall statistics family of operational mode commands. [Command Reference: Interfaces]
• Congestion control for chassis queues—Enables you to avoid congestion by controlling the aggregated traffic transmitted from the chassis queues into the PIC. To do so, configure the chassis queues to derive their scheduling configuration from the associated logical interfaces, or assign a custom scheduler to the packet forwarding component queues. To configure derived scheduling, include the scheduler-map-chassis derived statement at the [edit class-of-service interfaces interface-name] hierarchy level. To assign a custom scheduler, include the scheduler-map-chassis map-name statement at the [edit class-of-service interfaces interface-name] hierarchy level. [Network Interfaces]

Routing Protocols

• OSPF point-to-point interfaces—Enables you to configure an Ethernet or aggregated Ethernet interface as a point-to-point interface. This allows the network to treat LAN interfaces with only two routers connected to them as point-to-point interfaces in Open Shortest Path First (OSPF). OSPF treats point-to-point interfaces and broadcast interfaces differently in terms of establishing neighbor adjacencies, flooding of link-state advertisement (LSA) messages, and representation of the network topology, as well as the shortest path first (SPF) calculation and protocol packets destination addresses. The operation of OSPF on point-to-point interfaces is relatively simple compared to LAN interfaces and there is no need to have a designated router.

  To configure an interface as an OSPF point-to-point interface, include the point-to-point statement at the [edit protocols ospf area area-id interface interface-name] hierarchy level. [Routing Protocols]

• Failure detection for static routes using the BFD protocol—The bidirectional forwarding detection (BFD) protocol is a simple hello mechanism that detects failures in a network. To enable failure detection for static routes, include the bfd-liveness-detection statement at the [edit routing-options static route address] or [edit routing-options static route address qualified-next-hop address] hierarchy level. [Routing Protocols]
• Route resolution enhancements—Enables you to configure route resolution to accept routes from specific routing tables and to use specific import policies to produce a resolution routing table. To configure route resolution, include the resolution statement at the [edit routing-options] hierarchy level. [Routing Protocols]

  Please contact Juniper Networks customer support before implementing this feature.

• BGP multipath enhancement—Enables you to disable the default requirement that paths accepted by BGP multipath must have the same neighboring autonomous system (AS). To configure, include the multiple-as statement at the [edit protocols bgp group group-name multipath] or [edit protocols bgp group group-name neighbor name multipath] hierarchy level. [Routing Protocols]

MPLS Applications

• RSVP multiple link bypass—Enables you to signal multiple bypasses concurrently for a link. To enable this feature, first configure link protection or node link protection by including the link-protection or node-link-protection statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. To configure a Resource Reservation Protocol (RSVP) interface to include multiple bypasses, specify both the bandwidth statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level and the max-bypasses statement at the [edit protocols rsvp interface interface-name] hierarchy level. [MPLS]

  Please contact Juniper Networks customer support before implementing RSVP multiple link bypass.

• LSP ping enhancement—Enables you to issue a label-switched path (LSP) ping command across a network that includes a route reflector. [MPLS]
• Bypass link protection priority—Enables you to configure a priority for a bypass link protection path. To configure the priority, include the priority statement at the [edit protocols rsvp interface interface-name link-protection bypass bypass-name] hierarchy level. [MPLS]
• Clear LDP sessions—Enables you to clear Label Distribution Protocol (LDP) sessions manually by issuing the clear ldp session command. You can clear the LDP session for a routing instance, an IP destination, or a logical router. If you specify no options, the default action is to clear all LDP sessions in the master routing instance. [Command Reference: Protocols]
• J-series support for MPLS—J-series routers now support Multiprotocol Label Switching (MPLS), including the push, pop, swap, multiple-push, and swap-and-push label operations. LDP, RSVP, and circuit cross-connect (CCC) are also now supported on J-series Services Routers. [J-series Services Router User Guide]
• MPLS optimize timer—Enables you to configure the optimize timer when a link traversed by a label-switched path goes down. To configure, include the optimize-timer statement at the [edit protocols mpls] or [edit protocols mpls label-switched-path pathname] hierarchy level. The default value is 180 seconds. [MPLS]

VPNs

• Data-MDT tunnels for multicast over VPNs—Eliminate the need to flood multicast packets to provider edge (PE) routers within a virtual private network (VPN) group that do not need to receive those packets (PE routers that have no end recipients for the multicast traffic). A tunnel is established between the source router and its PE router. Other PE routers that have receivers for the multicast traffic connect to this tunnel. The tunnel, called a data-driven multicast distribution tree (data-MDT) tunnel, is created based on the multicast data in the VPN.

  To specify when to create a new data-MDT tunnel, configure the maximum threshold value for a source router or VPN group pair by including the rate statement at the [edit routing-instances instance-name protocols pim mdt threshold source source-IP-address group group-name] hierarchy level. The data rate is specified in kilobits per second (Kbps). To specify the maximum number of data-MDT tunnels that can be created for a single routing instance, include the tunnel-limit statement at the [edit routing-instances instance-name protocols pim mdt] hierarchy level. To specify the IP group range used when a new data-MDT tunnel needs to be initiated on the PE router, include the group-range statement at the [edit routing-instances instance-nameprotocols pim mdt] hierarchy level. [Multicast, VPNs]

• Layer 2 circuit termination—Enables you to terminate a Layer 2 circuit locally on a PE router, similar to a CCC local interface switch. This capability allows switching between Frame Relay DLCIs. The interfaces can be protected with Automatic Protection Switching (APS). To configure a locally terminated circuit, include the local-switching statement at the [edit protocols l2circuit] hierarchy level. [VPNs]
• IP header filtering in Layer 3 VPN applications—Enables you to filter traffic based on the IP header by including the vrf-table-label statement at the [edit routing-instance routing-instance-name] hierarchy level. This functionality is supported on the 4-port Gigabit Ethernet PIC and the 4-port Gigabit Ethernet PIC with SFPs on M-series and T-series routing platforms. [VPNs]
• J-series support for VPNs—J-series Services Routers now support Layer 2 VPNs, Layer 3 VPNs, and VPN routing and forwarding (VRF) table label forwarding and filtering. [J-series Services Router User Guide]

  If you plan to configure a large number of Layer 3 VPN routes with unique next hops, please contact Juniper Networks customer support.

Class of Service

• CoS for IPSec tunnels (ES PIC on T-series and M-series platforms with Enhanced FPCs)—CoS information is preserved inside IP Security (IPSec) tunnels. The ES PIC copies the ToS byte from the inner IP header to the GRE or IP-IP header. No configuration is necessary. [Network Interfaces]
• CoS for tunnels (Adaptive Services, Link Services, and Tunnel PICs on T-series and M-series platforms with Enhanced FPCs)—CoS information is preserved inside GRE and IP-IP tunnels. To configure, include the tunnel statement at the [edit interfaces ip-fpc/pic/port unit logical-unit-number] or [edit interfaces gr-fpc/pic/port unit logical-unit-number] hierarchy level, include the rewrite-rules statement at the [edit class-of-service] and [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy levels, and include the loss-priority and forwarding-class statements at the [edit firewall filter filter-name term term-name then] hierarchy level. As an alternative to modifying the firewall configuration, you can include the classifiers statement at the [edit class-of-service] hierarchy level. [Network Interfaces]
• Enhancement to DSCP rewrite rule—Enables you to use the packet loss priority (PLP) field when defining a DSCP rewrite rule. To configure, include the loss-priority statement at the [edit class-of-service rewrite-rules dscp rewrite-name forwarding-class class-name] hierarchy level and the dscp statement at the [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] hierarchy level. [Network Interfaces]

Routing Policy and Firewall Filters

• Filtering based on FEC criteria—Enables you to count or police packets of each forwarding equivalence class (FEC) for ingress and transit LDP traffic. To configure, include the interface or interface-set statement at the [edit firewall filter filter-name from] hierarchy level. The interface and interface-set statements are mutually exclusive. The interface statement enables you to configure a single interface as a match condition. The interface-set statement enables you to configure multiple interfaces as a match condition. You also need to include the filter at the [edit protocols ldp policing fec class ingress-traffic] or [edit protocols ldp policing fec class transit-traffic] hierarchy level. If traffic does not match any of the terms of the filter, the default action is to pass all packets and not apply policers. [Policy Framework, MPLS]
• TTL matching criteria—Enables you to configure firewall filter matching based on time-to-live (TTL) timer values, on T-series and M320 routing platforms only. [Policy Framework]

Network Management

• Enhancement to the show snmp command—Enables you to display local MIB object values through the CLI instead of a network management system (NMS). Issue the show snmp mib (get | get-next | walk) name command. [Command Reference: Protocols]
• Chassis 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]
• The Ping MIB contains new objects. [Network Management]
• J-series support for MIB definitions—Chassis MIB definitions have been updated to support J-series Services Routers. You can find the enterprise-specific Juniper Networks MIBs at http://www.juniper.net/techpubs/software/index_mibs.html.

JUNOScope

• RADIUS authentication—Allows users with RADIUS accounts to log in to the JUNOScope software. To enable, configure one or more RADIUS authentication servers to share user account information with a JUNOScope server, set up the JUNOScope software to share user account information with one or more RADIUS authentication server hosts, and add users in JUNOScope to reference user account information on the RADIUS authentication server. [JUNOScope Guide, System Basics]

JUNOScript and other APIs

• Table 1 lists the new JUNOScript tags and their corresponding CLI commands. [JUNOScript Reference]

  Table 1: JUNOS 7.1 JUNOScript Tags and Equivalent CLI Commands

  show ldp fec-filters	<get-ldp-fec-filters-information>	<ldp-fec-filters-information>
  show pfe statistics traffic	<get-pfe-statistics>	<pfe-statistics>
  show pim mdt	<get-pim-mdt-information>	<pim-mdt-information>
  show route instance operational	<get-operational-routing-instance- information>	<operational-routing-instance- information>
  show services rpm active-servers	<get-active-servers>	<active-servers>
  show services rpm history-results	<get-history-results>	<history-results>
  show services rpm probe-results	<get-probe-results>	<probe-results>
  show services service-sets summary	<get-service-set-summary-information>	<service-set-summary-information>
  show services stateful-firewall statistics	<get-service-sfw-statistics-information>	<service-sfw-statistics-information>
  show snmp mib get	<get-snmp-object>	<snmp-object-information>
  show snmp mib get-next	<next-snmp-object>	<snmp-object-information>
  show snmp mib walk	<walk-snmp-object>	<snmp-object-information>
  show system configuration rescue	<get-rescue-information>	<rescue-information>
  show system license installed	<get-license-information>	<license-information>
  show system license keys	<get-license-key-information>	<license-key-information>