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 specific information about PIC combination rules, consult Technical Bulletin PSN-2007-01-023. Go to http://www.juniper.net/customers/support and click Technical Bulletins. On the JTAC Technical Bulletins web page, enter PSN-2007-01-023 in the Search field, select the CS Technical Bulletin ID radio button, and click Search.

Platform and Infrastructure

• Time zone database updates—For all JUNOS routers, the time zone database information can be updated independently of the JUNOS operating system. This feature simplifies time zone management in JUNOS systems by allowing for future time zone database adjustments independent of the JUNOS operating system. [System Basics]
• DHCP subscriber limitations—Configurations that contain more than 40,000 DHCP subscribers can experience failure during subscriber authentication that results in the loss of any previously-authenticated subscribers.
• Reduction in the minimum interval required between successive Routing Engine switchover events—With JUNOS software Release 9.1R2 and later, the minimum interval required between successive Routing Engine switchover events is 4 minutes (240 seconds). In previous releases, the minimum interval required was 5 minutes (300 seconds).

User Interface and Configuration

• The dhcp-options statement at the [edit access profile radius attributes exclude] hierarchy level is not supported. [System Basics]
• Modified URL syntax for IPv6 host addresses—When specifying a URL in a JUNOS statement using an IPv6 host address, you must enclose the entire URL in quotation marks (" ") and enclose the IPv6 host address in brackets ([ ]). For example, "ftp://username<:password>@[host-address]<:port>/url-path" or "scp://username<:password>@[host-address]<:port>/url-path". This type of URL format appears in the system archival statement syntax. Not using the quotations and brackets in conjunction with using an IPv6 host address results in a failure when the transfer on commit is executed. [System Basics]
• New IPv6 system options—The following configuration statements are new to the [edit system internet-options] hierarchy level:
  • ipv6-duplicate-addr-detection-transmits—Controls the number of attempts for IPv6 duplicate address detection.
  • ipv6-reject-zero-hop-limit—Enables the dropping of IPv6 packets with a zero hop limit in their header.
  • no-ipv6-reject-zero-hop-limit—Disables the dropping of IPv6 packets with a zero hop limit in their header.

  [System Basics]

• New command to verify RADIUS server authentication parameters—A new command enables you to verify RADIUS server authentication parameters. The syntax is as follows:

  test access radius-server address user username password password secret secret

  <authentication-port port>

  <retry number>

  <source-address address>

  <timeout number>

  [System Basics Command Reference]

• Enhanced show command support for MX960 routers—The show chassis environment fpc command displays information about Tri-Rate DPCs (10/100/1000 MX DPCs) installed in the chassis. [System Basics Command Reference]
• Change in use of special characters for routing instance and firewall filter and policy names—You can no longer use special characters within the names of routing instances. A commit check and upgrade to JUNOS Release 9.0 fails if you include a special character within a routing instance name. The routing instance name can include letters, numbers, and hyphens. In addition, a routing instance name can now be up to 128 characters long. You configure a routing instance name at the [edit routing-instances routing-instance-name] hierarchy level. The commit check is enforced wherever a routing instance name is referenced in the JUNOS CLI.

  A commit check is also now enforced for firewall filter and policy statement names. The commit check fails if these names include special characters. You configure firewall filters at the [edit firewall filter filter-name] hierarchy level. You configure a policy statement at the [edit policy-options policy-statement policy-name] hierarchy level. [Routing Protocols, Policy Framework]

Interfaces and Chassis

• Aggregated Ethernet interfaces on Ethernet intelligent queuing (IQ2) PICs in MX-series routing platforms support the configuration of flexible-vlan-tagging, native-vlan-id, and rewrite operations on dual-tagged frames, which consist of the following configuration statements:
  • inner-tag-protocol-id
  • inner-vlan-id
  • pop-pop
  • pop-swap
  • push-push
  • swap-push
  • swap-swap

  [Network Interfaces]

• New show interfaces terse option—The show interfaces terse command includes a new routing-instance all option. When executing the show interfaces terse command using the routing-instance all option, interfaces for all routing instances are displayed. [Interfaces Command Reference]
• New range of values for interface hold time—The physical interface hold time can be configured from 0 to 4,294,967,295 milliseconds. To configure the hold time, include the hold-time statement at the [edit interfaces interface-name] hierarchy level. [Network Interfaces]
• The Corrected Errors count and Corrected Errors ratio for Forward Error Correction (FEC) counters can be displayed on 10-Gigabit Ethernet Xenpak interfaces that support FEC. To display the FEC counters, enter the show interfaces ge-fpc/pic/port extensive command. [Interfaces Command Reference]
• New command to display the globally-learned MAC address count for the router—A new command has been added to display the globally-learned MAC address count for the router. To display the globally-learned MAC address count, issue the show bridge mac-table global-count command. [Protocols Command Reference]
• Change in output from show interfaces diagnostics optics command—The show interfaces diagnostics optics command for optical interfaces no longer reports the decibel (dBm) value of the received signal if the received power is zero milliwatts (0.0000 mW). [Interfaces Command Reference]
• Ethernet interface ping and traceroute enhancements—You can optionally specify the Maintenance Association End Point (MEP) identifier in the ping ethernet and traceroute ethernet commands for Ethernet interfaces. [Interfaces Command Reference]

Services Applications

• By default, the JUNOS software allocates NAT ports sequentially. To configure random port allocation, include the random-allocation statement at the [edit services nat pool pool-name port (automatic | range)] hierarchy level. [Services Interfaces]
• Increase in number of service sets support for interfaces—The number of service sets that can be applied to an interface has been increased to a maximum of six service sets. The previous maximum was three service sets. [Services Interfaces]
• Neighbor discovery for IPv6 NAT pool of addresses—Starting with JUNOS 9.1, to enable multicast filters on Ethernet interfaces when IPv6 NAT is used for neighbor discovery, you must include the ipv6-multicast-interfaces all statement at the [edit services nat] hierarchy level. [Services Interfaces]

Layer 2 Ethernet Services

• New command to display globally-learned MAC address count—A new command displays the globally-learned MAC address count for the router. Issue the show bridge mac-table global-count command. [Protocols Command Reference]
• STP root protection enhancement—STP root protection ensures that the port on which root protection is enabled is the spanning-tree designated port. If the bridge receives superior STP Bridge Protocol Data Units (BPDUs) on a root protection-enabled port, root protection moves this port to a root-prevented STP state. This state is displayed as (Root-Prev) in the output of the show spanning-tree interface command and (Root Prevented) in the output of the show spanning-tree interface detail command. To configure root protection, include the no-root-port statement at the [edit protocols (mstp | rstp | vstp) interface interface-name] or [edit protocols vstp vlan vlan-id interface interface-name] hierarchy levels. [Protocols Command Reference, Routing Protocols ]

General Routing

• VRRP for IPv6 and restricting router advertisements—The master VRRP for an IPv6 router must respond to a Router Solicitation message with the virtual IP address of the router. However, when the interface interface-name statement is included at the [edit protocols router-advertisement] hierarchy level, the backup VRRP for an IPv6 router might send a response before the VRRP master responds. In this case, the default route of the client is not set to the master VRRP router's virtual IP address. To avoid this situation, include the virtual-router-only statement at the [edit protocols router-advertisement interface interface-name] hierarchy level. When this statement is included, router advertisements are sent only for VRRP IPv6 groups configured on the interface (if the groups are in the master state). You must include this statement on both the master and the backup router. [High Availability, Routing Protocols]
• Enhancement to the show vrrp command—The show vrrp command now includes the logical-router logical-router-name option. This feature enables you to specify the logical router for which you want to display Virtual Router Redundancy Protocol (VRRP) information. [Interfaces Command Reference]
• VRRP operational command change—When the VRRP virtual interface is down, the output of the show vrrp extensive and show vrrp detail commands now display N/A in the Master router: field. Previously, when you issued these commands, the Master router: field displayed the IP address of the last known master router. [Interfaces Command Reference]
• Nonstop active routing synchronization enhancement—Changes have been made to the Routing Engine synchronization process for nonstop active routing (NSR). When you include the commit synchronize statement at the [edit system] hierarchy level, the commit completes even if the secondary Routing Engine is down. When the secondary Routing Engine comes up, its configuration will automatically be synchronized. Previously, the commit failed in this scenario. [High Availability]
• Nonstop active routing and VPN—When nonstop active routing is enabled at the [edit routing-options] hierarchy, you cannot enable automatic route distinguishers for multicast VPN routing instances (automatic route distinguishers are enabled by configuring the route-distinguisher-id statement). [High Availability]

Routing Protocols

• BGP statement has been deprecated—The l2-vpn unicast statement at the [edit protocols bgp family] hierarchy level has been deprecated. [Routing Protocols]
• LDP graceful restart timer enhancements—Added new settings for Label Distribution Protocol (LDP) reconnect timers. To configure the reconnection time, include the reconnect-time or maximum-neighbor-reconnect-time statement at the [edit protocols ldp graceful-restart] hierarchy level. Also, the pre-existing maximum-recovery-time statement has been renamed as maximum-neighbor-recovery-time for consistency. The show ldp session detail operational command output now includes a field to display local maximum neighbor reconnect time. [High Availability, Protocols Command Reference]
• OSPF show command enhancement—The show (ospf | ospf3) neighbor command has been enhanced to display OSPF neighbors for all routing instances. To display OSPF neighbors for all routing instances, include the new all option. [Protocols Command Reference]

MPLS Applications

• Label withdrawal timer—The label withdrawal timer delays sending a label withdrawal request for a FEC to a neighbor. When an IGP link fails, the label associated with the LDP FEC traversing that link needs to be replaced and then readvertised. By default, LDP waits for 60 seconds before withdrawing labels to avoid resignaling LSPs multiple times while the IGP is reconverging. To specify the label withdrawal delay time in seconds, include the label-withdrawal-delay statement at the [edit protocols ldp] hierarchy level. [MPLS Applications]

Multicast

• Designated router election on P2P links—To comply with the latest PIM drafts, you should enable designated router (DR) election on all PIM interfaces, including point-to-point (P2P) interfaces. (DR election is enabled by default on all other interfaces.) To enable DR election on P2P interfaces, include the dr-election-on-p2p statement at the [edit protocols pim] hierarchy level. [Multicast]

VPNs

• VPLS route local preference—The JUNOS software no longer uses the local preference value configured for the BGP Layer 2 VPN (l2vpn) route address family with regard to VPLS routes. The local preference used for VPLS routes is now solely derived from the value configured using the site-preference statement configured at the [edit routing-instances routing-instance-name protocols vpls site site-name] hierarchy level. However, you can still change the preference value for VPLS routes exported to other routers by configuring an export policy. [VPNs]
• VPLS connection option—A new configuration statement enables you to specify when a VPLS connection is taken down depending on whether or not the interface for the VPLS routing instance is customer facing or Integrated Routing and Bridging (IRB). To enable this feature, include the connectivity-type (ce | irb) statement at either of the following hierarchy levels:
  • [edit logical-routers logical-router-name routing-instances routing-instance-name protocols vpls]
  • [edit routing-instances routing-instance-name protocols vpls]

  The default value is ce. [VPNs]

Class of Service

• When an Ethernet IQ2 PIC is installed on a routing platform capable of supporting 8 queues, the IQ2 PIC will have 8 queues enabled by default. [Class of Service]

Network Management

• SNMP version 1 and version 2 community clients (M-series, T-series, and MX-series platforms)—The routing-instances test-lr/test-ri configuration statement for this feature has been modified. To specify a routing instance when you add a client to an SNMP community, include the routing-instance routing-instance-name statement at the [edit snmp community community-name] hierarchy level. To specify a routing instance that is defined within a logical router, include the routing-instance routing-instance-name statement at the [edit snmp community community-name logical-router logical-router-name] hierarchy level.

  To specify a routing instance when you add a client to an SNMPv3 trap target, include the routing-instance routing-instance-name statement at the [edit snmp v3 target-address target-address] hierarchy level. To specify a logical router when you add a client in an SNMPv3 trap target, include the logical-router logical-router-name statement at the [edit snmp v3 target-address target-address]. To specify a routing instance of SNMP trap packets sent by the router, include the routing-instance routing-instance-name statement at the [edit snmp trap-options] hierarchy level. To specify a routing instance that is defined within a logical router, include the routing-instance routing-instance-name statement at the [edit snmp trap-options logical-router logical-router-name] hierarchy level. To specify a routing instance of an SNMP trap group, include the routing-instance routing-instance-name statement at the [edit snmp trap-group trap-group-name] hierarchy level. To specify a logical router for an SNMP trap group, include the logical-router logical-router-name statement at the [edit snmp trap-group trap-group-name] hierarchy level. [Network Management, Feature Guide]

JUNOS XML API and Scripting

• NETCONF support for the edit-config tag—Enables the edit-config tag to work with a text-formatted configuration file. This file can be referenced via a URL or it can be added inline within the edit-config tag. [NETCONF Guide]

System Logs

• Licensed feature name displayed—The system log entries for licensed features now display feature names instead of feature numbers. [System Logs]
• MPLS LSP bandwidth displayed—The system log entries for MPLS LSP now include information about bandwidth usage. [System Logs]