Handling Nonoperational PE Units
The CB can access nonoperational units through an SPX link to correct common issues.
A PE unit may become nonoperational for the following reasons:
- The PE is running an image version that does not match the version on the CB.
- The modules installed on the PE unit do not match the reserved configuration for the
PE unit that is stored on the CB. For example, the reserved configuration on the CB
contains a configuration for SPX unit 18 with a 48-port module in slot 1, but the
actual PE unit has a 24-port module installed in slot 1. In this case, you can remove
the reserved configuration of the nonoperational SPX unit 18 with the
no spx unit 18command so the CB can learn unit 18 modules correctly. Refer to Adding a reserved PE configuration on the CB for more information.
All data ports, except for SPX ports or SPX LAGs, in a nonoperational PE are shut down. The CB can still control the nonoperational PE in the following limited ways:
- The CB can download the correct images to the PE unit. Refer to SPX image upgrade for more information.
- The CB can unconfigure the PE unit to convert it to a regular router. Refer to Unconfiguring the 802.1br core stack or PE units.
- The CB can reload the PE unit.