JunosE 11.2.0 Release Notes

Errata

This section identifies errors found in the JunosE documentation. These errors are corrected in subsequent releases of the affected documentation.

• The JunosE documentation for Release 6.0.5 and higher-numbered releases states that when you upgrade the JunosE Software from Release 5.1.1 or lower-numbered releases, you must perform the upgrade in two stages: first to an intermediate release and then to the higher-numbered release that you want to run. This statement is only partially correct; you must perform a two-stage upgrade only when you upgrade from a new NVS card. This restriction is not applicable if you upgrade your software remotely through Telnet or FTP.

The imprecise information appears in the following JunosE documents:

• The Upgrading to JunosE Software Release 6.x.x or Higher-Numbered Releases from Release 5.1.1 or Lower-Numbered Releases special hardware notice dated 31 March 2006
• The Upgrading to JunosE Software Release 6.x.x or Higher-Numbered Releases from Release 5.1.1 or Lower-Numbered Releases section in the JunosE Release Notes for the following releases:
• Releases 6.0.5, 6.1.4, and 6.1.5
• Releases 7.1.2, 7.1.3, 7.1.4, 7.2.x, 7.3.x
• Releases 8.x, 9.x, 10.x, 11.0.x, and 11.1.x
• The Upgrading to JunosE Software Release 6.x.x or Higher-Numbered Releases from Release 5.1.1 or Lower-Numbered Releases section in ERX Hardware Guide, Chapter 8, Maintaining ERX Routers for the following releases:
• Release 7.3.x
• Releases 8.x, 9.x, 10.x, 11.0.x, and 11.1.x
• The Upgrading to JunosE Software Release 6.x.x or Higher-Numbered Releases from Release 5.1.1 or Lower-Numbered Releases section in the JunosE System Basics Configuration Guide, Chapter 3, Installing JunosE Software for the following releases:
• Release 7.3.x
• Releases 8.x, 9.x, 10.x, 11.0.x, and 11.1.x
• In lower-numbered releases, the Detecting Corrupt File Configurations section in JunosE System Basics Configuration Guide, Chapter 5, Managing the System fails to mention that when you check the running configuration of a .CNF file while auto mode is enabled, auto mode is not stopped immediately. Instead, the following warning message appears:
host1(config)#service check-config 1120frs.cnf
WARNING: This command will cause config monitor to switch into manual mode. Proceed with current command? [confirm]

If you confirm you want to check the running configuration in manual mode, then auto mode is stopped.

• The Grouping ICR Subscribers Based on S-VLAN IDs and Example: Configuring ICR Partitions That Group Subscribers by S-VLAN ID sections in JunosE 11.1.x Service Availability Configuration Guide, Chapter 6, Managing Interchassis Redundancy fail to mention that, to enable the master router to send PPPoE Active Discovery Termination (PADT) packets to the clients and create new sessions for the PPPoE subscribers, you must create a dummy IP interface for each S-VLAN subinterface that is part of the ICR partition. See the JunosE 11.2.0 Service Availability Configuration Guide for updated information.
• In the Grouping ICR Subscribers Based on S-VLAN IDs and Example: Configuring ICR Partitions That Group Subscribers by S-VLAN ID sections in JunosE 11.1.x Service Availability Configuration Guide, Chapter 6, Managing Interchassis Redundancy, the use-default-mac keyword, which is used with the svlan-list, svlan-range, and svlan-list-explicit commands, was incorrectly documented as required for generating Gratuitous ARP (GARP). In fact, the keyword use-default-mac is not required for generating GARP. An example of the correct usage of the commands is as follows:
host1(config-if)#ip vrrp 1 icr-partition svlan-list 100 102 105 108 control-interface advertise-mac

host1(config-if)#ip vrrp 1 icr-partition svlan-range 100 110 control-interface advertise-mac

host1(config-if)#ip vrrp 1 icr-partition svlan-list-explicit 120 1 120 2 control-interface advertise-mac


See the JunosE 11.2.0 Service Availability Configuration Guide for updated information.

• In lower-numbered releases, the description of the mpls ldp graceful-restart reconnect-time command in the JunosE Command Reference Guide A to M incorrectly states that the no version restores the default value of 120 seconds. The correct default value is 140 seconds.
• The JunosE Command Reference Guide N to Z omits the description of the show memory-management protection command, beginning with JunosE Release 7.1.0 in which it was introduced.

The show memory-management protection command is available in Privileged Exec mode. You can use this command to display the information about memory management protection of the router.

The syntax for this command is:

show memory-management protection [detail] [filter]

The command can be used only in the support mode and is not user configurable.