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 more information about PIC combinations during this beta period, please consult the technical bulletin located on the JUNOS beta page, here: http://www.juniper.net/beta/junos.

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

• 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.[JUNOS Software Installation and Upgrade Guide, JUNOS System Basics and Services Command Reference]

• The keyword options re0 and re1 used with the request system software add command, are available on all routing platforms with redundant Routing Engines. Previously, these options were only available on the TX Matrix routing platform. [JUNOS Software Installation and Upgrade Guide, JUNOS System Basics and Services Command Reference]

Platform and Infrastructure

• Improved packet handling (M-series routers)—The number of host-bound packets that an M-series router can receive has increased. As a result, when the router receives a burst of host-bound traffic, fewer packets are dropped. No new configuration statements are required.
• With JUNOS Release 8.2, there is approximately a 2% to 5% increase in memory usage on the Packet Forwarding Engine. The increase in memory usage causes a slight decrease in the maximum number of routes that are supported on the Packet Forwarding Engine.
• Disabling of video traffic load balancing is not supported if the incoming IP traffic with protocol 99/100 has IP options.

User Interface and Configuration

• For each unique client-identifier client-id, the DHCP server issues a unique lease and IP address from the pool. Previously, when the client provided an incorrect client-identifier client-id, the DHCP server did not issue a lease.
• The show configuration operational mode command now displays the last time the candidate configuration was changed. The command also displays the last time changes to the configuration were committed and the name of the user who committed the configuration. [JUNOS System Basics and Services Command Reference]

Interfaces and Chassis

• On IQ2 PICs without per-unit-scheduler configuration, the whole PIC supports 4071 VLANs and you can configure all of the VLANs on the same port. On IQ2 PICs with per-unit-scheduler configuration, the whole PIC supports 1024 minus (two times the number of ports), because each port is allocated two default schedulers. Prior to JUNOS Release 8.2, with per-unit-scheduler configuration, each port received an equal share of schedulers or shaped VLANs: [(1024 minus (two times the number of ports)/the number of ports]. For Release 8.2 and later, with per-unit-scheduler configuration, the scheduler-shaped VLAN per port allocation is user configurable.
• Endpoint Discriminator Class compatibility checking is now enabled on MLPPP interfaces. Prior to JUNOS Release 8.0, when a Juniper Networks router received an unsupported Endpoint Discriminator Class message from an MLPPP session peer, it returned an ACK response.
• You can now configure the bandwidth statement on DS, T1, and E1 interfaces. This configuration was blocked earlier as part of the fix for PR 70879.
• The output for the show chassis hardware operational mode command now includes a NEBS descriptor for Network Equipment Building System (NEBS)-compliant platforms.
• Per-port framing configuration is now applicable for SONET 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. [JUNOS Network Interfaces Configuration Guide]
• On M120 routers, the output from the show chassis fabric plane command now displays planes that are not present or are offline as OFFLINE instead of EMPTY. [JUNOS System Basics and Services Command Reference]
• On the M120 router, if a Forwarding Engine Board (FEB) is brought offline or removed, any interfaces on the Flexible PIC Concentrators (FPCs) connected to the FEB are deleted. If the FEB is subsequently brought back online, the interfaces are restored. In previous releases, the interfaces were not deleted when a FEB was brought offline or removed and they appeared to be available when they actually were not. [JUNOS System Basics Configuration Guide, JUNOS 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 routers. In addition, the output from the show chassis alarms and show system alarms commands now include power module related alarms if present. [JUNOS System Basics and Services Command Reference]
• With JUNOS Release 8.2, for Fast Ethernet interfaces configured with auto-negotation, when the PIC is taken offline and then brought 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.
• When an interface does not support the flexible-vlan-tagging statement, but this statement is configured on the interface, the system logs an error message, but maintains the interface state as up. However, the interface state is shown as down in the output from the show vrrp summary command. [JUNOS Interfaces Command Reference]
• 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. [JUNOS Interfaces Command Reference]
• On J-series Services Routers, the flow-control configuration statement is not supported on Fast Ethernet and Gigabit Ethernet interfaces. Previously, this unsupported option was available in the CLI. With JUNOS 8.2, this option has been removed from the CLI.
• The default packet size for IQ PICs has been changed from 256 bytes to 40 bytes. [JUNOS Class of Service Configuration Guide, JUNOS Network Interfaces Configuration Guide]
• 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]

    [JUNOS Class of Service Configuration Guide]

• The traceoptions statement configured at the [edit protocols vrrp] hierarchy level and its related functionality have been standardized. The additional match regex option has been added at the [edit protocols vrrp traceoptions file] hierarchy to refine the output to include only those lines that match the given regular expression. Also, the range for the file size and count has been expanded. The range is from 0 through 4,294,967,296. [JUNOS Network Interfaces Configuration Guide]
• The system no longer allows you to configure IP addresses on a logical unit of a physical virtual loopback tunnel interface. [JUNOS Network Interfaces Configuration Guide]
• You can configure the no-keepalives option on interfaces encapsulated with Cisco-compatible HDLC framing for a translational cross-connect. To do so, include the no-keepalives statement at the [edit interfaces interface-name encapsulation cisco-hdlc-tcc hierarchy level. [JUNOS Network Interfaces Configuration Guide]
• By default, the monitor traffic command has DNS resolution disabled. Also, when the detail or extensive options are used, the default packet length is 1514 bytes. To enable DNS resolution, use the resolve option with the monitor traffic command. [JUNOS Interfaces Command Reference]
• MAC filtering is not supported on Gigabit and 4-port Fast Ethernet interfaces for J6350 and J4350 platforms. In previous software releases, the unsupported source-filtering configuration at the [edit interfaces interface-name fastether-options] hierarchy level was available for these platforms. With JUNOS Release 8.2R1, this option is no longer available in the CLI.
• The show interfaces interface-name extensive command displays input and output CoS transmit queues separately under new Direction: Input and Direction: Output field headings. [JUNOS Interfaces Command Reference]
• Enhanced XENPAK optics statistics—Some XENPAK transceivers provide a subset of the diagnostics that can be polled and displayed by the JUNOS software using the operational mode command show interfaces diagnostics optics. If a XENPAK transceiver can only provide a subset, the statistics fields that cannot be populated with optics information display N/A in the command output. [JUNOS Interfaces Command Reference]

Services Applications

• The valid range for the destination-port statement at the [edit services rpm probe probe-name test test-name] hierarchy level has changed. The previous values were 7 or from 49,152 through 65,533. The new values are 7 or from 49,160 through 65,535.
• Modification to the request security pki local-certificate enroll command—If you do not want to use the default values for the validity-end-time and validity-start-time options, you must configure both options. Previously, you could choose to configure only either an end time or a start time. The validity-end-time and validity-start-time options remain optional. The default value for the validity-start-time option is the current time minus 15 minutes. The default value for the validity-end-time option is the current time plus one week. [JUNOS System Basics Configuration Guide, JUNOS System Basics and Services Command Reference]
• IKE policy enhancement—The any-remote-id statement at the [edit services ipsec-vpn ike policy policy-name remote-id] hierarchy level allows any remote ID to connect. This statement is supported only for IKE policies that are referenced in IKE access profiles of dynamic endpoints. You cannot configure the remote-id statement when the any-remote-id statement is configured for the same policy. [JUNOS Services Interfaces Configuration Guide]
• When a Multiservices PIC experiences persistent back pressure (for 3 seconds), a coredump is triggered and the PIC is rebooted to help clear the condition. A system log message is generated at level LOG_ERR: "MAC stuck, trigger coredump via nmi".

Routing Protocols

• Support for RFC 3847, Restart Signaling for Intermediate System to Intermediate System (IS-IS)—The IS-IS graceful restart TLV defined in the RFC has an optional restarting neighbor ID field that can be filled in when a restart ACK is sent on a LAN interface. This field is useful when there is more than one restarting router on a LAN because it allows the restarting router to determine whether the ACK was sent in response to its own restart request. [JUNOS Routing Protocols Configuration Guide]
• In previous releases, BFD configuration statements were available at several [edit logical-router] hierarchy levels. However, these configuration statements were not recognized by the JUNOS software. With Release 8.2, BFD configuration statements are no longer available at any [edit logical-router] hierarchy level. [JUNOS Routing Protocols Configuration Guide]
• The UDP source port for BFD packets is in the range from 49,152 to 65,535. In previous releases, the UDP source port for BFD packets was port 3784. [JUNOS Class of Service Configuration Guide]

MPLS Applications

• When IGP hello messages continue to be passed, RSVP does not preempt a session passing through a neighboring router even if the RSVP hello messages time out. However, RSVP sessions are brought down as soon as the IGP hello messages are lost. Because of this change of behavior, RSVP sessions are not brought down immediately even if RSVP is disabled on the neighboring router. If RSVP is disabled, the LSPs are not brought down until the RSVP PATH/RESV messages time out. [JUNOS Routing Protocols Configuration Guide]

Routing Policy and Firewall Filters

• Packets with a destination of 0.0.0.0 are now discarded by default. Previously, when a default route covering the destination address 0.0.0.0 (the obsolete limited broadcast address) was installed, the packets were forwarded. To forward traffic destined to 0.0.0.0, you can add a static route to 0.0.0.0/32 (for IPv4) or 0::0/128 (for IPv6). [JUNOS Policy Framework Configuration Guide]
• Enhanced load balancing functionality—The routing platform now supports indexed next-hop load balancing for IPv4 to MPLS next hops. This allows you to configure two-level hierarchical load balancing. To configure, 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. [JUNOS Policy Framework Configuration Guide, JUNOS MPLS Applications Configuration Guide]

VPNs

• The output statement for VPLS egress forwarding table filters is deprecated. You can no longer configure the output statement at the [edit forwarding-options family vpls filter] hierarchy level. You can continue to configure ingress forwarding table filters with the input statement at the [edit forwarding-options family vpls filter] hierarchy level. [JUNOS Policy Framework Configuration Guide, JUNOS VPNs Configuration Guide]

Class of Service

• 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. [JUNOS Class of Service Configuration Guide]
• For queues with negative credits, Juniper Networks routers now transmit traffic from the queue with the highest priority (3) first and then transmit traffic from queues with lower priorities when the high-priority queue is empty.
• The IQ PIC default average packet size is now 40 bytes. In previous releases, the default was 256 bytes. To modify the packet size to 256 bytes, include the large-scale statement at the [edit chassis fpc fpc-slot pic pic-slot q-pic-large-buffer] hierarchy level. [JUNOS Class of Service Configuration Guide, JUNOS System Basics Configuration Guide, Network Interfaces Configuration Guide]

J-Web

• The J-Web interface now includes a setting for the hardware-timestamp statement.
• J-Web Quick Configuration support for static ARP addresses on Ethernet interfaces—Support for configuring static ARP addresses on Gigabit Ethernet and Fast Ethernet interfaces has been extended to the Quick Configuration pages on the J-Web interface. You can now configure static ARP addresses using the Interfaces Quick Configuration page. [J-Web Interface User Guide]

JUNOS API and Other Scripting

• When a JUNOScript or NETCONF client application requests information from the candidate configuration, attributes in the <configuration> tag indicate when the configuration last changed, both as the number of seconds since 1 January 1970 and as a translation to local time. When the client requests the committed configuration, attributes indicate when it was committed (again in the two time formats) and also names the user who requested the commit operation. [JUNOScript API Guide and NETCONF API Guide]

System Log

System log message tag names are now 32 characters or fewer in length. Table 1 lists the previous and new name of each tag. The third column in the table indicates whether the text written to the system log for the tag has also changed. For details about the changed text, see the list that follows the table.

Table 1: System Log Messages: 32–Character Limit Changes

The logged text for some system log messages has changed as indicated in the following list. Tags for which the name has also changed in JUNOS Release 8.2 (see Table 1) are listed by their new name.

• ASP_SFW_ALG_PROMOTION_FAILED—ALG promotion failed. Stateful firewall application stateful-firewall-application-name conflicts with NAT application nat-application-name or QoS application; request creation of discard flow
• ASP_SFW_ICMP_PACKET_ERROR_LENGTH—proto protocol-number (protocol-name), source-interface-name:source-address:source-port -> destination-address:destination-port, ICMP packet had invalid number of bytes
• ASP_SFW_IP_PACKET_FRAG_LEN_INV—proto protocol-number (protocol-name), source-interface-name:source-address:source-port -> destination-address:destination-port, IP fragment length invalid
• ASP_SFW_PING_DUPLICATED_SEQNO—proto protocol-number (protocol-name), source-interface-name:source-address:source-port -> destination-address:destination-port, Duplicate ICMP echo request; packet dropped
• ASP_SFW_PING_MISMATCHED_SEQNO—proto protocol-number (protocol-name), source-interface-name:source-address:source-port -> destination-address:destination-port, ICMP echo reply has no matching sequence number; packet dropped
• ASP_SFW_PING_OUTOF_SEQNO_CACHE—proto protocol-number (protocol-name), source-interface-name:source-address:source-port -> destination-address:destination-port, Too many ICMP echo requests without replies; packet dropped
• AUDITD_RADIUS_REQ_CREATE_FAILED—Unable to create RADIUS request: error-message
• AUDITD_RADIUS_REQ_DROPPED—Discarded Accounting-Request message; no RADIUS server responded
• AUDITD_RADIUS_REQ_TIMED_OUT—Retransmitted request to RADIUS server radius-server
• CHASSISD_GRES_UNSUPP_INTERFACE—Unable to enable graceful Routing Engine switchover; interface interface-name does not support it
• CHASSISD_GRES_UNSUPP_PIC—Unable to enable graceful Routing Engine switchover; PIC does not support it
• CHASSISD_HSR_ELEMENTS_ERROR—Provided number of HSR elements (count) was invalid
• L2TPD_DB_TUN_GRP_ALLOC_FAILED—Unable to allocate memory for tunnel group
• L2TPD_DEFAULT_PROTO_CREATE_FAIL—Unable to create default L2TP module
• L2TPD_IFD_MSG_REGISTER_FAILED—Unable to register message handler for interface device: error-message
• L2TPD_IFL_MSG_REGISTER_FAILED—Unable to register message handler for interface: error-message
• L2TPD_MESSAGE_REGISTER_FAILED—Unable to register L2TP message handler: error-message
• L2TPD_SESSION_IFL_CLI_TREE_ALLOC—Unable to allocate memory for session tree for interface interface-name
• L2TPD_TUNNEL_GROUP_CFG_ADD_FAIL—Unable to add tunnel group tunnel-group (service set service-set) to configuration for PIC pic-slot: error-message
• L2TPD_TUNNEL_GROUP_CFG_DEL_FAIL—Unable to delete tunnel group tunnel-group (service set service-set): error-code
• LIBJNX_COMPRESS_EXEC_FAILED—Unable to compress file 'filename' using program-name: error-message
• LIBJNX_DEFAULT_IP_ADDR_NOT_SET—Unable to retrieve system default IP address: not set in kernel (error-message)
• PPPD_CHAP_AUTH_IN_PROGRESS—Interface interface-name received response 'operation' with CHAP ID message-id, but was still authenticating previous response
• PPPD_CHAP_INVALID_IDENTIFIER—Interface interface-name received 'operation' message with CHAP ID message-id instead of expected ID expected-value
• PPPD_RADIUS_ALLOC_PASSWD_FAILED—Unable to allocate RADIUS password of size size: error-message
• PPPD_RADIUS_CREATE_REQ_FAILED—Unable to create RADIUS access request message: error-message
• RDD_IFDEV_INCOMPATIBLE_SWITCH—Unable to switch rsp-interface-name to secondary interface secondary-interface-name; PIC is incompatible with primary
• RPD_KRT_IFD_CELL_RELAY_INV_MODE—Invalid mode (mode) specified for interface device interface-name; defaulting to port mode
• RPD_KRT_IFD_CELL_RELAY_NO_MODE—No mode specified for interface device interface-name; defaulting to port mode
• RPD_KRT_IFL_CELL_RELAY_INV_MODE—Invalid mode (mode) specified for logical iinterface interface-name; defaulting to port mode
• RPD_KRT_IFL_CELL_RELAY_NO_MODE—No mode specified for logical interface interface-name; defaulting to port mode
• RPD_MPLS_PATH_BW_NOT_AVAILABLE—Unable to satisfy bandwidth configured for MPLS path pathname on LSP lsp-name
• RPD_MSDP_SRC_ACTIVE_OVER_LIMIT—Number of MSDP source-active messages about originator exceeded configured limit message
• RPD_MSDP_SRC_ACTIVE_OVER_THRESH—Number of MSDP source-active messages about originator exceeded configured threshold message
• RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT—Number of MSDP source-active messages about originator no longer exceeded configured limit message
• RPD_MSDP_SRC_ACTIVE_UNDER_THRESH—Number of MSDP source-active messages about originator no longer exceeded configured threshold message

The following system log messages no longer appear in the JUNOS System Log Messages Reference. They report internal problems with the JUNOS software, not errors or events related to your configuration. When these messages appear in the system log, contact your technical support representative for assistance.

• AUDITD_DAEMONIZE_FAILED
• AUDITD_EVLIB_FAILURE
• AUDITD_NOT_ROOT
• AUDITD_PID_FILE_LOCK
• AUDITD_PID_FILE_UPDATE
• AUDITD_USAGE
• DCD_NOT_ROOT (previously DCD_AS_ROOT)
• L2TPD_DAEMONIZE_FAILED
• L2TPD_DUPLICATE
• L2TPD_EVLIB_FD_ALREADY_REGISTERED
• L2TPD_EVLIB_MAINLOOP_FAILURE
• L2TPD_IFD_CLI_RECORD_ALLOC_FAILED
• L2TPD_IFL_CLI_RECORD_ALLOC_FAILED
• L2TPD_NOT_ROOT
• L2TPD_PID_FILE_LOCK
• L2TPD_PID_FILE_UPDATE
• L2TPD_SESSION_CFG_ADD_INVALID_ADDRESS
• L2TPD_SESSION_CFG_DELETE_INVALID_ADDRESS
• L2TPD_USAGE
• MIB2D_INIT_FAILURE
• PPPD_ARGUMENT_FAILURE
• PPPD_DAEMON_FAILURE
• PPPD_EVLIB_MAINLOOP_FAILURE
• PPPD_PERMISSION_FAILURE
• PPPD_PID_LOCK_FAILURE
• PPPD_PID_UPDATE_FAILURE
• RDD_DAEMONIZE_FAILED
• RDD_DUPLICATE
• RDD_EVLIB_EXIT_FAILURE
• RDD_NOT_ROOT
• RDD_PID_FILE_LOCK
• RDD_PID_FILE_UPDATE
• RDD_USAGE
• RPD_USAGE (previously RPD_PARSE_USAGE)

[JUNOS System Log Messages Reference]

Copyright © 2007, Juniper Networks, Inc. All Rights Reserved. Trademark Notice.