|
|
This appendix provides a command reference for those Cisco IOS commands---or aspects of the commands---that are unique to Layer 3 switching.
Port 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.
To set up port-based traffic mirroring, or snooping, use the snoop command. To disable snooping, use the no form of this command.
snoop interface source-port direction snoop-direction
source-port | Number of the port or ports being monitored. |
direction | Direction of traffic on the source port or ports that is monitored: receive, transmit, or both. |
Snooping is disabled on all interfaces.
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.
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 fa 12/0/15 8500CSR(config-if)# shutdown 8500CSR(config-if)# snoop interface fa 0/0/1 direction both 8500CSR(config-if)# no shutdown
show snoop
To display the current snooping sessions, use the show snoop command.
show snoop [interface destination-port]
destination-port | Number of the snooping interface. |
Privileged EXEC
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)
show snoop-vc
To display the virtual circuits being used by the snooping feature, use the show snoop-vc command.
show snoop-vc [interface destination-port]
destination-port | Snoop monitoring port. |
Privileged EXEC
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
.........
show snoop
To enable Quality of Service (QoS) mapping on the device, use the qos switching command. To disable it, use the no form of this command.
qos switchingThis command has no keywords or arguments.
QoS mapping is enabled.
Global configuration
The following example shows how to enable QoS mapping using the qos switching configuration command.
8500CSR(config)# qos switching
qos mapping-precedence
To 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.
qos mapping [source source-int] [destination dest-int] precedence value wrr-weight weight
source-int | Source interface from which you want to define a traffic precedence; optional. |
dest-int | Destination interface to which you want to define a traffic precedence; optional. |
value | The precedence value (0 to 3) is derived from the IP precedence field. The higher 2-bits of the IP precedence field is used. When a precedence value x is specified, it also implicitly assigns the same WRR-weight to precedence |
weight | The WRR-scheduling weight (1 to 15). This parameter specifies the weight assigned to traffic with the given precedence. |
The default WRR-weight for a precedence value n is 2 ^ n.
Global configuration
When a precedence value n is specified, it implicitly assigns the same WRR-weight to the precedence n + 1.
The following example shows how to set the system-level QoS mapping using the
qos mapping precedence configuration command.
8500CSR(config)# qos mapping precedence 0 wrr-weight 4
qos switching
To show whether QoS mapping is enabled on the device, use the show qos switching command.
show qos switchingThis command has no keywords or arguments.
Privileged EXEC
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
show qos mapping
To 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]
source-int | Source interface from which you want to display QoS mapping; optional. |
dest-int | Destination interface to which you want to display QoS mapping; optional. |
Privileged EXEC
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
show qos switching
To switch to the redundancy mode, use the redundancy global configuration command.
redundancyThis command has no arguments or keywords.
Global configuration
To enter the main-cpu mode of redundancy mode, use the main-cpu command.
The following example shows how to enter the redundancy mode.
Router(config)# redundancy Router(config-r)#
The following example shows how to switch to the main-cpu submode of redundancy mode.
Router(config-r)#main-cpuRouter(config-r-mc)#
auto-sync
main-cpu
primary-cpu preferred
redundancy force-failover main-cpu
show redundancy
To 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-cpuThis command has no arguments or keywords.
Privileged EXEC
If the secondary route processor is in ROMMON mode it becomes the primary route processor but continues in the ROMMON mode, meaning that the IOS does not automatically open.
The following example shows how to make the secondary route processor the primary.
Router# redundancy force-failover main-cpu
show redundancy
To 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.
primary-cpu preferred [slot4 | slot8]
slot4 | slot8 | Specifies either slot 4 or slot 8 of the ATM switch. |
No preferred route processor.
Redundancy
The primary route processor is determined based on the previous configuration.
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
auto-sync
redundancy force-failover main-cpu
show redundancy
To 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}
primary | Displays the capabilities of the primary route processor. |
secondary | Displays the capabilities of the secondary route processor. |
Privileged EXEC
The show capability display includes hardware and functional versions of the various components.
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
To list all redundancy-related information, use the show redundancy Privileged EXEC command.
show redundancyThis command has no arguments or keywords.
Privileged EXEC
This command is available on the primary route processor only.
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)
Posted: Wed Dec 22 14:12:18 PST 1999
Copyright 1989-1999©Cisco Systems Inc.