Changes in Default Behavior and Syntax

Hardware

• Combinations of PICs—On Juniper Networks routing platforms, you can typically install any combination of Physical Interface Cards (PICs) in a single Enhanced Flexible PIC Concentrator (FPC). Newer JUNOS services for some PICs can require significant Internet Processor ASIC memory, and some configuration rules might limit certain combinations of PICs on some platforms. To conserve memory, group PICs in the same family together on the same FPC. Ethernet and SONET/SDH PICs typically do not use large amounts of memory. Adaptive Services, Asynchronous Transfer Mode (ATM) 2, Gigabit Ethernet, and IQ serial PICs use more.

  Configuration rules might apply to PICs installed on standard Enhanced FPCs on the following routing platforms: M5, M10, M20, M40, M40e, M160, M320, J20, T320, and T640.

  Configuration rules do not apply to PICs installed in the following routers or FPCs:

  • J-series, M7i, M10i, or M120 routers
  • Enhanced Plus FPCs on M-series and J20 routers
  • Enhanced Scaling FPCs

  When you upgrade the JUNOS software, a warning appears if any configuration rules affect your PIC combinations. If you continue the installation, the PICs appear to be online (the LEDs are on), but the JUNOS software cannot enable them and they cannot pass traffic. As a workaround, you need to plan which PICs to install on the Enhanced FPCs or PIC slots on your routing platform. For information about PIC combinations in previous JUNOS releases, consult JTAC Technical Bulletin PSN-2007-01-023, which is accessible at https://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2007-01-023 (you need to provide your Juniper Networks username and password). For information about PIC combinations in the current beta period, please consult the Technical Bulletins section of the JUNOS beta page accessible at http://www.juniper.net/beta/junos.

Platform and Infrastructure

• Enhancements to the clear dhcp relay binding and show dhcp relay binding commands (M-series, MX-series, and T-series routing platforms)—The clear dhcp relay binding and show dhcp relay binding operational commands are enhanced for the extended DHCP relay agent. You can use the clear dhcp relay binding command to clear the binding state of a DHCP client from the client table. You can use the show dhcp relay binding command to display information about the address bindings in the DHCP client table.

  The clear dhcp relay binding command now provides the following enhancements:

  • all option—You can use the all option for all forms of the command to clear the binding state for all DHCP clients.
  • interface option—You can use the interface option for all forms of the command to clear the binding state for DHCP clients on a specified interface.

  The show dhcp relay binding command now provides the following enhancements:

  • Summary information—You can now view summary counts of the total number of DHCP clients and the number of DHCP clients in each state. This new information appears in the output of the show dhcp relay binding and show dhcp relay binding detail commands.
  • The interface option—You can use the interface option for the show dhcp relay binding and show dhcp relay binding detail commands to display information for DHCP clients on the specified interface.
  • The mac-address option—You can use the mac-address option for all forms of the command to display information for DHCP clients by their MAC address.

  [Routing Protocols and Policies Command Reference]

• Behavior change for a loopback interface—For logical loopback interface lo0.16385, IPv6 link-local addresses are no longer created by default. Previously, an IPv6 link-local address was configured automatically by the JUNOS software for the lo0.16385 interface. [Interfaces Command Reference]
• Operational mode output change (J2320, J2350, J4350, and J6350 Services Routers)—Previously, the show chassis fpc command output for selected J-series Services Routers showed just the slot into which a 2-slot-high PIM was physically inserted. Now the show chassis fpc, show chassis fpc slot, and show chassis fpc slot detail commands also indicate the slot that is unusable. [J-series Basic Configuration, Interfaces Command Reference]
• Change for source routing—The source-routing statement has been removed from the [edit logical-routers logical-router-name routing-options] and [edit routing-instances routing-instance-name routing-options] hierarchy levels. If you need to configure source routing, include the source-routing statement at the [edit routing-options] hierarchy level. [Routing]
• Change in fan alarm behavior (MX-series routers)—When the conditions that cause a fan alarm to be activated are removed, the alarm now resets automatically. Previously, you had to clear the alarm manually. [System Basics and Services Command Reference]
• New alarm for unsupported AC PEM configurations (MX-series routers)—The red alarm “Inv AC Cfg” is now displayed when you install only one Power Entry Module (PEM) in an MX-series router or install two or more PEMs in only odd slots or even slots. To avoid triggering the alarm, you must install one PEM in an odd-numbered slot and the other in an even-numbered slot. [MX-series Hardware Guide]

User Interface and Configuration

• Displaying core files (T-series routing platforms)—The new show system core-dumps command displays system core files created when the router fails. [System Basics, System Basics and Services Command Reference]
• force option for synchronized commit operations (M-series and T-series routing platforms with dual Routing Engines)—Enables you to perform a synchronized commit operation even when there are open configuration sessions or uncommitted changes on the second Routing Engine. The standard commit synchronize command fails if either condition holds. To force the synchronized commit operation, include the new force option with the commit synchronize command. It terminates open configuration sessions and discards uncommitted changes on the second Routing Engine, copies the configuration from the first Routing Engine to the second, and commits the configuration on both Routing Engines. [CLI User Guide]
• Routing Engine redundancy change (M-series and T-series routing platforms with dual Routing Engines)—In JUNOS Release 8.4 and later, you can configure only one Routing Engine as the master (you can include only one of the re0 master and re1 master statements at the [edit chassis redundancy routing-engine] hierarchy level). If you attempt to commit a configuration that designates both Routing Engines as the master, the commit operation fails. [System Basics]
• Logical router support with BFD—The show bfd session operational mode command now displays information about active BFD sessions for logical routers. For information about a specific logical router, use the logical-router logical-router-name option. For information about all configured logical routers, use the logical-router all option. [Routing Protocols and Policies Command Reference]
• Enhancement to system log message help—The help syslog command has been modified to accept regular expressions, which provides you the ability to refine the list of messages with more precision. [System Log]
• New scripting functionality for XSLT/SLAX—A new operational script option called jcs:split() is similar to the split feature in PERL scripting. This option allows you to split a string based on the delimiters. [Automation]
• Using an IPv6 source address for system log messages—Enables you to specify an IPv6 address as the source address reported in system log messages that are directed to a remote machine. Previously, IPv4 addresses were allowed, but not IPv6 addresses. The UDP source port for IPv6 is 514 (as specified in RFC 3164). To set the source address, include the source-address address statement at the [edit system syslog] hierarchy level. [System Basics, System Log]
• Tracking IS-IS and OSPF graceful restart events—Enables you to track the progress of a graceful restart event for IS-IS and OSPF/OSPFv3. Include the graceful-restart statement at the [edit protocols (isis | ospf | ospf3) traceoptions flag] hierarchy level. [High Availability]
• Displaying system statistics for MX-series routers—The new bridge option to the show system statistics command displays system statistics on MX-series routers. [System Basics and Services Command Reference]

Interfaces and Chassis

• New configuration statement for E3 interfaces—You can include the invert-data statement at the [edit interfaces interface-name e3-options] hierarchy level. This statement inverts the transmission of unused data bits on the E3 interface, which is needed to make the interface compatible with another vendor’s E3 interface. [Network Interfaces]
• Modification to a VRRP operational mode command—When you issue the show vrrp summary | match interface-name command, the order in which the fields appear in the output has changed to the following: Interface, Int state, Group, VR state, Type, Address. Also, the information that formerly appeared in the Unit field is now included in the Address field. [Interfaces Command Reference]
• Upgrade behavior for MAC addresses (MX-series routers)—When you upgrade an MX-series router to JUNOS Release 8.4 from an earlier JUNOS software release, the MAC addresses for Gigabit Ethernet and 10-Gigabit Ethernet interfaces change. [Network Interfaces]
• Support for priority-tagged packets in native VLANs (Gigabit Ethernet and 10-Gigabit Ethernet interfaces installed in MX-series routers)—When you include the native-vlan-id statement for a logical interface on a Gigabit Ethernet or 10-Gigabit Ethernet interface in an MX-series router, the logical interface now accepts priority-tagged Ethernet frames with the VLAN identifier set to zero (0), as well as untagged frames and frames tagged with the native VLAN ID. Previously, priority-tagged frames were not accepted automatically on the native VLAN. [Network Interfaces]
• Implicit multiservice family for Ethernet OAM (Ethernet-based interfaces on M320, MX-series, and T-series routing platforms)—When you configure a logical interface unit for an Ethernet-based interface on routers that support Ethernet OAM functionality, the interface is automatically and implicitly added to the new multiservice interface family. Even though this assignment does not appear in the configuration, you can view the assignment of the interface into the multiservice family in the Proto field of the output from the show interfaces terse command. No new statements are required to enable this implicit behavior. [Network Interfaces, Interfaces Command Reference]
• Improved statistics for Ethernet interfaces—The output of the show interfaces extensive command for 10-Gigabit Ethernet interfaces with XENPAK SFPs now provides more accurate statistics for the byte and packet counts in the Traffic statistics and MAC statistics fields. [Interfaces Command Reference]
• Additional information available about OAM CFM for Ethernet interfaces—Enables you to obtain separate link and protocol status about Ethernet interfaces that have OAM CFM enabled. The information now appears in the output of the show oam protocol ethernet connection-fault-management interfaces command. [Interfaces Command Reference]
• Increased number of screened incoming ISDN phone numbers—You can now specify up to 30 phone numbers in the list of incoming ISDN callers that are accepted or rejected. Include an incoming-called-number statement for each one at the [edit interfaces br-pim/0/port isdn-options] hierarchy level. In JUNOS Release 8.2 and earlier, the limit was eight phone numbers. [Network Interfaces]
• Required FPGA version for ATM2 PIC (M120 and M320 routers)—On M120 and M320 routers, the JUNOS software generates a chassis alarm and SNMP trap if the revision number for the ATM2 PIC FPGA is less than 8B44(4). [Network Management]
• CLI change for a system process—The CLI name for the Ethernet OAM link fault management process has changed from lfm to ethernet-link-fault-management. As a result, the operational command to restart this process is now restart ethernet-link-fault-management. To disable the Ethernet OAM link fault management process, include the disable statement at the [edit system processes ethernet-link-fault-management] hierarchy level. [System Basics, System Basics and Services Command Reference]
• SFP information included in operational command output (J-series Services Routers)—For 6-port Gigabit Ethernet uPIMs with small form-factor pluggable transceivers (SFPs) on J-series Services Routers, the show chassis hardware command output now displays information about the SFPs. [J-series Basic Configuration, Interfaces Command Reference]
• Behavior change for PAP (J-series Services Routers)—If you configure passive mode for Password Authentication Protocol (PAP) on an ATM interface configured for Point-to-Point Protocol over Ethernet (PPPoE) over ATM, the router no longer indicates that it can be the Link Control Protocol (LCP) authenticator during LCP negotiations. Previously, the router did indicate it could be the LCP authenticator, even in passive mode. [J-series Basic Configuration, Network Interfaces]
• Corrected output for Gigabit Ethernet IQ2 interfaces—For Gigabit Ethernet IQ2 interfaces, the Queued: Packets field in the output of the show interfaces queue and show interfaces extensive commands now displays a value instead of the words Not Available. Because the PIC itself cannot provide a packet count, the JUNOS software calculates the value by assuming that one frame buffer represents one packet. If the queued packets are very large or very small, the calculation might differ from the actual value, but only when traffic is transiting the router. When traffic is stopped, the value equals the actual count. [Network Interfaces]
• Routing Engine mastership option for routing matrixes—Enables you to combine the all-chassis option with each of the acquire, release, and switch options to the request chassis routing-engine master command when issued on the TX Matrix platform in a routing matrix. Previously, you could combine the all-chassis option with the switch option only. [System Basics and Services Command Reference]
• Update for chassis operational mode command output (MX-series routers)—In the output of the show chassis fpc detail command, the Total DDR DRAM and Total RLDRAM fields replace the Total SDRAM and Total SRAM fields, respectively. [System Basics and Services Command Reference]
• Valid link mode for J-series 4-port Fast Ethernet ePIM—For this PIM, the only valid value for the link-mode statement at the [edit interfaces fe-fpc/pic/port] hierarchy level is full-duplex. If you specify half-duplex (or full-duplex mode is not autonegotiated), the interface process writes the following message to the system log: "Half-duplex mode not supported on this PIC, forcing Full-duplex mode."

Services Applications

• Update to the show services l2tp session extensive command—New output fields have been added to display the policer bandwidth, policer burst size, and firewall filter name. [System Basics and Services Command Reference]
• Changed port range for RPM probes—The valid range for the destination-port statement at the [edit services rpm probe probe-name test test-name] hierarchy level has changed from 7, 49152 through 65535 to 7, 49160 through 65535. [Services Interfaces]
• Additional information about RPM probes—Enables you to obtain test results for single-direction probes; include the one-way-hardware-timestamp statement at the [edit services rpm probe probe-name test test-name] hierarchy level. Also, the output of the show services rpm command now includes additional fields that report ingress and egress jitter data. [Services Interfaces]

• Enhancements to clear services ipsec-vpn commands—Four new options have been added to the clear services ipsec-vpn ipsec security associations command. They enable you to clear IPSec security associations (SAs) on the Adaptive Services PIC based on specific characteristics:

  • ASs for a specific remote gateway: clear services ipsec-vpn ipsec security associations remote-gateway remote-gateway-address
  • ASs for a specific tunnel: clear services ipsec-vpn ipsec security associations tunnel-index tunnel-index-number
  • ASs for a specific remote gateway in a specific service set: clear services ipsec-vpn ipsec security associations service-set-name remote-gateway remote-gateway-address
  • ASs for a specific tunnel in a specific service set: clear services ipsec-vpn ipsec security associations service-set-name tunnel-index tunnel-index-number
  [System Basics and Services Command Reference]
• Clearing IKE SAs when AS PIC goes offline—Enables you to have the IKE SAs associated with tunnels cleared automatically when an AS PIC goes offline or is restarted. Include the clear-ike-sas-on-pic-restart statement at the [edit services ipsec-vpn] hierarchy level. [Services Interfaces]
• New fields for L2TP operational mode command output—The new Session encapsulation overhead and Session cell overhead fields have been added to the output of the show services l2tp session extensive command. The new fields display overhead information for cells and encapsulation used within an L2TP session. [System Basics and Services Command Reference]
• Services PICs do not reboot in MAC flow-control situation—Adaptive Services and MultiServices PICs in layer-2 mode (running Layer 2 services) are no longer rebooted when a MAC flow-control situation is detected. [Services Interfaces]

Layer 2 Ethernet Services

• Treatment of MAC address accounting statistics—On MX-series routers running JUNOS Release 8.4 and later, the treatment of MAC address accounting statistics is different from MX-series routers running JUNOS Release 8.3 and earlier, and from M-series and T-series routing platforms running any release of the JUNOS software (including JUNOS Release 8.4 and later). The new treatment on MX-series routers running JUNOS Release 8.4 and later is as follows:

  • By default, MAC statistics collection is disabled (for the other combinations of routing platform and JUNOS software, statistics collection is enabled by default). To enable MAC statistics, include the mac-statistics statement at the appropriate hierarchy level:

    • [edit protocols l2-learning] for the entire router
    • [edit routing-instances routing-instance-name protocols vpls] for a VPLS domain
    • [edit routing-instances routing-instance-name bridge-domains domain-name bridge-options] for a bridge domain in a virtual switch
  • When the router moves to a different location in the network, both source and destination statistics are reset to zero (for the other combinations of routing platform and JUNOS software, only source statistics are reset). In other words, in the output from the show route forwarding-table family vpls destination mac-address extensive command, the Packet count and Byte count fields are cleared in both the Route used as destination and Route used as source sections.
  • When a destination MAC address entry expires, statistics for it are reset to zero (for the other combinations of routing platform and JUNOS software, the statistics are retained). In output from the show route forwarding-table family vpls destination mac-address extensive command, the Packet count and Byte count fields are cleared in the Route used as destination section.
  [Routing, Routing Protocols and Policies Command Reference]
• On MX-series routers running JUNOS Release 8.4 and later, you can set the expiration time of entries in the MAC table only for the entire router, not for specific VPLS routing instances. To set the expiration for the entire router, include the mac-table-aging-time seconds statement at the [edit protocols l2-learning] hierarchy level. Do not include the mac-table-aging-time statement at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level on MX-series routers running JUNOS Release 8.4 and later. [Routing]

General Routing and Routing Protocols

• New tracing operation—Enables you to trace condition-manager events. Include the condition-manager statement at the [edit routing-options traceoptions flag] hierarchy level. [Routing]
• New reconnection time for LDP graceful restart—The default reconnection time for LDP graceful restart is now 60 seconds (instead of 20 seconds) when the neighbor is another Juniper Networks routing platform. For neighboring routers from another vendors, the maximum reconnection time is 120 seconds, even if the neighbor advertises a time greater than that. [High Availability]

MPLS Applications

• Multiple interfaces to receive point-to-multipoint LSP traffic—Enables you to specify multiple outbound interfaces as the target for point-to-multipoint LSPs included in a circuit cross-connect (CCC) connection. To specify multiple interfaces to receive point-to-multipoint LSP traffic, include the output-interface statement at the [edit protocols connections p2mp-receive-switch switch-name] hierarchy level. [MPLS Applications]
• RSVP PathErr message generated for object with unknown C-type—If an RSVP Path message contains an object with a known class but an unknown C-type, a PathErr message is now generated and sent to the previous hop in the RSVP path. Previously, the PathErr message was not sent. No new configuration statements or commands are required. [MPLS Applications]
• LDP FEC filtering for Layer 2 sessions—Enables the router to send and receive forwarding equivalence classes (FECs) for Layer 2 circuits or LDP-based VPLS only. This feature is useful if all LDP neighbors associated with an LDP session are using Layer 2 prefixes and you want the router to filter out Layer 3 prefixes. To advertise and receive FECs for a Layer 2 LDP session only, include the l2-smart-policy statement at the [edit protocols ldp] hierarchy level. If you configure an explicit export or import policy, the l2-smart-policy statement is disabled. [MPLS Applications, VPNs]
• Simplified behavior for LDP OAM periodic traceroute—Previously, it was necessary to configure at least one option for the periodic-traceroute statement at the [edit protocols ldp oam fec fec-number] hierarchy level to enable a periodic traceroute of a Label Distribution Protocol (LDP) forwarding equivalence class (FEC). Now you only need to include the periodic-traceroute statement in the configuration to enable the periodic traceroute. [MPLS Applications]
• Constraint removal for LDP OAM periodic traceroute—Previously, Bidirectional Forwarding Detection (BFD) was required to enable periodic traceroute within a Label Distribution Protocol (LDP) Operation, Administration, and Maintenance (OAM) configuration. These configurations are now separate and you do not need to configure LDP BFD to enable a periodic traceroute. You can also disable BFD liveness detection for a specific LDP forwarding equivalence class (FEC). To disable BFD on an FEC, include the no-bfd-liveness-detection statement at the [edit protocols ldp oam fec fec-number] hierarchy level. [MPLS Applications]
• Only the ingress and egress routers generate traps when an LSP flaps—When an LSP goes down and comes back up, only the ingress and egress routers for the LSP generate the SNMP traps mplsTunnelDown and mplsTunnelUp. Previously, all routers associated with an LSP, including transit routers, generated the traps in this circumstance. [MPLS Applications]

VPNs

• Change for VPLS support in logical routers—You can now configure VPLS routing instances for multiple logical routers on a single physical router. Previously, you could only configure VPLS in the first logical router. [VPNs, Feature Guide]
• VPLS egress forwarding table filters are deprecated—The output output-filter-name statement is deprecated at the [edit forwarding-options family vpls filter] hierarchy level. You can continue to configure ingress forwarding table filters by including the input input-filter-name statement at the [edit forwarding-options family vpls filter] hierarchy level. [VPNs, Policy Framework]
• Customer multicast route advertisement—When advertising BGP multicast VPN intra-AS customer multicast (c-multicast) routes, route reflectors now set the originator identifier to self. Also, the route preference has been changed to prefer the active IBGP multicast VPN c-multicast route over the inactive route.

Class of Service

• TCM statistics added to the CoS MIB (PICs installed in Enhanced II FPCs)—Statistics for tricolor marking (TCM), such as medium-high and medium-low loss priorities that appear in the output of the show interfaces command, have been added to the Juniper Networks enterprise-specific CoS MIB. [Network Management]
• Extended platform support for TCM (M120 and MX-series routers)—The M120 and MX-series routers now support TCM. [Class of Service]
• Change to JUNOS XML representation of CoS interfaces in JUNOS Release 8.5—In JUNOS Release 8.5, the JUNOS XML representation of interfaces at the [edit class-of-service interfaces] hierarchy level will change. We are announcing this change now to give you the maximum time possible to change JUNOScript and NETCONF scripts that configure or retrieve information about interfaces at this level. As an example, in JUNOS Release 8.4 and earlier, the following JUNOS XML and X-Path expressions represent two interfaces, fe-0/0/0 and ge-0/0/0:

  <configuration> <class-of-service> <interfaces> <name>fe-0/0/0</name> <!- - tag elements for other statements - -> </interfaces> <interfaces> <name>ge-0/0/0</name> <!- - tag elements for other statements - -> </interfaces> </class-of-service> </configuration> /configuration/class-of-service/interfaces[name='fe-0/0/0']/* /configuration/class-of-service/interfaces[name='ge-0/0/0']/*

  The new JUNOS XML and X-Path expressions for JUNOS Release 8.5 and later are as follows:

  <configuration> <class-of-service> <interfaces> <interface> <name>fe-0/0/0</name> <!- - tag elements for other statements - -> </interface> <interface> <name>ge-0/0/0</name> <!- - tag elements for other statements - -> </interface> </interfaces> </class-of-service> </configuration> /configuration/class-of-service/interfaces/interface[name='fe-0/0/0']/* /configuration/class-of-service/interfaces/interface[name='ge-0/0/0']/*

  The CLI syntax is not changing for CoS interfaces. [JUNOS XML API Configuration Reference]

• Minimum shaping rate (MX-series routers)—If you include the shaping-rate statement at the [edit class-of-service interfaces interface-name] hierarchy level on an MX-series router, the shaping rate value for the physical interface must now be a minimum of 160 Kbps. [Class of Service]

Forwarding and Sampling

• ARP entry required for IPv4 port mirroring—For IPv4 port mirroring to reach a next-hop destination, you must manually include a static ARP entry in the router configuration. [Services Interfaces]

JUNOScope

• Additional information required during JUNOScope installation—During JUNOScope installation, users are prompted to provide the default IP address of the JUNOScope server, so that software images can be downloaded from the JUNOScope server to a device even if Domain Name System (DNS) or static host mappings are not configured on the device. [JUNOScope]

JUNOS XML API and Scripting

• JUNOS XML <product-model> tag—The XML output of the show version command has changed. For all platforms, the XML output now shows an additional <product-model> tag, reflecting the underlying hardware. The <product-name> tag is still included in the output and now specifies the product name. Additionally, for FIPS versions of the JUNOS software, the output now contains the <fips> tag. [JUNOS XML API Operational Reference]
• TCP port for NETCONF over SSH—The dedicated Transmission Control Protocol (TCP) port for SSH access to the NETCONF server is 830. In earlier releases of the JUNOS software, the value was 32000. [NETCONF API]
• JUNOScript <force-synchronize/> tag for synchronized commit operations (M-series and T-series routing platforms with dual Routing Engines)—Enables a JUNOScript client application to perform a synchronized commit operation even when there are open configuration sessions or uncommitted changes on the second Routing Engine. The operation invoked by the standard <synchronize/> tag fails if either condition holds. To force the synchronized commit operation, enclose the new <force-synchronize/> tag in <rpc> and <commit-configuration> tag elements, instead of the <synchronize/> tag. Open configuration sessions are terminated, uncommitted changes are discarded on the second Routing Engine, the configuration is copied from the first Routing Engine to the second, and the configuration is committed on both Routing Engines. [JUNOScript API]