-
Cisco ME 6500 Series Cisco IOS Command Reference, 12.2ZU
-
Acronyms
-
Acknowledgments for Open-Source Software
-
channel-protocol to class-map
-
Command-Line Interface
-
action to channel-group
-
clear ca to copy /noverify
-
Quick Links to Catalyst 6500 Series Switch Cisco IOS Commands
-
Whole book PDF: Cisco ME 6500 Series Ethernet Switches Cisco IOS Command Reference, Release 12.2 ZU
-
Index
-
define interface-range to duplex
-
encapsulation to mls exclude
-
mls flow to pagp port
-
platform ip features sequential to process-min-time percent
-
Preface
-
rcv-queue to show bootvar
-
shutdown vlan to time-range
-
show cable-diag to show ip cache
-
show ip cef to show mls asic
-
show mls cef to show qm-sp
-
show queueing to show vtp
-
traceroute mac to username
-
verify to wrr-queue
-
wrr-queue cos to wrr-queue threshold
-
Table Of Contents
show cef interface policy-statistics
show interfaces private-vlan mapping
show interfaces switchport backup
22show catalyst6000
To display the information about the Cisco ME 6500 series Ethernet switch, use the show catalyst6000 command.
show catalyst6000 {all | chassis-mac-address | switching-clock | traffic-meter}
Syntax Description
Defaults
all
Command Modes
EXEC
Command History
Usage Guidelines
The switching-clock keywords are not supported on the Cisco ME 6500 series Ethernet switch.
The Cisco ME 6500 series Ethernet switch has 64 MAC addresses that are available to support the software features. You can enter the show catalyst6000 chassis-mac-address command to display the MAC-address range on your chassis.
Examples
This example shows how to display the MAC-address ranges and the current and peak traffic-meter readings:
Router> show catalyst6000 allchassis MAC addresses: 64 addresses from 0001.6441.60c0 to 0001.6441.60fftraffic meter = 0% Never clearedpeak = 0% reached at 08:14:38 UTC Wed Mar 19 2003Router>This example shows how to display the MAC-address ranges:
Router# show catalyst6000 chassis-mac-addresschassis MAC addresses: 64 addresses from 00d0.004c.1800 to 00d0.004c.1c00Router#This example shows how to display the current and peak traffic-meter readings:
Router> show catalyst6000 traffic-metertraffic meter = 0% Never clearedpeak = 0% reached at 10:21:48 PST Mon Mar 13 2006Router#show cdp neighbors
To display detailed information about the neighboring devices that are discovered through CDP, use the show cdp neighbors command.
show cdp neighbors [type number] [detail]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to display the information about the CDP neighbors:
Router# show cdp neighborsCapability Codes: R - Router, T - Trans Bridge, B - Source Route BridgeS - Switch, H - Host, I - IGMP, r - Repeater, P - PhoneDevice ID Local Intrfce Holdtme Capability Platform Port IDlab-7206 Eth 0 157 R 7206VXR Fas 0/0/0lab-as5300-1 Eth 0 163 R AS5300 Fas 0lab-as5300-2 Eth 0 159 R AS5300 Eth 0lab-as5300-3 Eth 0 122 R AS5300 Eth 0lab-as5300-4 Eth 0 132 R AS5300 Fas 0/0lab-3621 Eth 0 140 R S 3631-telcoFas 0/0008024 2758E0 Eth 0 132 T CAT3000 1/2Table 2-29 describes the fields that are shown in the example.
This example shows how to display detailed information about your CDP neighbors:
Router# show cdp neighbors detail-------------------------Device ID: lab-7206Entry address(es):IP address: 172.19.169.83Platform: cisco 7206VXR, Capabilities: RouterInterface: Ethernet0, Port ID (outgoing port): Gigabitethernet0/0/0Holdtime : 123 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) 5800 Software (C5800-P4-M), Version 12.1(2)Copyright (c) 1986-2002 by Cisco Systems, Inc.advertisement version: 2Duplex: half-------------------------Device ID: lab-as5300-1Entry address(es):IP address: 172.19.169.87...Table 2-30 describes the fields that are shown in the example.
Related Commands
show cef interface policy-statistics
To display the per-interface traffic statistics, use the show cef interface policy-statistics command.
show cef interface policy-statistics
Syntax Description
This command has no keywords or arguments.
Defaults
This command has no default settings.
Command Modes
User EXEC
Command History
Examples
This example shows how to display the per-interface traffic statistics:
Router# show cef interface policy-statisticsPOS7/0 is up (if_number 7)Bucket Packets Bytes1 0 02 0 03 0 04 0 05 100 100006 0 07 0 08 0 0Router#show class-map
To display class-map information, use the show class-map command.
show class-map [class-name]
Syntax Description
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
Examples
This example shows how to display class-map information for all class maps:
Router# show class-mapClass Map match-any class-default (id 0)Match anyClass Map match-any class-simple (id 2)Match anyClass Map match-all ipp5 (id 1)Match ip precedence 5Class Map match-all agg-2 (id 3)Router#This example shows how to display class-map information for a specific class map:
Router# show class-map ipp5Class Map match-all ipp5 (id 1)Match ip precedence 5Router#Related Commands
show counters interface
To display the information about the interface counter, use the show counters interface command.
show counters interface {type mod/port} [delta]
Syntax Description
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
Usage Guidelines
The show counters interface command is not supported on SVIs.
The show counters interface delta command displays a detailed list of the last-saved counter values.
Examples
This example shows how to display the information about the interface counter:
Router# show counters interface gigabitethernet 1/264 bit counters:0. rxHCTotalPkts = 1825761. txHCTotalPkts = 53942. rxHCUnicastPkts = 5823. txHCUnicastPkts = 94. rxHCMulticastPkts = 1770015. txHCMulticastPkts = 53836. rxHCBroadcastPkts = 49937. txHCBroadcastPkts = 28. rxHCOctets = 138194829. txHCOctets = 213367810. rxTxHCPkts64Octets = 16708111. rxTxHCPkts65to127Octets = 986812. rxTxHCPkts128to255Octets = 013. rxTxHCPkts256to511Octets = 1102114. rxTxHCpkts512to1023Octets = 015. rxTxHCpkts1024to1518Octets = 016. txHCTrunkFrames = 017. rxHCTrunkFrames = 018. rxHCDropEvents = 1047332 bit counters:0. rxCRCAlignErrors = 01. rxUndersizedPkts = 02. rxOversizedPkts = 03. rxFragmentPkts = 04. rxJabbers = 05. txCollisions = 06. ifInErrors = 07. ifOutErrors = 08. ifInDiscards = 09. ifInUnknownProtos = 010. ifOutDiscards = 011. txDelayExceededDiscards = 012. txCRC = 013. linkChange = 014. wrongEncapFrames = 0All Port Counters1. InPackets = 1825802. InOctets = 138201003. InUcastPkts = 5824. InMcastPkts = 1770055. InBcastPkts = 49936. OutPackets = 53947. OutOctets = 21336788. OutUcastPkts = 99. OutMcastPkts = 538310. OutBcastPkts = 211. AlignErr = 012. FCSErr = 013. XmitErr = 014. RcvErr = 015. UnderSize = 016. SingleCol = 017. MultiCol = 018. LateCol = 019. ExcessiveCol = 020. CarrierSense = 021. Runts = 022. Giants = 023. InDiscards = 024. OutDiscards = 025. InErrors = 026. OutErrors = 027. InUnknownProtos = 028. txCRC = 029. TrunkFramesTx = 030. TrunkFramesRx = 031. WrongEncap = 032. Broadcast_suppression_discards = 033. Multicast_suppression_discards = 034. Unicast_suppression_discards = 035. rxTxHCPkts64Octets = 16708436. rxTxHCPkts65to127Octets = 986837. rxTxHCPkts128to255Octets = 038. rxTxHCPkts256to511Octets = 1102239. rxTxHCpkts512to1023Octets = 040. rxTxHCpkts1024to1518Octets = 041. DropEvents = 1047342. CRCAlignErrors = 043. UndersizedPkts = 044. OversizedPkts = 045. FragmentPkts = 046. Jabbers = 047. Collisions = 048. DelayExceededDiscards = 049. bpduOutlost = 050. qos0Outlost = 051. qos1Outlost = 052. qos2Outlost = 053. qos3Outlost = 054. qos4Outlost = 055. qos5Outlost = 056. qos6Outlost = 057. qos7Outlost = 058. qos8Outlost = 059. qos9Outlost = 060. qos10Outlost = 061. qos11Outlost = 062. qos12Outlost = 063. qos13Outlost = 064. qos14Outlost = 065. qos15Outlost = 066. qos16Outlost = 067. qos17Outlost = 068. qos18Outlost = 069. qos19Outlost = 070. qos20Outlost = 071. qos21Outlost = 072. qos22Outlost = 073. qos23Outlost = 074. qos24Outlost = 075. qos25Outlost = 076. qos26Outlost = 077. qos27Outlost = 078. qos28Outlost = 079. qos29Outlost = 080. qos30Outlost = 081. qos31Outlost = 082. bpduCbicOutlost = 083. qos0CbicOutlost = 084. qos1CbicOutlost = 085. qos2CbicOutlost = 086. qos3CbicOutlost = 087. bpduInlost = 088. qos0Inlost = 089. qos1Inlost = 090. qos2Inlost = 091. qos3Inlost = 092. qos4Inlost = 093. qos5Inlost = 094. qos6Inlost = 095. qos7Inlost = 096. qos8Inlost = 097. qos9Inlost = 098. qos10Inlost = 099. qos11Inlost = 0100. qos12Inlost = 0101. qos13Inlost = 0102. qos14Inlost = 0103. qos15Inlost = 0104. pqueInlost = 0105. Overruns = 0106. maxIndex = 0Router#This example shows how to display the values for the interface counters since the last clear counters command:
Router# show counters interface gigabitethernet1/2 deltaTime since last clear---------------------never64 bit counters:0. rxHCTotalPkts = 1826381. txHCTotalPkts = 53962. rxHCUnicastPkts = 5823. txHCUnicastPkts = 94. rxHCMulticastPkts = 177061...Router#Related Commands
show diagnostic
To view the test results of the online diagnostics and list the supported test suites, use the show diagnostic command.
show diagnostic bootup level
show diagnostic content [module num]
show diagnostic events [module num] [event-type event-type]
show diagnostic {ondemand settings}
show diagnostic {result [module num] [detail]}
show diagnostic schedule [module num]
Syntax Description
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
Usage Guidelines
If you do not enter a module num, information for all modules is displayed.
In the command output, the possible testing results are as follows:
•
Passed (.)
•
•
Examples
This example shows how to display the test suite and the monitoring interval and test attributes:
Router# show diagnostic content module 1Module 1: Cisco ME 6524 Ethernet Switch (Active)Diagnostics test suite attributes:M/C/* - Minimal bootup level test / Complete bootup level test / NAB/* - Basic ondemand test / NAP/V/* - Per port test / Per device test / NAD/N/* - Disruptive test / Non-disruptive test / NAS/* - Only applicable to standby unit / NAX/* - Not a health monitoring test / NAF/* - Fixed monitoring interval test / NAE/* - Always enabled monitoring test / NAA/I - Monitoring is active / Monitoring is inactiveR/* - Power-down line cards and need reset supervisor / NAK/* - Require resetting the line card after the test has completed / NAT/* - Shut down all ports and need reset supervisor / NATesting IntervalID Test Name Attributes (day hh:mm:ss.ms)==== ================================== ============ =================1) TestTransceiverIntegrity --------> **PD****I*** not configured2) TestScratchRegister -------------> ***N****A*** 000 00:00:30.003) TestNonDisruptiveLoopback -------> **PN****A*** 000 00:00:05.004) TestLoopback --------------------> M*PD****I*** not configured5) TestNewIndexLearn ---------------> M**N****I*** not configured6) TestDontConditionalLearn --------> M**N****I*** not configured7) TestBadBpduTrap -----------------> M**D****I*** not configured8) TestMatchCapture ----------------> M**D****I*** not configured9) TestProtocolMatchChannel --------> M**D****I*** not configured10) TestFibDevices ------------------> M**N****I*** not configured11) TestIPv4FibShortcut -------------> M**N****I*** not configured12) TestL3Capture2 ------------------> M**N****I*** not configured13) TestIPv6FibShortcut -------------> M**N****I*** not configured14) TestMPLSFibShortcut -------------> M**N****I*** not configured15) TestNATFibShortcut --------------> M**N****I*** not configured16) TestAclPermit -------------------> M**N****I*** not configured17) TestAclDeny ---------------------> M**N****A*** 000 00:00:05.0018) TestQoSTcam ---------------------> M**D****I*** not configured19) TestL3VlanMet -------------------> M**N****I*** not configured20) TestIngressSpan -----------------> M**N****I*** not configured21) TestEgressSpan ------------------> M**N****I*** not configured22) TestNetflowInlineRewrite --------> C*PD****I*** not configured23) TestFibTcamSSRAM ----------------> ***D****IR** not configured24) TestAsicMemory ------------------> ***D****IR** not configured25) TestAclQosTcam ------------------> ***D****IR** not configured26) TestNetflowTcam -----------------> ***D****IR** not configured27) FirmwareDiagStatus --------------> M**N****I*** not configuredRouter#This example shows how to display the configured boot-up diagnostic level:
Router# show diagnostic bootup levelCurrent Bootup Diagnostic Level = CompleteRouter#This example shows how to display the event log for the diagnostics:
Router# show diagnostic eventsDiagnostic events (storage for 500 events, 1 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------03/08 21:39:36.311 I [1] Diagnostics PassedRouter#This example shows how to display the settings for the ondemand diagnostics:
Router# show diagnostic ondemand settingsOndemand Run Iteration = 2Ondemand Action-on-Error = CONTINUERouter#This example shows how to display the current scheduled diagnostic tasks for the specified slot:
Router# show diagnostic schedule module 1Current Time = 07:55:30 UTC Fri August 2 2002Diagnostic for Module 1:Schedule #1:To be run on January 3 2006 23:32Test ID(s) to be executed:1.Schedule #2:To be run daily 14:45Test ID(s) to be executed:2.Schedule #3:To be run weekly Monday 3:33Test ID(s) to be executed:all.Router#This example shows how to display the testing results for the specified slot:
Router# show diagnostic result module 1Current bootup diagnostic level: minimalModule 1: Cisco ME 6524 Ethernet Switch (Active) SerialNo : CSJ09515511Overall Diagnostic Result for Module 1 : PASSDiagnostic level at card bootup: minimalTest results: (. = Pass, F = Fail, U = Untested)1) TestTransceiverIntegrity:Port 25 26 27 28 29 30 31 32----------------------------. U U U U U U U2) TestScratchRegister -------------> .3) TestNonDisruptiveLoopback:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------. . . . . . . . . . . . . . . . . . . . . . . .Port 25 26 27 28 29 30 31 32----------------------------U U U U U U U U4) TestLoopback:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------. . . . . . . . . . . . . . . . . . . . . . . .Port 25 26 27 28 29 30 31 32----------------------------. . . . . . . .5) TestNewIndexLearn ---------------> .6) TestDontConditionalLearn --------> .7) TestBadBpduTrap -----------------> .8) TestMatchCapture ----------------> .9) TestProtocolMatchChannel --------> .10) TestFibDevices ------------------> .11) TestIPv4FibShortcut -------------> .12) TestL3Capture2 ------------------> .13) TestIPv6FibShortcut -------------> .14) TestMPLSFibShortcut -------------> .15) TestNATFibShortcut --------------> .16) TestAclPermit -------------------> .17) TestAclDeny ---------------------> .18) TestQoSTcam ---------------------> .19) TestL3VlanMet -------------------> .20) TestIngressSpan -----------------> .21) TestEgressSpan ------------------> .22) TestNetflowInlineRewrite:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------U U U U U U U U U U U U U U U U U U U U U U U UPort 25 26 27 28 29 30 31 32----------------------------U U U U U U U U23) TestFibTcamSSRAM ----------------> U24) TestAsicMemory ------------------> U25) TestAclQosTcam ------------------> U26) TestNetflowTcam -----------------> U27) FirmwareDiagStatus --------------> .Router#This example shows how to display the detailed testing results for the specified slot:
Router# show diagnostic result module 1 detailCurrent bootup diagnostic level: minimalModule 1: Cisco ME 6524 Ethernet Switch (Active) SerialNo : CSJ09515511Overall Diagnostic Result for Module 1 : PASSDiagnostic level at card bootup: minimalTest results: (. = Pass, F = Fail, U = Untested)1) TestTransceiverIntegrity:Port 25 26 27 28 29 30 31 32----------------------------. U U U U U U U2) TestScratchRegister -------------> .3) TestNonDisruptiveLoopback:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------. . . . . . . . . . . . . . . . . . . . . . . .Port 25 26 27 28 29 30 31 32----------------------------U U U U U U U U4) TestLoopback:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------. . . . . . . . . . . . . . . . . . . . . . . .Port 25 26 27 28 29 30 31 32----------------------------. . . . . . . .5) TestNewIndexLearn ---------------> .6) TestDontConditionalLearn --------> .7) TestBadBpduTrap -----------------> .8) TestMatchCapture ----------------> .9) TestProtocolMatchChannel --------> .10) TestFibDevices ------------------> .11) TestIPv4FibShortcut -------------> .12) TestL3Capture2 ------------------> .13) TestIPv6FibShortcut -------------> .14) TestMPLSFibShortcut -------------> .15) TestNATFibShortcut --------------> .16) TestAclPermit -------------------> .17) TestAclDeny ---------------------> .18) TestQoSTcam ---------------------> .19) TestL3VlanMet -------------------> .20) TestIngressSpan -----------------> .21) TestEgressSpan ------------------> .22) TestNetflowInlineRewrite:Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24----------------------------------------------------------------------------U U U U U U U U U U U U U U U U U U U U U U U UPort 25 26 27 28 29 30 31 32----------------------------U U U U U U U U23) TestFibTcamSSRAM ----------------> U24) TestAsicMemory ------------------> U25) TestAclQosTcam ------------------> U26) TestNetflowTcam -----------------> U27) FirmwareDiagStatus --------------> .Router#This example shows how to display the event logs for the diagnostics:
Router# show diagnostic eventsDiagnostic events (storage for 500 events, 1 events recorded)Event Type (ET): I - Info, W - Warning, E - ErrorTime Stamp ET [Card] Event Message------------------ -- --------------------------------------------------------03/08 21:39:36.311 I [1] Diagnostics PassedRouter#Related Commands
show diagnostic cns
To display the information about the CNS subject, use the show diagnostic cns command.
show diagnostic cns {publish | subscribe}
Syntax Description
publish
Displays the subject with which the diagnostic results is published.
subscribe
Displays the subscribed subjects.
Defaults
This command has no default settings.
Command Modes
EXEC
Command History
Usage Guidelines
The CNS subsystem communicates with remote network applications through the CNS-event agent and follows the publish and subscribe model. An application sets itself up to receive events by subscribing to the approprate event subject name.
Examples
This example shows how to display the subject with which the diagnostic results is published:
Router# show diagnostic cns publishSubject: cisco.cns.device.diag_resultsRouter#This example shows how to display the subscribed subject:
Router# show diagnostic cns subscribeSubject: cisco.cns.device.diag_get_resultsRouter#Related Commands
show diagnostic sanity
To display sanity check results, use the show diagnostic sanity command.
show diagnostic sanity
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
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 to maintaining the system sanity.
The following is a list of the checks that are run and the action taken when the condition is found:
•
•
Trunking Checks
•
•
•
•
Channeling Checks
•
•
•
Spanning-tree VLAN Checks
•
•
•
•
•
Spanning-tree Port Checks
•
•
UDLD Checks
•
•
•
Assorted Port Checks
•
•
•
–
–
–
–
•
•
Bootstring and Config Register Checks
•
•
•
If only device: is specified as a filename, then the system verifies that the first file is on the device.
Assorted Checks
•
•
•
•
•
•
•
•
Examples
This example displays samples of the messages that could be displayed with the show diagnostic sanity command:
Router# show diagnostic sanityPinging 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/1Multicast routing is enabled globally but not enabled on the followinginterfaces:GigabitEthernet1/1, GigabitEthernet1/2A 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 theslave.Invalid boot image "bootflash:asdasd" specified in the boot string on theslave.Please check your boot string on the slave.UDLD has been disabled globally - port-level UDLD sanity checks arebeing bypassed.OR[The following ports have UDLD disabled. Please enable UDLD for optimumconfig: