Diagtest
Diagtest
Note
For information about configuring online diagnostic tests see Chapter 14, Configuring Online Diagnostics. We recommend that before you enable any online diagnostics tests that you enable the logging console/monitor to see all warning messages. We recommend that when you are running disruptive tests that you only run the tests when connected through console. When disruptive tests are complete a warning message on the console recommends that you reload the system to return to normal operation: strictly follow this warning. While tests are running, all ports are shut down as a stress test is being performed with looping ports internally and external traffic might affect the test results. The switch must be rebooted to bring the switch to normal operation. When you issue the command to reload the switch, the system will ask you if the configuration should be saved. Do not save the configuration. If you are running the tests on the switch processor (SP), after the test is initiated and complete, you must reload or power down and then power up the switch. If you are running the tests on other modules, after the test is initiated and complete, you must reset the module.
Tip
For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page: http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Global Health-Monitoring Tests, page A-2 Per-Port Tests, page A-6 PFC Layer 2 Forwarding Engine Tests, page A-13 DFC Layer 2 Forwarding Engine Tests, page A-16 PFC Layer 3 Forwarding Engine Tests, page A-21
A-1
DFC Layer 3 Forwarding Engine Tests, page A-26 Replication Engine Tests, page A-32 Fabric Tests, page A-34 Exhaustive Memory Tests, page A-36 IPSEC Services Modules Tests, page A-39 Stress Tests, page A-41 Critical Recovery Tests, page A-42 General Tests, page A-44
TestEARLInternalTables, page A-2 TestSPRPInbandPing, page A-3 TestScratchRegister, page A-3 TestMacNotification, page A-4 TestErrorCounterMonitor, page A-4 TestLtlFpoeMemoryConsistency, page A-5 TestMgmtPortsLoopback, page A-5 TestDataPortLoopback, page A-6
TestEARLInternalTables
The TestEARLInternalTables test detects most PFC and DFC hardware table problems by running consistency checks on the PFC and DFC hardware tables. The test runs every 5 minutes. A failure of the test for the PFC results in one of these actions:
Failover to the redundant supervisor engine. If a redundant supervisor engine is not installed, shutdown of the supervisor engine. Up to two resets of the DFC-equipped switching module. Shutdown following a third failure.
A failure of the test for a test of a DFC results in one of these actions:
A-2
OL-13013-06
Appendix A
Table A-1
TestSPRPInbandPing
The TestSPRPIinbandPing test detects most runtime software driver and hardware problems on supervisor engines by running diagnostic packet tests using the Layer 2 forwarding engine, the Layer 3 and 4 forwarding engine, and the replication engine on the path from the switch processor to the route processor. Packets are sent at 15-second intervals. Ten consecutive failures of the test results in failover to the redundant supervisor engine (default) or reload of the supervisor engine if a redundant supervisor engine is not installed.
Table A-2 TestSPRPInbandPing Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes in order to maintain accuracy. On. 12.1(13)E, 12.2(14)SX to12.2(17d)SXB5, and 12.2(18)SXD. Reset the active supervisor engine. Active and standby supervisor engine.
TestScratchRegister
The TestScratchRegister test monitors the health of application-specific integrated circuits (ASICs) by writing values into registers and reading back the values from these registers. The test runs every 30 seconds. Five consecutive failures causes a supervisor engine to switchover (or reset), if you are testing the supervisor engine, or in the module powering down when testing a module.
Table A-3 TestScratchRegister Test Attributes
A-3
Table A-3
Description Reset the malfunctioning supervisor engine or power down the module. Supervisor Engine 720, DFC-equipped modules, WS-X6148-FE-SFP, WS-X6148A-GE-TX, and WS-X6148A-RJ-45.
TestMacNotification
The TestMacNotification test verifies that the data and control path between DFC modules and supervisor engines is working properly. This test also ensures Layer 2 MAC address consistency across Layer 2 MAC address tables. The test runs every six seconds. Ten consecutive failures causes the module to reset during bootup or runtime (default). After three consecutive resets, the module powers down.
Table A-4 TestMacNotification Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(14)SX. Reset the module. After the module has ten consecutive failures or three consecutive resets, it powers down. DFC-equipped modules.
TestErrorCounterMonitor
The TestErrorCounterMonitor test monitors the errors/interrupts that occur on each module in the system by periodically polling for the error counters maintained in the module. If the errors exceed a threshold value, a syslog message is displayed with detailed information including the error-counter identifier, port number, total failures, consecutive failures, and the severity of the error counter.
Table A-5 TestErrorCounterMonitor Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes to maintain accuracy. On. 12.2(33)SXH.
A-4
OL-13013-06
Appendix A
Table A-5
Description Display a syslog message indicating the error-counters detected on that port. All modules including the supervisor engines.
TestLtlFpoeMemoryConsistency
The TestLtlFpoeMemoryConsistency test verifies that the LTL and FPOE memories are working properly. The test runs every 15 seconds. Self-correction is applied if an error is detected. If self-correction fails, corrective action is triggered through GOLD which is used to reset the module. The module is powered-down on the third consecutive module reset. If self-correction passes, no action is taken. If too many self-corrections occur within a short period of time, the module is reset.
Table A-6 TestLtlFpoeMemoryConsistency Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXI2. Failure of this test causes the module to reset and power down after two resets. All modules including the supervisor engines.
TestMgmtPortsLoopback
The TestMgmtPortsLoopback test sends a packet from the inband port of the supervisor to the Firewall or NAM service module to verify the health of the backplane ports. The packet is looped back to the supervisor in hardware. If the packet does not return from the supervisor, the service application is queried for the status of the packet and depending on the action suggested by the service module, a syslog message is displayed and the card is reset. The TestMgmtPortsLoopback test runs every 30 seconds.
Table A-7 TestMgmtPortsLoopback Test Attributes
Description Nondisruptive. Do not disable. If the failure is isolated to the firewall module, then a syslog is printed indicating which port failed the test. If the test fails due to any other datapath issue for 10 consecutive times, the linecard is reset. If the test fails persistently, the module is powered down. On.
Default
A-5
Table A-7
TestDataPortLoopback
The TestDataPortLoopback test sends a packet from the inband port of the supervisor to the data port on the Firewall or NAM service module to verify the data packet path. The packet is looped back to the supervisor in hardware. If the packet does not return from the supervisor, hardware counters are polled to isolate the faulty path. The TestDataPortLoopback test runs every 45 seconds.
Table A-8 TestDataPortLoopback Test Attributes
Description Nondisruptive. Do not disable. If the test fails for 10 consecutive times, the linecard is reset. If the test fails persistently, the module is powered down. On. 12.2(33)SXJ. None. Bennu and NAM service modules.
Per-Port Tests
The per-port tests consist of the following tests:
TestNonDisruptiveLoopback, page A-7 TestLoopback, page A-7 TestActiveToStandbyLoopback, page A-8 TestUnusedPortLoopback, page A-8 TestTransceiverIntegrity, page A-9 TestNetflowInlineRewrite, page A-9 TestPortTxMonitoring, page A-10 TestSnrMonitoring, page A-10 TestDCPLoopback, page A-11 TestCCPLoopback, page A-11 TestNPLoopback, page A-12 TestMediaLoopback, page A-13
A-6
OL-13013-06
Appendix A
TestNonDisruptiveLoopback
The TestNonDisruptiveLoopback test verifies the data path between the supervisor engine and the network ports of a module. In this test, a Layer 2 packet is flooded onto VLAN that contains a group of test ports. The test port group consists of one port per port ASIC channel. Each port in the test port group nondisruptively loops back the packet and directs it back to the supervisor engines inband port. The ports in the test port group are tested in parallel.
Table A-9 TestNonDisruptiveLoopback Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(18)SXF. Error disable a port after 10 consecutive failures. Error disable a channel if all of its ports failed the test in one test cycle. Reset the module after a failure of all channels. WS-X6148-FE-SFP, WS-X6148A-GE-TX and WS-X6148A-RJ-45.
Hardware support
TestLoopback
The TestLoopback test verifies the data path between the supervisor engine and the network ports of a module. In this test, a Layer 2 packet is flooded onto a VLAN that consists of only the test port and the supervisor engines inband port. The packet loops back in the port and returns to the supervisor engine on that same VLAN.
Table A-10 TestLoopback Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. Runs at bootup or after online insertion and removal (OIR). 12.1(13)E, 12.2(14)SX. Error disable a port if the loopback test fails on the port. Reset the module if all of the ports fail. All modules including supervisor engines.
A-7
TestActiveToStandbyLoopback
The TestActiveToStandbyLoopback test verifies the data path between the active supervisor engine and the network ports of the standby supervisor engine. In this test, a Layer 2 packet is flooded onto a VLAN that consists of only the test port and the supervisor engines inband port. The test packets are looped back in the targeted port and are flooded back onto the bus with only the active supervisor enginess inband port listening in on the flooded VLAN.
Table A-11 TestActiveToStandbyLoopback Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of loopback port (for example, Spanning Tree Protocol). Schedule during downtime. Runs at bootup or after OIR. 12.1(13)E, 12.2(14)SX. Error disable a port if the loopback test fails on the port. Reset the supervisor engine if all of the ports fail. Standby supervisor engine only.
TestUnusedPortLoopback
The TestUnusedPortLoopback test verifies the data path between the supervisor engine and the network ports of a module in the runtime periodically. In this test, a Layer 2 packet is flooded onto the VLAN associated with the test port and the supervisor engine inband port only. The packet loops back in the port and returns to the supervisor engine on the same VLAN. It's similar to TestLoopback but only runs on unused (admin down) network ports and only one unused port per port ASIC. This test substitutes the lack of nondisruptive loopback test in current ASICs and runs every 60 seconds.
Table A-12 TestUnusedPortLoopback Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes to maintain accuracy. On. 12.2(33)SXH
A-8
OL-13013-06
Appendix A
Table A-12
Description Display a syslog message indicating the port(s) that failed. For modules other than supervisor engines, if all port groups fail (for example, at least one port per port ASIC fails more than the failure threshold for all port ASICs), the default action is to reset the module and power down the module after two resets. All modules including supervisor engines.
Hardware support
TestTransceiverIntegrity
The TestTransceiverIntegrity test is a security test performed on the transceiver during transceiver online insertion and removal (OIR) or module bootup to make sure that the transceiver is supported.
Table A-13 TestTransceiverIntegrity Test Attributes
Description Nondisruptive. Not applicable. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Error disable the port. All modules with transceivers.
TestNetflowInlineRewrite
The TestNetflowInlineRewrite test verifies the NetFlow lookup operation, the ACL permit and deny functionality, and the inline rewrite capabilities of the port ASIC. The test packet will undergo a NetFlow table lookup to obtain the rewrite information. The VLAN and the source and destination MAC addresses are rewritten when the packet reaches the targeted port.
Table A-14 TestNetflowInlineRewrite Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on configuration of loopback port (for example, Spanning Tree Protocol). Schedule during downtime. Run this test during bootup only. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX.
A-9
Table A-14
Description None. See the system message guide for more information. All modules including supervisor engines.
TestPortTxMonitoring
The test polls the transmit counters on each port periodically and displays a syslog and error disables the port if no activity is seen for the configured time interval and failure threshold. You configure the time interval and threshold by entering the diagnostic monitor interval and diagnostic monitor threshold commands. The test does not source any packets, but leverages the CDP protocol that transmits packets periodically. If CDP is disabled, the polling for that port is skipped. The test runs every 75 seconds and the failure threshold is set to 5 by default.
Table A-15 TestPortTxMonitoring Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes. On. 12.2(33)SXH. Display a syslog message indicating the port(s) that failed. Error disable the port(s) that failed. All modules including the supervisor engines.
TestSnrMonitoring
The TestSnrMonitoring test monitors the health of the WS-X6716-10GT-3C and WS-X6716-10GT-3CXL linecards. The test is added to the WS-X6716-10GT-3C and WS-X6716-10GT-3CXL linecards for standalone and VSS (Virtual Switching Systems) setups. The SNR (signal-to-noise ratio) margin for a port varies between 12.7 dB to +12.7 dB. The test uses the following two threshold levels to compare SNR:
When the SNR value drops below the minor threshold, the test logs a minor warning message. When the SNR value drops below the major threshold, the test logs a major warning message. Similarly, recovery messages are logged when SNR recovers the two threshold levels. The default interval for the test is 30 seconds and can be configured to as low as 10 seconds for faster monitoring. The TestSnrMonitoring is not a bootup test and cannot be run on demand.
A-10
OL-13013-06
Appendix A
Table A-16
TestDCPLoopback
The TestDCPLoopback test checks the data plane data path. The TestDCPLoopback test sends an online diagnostics packet from the supervisor engine to data ports on the Wireless Services Module (WiSM2). The TestDCPLoopback test checks whether the test packet loops back. If the test fails, a syslog message is displayed to indicate the error. The TestDCPLoopback test also can be run as health monitoring, on-demand, and scheduled tests.
Table A-17 TestDCPLoopback Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. A syslog message is displayed after five consecutive failures. WS-SVC-WISM2-K9.
TestCCPLoopback
The TestCCPLoopback test checks the control plane data path. The TestCCPLoopback test sends an online diagnostics packet from the supervisor engine to service or high availability port on the Wireless Services Module (WiSM2). The TestCCPLoopback checks whether the test packet loops back. If the test fails, a syslog message is displayed to indicate the error. The TestCCPLoopback test also can be run as health monitoring, on-demand, and scheduled tests.
Table A-18 TestCCPLoopback Test Attributes
A-11
Table A-18
Description 12.2(33)SXJ. A syslog message is displayed after five consecutive failures. WS-SVC-WISM2-K9.
TestNPLoopback
The TestNPLoopback test checks the data path of the ACE30 module for data path errors. The TestNPLoopback test runs at bootup, and the default configuration is a health-monitoring test that runs every 15 seconds. If TestNPLoopback fails, an SCP (Switch-module Configuration Protocol) message is sent to the ACE30 module indicating which network processors have failed. Upon receipt of the SCP message, ACE30 will take corrective action. If the TestNPLoopback test fails for ten consecutive times, the ACE30 module is reset.
Table A-19 TestNPLoopback Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. A syslog message is displayed to inform the ACE30 about the port(s) that failed the test on the failure code. Depending on the failure code, the ACE30 decides whether to take corrective action or not. The suggested action for ACE30 is to collect core dumps from all network processors and reset the ACE30 module. ACE30-MOD-K9.
Hardware support
A-12
OL-13013-06
Appendix A
TestMediaLoopback
The TestMediaLoopback test verifies the data path of MediaNet-like traffic. Index direct UDP packets are sent out to the MediaNet interface under test. The packets are looped back and forwarded to the inband port of the linecard.
Table A-20 TestMediaLoopback Test Attributes
Description Disruptive. Do not disable. Off. 12.2(33)SXJ. None. See the system message guide for more information. All C5 linecards supporting MediaNet.
TestNewIndexLearn, page A-13 TestDontConditionalLearn, page A-14 TestBadBpduTrap, page A-14 TestMatchCapture, page A-15 TestStaticEntry, page A-15
TestNewIndexLearn
The TestNewIndexLearn test is a combination of the TestNewLearn and the TestIndexLearn tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-16.
Table A-21 TestNewIndexLearn Test Attributes
Description Nondisruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX.
Default Release
A-13
Table A-21
Description None. See the system message guide for more information. Supervisor engines only.
TestDontConditionalLearn
The TestDontConditionalLearn test is a combination of the TestDontLearn and the TestConditionalLearn tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-16.
Table A-22 TestDontConditionalLearn Test Attributes
Description Nondisruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
TestBadBpduTrap
The TestBadBpduTrap test is a combination of the TestTrap and the TestBadBpdu tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-16.
Table A-23 TestBadBpduTrap Test Attributes
Description Disruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
A-14
OL-13013-06
Appendix A
TestMatchCapture
The TestMatchCapture test is a combination of the TestProtocolMatchChannel and the TestCapture tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-16.
Table A-24 TestMatchCapture Test Attributes
Description Disruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
TestStaticEntry
The TestStaticEntry test verifies that static entries are populated in the Layer 2 MAC address table. This functionality is verified during diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-25 TestStaticEntry Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
Recommendation
A-15
TestDontLearn, page A-16 TestNewLearn, page A-16 TestIndexLearn, page A-17 TestConditionalLearn, page A-18 TestTrap, page A-18 TestBadBpdu, page A-19 TestProtocolMatchChannel, page A-19 TestCapture, page A-20 TestStaticEntry, page A-20
TestDontLearn
The TestDontLearn test verifies that new source MAC addresses are not populated in the MAC address table when they should not be learned. This test verifies that the don't learn feature of the Layer 2 forwarding engine is working properly. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine inband port through the switch fabric and looped back from one of the ports on the DFC-enabled module. The don't learn feature is verified during diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-26 TestDontLearn Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestNewLearn
The TestNewLearn test verifies the Layer 2 source MAC address learning functionality of the Layer 2 forwarding engine. For supervisor engines, a diagnostic packet is sent from the supervisor engine inband port to verify that the Layer 2 forwarding engine is learning the new source MAC address from the diagnostic packet. For DFC-enabled modules, a diagnostic packet is sent from the supervisor engine
A-16
OL-13013-06
Appendix A
inband port through the switch fabric and looped backed from one of the ports on the DFC-enabled module. The Layer 2 learning functionality is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-27 TestNewLearn Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestIndexLearn
The TestIndexLearn test ensures that existing MAC address table entries can be updated. This test verifies the Index Learn feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engine Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Index Learn feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-28 TestIndexLearn Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
A-17
TestConditionalLearn
The TestConditionalLearn test verifies the ability to learn a Layer 2 source MAC address under specific conditions. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engine Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Conditional Learn feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-29 TestConditionalLearn Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestTrap
The TestTrap test verifies the ability to trap or redirect packets to the switch processor. This test verifies that the Trap feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Trap feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-30 TestTrap Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
A-18
OL-13013-06
Appendix A
TestBadBpdu
The TestBadBpdu test verifies the ability to trap or redirect packets to the switch processor. This test verifies that the Trap feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The BPDU feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-31 TestBadBpdu Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestProtocolMatchChannel
The TestProtocolMatchChannel test verifies the ability to match specific Layer 2 protocols in the Layer 2 forwarding engine. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Match feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-32 TestProtocolMatchChannel Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
A-19
TestCapture
The TestCapture test verifies that the capture feature of Layer 2 forwarding engine is working properly. The capture functionality is used for multicast replication. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Capture feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-33 TestCapture Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestStaticEntry
The TestStaticEntry test verifies the ability to populate static entries in the Layer 2 MAC address table. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Static Entry feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-34 TestStaticEntry Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
A-20
OL-13013-06
Appendix A
TestFibDevices, page A-21 TestIPv4FibShortcut, page A-22 TestIPv6FibShortcut, page A-22 TestMPLSFibShortcut, page A-23 TestNATFibShortcut, page A-23 TestL3Capture2, page A-24 TestAclPermit, page A-24 TestAclDeny, page A-25 TestQoS, page A-26
TestFibDevices
The TestFibDevices test verifies whether the FIB TCAM and adjacency devices are functional. One FIB entry is installed on each FIB TCAM device. A diagnostic packet is sent to make sure that the diagnostic packet is switched by the FIB TCAM entry installed on the TCAM device. This is not an exhaustive TCAM device test; only one entry is installed on each TCAM device.
Note
Compared to the IPv4FibShortcut and IPv6FibShortcut tests, this test tests all FIB and adjacency devices using IPv4 or IPv6 packets, depending on your configuration.
Table A-35
Description Nondisruptive. Run this test on-demand to verify the Layer 3 forwarding functionality if you experience problems with the routing capability. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-21
TestIPv4FibShortcut
The TestIPv4FibShortcut test verifies the IPV4 FIB forwarding of the Layer 3 forwarding engine is working properly. One diagnostic IPV4 FIB and adjacency entry is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table A-36 TestIPv4FibShortcut Test Attributes
Description Nondisruptive. Run this test on-demand to verify the Layer 3 forwarding functionality if you experience problems with the routing capability. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestIPv6FibShortcut
The TestIPv6FibShortcut test verifies that the IPV6 FIB forwarding of the Layer 3 forwarding engine is working properly. One diagnostic IPV6 FIB and adjacency entry is installed and a diagnostic IPv6 packet is sent to make sure the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table A-37 TestIPv6FibShortcut Test Attributes
Description Nondisruptive. Run this test on-demand to verify the Layer 3 forwarding functionality if you experience problems with the routing capability. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-22
OL-13013-06
Appendix A
TestMPLSFibShortcut
The TestMPLSFibShortcut test verifies that the MPLS forwarding of the Layer 3 forwarding engine is working properly. One diagnostic MPLS FIB and adjacency entry is installed and a diagnostic MPLS packet is sent to make sure that the diagnostic packet is forwarded according to the MPLS label from the adjacency entry.
Table A-38 TestMPLSFibShortcut Test Attributes
Description Nondisruptive. This test can also be used as a health-monitoring test. Use as a health-monitoring test if you are routing MPLS traffic. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestNATFibShortcut
The TestNATFibShortcut test verifies the ability to rewrite a packet based on the NAT adjacency information (rewrite destination IP address). One diagnostic NAT FIB and adjacency entry is installed and the diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to the rewritten IP address.
Table A-39 TestNATFibShortcut Test Attributes
Description Nondisruptive. This test can also be used as a health-monitoring test. Use as a health-monitoring test if the destination IP address is being rewritten (for example, if you are using NAT). This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-23
TestL3Capture2
The TestL3Capture2 test verifies that the Layer 3 capture (capture 2) feature of the Layer 3 forwarding engine is working properly. This capture feature is used for ACL logging and VACL logging. One diagnostic FIB and adjacency entry with a capture 2 bit set is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to the capture bit information.
Table A-40 TestL3Capture2 Test Attributes
Description Disruptive. This test can not be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestAclPermit
The TestAclPermit test verifies that the ACL permit functionality is working properly. An ACL entry permitting a specific diagnostics packet is installed in the ACL TCAM. The corresponding diagnostic packet is sent from the supervisor engine and looked up by the Layer 3 forwarding engine to make sure that it hits the ACL TCAM entry and gets permitted and forwarded appropriately.
Table A-41 TestACLPermit Test Attributes
Description Disruptive. This test can not be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-24
OL-13013-06
Appendix A
TestAclDeny
The TestAclDeny test verifies that the ACL deny feature of the Layer 2 and Layer 3 forwarding engine is working properly. The test uses different ACL deny scenarios such as input, output, Layer 2 redirect, Layer 3 redirect, and Layer 3 bridges to determine whether or not the ACL deny feature is working properly.
Table A-42 TestACLDeny Test Attributes
Description Disruptive. Do not disable. On. 12.1(13)E, 12.2(14)SX. Automatic ASIC reset for recovery. Supervisor engines and DFC-enabled modules.
TestNetflowShortcut
The TestNetflowShortcut test verifies that the NetFlow forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic NetFlow entry and adjacency entry is installed, and a diagnostic packet is sent to make sure it is forwarded according to the rewritten MAC and VLAN information.
Table A-43 TestNetflowShortcut Test Attributes
Description Disruptive for looped back ports. The disruption is 500 ms. Run this test on-demand if you suspect that NetFlow is not working properly. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-25
TestQoS
The TestQoS test verifies whether or not the QoS input and output TCAM is functional by programming the QoS input and output TCAM so that the ToS value of the diagnostic packet is changed to reflect either input or output.
Table A-44 TestQoS Test Attributes
Description Disruptive for looped back ports. The disruption is 500 ms. Schedule during downtime. This test runs by default during bootup or after a reset or OIR 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestFibDevices, page A-26 TestIPv4FibShortcut, page A-27 TestIPv6FibShortcut, page A-28 TestMPLSFibShortcut, page A-28 TestNATFibShortcut, page A-29 TestL3Capture2, page A-29 TestAclPermit, page A-30 TestAclDeny, page A-30 TestQoS, page A-31 TestNetflowShortcut, page A-31 TestAclFpgaMonitor, page A-32
TestFibDevices
The TestFibDevices test verifies that the FIB TCAM and adjacency devices are functional. One FIB entry is installed on each FIBTCAM device and a diagnostic packet is sent to make sure that the diagnostic packet is switched by the FIB TCAM entry installed on the TCAM device. This is not an exhaustive TCAM device test. Only one entry is installed on each TCAM device.
Note
Compared to the IPv4FibShortcut and IPv6FibShortcut tests, the TestFibDevices test tests all FIB and adjacency devices using IPv4 or IPv6 packets, depending on your configuration.
A-26
OL-13013-06
Appendix A
Table A-45
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestIPv4FibShortcut
The TestIPv4FibShortcut test verifies that the IPv4 FIB forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic IPv4 FIB and adjacency entry is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table A-46 TestIPv4FibShortcut Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-27
TestIPv6FibShortcut
The TestIPv6FibShortcut test verifies that the IPv6 FIB forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic IPv6 FIB and adjacency entry is installed and a diagnostic IPv6 packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table A-47 TestIPv6FibShortcut Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestMPLSFibShortcut
The TestMPLSFibShortcut test verifies that the MPLS forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic MPLS FIB and adjacency entry is installed and a diagnostic MPLS packet is sent to make sure that the diagnostic packet is forwarded using the MPLS label from the adjacency entry.
Table A-48 TestMPLSFibShortcut Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-28
OL-13013-06
Appendix A
TestNATFibShortcut
The TestNATFibShortcut test verifies the ability to rewrite a packet based on NAT adjacency information, such as the rewrite destination IP address. One diagnostic NAT FIB and adjacency entry is installed and a diagnostic packet is sent to make sure the diagnostic packet is forwarded according to the rewritten IP address.
Table A-49 TestNATFibShortcut Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestL3Capture2
The TestL3Capture2 test verifies that the Layer 3 capture (capture 2) feature of the Layer 3 forwarding engine is working properly. This capture feature is used for ACL logging and VACL logging. One diagnostic FIB and adjacency entry with a capture 2-bit set is installed, and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to capture bit information.
Table A-50 TestL3Capture2 Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-29
TestAclPermit
The TestAclPermit test verifies that the ACL permit functionality is working properly. An ACL entry permitting a specific diagnostics packet is installed in the ACL TCAM. The corresponding diagnostic packet is sent from the supervisor engine and is looked up by the Layer 3 forwarding engine to make sure it hits the ACL TCAM entry and gets permitted and forwarded correctly.
Table A-51 TestACLPermit Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestAclDeny
The TestAclDeny test verifies that the ACL deny feature of the Layer 2 and Layer 3 forwarding engine is working properly. The test uses different ACL deny scenarios such as input and output Layer 2 redirect, Layer 3 redirect, and Layer 3 bridges.
Table A-52 TestACLDeny Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime if you are using ACLs. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-30
OL-13013-06
Appendix A
TestQoS
The TestQoS test verifies whether or not the QoS input and output TCAM is functional by programming the QoS input and output TCAM so that the ToS value of the diagnostic packet is changed to reflect either input or output.
Table A-53 TestQoS Test Attributes
Description Disruptive for looped-back ports. The disruption is typically less than one second. Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestNetflowShortcut
The TestNetFlowShortcut test verifies that the NetFlow forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic NetFlow entry and adjacency entry is installed and a diagnostic packet is sent to make sure it is forwarded according to the rewritten MAC and VLAN information.
Table A-54 TestNetflowShortcut Test Attributes
Description Disruptive for looped-back ports. Disruption is typically less than one second. Run this test on-demand if you suspect that NetFlow is not working properly. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-31
TestAclFpgaMonitor
The TestAclFpgaMonitor test monitors the ACL FPGA for an invalid ACL TCAM reply status in the following linecards: WS-X6704-10GE, WS-X6724-SFP, WS-X6748-SFP, WS-X6748-GE-TX and takes recovery action if an invalid reply is detected.
Table A-55 TestAclFpgaMonitor Test Attributes
Description NonDisruptive. Do not disable. On. 12.2(33)SXI4, 12.2(18)SXF17a. Reset the linecard and optionally admin-down all the ports on the linecard. DFC-equipped WS-X6748-GE-TX, WS-X6704-10GE, WS-X6724-SFP, WS-X6748-SFP modules with WS-F6700-DFC3B or WS-F6700-DFC3BXL DFC.
TestL3VlanMet
The TestL3VlanMet test verifies that the multicast functionality of the replication engine is working properly. The replication engine is configured to perform multicast replication of a diagnostic packet onto two different VLANs. After the diagnostic packet is sent out from the supervisor engines inband port, the test verifies that two packets are received back in the inband port on the two VLANs configured in the replication engine.
Table A-56 TestL3VlanMet Test Attributes
Description Disruptive for DFC-equipped modules. Disruption is typically less than one second on looped-back ports. Run this test on-demand to test the multicast replication abilities of the replication engine. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX.
A-32
OL-13013-06
Appendix A
Table A-56
Description None. See the system message guide for more information. Supervisor engines and WS-65xx, WS-67xx, and WS-68xx modules.
TestIngressSpan
The TestIngressSpan test ensures that the port ASIC is able to tag packets for ingress SPAN. This test also verifies that the ingress SPAN operation of the rewrite engine for both SPAN queues is working properly.
Table A-57 TestIngressSpan Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive for both SPAN sessions. Also disruptive for the loopback port on modules. Duration of the disruption depends on the configuration of the loopback port (for example, Spanning Tree Protocol). Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and WS-65xx and WS-67xx modules.
TestEgressSpan
The TestEgressSpan test verifies that the egress SPAN replication functionality of the rewrite engine for both SPAN queues is working properly.
Table A-58 TestEgressSpan Test Attributes
Description Disruptive for both SPAN sessions. Disruption is typically less than one second. Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and WS-65xx and WS-67xx modules.
A-33
Fabric Tests
These are the Fabric tests:
TestFabricSnakeForward, page A-34 TestFabricSnakeBackward, page A-34 TestSynchedFabChannel, page A-35 TestFabricCh0Health, page A-36 TestFabricCh1Health, page A-36
TestFabricSnakeForward
The TestFabricSnakeForward test consists of two test cases: the internal snake test and the external snake test. The internal snake test generates the test packets inside the fabric ASIC and the test data path is limited so that it stays inside the fabric ASIC. The external snake test generates the test packet using the supervisor engine inband port; the test data path involves the port ASIC, the rewrite engine ASIC inside the supervisor engine, and the fabric ASIC. Whether or not the supervisor engine local channel is synchronized to the fabric ASIC determines which test is used. If it is synchronized, the external snake test is used; if it is not, the internal snake test is used. For both tests, only the channels that are not synchronized to any modules are involved in the test. The Forward direction indicates that the snaking direction is from the low-numbered channel to the high-numbered channel.
Table A-59 TestFabricSnakeForward Test Attributes
Description Nondisruptive. Run on-demand. This test can result in high CPU utilization. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Supervisor engines crash to ROMMON; SFMs reset. Supervisor Engine 720 and SFM.
TestFabricSnakeBackward
The TestFabricSnakeBackward test consists of two test cases: the internal snake test and the external snake test. The internal snake test generates the test packets inside the fabric ASIC, and the test data path is limited so that it stays inside the fabric ASIC. The external snake test generates the test packet using the supervisor engine inband port and the test data path involves the port ASIC, the rewrite engine ASIC inside the supervisor engine, and the fabric ASIC. Whether or not the supervisor engine local channel is synchronized to the fabric ASIC determines which test is used. If it is synchronized, the external snake
A-34
OL-13013-06
Appendix A
test is used; if it is not, internal snake test is used. For both tests, only the channels that are not synchronized to any modules are involved in the test. The backward direction indicates that the snaking direction is from the high-numbered channel to the low-numbered channel.
Table A-60 TestFabricSnakeBackward Test Attributes
Description Nondisruptive. Run on-demand. This test can result in high CPU utilization. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Supervisor engines crash to ROMMON; SFMs reset. Supervisor Engine 720 and SFM.
TestSynchedFabChannel
The TestSynchedFabChannel test periodically checks the fabric synchronization status for both the module and the fabric. This test is available only for fabric-enabled modules. This test is not a packet-switching test so it does not involve the data path. This test sends an SCP control message to the module and fabric to query the synchronization status.
Table A-61 TestSynchedFabChannel Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after five consecutive failures. Three consecutive reset cycles results in the module powering down. A fabric switchover may be triggered, depending on the type of failure. All fabric-enabled modules.
Hardware support
A-35
TestFabricCh0Health
The TestFabricCh0Health test constantly monitors the health of the ingress and egress data paths for fabric channel 0 on 10-gigabit modules. The test runs every five seconds. Ten consecutive failures are treated as fatal and the module resets; three consecutive reset cycles may result in a fabric switchover.
Table A-62 TestFabricSCh0Health Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after 10 consecutive failures. Three consecutive resets powers down the module. WS-X6704-10GE and WS-6702-10GE.
TestFabricCh1Health
The TestFabricCh1Health test constantly monitors the health of the ingress and egress data paths for fabric channel 1 on 10-gigabit modules. The test runs every five seconds. Ten consecutive failures are treated as fatal and the module resets; three consecutive reset cycles may result in a fabric switchover.
Table A-63 TestFabricCh1Health Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after 10 consecutive failures. Three consecutive failures resets powers down the module. WS-X6704-10GE module.
A-36
OL-13013-06
Appendix A
Note
Because the supervisor engine must be rebooted after running memory tests, run memory tests on the other modules before running them on the supervisor engine. For more information about running on-demand online diagnostic tests see the Configuring On-Demand Online Diagnostics section on page 14-3.
TestFibTcamSSRAM
The TestFibTcamSSRAM test checks the FIB TCAM and Layer 3 Adjacency SSRAM memory.
Table A-64 TestFibTcamSSRAM Test Attributes
Description Disruptive. Disruption is several hours. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.1(20)E, 12.2(14)SX, 12.2(17a)SX. Not applicable. All modules including supervisor engines.
TestAsicMemory
The TestAsicMemory test uses an algorithm to test the memory on a module.
Table A-65 TestAsicMemory Test Attributes
Description Disruptive. Disruption is approximately one hour. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(17a)SX. Not applicable. All modules including supervisor engines.
A-37
TestAclQosTcam
The TestAclQosTcam test tests all the bits and checks the location of both ACL and QOS TCAMs on the PFC. It is not supported on the PFC3A.
Table A-66 TestAclQosTcam Test Attributes
Description Disruptive. Disruption is approximately one hour. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
TestNetflowTcam
The TestNetflowTcam test tests all the bits and checks the location of the Netflow TCAM.
Table A-67 TestNetflowTcam Test Attributes
Description Disruptive. Disruption is several minutes and can vary depending on the version of the PFC. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
A-38
OL-13013-06
Appendix A
TestQoSTcam
The TestQoSTcam test performs exhaustive memory tests for QoS TCAM devices.
Table A-68 TestQoSTcam Test Attributes
Description Disruptive. Disruption is several minutes and can vary depending on the version of the PFC. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
TestIPSecClearPkt
The TestIPSecClearPkt test sends a packet through the switch fabric or bus from the supervisor engine inband port through to the crypto engine. The packet is sent back without encryption from the crypto engine to the supervisor engine in-band port. The packet is checked to verify that the encryption is not done and that the packet data fields are reserved. The Layer 2 lookup drives the packet between the supervisor in-band port and the crypto engine.
Table A-69 TestIPSecClearPkt Test Attributes
Description Nondisruptive. Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.2(18)SXE2.2.
A-39
Table A-69
Description None. See the system message guide for more information. VPN service module.
TestHapiEchoPkt
The TestHapiEchoPkt test sends a Hapi Echo packet to the crypto engine using the control path. After the Hapi Echo packet is sent to the crypto engine, it is echoed back from the crypto engine. The packet is sent from the supervisor engine inband port to the crypto engine using index-direct and is sent back using broadcast to a diagnostic VLAN.
Table A-70 TestHapiEchoPkt Test Attributes
Description Disruptive. Run this test on-demand. This test cannot be run from on-demand CLI. On. 12.2(18)SXE2. None. See the system message guide for more information. VPN service module.
TestIPSecEncryptDecryptPkt
The TestIPSecEncryptDecryptPkt test checks the encryption functionality by exchanging a packet between the supervisor engine in-band port and the crypto engine of the IPsec services modules (WS-SVC-IPSEC, SPA-IPSEC) using the switch fabric or bus (whichever is applicable). After several exchanges, the packet is checked to verify that the original data is preserved after the encryption and decryption process performed by the crypto engine. The Layer 2 lookup drives the packet between the supervisor in-band port and the crypto engine.
Table A-71 TestIPSecEncryptDecryptPkt Test Attributes
Description Nondisruptive. Test runs every minute by default. This test can only be run at bootup. This test runs by default during bootup or after a reset or OIR. 12.2(18)SXE2.2. None. See the system message guide for more information. VPN services module.
A-40
OL-13013-06
Appendix A
Stress Tests
The stress tests consist of the following tests:
TestTrafficStress
The TestTrafficStress test stress tests the switch and the installed modules by configuring all of the ports on the modules into pairs, which then pass packets between each other. After allowing the packets to pass through the switch for a predetermined period, the test verifies that the packets are not dropped.
Table A-72 TestTrafficStress Test Attributes
Description Disruptive. Disruption is several minutes. Use this test to qualify hardware before installing it in your network. Off. 12.2(18)SXF. Not applicable. Supervisor Engine 720 and Supervisor Engine 32.
TestEobcStressPing
The TestEobcStressPing test stress tests a modules EOBC link with the supervisor engine. The test is started when the supervisor engine initiates a number of sweep-ping processes (the default is one). The sweep-ping process pings the module with 20,000 SCP-ping packets. The test passes if all 20,000 packets respond before each packet-ping timeout, which is two seconds. If unsuccessful, the test allows five retries to account for traffic bursts on the EOBC bus during the test.
Table A-73 TestEobcStressPing Test Attributes
Description Disruptive. Disruption is several minutes. Use this test to qualify hardware before installing it in your network. Off. 12.2(18)SXD. Not applicable. Supervisor Engine 720 and Supervisor Engine 32.
A-41
TestMicroburst
The TestMicroburst test monitors packet microbursts in the port ASICs and logs them to SEA unless consecutive failures reach the threshold.
Table A-74 TestMicroburst Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. Not applicable. C5 linecards that support MediaNet.
The TestFabricCh0Health and TestFabricCh1Health tests are also considered critical recovery tests. See the Fabric Tests section on page A-34 for a description of these tests.
TestL3HealthMonitoring
The TestL3HealthMonitoring test triggers a set of diagnostic tests involving IPv4 and IPv6 packet switching on a local DFC whenever the system tries to self-recover from a detected hardware fault. The tests shut down the front panel port (usually port 1) for testing purposes. If the diagnostic tests are not passing, it is an indication that the hardware fault cannot be fixed and a self-recovery sequence will be applied again
Table A-75 TestL3HealthMonitoring Test Attributes
Attribute Disruptive/Nondisruptive
Description Disruptive. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). Forwarding and port functions are disrupted during the test. Do not disable. Off. 12.2(14)SX.
A-42
OL-13013-06
Appendix A
Table A-75
TestTxPathMonitoring
The TestTxPathMonitoring test sends index-directed packets periodically to each port on the Supervisor Engine 720 and WS-X67xx series modules to verify ASIC synchronization and correct any related problems. The test runs every two seconds.
Table A-76 TestTxPathMonitoring Test Attributes
Description Nondisruptive. Do not change the default settings. On. 12.2(14)SX. Not applicable (self-recovering). Supervisor Engine 720 and WS-67xx series modules.
TestSynchedFabChannel
The TestSynchedFabChannel test periodically checks the fabric synchronization status for both the module and the fabric. This test is available only for fabric-enabled modules. This test is not a packet-switching test so it does not involve the data path. This test sends an SCP control message to the module and fabric to query the synchronization status.
Table A-77 TestSynchedFabChannel Test Attributes
Description Nondisruptive. Do not turn off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. All fabric-enabled modules.
A-43
General Tests
The general tests consist of the following tests:
ScheduleSwitchover
The ScheduleSwitchover test allows you to trigger a switchover at any time using the online diagnostics scheduling capability.
Table A-78 ScheduleSwitchover Test Attributes
Description Disruptive. Schedule this test during downtime to test the ability of the standby supervisor engine to take over after a switchover. Off. 12.2(17B)SXA None Supervisor engines only.
TestFirmwareDiagStatus
The TestFirmwareDiagStatus test displays the results of the power-on diagnostic tests run by the firmware during the module bootup.
Table A-79 TestFirmwareDiagStatus Test Attributes
Description Nondisruptive. This test can only be run at bootup. This test runs by default during bootup or after a reset or OIR 12.2(18)SXD None. See the system message guide. All modules, including supervisor engines.
A-44
OL-13013-06
Appendix A
TestCFRW
The TestCFRW test verifies the CompactFlash disk or disks on the supervisor engine. This test is performed during system boot-up or whenever a disk is inserted. A 128-byte temporary file is written to each disk present in the slot and read back. The content read back is checked and the temporary file is deleted. You can also execute this test from the CLI.
Table A-80 TestCFRW Test Attributes
Description Nondisruptive. Do not disable. No traffic is affected. On. 12.2(33)SXH. Format or replace the failed CompactFlash. External CompactFlash on the active and the standby Supervisor Engine 720 and Supervisor Engine 32.
Tip
For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page: http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
A-45
A-46
OL-13013-06