[ 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 summary 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. 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 Type 3 FPCs only, the rate limit for ICMP traffic has been increased from the current 50 pps to 250 pps per logical interface.

J-series chassis power and heat capacities for PIM combinations—Before you install a PIM, verify that the combination of PIMs installed in a chassis does not exceed the power and heat capacities for that model. The capacity of each chassis model and power and heat values required by each PIM can be represented in nondimensional tokens.

Caution: Do not install a combination of PIMs in a single chassis that exceeds the power and heat capacities described in this section. Installing a combination of PIMs in your router might cause equipment damage.

Add the token values for power and heat for each PIM or module that you want to install in a single chassis. The power tokens for a J4350 or J6450 chassis must not exceed 100. Likewise, the heat tokens must not exceed 100.

Table 2 shows the power and heat dissipation tokens assigned to each J-series PIM or module.

Table 2: J-series PIM Power Consumption and Heat Dissipation

Name	Model Number	PIM Abbreviation in JUNOS CLI	Tokens
Name	Model Number	PIM Abbreviation in JUNOS CLI	Power	Heat
16-Port Gigabit Ethernet uPIM	JXU-16GE-TX-S	16xGE uPIM	38	36
8-Port Gigabit Ethernet uPIM	JXU-8GE-TX-S	8xGE uPIM	21	27
6-Port Gigabit Ethernet uPIM	JXU-6GE-SFP-S	6xSFP uPIM	13	13
1-Port SFP Gigabit Ethernet ePIM	JXE-1GE-SFP-S	1xGE SFP	8	8
1-Port Copper Gigabit Ethernet ePIM	JXE-1GE-TX-S	1xGE Copper	6	7
4-Port Fast Ethernet ePIM	JXE-4FE-TX-S	4xFE ePIM	9	9
Dual-Port Fast Ethernet PIM	JX-2FE-TX-S	2xFE	6	6
ADSL 2/2+ Annex A PIM (1 port, for POTS)	JX-1ADSL-A-S	1x ADSL Annex A	16	16
ADSL 2/2+ Annex B PIM (1 port, for ISDN)	JX-1ADSL-B-S	1x ADSL Annex B	16	16
G.SHDSL PIM (2-port two-wire mode or 1-port four-wire mode)	JX-2SHDSL-S	2x SHDSL (ATM)	9	10
Dual-Port E1 PIM	JX-2E1–RJ48–S	2xE1	6	6
Dual-Port T1 PIM	JX-2T1–RJ48–S	2xT1	6	5
T3 PIM (also known as DS3)	JX-1DS3-S	1xT3	7	7
E3 PIM (1 port)	JX-1E3-S	1xE3	7	7
Dual-Port Channelized T1/E1/ISDN PRI PIM	JX-2E1-RJ48-S	2xCT1E1 / PRI	6	5
4-Port ISDN BRI S/T PIM	JX-4BRI-S-S	4x BRI S/T	4	4
4-Port ISDN BRI U PIM	JX-4BRI-U-S	4x BRI U	4	6
Dual-Port Serial PIM	JX-2Serial-S	2xSerial	5	6
TGM550 Telephony Gateway Module	Avaya	1x TGM550	14	19
TIM510 E1/T1 Telephony Interface Module	Avaya	1x DS1 TIM510	6	6
TIM514 Analog Telephony Interface Module	Avaya	4x FXS, 4xFXO TIM514	4	13
TIM521 BRI Telephony Interface Module	Avaya	4x BRI TIM521	3	3

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. [Installation Guide, System Basics and Services Command Reference]
If GRES is still enabled on a router, JUNOS software upgrade and downgrade procedures will be aborted. [Installation Guide]

User Interface and Configuration

The maximum number of outstanding transfer processes has been restricted to 10. [System Basics]
When you issue a tnping prompt, the response from a secondary Routing Engine now reverts to its local address instead of to the backup address. [System Basics]
The traceoptions statement at the [edit access] hierarchy level has been deprecated with the removal of NASD. A new traceoptions statement is available at the [edit protocols ppp] hierarchy level. The flag kernel option has been renamed flag rtsock. [System Basics, Network Interfaces]
The J-Web interface now includes a setting for the hardware-timestamp statement. [J-series Administration Guide]
On M-series and T-series routing platforms, the request system snapshot command previously used the same default values for root-size, config-size, and var-size, which did not support certain hardware configurations. These values have now been adjusted to appropriate values for the hardware. On J-series Services Routers, these values are user-configurable options. [System Basics and Services Command Reference]

Interfaces and Chassis

VRRP trace logging enhancement—You can enable the VRRP process to log in microseconds by including the microsecond-stamp statement at the [edit protocols vrrp traceoptions] hierarchy level. [Network Interfaces]
Update to monitor interface statistics command—Previously the monitor interface statistics command output for the LCC of a multichassis system displayed the physical interface statistics for the whole system. Now it displays traffic statistics for physical interfaces present on the LCC only. [Interfaces Command Reference]
Transit traffic blocked from management Ethernet interface to Packet Forwarding Engine. (M-series and T-series routing platforms)—A JUNOS software change has been made to make traffic flow consistent. Traffic is already blocked from the Packet Forwarding Engine to the management Ethernet interface (fxp0). Traffic is now blocked from fxp0 to the Packet Forwarding Engine.
In show chassis hardware command output for J-series Services Routers, the identifier for the 2x CT1E1 PIC now appears as 2x CT1E1 / PRI to reflect the addition of PRI capability in the PIC.
On IQ2 PICs without per-unit-scheduler configuration, the whole PIC supports 4071 VLANs and you can configure all 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. [Network Interfaces]
On 1-port 10-Gigabit IQ2 PICs, if you configure a local loopback using the loopback statement at the [edit interfaces interface-name gigether-options] hierarchy level, the transmit path stops working, causing the remote end to detect a down link. [Network Interfaces]
The output for the show chassis hardware operational mode command now includes a NEBS descriptor for Network Equipment Building System (NEBS)-compliant platforms. [System Basics and Services Command Reference]
You can now configure up to 30 dialer pools at the [edit interfaces interface-name dialer-options] hierarchy level. Previously the maximum was 16. [Network Interfaces, J-series Basic Configuration]
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]
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. [Network Interfaces]
You can now enable or disable SNMP notifications on state change for Channelized IQ PIC interfaces. To configure these options, include the (traps | no-traps) statement at the [edit interfaces interface-name] hierarchy level. These options are already available for other interface types. [Network Interfaces]
The JUNOS software now supports IPv6 static neighbor discovery cache entries, similar to static ARP entries in IPv4. [Network Interfaces]
Notification of link-down alarm generation and transfer is now supported for 10-Gigabit Ethernet PICs on T-series routing platforms. To configure this option, include the asynchronous-notification statement at the [edit interfaces interface-name gigether-options] hierarchy level. [Network Interfaces]
You can now configure an MTU value on dialer interfaces with multilink encapsulation. To configure this setting, include the mtu statement at the [edit interfaces dl0 unit logical-unit-number family inet] hierarchy level. [Network Interfaces]
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. [Network Interfaces]
For PICs with small form-factor pluggable transceivers (SFPs), the show chassis pic command output includes new Fiber type and Wavelength fields. [Interfaces Command Reference]
For J-series Services Routers only, the source-address-filter statement at the [edit interfaces interface-name gigether-options] hierarchy level has been deleted from the CLI, because J-series Gigabit Ethernet interfaces do not support MAC filtering. [Network Interfaces, J-series Basic Configuration]
Change in options hierarchy for serial interfaces—The control-leads statement at the [edit-interfaces interface-name] hierarchy level has been deprecated. For J-series serial interfaces (se-pim/0/port), it is replaced by the dce-options statement. For M-series and T-series serial interfaces (se-fpc/pic/port), it is replaced by the dte-options statement. Serial interface functions and substatements remain unchanged. Although the control-leads statement still operates in existing configurations, use the dce-options or dte-options statement for new configurations. [Network Interfaces, J-series Configuration]

The following table shows the round-trip time (RTT) delay buffer values for IQ2 PICs, which are nonstandard and vary by PIC type and direction. The values are rounded up slightly to account for oversubscription. [Network Interfaces]

IQ2 PIC Type	Ingress Buffer (ms)	Egress Buffer (ms)
4-port Gigabit Ethernet (Type 1)	200	300
8-port Gigabit Ethernet (Type 2)	175	200
8-port Gigabit Ethernet (Type 3)	35	225
1-port 10-Gigabit Ethernet (Type 3)	25	190

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]
MTU configurable on multilink dialer interfaces (J–series Services Routers only)—You can now configure an MTU value on dialer interfaces with multilink encapsulation. To configure this setting, include the mtu statement at the [edit interfaces dl0 unit logical-unit-number family inet] hierarchy level. [Network Interfaces]
Previously, you could include up to eight incoming-called-number statements at the [edit interfaces br-pim/0/port isdn-options] hierarchy level. Starting in JUNOS Release 8.3, you can configure up to 30 incoming called numbers. [Network Interfaces]
On aggregated Ethernet (ae0) interfaces, interface policers configured with the bandwidth-percent statement are not supported. [Network Interfaces]
Routing Engine mastership option for routing matrixes—Enables you to combine the all-chassis option with each of the acquire, release, and switch options for the request chassis routing-engine master command when issued on the TX Matrix platform in a routing matrix. Previously, you could combine the all-chassis option with the switch option only. [System Basics and Services Command Reference]

Services Applications

Update to clear services ipsec-vpn certificates command—When you issue the clear services ipsec-vpn certificates command, it now clears the certificate revocation list (CRL) from the cache along with the certificates. [System Basics and Services Command Reference]
When a MultiServices PIC is experiencing persistent back pressure (for 3 seconds), a core dump 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."
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. [Services Interfaces]
The valid range for the destination-port statement at the [edit services rpm probe probe-name test test-name] hierarchy level has changed from 7 or the range from 49152 through 65535 to 7 or the range from 49160 through 65535. [Services Interfaces]

Routing Protocols

For the show ospf overview command, the brief and detail options previously displayed the same information as the standard command, and the extensive option also displayed trace information. The brief and detail options are now deprecated and the extensive option is still supported. [Protocols Command Reference]
You can now configure BFD for IBGP sessions and multihop EBGP sessions. Previously this resulted in a commit error. In addition, you can now configure bfd-liveness-detection at the global BGP level. Previously it was only allowed at the group and neighbor level. [Routing Protocols]
If you enable the BGP traceoptions flag update option (only), received keepalive messages will no longer generate a trace message. [Routing Protocols]
New BFD traceoptions flag—A new pipe-detail flag is supported at the [edit protocols bfd traceoptions] hierarchy level. [Routing Protocols]

Multicast

The enable | disable statement at the [edit routing-options multicast interface] hierarchy level is now deprecated. [Multicast]
The traceoptions statement currently configured at the [edit routing-options] hierarchy level is now also configurable at the [edit routing-options multicast] level for multicast-specific tracing operations. [Multicast]
The mtrace statement is now supported in logical router configurations. [Multicast]
When you enable automatic rendezvous point (auto-RP) assignment, you must configure the autorp-announce and autorp-discovery groups explicitly as dense groups for auto-RP to function. When the autorp-discovery group is not configured as a dense group, auto-RP is not enabled, irrespective of the mode in which auto-RP is configured. When the autorp-announce group is not configured as a dense group, auto-RP is enabled in discovery mode only; mapping and announce modes are disabled. [Multicast]

MPLS Applications

Display output for the show rsvp version command has been updated to comply with UI standards. Changes are cosmetic only. [Protocols Command Reference]
The traceroute as-number-lookup and lsping functionality now works with logical router configurations. [MPLS Applications]
The monitor label-switched-path command now works with logical router configurations. [Protocols Command Reference]
LSP optimization performance—To avoid delays in LSP reoptimization when the LSP configuration changes, configure the LSP optimization switchover time interval to 90 seconds or less by including the optimize-timer 90 statement setting at the [edit protocols mpls] hierarchy level. You should also enable ICMP tunneling on all PE and P routers by including the icmp-tunneling statement at the same hierarchy level. To verify that the paths are operating correctly, issue the ping clns or traceroute clns command from CE router to CE router. [MPLS Applications, System Basics and Services Command Reference]

Class of Service

Average buffer WRED (IQ PICs, except for Gigabit Ethernet IQ PICs)—By default, the PIC is configured to use instantaneous buffer occupancy for WRED. You can optionally specify a value for the instant-usage-weight-exponent statement at the [edit chassis fpc number pic number red-buffer-occupancy weighted-average] hierarchy level. If not specified, it defaults to 1. The range of values for this statement is 0 through 31. The value you specify will be revised up or down to the nearest value that is supported by the IQ PIC. [Class of Service, System Basics]
Prior to JUNOS Release 7.4, the JUNOS software imposed a commit restriction of 50 percent as the maximum CoS shaping rate. This restriction still applies to OC12 PICs, but does not apply to OC48 PICs. [Class of Service]
For queues with negative credits, Juniper Networks routers now transmit traffic from the queue with the highest priority (3) first and transmit traffic from queues with lower priorities when the high-priority queue is empty. [Class of Service]
On T-series, J-series, M120, M320, and MX960 platforms, an implicit default classifier is now supported for IPv6 traffic, similar to the existing one for IPv4 traffic. The implicit dscp-ipv6 classifier is applied to every logical interface that does not have one configured in the CLI. This classifier is applied the same way that the ipprec-compatibility classifier is applied for IPv4. [Class of Service]
1-port OC12 PICs on T-series and M320 routing platforms now support up to eight queues. [Class of Service]

Routing Policy and Firewall Filters

In firewall configurations, you can now use numeric values for the icmp-type match condition for protocol family inet6. Previously this behavior was supported only for family inet. [Policy Framework]
Support for policy filtering based on BGP extended communities—You can now specify an extended BGP community for a BGP community routing policy. When you configure the extended communities attribute, include a 16-bit number that identifies the specific extended BGP community in the members [community-ids] statement at the [edit policy-options community name] hierarchy level. Previously, the only types of extended communities you could specify were bandwidth, target, origin, or domain-id. [Policy Framework]
Configuration for metric expressions—Previously, you could not load a configuration for metric2 options under the then metric expression statement by issuing the load merge | override command. You can now load values for the multiplier and offset options of the metric and metric2 statements at the [edit policy-options policy-statement name term name then metric expression] hierarchy level. [Policy Framework]
The CLI syntax for defining policers locally inside a filter statement, which has been deprecated for several releases, is no longer allowed. You must define filter-specific policers at the firewall level instead. [Policy Framework]
If you include the port statement along with either the source-port or destination-port statement in a match condition in a firewall filter term, the configuration is invalid and the commit will fail. [Policy Framework]
The name of a firewall filter, counter, and policer can now be up to 64 characters long. Previously the name could be only 24 characters long. You configure firewall filters at the [edit firewall family family-name filter filter-name] hierarchy level. The counter name is an action modifier that you configure at the [edit firewall family family-name filter filter-name term term-name then count counter-name] hierarchy level. You configure firewall policers at the [edit firewall policer policer-name] hierarchy level. [Policy Framework]
The deprecated syntax of defining policers locally at the [edit firewall family inet filter] hierarchy level is no longer accepted. You need to define filter-specific policers at the [edit firewall] level. [Policy Framework]

Network Management

A new system log message and a health monitoring service trap have been added to track the kernel memory usage going above 80 percent. [Network Management, System Log Reference]

JUNOScript API

The JUNOScript Perl module for establishing Telnet connections no longer includes the -l option on the telnet command, because that option is not compatible with all vendors’ versions of Telnet. It instead uses the Perl Expect module to parse the prompt generated by the Telnet server. The Expect module is now included in the JUNOScript Perl prerequisites package. [JUNOScript API Guide]

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