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-2004-12-002. Go to http://www.juniper.net/customers/support and under the Research A Problem section, click Technical Bulletins. On the JTAC Technical Bulletins web page, enter PSN-2004-12-002 in the Search field, select the CS Technical Bulletin ID radio button, and click Search.

Software Installation

• Compact Flash requirement increased (M-series, MX-series, and T-series routing platforms)—The compact flash disk memory requirement for JUNOS software Release 9.0 is 1 GB. For M7i and M10i routing platforms with only 256 MB memory, see the Customer Support Center JTAC Technical Bulletin PSN-2007-10-001 https://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2007-10-001&actionBtn=Search. [Installation and Upgrade]

Platform and Infrastructure

• Whenever you configure allow-fragmentation on a GRE tunnel, you must also include either the tunnel key or the clear-dont-fragment-bit statement. This configuration enables the router to send affected packets to the PIC so that the correct IP header can be placed in the fragments. Otherwise, on the reassembly side some packets might be lost when fragments arrive in the PIC out of sequence at high speeds. [Services Interfaces]
• Due to changes in the JUNOS TCP/IP networking stack, the output of the show system connections extensive command may be different from JUNOS 8.4 and earlier. [System Basics]
• Starting the key management process (kmd)—The key management process (kmd) starts only when IPSec is configured on the router. Previously, this process started by default. [System Basics]
• New logical-router option for the clear arp command—Starting with JUNOS 8.5 the new command argument, logical-router, was added to the clear arp command. This argument is only available in the main router context. [System Basics]
• ISO option added to the show pfe route command—Starting with JUNOS 9.0, for J-series only, the ISO option was added to the show pfe route command. Use the ISO option to display PFE ISO routes. [System Basics]

User Interface and Configuration

• Showing core files on all JUNOS routing platforms—The show system core-dumps command is no longer hidden. You can use this command to show system core files created when the router fails. [System Basics]
• New show security screens command—Enables users to view screen object configurations in CLI mode. This command displays each screen’s inherited, configured, or default parameters. It optionally takes screen-name and display values for individual screens. [System Basics and Services Command Reference]
• New request system scripts event-scripts reload command—Simplifies the process of activating manual changes to event policies within active event-scripts. After changing the event policies within the event scripts, run the request system scripts event-scripts reload command to activate the event policies change. Configuration and Diagnostic Automation]
• Enhanced show spanning-tree bridge command output—The output of the show spanning-tree bridge command now displays the number of topology changes and time since last topology change for each Multiple Spanning Tree Instance (MSTI). [Routing Protocols and Policies Command Reference]
• Encrypted passwords—In JUNOS 9.0 and later, you can no longer specify a null value for a user's encrypted password. In other words, you cannot specify a pair of quotation marks with nothing between them as the value of the encrypted-password statement at the following hierarchy levels:
  • [edit login user name authentication]
  • [edit system root-authentication]
  • [edit system diag-port-authentication]
  • [edit system pic-console-authenication]
• Starting in JUNOS 9.0, the output of the show system license command now shows complete license names. [System Basics]

Interfaces and Chassis

• Starting with Release 8.4 in MX-960 routers, the under-voltage parameters for PEM status have been modified to improve recognition and generation of alarm conditions. The CLI command show chassis environment can be used to display the PEM environment alarm status. [System Basics and Services Configuration]
• The output of the show oam protocol ethernet connection-fault-management interfaces command has been enhanced to show separate link and protocol status. [Interfaces Command Reference]
• Show VRRP commands available in logical router context—Output for the following commands are available in a logical router context: show vrrp, show vrrp brief, show vrrp summary, show vrrp detail, show vrrp extensive, show vrrp profile statistics, show vrrp interface if-name, show vrrp track, show vrrp track detail, and show vrrp track summary. [High Availability]
• IPv4 source routing support disabled by default (M-series, MX-series, and T-series platforms)—IPv4 source routing is now disabled by default. To enable source routing on IPv4, include the ip statement at the [edit routing-options source-routing] hierarchy level. We recommend that you do not enable IPv4 source routing. [Routing Protocols]
• 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." [Network Interfaces]
• On Ethernet PICs, you can no longer simultaneously configure source filters on physical interfaces and on untagged logical interfaces. [Policy Framework]
• The CLI help description for the source-address-filter statement has changed from "Name of source address filter" to "Remote MAC address." [Network Interfaces]
• New packet reassembly functionality on GRE tunnels (AS PICs only)—Enables reassembly of fragmented tunnel packets on generic routing encapsulation (GRE) tunnel interfaces. To activate this capability, include the reassemble-packets statement at the [edit interfaces gre-fpc/pic/port unit logical-unit-number] hierarchy level. [Services Interfaces]
• Support for advertisement interval for VRRP IPv6 address —Include the inet6-advertise-interval milliseconds statement at the [edit interfaces interface-name unit number family inet6 address destination-prefix vrrp-inet6-group group-number] hierarchy level. The range that you can configure the advertisement interval is from 100 through 40,950 milliseconds. You can continue to use the advertise-interval seconds statement to configure the advertisement interval for VRRP IPv4 addresses. [High Availability]
• The output for the show aps operational mode command has been enhanced to include the new admin down value in the Interface State field. This value indicates that the interface has been administratively disabled using the disable statement at the [edit interfaces interface-name] hierarchy level. [Interfaces Command Reference]
• Statistics—Starting in JUNOS 8.4 on MX-series routers, statistics for an aged destination MAC entry are not retained. In addition, source and destination statistics are reset during a MAC move (in previous releases only source statistics were reset during a MAC move). [Routing Protocols]
• LSQ redundancy extended to M120 routers—Link Services Intelligent Queuing (LSQ) redundancy features, including warm standby and hot standby, are now supported on M120 routers as on other routing platforms. You can configure these features at the [edit interfaces rlsq number redundancy-options] hierarchy level. [Services Interfaces]
• Ignore Layer 3 incomplete errors—By default, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces count Layer 3 incomplete errors. The router can be configured to ignore the counting of Layer 3 incomplete errors on Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces. To ignore Layer 3 incomplete errors, include the ignore-l3-incompletes statement at the following hierarchy levels: [edit interfaces interface-name fastether-options] and [edit interfaces interface-name gigether-options]. [Network Interfaces Configuration Guide]
• Reset statistics on MX-series routers—Beginning with JUNOS Release 8.4 on MX-series routers, statistics for an aged destination MAC entry are not retained. In addition, source and destination statistics are reset during a MAC move (in previous releases only source statistics were reset during a MAC move). [Policy Framework]
• The ATM PIC driver might not always use the minimum port shaping rate (of all the ports on a multiport ATM DS3 or E3 PIC) selected for cell transmission shaping, in situations where the DS3 or E3 port parameters are not identical on all ports of a multiport ATM DS3 or E3 PIC. The PIC's shaping rate is always updated to conform to the last port setting updated by the PIC software driver, rather than use the minimum port (shaping) rate. There is no syslog message to inform the user of the shaping rate decision applied by the software driver. [Network Interfaces Configuration Guide]
• At the [edit routing-instances] hierarchy level, you can no longer configure a routing instance with the name "default.” [Routing Protocols]
• Link mode and speed on Ethernet Interfaces—Fast Ethernet interfaces can operate in either full-duplex or half-duplex mode. All other interfaces operate only in full-duplex mode. When you manually configure Fast Ethernet interfaces, link mode and speed must both be configured. If both these values are not configured, the router uses autonegotiation for the link and ignores the user-configured settings. For Gigabit Ethernet interfaces on the M-series and T-series routers running JUNOS software prior to Release 8.0, if link mode is configured and speed is not, no error message is displayed. [Network Interfaces]
• On Ethernet PICs, you can no longer simultaneously configure source filters on physical interfaces and on untagged logical interfaces. [Network Interfaces]
• For MX480 and MX240 routers, starting in JUNOS 8.5, the PEM entry of the CLI command show chassis hardware displays "PS 1.2-1.7kW; 100-240V AC in." [System Basics and Services Command Reference]
• Aggregated Ethernet interfaces on Ethernet Intelligent Queuing (IQ2) PICs in MX-series routing platforms now support the configuration of flexible VLAN tagging, native VLAN IDs, 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, and swap-swap. [Network Interfaces]

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]
• Starting in JUNOS Release 9.0 running on M-series routers; to improve threshold detection accuracy when using the request snmp spoof-trap command, the jnxDfcSoftMemThresholdExceeded trap value upper threshold is now 10 percent of the value set. [System Basics and Services Command Reference]
• New commands to display RADIUS information (M7i and M10i routers)—The show services radius servers command and the show services radius statistics command enable you to display server information and statistics for RADIUS servers configured on the router. [System Basics and Services Command Reference]
• The syntax of the show services stateful-firewall flows pgcp and show services stateful-firewall conversations pgcp commands has changed. The new syntax is: show services pgcp stateful-firewall flows and show services pgcp stateful-firewall conversations. [System Basics and Services Command Reference]
• On J-series Services Routers, the JUNOS software now also supports the Cisco certificate authority (CA) for IPSec profiles to request digital certificates. The JUNOS software continues to support the Microsoft and Entrust CAs for J-series routers. You use the [edit security pki] hierarchy to configure IPSec. [System Basics]
• The output provided by the show services stateful-firewall flows operational mode command has been updated. It no longer displays ICMP port information, because the port information provided in previous releases was inaccurate. [System Basics and Services Command Reference]
• The M120 router now supports redundancy services PIC (rsp) interfaces. [Services Interfaces]
• Starting in JUNOS Release 9.0, the command show service l2tp tunnel/session/summary accuracy level is improved, now showing counters values correctly up to an accuracy of xxxxxx.x kilo/mega.

  Therefore:

  • If a counter value is greater than 5,000,000, then xxxxxx.xM format is shown.
  • If the counter value is greater than 5000, then xxxxxx.xK format is shown.
  • Otherwise the "Absolute" value is shown. [System Basics and Services Command Reference
• In JUNOS 9.2 and later, you must now include the following configuration to make the flow monitoring feature operable:

  [edit system]

  ntp {

  boot-server ntp.juniper.net;

  server 172.17.28.5;

  }

  processes {

  ntp enable;

  }

General Routing

• New clear spanning-tree protocol-migration command—To revert from the original IEEE 802.1D Spanning Tree Protocol back to the Rapid Spanning Tree Protocol after the force-version statement has been removed from the configuration, enter the clear spanning-tree protocol-migration command. [Routing Protocols and Policies Command Reference]
• New condition for making policy decisions based on route existence—Allows you to define a policy condition based on the existence of routes in specific tables and use it in BGP export policies. To implement this feature, include the condition condition-name statement at the [edit policy-options] hierarchy level with the following option: if-route-exists address in-table table-name. You could then include the defined condition in the from statement of a policy term. This condition is available on all Juniper Networks platforms. A related operational mode command, show policy conditions, displays all configured conditions as well as the routing tables with which the configuration manager interacts. [Policy Framework, Protocols Command Reference]

Routing Protocols

• Change in use of special characters for routing instance 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 Configuration Guide, Policy Framework Configuration Guide]

• The output of the operational mode command show isis overview now includes a field that displays the time that remains before the overload timer is set to expire. [Routing Protocols and Policies Command Reference]
• The output of the show bgp group command has been enhanced to display the time remaining for the timer to delay update of the multiple-exit-discriminator (MED) attribute for BGP peers or groups. [Routing Protocols and Policies Command Reference]
• New BFD traceoptions flag—A new pipe-detail flag is supported at the [edit protocols bfd traceoptions] hierarchy level. [Routing Protocols]
• RIPng support extended to routing instances—You can now configure routing instances for the Routing Information Protocol next generation (RIPng). Include the statements in the [edit protocols ripng] hierarchy at the [edit routing-instances routing-instance-name] hierarchy. [Routing Protocols]
• Support to disable BFD adaptation—You can now disable adaptation for the Bidirectional Forwarding Detection (BFD) Protocol for all protocols that support BFD, including static routes, IS-IS, OSPF, RIP, BGP, and PIM. To configure BFD sessions not to adapt to changing network conditions, include the no-adaptation statement with the bfd-liveness-detection statement. Note: We recommend that you not disable BFD adaptation unless it is preferable for BFD adaptation not to be enabled in your network. Disabling BFD adaptation might cause instability when network conditions change. [Routing Protocols]
• Beginning with JUNOS Release 8.5, OSPF no longer advertises a router identifier interface that is not configured to run OSPF as a stub network in its link-state advertisements. [Routing Protocols]
• Additional output for show ospf overview command—The output of the operational mode command show ospf overview now includes a field that displays the time that remains before the overload timer is set to expire. [Routing Protocols]
• RIPv2 support for third-party next hops—When exporting routes, RIPv2 now supports third-party next hops specified in policies, such as Virtual Router Redundancy Protocol (VRRP) groups. [Policy Framework]
• MX-series routers support the VLAN Spanning Tree Protocol (VSTP)—VSTP maintains a separate spanning-tree instance for each VLAN and is compatible with the Per-VLAN Spanning Tree Plus (PVST+) and Rapid-PVST+ protocols supported on Cisco Systems routers and switches. To configure VSTP, include the vstp statement at the [edit protocols] or [edit routing-instances routing-instance-name protocols] hierarchy level. To enable a VSTP instance for a specified VLAN, include the vlan statement at the [edit protocols vstp] or [edit routing-instances routing-instance-name protocols vstp] hierarchy level. [Routing Protocols Configuration Guide]
• The clear isis database operational mode command now supports the purge command. Use the purge command to discard link-state database entries for IS-IS. [Routing Protocols and Policies Command Reference]
• Some maximum values increased for OSPF—For OSPF, the maximum values that you can configure for the shortest-path-first delay and hold-down intervals have been increased. The maximum value that you can now configure for the delay milliseconds statement at the [edit protocols (ospf | ospf3) spf-options] hierarchy level is 8000. The default value remains 200. The maximum value that you can now configure for the holddown milliseconds statement at the [edit protocols (ospf | ospf3) spf-options] hierarchy level is 20,000. The default value remains 5000. [Routing Protocols]
• The output of the show route resolution summary command has been enhanced to include information about the reference count, contributing routing tables, and configured policies. [Routing Protocols and Policies Command Reference]

MPLS Applications

• Only the ingress and egress routers generate traps when an LSP flaps—When an LSP flaps, only the ingress and egress routers of that LSP generate SNMP traps (mplsTunnelUp and mplsTunnelDown). Previously, all the routers associated with an LSP—that is, the ingress, egress, and the transit routers—generated SNMP traps when the LSP flapped. [Network Management]
• Changes to ECMP support—Enhancements made to ECMP introduced in JUNOS Release 8.3 are not longer supported. [MPLS Applications book]
• Support for longer LSP names—The JUNOS software now allows you to configure LSP names that are up to 64 characters long. The mplsLspInfoList table replaces the mplsLspList table in the Juniper Networks Enterprise-Specific MPLS MIB (mib-jnx-mpls.txt), and extends the maximum length of LSP names from 32 characters to 64 characters. [Network Management]
• New option for show ldp neighbor—The show ldp neighbor command has a new option, neighbor-address. This option allows you to display LDP neighbor information about a specific LDP neighbor using the LDP neighbor IP address. [Routing Protocols Command Reference]
• mplsTunnelReoptimized trap—The mplsTunnelReoptimized trap is generated every time the optimization-timer expires; that is, when the optimization-timer exceeds the value set for the optimize-timer statement at the [edit protocols mpls label-switched-path path-name] hierarchy level. [Network Management]
• BFD on an MPLS LSP—When BFD is configured on an MPLS LSP and the LSP is currently using the secondary path, the revertive timer will switch back to the primary path only after the BFD session on the primary path is up. [MPLS Applications]
• New message in the LSP history log—A new log message was added to the output for the show mpls lsp extensive command as follows: Requested bandwidth unavailable: re-optimized path. The message is generated when an LSP path that is re-optimized fails due to bandwidth allocation. [MPLS Log Reference]

VPNs

• 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.
• Additional BGP command—The JUNOS software now includes a clear bgp table table-name command. Use this operational mode command to request that BGP refresh routes for all routing tables or for a specific table. You can also perform this operation on all logical routers or a specific logical router. [Routing Protocols and Policies Command Reference]
• Extended community types in BGP—For BGP communities, when you configure the extended community type using the community-ids statement at the [edit policy-options community name members] hierarchy level, you must use an AS number for the src-as type and an IP address for the rt-import type. [Policy Framework]
• Enhanced show route table command—The output for the show route table routing-table-name operational mode command has been enhanced to display the sender and group address for the PMSI: PIM-SM field, which displays information about the PIM sparse mode provider tunnel. [Routing Protocols and Policies Command Reference]

Class of Service

• On M-series and T-series, when you use wildcards to configure logical interfaces, the configuration includes a default scheduler map even though per-logical-interface queuing is not configured and the interface does not reside on a PIC that supports logical interface queuing. [Class of Service]

Forwarding and Sampling

• Restriction to filter group number—The filter group number option configured under the [edit interfaces interface-name unit logical-unit-number family family filter] hierarchy is now restricted to values from 0 to 255. Verify that existing configurations meet this restriction before performing an upgrade to JUNOS Release 8.5. [Network Interfaces Configuration Guide]

Routing Policy and Firewall Filters

• Change in use of special characters for routing instance 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 Configuration Guide, Policy Framework Configuration Guide]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.