Online Diagnostic Tests
This appendix describes the online diagnostic tests and provides recommendations for how to use them.
The online diagnostic tests are included in these categories:
For information about configuring online diagnostic tests refer to Chapter42, “Configuring Online Diagnostics”
Global Health-Monitoring Tests
The global health monitoring tests consist of the following tests:
TestSPRPInbandPing
TestMacNotification
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.
Table A-1 TestSPRPInbandPing Test Attributes
|
|
|
Nondisruptive. |
|
Do not disable. Test is automatically disabled during CPU-usage spikes in order to maintain accuracy. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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-2 TestScratchRegister Test Attributes
|
|
|
Nondisruptive. |
|
Do not disable. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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-3 TestMacNotification Test Attributes
|
|
|
Nondisruptive. |
|
Do not disable. |
|
On. |
|
12.2(33)SRA and later releases. |
|
Reset the module. After the module has ten consecutive failures or three consecutive resets, it powers down. |
|
DFC-equipped modules. |
Per-Port Tests
The per-port tests consist of the following tests:
TestNonDisruptiveLoopback
TestLoopback
TestActiveToStandbyLoopback
TestTransceiverIntegrity
TestNetflowInlineRewrite
TestNonDisruptiveLoopback
The TestNonDisruptiveLoopback test verifies the data path between the supervisor engine and the network ports of a module. In this test, a Layer2 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 engine’s inband port. The ports in the test port group are tested in parallel.
Table A-4 TestNonDisruptiveLoopback Test Attributes
|
|
|
Nondisruptive. |
|
Do not disable. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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. |
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 engine’s inband port. The packet loops back in the port and returns to the supervisor engine on that same VLAN.
Table A-5 TestLoopback Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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. |
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 engine’s inband port. The test packets are looped back in the targeted port and are flooded back onto the bus with only the active supervisor engines’s inband port listening in on the flooded VLAN.
Table A-6 TestActiveToStandbyLoopback Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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. |
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-7 TestTransceiverIntegrity Test Attributes
|
|
|
Nondisruptive. |
|
Not applicable. |
|
This test runs by default during bootup or after a reset or OIR. |
|
12.2(33)SRA and later releases. |
|
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-8 TestNetflowInlineRewrite Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
All modules including supervisor engines. |
PFC Layer 2 Forwarding Engine Tests
The PFC Layer 2 Forwarding Engine tests consist of the following tests:
TestNewIndexLearn
TestDontConditionalLearn
TestBadBpduTrap
TestMatchCapture
TestStaticEntry
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.
Table A-9 TestNewIndexLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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.
Table A-10 TestDontConditionalLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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.
Table A-11 TestBadBpduTrap Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines only. |
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.
Table A-12 TestMatchCapture Test Attributes
|
|
|
Nondisruptive. |
|
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.2(33)SRA and later releases. |
|
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-13 TestStaticEntry Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
DFC Layer 2 Forwarding Engine Tests
The DFC Layer 2 Forwarding Engine tests consists of the following tests:
TestDontLearn
TestNewLearn
TestIndexLearn
TestConditionalLearn
TestTrap
TestBadBpdu
TestProtocolMatchChannel
TestCapture
TestStaticEntry
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-14 TestDontLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 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-15 TestNewLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 engine’s 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 engine’s 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-16 TestIndexLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
DFC-enabled modules. |
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 engine’s 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 engine’s 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-17 TestConditionalLearn Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 engine’s inband port and performs a packet lookup using the supervisor engine’s Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine’s 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-18 TestTrap Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
DFC-enabled modules. |
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 engine’s inband port and performs a packet lookup using the supervisor engine’s Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine’s 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-19 TestBadBpdu Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 engine’s inband port and performs a packet lookup using the supervisor engine’s Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine’s inband port through the switch fabric and looped back from one of the DFC ports. T he Match feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-20 TestProtocolMatchChannel Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
DFC-enabled modules. |
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 engine’s inband port and performs a packet lookup using the supervisor engine’s Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine’s 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-21 TestCapture Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 engine’s inband port and performs a packet lookup using the supervisor engine’s Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine’s 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-22 TestStaticEntry Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
DFC-enabled modules. |
PFC Layer 3 Forwarding Engine Tests
The PFC Layer 3 Forwarding Engine tests consists of the following tests:
TestFibDevices
TestIPv4FibShortcut
TestIPv6FibShortcut
TestMPLSFibShortcut
TestNATFibShortcut
TestL3Capture2
TestAclPermit
TestAclDeny
TestQoS
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-23 TestFibDevices Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
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-24 TestIPv4FibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-25 TestIPv6FibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
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-26 TestMPLSFibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-27 TestNATFibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 the capture bit information.
Table A-28 TestL3Capture2 Test Attributes
|
|
|
Nondisruptive. |
|
This test can also be used as a health-monitoring test. Use as a health-monitoring test if you are using ACL or VACL logging. |
|
This test runs by default during bootup or after a reset or OIR. |
|
12.2(33)SRA and later releases. |
|
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-29 TestACLPermit Test Attributes
|
|
|
Nondisruptive. |
|
This test can also be used as a health-monitoring test. Use as a health-monitoring test if you are using ACLs. |
|
This test runs by default during bootup or after a reset or OIR. |
|
12.2(33)SRA and later releases. |
|
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, 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-30 TestACLDeny Test Attributes
|
|
|
Nondisruptive. |
|
Do not disable. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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-31 TestNetflowShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
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-32 TestQoS Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
DFC Layer 3 Forwarding Engine Tests
The DFC Layer 3 Forwarding Engine tests consists of the following tests:
TestFibDevices
TestIPv4FibShortcut
TestIPv6FibShortcut
TestMPLSFibShortcut
TestNATFibShortcut
TestL3Capture2
TestAclPermit
TestAclDeny
TestQoS
TestNetflowShortcut
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.
Table A-33 TestFibDevices Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-34 TestIPv4FibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 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-35 TestIPv6FibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-36 TestMPLSFibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 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-37 TestNATFibShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-38 TestL3Capture2 Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 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-39 TestACLPermit Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-40 TestACLDeny Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
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-41 TestQoS Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-42 TestNetflowShortcut Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and DFC-enabled modules. |
Replication Engine Tests
The Replication Engine tests consists of the following tests:
TestL3VlanMet
TestIngressSpan
TestEgressSpan
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 engine’s 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-43 TestL3VlanMet Test Attributes
|
|
|
Nondisruptive for supervisor engines. 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.2(33)SRA and later releases. |
|
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-44 TestIngressSpan Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-45 TestEgressSpan Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
Supervisor engines and WS-65xx and WS-67xx modules. |
Fabric Tests
The Fabric tests consists of the following tests:
TestFabricSnakeForward
TestFabricSnakeBackward
TestSynchedFabChannel
TestFabricCh0Health
TestFabricCh1Health
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-46 TestFabricSnakeForward Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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 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-47 TestFabricSnakeBackward Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
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-48 TestSynchedFabChannel Test Attributes
|
|
|
Nondisruptive. |
|
Do not turn this test off. Use as a health-monitoring test. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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. |
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-49 TestFabricSCh0Health Test Attributes
|
|
|
Nondisruptive. |
|
Do not turn this test off. Use as a health-monitoring test. |
|
On. |
|
12.2(33)SRA and later releases. |
|
The module resets after 10 consecutive failures. Three consecutive resets powers down the module. Effective from 15.3(1)S1 release onwards, for ES+ line cards, a recovery mechanism is introduced for every two consecutive failure of the TestFabricCh0Health test. If the test fails even after 5 recovery patches or 10 consecutive failures, then the module is reloaded. |
|
WS-X6704-10GE and WS-6702-10GE. |
TestFabricCh1Health
The 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-50 TestFabricCh1Health Test Attributes
|
|
|
Nondisruptive. |
|
Do not turn this test off. Use as a health-monitoring test. |
|
On. |
|
12.2(33)SRA and later releases. |
|
The module resets after 10 consecutive failures. Three consecutive failures resets powers down the module. Effective from 15.3(1)S1 release onwards, for ES+ line cards, a recovery mechanism is introduced for every two consecutive failure of the TestFabricCh1Health test. If the test fails even after 5 recovery patches or 10 consecutive failures, then the module is reloaded. |
|
WS-X6704-10GE module. |
Exhaustive Memory Tests
The exhaustive memory tests include the following tests:
TestFibTcamSSRAM
TestAsicMemory
TestAclQosTcam
TestNetflowTcam
TestQoSTcam
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.
TestFibTcamSSRAM
The TestFibTcamSSRAM test checks the FIB TCAM and Layer 3 Adjacency SSRAM memory.
Table A-51 TestFibTcamSSRAM Test Attributes
|
|
|
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.2(33)SRA and later releases. |
|
Not applicable. |
|
All modules including supervisor engines. |
TestAsicMemory
The TestAsicMemory test uses an algorithm to test the memory on a module.
Table A-52 TestAsicMemory Test Attributes
|
|
|
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(33)SRA and later releases. |
|
Not applicable. |
|
All modules including supervisor engines. |
TestAclQosTcam
The TestAclQosTcam test tests all the bits and checks the location of both ACL and QOS TCAMs on the PFC3B, PFC3BXL, PFC3C, and PFC3CXL. It is not supported on the PFC3A.
Table A-53 TestAclQosTcam Test Attributes
|
|
|
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(33)SRA and later releases. |
|
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-54 TestNetflowTcam Test Attributes
|
|
|
Disruptive. Disruption is several minutes and can vary depending on the type of PFC you are testing. |
|
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(33)SRA and later releases. |
|
Not applicable. |
|
All modules including supervisor engines. |
TestQoSTcam
The TestQoSTcam test performs exhaustive memory tests for QoS TCAM devices.
Table A-55 TestQoSTcam Test Attributes
|
|
|
Disruptive. Disruption is several minutes and can vary depending on what type of PFC you are testing. |
|
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(33)SRA and later releases. |
|
Not applicable. |
|
All modules including supervisor engines. |
IPSEC Services Modules Tests
The IPSEC Services Modules Tests include the following tests:
TestIPSecClearPkt
TestHapiEchoPkt
TestIPSecEncryptDecryptPkt
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-56 TestIPSecClearPkt Test Attributes
|
|
|
Nondisruptive. |
|
Run this test on-demand. |
|
This test runs by default during bootup or after a reset or OIR. |
|
12.2(33)SRA and later releases. |
|
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-57 TestHapiEchoPkt Test Attributes
|
|
|
Disruptive. |
|
Run this test on-demand. This test cannot be run from on-demand CLI. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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-58 TestIPSecEncryptDecryptPkt Test Attributes
|
|
|
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(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
VPN services module. |
Stress Tests
The stress tests consist of the following tests:
TestTrafficStress
TestEobcStressPing
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-59 TestTrafficStress Test Attributes
|
|
|
Disruptive. Disruption is several minutes. |
|
Use this test to qualify hardware before installing it in your network. |
|
Off. |
|
12.2(33)SRA and later releases. |
|
Not applicable. |
|
Supervisor Engine 720 and Supervisor Engine 32. |
TestEobcStressPing
The TestEobcStressPing test stress tests a module’s 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-60 TestEobcStressPing Test Attributes
|
|
|
Disruptive. Disruption is several minutes. |
|
Use this test to qualify hardware before installing it in your network. |
|
Off. |
|
12.2(33)SRA and later releases. |
|
Not applicable. |
|
Supervisor Engine 720 and Supervisor Engine 32. |
Critical Recovery Tests
The critical recovery tests consist of the following tests:
The TestFabricCh0Health and TestFabricCh1Health tests are also considered critical recovery tests. See the “Fabric Tests” section 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-61 TestL3HealthMonitoring Test Attributes
|
|
|
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. |
|
On. |
|
12.2(33)SRA and later releases. |
|
Not applicable. |
|
DFC-equipped modules |
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-62 TestTxPathMonitoring Test Attributes
|
|
|
Nondisruptive. |
|
Do not change the default settings. |
|
On. |
|
12.2(33)SRA and later releases. |
|
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-63 TestSynchedFabChannel Test Attributes
|
|
|
Nondisruptive. |
|
Do not turn off. Use as a health-monitoring test. |
|
On. |
|
12.2(33)SRA and later releases. |
|
None. See the system message guide for more information. |
|
All fabric-enabled modules. |
General Tests
The general tests consist of the following tests:
ScheduleSwitchover
TestFirmwareDiagStatus
ScheduleSwitchover
The ScheduleSwitchover test allows you to trigger a switchover at any time using the online diagnostics scheduling capability.
Table A-64 ScheduleSwitchover Test Attributes
|
|
|
Disruptive. |
|
Schedule this test during downtime to test the ability of the standby supervisor engine to take over after a switchover. |
|
Off. |
|
12.2(33)SRA and later releases. |
|
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-65 TestFirmwareDiagStatus Test Attributes
|
|
|
Nondisruptive. |
|
This test can only be run at bootup. |
|
This test runs by default during bootup or after a reset or OIR |
|
12.2(33)SRA and later releases. |
|
None. See the system message guide. |
|
All modules, including supervisor engines. |