Release 15.4SY Supervisor Engine 2T Software Configuration Guide

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book

Results

Updated:
August 14, 2014

Chapter: Online Diagnostics

Online Diagnostics

note.gif

Note ●blank.gif For complete syntax and usage information for the commands used in this chapter, see these publications:

http://www.cisco.com/en/US/products/ps11846/prod_command_reference_list.html

  • Cisco IOS Release 15.4SY supports only Ethernet interfaces. Cisco IOS Release 15.4SY does not support any WAN features or commands.

 

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

Participate in the Technical Documentation Ideas forum

 

Prerequisites for Online Diagnostics

None.

Restrictions for Online Diagnostics

None.

Information About Online Diagnostics

With online diagnostics, you can test and verify the hardware functionality of the switch while the switch is connected to a live network.

The online diagnostics contain packet switching tests that check different hardware components and verify the data path and control signals. Disruptive online diagnostic tests, such as the built-in self-test (BIST) and the disruptive loopback test, and nondisruptive online diagnostic tests, such as packet switching, run during bootup, module online insertion and removal (OIR), and system reset. The nondisruptive online diagnostic tests run as part of background health monitoring. Either disruptive or nondisruptive tests can be run at the user’s request (on-demand).

The online diagnostics detect problems in the following areas:

  • Hardware components
  • Interfaces (GBICs, Ethernet ports, and so forth)
  • Connectors (loose connectors, bent pins, and so forth)
  • Solder joints
  • Memory (failure over time)

Online diagnostics is one of the requirements for the high availability feature. High availability is a set of quality standards that seek to limit the impact of equipment failures on the network. A key part of high availability is detecting hardware failures and taking corrective action while the switch runs in a live network. Online diagnostics in high availability detect hardware failures and provide feedback to high availability software components to make switchover decisions.

Online diagnostics are categorized as bootup, on-demand, schedule, or health-monitoring diagnostics. Bootup diagnostics run during bootup; on-demand diagnostics run from the CLI; schedule diagnostics run at user-designated intervals or specified times when the switch is connected to a live network; and health-monitoring runs in the background.

Default Settings for Online Diagnostics

See the default information for each test in Appendix A, “Online Diagnostic Tests.”

How to Configure Online Diagnostics

Setting Bootup Online Diagnostics Level

You can set the bootup diagnostics level as minimal or complete or you can bypass the bootup diagnostics entirely. Enter the complete keyword to run all diagnostic tests; enter the minimal keyword to run only EARL tests and loopback tests for all ports in the switch. Enter the no form of the command to bypass all diagnostic tests. The default bootup diagnositcs level is minimal.

To set the bootup diagnostic level, perform this task:

 

Command
Purpose

Router(config)# diagnostic bootup level { minimal | complete }

Sets the bootup diagnostic level.

This example shows how to set the bootup online diagnostic level:

Router(config)# diagnostic bootup level complete
Router(config)#
 

This example shows how to display the bootup online diagnostic level:

Router(config)# show diagnostic bootup level
Current bootup diagnostic level: complete
 
Router(config)#

Configuring On-Demand Online Diagnostics

You can run the on-demand online diagnostic tests from the CLI. You can set the execution action to either stop or continue the test when a failure is detected or to stop the test after a specific number of failures occur by using the failure count setting. You can configure a test to run multiple times using the iteration setting.

You should run packet-switching tests before memory tests.

note.gif

Noteblank.gif Do not use the diagnostic start all command until all of the following steps are completed.

Because some on-demand online diagnostic tests can affect the outcome of other tests, you should perform the tests in the following order:

1.blank.gif Run the nondisruptive tests.

2.blank.gif Run all tests in the relevant functional area.

3.blank.gif Run the TestTrafficStress test.

4.blank.gif Run the TestEobcStressPing test.

5.blank.gif Run the exhaustive-memory tests.

To run on-demand online diagnostic tests, perform this task:

Step 1blank.gif Run the nondisruptive tests.

To display the available tests and their attributes, and determine which commands are in the nondisruptive category, enter the show diagnostic content command.

Step 2blank.gif Run all tests in the relevant functional area.

Packet-switching tests fall into specific functional areas. When a problem is suspected in a particular functional area, run all tests in that functional area. If you are unsure about which functional area you need to test, or if you want to run all available tests, enter the complete keyword.

Step 3blank.gif Run the TestTrafficStress test.

This is a disruptive packet-switching test. This test switches packets between pairs of ports at line rate for the purpose of stress testing. During this test all of the ports are shut down, and you may see link flaps. The link flaps will recover after the test is complete. The test takes several minutes to complete.

Disable all health-monitoring tests f before running this test by using the no diagnostic monitor module number test all command.

Step 4blank.gif Run the TestEobcStressPing test.

This is a disruptive test and tests the Ethernet over backplane channel (EOBC) connection for the module. The test takes several minutes to complete. You cannot run any of the packet-switching tests described in previous steps after running this test. However, you can run tests described in subsequent steps after running this test.

Disable all health-monitoring tests before running this test by using the no diagnostic monitor module number test all command. The EOBC connection is disrupted during this test and will cause the health-monitoring tests to fail and take recovery action.

Step 5blank.gif Run the exhaustive-memory tests.

Before running the exhaustive-memory tests, all health-monitoring tests should be disabled because the tests will fail with health monitoring enabled and the switch will take recovery action. Disable the health-monitoring diagnostic tests by using the no diagnostic monitor module number test all command.

Perform the exhaustive-memory tests in the following order:

1.blank.gif TestFibTcamSSRAM

2.blank.gif TestAclQosTcam

3.blank.gif TestNetFlowTcam

4.blank.gif TestAsicMemory

5.blank.gif TestAsicMemory

You must reboot the after running the exhaustive-memory tests before it is operational again. You cannot run any other tests on the switch after running the exhaustive-memory tests. Do not save the configuration when rebooting as it will have changed during the tests. After the reboot, reenable the health-monitoring tests using the diagnostic monitor module number test all command.

 

To set the bootup diagnostic level, perform this task:

 

Command
Purpose

Router# diagnostic ondemand { iteration iteration_count } | { action-on-error {continue | stop } [ error_count ]}

Configures on-demand diagnostic tests to run, how many times to run (iterations), and what action to take when errors are found.

This example shows how to set the on-demand testing iteration count:

Router# diagnostic ondemand iteration 3
Router#
 

This example shows how to set the execution action when an error is detected:

Router# diagnostic ondemand action-on-error continue 2
Router#

Scheduling Online Diagnostics

You can schedule online diagnostics to run at a designated time of day or on a daily, weekly, or monthly basis. You can schedule tests to run only once or to repeat at an interval. Use the no form of this command to remove the scheduling.

To schedule online diagnostics, perform this task:

 

Command
Purpose

Router(config)# diagnostic schedule module number test { test_id | test_id_range | all } [ port { num | num_range | all }] { on mm dd yyyy hh : mm } | { daily hh : mm } | { weekly day_of_week hh : mm }

Schedules on-demand diagnostic tests on the specified module for a specific date and time, how many times to run (iterations), and what action to take when errors are found.

This example shows how to schedule diagnostic testing on a specific date and time for a specific port on module 1:

Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 on january 3 2003 23:32
Router(config)#
 

This example shows how to schedule diagnostic testing to occur daily at a certain time for a specific port:

Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 daily 12:34
Router(config)#
 

This example shows how to schedule diagnostic testing to occur weekly on a certain day for a specific port:

Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 weekly friday 09:23
Router(config)#

Configuring Health-Monitoring Diagnostics

You can configure health-monitoring diagnostic testing while the switch is connected to a live network. You can configure the execution interval for each health-monitoring test, the generation of a system message upon test failure, or the enabling or disabling an individual test. Use the no form of this command to disable testing.

To configure health-monitoring diagnostic testing, perform this task:

 

Command
Purpose

Step 1

Router(config)# diagnostic monitor interval module number test { test_id | test_id_range | all } [ hour hh ] [ min mm ] [ second ss ] [ millisec ms ] [ day day ]

Configures the health-monitoring interval of the specified tests. The no form of this command will change the interval to the default interval, or zero.

Step 2

Router(config)#[ no ] diagnostic monitor module number test { test_id | test_id_range | all }

Enables or disables health-monitoring diagnostic tests.

This example shows how to configure the specified test to run every two minutes on module 1:

Router(config)# diagnostic monitor interval module 1 test 1 min 2
Router(config)#
 

This example shows how to run the test if health monitoring has not previously been enabled:

Router(config)# diagnostic monitor module 1 test 1
 

This example shows how to enable the generation of a syslog message when any health-monitoring test fails:

Router(config)# diagnostic monitor syslog
Router(config)#

How to Run Online Diagnostic Tests

Overview of Diagnostic Test Operation

After you configure online diagnostics, you can start or stop diagnostic tests or display the test results. You can also see which tests are configured and what diagnostic tests have already run.

  • Enable the logging console/monitor to see all warning messages before you enable any online diagnostics tests.
  • When you are running disruptive tests, run the tests when connected through the 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 because a stress test is being performed with ports configured to loop internally; external traffic might alter 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 a supervisor engine, after the test is initiated and complete, you must reload or power down and then power up the entire system.
  • If you are running the tests on a switching module, rather than the supervisor engine, after the test is initiated and complete, you must reset the switching module.

Starting and Stopping Online Diagnostic Tests

After you configure diagnostic tests to run, you can use the start and stop to begin or end a diagnostic test. To start or stop an online diagnostic command, perform one of these tasks:

 

Command
Purpose

Router# diagnostic start module number test { test_id | test_id_range | minimal | complete | basic | per-port | non-disruptive | all} [port { num | port#_range | all}]

Starts a diagnostic test on a port or range of ports on the specified module.

Router# diagnostic stop module number

Stops a diagnostic test on the specified module.

This example shows how to start a diagnostic test on module 1:

Router# diagnostic start module 1 test 5
Module 1:Running test(s) 5 may disrupt normal system operation
Do you want to run disruptive tests? [no]yes
00:48:14:Running OnDemand Diagnostics [Iteration #1]...
00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5}...
00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully
00:48:14:Running OnDemand Diagnostics [Iteration #2]...
00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5}...
00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully
Router#
 

This example shows how to stop a diagnostic test:

Router# diagnostic stop module 1
Router#

Running All Online Diagnostic Tests

You can run all diagnostic tests, disruptive and nondisruptive, at once with a single command. In this case, all test dependencies will be handled automatically.

note.gif

Note ●blank.gif Running all online diagnostic tests will disrupt normal system operation. Reset the system after the diagnostic start system test all command has completed.

  • Do not insert, remove, or power down modules or the supervisor while the system test is running.
  • Do not issue any diagnostic command other than the diagnostic stop system test all command while the system test is running.
  • Make sure no traffic is running in background.

 

To start or stop all online diagnostic tests, perform one of these tasks:

 

Command
Purpose

Router# diagnostic start system test all

Executes all online diagnostic tests.

Router# diagnostic stop system test all

Stops the execution of all online diagnostic tests.

This example shows how to start all online diagnostic tests:

Router# diagnostic start system test all
*************************************************************************
* WARNING: *
* 'diagnostic start system test all' will disrupt normal system *
* operation. The system requires RESET after the command *
* 'diagnostic start system test all' has completed prior to *
* normal use. *
* *
* IMPORTANT: *
* 1. DO NOT INSERT, OIR, or POWER DOWN Linecards or *
* Supervisor while system test is running. *
* *
* 2. DO NOT ISSUE ANY DIAGNOSTIC COMMAND except *
* "diagnostic stop system test all" while system test *
* is running. *
* *
* 3. PLEASE MAKE SURE no traffic is running in background. *
*************************************************************************
Do you want to continue? [no]:

Displaying Online Diagnostic Tests and Test Results

You can display the online diagnostic tests that are configured and check the results of the tests using the following show commands:

  • show diagnostic content
  • show diagnostic health

To display the diagnostic tests that are configured, perform this task:

 

Command
Purpose

show diagnostic { bootup level | content [ module num ] | events [ module num ] [ event-type event-type ] | health | ondemand settings | result [ module num ] [ detail ] | schedule [ module num ]}

Displays the test results of online diagnostics and lists supported test suites.

This example shows how to display the online diagnostics that are configured on module 6:

Router# show diagnostic content module 6
 
Module 6: Supervisor Engine 2T 10GE w/ CTS (Active)
 
Diagnostics test suite attributes:
M/C/* - Minimal bootup level test / Complete bootup level test / NA
B/* - Basic ondemand test / NA
P/V/* - Per port test / Per device test / NA
D/N/* - Disruptive test / Non-disruptive test / NA
S/* - Only applicable to standby unit / NA
X/* - Not a health monitoring test / NA
F/* - Fixed monitoring interval test / NA
E/* - Always enabled monitoring test / NA
A/I - Monitoring is active / Monitoring is inactive
R/* - Power-down line cards and need reload supervisor / NA
K/* - Require resetting the line card after the test has completed / NA
T/* - Shut down all ports and need reload supervisor / NA
 
Test Interval Thre-
ID Test Name Attributes day hh:mm:ss.ms shold
==== ================================== ============ =============== =====
1) TestTransceiverIntegrity --------> **PD*X**I*** not configured n/a
2) TestLoopback --------------------> M*PD*X**I*** not configured n/a
3) TestActiveToStandbyLoopback -----> M*PDSX**I*** not configured n/a
4) TestL2CTSLoopback ---------------> M*PD*X**I*** not configured n/a
5) TestL3CTSLoopback ---------------> M*PD*X**I*** not configured n/a
6) TestScratchRegister -------------> ***N****A*** 000 00:00:30.00 5
7) TestNewIndexLearn ---------------> M**N****I*** 000 00:00:15.00 10
8) TestDontConditionalLearn --------> M**N****I*** 000 00:00:15.00 10
9) TestBpduTrap --------------------> M**D*X**I*** not configured n/a
10) TestMatchCapture ----------------> M**D*X**I*** not configured n/a
11) TestProtocolMatchChannel --------> M**D*X**I*** not configured n/a
12) TestMacNotification -------------> M**NS***A*** 000 00:00:15.00 10
13) TestPortSecurity ----------------> M**D*X**I*** not configured n/a
14) TestIPv4FibShortcut -------------> M**N****I*** 000 00:00:15.00 10
15) TestL3Capture2 ------------------> M**D*X**I*** not configured n/a
16) TestIPv6FibShortcut -------------> M**N****I*** 000 00:00:15.00 10
17) TestMPLSFibShortcut -------------> M**N****I*** 000 00:00:15.00 10
18) TestNATFibShortcut --------------> M**N****I*** 000 00:00:15.00 10
19) TestAclPermit -------------------> M**N****I*** 000 00:00:15.00 10
20) TestAclDeny ---------------------> M**D*X**I*** not configured n/a
21) TestAclRedirect -----------------> M**N****I*** not configured n/a
22) TestRBAcl -----------------------> M**N****I*** not configured n/a
23) TestQos -------------------------> M**D*X**I*** not configured n/a
24) TestDQUP ------------------------> M**D*X**I*** not configured n/a
25) TestL3VlanMet -------------------> M**D*X**I*** not configured n/a
26) TestIngressSpan -----------------> M**D*X**I*** not configured n/a
27) TestEgressSpan ------------------> M**D*X**I*** not configured n/a
28) TestNetflowShortcut -------------> M**D*X**I*** not configured n/a
29) TestInbandEdit ------------------> M**D*X**I*** not configured n/a
30) TestFabricInternalSnake ---------> M**D*X**I*** not configured n/a
31) TestFabricExternalSnake ---------> M**D*X**I*** not configured n/a
32) TestFabricVlanLoopback ----------> M**N*X**I*** not configured n/a
33) TestTrafficStress ---------------> ***D*X**I**T not configured n/a
34) TestL3TcamMonitoring ------------> ***N****A*** 000 00:00:15.00 10
35) TestFibTcam ---------------------> ***D*X**IR** not configured n/a
36) TestAclQosTcam ------------------> ***D*X**IR** not configured n/a
37) TestEarlMemOnBootup -------------> M**N*X**I*** not configured n/a
38) TestAsicMemory ------------------> ***D*X**IR** not configured n/a
39) ScheduleSwitchover --------------> ***D*X**I*** not configured n/a
40) TestFirmwareDiagStatus ----------> M**N****I*** 000 00:00:15.00 10
41) TestAsicSync --------------------> ***N****A*** 000 00:00:15.00 10
42) TestUnusedPortLoopback ----------> **PN****A*** 000 00:01:00.00 10
43) TestNonDisruptiveLoopback -------> **PN****A*** 000 00:00:10.00 10
44) TestFabricFlowControlStatus -----> ***N****I*** 000 00:00:15.00 10
45) TestPortTxMonitoring ------------> **PN****A*** 000 00:01:15.00 5
46) TestOBFL ------------------------> M**N****I*** 000 00:00:15.00 10
47) TestCFRW ------------------------> M*VN*X**I*** not configured n/a
48) TestLtlFpoeMemoryConsistency ----> ***N****A*** 000 00:00:30.00 1
49) TestErrorCounterMonitor ---------> ***N****A*** 000 00:00:30.00 10
50) TestEARLInternalTables ----------> ***N****A*** 000 00:05:00.00 1
 
Router#
 

This example shows how to display the online diagnostic results for module 6:

Router# show diagnostic result module 6
 
Current bootup diagnostic level: minimal
 
Module 6: Supervisor Engine 2T 10GE w/ CTS (Active) SerialNo : SAD132602A6
 
Overall Diagnostic Result for Module 6 : PASS
Diagnostic level at card bootup: minimal
 
Test results: (. = Pass, F = Fail, U = Untested)
 
1) TestTransceiverIntegrity:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
2) TestLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
3) TestActiveToStandbyLoopback:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
4) TestL2CTSLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
 
5) TestL3CTSLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
 
6) TestScratchRegister ------------->.
7) TestNewIndexLearn --------------->.
8) TestDontConditionalLearn -------->.
9) TestBpduTrap -------------------->.
10) TestMatchCapture ---------------->.
11) TestProtocolMatchChannel -------->.
12) TestMacNotification -------------> U
13) TestPortSecurity ---------------->.
14) TestIPv4FibShortcut ------------->.
15) TestL3Capture2 ------------------>.
16) TestIPv6FibShortcut ------------->.
17) TestMPLSFibShortcut ------------->.
18) TestNATFibShortcut -------------->.
19) TestAclPermit ------------------->.
20) TestAclDeny --------------------->.
21) TestAclRedirect ----------------->.
22) TestRBAcl ----------------------->.
23) TestQos ------------------------->.
24) TestDQUP ------------------------>.
25) TestL3VlanMet ------------------->.
26) TestIngressSpan ----------------->.
27) TestEgressSpan ------------------>.
28) TestNetflowShortcut ------------->.
29) TestInbandEdit ------------------>.
30) TestFabricInternalSnake --------->.
31) TestFabricExternalSnake --------->.
32) TestFabricVlanLoopback ---------->.
33) TestTrafficStress ---------------> U
34) TestL3TcamMonitoring ------------>.
35) TestFibTcam ---------------------> U
36) TestAclQosTcam ------------------> U
37) TestEarlMemOnBootup ------------->.
38) TestAsicMemory ------------------> U
39) ScheduleSwitchover --------------> U
40) TestFirmwareDiagStatus ---------->.
41) TestAsicSync -------------------->.
42) TestUnusedPortLoopback:
 
Port 1 2 3 4 5
-------------------
U U U..
 
 
43) TestNonDisruptiveLoopback:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
44) TestFabricFlowControlStatus -----> U
45) TestPortTxMonitoring:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
46) TestOBFL ------------------------>.
47) TestCFRW:
 
Device 1
---------
.
 
 
48) TestLtlFpoeMemoryConsistency ---->.
49) TestErrorCounterMonitor --------->.
50) TestEARLInternalTables ---------->.
 
 
Router#
 

This example shows how to display the detailed online diagnostic results for module 6:

Router# show diagnostic result module 6 detail
 
Current bootup diagnostic level: minimal
 
Module 6: Supervisor Engine 2T 10GE w/ CTS (Active) SerialNo : SAD132602A6
 
Overall Diagnostic Result for Module 6 : PASS
Diagnostic level at card bootup: minimal
 
Test results: (. = Pass, F = Fail, U = Untested)
 
___________________________________________________________________________
 
1) TestTransceiverIntegrity:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
2) TestLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:25
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:25
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
3) TestActiveToStandbyLoopback:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
4) TestL2CTSLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:29
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:29
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
5) TestL3CTSLoopback:
 
Port 1 2 3 4 5
-------------------
.....
 
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:33
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:33
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
6) TestScratchRegister ------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 8191
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:41
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:41
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
7) TestNewIndexLearn --------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:37
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:37
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
8) TestDontConditionalLearn -------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:37
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:37
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
9) TestBpduTrap -------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:37
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:37
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
10) TestMatchCapture ---------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:37
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:37
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
11) TestProtocolMatchChannel -------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:39
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:39
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
12) TestMacNotification -------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
13) TestPortSecurity ---------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:41
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:41
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
14) TestIPv4FibShortcut ------------->.
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
15) TestL3Capture2 ------------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
16) TestIPv6FibShortcut ------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
17) TestMPLSFibShortcut ------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
18) TestNATFibShortcut -------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
19) TestAclPermit ------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
20) TestAclDeny --------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
21) TestAclRedirect ----------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
22) TestRBAcl ----------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
23) TestQos ------------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
24) TestDQUP ------------------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
25) TestL3VlanMet ------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
26) TestIngressSpan ----------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
27) TestEgressSpan ------------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
28) TestNetflowShortcut ------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
29) TestInbandEdit ------------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
30) TestFabricInternalSnake --------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
31) TestFabricExternalSnake --------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
32) TestFabricVlanLoopback ---------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:43
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:43
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
33) TestTrafficStress ---------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
34) TestL3TcamMonitoring ------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 16382
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
35) TestFibTcam ---------------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
36) TestAclQosTcam ------------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
37) TestEarlMemOnBootup ------------->.
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:44
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:44
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
38) TestAsicMemory ------------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
39) ScheduleSwitchover --------------> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
40) TestFirmwareDiagStatus ---------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:44
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:44
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
41) TestAsicSync -------------------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 16382
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:42
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
42) TestUnusedPortLoopback:
 
Port 1 2 3 4 5
-------------------
U U U..
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 4261
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:41:53
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:41:53
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
43) TestNonDisruptiveLoopback:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
44) TestFabricFlowControlStatus -----> U
 
Error code ------------------> 3 (DIAG_SKIPPED)
Total run count -------------> 0
Last test testing type ------> n/a
Last test execution time ----> n/a
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> n/a
Total failure count ---------> 0
Consecutive failure count ---> 0
Current run count --------------->: 0
First test execution time ------->:
Last test execution time -------->:
Total FPOE Rate0 Count ---------->: 0
Total FPOE Reduced Rate Count --->: 0
___________________________________________________________________________
 
45) TestPortTxMonitoring:
 
Port 1 2 3 4 5
-------------------
U U U U U
 
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 3419
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:25
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:25
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
46) TestOBFL ------------------------>.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:44
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:44
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
47) TestCFRW:
 
Device 1
---------
.
 
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 1
Last test testing type ------> Bootup
Last test execution time ----> May 13 2011 21:59:44
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 13 2011 21:59:44
Total failure count ---------> 0
Consecutive failure count ---> 0
___________________________________________________________________________
 
48) TestLtlFpoeMemoryConsistency ---->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 8191
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:42
Total failure count ---------> 0
Consecutive failure count ---> 0
 
LTL PARITY
Ltl index -------------------> 0
Rbh value -------------------> 0
 
FPOE DB
Table size ------------------> 0
Last entries checked --------> 0
Total fail count ------------> 0
Total correction count ------> 0
Last detection time ---------> May 13 2011 21:58:47
Last result -----------------> UNKNOWN
Last fail count -------------> 0
Last correction count -------> 0
 
___________________________________________________________________________
 
49) TestErrorCounterMonitor --------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 8191
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:42:42
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:42:42
Total failure count ---------> 0
Consecutive failure count ---> 0
Error Records ---------------> n/a
___________________________________________________________________________
 
50) TestEARLInternalTables ---------->.
 
Error code ------------------> 0 (DIAG_SUCCESS)
Total run count -------------> 854
Last test testing type ------> Health Monitoring
Last test execution time ----> May 16 2011 21:38:38
First test failure time -----> n/a
Last test failure time ------> n/a
Last test pass time ---------> May 16 2011 21:38:38
Total failure count ---------> 0
Consecutive failure count ---> 0
 
AGE GROUP
Total CC run count ----------> 860
Table size ------------------> 16384
Total fail count ------------> 0
Total correction count ------> 0
Last completion time --------> May 16 2011 21:39:30
Last result -----------------> PASS
Last fail count -------------> 0
Last correction count -------> 0
Last entries checked --------> 16384
Consistency checker ---------> ON
 
BUNDLE PORT MAP
Total CC run count ----------> 860
Table size ------------------> 512
Total fail count ------------> 0
Total correction count ------> 0
Last completion time --------> May 16 2011 21:39:12
Last result -----------------> PASS
Last fail count -------------> 0
Last correction count -------> 0
Last entries checked --------> 512
Consistency checker ---------> ON
 
BUNDLE EXTENSION MAP
Total CC run count ----------> 860
Table size ------------------> 256
Total fail count ------------> 0
Total correction count ------> 0
Last completion time --------> May 16 2011 21:39:12
Last result -----------------> PASS
Last fail count -------------> 0
Last correction count -------> 0
Last entries checked --------> 256
Consistency checker ---------> ON
 
VLAN ACCESS MODE MEMORY
Total CC run count ----------> 860
Table size ------------------> 512
Total fail count ------------> 0
Total correction count ------> 0
Last completion time --------> May 16 2011 21:39:12
Last result -----------------> PASS
Last fail count -------------> 0
Last correction count -------> 0
Last entries checked --------> 512
Consistency checker ---------> ON
___________________________________________________________________________
 
 
Router#
 

This example shows how to display the output for the health checks performed:

Router# show diagnostic health
Non-zero port counters for 6/4 -
13. linkChange = 8530
 
Non-zero port counters for 6/5 -
13. linkChange = 8530
 
Router#

How to Perform Memory Tests

Most online diagnostic tests do not need any special setup or configuration. However, the memory tests, which include the TestFibTcamSSRAM and TestLinecardMemory tests, have some required tasks and some recommended tasks that you should complete before running them.

Before you run any of the online diagnostic memory tests, perform the following tasks:

  • Required tasks

–blank.gif Isolate network traffic by disabling all connected ports.

–blank.gif Do not send test packets during a memory test.

–blank.gif Reset the system before returning the system to normal operating mode.

  • Turn off all background health-monitoring tests using the no diagnostic monitor module number test all command.

How to Perform a Diagnostic Sanity Check

You can run the diagnostic sanity check in order to see potential problem areas in your network. The sanity check runs a set of predetermined checks on the configuration with a possible combination of certain system states to compile a list of warning conditions. The checks are designed to look for anything that seems out of place and are intended to serve as an aid for maintaining the system sanity.

To run the diagnostic sanity check, perform this task:

 

Command
Purpose

show diagnostic sanity

Runs a set of tests on the configuration and certain system states.

This example displays samples of the messages that could be displayed with the show diagnostic sanity command:

Router# show diagnostic sanity
Pinging default gateway 10.6.141.1....
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.6.141.1, timeout is 2 seconds:
..!!.
Success rate is 0 percent (0/5)
 
IGMP snooping disabled please enable it for optimum config.
 
IGMP snooping disabled but RGMP enabled on the following interfaces,
please enable IGMP for proper config :
Vlan1, Vlan2, GigabitEthernet1/1
 
Multicast routing is enabled globally but not enabled on the following
interfaces:
GigabitEthernet1/1, GigabitEthernet1/2
 
A programming algorithm mismatch was found on the device bootflash:
Formatting the device is recommended.
 
The bootflash: does not have enough free space to accomodate the crashinfo file.
 
Please check your confreg value : 0x0.
 
Please check your confreg value on standby: 0x0.
 
The boot string is empty. Please enter a valid boot string.
Could not verify boot image "disk0:" specified in the boot string on the
slave.
 
Invalid boot image "bootflash:asdasd" specified in the boot string on the
slave.
 
Please check your boot string on the slave.
 
UDLD has been disabled globally - port-level UDLD sanity checks are
being bypassed.
OR
[
The following ports have UDLD disabled. Please enable UDLD for optimum
config:
Gi1/22
 
The following ports have an unknown UDLD link state. Please enable UDLD
on both sides of the link:
Gi1/22
]
 
The following ports have portfast enabled:
Gi1/20, Gi1/22
 
The following ports have trunk mode set to on:
Gi1/1, Gi1/13
 
The following trunks have mode set to auto:
Gi1/2, Gi1/3
 
The following ports with mode set to desirable are not trunking:
Gi1/3, Gi1/4
 
The following trunk ports have negotiated to half-duplex:
Gi1/3, Gi1/4
 
The following ports are configured for channel mode on:
Gi1/1, Gi1/2, Gi1/3, Gi1/4
 
The following ports, not channeling are configured for channel mode
desirable:
Gi1/14
 
The following vlan(s) have a spanning tree root of 32768:
1
 
The following vlan(s) have max age on the spanning tree root different from
the default:
1-2
 
The following vlan(s) have forward delay on the spanning tree root different
from the default:
1-2
 
The following vlan(s) have hello time on the spanning tree root different
from the default:
1-2
 
The following vlan(s) have max age on the bridge different from the
default:
1-2
 
The following vlan(s) have fwd delay on the bridge different from the
default:
1-2
 
The following vlan(s) have hello time on the bridge different from the
default:
1-2
 
The following vlan(s) have a different port priority than the default
on the port gigabitEthernet1/1
1-2
 
The following ports have recieve flow control disabled:
Gi1/20, Gi1/22
 
The following inline power ports have power-deny/faulty status:
Gi1/1, Gi1/2
 
The following ports have negotiated to half-duplex:
Gi1/22
 
The following vlans have a duplex mismatch:
Gig 1/22
The following interafaces have a native vlan mismatch:
interface (native vlan - neighbor vlan)
Gig 1/22 (1 - 64)
 
The value for Community-Access on read-only operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.
 
The value for Community-Access on write-only operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.
 
The value for Community-Access on read-write operations for SNMP is the same
as default. Please verify that this is the best value from a security point
of view.

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

Participate in the Technical Documentation Ideas forum

 

Was this Document Helpful?

FeedbackFeedback

Contact Cisco