Enabling and using SPX monitoring
Use SPX monitoring tools to help you determine the source of an issue in the Campus
Fabric domain, whether the issue stems from a configuration error or system problems.
Output from the
show spx-mon command highlights issues and provides possible next steps to resolve the issues.
From the CB active controller, SPX monitoring checks for the following common issues in the Campus Fabric domain:
- New PE units: The system message indicates that executing the
write memorycommand is required. - PE state: "Ready" indicates that the PE has successfully joined the CB.
- PE units with configuration mismatch: The system displays steps needed to correct the problem.
- PE units with image mismatch: The system lists steps to correct the condition (for example, enable autocopy or configure the TFTP server).
- Current CPU utilization: CPU utilization is listed for the active controller, and, if CPU utilization on the standby controller or any PE unit exceeds 50 per cent, updates are included.
- Port utilization: For each PE, the system indicates the SPX port with the highest utilization.
- SPX port errors: Any PE SPX port errors are listed. For each PE, the SPX port with the highest error count is also listed.
- PE user port errors: Any PE user ports with errors are listed. For each PE, the user port with the highest utilization is also listed.
- SPX port state: The system checks PE port state against CB port state.
- PE chain or ring state: The system lists the members of a chain, the CB SPX port connection, and whether the connection is active.
- PE ring ACL state: The system displays whether the PE ring has passed ACL verification.
Some other items that SPX monitoring can diagnose include:
- PE-to-PE port consistency between the active and standby controllers
- SPX port hardware configuration
- SPX LAG hardware configuration
- CB-PE topology database
- PE forwarding entries
- SPX port VLAN configuration
- SPX port spanning tree state
- Virtual ports for all PE ports
- PE join validation.
Perform the following steps to enable and use SPX monitoring features.
- In global configuration mode on the CB, enter the
enable spx-moncommand. - On the CB in Privileged EXEC or global configuration mode, enter the
show spx-moncommand for information on PE state.ICX7750-48F Router# show spx-mon spx-mon is enabled Total 2 PE(s) attached Number of PEs in Ready State : 2 (Id(s): 17, 23) Number of PEs in Reserve : 1 (Id(s): 18) Number of PEs in Config-mismatch : 0 Number of PEs in Image-Mismatch : 0 CLI: sh spx-mon pe-join <cb-cport> can be used to diagnose pe-join issues Active CPU Utilization 1 sec avg 1 percent busy 5 sec avg 1 percent busy 60 sec avg 1 percent busy 300 sec avg 1 percent busy PE CPU Utilization: Normal Spx Interface Utilization: Very low Spx Interface Errors: None PE User Port Errors: None ---------------------------------------------------------------------------------------------- SPX CB [CASC PORT] CHAINS CB Port Epoch |Ring Id FSM State|Remote CB port | Chain ---------------------------------------------------------------------------------------------- 2/1/1 9 NO 0 INIT INVALID PE17--PE23The example shows that spx-mon is enabled, two PEs (17 and 23) are attached and in Ready state, and one PE configuration is reserved (PE 18). There are no configuration issues, and CPU Utilization is normal, while SPX usage is very low and error-free. One PE chain is connected through CB port 2/1/1. - For information on a PE unit joining the domain, enter the
show spx-mon pe-joincommand followed by the port number for the CB cascade port.ICX7750-26Q(config)# show spx-mon pe-join 2/1/1 Error! Last PE 23 in the chain has no DOWNSTREAM SPX ports in UP state Above error(s) needs to be corrected...
The example checks CB SPX port 2/1/1 and shows a PE join issue for PE unit 23.In this situation, CB SPX port 2/1/1 is connected to a PE chain with PE 23 as the last PE. A new PE cannot join the chain until at least one of the SPX ports on PE 23 is up. The system has detected that no SPX port is up to allow the new PE to join.