The SPX monitoring PE join checklist

The following checklist can be used to diagnose PE-join issues in conjunction with SPX monitoring tools.

Problem	Items to check	Related commands and instructions
PE unit is not responding or does not join CB — No transit PE in topology	The CB port is up.	`show interfaces brief`
	The CB is enabled.	`show spx` (spx cb-enable is present)
	The SPX port or LAG is correct.	`show spx debug lag all` The command as shown derives information on LAG connections and members from the CB. Use the keyword distributed to derive information directly from remote PE units. For example, `show spx debug lag all distributed all-pe`
	The LLDP packet is being received by the CB.	`show spx pe topology` level
	Topology is valid.	`show spx`
	Free PE IDs are available.	`show spx`
PE does not join — Transit PE present in topology	PEs on the path joined and are in Ready state.	`show spx-mon`
	PE forwarding entries match upstream and cascade port configuration.	`show spx-mon`
	CB port is up.	`show interfaces brief`
	LLDP packet is being received.	`show spx pe topology` level
	Topology is valid.	`show spx`
	Free PE IDs are available.	`show spx`
PE joins but does not achieve Ready state, or PE ages out	CB port is up.	`show interfaces brief`
	The port has no errors or unidirectional failures.	`show statistics`
	CSP port state is correct.	`show spx debug port` unit/slot/port