| 1. PE unit is not responding or does not join CB.
|
a. Cable is correctly connected and connecting port is up.
|
On CB and PE port:
show interfaces brief
|
| b. PE unit shows up and is in Ready state.
|
On CB and PE:
show running-config
On CB:
show spx
|
| c. All transit PE units are correctly connected and are in Ready state.
|
On CB:
show spx
|
| d. All transit PE units are correctly configured.
|
show spx debug port
unit/slot/port (for all SPX LAG members)
|
e. CB configuration is correct. SPX is enabled (spx cb-enable is present in configuration).
|
On CB:
show running-config
|
| f. There is an SPX port or SPX LAG connection from the CB to the PE unit.
|
On CB:
show running-config
On CB:
show spx
show spx debug port
unit/slot/port (for all SPX LAG members)
|
| g. Is the PE unit stuck in sync?
|
Contact technical support.
|
| 2. Topology not supported.
|
Is the configuration blocked?
|
Review "Invalid Topology" message on console for details. If no message appears,
check that maximum configuration limits for PEs or CBs have not been exceeded.
|
| 3. CB cannot assign PE ID.
|
Ports and connections are valid.
PE ID is available (not already in use or reserved).
|
The following message in the CB port log indicates the pe-id is reserved, but the
topology of the joining PE does not match the reserved configuration:
"No available ID: must remove unused "pe-id."
In this case, you should remove the unused pe-id configuration.
|
| 4. Image mismatch.
|
Is there a major image mismatch?
|
show stack
show spx
|
|
Path to FTP server is configured correctly.
The image folder is present.
FTP server is connected.
|
show running-config
Ping the server address to verify connectivity.
|
| Auto image copy is disabled.
|
From CB:
show stack detail
If auto image copy should be disabled, manually download the image from the CB to
the PE unit, or reset the PE unit.
|
| 5. Configuration mismatch.
|
PE configuration on CB matches actual PE modules.
|
If the PE configuration on the CB does not match actual PE modules, remove the reserved
configuration on the CB. Issue a
no spx unit
ID command to remove the reserved configuration of the PE unit
ID. This causes the CB to relearn the correct modules for the PE unit. If the
no spx unit
xx command is blocked due to the configuration on the PE unit, remove the erroneous
configuration.
|
| 6. A connected PE unit detaches from the CB.
|
SPX LAG or SPX port status.
|
If ports are down, investigate reasons. If ports are up, a further issue is indicated.
Collect
supportsave spx output for both CB and PE for further analysis. Call technical support for assistance.
|
| 7. SPX LAG issues are evident.
|
LAG configuration is correct.
Connections on both sides of the LAG match. Speeds on both sides match.
Ports in LAG are operational.
Topology is valid.
|
show spx debug lag all
Adding the
distributed keyword to the command. Without the keyword, the command output is derived from the
CB. The following example displays information on LAG members and connections directly
from PE units.
show spx debug lag all distributed all-pe
|
| 8. LAG issues between PE ports are evident.
|
LAG configuration is correct.
|
show lag
|
| 9. Multicast traffic not being forwarded to one or more virtual ports.
|
Virtual ports are part of mcache OIF.
|
Run the
show ip pim vrf vrf1 mc command on both the router and the joined PE locally and compare output.
|
|
Issues persist.
|
Contact technical support for any additional assistance.
|