![]() |
Layer 3 Switching Software Feature and Configuration Guide, 12.0(10)W5(18c)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Command Reference
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Table of ContentsCommand ReferencePort Snooping Commands
QoS Commands Redundancy Commands redundancy
SDM Commandsredundancy force-failover main-cpu redundancy primary-cpu preferred show capability show redundancy Controller and Switch show Commands show controllers
Port Commandsshow controllers access-list show controllers adjacency show controllers cef show controllers interface-info show controllers ipmcast show controllers ipx-prefix show controllers c8500 interface-map show controllers c8500 ipmcast show controllers c8500 ipx-node show controller c8500 ipx-prefix show controllers c8500 queuing show switch counters Command ReferenceThis appendix provides a command reference for those Cisco IOS commandsor aspects of the commandsthat are unique to Layer 3 switching on the Catalyst 8540 CSR, Catalyst 8510 CSR, and Catalyst 8540 MSR with Layer 3 functionality. This appendix includes the following categories of commands:
Port Snooping CommandsPort snooping lets you transparently mirror traffic from one or more source ports to a destination port. The following commands let you set up and monitor snooping. snoopTo set up port-based traffic mirroring, or snooping, use the snoop command. To disable snooping, use the no form of this command.
Syntax Description
Snooping is disabled on all interfaces. Command Modes Interface configuration The snooping destination port can be any port in the system, except for the source port or ports, the Ethernet management port on the route processor, or any ports configured for Fast EtherChannel. The snooping source port can be any port on an interface module. There can be multiple snooping destination ports operating simultaneously, but only one destination port can be used per snooping session. Examples The following example shows how to set up bidirectional port snooping using the snoop interface configuration command. In this example, the destination port is 12/0/15 and the source port is 0/0/1. 8500CSR# configure terminal 8500CSR(config)# interface fastethernet 12/0/15 8500CSR(config-if)# shutdown 8500CSR(config-if)# snoop interface fastethernet 0/0/1 direction both 8500CSR(config-if)# no shutdown Related Commands show snoop show snoopTo display the current snooping sessions, use the show snoop command. show snoop [interface destination-port]Syntax Description
Command Modes Privileged EXEC Examples The following example shows output from the show snoop command. 8500CSR# show snoop Snoop Test Port Name: FastEthernet1/0/4 (interface status=SNOOPING) Snoop option: (configured=enabled)(actual=enabled) Snoop direction: (configured=receive)(actual=receive) Monitored Port Name: (configured=FastEthernet1/0/3)(actual=FastEthernet1/0/3) Related Commands show snoop-vc show snoop-vcTo display the virtual circuits being used by the snooping feature, use the show snoop-vc command. show snoop-vc [interface destination-port]Syntax Description
Command Modes Privileged EXEC Examples The following example shows output from the show snoop-vc command. 8500CSR# show snoop-vc
Snooping Snooped
Interface VPI VCI Type X-Interface X-VPI X-VCI Dir Status
FastEthernet1/0/4 4 223 PVC FastEthernet1/0/3 0
35 RX UP
FastEthernet1/0/4 4 224 PVC FastEthernet1/0/3 0
36 RX UP
FastEthernet1/0/4 8 223 PVC FastEthernet1/0/3 0
57 RX UP
FastEthernet1/0/4 8 224 PVC FastEthernet1/0/3 0
58 RX UP
FastEthernet1/0/4 8 225 PVC FastEthernet1/0/3 0
59 RX UP
.........
Related Commands show snoop QoS Commandsqos switchingTo enable quality of service (QoS) mapping on the device, use the qos switching command. To disable QoS mapping, use the no form of this command.
Syntax Description This command has no keywords or arguments. Defaults QoS mapping is enabled. Command Modes Global configuration Examples The following example shows how to enable QoS mapping using the qos switching configuration command. 8500CSR(config)# qos switching Related Commands qos mapping precedence qos mapping precedenceTo configure QoS mapping at the system or interface level, use the qos mapping precedence command. To set the QoS precedence back to the default value, use the no form of this command.
Syntax Description
Defaults The default WRR-weight for a precedence value n is 2 ^ n. Command Modes Global configuration Usage Guidelines When a precedence value n is specified, it implicitly assigns the same WRR weight to the precedence n + 1. Examples The following example shows how to set the system-level QoS mapping using the 8500CSR(config)# qos mapping precedence 0 wrr-weight 4 Related Commands qos switching show qos switchingTo show whether QoS mapping is enabled on the device, use the show qos switching command. show qos switchingSyntax Description This command has no keywords or arguments. Command Modes Privileged EXEC Examples The following example shows how to display whether QoS mapping is enabled using the show qos switching command. 8500CSR# show qos switching QoS Based IP Switching enabled Related Commands show qos mapping show qos mappingTo show the QoS mapping in effect at the system or interface level, use the show qos mapping command. show qos mapping [source source-int] [destination dest-int]Syntax Description
Command Modes Privileged EXEC Examples The following example shows how to display the system-level QoS mapping using the show qos mapping command. 8500CSR# show qos mapping
Precedence WRR-Weight
0 1
1 2
2 4
3 8
Related Commands show qos switching Redundancy CommandsredundancyTo enter redundancy mode, use the redundancy global configuration command. redundancySyntax Description This command has no arguments or keywords. Command Modes Global configuration Usage Guidelines To enter the main-cpu mode of redundancy mode, use the main-cpu command. Examples The following example shows how to enter redundancy mode. Router(config)# redundancy Router(config-r)# The following example shows how to switch to the main-cpu submode of redundancy mode.
Related Commands auto-sync redundancy force-failover main-cpuTo force the primary route processor to allow the secondary route processor to take over and become the primary, use the redundancy force-failover main-cpu EXEC command. redundancy force-failover main-cpuSyntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Usage Guidelines If the secondary route processor is in ROMMON mode it becomes the primary route processor but continues in ROMMON mode; that is, the IOS software is not loaded. The force-failover main-cpu command causes the main processor functions of the switch to change to the secondary route processor, if one is installed. If the command is executed when only one route processor is installed, the command is ignored and an error message indicating this condition appears. Examples The following example shows how to make the secondary route processor the primary. Router# redundancy force-failover main-cpu Related Commands show redundancy redundancy primary-cpu preferredTo establish the preferred primary route processor, which also establishes the preferred secondary route processor, use the primary-cpu preferred redundancy command. To change the primary route processor to a secondary, use the no form of this command.
Syntax Description
Defaults No preferred route processor. Command Modes Redundancy Usage Guidelines The primary route processor is determined based on the previous configuration. Examples The following example shows how to enter redundancy mode and establish the preferred primary route processor for slot4. Switch(config)# redundancy Switch(config-r)# primary-cpu preferred slot4 Related Commands auto-sync show capabilityTo display the capabilities of the primary or secondary route processor and the software version that is running, use the show capability EXEC command. show capability {primary | secondary}Syntax Description
Command Modes Privileged EXEC Usage Guidelines The show capability display includes hardware and functional versions of the various components. Examples The following example displays the capabilities of a primary route processor. Router# show capability primary Dram Size is :64 MB Pmem Size is :4 MB Nvram Size is :512 KB BootFlash Size is :8 MB ACPM hw version 3.1 ACPM functional version 3.8 Netclk Module present flag :1 NCLK hw version 1.0 NCLK func version 1.2 Printing the parameters for Switch card: 0 SWC0 HW version 2.2 SWC0 Functional version 0.40 SWC0 Table memory size: 8 MB SWC0 Feat Card Present Flag: 1 SWC0 Feat Card HW version 1.0 SWC0 Feat Card Functional version 2.0 Printing the parameters for Switch card: 1 SWC1 HW version 0.0 SWC1 Functional version 0.0 SWC1 Table memory size: 0 MB SWC1 Feat Card Present Flag: 0 SWC1 Feat Card HW version 0.0 SWC1 Feat Card Functional version 0.0 Printing the parameters for Switch card: 2 SWC2 HW version 2.2 SWC2 Functional version 0.40 SWC2 Table memory size: 8 MB SWC2 Feat Card Present Flag: 1 SWC2 Feat Card HW version 1.0 SWC2 Feat Card Functional version 2.0 Number of Drivers in IOS: 3 Driver 0 type: 2560 Driver 0 Functional Version 0.27 Driver 1 type: 2562 Driver 1 Functional Version 0.1 Driver 2 type: 2564 Driver 2 Functional Version 0.1 show redundancyTo list all redundancy-related information, use the show redundancy privileged EXEC command. show redundancySyntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Usage Guidelines This command is available on the primary route processor only. Examples The following example lists redundancy information. Router# show redundancy Primary ------- Slot: 4 Uptime: 4 minutes Image: Version 12.0(19980716:020138) [kartik-ehsa-integ 107] Last Running Config. Sync: 4 minutes Last Startup Config. Sync: 4 minutes Last Restart Reason: Normal boot Secondary --------- Slot: 8 Uptime: 4 minutes Image: Version 12.0(19980716:020138) SDM Commandssdm access-listTo partition the TCAM space for the access list region, use the sdm access-list command. sdm access-list num-entriesSyntax Description
Command Modes Global configuration Usage Guidelines The enhanced Gigabit Ethernet interface module supports TCAM sizes of 32K, 64K, or 256K. The combined size of the protocol regions and access lists should not exceed your TCAM space. The default size of the access lists in a 32K, 64K, or 256K TCAM is 512. You can use the sdm access-list command to partition the TCAM space for access lists. Related Commands sdm autolearnTo enable the switching database manager (SDM) autolearn feature, use the sdm autolearn command. To disable it, use the no form of this command. sdm autolearnno sdm autolearn Syntax Description Description This command has no keywords or arguments. Defaults SDM autolearn is enabled. Command Modes Global configuration Usage Guidelines When the SDM autolearn feature is enabled, SDM automatically saves mask-length distribution for the routing database. SDM then uses this mask-length distribution as the initial mask-length distribution, which takes effect during the next system reboot. sdm sizeTo configure the size of each protocol region in the SDM, use the sdm size command. sdm size region-name {num-entries | k-entries num-k-entries}Syntax Description
Command Modes Global configuration Usage Guidelines The combined size entered for all the protocol regions should not exceed the total TCAM sizes of 32K, 64K, or 256K. The supported size can be displayed using the show sdm size command. The size of SDM is represented as the number of base entries. Each protocol region entry can occupy one or more TCAM entries. The combined size of all the protocol regions should be calculated in terms of the base entries. Table A-1 lists the number of TCAM entries needed for each protocol region. Table A-1: Protocol Regions and TCAM Entries
Since the ip-prefix region occupies one TCAM entry, the sdm size ip-prefix k-entries 6 command configures 6K TCAM entries in the SDM for the ip-prefix region. Since each ipx-node entry occupies two TCAM entries, the sdm size ipx-node k-entries 3 command configures 6K TCAM entries in the SDM for the ipx-node region. Related Commands show sdm internalTo display SDM management information for each protocol region in TCAM, use the show sdm internal EXEC command. The information includes SDM status, minimum TCAM size available, and the TCAM size required for the configuration. For each application region, this command also yields information about the logical start and end of the application region in TCAM, lookup type, key size, and statistics about other key operations. show sdm internal { all-region | ip-adjacency |ip-multicast | ip-prefix | ipx-network |ipx-node } Syntax Description
Command Modes Privileged EXEC Examples The following example is sample output from the show sdm internal command: Router# show sdm internal all-region Address Map : Status :Ready TCAM Minimum Size :262144 entries TCAM Required Size :29248 entries SRAM Sz :481280 entries TCAM Start :32 Xinfo Start :262144 Xinfo Size :225536 Name :IPX BVI Network Size :32 MinSize :32 MaxSize :32 FreeKey :0x0 Start :0x20 End :0x3F Entry :32-bit Lookup :Exact-Match Events : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 0 Failure 0 Name :IP Adjacency Size :2048 MinSize :32 MaxSize :65536 FreeKey :0xEEEEEEEE Start :0x40 End :0x83F Entry :32-bit Lookup :Exact-Match Events : Insert :Success 5 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 5 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 0 Failure 0 Name :IPX Node Size :2048 MinSize :32 MaxSize :65536 FreeKey :0xF0000000 Start :0x840 End :0x183E Entry :64-bit Lookup :Exact-Match Events : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 0 Failure 0 Name :IP Prefix Size :8192 MinSize :32 MaxSize :262144 FreeKey :0xEEEEEEEEEEEEEEEE Start :0x1840 End :0x383F Entry :32-bit Lookup :Longest-Match Buckets :33 Events : Insert :Success 9 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 9 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 20 Failure 0 Name :IPX Network Size :6144 MinSize :32 MaxSize :65536 FreeKey :0x0 Start :0x3840 End :0x503F Entry :32-bit Lookup :Exact-Match Events : Insert :Success 2 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 2 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 0 Failure 0 Name :IP Multicast Size :3072 MinSize :16 MaxSize :65536 FreeKey :0xF0000000F0000000 Start :0x5040 End :0x683E Entry :64-bit Lookup :Longest-Match Buckets :34 Events : Insert :Success 3 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 3 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 31 Failure 0 Name :UDP Flooding Size :256 MinSize :256 MaxSize :256 FreeKey :0xF0000000 Start :0x6840 End :0x6A3E Entry :64-bit Lookup :Exact-Match Events : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 IPCs : Insert :Success 0 Failure 0 Delete :Success 0 Failure 0 Modify :Success 0 Failure 0 Move :Success 0 Failure 0 Mask RW :Success 0 Failure 0 Name :MAC Addr Size :1024 MinSize :64 MaxSize :65536 FreeKey :0x0 Start :0x6A40 End :0x723E Entry :64-bit Lookup :Reserved show sdm sizeTo display the size of TCAM and the size of each protocol region, use the show sdm size EXEC command. The size is shown as number of entries. show sdm sizeSyntax Description This command does not have any keywords or arguments. Command Modes Privileged EXEC Examples The following is sample output from the show sdm size command: Router# show sdm size
Switching Database Region Sizes :
IPX BVI Network :32 32-bit entries
IP Adjacency :2048 32-bit entries
IPX Node :2048 64-bit entries
IP Prefix :8192 32-bit entries
IPX Network :6144 32-bit entries
IP Multicast :3072 64-bit entries
UDP Flooding :256 64-bit entries
MAC Addr :1024 64-bit entries
Access List :512 128-bit entries
Controller and Switch show Commandsshow controllersTo display the controller register values, use the show controllers EXEC command. show controllers interface-type slot/subslot/interfaceSyntax Description
Command Modes Privileged EXEC Usage Guidelines This command uses IPC to get the values of MAC registers and MII registers. If the interface processor stops responding to IPC, the counter values shown are no longer current. Examples The following is sample output from the show controllers command for a fast Ethernet interface: Router# show controllers fastethernet 11/0/4 IF Name:FastEthernet11/0/4 Port Status UP Loopback Reg [3-0]|[7-4]:0x8|0x8 Duplex/Speed Reg [3-0]|[7-4]:0xFFFF|0x0 FPGA Rev :6.8 Slicer registers SMDR 0x0060 (Tx En, Rx En) SSTR 0x1000 EVER 0x1704 (Ver C1) SSMR 0x4000 SIMR 0x0000 MBXW 0x0000 MBXR 0x0000 SPER 0xF000 GMUX VER 0xF000 MARKER 0x0000 MAC registers CMCR :0x00000443 CMPR :0x140A0E60 MII registers: Control Register (0x0):0x2000 Status Register (0x1):0x780D (Link Up) PHY Identification Register 1 (0x2):0x7810 PHY Identification Register 2 (0x3):0x43 Auto Neg. Advertisement Reg (0x4):0x81 (Speed 100,Duplex half) Auto Neg. Partner Ability Reg (0x5):0x0 (Peer not auto-negotiating) Auto Neg. Expansion Register (0x6):0x0 Mirror Register (0x10):0x630 Interrupt Enable Register (0x11):0x0 Interrupt Status Register (0x12):0x4000 Configuration Register (0x13):0x0 (UTP, Tx Enable) Chip Status Register (0x14):0x28C8 (Link Up, Half, 100) Link Status Register [3-0]|[7-4]:0x1|0x0 MAC Receive Counters: bytes = 130461473 pkt64 = 5204 pkt65to127 = 10532 pkt128to255 = 54499 pkt256to511 = 1651 pkt512to1023 = 766 pkt1024to1522 = 4456 good_giants = 0 error_giants = 0 good_runts = 0 error_runts = 0 ucast_pkts = 25743 mcast_pkts = 57570 bcast_pkts = 59331 align_errs = 0 fcs_errs = 0 overruns = 0 MAC Transmit Counters: Bytes = 159215359 pkt64 = 43038 pkt65to127 = 38282 pkt128to255 = 54526 pkt256to511 = 26485 pkt512to1023 = 731 pkt1024to1518 = 4507 ucast_pkts = 30936 mcast_pkts = 10927 bcast_pkts = 60170 fcs_errs = 0 giants = 0 underruns = 0 one_collision = 0 mult_collisions = 0 excess_collisions = 0 Slicer Receive Counters: Cells = 1698452 Frames = 99087 Header Sequence Errors = 0 fcs_errs = 0 Length = 0 Slicer Transmit Counters: Cells = 1721097 Frames = 61233 Table A-2 describes some of the important fields in the previous display. Table A-2: show controllers Registers and Descriptions for Fast Ethernet Interfaces
The following is sample output from the show controllers command for a Gigabit Ethernet interface: Router# show controllers gigabitethernet 9/0/0 IF Name:GigabitEthernet9/0/0 Port Status DOWN FPGA Rev :0.2 Gigabit Ether Status :0x310 (Link Down, Rx Sync-N, Optical detect-N) Mode Parallel Register :0x36 Port 0 Serial Mode Register :0x1 Port 1 Serial Mode Register :0x1 Link Interrupt Enable :0x1 Tx Disable :0x3 Slicer registers SMDR 0x0060 (Tx En, Rx En) SSTR 0x1000 EVER 0x1704 (Ver C1) SSMR 0x4000 SIMR 0x0000 MBXW 0x0000 MBXR 0x0000 SPER 0xF000 GMUX VER 0x17B1 MARKER 0x17B1 MAC registers CMCR :0x00000423 CMPR :0x140A0E61 MII registers: Control Register (0x0):0x4140 Status Register (0x1):0x159 Auto Neg. Advt. Register (0x4):0x20 Auto Neg. Partner Ability Reg (0x5):0x0 RX Configuration Register (0xA):0x21 TR_IPG_TIME Register (0x10):0x6 PAUSE_TIME Register (0x11):0x0 PAUSE_SA1 Register (0x12):0x0 PAUSE_SA2 Register (0x13):0x0 PAUSE_SA3 Register (0x14):0x0 Pause Watermark Register (0x15):0xC040 TX FIFO Watermark Register (0x16):0xFF02 PAUSE_STAT_SENT Register (0x17):0x0 PAUSE_STAT_RCVD Register (0x18):0x0 Memory Address Register (0x19):0x0 Memory Control Register (0x1A):0x1 Memory Data High Register (0x1B):0x0 Memory Data Low Register (0x1C):0x0 Sys Control Register (0x1E):0x70C Sys Status Register (0x1F):0x0 Link Status Register [3-0]|[7-4]:0x0|0x0 Counters : Channel 0: MAC Receive Counters: bytes = 130461473 pkt64 = 5204 pkt65to127 = 10532 pkt128to255 = 54499 pkt256to511 = 1651 pkt512to1023 = 766 pkt1024to1522 = 4456 good_giants = 0 error_giants = 0 good_runts = 0 error_runts = 0 ucast_pkts = 25743 mcast_pkts = 57570 bcast_pkts = 59331 align_errs = 0 fcs_errs = 0 overruns = 0 MAC Transmit Counters: Bytes = 159215359 pkt64 = 43038 pkt65to127 = 38282 pkt128to255 = 54526 pkt256to511 = 26485 pkt512to1023 = 731 pkt1024to1518 = 4507 ucast_pkts = 30936 mcast_pkts = 10927 bcast_pkts = 60170 fcs_errs = 0 giants = 0 underruns = 0 one_collision = 0 mult_collisions = 0 excess_collisions = 0 Ingress Markers = 16103 Egress Markers = 32207 Slicer Receive Counters: Cells = 1698452 Frames = 99087 Header Sequence Errors = 0 fcs_errs = 0 Length = 0 Slicer Transmit Counters: Cells = 1721097 Frames = 61233 Channel 1: MAC Receive Counters: bytes = 130461893 pkt64 = 5204 pkt65to127 = 10532 ........... Channel 7: MAC Receive Counters: bytes = 13050012 pkt64 = 5208 pkt65to127 = 10552 pkt128to255 = 54501 pkt256to511 = 1656 pkt512to1023 = 772 pkt1024to1522 = 4459 good_giants = 0 error_giants = 0 good_runts = 0 error_runts = 0 ucast_pkts = 25743 mcast_pkts = 57570 bcast_pkts = 59331 align_errs = 0 fcs_errs = 0 overruns = 0 MAC Transmit Counters: Bytes = 15915320 pkt64 = 43030 pkt65to127 = 38762 pkt128to255 = 54529 pkt256to511 = 26487 pkt512to1023 = 600 pkt1024to1518 = 4490 ucast_pkts = 31230 mcast_pkts = 11306 bcast_pkts = 60171 fcs_errs = 0 giants = 0 underruns = 0 one_collision = 0 mult_collisions = 0 excess_collisions = 0 Ingress Markers = 16105 Egress Markers = 32203 Slicer Receive Counters: Cells = 1698452 Frames = 99087 Header Sequence Errors = 0 fcs_errs = 0 Length = 0 Slicer Transmit Counters: Cells = 1721097 Frames = 61233 Table A-3 describes some of the important fields in the previous display. Table A-3: show controllers Registers and Descriptions for Gigabit Ethernet Interfaces
show controllers access-listTo display the access control list (ACL) entries on an interface module, use the show controllers access-list command. show controllers interface-type slot/subslot/interface access-list {in | out}Syntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays TCAM entries for an ACL configured on an interface. It interprets the contents of TCAM and displays them in the same format as the Cisco IOS ACL commands, such as the show access-lists command.
Examples The following is sample output from the show controllers access-list command: Router# show controllers fastethernet 3/0/0 access-list in Input ACL entries for Interface FastEthernet3/0/0 Index:6 Label:2 [V:0 M:1][0 IP] deny ip 100.1.3.0 0.0.0.255 any [V:0 M:2][1 IP] permit ip any any [V:0 M:3][2 IPX] permit 1 2.1000.0000.0003 [V:0 M:4][3 IPX] deny 1 2 [V:0 M:5][4 IPX] deny any any This output corresponds to the following access-list configuration: Router# show running-config interface fastethernet 3/0/0 Building configuration... Current configuration: ! interface FastEthernet3/0/0 ip address 1.0.0.1 255.0.0.0 ip access-group 100 in no ip directed-broadcast ipx access-group 800 in ipx network 4 end Table A-4 describes the fields in the show controllers access-list display. Table A-4: show controllers access-list Field Descriptions
show controllers adjacencyTo display the IP address table on an interface module, use the show controllers adjacency EXEC command. show controllers interface-type slot/subslot/interface adjacency {ip-address | detail} [cam module-num]Syntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays the IP address table on each interface module. This table contains IP address entries present in the ARP table (displayed by show arp command) and adjacency table (displayed by show adjacency command). This table has a one-to-one correspondence with the adjacency table. Examples The following is sample output from the show controllers adjacency command: Router# show controllers fastethernet 3/0/0 adjacency IPaddr:1.0.0.2 MACaddr:00e0.4f5d.f000 FastEthernet3/0/0(6) IPaddr:2.0.0.6 MACaddr:0007.0007.0007 FastEthernet3/0/2(8) IPaddr:1.0.0.5 MACaddr:0005.0005.0005 FastEthernet3/0/0(6) IPaddr:2.0.0.5 MACaddr:0006.0006.0006 FastEthernet3/0/2(8) Total number of IP adjacency entries:4 Missing IP adjacency entries:0 show controllers cefTo display the IP prefix table on interface modules, use the show controllers cef EXEC command. show controllers interface-type slot/subslot/interface cef {prefix mask | detail | missing | summary} [cam module-num]Syntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays the IP prefix table on each interface module. The table contains IP prefix entries present in the IP routing table (displayed by the show ip route command) and CEF table (displayed by the show ip cef command). This table has a one-to-one correspondence with the CEF table. Examples The following is sample output from the show controllers cef command: Router# show controllers fastethernet 3/0/0 cef
Default Network Information:
Load Balancing:Off
Prefix/Masklen Next Hop
0.0.0.0/0 not populated
0.0.0.0/32 not populated
1.0.0.0/8 SRP
1.0.0.0/32 SRP
1.0.0.1/32 SRP
1.0.0.2/32 not populated
1.0.0.5/32 not populated
1.255.255.255/32 SRP
2.0.0.0/8 SRP
2.0.0.0/32 SRP
2.0.0.1/32 SRP
2.0.0.5/32 not populated
2.0.0.6/32 not populated
2.255.255.255/32 SRP
11.0.0.0/8 not populated
12.0.0.0/8 not populated
20.0.0.0/8 2.0.0.5
40.0.0.0/8 not populated
128.46.167.95/32 not populated
128.118.25.3/32 not populated
140.247.60.28/32 not populated
Prefix/Masklen Next Hop
171.69.1.129/32 not populated
172.20.42.0/24 SRP
172.20.42.0/32 SRP
172.20.42.213/32 SRP
172.20.42.255/32 SRP
199.199.199.0/24 1.0.0.2
2.0.0.5
224.0.0.0/4 not populated
224.0.0.0/24 SRP
255.255.255.255/32 not populated
Total IP Prefix Entries in CAM:15
Missing IP Prefix Entries in CAM:0
CEF entries not populated:15
The following is sample output from the show controllers cef summary command. 8500#sh controller f3/0/0 cef summary Total IP Prefix Entries in CAM:14 Missing IP Prefix Entries in CAM:0 CEF entries not populated:8 The following is sample output from the show controllers cef missing command: Router# show controllers fastethernet 3/0/0 cef missing Prefix/Masklen Next Hop Total IP Prefix Entries in CAM:15 Missing IP Prefix Entries in CAM:0 CEF entries not populated:15 Table A-5 describes some of the fields in the display. Table A-5: show controllers cef Field Descriptions
show controllers interface-infoTo display the resident interface entry that corresponds to a second interface, use the show controllers interface-info EXEC command. show controllers interface1 interface-info interface2Syntax Description
Command Modes Privileged EXEC Usage Guidelines One interface table for each physical port is resident on each interface module. Each table maintains entries corresponding to all interfaces or subinterfaces in the system. Each entry is indexed by a unique-identifier assigned to each interface or subinterface. The interface entry maintains the following information:
Examples The following is sample output from the show controllers interface-info command: Router# show controllers gigabitethernet 12/0/0 interface-info gigabitethernet 12/0/0
IF Entry for GigabitEthernet12/0/0 on GigabitEthernet12/0/0
Mac(hex) - 00:10:7B:C5:D3:77
isMyInteface :True isSubInterface :False
Status Down Broute VC - 0 Bcast VC - 0
Netmask:32
FEC disabled
Trunking Disabled
State :Not-Applicable/Listening/Blocking
Bridge-Group disabled
IP routing off bridging off
IPX routing off bridging off
Appletalk routing off
In Encapsulation:
ICMP Redirect disabled Unreachable disabled
IP Multicast disabled:ttl-threshold:0
ACL Indexs:
Input ACL:0 Output ACL:0
ACL Flags:
Input IP:OFF Output IP:OFF
Input IPX:OFF Output IPX:OFF
Slowpath - Input:OFF
The display contains the following categories of information:
show controllers ipmcastTo display the IP multicast routing table information stored on an interface module, use the show controllers ipmcast EXEC command. show controllers interface-type slot/subslot/interface ipmcast group-address [source-address [detail] | all] [cam module-num]Syntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays the IP multicast routing table entries for all sources within a group (*, G) or for a specified source (S, G) within a group. Examples The following is sample output from the show controllers ipmcast command: Router# show controllers fastethernet 0/0/7 ipmcast 231.1.1.1 171.11.78.77 detail
MEMBER_ENTRY, root vc = 1/33, packet counter = 4
(231.1.1.1, 171.11.78.77), CAM Loc 0x4025, 0 E 50 0 0 4 2 13
Send_to_cpu flag not set, SPT flag set
p2mp vc:root FastEthernet0/0/7, VPI = 1, VCI = 33
leaf FastEthernet0/0/3, VPI = 0, VCI = 226
FastEthernet0/0/0, VPI = 0, VCI = 227
Table A-6 describes some of the fields in the display. Table A-6: show controllers ipmcast Field Descriptions
show controllers ipx-prefixTo display the IPX network entries for a specified interface, use the show controllers ipx-prefix EXEC command. show controllers interface-type slot/subslot/interface ipx-prefix {all-entries | cam-summary | fail-entries | fail-summary}[cam module-num]Syntax Description
Command Modes Privileged EXEC Examples The following is sample output from the show controllers ipx-prefix command: Router# show controllers fastethernet 10/0/9 ipx-prefix all-entries
IPX Prefix Entries in CAM, Interface FastEthernet10/0/9
-----------------------------------------------------------------
Codes:C - Connected network, R - Remote network
V - valid entry, N - Network entry
L - load balancing enabled, D - default network
E - EIGRP enabled, I - Internal network
B - BVI network, M - My Mac Address
VC - VCI
C 1009 V N
Novell ether IF No 14 00d0.5845.2660 My-Node Valid
R 5004 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 5005 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 5006 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
show controllers c8500 interface-mapTo display the interface number assigned to each interface or subinterface, use the show controllers c8500 interface-map EXEC command. show controllers c800 interface-mapSyntax Description This command has no arguments or keywords. Command Modes Privileged EXEC Usage Guidelines The output from this command shows all the interfaces and subinterfaces in the system, along with the assigned interface number for each. This command displays information specific to the Catalyst 8510 and Catalyst 8540 switch routers. Examples The following is sample output from the show controllers c800 interface-map command: Router# show controllers c8500 interface-map GigabitEthernet2/0/0 (IF number:4) GigabitEthernet12/0/0 (IF number:5) GigabitEthernet12/0/1 (IF number:6) show controllers c8500 ipmcastTo display IP multicast routing table control layer information, VC sharing information, and statistics, use the show controllers c8500 ipmcast EXEC command. show controllers c8500 ipmcast group-address {source-address | all}show controllers c8500 ipmcast group-address vc-sharing show controllers c8500 ipmcast group-address {stats | reset} Syntax Description
Command Modes Privileged EXEC Usage Guidelines When an IP multicast source address or the keyword all is specified, this command displays IP multicast routing table control layer information, such as the VC used for an IP multicast packet matching a particular entry. When the keyword vc-sharing is specified, this command displays all the point-to-multipoint VCs used for an IP multicast group and the number of entries that are sharing this VC. When the keyword stats is used, this command displays debugging information. The show controllers c8500 ipmcast command displays information specific to the Catalyst 8510 and Catalyst 8540 switch routers. Examples The following sample output from the show controllers c8500 ipmcast command displays routing table control layer information for an IP multicast group: Router# show controllers c8500 ipmcast 231.1.1.1 all
(*, 231.1.1.1), RPF NULL, root vc 0/0
(171.11.78.77, 231.1.1.1), RPF BVI1, root vc 1/33
FastEthernet0/0/7, root vc 1/33
shr_vc_db vc 1/33, usage_count 1, olist size 2
FastEthernet0/0/0, root vc 1/33
shr_vc_db vc 1/33, usage_count 1, olist size 2
FastEthernet0/0/3, root vc 1/33
shr_vc_db vc 1/33, usage_count 1, olist size 1
Table A-7 describes some of the fields in the previous display. Table A-7: show controllers c8500 ipmcast Field Descriptions
The following sample output from the show controllers c8500 ipmcast command displays VC sharing information for an IP multicast group: Router# show controllers c8500 ipmcast 231.1.1.1 vc-sharing FastEthernet0/0/0 vc 1/36, usage count:1 FastEthernet0/0/3 vc 1/36, usage count:1 FastEthernet0/0/7 vc 1/36, usage count:1 The following sample output from the show controllers c8500 ipmcast command displays general debugging statistics: Router# show controllers c8500 ipmcast stats
LSS Mroute General Statistics:
# of times p2mp vc are created 6
# of times p2mp vc are released 3
# of times failed to create p2mp vc's 0
# of times failed to release p2mp vc's 0
# of times stats IPC polls sent 15
# of times stats IPC polls received 15
# of times mroute entries created 6
# of times mroute entries deleted 0
# of times mroute flags modified 32
# of times mroute rpf changed 0
# of times midb changed 9
# of times sidb updated 4
# of times add member IPCs sent 2
# of times add member IPC failed 0
# of times add group IPCs sent 11
# of times add group IPCs failed 0
# of times spt flag changed 2
# of times register flag changed 0
# of times mroute nofs changed 4
# of times fastdrop sets 0
# of times fastdrop clears 0
# of times shared vc db created 6
# of times shared vc db freed 3
# of times shared vc hash table created 5
# of times shared vc hash table freed 4
# of times shared oif db created 10
# of times shared oif db freed 5
lss_index_array usuage: start_index = 35, end_index = 33
vc 1/34, count 3
show controllers c8500 ipx-nodeTo display the specified node entry for all interfaces, use the show controllers c8500 ipx-node EXEC command. show controllers c8500 ipx-node node-numSyntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays information specific to the Catalyst 8510 and Catalyst 8540 switch routers. Examples The following is sample output from the show controllers c8500 ipx-node command: Router# show controllers c8500 ipx-node 101010.00d0.5845.2662 Codes:V - valid entry, M - My-node, I - IF/VC flag Interface Network Node IF Number Flags GigabitEthernet1/0/0 101010 00d0.5845.2662 18 MV GigabitEthernet1/1/0 101010 00d0.5845.2662 18 MV FastEthernet10/0/0 101010 00d0.5845.2662 18 IMV FastEthernet10/0/1 101010 00d0.5845.2662 18 IMV FastEthernet10/0/2 101010 00d0.5845.2662 18 IMV FastEthernet10/0/3 101010 00d0.5845.2662 18 IMV FastEthernet10/0/4 101010 00d0.5845.2662 18 IMV FastEthernet10/0/5 101010 00d0.5845.2662 18 IMV FastEthernet10/0/6 101010 00d0.5845.2662 18 IMV FastEthernet10/0/7 101010 00d0.5845.2662 18 IMV FastEthernet10/0/8 101010 00d0.5845.2662 18 IMV FastEthernet10/0/9 101010 00d0.5845.2662 18 IMV FastEthernet10/0/10 101010 00d0.5845.2662 18 IMV FastEthernet10/0/11 101010 00d0.5845.2662 18 IMV FastEthernet10/0/12 101010 00d0.5845.2662 18 IMV FastEthernet10/0/13 101010 00d0.5845.2662 18 IMV FastEthernet10/0/14 101010 00d0.5845.2662 18 IMV FastEthernet10/0/15 101010 00d0.5845.2662 18 IMV show controller c8500 ipx-prefixTo display IPX network entries for a specified network for all interfaces, use the show controller c8500 ipx-prefix EXEC command. show controller c8500 ipx-prefix prefixSyntax Description
Command Modes Privileged EXEC Usage Guidelines This command displays information specific to the Catalyst 8510 and Catalyst 8540 switch routers. Examples The following is sample output from the show controller c8500 ipx-prefix command for all entries: Router# show controllers f10/0/9 ipx-prefix all-entries
IPX Prefix Entries in CAM, Interface FastEthernet10/0/9
-----------------------------------------------------------------
Codes:C - Connected network, R - Remote network
V - valid entry, N - Network entry
L - load balancing enabled, D - default network
E - EIGRP enabled, I - Internal network
B - BVI network, M - My Mac Address
VC - VCI
C 1009 V N
Novell ether IF No 14 00d0.5845.2660 My-Node Valid
R 5004 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 5005 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 5006 V N
Novell ether IF No 24 00d0.bbcd.b40e Valid
R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
The following is sample output from the show controller c8500 ipx-prefix command for a specified IPX network: Router# show controllers c8500 ipx-prefix 101010
GigabitEthernet1/0/0 R 101010 V B
Novell ether IF No 8 00d0.5845.265a My-Node Valid
GigabitEthernet1/1/0 R 101010 V B
Novell ether IF No 8 00d0.5845.265a My-Node Valid
FastEthernet10/0/0 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/1 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/2 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/3 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/4 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/5 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/6 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/7 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/8 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/9 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/10 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/11 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/12 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/13 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/14 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
FastEthernet10/0/15 R 101010 V N B
Novell ether IF No 24 00d0.5845.2662 My-Node Valid
show controllers c8500 queuingTo display current queuing information for all well-known static VCs in the system, use the show controllers c8500 queuing EXEC command. show controllers c8500 queuingSyntax Description This command has no arguments or keywords. Command Modes Privileged EXEC. Usage Guidelines This command displays information specific to the Catalyst 8510 and Catalyst 8540 switch routers. Examples The following is sample output from the show controllers c8500 queuing command: Router# show controllers c8500 queuing INT X-INT VCI QCNT VCI QCNT f0/0/0 SRP 34 0 40 400 Table A-8 describes the fields in the display. Table A-8: show controllers c8500 queuing Field Descriptions
show switch countersTo display the counters on the switch router's interfaces, use the show switch counters EXEC command. show switch countersSyntax Description This command has no arguments or keywords Command Modes Privileged EXEC Usage Guidelines This command does not use IPC to get the information and can be used to find the port state prior to using any IPC-based commands, such as the show controllers command. The counts reflect the actual number that the interface has received; these counter values are not reset when the clear counters command is issued. Examples The following is sample output from the show switch counters command: Router# show switch counters
Interface Input Runts Giants Input CRC Frame Output Output
State Packets Errors Packets Errors
-----------------------------------------------------------------------------
G9/0/0 AD 0 0 0 0 0 0 0 0
G9/0/1 AD 0 0 0 0 0 0 0 0
ATM10/0 U 112459 0 0 0 0 0 112459 0
ATM10/0 U 116132 0 0 0 0 0 116132 0
F11/0/0 AD 0 0 0 0 0 0 0 0
F11/0/1 AD 0 0 0 0 0 0 0 0
F11/0/2 AD 0 0 0 0 0 0 0 0
F11/0/3 AD 0 0 0 0 0 0 0 0
F11/0/4 U 1011 0 0 0 0 0 30379 0
F11/0/5 U 0 0 0 0 0 0 29547 0
F11/0/6 AD 0 0 0 0 0 0 0 0
F11/0/7 AD 0 0 0 0 0 0 0 0
F11/0/8 AD 0 0 0 0 0 0 0 0
F11/0/9 U 0 0 0 0 0 0 0 0
F11/0/10AD 0 0 0 0 0 0 0 0
F11/0/11AD 0 0 0 0 0 0 0 0
F11/0/12AD 0 0 0 0 0 0 0 0
F11/0/13AD 0 0 0 0 0 0 0 0
F11/0/14AD 0 0 0 0 0 0 0 0
F11/0/15U 0 0 0 0 0 0 0 0
-----------------------------------------------------------------------------
AD - Admin Down, D - Down, F - Fail, U - Up
Port Commandsepc port-reloadTo indicate that a port detected as being stuck should be reset and reloaded, use the epc port-reload command. To indicate that a port detected as being stuck should be shut down, use the no form of the command. epc port-reloadno epc port-reload Syntax Description This command has no arguments or keywords. Command Modes Global configuration Usage Guidelines The epc port-reload command specifies how the system should respond when a port is detected as being stuck. If a port does not respond for a specified duration of time (set with the epc portstuck-wait command) to messages sent by the CPU, the port is declared stuck. If the epc port-reload command is in effect, the stuck port is reset and its microcode is reloaded so that it resumes normal operation. If the no epc port-reload command is in effect, the port is shut down. Examples The following example shows how to specify that a port detected as being stuck should be reset and reloaded: Router(config)# epc port-reload Related Commands epc portstuck-waitTo specify how long the port-stuck detection mechanism should wait after a port has stopped responding to CPU requests, use the epc portstuck-wait command. To set this value to its default, use the no epc portstuck-wait command. epc portstuck-wait secondsSyntax Description
Defaults 180 seconds Command Modes Global configuration Syntax Description For a port to be declared stuck, no response to any requests must be received by the CPU for the length of time specified by the epc portstuck-wait command. Once this time has elapsed with no response, the port is declared stuck and the action specified in the epc port-reload command is taken. Examples The following example shows how to specify a wait time of four minutes before declaring a port stuck: Router# epc portstuck-wait 240 Related Commands
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|