JunosE 12.1.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 following JunosE documentation set fails to mention additional information regarding the creation of core dump files when the NMI button is depressed:
• ERX Hardware Guide—Resetting Line Modules and SRP Modules section in Chapter 9, Troubleshooting
• E120 and E320 Hardware Guide—Resetting Line Modules and SRP Modules section in Chapter 9, Troubleshooting

If you configure the router to generate core dumps using the exception dump command in Global Configuration mode, and if sufficient space is available at the destination to which the core dump files are transferred (such as the local flash card if you used the local keyword with the exception dump command), depressing the NMI button causes a core dump file to be stored on the flash card. This method of generating core dump files is applicable for both SRP modules and line modules. You can use the show exception dump command to determine whether core dumps are generated for only SRP modules or line modules.

• The Monitoring the System section in JunosE System Basics Configuration Guide, Chapter 5, Managing the System omits the description for the subfields of the show memory-management protection command.

See the JunosE 12.1.x System Basics Configuration Guide for updated information.

• The following note applies to Step 6 in the procedure that describes how to use the slot-replace command to replace a line module in the Replacing a Line Module Without Erasing the Slot section in JunosE System Basics Configuration Guide, Chapter 6, Managing Modules:

You cannot use the slot-replace command to replace an ES2 10G ADV LM in a particular slot with an ES2 10G LM without erasing the interface configuration on the slot. If you attempt such a replacement of LMs that are part of a redundancy group or a high availability pair of modules, the ES2 10 LM resets.

• The following note regarding the usage of ES2 10G ADV LMs and ES2 10 LMs in a line-module redundancy group applies to the E120 and E320 Routers section under the Line Module Redundancy Requirements main topic in JunosE Service Availability Configuration Guide, Chapter 2, Managing Module Redundancy:

In a redundancy group of line modules, if an ES2 10G LM functions as the primary line module and an ES2 10G ADV LM operates as the standby module, a stateless switchover happens from the primary to the secondary line module when the primary line module has encountered a failure. After the switchover occurs, the ES2 10G LM starts functioning as the standby module and the ES2 10G ADV LM becomes the primary module.

In such a scenario, you cannot use the redundancy revert command in Global Configuration mode or redundancy revertive command in Privileged Exec mode to revert the ES2 10G LM as the primary module.

We recommend that you lock out all the ES2 10G ADV LMs in the redundancy group to prevent a stateless switchover from ES2 10G LMs to ES2 10G ADV LMs. Using ES2 10G ADV LMs as the backup modules for ES2 10 ADV LMs that operate as primary modules is undefined.

• The following additional information applies to the Guidelines for Configuring Stateful Line Module Switchover section in JunosE Service Availability Configuration Guide, Chapter 4, Managing Stateful Line Module Switchover:

Hardware or software failure of an ES2-S1 Service IOA on an ES2 4G LM does not cause a stateful line module switchover.

• The following additional information regarding the processing of L2TP sessions during a stateful line module switchover procedure applies to the L2TP subtopic under the Application Support for Stateful Line Module Switchover section in JunosE Service Availability Configuration Guide, Chapter 4, Managing Stateful Line Module Switchover:

When you perform a stateful switchover on one pair of line modules enabled for high availability, L2TP sessions continue to be established on the other tunnel server modules. The Server Card manager (SCM) application selects the circuits from other tunnel server modules to reroute the L2TP sessions until the stateful switchover from the primary module to the secondary module is completed. The L2TP application notifies the SCM after the switchover is completed and the SCM continues to balance the sessions across all the available tunnel server modules.

• The Duplicate and Broadcast Accounting section in JunosE Broadband Access Configuration Guide, Chapter 1, Remote Access Overview incorrectly states that the accounting information continues to be sent to the authenticating virtual router, but not to the operational virtual router, regardless of whether duplicate or broadcast AAA accounting is enabled on those routers. The following information describes the correct transmission of accounting information to authenticating virtual routers and operational virtual routers:

The accounting information is always sent to the authenticating virtual router. The accounting information is sent to the operational virtual router only if duplicate accounting is not enabled and if the authenticating virtual router is different than the operational virtual router.