[ Contents] [ Prev] [ Next] [ Report an Error]

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 under the Research A Problem section, 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.

Software Installation

Upgrade limitation for logical routers—Routers running JUNOS Release 7.4 or earlier that have logical router configurations enabled might display the following error when an upgrade to Release 7.6 or later is installed:
```
Validating against /config/juniper.conf.gz Init daemon:
```
```
/var/etc/init.inc+:19: syntax error near 're-mode' 
```
```
Init daemon: /var/etc/init.inc+:25: syntax error near 're-mode' 
```
```
Init daemon: /var/etc/init.inc+:32: syntax error near 're-mode' 
```
```
mgd: error: configuration check-out failed Validation failed  
```
If this is the only error message that is reported, you have to perform the upgrade by issuing the command request system software add no-validate.

Platform and Infrastructure

FEB behavior change (M120 routers)—If a Forwarding Engine Board (FEB) is brought offline or removed, any interfaces on the Flexible PIC Concentrators connected to the FEB are deleted. If the FEB is subsequently brought back online, the interfaces are restored. [System Basics, System Basics and Services Command Reference]
Update for J-series Services Router operational commands—The show chassis hardware and show chassis environment commands now show the status of redundant power supply modules in the J6300 and J6350 Services Routers. In addition, the output of the show chassis alarms and show system alarms commands now include power module related alarms, if present. [System Basics and Services Command Reference]
Removal of an unsupported encapsulation type (J-series Services Routers)—Because flexible VLAN tagging is not supported on Fast Ethernet interfaces installed in J-series Services Routers, the flexible-vlan-tagging statement has been removed from the [edit interfaces fe-fpc/pic/port] hierarchy level in the CLI. [J-series Basic Configuration]
Improved packet handling (M-series routers)—The number of host-bound packets that an M-series router can receive has been increased. As a result, when the router receives a burst of host-bound traffic, fewer packets are dropped. No new configuration statements are required.

User Interface and Configuration

Modification to the rollback command—The rollback configuration mode command now loads the entire configuration specified and marks changed objects only (equivalent to a load update command). Previously, every object was marked as changed (equivalent to a load override command). No new configuration statements are required. [CLI]
Enhancement to the output of the show configuration command—The show configuration operational mode command now displays information regarding the commit process, including the last time changes to the configuration database were activated and the name of the user who committed the configuration. This information is also available in the response to the JUNOScript <get-configuration> and NETCONF <get-config> tag elements. [System Basics and Services Command Reference, JUNOScript, NETCONF]

Interfaces and Chassis

GRES configuration change—The enable and disable options at the [edit chassis redundancy graceful-switchover] hierarchy level have been removed. Although these options are still recognized in the current release of the JUNOS software, they will be removed in a future release. We recommend that you remove these options from your configurations.
New show chassis temperature-thresholds operational mode command—The M120 router and the MX960 Ethernet Services Router have per-FRU and per-slot temperature thresholds for setting the fan to high speed and for raising yellow and red alarms. The show chassis temperature-thresholds command displays these settings. [System Basics and Services Command Reference]
Revised bandwidth limitations (Gigabit Ethernet IQ and IQ2 PICs installed in M320 and T-series routing platforms)—If you configure VLAN tagging, the JUNOS software creates an internal logical interface that reserves 50 Kbps of bandwidth from Gigabit Ethernet IQ interfaces and 2 Mbps of bandwidth from Gigabit Ethernet IQ2 interfaces. As a result, the effective available bandwidth for these interface types is now 999.5 Mbps and 998 Mbps, respectively. [Network Interfaces]
Update for 10-Gigabit Ethernet IQ2 interfaces—When the router receives B3 and remote error indication path (REI-P) errors in incoming frames, the output of the show interfaces extensive command now increments the counters for these errors. Previously, the path B3 and REI-P counters were always listed as zero. [Interfaces Command Reference]
Change in default behavior for Gigabit Ethernet interfaces (J4350 and J6350 Services Routers)—By default, Gigabit Ethernet interfaces installed in J4350 and J6350 Services Routers autonegotiate the link settings. For JUNOS Release 8.1 and later, when you manually configure either the link mode or speed settings, the system ignores the configuration and generates a system log message. When you configure both the link mode and speed, the link negotiates the user-specified link mode and speed settings if autonegotiation is disabled. When autonegotiation is enabled and you specify the link mode and speed, the link autonegotiates with your manually configured settings. Previously, manual configuration of link mode and speed was ignored when autonegotiation was turned on. If you disable autonegotiation and do not manually configure the link mode and the speed, the link is negotiated at 1000 Mbps full duplex. [J-series Basic Configuration]
MTU change for Gigabit Ethernet interfaces (J4350 and J6350 Services Routers)—The maximum configurable MTU value has been changed to 9018 bytes. If you configure an MTU value greater than 9018, the system does not accept the configuration and generates an error message similar to the following: “Sep 5 15:55:48 aspen /kernel: ge-0/0/1: Illegal media change. MTU invalid: 9192. Max MTU supported on this PIC: 9018.” [J-series Basic Configuration]
New MTU error message for 4-port Fast Ethernet interfaces (J4350 and J6350 Services Routers)—The maximum configurable MTU value on a J4350 or J6350 Services Router is 1518 bytes. If you configure an MTU value greater than 1518, the system does not accept the configuration and generates an error message similar to the following: “Sep 5 15:55:48 aspen /kernel: fe-3/0/1: Illegal media change. MTU invalid: 9192. Max MTU supported on this PIC: 1518.” [J-series Basic Configuration]
PPP timer enhancement—Enables you to configure a restart timer for the Link Control Protocol (LCP) and Network Control Protocol (NCP) components of a PPP session. To configure a restart timer for LCP and NCP, include the lcp-restart-timer and ncp-restart-timer statements at the [edit interfaces interface-name ppp-options] hierarchy level. The range for the LCP timer is 20 through 10,000 milliseconds, the range for the NCP timer is 500 through 10,000 milliseconds, and the default value for both timers is 3 seconds. [Network Interfaces]
EPD threshold modification—The minimum early packet discard (EPD) threshold has been changed to 48 cells for ATM2 IQ interfaces on the following PICs:
- 1-port OC48
- 1-port and 2-port OC12
- 2-port OC3, DS3, and E3
- 4-port DS3 and E3
By default, for UBR the EPD threshold is approximately 1 percent of the available cell buffers. If shaping is enabled, the default EPD threshold is proportional to the shaping rate according to the following formula:

default epd-threshold = number of buffers * shaping rate / line rate

By default, the software estimates how much buffer space is needed for each PVC. However, you can configure the per-VC buffer space. In general, ATM PVCs need larger buffers for data traffic and smaller buffers for time-sensitive applications. Unnecessarily deep buffers might cause excessive delays on congested PVCs. Overly shallow buffers might cause premature random early detection (RED) or tail packet drops in bursty conditions.

If the default EPD threshold formula calculation result is less than 48 cells, the minimum value of 48 cells will be used as the EPD threshold.

To set the EPD threshold, include the epd-threshold statement at the following hierarchy levels:
- [edit interfaces interface-name unit logical-unit-number]
- [edit interfaces interface-name unit logical-unit-number address address family family multipoint-destination address]
- [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number]
- [edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number address address family family multipoint-destination address]
- [edit interfaces at-fpc/pic/port atm-options scheduler-maps map-name forwarding-class class-name]
  [Class of Service]
Changes to Daylight Saving Time—Beginning in 2007, DST (Daylight Saving Time) for the USA 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.
EDC checking—Endpoint Discriminator Class compatibility checking is now enabled on Multilink PPP (MLPPP) interfaces. Prior to JUNOS Release 8.0, when a routing platform received an unsupported Endpoint Discriminator Class message from an MLPPP session peer, it returned an acknowledgement (ACK) response. [Network Interfaces]
Change for SONET/SDH interfaces—Per-port framing configuration is now applicable for SONET/SDH interfaces in concatenated mode (default mode) only. When you configure a PIC to operate in nonconcatenated mode, the individual channels inherit framing configuration from the [edit chassis fpc number pic number framing (sonet | sdh)] hierarchy level. [Network Interfaces]
Updated operational mode command output for SFP-based interfaces—In the show chassis hardware command output, the “Description” field entry for small form-factor pluggable (SFP) transceivers with Part Number 740-015638 has been changed from “Unknown” to “Load SFP.” [System Basics and Services Command Reference]
Bandwidth settings for DS0, T1, and E1 interfaces—You can now configure the bandwidth statement on DS0, T1, and E1 interfaces once again. This configuration was blocked earlier as part of the fix for PR 70879. [Network Interfaces]
Auto-negotiation settings for Fast Ethernet interfaces—For Fast Ethernet interfaces configured with auto-negotiation, when the you take the PIC offline and then bring it back online, the link partner interface at the other end of the connection defaults to half-duplex mode. In previous releases, the link partner interface remained in full-duplex mode. [Network Interfaces]
New restriction for J4350 and J6350 Services Routers—MAC address filtering is not supported on Gigabit Ethernet and 4-port Fast Ethernet interfaces for the J4350 and J6350 Services Routers. In previous software releases, the unsupported source-filtering statement at the [edit interfaces interface-name fastether-options] hierarchy level was available for these routers. However, this statement is no longer available in the CLI. [Network Interfaces, J-series Basic Configuration]

Routing Protocols

Enhancements and changes for an IS-IS operational mode command—Adds the <isis-topology-id> XML tag to the output of the show route isis command and changes the name of the “Unicast” field to “IPV4 Unicast.” [Protocols Command Reference]
Enhancement for a forwarding table operational mode command—Adds the “Index” and “Reference” fields to the output of the show route forwarding-table command. [Protocols Command Reference]

Services Applications

New differential delays (MultiServices PICs)—The default yellow and red limits for differential delay are now 72 ms and 120 ms, respectively, and double the prior defaults for Adaptive Services PICs. You can see these new defaults in the output of the show interfaces extensive lsq-fpc/pic/port:channel command. No new statements are required. [Services Interfaces, System Basics and Services Command Reference]
Overlapping address pools—When you configure address pools for NAT and user access, these address pools can now overlap one another. Previously, the address pools needed to be unique for both NAT and user access. To configure overlapping address pools, include the address or address-range statement at the [edit access address-pool pool-name] and [edit services nat pool pool-name] hierarchy level. [Services Interfaces, System Basics]
Default settings change for a services PICs application (Adaptive Services and MultiServices PICs)—The predefined remote call procedure (RPC) application included in the junos-defaults configuration group has changed. The new range for the predefined rpc-program-number statement at the [edit groups junos-defaults applications application (junos-rpc-services-tcp | junos-rpc-services-udp)] hierarchy level is now 100001 to 400000. The previous range was 100000 to 400000. No configuration is necessary to inherit these new values. [Services Interfaces, System Basics]
New recovery functionality (AS PICs)—When an AS PIC experiences persistent back pressure as a result of high traffic volume for 3 seconds, the condition triggers an automatic core dump and reboot of the PIC to help clear the blockage. A system log message at level LOG_ERR is generated. This mechanism applies to both Layer 2 and Layer 3 service packages. [Services Interfaces]
Enhancements to a dynamic flow capture operational mode command—The following flow statistics information fields have been added to the output of the show services dynamic-flow-capture statistics command: “Active flow cache entries”, “Active flow cache usage percentage”, “Flow cache entries allocated”, “Number of control sources”, “Number of content destinations”, “Number of criteria”, “Maximum criteria matching one flow”, “Cached flows purged for memory”, and “Maximum filters matching one packet.” [System Basics and Services Command Reference]
Flow tap access restrictions—-View and configuration access to the [edit services flow-tap] hierarchy level is restricted to users with flow-tap or flow-tap-control permission only. In previous releases, this hierarchy was accessible to all CLI users. [Services Interfaces]
Revised behavior for digital certificate enrollment—When you issue the request security pki local-certificate enroll command with the validity-start-time and the validity-end-time options, you must now specify both options manually in order for the manual settings to take effect. If you do not specify both the start time and end time, the default value for the start time is the current time minus 900 seconds and the default value for the end time is one week after the start time. [System Basics]
MultiServices PIC update—When a Multiservices PIC experiences persistent back pressure (for 3 seconds), the routing platform now dumps core and the PIC reboots to help clear the condition. A system log message is generated at level LOG_ERR: “MAC stuck, trigger coredump via nmi”. [Services Interfaces, System Log Messages]
J-Web support for RPM hardware timestamping—The J-Web user interface now includes a setting for the hardware-timestamp statement. [J-Web]

MPLS Applications

Revised behavior for RSVP—RSVP now relies more on interior gateway protocol (IGP) hellos to mark neighbors as down. The change helps to improve the resiliency of the network during link state changes. The JUNOS software now does not preempt RSVP sessions immediately when RSVP hellos time out if the IGP hellos are still being sent and received by peers. However, when both the RSVP and the IGP hellos are discontinued, the RSVP sessions are terminated. As always, LSPs continue to be torn down when RSVP PATH and RESV messages time out. [MPLS Applications]
Revised RSVP session limit—In JUNOS Release 7.6 and later, the RSVP default maximum session limit has been increased from 50,000 to 100,000 sessions. [MPLS Applications]
Enhancement for an MPLS operational mode command—The timestamp in the output of the show mpls lsp extensive command now includes milliseconds. [Protocols Command Reference]
Enhanced load balancing functionality—The routing platform now supports indexed next-hop load balancing for IPv4 to MPLS next hops. To configure two-level hierarchical load balancing, include the indexed-next-hop statement at the [edit forwarding-options load-balance] hierarchy level and the label-1 and label-2 statements at the [edit forwarding-options hash-key family mpls] hierarchy level. [Routing, MPLS Applications]

VPNs

Modified VPLS behavior for logical routers—If you configure multiple logical routers, you can now configure VPLS in only one of the logical routers. The JUNOS software automatically enables the first configured logical router to support VPLS and prevents VPLS from working in subsequent logical routers. No new configuration statements are required. [VPNs, Feature Guide]

Class of Service

New class-of-service limitation—The JUNOS software now prevents you from configuring both the three-color-policer statement and the loss-priority statement at the [edit firewall family family-name filter filter-name term term-name then] hierarchy level at the same time. [Class of Service]
Increase in packet buffer size (Type 1 and Type 2 FPCs installed in M320 and T-series routing platforms)—Starting in JUNOS Release 8.1, the total buffer size is increased to 80,000 microseconds. The previous total packet buffer size was 50,000 microseconds. If your configuration from a previous JUNOS release includes the buffer-size percent statement at the [edit class-of-service schedulers scheduler-name] hierarchy level, the allocated amount of buffer when you upgrade the routing platform to JUNOS Release 8.1 is increased because the percentage is based on the total buffer size. Also, if you do not include the buffer-size statement in the configuration, the buffer sizes for queues 0 and 3 are increased because the default buffer sizes for queues 0 and 3 are 95 percent and 5 percent, respectively, of the total buffer size. [Class of Service]
Traffic control profiles modification (Link services intelligent queuing [LSQ] interfaces on Adaptive Services PICs)—For LSQ interfaces, a value of 0 is no longer supported for the percent statement at the [edit class-of-service traffic-control-profiles profile-name (guaranteed-rate | delay-buffer-rate | shaping-rate)] hierarchy level. The new range for the percent statement is 1 through 100. If you configure a value of 0, you now receive an error message. [Class of Service]
Class of service change (Gigabit Ethernet IQ interfaces)—If you do not configure 802.1p rewrite rules for a class-of-service (CoS) configuration on Gigabit Ethernet IQ interfaces, the forwarding class and loss priority are now rewritten to 0. This new behavior matches the default behavior of 802.1p rewrite rules on T-series routing platforms. [Class of Service]
Classifying IPv6 with MPLS explicit labels (M120 routers and MX960 Ethernet Services routers)—To classify IPv6 packets with MPLS explicit labels on MX960 Ethernet Services routers and M120 routers, you need to set the DSCP IPv6 classifier to the same interface. To configure this setting, include the dscp-ipv6 default statement at the [edit class-of-service interfaces interface-name unit logical-unit-number classifiers] hierarchy level. [Class of Service]
Revised processing for high-priority queues—For queues with negative credits, the routing platform now transmits traffic from the queue with the highest priority (3) first and then transmits traffic from queues with lower priorities when the high-priority queue is empty. [Class of Service]
Maximum shaping rate limitations removed (OC48 PICs)—Prior to JUNOS Release 7.4, the JUNOS software imposed a commit restriction of 50% as the maximum class-of-service (CoS) shaping rate. This restriction still applies to OC12 PICs, but has been removed for OC48 PICs. [Class of Service]
Support for eight queues on 1-port OC12 PIC—Enables you to configure up to eight queues on a 1-port OC12 PIC running in OC12c mode on an M320 or T640 routing platform. Include the max-queues-per-interface number-of-queues statement at the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level. The previous limit was four queues. [System Basics]

Routing Policy and Firewall Filters

Change for management interfaces (M-series and T-series routing platforms)—The fxp0 interface no longer supports load-sharing next hops. This restriction only affects fxp0 routes. [Policy]

Network Management

Standardized tracing operations for SNMP activity—Tracing operations for the following Simple Network Management Protocol (SNMP) processes have been standardized to include new options for configuring access to log files and for configuring a regular expression for lines to be logged:
- SNMP agent process (snmpd)—Responds to SNMP requests.
- SNMP remote operations process (rmopd)—Services SNMP requests for execution of ping and traceroute operations.
- Management Information Base II (MIB II) process (mib2d)—Services requests for information gathered and reported by SNMP.
To configure access to log files, include the file (world-readable | no-world-readable) statement at the [edit snmp traceoptions] hierarchy level. To refine trace operation output, include the match regex statement at the [edit snmp traceoptions file filename] hierarchy level and specify a regular expression to be matched. [Network Management]
Replacement of the LDP MIB—The branch used by the LDP MIB (ldpmib.mib) conflicts with RFC 3812. As a result, the ldpmib.mib file has been deprecated and replaced by the jnx-mpls-ldp.mib file. You can access the new MIB here: https://www.juniper.net/techpubs/software/junos/junos81/swconfig81-net-mgmt/html/mib-jnx-mpls-ldp.txt [Network Management]

System Log Messages

Change for system log messages—The JUNOS Release 8.1 software no longer generates system log messages whose tags have the prefix NASD. Many of the deprecated messages have been replaced by tags with the prefix PPPD. [System Log Messages]
Future changes for system log messages—Starting in JUNOS Release 8.2, the tag that uniquely identifies a system log message (for example, UI_AUTH_EVENT) will be 32 characters or less. Existing tag names will be shortened as necessary, requiring you to update tools that search in the system log for such tags. The JUNOS 8.2 Release Notes will list all the changed tags. [System Log Messages]

JUNOS API and Scripting

Changed mapping for a JUNOS XML request tag—The <get-feb-information> tag now corresponds to the show chassis feb detail command (it was previously show chassis feb). [JUNOS XML API Operational Reference]
Deprecated JUNOS XML request tag—The <get-ggsn-inspection-information> tag, which mapped to the show services ggsn inspection command, has been removed from the JUNOS software. [JUNOS XML API Operational Reference]
Renamed JUNOS event policy statement—Starting in JUNOS Release 8.1, you can upload a committed configuration file for a JUNOS event policy by including the committed statement at the [edit event-options policy policy-name then upload filename] hierarchy level. Previously, the committed statement was known as the running statement at the [edit event-options policy policy-name then upload filename] hierarchy level. Although the running statement is recognized in the current release, it will be removed in a future release. We recommend that you update your configurations and use the new committed statement. [Configuration and Diagnostic Automation]
XML enhancement for an LMP operational mode command—A new XML tag, <lm-control-channel-info>, has been added to the XML schema for the show link-management routing command. [XML API Operational Reference]

[ Contents] [ Prev] [ Next] [ Report an Error]