Table Of Contents
Online Offline Diagnostics—Field Diagnostics on Cisco uBR10012 Router User's Guide
Prerequisites for Online Offline Diagnostics
Restrictions for Online Offline Diagnostics
Information About Online Offline Diagnostics
Overview of Online Offline Diagnostics
Field Diagnostic Image Information
Field Diagnostic Test Information
Benefits of Online Offline Diagnostics
How to Use Online Offline Diagnostics on a Cisco uBR10012 Router
Downloading a Field Diagnostic Image
Running a Field Diagnostic Test
Verifying the Line Cards That Support the Field Diagnostic Image
Determining the Field Diagnostic Tests to Run
Loading the Field Diagnostic Image onto a Line Card and Starting a Field Diagnostic Test
Running a Per-Port or All Test
Removing a Field Diagnostic Image from a Line Card to Resume Normal Line Card Operation
Stopping an In-Progress Field Diagnostic Test
Verification Examples for Online Offline Diagnostics
Verifying Field Diagnostic Support for a Line Card: Example
Displaying Detailed Test Results Run on a Line Card: Example
Reviewing Test Results: Example
Feature Information for Online Offline Diagnostics on the Cisco uBR10012 Router
Online Offline Diagnostics—Field Diagnostics on Cisco uBR10012 Router User's Guide
First Published: NALast Updated: November 16, 2009Online Offline Diagnostics (OOD) Field Diagnostics, provides a means for testing and verifying hardware-related issues on a line card, when its deployed in the field. Download the OOD image from the Cisco website to perform hardware diagnostic tests on any line card in the uBR10012 universal broadband router. The test results are used to troubleshoot network issues and verify if a line card is faulty.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Online Offline Diagnostics
•
•
•
•
•
Prerequisites for Online Offline Diagnostics
Table 1 shows the hardware compatibility prerequisites for Online Offline Diagnostics:
Note
The software prerequisites for the Online Offline Diagnostics feature are:
•
•
Note
•
•
•
Restrictions for Online Offline Diagnostics
•
•
•
•
Information About Online Offline Diagnostics
The following sections provides an overview about the Online Offline Diagnostics feature, its benefits and system requirements when used on the Cisco uBR10012 universal broadband router:
•
•
•
•
Overview of Online Offline Diagnostics
The Online Offline Diagnostics (OOD) feature is a field diagnostic mechanism that provides customers with a method of testing and verifying line card hardware problems. For a list of hardware that support field diagnostics on the Cisco uBR10012 universal broadband router, see "Prerequisites for Online Offline Diagnostics" section
To perform a hardware diagnostic test on a line card in the Cisco uBR10012 universal broadband router, download an OOD Field Diagnostic image free of charge from the Cisco website and use it to test whether the line card problems are due to faulty hardware. You can run field diagnostic tests on the standby line card at any time without interrupting service. Testing the standby line card improves high availability of the system by ensuring the protect line card is ready for a switchover.
To verify whether or not the hardware is faulty, run the tests for line cards having PRE1 and PRE2. The PRE4 setup is only supported in Cisco IOS Release 12.2(33)SCC.
Field Diagnostic Image Information
A Field Diagnostic image is used to run diagnostic tests on a line card. The Field Diagnostic image is typically loaded from cisco.com onto the router, then from the router onto the line card to perform Field Diagnostic tests. Once Field Diagnostic testing is complete, the Field Diagnostic image must be unloaded off the line card to resume normal line card operation.
A few notes regarding Field Diagnostic images:
•
•
After the Field Diagnostic image is placed on one of the router's flash file systems, the Field Diagnostic image is downloaded onto the line card. When the Field Diagnostic image is downloaded onto a line card, the line card is automatically taken offline. Once field diagnostic testing is complete and the test results have been gathered, the Field Diagnostic image must be unloaded off the line card before normal line card operation can resume. Normal line card operation will resume automatically once the Field Diagnostic image has been unloaded off the line card.
•
The Field Diagnostic images for the Cisco ubr10012 universal broadband router can be downloaded from the following URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/ubr10kfielddiag
Field Diagnostic Test Information
The individual Field Diagnostic tests themselves, as well as per-port tests, are not currently relevant for troubleshooting purposes unless Field Diagnostic tests have already been run. If you want to run Field Diagnostic tests, we recommend selecting the all, basic, or default tests. The following explanations provide an overview of each test:
•
This test should only be performed if a line card is cabled for external loopback testing.
•
•
The estimates for the amount of time required to run each type of line card are given in the Field Diagnostics release notes.
Individual tests are useful for verification testing purposes. For instance, if a default test suite is run and all of the tests pass except test 5, test 5 can be run individually to confirm the test result of fail without having to run an entire test suite.
Benefits of Online Offline Diagnostics
Improved Troubleshooting
Field Diagnostics is used to verify if a line card problem is hardware-related or not. In cases where a problem is software-related, the Field Diagnostic image allows users to quickly rule out hardware problems as the cause and instead focus on fixing the software issue causing the problem.
Pre-installation Line Card Hardware Verification
Field Diagnostics allows users to verify whether a line card has hardware problems before installing the line card in a Cisco ubr10012 universal broadband router.
On-Site Fault Detection
Field Diagnostics is used to verify if a line card problem is due to a hardware fault; therefore, Field Diagnostics can be used to confirm if a problem is indeed hardware-related and a line card needs to be returned.
Additional Uptime
Field Diagnostics can increase network uptime by ensuring that line cards are not mistakenly taken offline when a problem is elsewhere.
How to Use Online Offline Diagnostics on a Cisco uBR10012 Router
This section describes the tasks that are performed to use Online Offline Field Diagnostics on the Cisco uBR10012 universal broadband router. The command-line interface (CLI) commands are used to complete the Field Diagnostic tasks.
See the following sections for the Field Diagnostic tasks:
•
•
•
•
Downloading a Field Diagnostic Image
Note
A Field Diagnostic image first must be downloaded to an FTP or TFTP server in order to run a field diagnostic test on a line card.
To download the Field Diagnostic image to an FTP or TFTP server, do the following:
Step 1
http://www.cisco.com/pcgi-bin/tablebuild.pl/ubr10kfielddiag
Step 2
Step 3
Running a Field Diagnostic Test
The following sections provide the instructions for running a Field Diagnostic test on a line card after the Cisco IOS image has been successfully loaded on the router and a Field Diagnostic image has been loaded onto the FTP or TFTP server.
This section covers the following topics:
•
•
•
Verifying the Line Cards That Support the Field Diagnostic Image
To check the line cards in the uBR10012 universal broadband router that support Field Diagnostic testing, enter the show diagnostic ood-status command in the privileged EXEC mode.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Determining the Field Diagnostic Tests to Run
The following are the tests that can be run on the line card:
•
•
•
Note
Loading the Field Diagnostic Image onto a Line Card and Starting a Field Diagnostic Test
To begin field diagnostic testing on a line card, the Field Diagnostic image must be loaded from the FTP or TFTP server onto the line card that will be tested.
Note
The following steps are required to download the Field Diagnostic image on to the line card:
Step 1
Step 2
a.
Note
See the "Running a Per-Port or All Test" section of this document for information on running per-port and all tests.In the following example, the Field Diagnostic image would be downloaded from the assigned TFTP server to the line card in subslot 8/1 and the default Field Diagnostic test suite would be run:
Router# diagnostic load subslot 8/1 tftp://126.1.1.1/myfolder/ubr10k-fdiagsclc-mz.7.0.bin autostart test defaultb.
The following example shows the Field Diagnostic image is loaded from the TFTP server to the line card in subslot 8/1. Note that the Field Diagnostic image has only been loaded onto the line card; Field Diagnostic testing has not begun.
Router# diagnostic load subslot 8/1 tftp://126.1.1.1/mytftpfolder/folder/ubr10k-fdiagsclc-mz.7.0.bin
Note
Step 3
See the "Running a Per-Port or All Test" section, for information on running per-port and all tests.
In the following example, a field diagnostic test with the default test suite is started on subslot 8/1. The example assumes that a Field Diagnostic image has been loaded onto the line card in subslot 8/1.
Router# diagnostic start subslot 8/1 test default
Note
Checking the Testing Process
Some individual tests take longer to run than others and the lack of feedback on the console may be time consuming h the tests are running properly.
If you are unsure if Field Diagnostic tests are still running, use the show diagnostic ood-status subslot slot/subslot detail command can be used to verify if the Field Diagnostic testing is in progress.
Analyzing Test Results
Note
After the Field Diagnostic test is run, an overall test result for the selected tests is displayed on the console. The overall test result is either pass or fail.
The overall results shown in the show diagnostic result and show diagnostic ood-status commands displays the overall results of all previously run tests, not just the most recently selected test or test suite. In the outputs of show diagnostic result and show diagnostic ood-status, the test results are listed as—Pass, Minor Error, or Major Error.
Pass—All of the Field Diagnostic tests passed.
Minor Error—This result is only seen with per-port and all tests. This error indicates that the tested interface is faulty but the other interfaces on the line card are not necessarily faulty
Major Error—This result indicates a hardware problem with the entire line card and the line card should not be used.
Use the recommendations based on the last test results below when deciding how to proceed after running any Field Diagnostics test.
Fail Result
If a test fails when a test suite is run, rerun the failed test or tests (not the entire test suite, just the test or tests that failed) by entering the diagnostic start target test failed-test-id command. This will confirm that the fail result is correct.
If the test fails again, copy any messages on the console exactly as they appear and gather the outputs of show diagnostic result and show diagnostic result detail and contact a customer support representative with the gathered information.
Pass Result
Each one of these tests suggests performing an external loopback test as a final test step. The external loopback test is supported on most, but not all, interfaces.
To see if external loopback testing is supported on an interface, enter the show diagnostic content command and see if the L attribute is available for an individual test. For information on running an external loopback test, proceed to the "Reviewing Test Results" section".•
•
If you would like to the test your line card further, attach an external loopback cable to a problem port (if you think the problem is in a particular port) or to all ports if possible and use the diagnostic start subslot slot/subslot test per-port port-number command to test the ports if your interface supports external loopback tests (see the note above for information on checking for external loopback support). If you run all of these tests and are still getting a pass result or external loopback testing is not supported on the interface, recable the router, unload the Field Diagnostic image, and place the line card back online. The problem is likely elsewhere.
•
If the test passed and you ran a basic test or individual tests but would like to run further tests, run a default test.
Running a Per-Port or All Test
The external loopback test is supported on some, but not all, interfaces.
To see if external loopback testing is supported on an interface, enter the show diagnostic content command and see if the L attribute is available for an individual test.For information on cabling DB-15 and RJ-45 connections for external loopback tests, see the Hard Plug Loopback Tests for E1 Lines document. Refer to other Cisco documentation regarding loopback cabling for particular cables and connector types.
A per-port Field Diagnostic test is used to test a specific port for hardware problems. A per-port test should only be run after a default test has been run and no problems were found on the other line card components. The all test suite is a test suite that includes the default test as well as all of the per-port tests. The all test suite should only be run if all of the interfaces are cabled with external loopback cables.
Per-port tests utilize external loopbacks to test the interface hardware. In most but not all cases, the interfaces to be tested need to be cabled with external loopback cables before per-port or all testing can begin. It is important to note that not all interfaces support external loopback testing.
In the following example, a per-port test is run on port 1 of the line card in subslot 8/1:
Router# diagnostic start subslot 8/1 test per-port port 1In the following example, all tests including all per-port diagnostic tests will be run on the line card in subslot 8/1:
Router# diagnostic start subslot 8/1 test allReviewing Test Results
After completing a Field Diagnostic test, a message will appear on the console indicating your overall test results. Additional show commands must be entered to gather test results and events information, however.
For additional information on diagnostic events and results, enter one of the following commands:
Table 2 Field Diagnostic show Commands for Viewing Test Results
Removing a Field Diagnostic Image from a Line Card to Resume Normal Line Card Operation
Note
The diagnostic unload subslot slot/subslot command can be used to unload a Field Diagnostic image as long as a test is not in progress. If you want to unload a Field Diagnostic image while a test is in progress, use the diagnostic stop subslot slot/subslot command to stop the test, followed by the diagnostic unload subslot slot/subslot command to unload the Field Diagnostic image.
Normal line card operation should resume after removing the Field Diagnostic image from the line card.
In the following example, the Field Diagnostic image is unloaded off the line card in subslot 8/1 and normal line card operation resumes. Note that the Field Diagnostic image unloading process does not begin until y is entered at the prompt to verify the operation.
Router# diagnostic unload subslot 8/1******************************************************************************WARNING:All Field Diagnostics test results and information will beunavailable to both the "show diagnostic result <target>" and"show diagnostic content <target>" commands.To save the test results, cancel the unloading process and enterthe "show diagnostic result <target>" command. Copy the outputinto a file, then re-enter the "diagnostic unload <target>" commandto restore normal line card operation.******************************************************************************% Are you sure that you want to perform this operation? [no]:yFDIAG [subslot 8/1]> Unloading the Field Diagnostics image and restoring the original run-time image, please wait ...FDIAG [subslot 8/1]> Field Diagnostics image was successfully unloadedSpecifying Testing Options
The following table provides a list of optional commands that can be entered before performing a Field Diagnostic test. None of these commands must be entered to perform a Field Diagnostic test and most Field Diagnostic test cases will not require these commands.
See the Cisco IOS CMTS Command Reference guide for additional information on any of the following commands:
Table 3 Field Diagnostics Pre-Testing Options
The following example shows how to change the size of the event table to 250. Note that the event table size is changed in global configuration mode.
Router# configure terminalRouter(config)# diagnostic event-log size 250The following example shows how to change diagnostic on-demand settings and then verify the changed diagnostic on-demand settings.
Router# diagnostic ondemand iterations 2Router# diagnostic ondemand action-on-failure stopRouter# show diagnostic ondemand settingsTest iterations = 2Action on test failure = stopStopping an In-Progress Field Diagnostic Test
To stop an in-progress test, enter the diagnostic stop subslot slot/subslot command while a test is in progress.
Note
The following example shows a diagnostic test being started and then stopped:
Router# diagnostic start subslot 8/1 test basicRouter#FDIAG [subslot 8/1]> Test ID(s) selected: 1-2,4,7,9-29,32-33FDIAG [subslot 8/1]> Running Field Diagnostics [Iteration #1] ...FDIAG [subslot 8/1]> Running MPC8260 Register Test {ID=1} ...FDIAG [subslot 8/1]> MPC8260 Register Test {ID=1} passedFDIAG [subslot 8/1]> Running MPC8260 Timer Test {ID=2} ...FDIAG [subslot 8/1]> MPC8260 Timer Test {ID=2} passedFDIAG [subslot 8/1]> Running march_dram_64 {ID=4} ...Router# diagnostic stop subslot 8/1FDIAG [subslot 8/1]> march_dram_64 {ID=4} passedFDIAG [subslot 8/1]> Testing is being abortedFDIAG [subslot 8/1]> Total testing time = 00:00:05.500Router#FDIAG [subslot 8/1]> Field Diagnostics was successfully stoppedVerification Examples for Online Offline Diagnostics
This section describes sample verification examples used to verify Online Offline Diagnostics on a line card.
•
•
•
Verifying Field Diagnostic Support for a Line Card: Example
In the following example, show diagnostic ood-status command is used to verify if Field Diagnostic testing is supported on the line cards. The support for the Field Diagnostic image is listed in the FDiag Support column of the show diagnostic ood-status command output:
Router# show diagnostic ood-statusLoad for five secs: 1%/0%; one minute: 2%; five minutes: 2%Time source is hardware calendar, *06:00:19.575 EDT Thu Oct 22 2009==== ======================== ======= ========== =========== ==============FDiag Loaded Overall CurrentSlot Card Description Support Image Type Diag Result Card State---- ------------------------ ------- ---------- ----------- --------------A Active PRE2-RP YES IOS N/A ONLINEB Standby PRE2-RP YES N/A N/A OFFLINE1 2jacket-1 YES LCDOS N/A ONLINE1 2cable-dtcc NO LCDOS N/A ONLINE2/1 2cable-tccplus NO LCDOS N/A ONLINE3/0 1gigethernet-hh-1 YES LCDOS N/A ONLINE3/1 1gigethernet-hh-1 YES LCDOS N/A ONLINE5/0 5cable-mc520h-d YES IOS N/A ONLINE6/0 5cable-mc520h-d YES Field Diag N/A RUNNING DIAG8/1 5cable-mc520u-d YES IOS N/A ONLINE==== ======================== ======= ========== =========== ==============Displaying Detailed Test Results Run on a Line Card: Example
In the following sample output, the test results per line card is displayed when the show diagnostic ood-status command is used along with subslot and detail keywords. The output displays diagnostic status of the line card along with details of the tests being run and their status, on the line card.
Router# show diagnostic ood-status subslot 6/0 detail==== ======================== ======= ========== =========== ==============FDiag Loaded Overall CurrentSlot Card Description Support Image Type Diag Result Card State---- ------------------------ ------- ---------- ----------- --------------6/0 5cable-mc520h-d YES Field Diag N/A RUNNING DIAG==== ======================== ======= ========== =========== ==============Detail testing progress for card in slot 6/0:Current card state: RUNNING DIAGTestID Test Name [Selected To Run (Y/N)] Status==== ============================================== =======1) Lookout2 RW test ......................... [Y] Passed2) Lookout2 R/W Intr bits ................... [Y] Passed3) Lookout2 Reset test ...................... [Y] Passed4) JIB2 PCI ID test ......................... [Y] Passed5) JIB2 Register read/write test ............ [Y] Passed6) JIB2 R/W Intr bits ....................... [Y] Passed7) JIB2 Reset test .......................... [Y] Passed8) JIB2 ifa6 SDRAM Test ..................... [Y] Running9) JIB2 ECC Disabled SDRAM Test ............. [Y] Not Run10) JIB2 Data Bus/Address SDRAM Test ......... [Y] Not Run11) JIB2 ifa6 SSRAM Test ..................... [Y] Not Run12) JIB2 Data Bus/Address SSRAM Test ......... [Y] Not Run13) Mfpga R/W Intr bits ...................... [Y] Not Run14) Mfpga Register read/write test ........... [Y] Not Run15) Mfpga Reset test......................... [Y] Not Run16) Internal Timer Test ...................... [Y] Not Run17) Random Register Test ..................... [Y] Not Run18) Processor Id Test ........................ [Y] Not Run19) Ping Test ................................ [Y] Not Run20) Core2 Memory Access Test ................. [Y] Not Run21) L1 Cache Test ............................ [Y] Not Run22) core 2 L1 Cache Test ..................... [Y] Not Run23) System DDR Test .......................... [Y] Not Run24) Local UART Port 0 Internal Loopback Test . [Y] Not Run25) Local UART Port 1 Internal Loopback Test . [Y] Not Run26) PCI Bridge R/W Test ...................... [Y] Not Run27) PCI Bridge ID Test ....................... [Y] Not Run28) DM Channel Test .......................... [Y] Not Run29) SMM665 Voltage Test ...................... [Y] Not Run30) MarchingPattern_nvram .................... [Y] Not Run31) DataPins_nvram ........................... [Y] Not RunRouter#Reviewing Test Results: Example
The following example is the show diagnostic result output for the last Field Diagnostic test run on the line card in subslot 8/1. The output reveals which tests passed, failed, and were not run (untested).
Router# show diagnostic result allSlot 8/1: 5cable-mc520s-d, 5 portsOverall diagnostic result: PASSTest results: (. = Pass, F = Fail, U = Untested)1) Gt Internal Reg (R/W) Test ----------------> .2) GT Sys Ctrlr PCI ID Test ------------------> .3) GT PCI Conf Reg R/W Test ------------------> .4) Gt Counters Test --------------------------> .5) ifa6 Memory Test --------------------------> .6) busErrorTest ------------------------------> .7) midPlaneRegTest ---------------------------> .8) Processor Id Test -------------------------> .9) Internal Timer Test -----------------------> .10) Random Register Test ----------------------> .(Additional output removed for readability)The following output shows detailed information for each Field Diagnostic test:
Schooner# show diagnostic result all detailSlot 8/1: 5cable-mc520s-d, 5 portsOverall diagnostic result: NOT AVAILABLETest results: (. = Pass, F = Fail, U = Untested)___________________________________________________________________________1) Gt Internal Reg (R/W) Test ----------------> UError code ----------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------> 0Last test execution time --------------> n/aFirst test failure time ---------------> n/aLast test failure time ----------------> n/aLast test pass time -------------------> n/aTotal failure count -------------------> 0Consecutive failure count -------------> 0___________________________________________________________________________2) GT Sys Ctrlr PCI ID Test ------------------> UError code ----------------------------> 0 (DIAG_SUCCESS)Total run count -----------------------> 0Last test execution time --------------> n/aFirst test failure time ---------------> n/aLast test failure time ----------------> n/aLast test pass time -------------------> n/aTotal failure count -------------------> 0Consecutive failure count -------------> 0___________________________________________________________________________(Additional output removed for readability)The following example shows how to display a list of previous diagnostic events with a brief description of each event.
Router# show diagnostic eventsDiagnostic events (storage for 500 events, 18 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------04/25 11:01:43.847 I [1/1] Card detected: 2cable-tccplus, S/N:04/25 11:01:51.991 I [8/1] Card detected: 5cable-mc520s-d, S/N:N/A04/25 11:40:36.163 I [8/1] Loading Field Diag image into 5cable-mc520s-d04/25 11:40:44.247 E [8/1] Invalid URL for Field Diag image04/25 11:49:02.003 I [8/1] Card detected: 5cable-mc520s-d, S/N:N/A04/25 12:01:31.451 I [8/1] Loading Field Diag image into 5cable-mc520s-d04/25 12:01:36.571 E [8/1] Invalid URL for Field Diag image04/25 12:02:44.799 I [8/1] Loading Field Diag image into 5cable-mc520s-d04/25 12:02:46.019 E [8/1] Field Diag image has crashed during bootup04/25 12:02:46.019 I [8/1] Restoring original run-time image04/25 12:02:46.799 E [8/1] Invalid URL for Field Diag image04/25 12:09:52.003 I [8/1] Card detected: 5cable-mc520s-d, S/N:N/A04/25 12:21:20.599 I [8/1] Loading Field Diag image into 5cable-mc520s-d04/25 12:21:22.599 E [8/1] Invalid URL for Field Diag image04/25 12:29:12.003 I [8/1] Card detected: 5cable-mc520s-d, S/N:N/A04/25 14:20:40.963 I [8/1] Loading Field Diag image into 5cable-mc520s-d04/25 14:21:46.059 I [8/1] Field Diag image is loaded and booting04/25 14:21:48.355 I [8/1] Test list retrieval is completedAdditional References
The following sections provide references related to configuring Online Offline Diagnostics:
Related Documents
CMTS Command Reference
Cisco IOS CMTS Cable Command Reference, at the following URL:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.htmlCisco uBR10012 Universal Broadband Router Documentation
Cisco uBR10012 Universal Broadband Router Hardware Installation Guide, at the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/guide/hig.htmlCisco uBR10012 Universal Broadband Router Software Configuration Guide, at the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/configuration/guide/scg.htmlCisco uBR10012 Universal Broadband Router Release Notes
http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_release_notes_list.html
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
For information about commands, see the Cisco IOS CMTS Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.
Feature Information for Online Offline Diagnostics on the Cisco uBR10012 Router
Table 4 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCC or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
Guest
