Changes in Default Behavior and Syntax in JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms

Class of Service

• The [edit firewall hierachical-policer] stanza documented in Chapter 21, “Configuring CoS on Enhanced IQ PICs,” of the CoS Configuration Guide is new to JUNOS Release 9.5. [Class of Service]

Layer 2 Ethernet Services

• Change in dhcp command (MX-series)—The output format of the show dhcp relay bindings detail command has changed from a tabular display to a line-by-line display. In addition, a new field, interface-name, was added to the output of this command. The interface-name field provides the MAC address of a client that is part of a DHCP relay/DHCP snooping configuration. [Command Reference: Protocols and Policies]

High Availability

• New priority hold time—With the priority-hold-time statement at the [edit protocols vrrp] hierarchy level, you can configure asymmetric behavior for VRRP routers. When a primary router loses a route, the standby router will become the primary router. After the formerly primary router (now the standby router) receives the route, it must wait for the configured time before declaring itself as the primary router again. [High Availability]

Multicast

• PIM restriction with nonforwarding instances—You cannot configure PIM within a nonforwarding instance. If you try to do so, the router displays a commit check error and does not complete the configuration commit process. [Multicast]

MPLS Applications

• Hello and hold time intervals for LDP targeted hellos—You can now configure hello and hold time intervals for LDP targeted hellos. To configure the targeted hello interval, include the hello-interval seconds statement at the [edit protocols ldp targeted-hello] hierarchy level. To configure the targeted hello hold time interval, include the hold-time seconds statement at the [edit protocols ldp targeted-hello] hierarchy level. For both statements, you can configure an interval of between 1 through 65,535 seconds. [MPLS Applications]
• IGP LDP synchronization holddown interval—You can now configure the time LDP waits before informing the IGP that the LDP neighbor and session for an interface are operational. For large networks with numerous FECs, it might be necessary to configure a longer value to allow enough time for the LDP label databases to be exchanged for the session. Specify the time in seconds by configuring the holddown-interval statement at the [edit ldp igp-synchronization] hierarchy level. You can configure a value of 10 through 60 seconds. The default value is 10 seconds. [MPLS]

Routing Protocols

• Bandwidth-based metric values for OSPF interfaces—Enables you to specify a set of bandwidth threshold values and associated metric values for an OSPF interface or for a topology on an OSPF interface. When the bandwidth of an interface changes, the JUNOS software automatically sets the interface metric to the value associated with the appropriate bandwidth threshold value. The JUNOS software uses the smallest configured bandwidth threshold value that is equal to or higher than the actual interface bandwidth to determine the metric value. If the interface bandwidth is higher than any of the configured bandwidth threshold values, the metric value configured for the interface is used instead of any of the bandwidth-based metric values configured. The ability to recalculate the metric for an interface when its bandwidth changes is especially useful for aggregate interfaces.

  To configure bandwidth-based metric values, include the bandwidth-based-metrics bandwidth value metric value statements at the [edit protocols (ospf| ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], or [edit protocols ospf area area-id interface interface-name topology topology-name] hierarchy levels. You must also configure the metric number statement at the [edit protocols (ospf | ospf3) area area-id interface interface-name], [edit protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name], or [edit protocols ospf area area-id interface interface-name topology topology-name] hierarchy levels.

  When configuring bandwidth-based metrics, you would typically configure multiple bandwidth and metric values as in the example below:

  [edit protocols]ospf { area 0.0.0.0 { interface ae0.0 { metric5;bandwidth-based metrics { bandwidth 2g metric 70; bandwidth 1g metric 80; bandwidth 3g metric 60; bandwidth 4g metric 50; bandwidth 5g metric 40; bandwidth 6g metric 30; bandwidth 7g metric 20;bandwidth 8g metric 10;}}}}

  In addition, the show ospf interface detail command has been enhanced so that the output for the Cost field displays the metric calculated when it is based on the bandwidth-based metric configuration. [Routing Protocols, Routing Protocols and Policies Command Reference]

• Enhancement to show (ospf | ospf3) database advertising-router and clear (ospf | ospf3) database advertising-router commands—You can now use the self option with the show (ospf | ospf3) database advertising-router command to display link-state advertisements (LSAs) generated by the router. You can also use the self option to discard entries for the LSAs advertised by the router. Execute the clear (ospf| ospf3) database advertising-router self purge command. Previously, you can to specify the router identifier of the router to display or discard self-generated LSAs. [Routing Protocols CR]
• Limit Bidirectional Forwarding Detection Protocol sessions for OSPF to neighbors in the full state—Enables you to configure the Bidirectional Forwarding Detection (BFD) Protocol to establish BFD sessions only for OSPF neighbors in the full state. By default, BFD sessions are established for all OSPF neighbors, Include the full-neighbors-only statement at the [edit protocols (ospf | ospf3) area area-id interface interface-name bfd-liveness-detection] or the [edit protocols ospf3 realm (ipv4-multicast | ipv4-unicast | ipv6-multicast) area area-id interface interface-name bfd-liveness-detection] hierarchy level. Logical systems and routing instances are also supported. [Routing Protocols]
• Enhancement to show bfd session extensive command—The output of the show bfd session extensive command displays the TTL value only when the minimum-receive-ttl number statement for the Bidirectional Forwarding Protocol (BFD) is configured. The minimum-receive-ttl statement is configured only for BFD sessions over multihop static routes. If this statement is not configured, the TTL value is no longer displayed. In addition, the Multi-hop field continues to be displayed in all cases. [Routing Protocols CR]

Routing Policy and Firewall Filters

• IPv6 support for the Ethernet type match condition for VPLS and Layer 2 bridging firewall filters—You can now specify ipv6 as a value for the ether-type statement at the [edit firewall family vpls filter filter-name term term-name from] or [edit firewall family bridge filter filter-name term term-name from] hierarchy level.
• Deprecated statements for VPLS and Layer 2 bridging firewall filters—For VPLS and Layer 2 bridging firewall filters, the vlan variable for the vlan-ether-type and ether-type match conditions has been deprecated. You can no longer configure vlan as a value at the [edit firewall family vpls filter filter-name term term-name from vlan-ether-type], [edit firewall family vpls filter filter-name term term-name from ether-type], [edit firewall family bridge filter filter-name term term-name from vlan-ether-type], and [edit firewall family bridge filter filter-name term term-name from ether-type] hierarchy levels.

  Note: Only the MX-series routers support the family bridge statement. [Policy, Layer 2]

• Enhancement to the show firewall command—The show firewall command now supports a terse option that enables you to display only the names of firewall filters. This option displays no other information about the firewall filters configured on your system. Use the show firewall terse command to verify that all the correct filters are installed. [Routing Protocols and Policies CR]

Platform and Infrastructure

• On the M7i Multiservice Edge Router and M10i Multiservice Edge Router platforms, the Enhanced Compact Forwarding Engine Board (CFEB-E) introduced in release 9.4 supports the 4-port Gigabit Ethernet Enhanced IQ2 (IQ2E) PIC with SFP, model number PE-4GE-TYPE1-SFP-IQ2E.
• Increase in limit to external paths accepted for BGP route target filtering—You can now specify for BGP to accept up to 256 external paths for route target filtering. Previously, the maximum number that you could configure was 16. The default value remains one. To specify the maximum number of external paths for BGP to accept for route target filtering, include the external-paths number statement at the [edit protocols bgp family route-target] hierarchy level. This statement is also supported for BGP groups and neighbors. [Routing Protocols]

Services

• The show services l2tp radius commands now displays when a server belongs to a profile that is the same for statistics.

Subscriber Access

• Enabling and disabling DHCP snooping support—You can now explicitly enable or disable DHCP snooping support on the router. If you disable DHCP snooping support, the router drops snooped DHCP discover and request messages.

  To enable DHCP snooping support, include the allow-snooped-clients statement at the [edit forwarding-options dhcp-relay overrides] hierarchy level. To disable DHCP snooping support, include the no-allow-snooped-clients statement at the [edit forwarding-options dhcp-relay overrides] hierarchy level. Both statements are also supported at the named group level and per-interface level.

  In JUNOS releases 10.0 and earlier, DHCP snooping is enabled by default. In releases 10.1 and later, DHCP snooping is disabled by default.

  [Subscriber Access]

User Interface and Configuration

• Option added to the file-copy operational request tag element—The source-address option has been added to the file-copy operational request tag element. This can be used by a JUNOScript client application to request information from a routing platform about the local address used in originating a connection for file copy. [JUNOS XML API Operational Reference]
• LSP ping interval—You can now specify the time interval for LSP ping messages when OAM is also configured. To specify the LSP ping interval time, include the lsp-ping-interval statement at the [edit protocols ldp oam] hierarchy level for LDP-signaled LSPs and at the [edit protocols mpls oam] hierarchy level for RSVP LSPs. [MPLS, System Basics Command Reference]
• The maximum number of aggregated Ethernet interfaces (LAG bundles) is 480 on all MX-series routers. [Network Interfaces, Layer 2 Configuration Guide]
• Configuration statements for disabling the reporting of ping record route and timestamp—Two new statements, no-ping-record-route and no-ping-time-stamp, have been introduced at the [edit system] hierarchy level. Include the no-ping-record-route statement in the configuration to prevent the Routing Engine from recording and displaying the route of the ping request packet in the response. Include the no-ping-time-stamp statement in the configuration to disable the Routing Engine from recording and displaying the timestamp in the ping response. By configuring these statements, you can prevent unauthorized users from discovering information about the PE router and its loopback address. [System Basics].
• Limitations to loopback configurations on 10–port Channelized E1/T1 IQE PICs—While configuring loopback on a 10-port Channelized E1/T1 IQE PIC, it is possible to simultaneously configure local/remote loopback at the CT1 partition and payload loopback at the T1 partition. Such a configuration will result in unpredictable PIC behavior and should not be used. [Network Interfaces]

Related Topics

• New Features in JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms
• Issues in JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms
• Errata and Changes in Documentation for JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms
• Upgrade and Downgrade Instructions for JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms