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 PICs typically do not use large amounts of memory. Gigabit Ethernet, ATM2, IQ serial PICs, and Adaptive Services PICs use more.

  Configuration rules might affect PICs installed on standard Enhanced FPCs used on the following routers: M5, M10, M20, M40, M40e, M160, and J20. They also apply to the M320 and T-series routing platforms when Type 1 Enhanced FPCs or Type 1 Enhanced II FPCs are used.

  No configuration rules affect PICS installed in J-series, M7i, or M10i routing platforms. No configuration rules affect PICS installed in Enhanced Plus FPCs on M-series and J20 platforms. No configuration rules affect Type 2 and Type 3 Enhanced FPCs installed in T-series or M320 platforms or the Enhanced Scaling FPC.

  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 more information about PIC combinations, please 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.

• Default MTU modification for E3 IQ and Channelized DS3 IQ PICs (M40e and M160 routers)—The default physical interface maximum transmission unit (MTU) on E3 IQ and Channelized DS3 IQ PICs installed in M40e and M160 routers has changed to 9192. [Network Interfaces]
• For M320 and T-series platforms that have Enhanced II FPCs and are configured to use tricolor marking, you can set the loss priority with a behavior aggregate (BA) classifier. Previously, on M320 and T-series platforms, you needed to set the loss priority using a multifield (MF) classifier.

Software Installation

• On J-series Services Routers, when you upgrade to a new software package from a remote location using the request system software add validate package-name command, the package is removed at the earliest opportunity in order to make room for the installation to be completed. (See also the “Software upgrade enhancements” feature description under “Software Installation” in the “Release 7.4 Features” section.)

Platform and Infrastructure

• Username—For the user statement at the [edit system login] hierarchy level, the username length has increased from 16 to 64 characters. [System Basics]
• IPv6 addresses—JUNOS software once again supports IPv6 addresses of the form ::x:y:z:0/127, which were supported in Release 7.3 and earlier. [System Basics]
• Graceful Routing Engine switchover—When 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]
• Enhanced debugging on dual Routing Engines—When replication errors or problems occur on a router that supports graceful restart, a live core dump is produced for both the master Routing Engine and the backup Routing Engine. The dump is written to the /var/crash/dump.live file. The core dump of both kernels can provide useful comparisons for debugging purposes. [System Basics]
• Enhanced support information—The output from the request support information command now includes the output from the show chassis hardware detail command instead of the show chassis hardware command. [Command Reference: System Basics and Services]
• The output from the show task memory command now correctly displays the amount of memory available to the routing protocol process (rpd). There may be a slight variation from previous output. [Command Reference: System Basics and Services]
• System log modifications—The following system log modifications have been made:
  • The syslog message UI_CLI_MMAP_INCREASE indicates that the system has run out of space for storing output data. This message used to be displayed only once for each command-line interface (CLI) session. It now appears each time the condition happens. This message used to be logged at the syslog error level. It is now logged at the warning level.
  • The JUNOS software now uses the name dfc for the local1 facility for messages directed to a remote system. The facility is for messages related to dynamic flow capture.
  • The logging level for SNMP community failure messages has been changed from LOG_NOTICE to LOG_DEBUG.
  • The string recorded in the system log for the LIBJNX_FILE_COPY_FAILED code is now "Failed to copy from source to destination."
  • The following code names have changed as indicated: PING_PROBE_FAILED replaces SNMP_TRAP_PING_PROBE_FAILED; PING_TEST_COMPLETED replaces SNMP_TRAP_PING_TEST_COMPLETED; and PING_TEST_FAILED replaces SNMP_TRAP_PING_TEST_FAILED.

  [System Log Reference]

• Beginning in 2007, Daylight Saving Time (DST) for the United States and Canada will begin at 2:00 a.m. on the second Sunday of March, and end at 2:00 a.m. on the first Sunday of November. The JUNOS software will automatically switch to the new DST schedule in 2007.

Interfaces and Chassis

• Channelized E1 PIC—Previously, when you configured a Channelized E1 PIC with the framing unframed option, you could also configure the timeslots statement, although it had no effect. Now, this combination is not permitted. [Network Interfaces]
• New options for serial interfaces (J-series Services Routers)—Enables you to specify what messages will be sent by a serial interface installed in a J-series Services Router when the channel is idle. To send a mark-flag (0x7F) message (the default value), include the flags statement at the [edit interfaces se-pim/0/port serial-options idle-cycle-flag] hierarchy level. To send an all-ones, mark-idle (0xFF) message, include the ones statement at the [edit interfaces se-pim/0/port serial-options idle-cycle-flag] hierarchy level. [Network Interfaces, J-series Configuration Guide]
• MLFR user-to-network interface (UNI) network-to-network interface (NNI) FRF.16 interoperability enhancement—To enable routers configured with APS to interoperate correctly with FRF.16, include the new send-lip-remove-link-for-link-reject statement at the [edit interfaces lsq-fpc/pic/port mlfr-uni-nni-bundle-options cisco-interoperability] hierarchy level. This option prompts the router to send a Link Integrity Protocol remove-link message when it receives an add-link rejection message. [Services Interfaces]
• Default adaptive services process behavior change for J-series Services Routers—For software releases earlier than JUNOS Release 7.4, the adaptive services process (spd) was selectively started on J-series Services Routers only when service sets were configured at the [edit services service-sets] hierarchy level. Starting with JUNOS Release 7.4, the process is also started when accounting is configured at the [edit forwarding-options accounting] hierarchy level. This change in default behavior enables the adaptive services process to show service sets created by an accounting configuration.
• On M40e routers, the maximum MTU size on 4xOC3 and 4xDS3 PICs has been increased from 4500 bytes to 9192 bytes.

Services Applications

• L2TP operational commands enhancement for M10i and M7i routers—The clear services l2tp session and clear services l2tp tunnel commands now support the all option. [Services Interfaces]

Routing Protocols

• RIPv2 hold-down and route expiry timeout changes—For Routing Information Protocol (RIP) version 2 (RIPv2), the default setting for the hold-down time (garbage collection) was previously 180 seconds. Starting in JUNOS Release 7.4R2, the default hold-down time is 120 seconds, in compliance with RFC 2453. To configure the hold-down time, include the holddown statement at the [edit protocols rip] hierarchy level. The default route expiry time (timeout) was previously 120 seconds. Starting in JUNOS Release 7.4R2, the default route expiry time is 180 seconds, in compliance with RFC 2453. [Routing Protocols]
• BGP description enhancement—The maximum length for BGP group and neighbor description strings protocols is 256 characters. Previously, the limit was 128 characters. To modify a description string, include the description statement at any of the following hierarchy levels:
  • [edit protocols bgp group group-name]
  • [edit routing-instances routing-instance-name protocols bgp group group-name]
  • [edit logical-routers logical-router-name protocols bgp group group-name]
  • [edit logical-routers logical-router-name routing-instances routing-instance-name protocols bgp group group-name]

  [Routing Protocols]

• IS-IS configuration enhancement—The JUNOS software no longer creates an IS-IS interface automatically whenever a logical interface has the family iso configured on it. If a logical interface has the family iso configured on it, but the interface is not specified at the [edit protocols isis] hierarchy level, and the interface all statement is not included at the [edit protocols isis] hierarchy level, an IS-IS interface is no longer automatically created. [Routing Protocols]

MPLS Applications

• Contact Juniper Networks Customer Support before deploying point-to-multipoint LSPs with logical routers. [MPLS]
• Enhancements for link protection and fast reroute—Provides additional support for MPLS LSP protection methods detailed in RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels. For link protection, the JUNOS software can now receive packets containing a fast reroute object with the 1-to-N bit set. For fast reroute, the JUNOS software can receive packets containing a fast reroute object with the 1-to-1 bit set. The changes enable the routing platform to interoperate with devices supporting the original implementation of fast reroute and link protection, as well as devices that conform to the RFC 4090 standard. No changes have been made to the fast reroute or link protection statement hierarchies. [MPLS Applications]
• MPLS LSP metric enhancement—The maximum value for the metric statement at the [edit protocols mpls lsp lsp-name] hierarchy level is now 16,777,215. Previously, the limit was 65,535. [MPLS Applications]

Multicast

• Local RPs in logical routers—There is now support for local RPs in logical routers for PIM sparse mode. All related warnings (such as “you cannot configure an RP on a logical router”) no longer appear. Local RP statements are now added to logical router statement listings. [Multicast]

Routing Policy and Firewall Filters

• Policy statements—When you configure several policy statements using the policy-statement configuration statement at the [edit policy-options] hierarchy level, and then you enter the show policy-options command, the output will display the policy statements in alphabetical order. Previously, the output from the show policy-options command displayed the policy statements in the order in which they were configured.