- aaa authentication dot1x
- action
- archive copy-sw
- archive download-sw
- archive tar
- archive upload-sw
- auto qos voip
- boot auto-copy-sw
- boot boothlpr
- boot config-file
- boot enable-break
- boot helper
- boot helper-config-file
- boot manual
- boot private-config-file
- boot system
- channel-group
- channel-protocol
- class
- class-map
- clear lacp
- clear mac address-table
- clear pagp
- clear setup express
- clear spanning-tree counters
- clear spanning-tree detected-protocols
- clear vmps statistics
- clear vtp counters
- cluster commander-address
- cluster discovery hop-count
- cluster enable
- cluster holdtime
- cluster member
- cluster outside-interface
- cluster run
- cluster standby-group
- cluster timer
- define interface-range
- delete
- deny
- dot1x default
- dot1x guest-vlan
- dot1x host-mode
- dot1x initialize
- dot1x max-req
- dot1x multiple-hosts
- dot1x port-control
- dot1x re-authenticate
- dot1x re-authentication
- dot1x reauthentication
- dot1x system-auth-control
- dot1x timeout
- duplex
- errdisable detect cause
- errdisable recovery
- flowcontrol
- interface port-channel
- interface range
- interface vlan
- ip access-group
- ip address
- ip igmp filter
- ip igmp max-groups
- ip igmp profile
- ip igmp snooping
- ip igmp snooping report-suppression
- ip ssh
- lacp port-priority
- lacp system-priority
- logging file
- mac access-group
- mac access-list extended
- mac address-table aging-time
- mac address-table notification
- mac address-table static
- mac address-table static drop
- match (access-map configuration)
- match (class-map configuration)
- mdix auto
- mls qos
- mls qos aggregate-policer
- mls qos cos
- mls qos dscp-mutation
- mls qos map
- mls qos queue-set output buffers
- mls qos queue-set output threshold
- mls qos srr-queue input bandwidth
- mls qos srr-queue input buffers
- mls qos srr-queue input cos-map
- mls qos srr-queue input dscp-map
- mls qos srr-queue input priority-queue
- mls qos srr-queue input threshold
- mls qos srr-queue output cos-map
- mls qos srr-queue output dscp-map
- mls qos trust
- monitor session
- mvr (global configuration)
- mvr (interface configuration)
- pagp learn-method
- pagp port-priority
- permit
- police
- police aggregate
- policy-map
- port-channel load-balance
- priority-queue
- queue-set
- rcommand
- reload
- remote command
- remote-span
Cisco IOS Commands
aaa authentication dot1x
Use the aaa authentication dot1x global configuration command on the switch stack or on a standalone switch to specify one or more authentication, authorization, and accounting (AAA) methods for use on interfaces running IEEE 802.1X. Use the no form of this command to disable authentication.
aaa authentication dot1x {default} method1 [method2...]
no aaa authentication dot1x {default}
Syntax Description
Note Though visible in the command-line help strings, the group tacacs+ keyword is not supported.
Defaults
No authentication is performed.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The method argument identifies the list of methods that the authentication algorithm tries in the given sequence to validate the password provided by the client. The only method that is truly 802.1X-compliant is the group radius method, in which the client data is validated against a RADIUS authentication server. The remaining methods enable AAA to authenticate the client by using locally configured data. For example, the local and local-case methods use the username and password that are saved in the IOS configuration file. The enable and line methods use the enable and line passwords for authentication.
If you specify group radius, you must configure the RADIUS server by entering the radius-server host global configuration command.
If you are not using a RADIUS server, you can use the local or local-case methods, which access the local username database to perform authentication. By specifying the enable or line methods, you can supply the clients with a password to provide access to the switch.
Use the show running-config privileged EXEC command to display the configured lists of authentication methods.
Examples
This example shows how to enable AAA and how to create an authentication list for 802.1X. This authentication first tries to contact a RADIUS server. If this action returns an error, the user is allowed access with no authentication.
Switch(config)# aaa new-model
Switch(config)# aaa authentication dot1x default group radius none
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
action
Use the action access map configuration command on the switch stack or on a standalone switch to set the action for the VLAN access map entry. Use the no form of this command to set the action to the default value, which is to forward.
action {drop | forward}
no action
Syntax Description
drop |
Drop the packet when the specified conditions are matched. |
forward |
Forward the packet when the specified conditions are matched. |
Defaults
The default action is to forward packets.
Command Modes
Access-map configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You enter access-map configuration mode by using the vlan access-map global configuration command.
If the action is drop, you should define the access map, including configuring any access control list (ACL) names in match clauses, before applying the map to a VLAN, or all packets could be dropped.
In access map configuration mode, use the match access map configuration command to define the match conditions for a VLAN map. Use the action command to set the action that occurs when a packet matches the conditions.
The drop and forward parameters are not used in the no form of the command.
Examples
This example shows how to identify and apply a VLAN access map vmap4 to VLANs 5 and 6 that causes the VLAN to forward an IP packet if the packet matches the conditions defined in access list al2:
Switch(config)# vlan access-map vmap4
Switch(config-access-map)# match ip address al2
Switch(config-access-map)# action forward
Switch(config-access-map)# exit
Switch(config)# vlan filter vmap4 vlan-list 5-6
You can verify your settings by entering the show vlan access-map privileged EXEC command.
Related Commands
archive copy-sw
Use the archive copy-sw privileged EXEC command on the stack master to copy the running image from the Flash memory on one stack member to the Flash memory on one or more other stack members.
archive copy-sw source stack-member-number /destination-system {/force-reload | /leave-old-sw | /no-set-boot | overwrite | /reload | /safe} destination-stack-member-number
Syntax Description
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The current software image is not overwritten with the downloaded image.
Both the software image and HTML files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
You can copy the image to more than one specific stack member by repeating the /destination-system destination-stack-member-number option in the command for each stack member to be upgraded. If you do not specify the destination-stack-member-number, the default is to copy the running image file to all stack members.
Using the /safe or /leave-old-sw option can cause the new image download to fail if there is insufficient Flash memory. If leaving the software in place would prevent the new image from fitting in Flash memory due to space constraints, an error results.
If you used the /leave-old-sw option and did not overwrite the old image when you downloaded the new one, you can remove the old image by using the delete privileged EXEC command. For more information, see the "delete" section.
Use the /overwrite option to overwrite the image on the Flash device with the downloaded one.
If you specify the command without the /overwrite option, the download algorithm verifies that the new image is not the same as the one on the switch Flash device or is not running on any stack members. If the images are the same, the download does not occur. If the images are different, the old image is deleted, and the new one is downloaded.
After downloading a new image, enter the reload privileged EXEC command to begin using the new image, or specify the /reload or /force-reload option in the archive download-sw command.
Examples
This example shows how to copy the running image from stack member 6 to stack member 8:
Switch# archive copy-sw 6 /destination-system 8
Related Commands
archive download-sw
Use the archive download-sw privileged EXEC command on the switch stack or on a standalone switch to download a new image to the switch or switch stack and to overwrite or keep the existing image.
archive download-sw {/force-reload | /imageonly | /leave-old-sw | /no-set-boot | /no-version-check | /destination-system stack-member-number | /only-system-type system-type | /overwrite | /reload | /safe} source-url
Syntax Description
Defaults
The current software image is not overwritten with the downloaded image.
Both the software image and HTML files are downloaded.
The new image is downloaded to the flash: file system.
The BOOT environment variable is changed to point to the new software image on the flash: file system.
Image names are case sensitive; the image file is provided in tar format.
Compatibility of the stack protocol version on the image to be downloaded is checked with the version on the switch stack.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The /imageonly option removes the HTML files for the existing image if the existing image is being removed or replaced. Only the IOS image (without the HTML files) is downloaded.
Using the /safe or /leave-old-sw option can cause the new image download to fail if there is insufficient Flash memory. If leaving the software in place prevents the new image from fitting in Flash memory due to space constraints, an error results.
If you used the /leave-old-sw option and did not overwrite the old image when you downloaded the new one, you can remove the old image by using the delete privileged EXEC command. For more information, see the "delete" section.
Use the /no-version-check option if you want to download an image that has a different stack protocol version than the one existing on the switch stack. You must use this option with the /destination-system option to specify the specific stack member to be upgraded with the image.
Note Use the /no-version-check option with care. All stack members, including the stack master, must have the same stack protocol version to be in the same switch stack. This option allows an image to be downloaded without first confirming the compatibility of its stack protocol version with the version of the switch stack.
You can upgrade more than one specific stack member by repeating the /destination-system option in the command for each stack member to be upgraded.
Use the /overwrite option to overwrite the image on the Flash device with the downloaded one.
If you specify the command without the /overwrite option, the download algorithm verifies that the new image is not the same as the one on the switch Flash device or is not running on any stack members. If the images are the same, the download does not occur. If the images are different, the old image is deleted, and the new one is downloaded.
After downloading a new image, enter the reload privileged EXEC command to begin using the new image, or specify the /reload or /force-reload option in the archive download-sw command.
Examples
This example shows how to download a new image from a TFTP server at 172.20.129.10 and overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://172.20.129.10/test-image.tar
This example shows how to download only the software image from a TFTP server at 172.20.129.10 to the switch:
Switch# archive download-sw /image-only tftp://172.20.129.10/test-image.tar
This example shows how to keep the old software version after a successful download:
Switch# archive download-sw /leave-old-sw tftp://172.20.129.10/test-image.tar
This example shows how to specifically upgrade stack members 6 and 8:
Switch# archive download-sw /image-only tftp://172.20.129.10/test-image.tar
/destination-system 6 /destination-system 8
Related Commands
archive tar
Use the archive tar privileged EXEC command on the switch stack or on a standalone switch to create a tar file, list files in a tar file, or extract the files from a tar file.
archive tar {/create destination-url flash:/file-url} | {/table source-url} | {/xtract source-url flash:/file-url}
Syntax Description
Defaults
None
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Filenames and directory names are case sensitive.
Image names are case sensitive.
Examples
This example shows how to create a tar file. The command writes the contents of the new-configs directory on the local Flash device to a file named saved.tar on the TFTP server at 172.20.10.30:
Switch# archive tar /create tftp:172.20.10.30/saved.tar flash:/new-configs
This example shows how to display the contents of the c29703750-tv0-m.tar file that is in Flash memory. The contents of the tar file are displayed on the screen:
Switch# archive tar /table flash:c29703750-tv0-m.tar
info (219 bytes)
c29703750-tv0-mz-121/ (directory)
c29703750-tv0-mz-121/html/ (directory)
c29703750-tv0-mz-121/html/foo.html (0 bytes)
c29703750-tv0-mz-121/vegas-tv0-mz-121.bin (610856 bytes)
c29703750-tv0-mz-121/info (219 bytes)
info.ver (219 bytes)
This example shows how to display only the c29703750-tv0-mz-121/html directory and its contents:
Switch# archive tar /table flash:c29703750-tv0-m.tar c29703750-tv0-mz-121/html
c29703750-tv0-mz-121/html/ (directory)
c29703750-tv0-mz-121/html/foo.html (0 bytes)
This example shows how to extract the contents of a tar file on the TFTP server at 172.20.10.30. This command extracts just the new-configs directory into the root directory on the local Flash file system. The remaining files in the saved.tar file are ignored.
Switch# archive tar /xtract tftp:/172.20.10.30/saved.tar flash:/ new-configs
Related Commands
archive upload-sw
Use the archive upload-sw privileged EXEC command on the switch stack or on a standalone switch to upload an existing switch image to a server.
archive upload-sw [/source-system-num stack member number | /version version_string] destination-url
Syntax Description
Defaults
Uploads the currently running image from the flash: file system.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You must specify the /source-system-num option to use the /version option. Using these options together uploads the specified image, not the running image, of a specific stack member.
The upload feature is available only if the HTML files associated with the Cluster Management Suite (CMS) have been installed with the existing image.
The files are uploaded in this sequence: the IOS image, the HTML files, and info. After these files are uploaded, the software creates the tar file.
Image names are case sensitive.
Examples
This example shows how to upload the currently running on stack member 6 image to a TFTP server at 172.20.140.2:
Switch# archive upload-sw /source-system-num 6 tftp://172.20.140.2/test-image.tar
Related Commands
auto qos voip
Use the auto qos voip interface configuration command on the switch stack or on a standalone switch to automatically configure quality of service (QoS) for voice over IP (VoIP) within a QoS domain. Use the no form of this command to return to the default setting.
auto qos voip {cisco-phone | trust}
no auto qos voip [cisco-phone | trust]
Syntax Description
Defaults
Auto-QoS is disabled on the interface.
When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels, and to configure the ingress and egress queues as shown in Table 2-1.
|
Traffic |
|
|
|
||
---|---|---|---|---|---|---|
Ingress DSCP3 |
46 |
26 |
- |
- |
- |
|
Ingress CoS4 |
5 |
3 |
6 |
7 |
- |
|
DiffServ |
EF |
AF31 |
- |
- |
- |
|
Assigned DSCP |
46 |
26 |
48 |
56 |
0 |
|
Assigned CoS |
5 |
3 |
6 |
7 |
0 |
|
CoS-to-Ingress Queue Map |
2, 3, 4, 5, 6, 7 (queue 2) |
0, 1 (queue 1) |
||||
CoS-to-Egress Queue Map |
5 (queue 1) |
3, 6, 7 (queue 2) |
2, 4 (queue 3) |
0, 1 (queue 4) |
1 STP = Spanning Tree Protocol 2 BPDU = bridge protocol data unit 3 DSCP = Differentiated Services Code Point 4 CoS = class of service |
Table 2-2 shows the generated auto-QoS configuration for the ingress queues.
|
|
|
|
|
---|---|---|---|---|
SRR1 shared |
1 |
0, 1 |
90 percent |
90 percent |
Priority |
2 |
2, 3, 4, 5, 6, 7 |
10 percent |
10 percent |
1 SRR = shaped round robin. Ingress queues support shared mode only. |
Table 2-3 shows the generated auto-QoS configuration for the egress queues.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
Use this command to configure the QoS appropriate for VoIP traffic within the QoS domain. The QoS domain includes the switch, the interior of the network, and edge devices that can classify incoming traffic for QoS.
To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.
Note The switch applies the auto-QoS-generated commands as if the commands were entered from the command-line interface (CLI). An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands fail to be applied, the previous running configuration is restored.
If this is the first interface on which you have enabled auto-QoS, the auto-QoS-generated global configuration commands are executed followed by the interface configuration commands. If you enable auto-QoS on another interface, only the auto-QoS-generated interface configuration commands for that interface are executed.
When you enable the auto-QoS feature on the first interface, these automatic actions occur:
•QoS is globally enabled (mls qos global configuration command), and other global configuration commands are added.
•When you enter the auto qos voip cisco-phone interface configuration command on a port at the edge of the network that is connected to a Cisco IP phone, the switch enables the trusted boundary feature. The switch uses the Cisco Discovery Protocol (CDP) to detect the presence or absence of a Cisco IP phone. When a Cisco IP phone is detected, the ingress classification on the interface is set to trust the QoS label received in the packet. When a Cisco IP phone is absent, the ingress classification is set to not trust the QoS label in the packet. The switch configures ingress and egress queues on the interface according to the settings in Table 2-2 and Table 2-3.
•When you enter the auto qos voip trust interface configuration command on a port connected to the interior of the network, the switch trusts the CoS value for nonrouted interfaces or the DSCP value for routed interfaces in ingress packets (the assumption is that traffic has already been classified by other edge devices). The switch configures the ingress and egress queues on the interface according to the settings in Table 2-2 and Table 2-3.
You can enable auto-QoS on static, dynamic-access, and voice VLAN access, and trunk ports.
To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug autoqos privileged EXEC command to enable auto-QoS debugging. For more information, see the "debug autoqos" section.
To disable auto-QoS on an interface, use the no auto qos voip interface configuration command. Only the auto-QoS-generated interface configuration commands for this interface are removed. If this is the last interface on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other interfaces affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
Examples
This example shows how to enable auto-QoS and to trust the QoS labels received in incoming packets when the switch or router connected to Gigabit Ethernet interface 0/1 on stack member 2 is a trusted device:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# auto qos voip trust
You can verify your settings by entering the show auto qos interface interface-id privileged EXEC command.
Related Commands
|
|
---|---|
Enables debugging of the auto-QoS feature. |
|
Defines the default CoS value of a port or assigns the default CoS to all incoming packets on the port. |
|
mls qos map {cos-dscp dscp1 ... dscp8 | dscp-cos dscp-list to cos} |
Defines the CoS-to-DSCP map or the DSCP-to-CoS map. |
Allocates buffers to a queue-set. |
|
Assigns shaped round robin (SRR) weights to an ingress queue. |
|
Allocates the buffers between the ingress queues. |
|
Maps CoS values to an ingress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps DSCP values to an ingress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the ingress priority queue and guarantees bandwidth. |
|
Maps CoS values to an egress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps DSCP values to an egress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the port trust state. |
|
Maps a port to a queue-set. |
|
Displays the initial configuration that is generated by the auto-QoS feature. |
|
Displays QoS information at the interface level. |
|
Assigns the shaped weights and enables bandwidth shaping on the four egress queues mapped to a port. |
|
Assigns the shared weights and enables bandwidth sharing on the four egress queues mapped to a port. |
boot auto-copy-sw
Use the boot auto-copy-sw global configuration command from the stack master to automatically upgrade switches in version-mismatch (VM) mode with the switch stack image. Use the no form of this command to not automatically upgrade switches in VM mode.
boot auto-copy-sw
no boot auto-copy-sw
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
A switch in version-mismatch (VM) mode is a switch that has a different stack protocol version than the version on the switch stack. Switches in VM mode cannot join the switch stack. If the switch stack has an image that can be copied to a switch in VM mode, this command automatically copies the switch in VM mode with the image from another stack member. The switch then exits VM mode, reboots, and joins the switch stack.
This command affects only switches in VM mode. It does not affect existing stack members.
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
|
Displays version information for the hardware and firmware. |
boot boothlpr
Use the boot boothlpr global configuration command on the switch stack or on a standalone switch to load a special IOS image, which when loaded into memory, can load a second IOS image into memory and launch it. This variable is used only for internal development and testing. Use the no form of this command to return to the default setting.
boot boothlpr filesystem:/file-url
no boot boothlpr
Syntax Description
filesystem: |
Alias for a Flash file system. Use flash: for the system board Flash device. |
/file-url |
The path (directory) and name of a bootable helper image. |
Defaults
No helper image is loaded.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Filenames and directory names are case sensitive.
This command changes the setting of the BOOTHLPR environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot config-file
Use the boot config-file global configuration command on a standalone switch to specify the filename that IOS uses to read and write a nonvolatile copy of the system configuration. Use the no form of this command to return to the default setting.
boot config-file flash:/file-url
no boot config-file
Syntax Description
flash:/file-url |
The path (directory) and name of the configuration file. |
Defaults
The default configuration file is flash:config.text.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command works properly only from a standalone switch.
Filenames and directory names are case sensitive.
This command changes the setting of the CONFIG_FILE environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot enable-break
Use the boot enable-break global configuration command on a standalone switch to enable interrupting the automatic boot process. Use the no form of this command to return to the default setting.
boot enable-break
no boot enable-break
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled. The automatic boot process cannot be interrupted by pressing the Break key on the console.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command works properly only from a standalone switch.
When you enter this command, you can interrupt the automatic boot process by pressing the Break key on the console after the Flash file system is initialized.
Note Despite the setting of this command, you can interrupt the automatic boot process at any time by pressing the MODE button on the switch front panel.
This command changes the setting of the ENABLE_BREAK environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot helper
Use the boot helper global configuration command on the switch stack or on a standalone switch to dynamically load files during boot loader initialization to extend or patch the functionality of the boot loader. Use the no form of this command to return to the default.
boot helper filesystem:/file-url ...
no boot helper
Syntax Description
Defaults
No helper files are loaded.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot helper-config-file
Use the boot helper-config-file global configuration command on the switch stack or on a standalone switch to specify the name of the configuration file to be used by the IOS helper image. If this is not set, the file specified by the CONFIG_FILE environment variable is used by all versions of IOS that are loaded. Use the no form of this command to return to the default setting.
boot helper-config-file filesystem:/file-url
no boot helper-config file
Syntax Description
filesystem: |
Alias for a Flash file system. Use flash: for the system board Flash device. |
/file-url |
The path (directory) and helper configuration file to load. |
Defaults
No helper configuration file is specified.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This variable is used only for internal development and testing.
Filenames and directory names are case sensitive.
This command changes the setting of the HELPER_CONFIG_FILE environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot manual
Use the boot manual global configuration command on a standalone switch to enable manually booting the switch during the next boot cycle. Use the no form of this command to return to the default setting.
boot manual
no boot manual
Syntax Description
This command has no arguments or keywords.
Defaults
Manual booting is disabled.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command works properly only from a standalone switch.
The next time you reboot the system, the switch is in boot loader mode, which is shown by the switch: prompt. To boot the system, use the boot boot loader command, and specify the name of the bootable image.
This command changes the setting of the MANUAL_BOOT environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot private-config-file
Use the boot private-config-file global configuration command on a standalone switch to specify the filename that IOS uses to read and write a nonvolatile copy of the private configuration. Use the no form of this command to return to the default setting.
boot private-config-file filename
no boot private-config-file
Syntax Description
filename |
The name of the private configuration file. |
Defaults
The default configuration file is private-config.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command works properly only from a standalone switch.
Filenames are case sensitive.
Examples
This example shows how to specify the name of the private configuration file to be pconfig:
Switch(config)#
boot private-config-file pconfig
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
boot system
Use the boot system global configuration command on a standalone switch to specify the IOS image to load during the next boot cycle. Use the no form of this command to return to the default setting.
boot system filesystem:/file-url ...
no boot system
Syntax Description
filesystem: |
Alias for a Flash file system. Use flash: for the system board Flash device. |
/file-url |
The path (directory) and name of a bootable image. Separate image names with a semicolon. |
Defaults
The switch attempts to automatically boot the system by using information in the BOOT environment variable. If this variable is not set, the switch attempts to load and execute the first executable image it can by performing a recursive, depth-first search throughout the Flash file system. In a depth-first search of a directory, each encountered subdirectory is completely searched before continuing the search in the original directory.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command works properly only from a standalone switch.
Filenames and directory names are case sensitive.
If you are using the archive download-sw privileged EXEC command to maintain system images, you never need to use the boot system command. The boot system command is automatically manipulated to load the downloaded image.
This command changes the setting of the BOOT environment variable. For more information, see "Boot Loader Commands."
Related Commands
|
|
---|---|
Displays the settings of the boot environment variables. |
channel-group
Use the channel-group interface configuration command on the switch stack or on a standalone switch to assign an Ethernet interface to an EtherChannel group. Use the no form of this command to remove an Ethernet interface from an EtherChannel group.
channel-group channel-group-number mode {active | {auto [non-silent] | desirable [non-silent] | on} | passive}
no channel-group
Syntax Description
Defaults
No channel groups are assigned.
No mode is configured.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
The active and passive keywords were added. |
Usage Guidelines
For Layer 2 EtherChannels, you do not have to create a port-channel interface first by using the interface port-channel global configuration command before assigning a physical interface to a channel group. Instead, you can use the channel-group interface configuration command. It automatically creates the port-channel interface when the channel group gets its first physical interface if the logical interface is not already created. If you create the port-channel interface first, the channel-group-number can be the same as the port-channel-number, or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel.
You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but we strongly recommend that you do so.
You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. You should manually configure the port-channel logical interface before putting the interface into the channel group.
After you configure an EtherChannel, configuration changes that you make on the port-channel interface apply to all the physical interfaces assigned to the port-channel interface. Configuration changes applied to the physical interface affect only the interface where you apply the configuration. To change the parameters of all ports in an EtherChannel, apply configuration commands to the port-channel interface, for example, spanning-tree commands or commands to configure a Layer 2 EtherChannel as a trunk.
If you do not specify non-silent with the auto or desirable mode, silent is assumed. The silent mode is used when the switch is connected to a device that is not PAgP-capable and seldom, if ever, sends packets. A example of a silent partner is a file server or a packet analyzer that is not generating traffic. In this case, running PAgP on a physical port prevents that port from ever becoming operational. However, it allows PAgP to operate, to attach the interface to a channel group, and to use the interface for transmission. Both ends of the link cannot be set to silent.
With the on mode, a usable EtherChannel exists only when a port group in the on mode is connected to another port group in the on mode. The on keyword is the only setting that is supported when the EtherChannel members are from different switches in the switch stack (cross-stack EtherChannel).
Do not configure an EtherChannel in both the PAgP and LACP modes. EtherChannel groups running PAgP and LACP can coexist on the same switch or on different switches in the stack (but not in a cross-stack configuration). Individual EtherChannel groups can run either PAgP or LACP, but they cannot interoperate.
If you set the protocol by using the channel-protocol interface configuration command, the setting is not overridden by the channel-group interface configuration command
Do not configure a port that is an active member of an EtherChannel as an 802.1X port. If 802.1X is enabled on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.
Do not configure a secure port as part of an EtherChannel or an EtherChannel port as a secure port.
For a complete list of configuration guidelines, refer to the "Configuring EtherChannels" chapter in the software guide for this release.
Examples
This example shows how to configure EtherChannel on a single switch in the stack. It assigns Gigabit Ethernet interfaces 0/4 and 0/5 on stack member 2 as static-access ports in VLAN 10 to channel 5 with the PAgP mode desirable:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode desirable
Switch(config-if-range)# end
This example shows how to configure EtherChannel on a single switch in the stack. It assigns Gigabit Ethernet interfaces 0/4 and 0/5 on stack member 2 as static-access ports in VLAN 10 to channel 5 with the LACP mode active:
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode active
Switch(config-if-range)# end
This example shows how to configure cross-stack EtherChannel. It assigns Gigabit Ethernet interfaces 0/4 and 0/5 on stack member 2 and Gigabit Ethernet interface 0/3 on stack member 3 as static-access ports in VLAN 10 to channel 5 with the PAgP and LACP modes disabled (on):
Switch# configure terminal
Switch(config)# interface range gigabitethernet2/0/4 -5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# channel-group 5 mode on
Switch(config-if-range)# exit
Switch(config)# interface gigabitethernet3/0/3
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 10
Switch(config-if)# channel-group 5 mode on
Switch(config-if)# exit
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
channel-protocol
Use the channel-protocol interface configuration command on the switch stack or on a standalone switch to restrict the protocol used on an interface to manage channeling. Use the no form of this command to return to the default setting.
channel-protocol {lacp | pagp}
no channel-protocol
Syntax Description
lacp |
Configure an EtherChannel with the Link Aggregation Control Protocol (LACP). |
pagp |
Configure an EtherChannel with the Port Aggregation Protocol (PAgP). |
Defaults
No protocol is assigned to the EtherChannel.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
Use the channel-protocol command only to restrict a channel to LACP or PAgP. If you set the protocol by using the channel-protocol command, the setting is not overridden by the channel-group interface configuration command.
You must use the channel-group interface configuration command to configure the EtherChannel parameters. The channel-group command also can set the mode for the EtherChannel.
You cannot enable both the PAgP and LACP modes on an EtherChannel group.
PAgP and LACP are not compatible; both ends of a channel must use the same protocol.
Examples
This example shows how to specify LACP as the protocol that manages the EtherChannel:
Switch
(config-if)# channel-protocol lacp
You can verify your settings by entering the show etherchannel [channel-group-number] protocol privileged EXEC command.
Related Commands
|
|
---|---|
Assigns an Ethernet interface to an EtherChannel group. |
|
show etherchannel protocol |
Displays protocol information the EtherChannel. |
class
Use the class policy-map configuration command on the switch stack or on a standalone switch to define a traffic classification match criteria (through the police, set, and trust policy-map class configuration commands) for the specified class-map name. Use the no form of this command to delete an existing class map.
class class-map-name
no class class-map-name
Syntax Description
class-map-name |
Name of the class map. |
Defaults
No policy map class-maps are defined.
Command Modes
Policy-map configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Before using the class command, you must use the policy-map global configuration command to identify the policy map and to enter policy-map configuration mode. After specifying a policy map, you can configure a policy for new classes or modify a policy for any existing classes in that policy map. You attach the policy map to an interface by using the service-policy interface configuration command.
After entering the class command, you enter policy-map class configuration mode, and these configuration commands are available:
•bandwidth: Although this command is displayed, it is not supported on Catalyst 3750Catalyst 2970 switches.
•exit: exits policy-map class configuration mode and returns to policy-map configuration mode.
•no: returns a command to its default setting.
•police: defines a policer or aggregate policer for the classified traffic. The policer specifies the bandwidth limitations and the action to take when the limits are exceeded. For more information, see the police and police aggregate policy-map class commands.
•set: specifies a value to be assigned to the classified traffic. For more information, see the set command.
•trust: defines a trust state for traffic classified with the class or the class-map command. For more information, see the trust command.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
The class command performs the same function as the class-map global configuration command. Use the class command when a new classification, which is not shared with any other ports, is needed. Use the class-map command when the map is shared among many ports.
Examples
This example shows how to create a policy map called policy1. When attached to the ingress direction, it matches all the incoming traffic defined in class1, sets the IP Differentiated Services Code Point (DSCP) to 10, and polices the traffic at an average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP value obtained from the policed-DSCP map and then sent.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
class-map
Use the class-map global configuration command on the switch stack or on a standalone switch to create a class map to be used for matching packets to the class whose name you specify and to enter class-map configuration mode. Use the no form of this command to delete an existing class map and to return to global configuration mode.
class-map [match-all | match-any] class-map-name
no class-map [match-all | match-any] class-map-name
Syntax Description
Defaults
No class maps are defined.
If neither the match-all or match-any keyword is specified, the default is match-all.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Use this command to specify the name of the class for which you want to create or modify class-map match criteria and to enter class-map configuration mode.
The class-map command and its subcommands are used to define packet classification, marking, and aggregate policing as part of a globally named service policy applied on a per-interface basis.
After you are in quality of service (QoS) class-map configuration mode, these configuration commands are available:
•description: describes the class map (up to 200 characters). The show class-map privileged EXEC command displays the description and the name of the class-map.
•exit: exits from QoS class-map configuration mode.
•match: configures classification criteria. For more information, see the match (class-map configuration) command.
•no: removes a match statement from a class map.
•rename: renames the current class map. If you rename a class map with a name that is already used, the message A class-map with this name already exists
appears.
To define packet classification on a physical-port basis, only one match command per class map is supported. In this situation, the match-all and match-any keywords are equivalent.
Only one access control list (ACL) can be configured in a class map. The ACL can have multiple access control entries (ACEs).
Examples
This example shows how to configure the class map called class1 with one match criterion, which is an access list called 103:
Switch(config)# access-list 103 permit any any dscp 10
Switch(config)# class-map class1
Switch(config-cmap)# match access-group 103
Switch(config-cmap)# exit
This example shows how to delete the class map class1:
Switch(config)# no class-map class1
You can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
clear lacp
Use the clear lacp privileged EXEC command on the switch stack or on a standalone switch to clear Link Aggregation Control Protocol (LACP) channel-group counters.
clear lacp {channel-group-number counters | counters}
Syntax Description
channel-group-number |
(Optional) Channel group number. The range is 1 to 12. |
counters |
Clear traffic counters. |
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
You can clear all counters by using the clear lacp counters command, or you can clear only the counters for the specified channel group by using the clear lacp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch#
clear lacp counters
This example shows how to clear LACP traffic counters for group 4:
Switch#
clear lacp 4 counters
You can verify that the information was deleted by entering the show lacp counters or the show lacp 4 counters privileged EXEC command.
Related Commands
|
|
---|---|
Displays LACP channel-group information. |
clear mac address-table
Use the clear mac address-table privileged EXEC command on the switch stack or on a standalone switch to delete from the MAC address table a specific dynamic address, all dynamic addresses on a particular interface, all dynamic addresses on stack members, or all dynamic addresses on a particular VLAN. This command also clears the MAC address notification global counters.
clear mac address-table {dynamic [address mac-addr | interface interface-id | vlan vlan-id] | notification}
Note Beginning with Cisco IOS Release 12.1(19)EA1, the clear mac address-table command replaces the clear mac- address-table command (with the hyphen). The clear mac-address-table command (with the hyphen) will become obsolete in a future release.
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(19)EA1 |
The clear mac-address-table command was replaced by the clear mac address-table command. |
Examples
This example shows how to remove a specific MAC address from the dynamic address table:
Switch# clear mac address-table dynamic address 0008.0070.0007
You can verify that the information was deleted by entering the show mac address-table privileged EXEC command.
Related Commands
clear pagp
Use the clear pagp privileged EXEC command on the switch stack or on a standalone switch to clear Port Aggregation Protocol (PAgP) channel-group information.
clear pagp {channel-group-number counters | counters}
Syntax Description
channel-group-number |
(Optional) Channel group number. The range is 1 to 12. |
counters |
Clear traffic counters. |
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can clear all counters by using the clear pagp counters command, or you can clear only the counters for the specified channel group by using the clear pagp channel-group-number counters command.
Examples
This example shows how to clear all channel-group information:
Switch#
clear pagp counters
This example shows how to clear PAgP traffic counters for group 10:
Switch#
clear pagp 10 counters
You can verify that information was deleted by entering the show pagp privileged EXEC command.
Related Commands
|
|
---|---|
Displays PAgP channel-group information. |
clear setup express
Use the clear setup express privileged EXEC command on the switch stack or on a standalone switch to exit Express Setup mode without saving the current configuration.
clear setup express
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
You can use the clear setup express command to exit Express Setup mode. For example, if you activate Express Setup and then decide to connect to the switch through the console port instead of through an Ethernet port, enter the clear setup express command. The switch exits Express Setup mode. The IP address 10.0.0.1 is no longer valid on the switch, and your connection using this IP address is ended.
This command is available only when the switch is in Express Setup mode.
Examples
This example shows how to exit Express Setup mode:
Switch# clear setup express
You can verify that the switch has exited Express Setup mode by entering the show express setup privileged EXEC command.
Related Commands
|
|
---|---|
Enables Express Setup mode. |
|
Displays if Express Setup mode is active. |
clear spanning-tree counters
Use the clear spanning-tree counters privileged EXEC command on the switch stack or on a standalone switch to clear the spanning-tree counters.
clear spanning-tree counters [interface interface-id]
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
If the interface-id is not specified, spanning-tree counters are cleared for all interfaces.
Examples
This example shows how to clear spanning-tree counters for all interfaces:
Switch# clear spanning-tree counters
Related Commands
|
|
---|---|
Displays spanning-tree state information. |
clear spanning-tree detected-protocols
Use the clear spanning-tree detected-protocols privileged EXEC command on the switch stack or on a standalone switch to restart the protocol migration process (force the renegotiation with neighboring switches) on all interfaces or on the specified interface.
clear spanning-tree detected-protocols [interface interface-id]
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
A switch running the rapid per-VLAN spanning-tree plus (rapid-PVST+) protocol or the Multiple Spanning Tree Protocol (MSTP) supports a built-in protocol migration mechanism that enables it to interoperate with legacy 802.1D switches. If a rapid-PVST+ switch or an MSTP switch receives a legacy 802.1D configuration bridge protocol data unit (BPDU) with the protocol version set to 0, it sends only 802.1D BPDUs on that port. A multiple spanning-tree (MST) switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a different region, or a rapid spanning-tree (RST) BPDU (version 2).
However, the switch does not automatically revert to the rapid-PVST+ or the MSTP mode if it no longer receives 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. Use the clear spanning-tree detected-protocols command in this situation.
Examples
This example shows how to restart the protocol migration process on an interface of stack member 2:
Switch# clear spanning-tree detected-protocols interface gigabitethernet2/0/1
Related Commands
|
|
---|---|
Displays spanning-tree state information. |
|
Overrides the default link-type setting and enables rapid spanning-tree transitions to the forwarding state. |
clear vmps statistics
Use the clear vmps statistics privileged EXEC command on the switch stack or on a standalone switch to clear the statistics maintained by the VLAN Query Protocol (VQP) client.
clear vmps statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to clear VLAN Membership Policy Server (VMPS) statistics:
Switch# clear vmps statistics
You can verify that information was deleted by entering the show vmps statistics privileged EXEC command.
Related Commands
|
|
---|---|
Displays the VQP version, reconfirmation interval, retry count, VMPS IP addresses, and the current and primary servers. |
clear vtp counters
Use the clear vtp counters privileged EXEC command on the switch stack or on a standalone switch to clear the VLAN Trunking Protocol (VTP) and pruning counters.
clear vtp counters
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to clear the VTP counters:
Switch# clear vtp counters
You can verify that information was deleted by entering the show vtp counters privileged EXEC command.
Related Commands
|
|
---|---|
Displays general information about the VTP management domain, status, and counters. |
cluster commander-address
You do not need to enter this command from the switch stack or from a standalone cluster member switch. The cluster command switch automatically provides its MAC address to cluster member switches when these switches join the cluster. The cluster member switch adds this information and other cluster information to its running configuration file. Use the no form of this global configuration command from the cluster member switch console port to remove the switch from a cluster only during debugging or recovery procedures.
cluster commander-address mac-address [member number name name]
no cluster commander-address
Syntax Description
Defaults
The switch is not a member of any cluster.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command is available only on the cluster command switch stack or the cluster command switch.
A cluster member can have only one cluster command switch.
The cluster member switch retains the identity of the cluster command switch during a system reload by using the mac-address parameter.
You can enter the no form on a cluster member switch to remove it from the cluster during debugging or recovery procedures. You would normally use this command from the cluster member switch console port only when the member has lost communication with the cluster command switch. With normal switch configuration, we recommend that you remove cluster member switches only by entering the no cluster member n global configuration command on the cluster command switch.
When a standby cluster command switch becomes active (becomes the cluster command switch), it removes the cluster commander address line from its configuration.
Examples
This is partial sample output from the running configuration of a cluster member.
Switch(config)# show running-configuration
<output truncated>
cluster commander-address 00e0.9bc0.a500 member 4 name my_cluster
<output truncated>
This example shows how to remove a member from the cluster by using the cluster member console.
Switch # configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# no cluster commander-address
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster discovery hop-count
Use the cluster discovery hop-count global configuration command on the switch stack or on the a cluster command switch on the cluster command switch to set the hop-count limit for extended discovery of candidate switches. Use the no form of this command to return to the default setting.
cluster discovery hop-count number
no cluster discovery hop-count
Syntax Description
number |
Number of hops from the cluster edge that the cluster command switch limits the discovery of candidates. The range is 1 to 7. |
Defaults
The hop count is set to 3.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command is available only on the cluster command switch stack or cluster command switch. This command does not operate on cluster member switches.
If the hop count is set to 1, it disables extended discovery. The cluster command switch discovers only candidates that are one hop from the edge of the cluster. The edge of the cluster is the point between the last discovered cluster member switch and the first discovered candidate switch.
Examples
This example shows how to set hop count limit to 4. This command is executed on the cluster command switch.
Switch(config)# cluster discovery hop-count 4
You can verify your setting by entering the show cluster privileged EXEC command.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
|
Displays a list of candidate switches. |
cluster enable
Use the cluster enable global configuration command on a command-capable switch or switch stack to enable it as the cluster command switch, assign a cluster name, and to optionally assign a member number to it. Use the no form of the command to remove all members and to make the cluster command switch a candidate switch.
cluster enable name [command-switch-member-number]
no cluster enable
Syntax Description
Defaults
The switch is not a cluster command switch.
No cluster name is defined.
The member number is 0 when the switch is the cluster command switch.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command on any command-capable switch that is not part of any cluster. This command fails if a device is already configured as a member of the cluster.
You must name the cluster when you enable the cluster command switch. If the switch is already configured as the cluster command switch, this command changes the cluster name if it is different from the previous cluster name.
Examples
This example shows how to enable the cluster command switch, name the cluster, and set the cluster command switch member number to 4.
Switch(config)# cluster enable Engineering-IDF4 4
You can verify your setting by entering the show cluster privileged EXEC command on the cluster command switch.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster holdtime
Use the cluster holdtime global configuration command on the switch stack or on the a cluster command switch to set the duration in seconds before a switch (either the command or cluster member switch) declares the other switch down after not receiving heartbeat messages. Use the no form of this command to set the duration to the default value.
cluster holdtime holdtime-in-secs
no cluster holdtime
Syntax Description
holdtime-in-secs |
Duration in seconds before a switch (either a command or cluster member switch) declares the other switch down. The range is 1 to 300 seconds. |
Defaults
The default holdtime is 80 seconds.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command with the cluster timer global configuration command only on the cluster command switch. The cluster command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by the interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the interval timer and the duration on the cluster command switch.
Switch(config)# cluster timer 3
Switch(config)# cluster holdtime 30
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster member
Use the cluster member global configuration command on the cluster command switch to add candidates to a cluster. Use the no form of the command to remove members from the cluster.
cluster member [n] mac-address H.H.H [password enable-password] [vlan vlan-id]
no cluster member n
Syntax Description
Defaults
A newly enabled cluster command switch has no associated cluster members.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command only on the cluster command switch to add a candidate to or remove a member from the cluster. If you enter this command on a switch other than the cluster command switch, the switch rejects the command and displays an error message.
You must enter a member number to remove a switch from the cluster. However, you do not need to enter a member number to add a switch to the cluster. The cluster command switch selects the next available member number and assigns it to the switch that is joining the cluster.
You must enter the enable password of the candidate switch for authentication when it joins the cluster. The password is not saved in the running or startup configuration. After a candidate switch becomes a member of the cluster, its password becomes the same as the cluster command-switch password.
If a switch does not have a configured host name, the cluster command switch appends a member number to the cluster command-switch host name and assigns it to the cluster member switch.
If you do not specify a VLAN ID, the cluster command switch automatically chooses a VLAN and adds the candidate to the cluster.
Examples
This example shows how to add a switch as member 2 with MAC address 00E0.1E00.2222 and the password key to a cluster. The cluster command switch adds the candidate to the cluster through VLAN 3.
Switch(config)# cluster member 2 mac-address 00E0.1E00.2222 password key vlan 3
This example shows how to add a switch with MAC address 00E0.1E00.3333 to the cluster. This switch does not have a password. The cluster command switch selects the next available member number and assigns it to the switch that is joining the cluster.
Switch(config)# cluster member mac-address 00E0.1E00.3333
You can verify your settings by entering the show cluster members privileged EXEC command on the cluster command switch.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
|
Displays a list of candidate switches. |
|
Displays information about the cluster members. |
cluster outside-interface
Use the cluster outside-interface global configuration command on the switch stack or on the a cluster command switch to configure the outside interface for cluster Network Address Translation (NAT) so that a member without an IP address can communicate with devices outside the cluster. Use the no form of this command to return to the default setting.
cluster outside-interface interface-id
no cluster outside-interface
Syntax Description
interface-id |
Interface to serve as the outside interface. Valid interfaces include physical interfaces, port-channels, or VLANs. The port-channel range is 1 to 12. The VLAN range is 1 to 4094. |
Defaults
The default outside interface is automatically selected by the cluster command switch.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command only on the cluster command switch. If you enter this command on a cluster member switch, an error message appears.
Examples
This example shows how to set the outside interface to VLAN 1:
Switch(config)# cluster outside-interface vlan 1
You can verify your setting by entering the show running-config privileged EXEC command.
Related Commands
cluster run
Use the cluster run global configuration command to enable clustering on a switch. Use the no form of this command to disable clustering on a switch.
cluster run
no cluster run
Syntax Description
This command has no arguments or keywords.
Defaults
Clustering is enabled on all switches.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
When you enter the no cluster run command on a cluster command switch or cluster command switch stack, the cluster command switch is disabled. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a cluster member switch, it is removed from the cluster. Clustering is disabled, and the switch cannot become a candidate switch.
When you enter the no cluster run command on a switch that is not part of a cluster, clustering is disabled on this switch. This switch cannot then become a candidate switch.
Examples
This example shows how to disable clustering on the cluster command switch:
Switch(config)# no cluster run
You can verify your setting by entering the show cluster privileged EXEC command.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
cluster standby-group
Use the cluster standby-group global configuration command to enable cluster command-switch redundancy by binding the cluster to an existing Hot Standby Router Protocol (HSRP). Entering the routing-redundancy keyword enables the same HSRP group to be used for cluster command-switch redundancy and routing redundancy. Use the no form of this command to return to the default setting.
cluster standby-group HSRP-group-name [routing-redundancy]
no cluster standby-group
Syntax Description
Defaults
The cluster is not bound to any HSRP group.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command only on the cluster command switch. If you enter it on a cluster member switch, an error message appears.
The cluster command switch propagates the cluster-HSRP binding information to all cluster-HSRP capable members. Each cluster member switch stores the binding information in its nonvolatile RAM (NVRAM).
The HSRP group name must be a valid standby group; otherwise, the command exits with an error.
The same group name should be used on all members of the HSRP standby group that is to be bound to the cluster. The same HSRP group name should also be used on all cluster-HSRP capable members for the HSRP group that is to be bound. (When not binding a cluster to an HSRP group, you can use different names on the cluster commander and the members.)
Examples
This example shows how to bind the HSRP group named my_hsrp to the cluster. This command is executed on the cluster command switch.
Switch(config)# cluster standby-group my_hsrp
This example shows how to use the same HSRP group named my_hsrp for routing redundancy and cluster redundancy.
Switch(config)# cluster standby-group my_hsrp routing-redundancy
This example shows the error message when this command is executed on a cluster command switch and the specified HSRP standby group does not exist:
Switch(config)# cluster standby-group my_hsrp
%ERROR: Standby (my_hsrp) group does not exist
This example shows the error message when this command is executed on a cluster member switch:
Switch(config)# cluster standby-group my_hsrp routing-redundancy
%ERROR: This command runs on a cluster command switch
You can verify your settings by entering the show cluster privileged EXEC command. The output shows whether redundancy is enabled in the cluster.
Related Commands
cluster timer
Use the cluster timer global configuration command on the switch stack or on the a cluster command switch to set the interval in seconds between heartbeat messages. Use the no form of this command to set the interval to the default value.
cluster timer interval-in-secs
no cluster timer
Syntax Description
interval-in-secs |
Interval in seconds between heartbeat messages. The range is 1 to 300 seconds. |
Defaults
The interval is 8 seconds.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Enter this command with the cluster holdtime global configuration command only on the cluster command switch. The cluster command switch propagates the values to all its cluster members so that the setting is consistent among all switches in the cluster.
The holdtime is typically set as a multiple of the heartbeat interval timer (cluster timer). For example, it takes (holdtime-in-secs divided by the interval-in-secs) number of heartbeat messages to be missed in a row to declare a switch down.
Examples
This example shows how to change the heartbeat interval timer and the duration on the cluster command switch:
Switch(config)# cluster timer 3
Switch(config)# cluster holdtime 30
You can verify your settings by entering the show cluster privileged EXEC command.
Related Commands
|
|
---|---|
Displays the cluster status and a summary of the cluster to which the switch belongs. |
define interface-range
Use the define interface-range global configuration command on the switch stack or on a standalone switch to create an interface-range macro. Use the no form of this command to delete the defined macro.
define interface-range macro-name interface-range
no define interface-range macro-name interface-range
Syntax Description
macro-name |
Name of the interface-range macro; up to 32 characters. |
interface-range |
Interface range; for valid values for interface ranges, see "Usage Guidelines." |
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The macro name is a 32-character maximum character string.
A macro can contain up to five ranges.
All interfaces in a range must be the same type; that is, all Fast Ethernet ports, all Gigabit Ethernet ports, all EtherChannel ports, or all VLANs, but you can combine multiple interface types in a macro.
When entering the interface-range, use this format:
•type {first-interface} - {last-interface}
•You must add a space between the first interface number and the hyphen when entering an interface-range. For example, gigabitethernet1/0/1 -5 is a valid range; gigabitethernet1/0/1-5 is not a valid range.
Valid values for type and interface:
•vlan vlan-id, where vlan-id is from 1 to 4094
VLAN interfaces must have been configured with the interface vlan command (the show running-config privileged EXEC command displays the configured VLAN interfaces). VLAN interfaces not displayed by the show running-config command cannot be used in interface-ranges.
•port-channel port-channel-number, where port-channel-number is from 1 to 12
•fastethernet stack member/module/{first port} - {last port}
•gigabitethernet stack member/module/{first port} - {last port}
For physical interfaces:
•stack member is the number used to identify the switch within the stack. The number ranges from 1 to 9 and is assigned to the switch the first time the stack member initializes.
•module is always 0
•the range is type stack member/0/number - number (for example, gigabitethernet 1/0/1 - 2)
When you define a range, you must enter a space before the hyphen (-), for example:
gigabitethernet1/0/1 - 2
You can also enter multiple ranges. When you define multiple ranges, you must enter a space after the first entry before the comma (,). The space after the comma is optional, for example:
fastethernet1/0/3 ,gigabitethernet1/0/1 - 2
fastethernet1/0/3 -4 , gigabitethernet1/0/1 - 2
gigabitethernet0/3 ,gigabitethernet 0/6 - 7
gigabitethernet0/3 -4 , gigabitethernet 0/6 - 7
Examples
This example shows how to create a multiple-interface macro:
Switch(config)#
define interface-range macro1 gigabitethernet1/0/1 -2 ,
gigabitethernet1/0/5
Related Commands
delete
Use the delete privileged EXEC command on the switch stack or on a standalone switch to delete a file or directory on the Flash memory device.
delete [/force] [/recursive] filesystem:/file-url
Syntax Description
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
If you use the /force keyword, you are prompted once at the beginning of the deletion process to confirm the deletion.
If you use the /recursive keyword without the /force keyword, you are prompted to confirm the deletion of every file.
The prompting behavior depends on the setting of the file prompt global configuration command. By default, the switch prompts for confirmation on destructive file operations. For more information about this command, refer to the Cisco IOS Command Reference for Release 12.1.
Examples
This example shows how to remove the directory that contains the old software image after a successful download of a new image:
Switch# delete /force /recursive flash:/old-image
You can verify that the directory was removed by entering the dir filesystem: privileged EXEC command.
Related Commands
|
|
---|---|
Downloads a new image to the switch and overwrites or keeps the existing image. |
deny
Use the deny MAC access list configuration command on the switch stack or on a standalone switch to prevent non-IP traffic from being forwarded if the conditions are matched. Use the no form of this command to remove a deny condition from the named MAC access list.
{deny | permit} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask |mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp]
no {deny | permit} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | aarp | amber | cos cos | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp]
Syntax Description
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition.
To filter IPX traffic, you use the type mask or lsap lsap mask keywords, depending on the type of IPX encapsulation being used. Filter criteria for IPX encapsulation types as specified in Novell terminology and Cisco IOS terminology are listed in Table 2-4.
Defaults
This command has no defaults. However; the default action for a MAC-named ACL is to deny.
Command Modes
MAC-access list configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You enter MAC-access list configuration mode by using the mac access-list extended global configuration command.
If you use the host keyword, you cannot enter an address mask; if you do not use the host keyword, you must enter an address mask.
When an access control entry (ACE) is added to an access control list, an implied deny-any-any condition exists at the end of the list. That is, if there are no matches, the packets are denied. However, before the first ACE is added, the list permits all packets.
Note For more information about named MAC extended access lists, refer to the software configuration guide for this release.
Examples
This example shows how to define the named MAC extended access list to deny NETBIOS traffic from any source to MAC address 00c0.00a0.03fa. Traffic matching this list is denied.
Switch(config-ext-macl)# deny any host 00c0.00a0.03fa netbios.
This example shows how to remove the deny condition from the named MAC extended access list:
Switch(config-ext-macl)# no deny any 00c0.00a0.03fa 0000.0000.0000 netbios.
This example denies all packets with Ethertype 0x4321:
Switch(config-ext-macl)# deny any any 0x4321 0
You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
dot1x default
Use the dot1x default interface configuration command on the switch stack or on a standalone switch to reset the configurable 802.1X parameters to their default values.
dot1x default
Syntax Description
This command has no arguments or keywords.
Defaults
These are the default values:
•The per-interface 802.1X protocol enable state is disabled (force-authorized).
•The number of seconds between re-authentication attempts is 3600 seconds.
•The periodic re-authentication is disabled.
•The quiet period is 60 seconds.
•The retransmission time is 30 seconds.
•The maximum retransmission number is 2 times.
•The host mode is single host.
•The client timeout period is 30 seconds.
•The authentication server timeout period is 30 seconds.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
This command was changed to the interface configuration mode. |
Examples
This example shows how to reset the configurable 802.1X parameters on an interface:
Switch(config-if)# dot1x default
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x guest-vlan
Use the dot1x guest-vlan interface configuration command on the switch stack or on a standalone switch to specify an active VLAN as an 802.1X guest VLAN. Use the no form of this command to return to the default setting.
dot1x guest-vlan vlan-id
no dot1x guest-vlan
Syntax Description
vlan-id |
Specify an active VLAN as an 802.1X guest VLAN. The range is 1 to 4094. |
Defaults
No guest VLAN is configured.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
When you configure a guest VLAN, clients that are not 802.1X-capable are put into the guest VLAN when the server does not receive a response to its Extensible Authentication Protocol over LAN (EAPOL) request/identity frame. Clients that are 802.1X-capable but fail authentication are not granted access to the network.
Guest VLANs are supported on 802.1X ports in single-host mode and multiple-hosts mode.
You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802.1X guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
Examples
This example shows how to specify VLAN 5 as an 802.1X guest VLAN:
Switch(config-if)# dot1x guest-vlan 5
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x host-mode
Use the dot1x host-mode interface configuration command on the switch stack or on a standalone switch to allow a single host (client) or multiple hosts on an 802.1X-authorized port that has the dot1x port-control interface configuration command set to auto. Use the no form of this command to return to the default setting.
dot1x host-mode {multi-host | single-host}
no dot1x host-mode [multi-host | single-host]
Syntax Description
multi-host |
Enable multiple-hosts mode on the switch. |
single-host |
Enable single-host mode on the switch. |
Defaults
The default is single-host mode.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. It replaces the dot1x multiple-hosts interface configuration command. |
Usage Guidelines
Use this command to limit an 802.1X-enabled port to a single client or to attach multiple clients to an 802.1X-enabled port. In multiple-hosts mode, only one of the attached hosts must be successfully authorized for all hosts to be granted network access. If the port becomes unauthorized (re-authentication fails or an Extensible Authentication Protocol over LAN [EAPOL]-logoff message is received), all attached clients are denied access to the network.
Before entering this command, make sure that the dot1x port-control interface configuration command is set to auto for the specified interface.
Examples
This example shows how to enable 802.1X globally, enable 802.1X on Gigabit Ethernet interface 0/1 on stack member 2, and enable multiple-hosts mode:
Switch(config)# dot1x system-auth-control
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-host
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x initialize
Use the dot1x initialize privileged EXEC command on the switch stack or on a standalone switch to manually return the specified 802.1X-enabled interface to an unauthorized state before initiating a new authentication session on the interface.
dot1x initialize interface interface-id
Syntax Description
interface interface-id |
Interface to be initialized. |
Defaults
There is no default setting.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
Use this command to initialize the 802.1X state machines and to set up a fresh environment for authentication. After you enter this command, the port status becomes unauthorized.
There is no no form of this command.
Examples
This example shows how to manually initialize Gigabit Ethernet interface 0/3 on stack member 2:
Switch# dot1x initialize interface gigabitethernet2/0/3
You can verify the unauthorized port status by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x max-req
Use the dot1x max-req interface configuration command on the switch stack or on a standalone switch to set the maximum number of times that the switch sends an Extensible Authentication Protocol (EAP)-request/identity frame (assuming that no response is received) to the client before restarting the authentication process. Use the no form of this command to return to the default setting.
dot1x max-req count
no dot1x max-req
Syntax Description
count |
Number of times that the switch sends an EAP-request/identity frame before restarting the authentication process. The range is 1 to 10. |
Defaults
The default is 2 times.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
This command was changed to the interface configuration mode. |
Usage Guidelines
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
Examples
This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity frame before restarting the authentication process:
Switch(config-if)# dot1x max-req 5
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
dot1x timeout tx-period |
Sets the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request. |
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x multiple-hosts
This is an obsolete command.
In past releases, the dot1x multiple-hosts interface configuration command was used on the switch stack or on a standalone switch to allow multiple hosts (clients) on an 802.1X-authorized port.
Command History
Related Commands
|
|
---|---|
Sets the 802.1X host mode on an interface. |
|
Displays 802.1X statistics, administrative status, and operational status for the switch or for the specified interface. |
dot1x port-control
Use the dot1x port-control interface configuration command on the switch stack or on a standalone switch to enable manual control of the authorization state of the port. Use the no form of this command to return to the default setting.
dot1x port-control {auto | force-authorized | force-unauthorized}
no dot1x port-control
Syntax Description
Defaults
The default is force-authorized.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You must globally enable 802.1X on the switch by using the dot1x system-auth-control global configuration command before enabling 802.1X on a specific interface.
The 802.1X protocol is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed ports.
The 802.1X protocol is supported on Layer 2 static-access ports and voice VLAN ports.
You can use the auto keyword only if the port is not configured as one of these:
•Trunk port—If you try to enable 802.1X on a trunk port, an error message appears, and 802.1X is not enabled. If you try to change the mode of an 802.1X-enabled port to trunk, an error message appears, and the port mode is not changed.
•Dynamic ports—A port in dynamic mode can negotiate with its neighbor to become a trunk port. If you try to enable 802.1X on a dynamic port, an error message appears, and 802.1X is not enabled. If you try to change the mode of an 802.1X-enabled port to dynamic, an error message appears, and the port mode is not changed.
•Dynamic-access ports—If you try to enable 802.1X on a dynamic-access (VLAN Query Protocol [VQP]) port, an error message appears, and 802.1X is not enabled. If you try to change an 802.1X-enabled port to dynamic VLAN assignment, an error message appears, and the VLAN configuration is not changed.
•EtherChannel port—Before enabling 802.1X on the port, you must first remove it from the EtherChannel. If you try to enable 802.1X on an EtherChannel or on an active port in an EtherChannel, an error message appears, and 802.1X is not enabled. If you enable 802.1X on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.
•Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable 802.1X on a port that is a SPAN or RSPAN destination port. However, 802.1X is disabled until the port is removed as a SPAN or RSPAN destination. You can enable 802.1X on a SPAN or RSPAN source port.
To globally disable 802.1X on the switch, use the no dot1x system-auth-control global configuration command. To disable 802.1X on a specific interface, use the no dot1x port-control interface configuration command.
Examples
This example shows how to enable 802.1X on Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1:
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# dot1x port-control auto
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x re-authenticate
Use the dot1x re-authenticate privileged EXEC command on the switch stack or on a standalone switch to manually initiate a re-authentication of all 802.1X-enabled ports or the specified 802.1X-enabled port.
dot1x re-authenticate interface interface-id
Syntax Description
interface interface-id |
Stack switch number, module, and port number of the interface to re-authenticate.Module and port number of the interface to re-authenticate. |
Defaults
There is no default setting.
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can use this command to re-authenticate a client without waiting for the configured number of seconds between re-authentication attempts (re-authperiod) and automatic re-authentication.
Examples
This example shows how to manually re-authenticate the device connected to Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1:
Switch# dot1x re-authenticate interface fastethernet2/0/1
Switch# dot1x re-authenticate interface gigabitethernet0/1
dot1x re-authentication
This is an obsolete command.
In past releases, the dot1x re-authentication global configuration command was used on the switch stack or on a standalone switch to set the amount of time between periodic re-authentication attempts.
Command History
Related Commands
dot1x reauthentication
Use the dot1x reauthentication interface configuration command on the switch stack or on a standalone switch to enable periodic re-authentication of the client. Use the no form of this command to return to the default setting.
dot1x reauthentication
no dot1x reauthentication
Syntax Description
This command has no arguments or keywords.
Defaults
Periodic re-authentication is disabled.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. It replaces the dot1x re-authentication global configuration command (with the hyphen). |
Usage Guidelines
You configure the amount of time between periodic re-authentication attempts by using the dot1x timeout reauth-period interface configuration command.
Examples
This example shows how to disable periodic re-authentication of the client:
Switch(config-if)# no dot1x reauthentication
This example shows how to enable periodic re-authentication and to set the number of seconds between re-authentication attempts to 4000 seconds:
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period 4000
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
dot1x timeout reauth-period |
Sets the number of seconds between re-authentication attempts. |
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x system-auth-control
Use the dot1x system-auth-control global configuration command on the switch stack or on a standalone switch to globally enable 802.1X. Use the no form of this command to return to the default setting.
dot1x system-auth-control
no dot1x system-auth-control
Syntax Description
This command has no arguments or keywords.
Defaults
802.1X is disabled.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
You must enable authentication, authorization, and accounting (AAA) and specify the authentication method list before globally enabling 802.1X. A method list describes the sequence and authentication methods to be queried to authenticate a user.
Examples
This example shows how to globally enable 802.1X on a switch:
Switch(config)# dot1x system-auth-control
You can verify your settings by entering the show dot1x [interface interface-id] privileged EXEC command.
Related Commands
|
|
---|---|
Enables manual control of the authorization state of the port. |
|
show dot1x [interface interface-id] |
Displays 802.1X status for the specified interface. |
dot1x timeout
Use the dot1x timeout interface configuration command on the switch stack or on a standalone switch to set 802.1X timers. Use the no form of this command to return to the default setting.
dot1x timeout {quiet-period seconds | reauth-period seconds | server-timeout seconds | supp-timeout seconds | tx-period seconds}
no dot1x timeout {quiet-period | reauth-period | server-timeout | supp-timeout | tx-period}
Syntax Description
Defaults
These are the default settings:
reauth-period is 3600 seconds.
quiet-period is 60 seconds.
tx-period is 30 seconds.
supp-timeout is 30 seconds.
server-timeout is 30 seconds.
Command Modes
Interface configuration
Command History
Usage Guidelines
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
The dot1x timeout reauth-period interface configuration command affects the behavior of the switch only if you have enabled periodic re-authentication by using the dot1x reauthentication interface configuration command.
During the quiet period, the switch does not accept or initiate any authentication requests. If you want to provide a faster response time to the user, enter a smaller number than the default.
Examples
This example shows how to enable periodic re-authentication and to set 4000 as the number of seconds between re-authentication attempts:
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period 4000
This example shows how to set 30 seconds as the quiet time on the switch:
Switch(config-if)# dot1x timeout quiet-period 30
This example shows how to set 25 seconds as the switch-to-authentication server retransmission time:
Switch(config)# dot1x timeout server-timeout 25
This example shows how to set 25 seconds as the switch-to-client retransmission time for the EAP request frame:
Switch(config-if)# dot1x timeout supp-timeout 25
This example shows how to set 60 as the number of seconds to wait for a response to an EAP-request/identity frame from the client before re-transmitting the request:
Switch(config-if)# dot1x timeout tx-period 60
You can verify your settings by entering the show dot1x privileged EXEC command.
Related Commands
duplex
Use the duplex interface configuration command on the switch stack or on a standalone switch to specify the duplex mode of operation for Fast Ethernet and Gigabit Ethernet ports. Use the no form of this command to return the port to its default value.
duplex {auto | full | half}
no duplex
Syntax Description
Defaults
The default is auto.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command is not available on small form-factor pluggable (SFP) module ports unless a 1000BASE-T SFP module is in the port. All other SFP modules operate only in full-duplex mode.
Certain ports can be configured to be either full duplex or half duplex. Applicability of this command depends on the device to which the switch is attached.
For Fast Ethernet ports, setting the port to auto has the same effect as specifying half if the attached device does not autonegotiate the duplex parameter.
For Gigabit Ethernet ports, setting the port to auto has the same effect as specifying full if the attached device does not autonegotiate the duplex parameter.
You cannot configure duplex mode on SFP module interfaces. However, when a 1000BASE-T SFP module is in the SFP module port, you can configure duplex mode to auto or full.
If both ends of the line support autonegotiation, we highly recommend using the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do use the auto setting on the supported side.
If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.
For 10/100/1000 Mbps ports, if both the speed and duplex are set to specific values, autonegotiation is disabled.
For 10/100 Mbps ports, if both speed and duplex are set to specific values, the link operates at the negotiated speed and duplex value.
Note For guidelines on setting the switch speed and duplex parameters, refer to the software configuration guide for this release.
Examples
This example shows how to configure an interface for full duplex operation:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# duplex full
You can verify your setting by entering the show interfaces privileged EXEC command.
Related Commands
|
|
---|---|
Displays the interface settings on the switch. |
|
Sets the speed on a 10/100 or 10/100/1000 Mbps interface. |
errdisable detect cause
Use the errdisable detect cause global configuration command on the switch stack or on a standalone switch to enable error disable detection for a specific cause or all causes. Use the no form of this command to disable the error disable detection feature.
errdisable detect cause {all | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap}
no errdisable detect cause {all | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | pagp-flap}
Syntax Description
Defaults
Detection is enabled for all causes.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
The gbic-invalid keyword is supported for SFP module ports. |
12.1(19)EA1 |
The dhcp-rate-limit keyword was added. |
Usage Guidelines
A cause (dhcp-rate-limit, dtp-flap, gbic-invalid, link-flap, loopback, and pagp-flap) is the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in an error-disabled state, an operational state similar to link-down state.
If you set a recovery mechanism for the cause by entering the errdisable recovery global configuration command for the cause, the interface is brought out of the error-disabled state and allowed to retry the operation when all causes have timed out. If you do not set a recovery mechanism, you must enter the shutdown and then the no shutdown commands to manually recover an interface from the error-disabled state.
Examples
This example shows how to enable error disable detection for the link-flap error-disable cause:
S
witch(config)# errdisable detect cause link-flap
You can verify your setting by entering the show errdisable detect privileged EXEC command.
Related Commands
|
|
---|---|
Displays errdisable detection information. |
|
show interfaces status err-disabled |
Displays interface status or a list of interfaces in the error-disabled state. |
errdisable recovery
Use the errdisable recovery global configuration command on the switch stack or on a standalone switch to configure the recover mechanism variables. Use the no form of this command to return to the default setting.
errdisable recovery {cause {all | bpduguard | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap | psecure-violation | security-violation | udld | vmps} | {interval interval}
no errdisable recovery {cause {all | bpduguard | dhcp-rate-limit | dtp-flap | gbic-invalid | link-flap | loopback | pagp-flap | psecure-violation | security-violation | udld | vmps} | {interval interval}
Syntax Description
Note Though visible in the command-line help strings, the unicast-flood, and channel-misconfig keywords are not supported.
Defaults
Recovery is disabled for all causes.
The default recovery interval is 300 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (bpduguard, dhcp-rate-limit, dtp-flap, gbic-invalid, link-flap, loopback, pagp-flap, psecure-violation, security-violation, udld, vmps) is defined as the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in error-disabled state, an operational state similar to link-down state. If you do not enable errdisable recovery for the cause, the interface stays in error-disabled state until you enter a shutdown and no shutdown interface configuration command. If you enable the recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry the operation again when all the causes have timed out.
Otherwise, you must enter the shutdown then no shutdown commands to manually recover an interface from the error-disabled state.
Examples
This example shows how to enable the recovery timer for the BPDU guard error-disable cause:
S
witch(config)# errdisable recovery cause bpduguard
This example shows how to set the timer to 500 seconds:
Switch(config)# errdisable recovery interval 500
You can verify your settings by entering the show errdisable recovery privileged EXEC command.
Related Commands
|
|
---|---|
Displays errdisable recovery timer information. |
|
show interfaces status err-disabled |
Displays interface status or a list of interfaces in error-disabled state. |
flowcontrol
Use the flowcontrol interface configuration command on the switch stack or on a standalone switch to set the receive flow-control state for an interface. When flow control send is operable and on for a device and it detects any congestion at its end, it notifies the link partner or the remote device of the congestion by sending a pause frame. When flow control receive is on for a device and it receives a pause frame, it stops sending any data packets. This prevents any loss of data packets during the congestion period.
Use the receive off keywords to disable flow control.
flowcontrol receive {desired | off | on}
Note The Catalyst 3750 2970 switch can only receive pause frames.
Syntax Description
Defaults
The default is flowcontrol receive off.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The switch does not support sending flow-control pause frames.
Note that the on and desired keywords have the same result.
When you use the flowcontrol command to set a port to control traffic rates during congestion, you are setting flow control on a port to one of these conditions:
•receive on or desired: The port cannot send out pause frames, but can operate with an attached device that is required to or is able to send pause frames; the port is able to receive pause frames.
•receive off: Flow control does not operate in either direction. In case of congestion, no indication is given to the link partner and no pause frames are sent or received by either device.
Table 2-5 shows the flow control results on local and remote ports for a combination of settings. The table assumes that receive desired has the same results as using the receive on keywords.
Examples
This example shows how to configure the local port to not support flow control by the remote port:
Switch(config-if)# flowcontrol receive off
You can verify your settings by entering the show interfaces privileged EXEC command.
Related Commands
|
|
---|---|
Displays the interface settings on the switch, including input and output flow control. |
interface port-channel
Use the interface port-channel global configuration command on the switch stack or on a standalone switch to access or create the port-channel logical interface. Use the no form of this command to remove the port-channel.
interface port-channel port-channel-number
no interface port-channel port-channel-number
Syntax Description
port-channel-number |
Port-channel number. The range is 1 to12. |
Defaults
No port-channel logical interfaces are defined.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
For Layer 2 EtherChannels, you do not have to create a port-channel interface first before assigning a physical interface to a channel group. Instead, you can use the channel-group interface configuration command. It automatically creates the port-channel interface when the channel group gets its first physical interface. If you create the port-channel interface first, the channel-group-number can be the same as the port-channel-number, or you can use a new number. If you use a new number, the channel-group command dynamically creates a new port channel.
You create Layer 3 port channels by using the interface port-channel command followed by the no switchport interface configuration command. You should manually configure the port-channel logical interface before putting the interface into the channel group.
Only one port channel in a channel group is allowed.
Follow these guidelines when you use the interface port-channel command:
•If you want to use the Cisco Discovery Protocol (CDP), you must configure it only on the physical interface and not on the port-channel interface.
•Do not configure a port that is an active member of an EtherChannel as an 802.1X port. If 802.1X is enabled on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.
For a complete list of configuration guidelines, refer to the "Configuring EtherChannels" chapter in the software guide for this release.
Examples
This example shows how to create a port-channel interface with a port channel number of 5:
Switch(config)#
interface port-channel 5
You can verify your setting by entering the show running-config privileged EXEC or show etherchannel channel-group-number detail privileged EXEC command.
Related Commands
interface range
Use the interface range global configuration command on the switch stack or on a standalone switch to enter interface range configuration mode and to execute a command on multiple ports at the same time. Use the no form of this command to remove an interface range.
interface range {port-range | macro name}
no interface range {port-range | macro name}
Syntax Description
port-range |
Port range. For a list of valid values for port-range, see the "Usage Guidelines" section. |
macro name |
Specify the name of a macro. |
Defaults
This command has no default setting.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
When you enter interface range configuration mode, all interface parameters you enter are attributed to all interfaces within the range.
For VLANs, you can use the interface range command only on existing VLAN switch virtual interfaces (SVIs). To display VLAN SVIs, enter the show running-config privileged EXEC command. VLANs not displayed cannot be used in the interface range command. The commands entered under interface range command are applied to all existing VLAN SVIs in the range.
All configuration changes made to an interface range are saved to nonvolatile RAM (NVRAM), but the interface range itself is not saved to NVRAM.
You can enter the interface range in two ways:
•Specifying up to five interface ranges
•Specifying a previously defined interface-range macro
All interfaces in a range must be the same type; that is, all Fast Ethernet ports, all Gigabit Ethernet ports, all EtherChannel ports, or all VLANs. However, you can define up to five interface ranges with a single command, with each range separated by a comma.
Valid values for port-range type and interface:
•vlan vlan-ID - vlan-ID, where VLAN ID is from 1 to 4094
•fastethernet stack member/module/{first port} - {last port}, where switch is the switch number and module is 0
•gigabitethernet stack member/module/{first port} - {last port}, where switch is the switch number and module is 0
For physical interfaces:
–stack member is the number used to identify the switch within the stack. The number ranges from 1 to 9 and is assigned to the switch the first time the stack member initializes.
–module is always 0
–the range is type stack member/0/number - number (for example, gigabitethernet1/0/1 - 2)
•port-channel port-channel-number - port-channel-number, where port-channel-number is from 1 to 12
Note When you use the interface range command with port channels, the first and last port channel number in the range must be active port channels.
When you define a range, you must enter a space between the first entry and the hyphen (-):
interface range gigabitethernet1/0/1 -2
When you define multiple ranges, you must still enter a space after the first entry, before the comma (,):
interface range fastethernet1/0/3 , gigabitethernet1/0/1 - 2
interface range gigabitethernet1/0/3 -5, gigabitethernet1/0/7 -8
You cannot specify both a macro and an interface range in the same command.
A single interface can also be specified in port-range (this would make the command similar to the interface interface-id global configuration command).
Note For more information about configuring interface ranges, refer to the software configuration guide for this release.
Examples
This example shows how to use the interface range command to enter interface range configuration mode to apply commands to two ports:
Switch(config)#
interface range gigabitethernet1/0/1 - 2
Switch(config-if-range)#
This example shows how to use a port-range macro macro1 for the same function. The advantage is that you can reuse macro1 until you delete it.
Switch(config)# define interface-range macro1 gigabitethernet1/0/1 - 2
Switch(config)# interface range macro macro1
Switch(config-if-range)#
Related Commands
interface vlan
Use the interface vlan global configuration command on the switch stack or on a standalone switch to create or access a VLAN dynamic switch virtual interface (SVI) and to enter interface configuration mode. Use the no form of this command to delete an SVI a VLAN.
interface vlan vlan-id
no interface vlan vlan-id
Syntax Description
vlan-id |
VLAN number. The range is 1 to 4094. |
Defaults
The default VLAN interface is VLAN 1.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You cannot delete the VLAN 1 interface.
SVIs VLANs are created the first time that you enter the interface vlan vlan-id command for a particular vlan. The vlan-id corresponds to the VLAN-tag associated with data frames on an ISL or 802.1Q encapsulated trunk or the VLAN ID configured for an access port.
Note When you create an SVI, it does not become active until it is associated with a physical port.
If you delete an SVI a VLAN by entering the no interface vlan vlan-id command, the deleted interface is no longer visible in the output from the show interfaces privileged EXEC command.
You can reinstate a deleted SVI VLAN by entering the interface vlan vlan-id command for the deleted interface. The interface comes back up, but much of the previous configuration will be gone.
The interrelationship between the number of SVIs configured on a switch stack and the number of other features being configured might have an impact on CPU utilization due to hardware limitations. You can use the sdm prefer global configuration command to reallocate system hardware resources based on templates and feature tables. For more information, see the sdm prefer command.
Examples
This example shows how to create a new VLAN SVI with VLAN ID 23 and enter interface configuration mode:
Switch(config)# interface vlan 23
Switch(config-if)#
You can verify your setting by entering the show interfaces and show interfaces vlan vlan-id privileged EXEC commands.
Related Commands
|
|
---|---|
show interfaces vlan vlan-id |
Displays the administrative and operational status of all interfaces or the specified VLAN. |
ip access-group
Use the ip access-group interface configuration command on the switch stack or on a standalone switch to control access to a Layer 2 or Layer 3 interface. Use the no form of this command to remove all access groups or the specified access group from the interface.
ip access-group {access-list-number | name} {in | out}
no ip access-group [access-list-number | name] {in | out}
Syntax Description
Defaults
No access list is applied to the interface.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
This command support was extended to Layer 2 interfaces. |
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
You can apply named or numbered standard or extended IP access lists to an interface. To define an access list by name, use the ip access-list global configuration command. To define a numbered access list, use the access list global configuration command. You can used numbered standard access lists ranging from 1 to 99 and 1300 to 1999 or extended access lists ranging from 100 to 199 and 2000 to 2699.
You can use this command to apply an access list to a Layer 2 or Layer 3 interface. However, note these limitations for Layer 2 interfaces (port ACLs):
•You can only apply ACLs in the inbound direction; the out keyword is not supported for Layer 2 interfaces.
•You can only apply one IP ACL and one MAC ACL per interface.
•Layer 2 interfaces Port ACLs do not support logging; if the log keyword is specified in the IP ACL, it is ignored.
•An IP ACL applied to an Layer 2 interface only filters IP packets. To filter non-IP packets, use the mac access-group interface configuration command with MAC extended ACLs.
You can use router ACLs, input port ACLs, and VLAN maps on the same switch. However, a port ACL takes precedence over a router ACL or VLAN map. When both an input port ACL and a VLAN map are applied, incoming packets received on ports with the port ACL applied are filtered by the port ACL. Other packets are filtered by the VLAN map.
•When an input port ACL is applied to an interface and a VLAN map is applied to a VLAN that the interface is a member of, incoming packets received on ports with the ACL applied are filtered by the port ACL. Other packets are filtered by the VLAN map.
•When an input router ACL and input port ACLs exist in an switch virtual interface (SVI), incoming packets received on ports to which a port ACL is applied are filtered by the port ACL. Incoming routed IP packets received on other ports are filtered by the router ACL. Other packets are not filtered.
•When an output router ACL and input port ACLs exist in an SVI, incoming packets received on the ports to which a port ACL is applied are filtered by the port ACL. Outgoing routed IP packets are filtered by the router ACL. Other packets are not filtered.
•When a VLAN map, input router ACLs, and input port ACLs exist in an SVI, incoming packets received on the ports to which a port ACL is applied are only filtered by the port ACL. Incoming routed IP packets received on other ports are filtered by both the VLAN map and the router ACL. Other packets are filtered only by the VLAN map.
•When a VLAN map, output router ACLs, and input port ACLs exist in an SVI, incoming packets received on the ports to which a port ACL is applied are only filtered by the port ACL. Outgoing routed IP packets are filtered by both the VLAN map and the router ACL. Other packets are filtered only by the VLAN map.
You can apply IP ACLs to both outbound or inbound Layer 3 interfaces.
A Layer 3 interface can have one IP ACL applied in each direction.
You can configure only one VLAN map and one router ACL in each direction (input/output) on a VLAN interface.
For standard inbound access lists, after the switch receives a packet, it checks the source address of the packet against the access list. IP extended access lists can optionally check other fields in the packet, such as the destination IP address, protocol type, or port numbers. If the access list permits the packet, the switch continues to process the packet. If the access list denies the packet, the switch discards the packet. If the access list has been applied to a Layer 3 interface, discarding a packet (by default) causes the generation of an Internet Control Message Protocol (ICMP) Host Unreachable message. ICMP Host Unreachable messages are not generated for packets discarded on a Layer 2 interface.
For standard outbound access lists, after receiving a packet and sending it to a controlled interface, the switch checks the packet against the access list. If the access list permits the packet, the switch sends the packet. If the access list denies the packet, the switch discards the packet and, by default, generates an ICMP Host Unreachable message.
If the specified access list does not exist, all packets are passed.
Examples
This example shows how to apply IP access list 101 to inbound packets on Gigabit Ethernet interface 0/1 on stack member 1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ip access-group 101 in
You can verify your settings by entering the show ip interface, show access-lists, or show ip access-lists privileged EXEC command.
Related Commands
ip address
Use the ip address interface configuration command on the switch stack or on a standalone switch to set an IP address for the Layer 2 switch or an IP address for each switch virtual interface (SVI) or routed port on the Layer 3 switch. Use the no form of this command to remove an IP address or to disable IP processing.
ip address ip-address subnet-mask [secondary]
no ip address [ip-address subnet-mask] [secondary]
Syntax Description
Defaults
No IP address is defined.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
If you remove the switch IP address through a Telnet session, your connection to the switch will be lost.
Hosts can determine subnet masks using the Internet Control Message Protocol (ICMP) Mask Request message. Routers respond to this request with an ICMP Mask Reply message.
You can disable IP processing on a particular interface by removing its IP address with the no ip address command. If the switch detects another host using one of its IP addresses, it will send an error message to the console.
You can use the optional keyword secondary to specify an unlimited number of secondary addresses. Secondary addresses are treated like primary addresses, except the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and ARP requests are handled properly, as are interface routes in the IP routing table.
Note If any router on a network segment uses a secondary address, all other devices on that same segment must also use a secondary address from the same network or subnet. Inconsistent use of secondary addresses on a network segment can very quickly cause routing loops.
When you are routing Open Shortest Path First (OSPF), ensure that all secondary addresses of an interface fall into the same OSPF area as the primary addresses.
If your switch receives its IP address from a Bootstrap Protocol (BOOTP) or Dynamic Host Configuration Protocol (DHCP) server and you remove the switch IP address by using the no ip address command, IP processing is disabled, and the BOOTP or DHCP server cannot reassign the address.
A Layer 3 switch can have an IP address assigned to each routed port and SVI. The number of routed ports and SVIs that you can configure is not limited by software; however, the interrelationship between this number and the number of other features being configured might have an impact on CPU utilization due to hardware limitations. You can use the sdm prefer global configuration command to reallocate system hardware resources based on templates and feature tables. For more information, see the sdm prefer command.
Examples
This example shows how to configure the IP address for the Layer 2 switch on a subnetted network:
Switch(config)# interface vlan 1
Switch(config-if)# ip address 172.20.128.2 255.255.255.0
This example shows how to configure the IP address for a port on the Layer 3 switch:
Switch(config)# ip multicast-routing
Switch(config)# interface gigabitethernet6/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 172.20.128.2 255.255.255.0
You can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
ip igmp filter
Use the ip igmp filter interface configuration command on the switch stack or on a standalone switch to control whether or not all hosts on a Layer 2 interface can join one or more IP multicast groups by applying an Internet Group Management Protocol (IGMP) profile to the interface. Use the no form of this command to remove the specified profile from the interface.
ip igmp filter profile number
no ip igmp filter
Syntax Description
profile number |
The IGMP profile number to be applied. The range is 1 to 4294967295. |
Defaults
No IGMP filters are applied.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can apply IGMP filters only to Layer 2 physical interfaces; you cannot apply IGMP filters to routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
An IGMP profile can be applied to one or more switch port interfaces, but one port can have only one profile applied to it.
Examples
This example shows how to apply IGMP profile 22 to an interface.
Switch(config)# interface gigabitethernet1/0/12
Switch(config-if)# ip igmp filter 22
You can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
Related Commands
ip igmp max-groups
Use the ip igmp max-groups interface configuration command on the switch stack or on a standalone switch to set the maximum number of Internet Group Management Protocol (IGMP) groups that a Layer 2 interface can join. Use the no form of this command to set the maximum back to the default, which is to have no maximum limit.
ip igmp max-groups number
no ip igmp max-groups
Syntax Description
number |
The maximum number of IGMP groups that an interface can join. The range is 0 to 4294967294. The default is no limit. |
Defaults
No limit.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can use this command only on Layer 2 physical interfaces; you cannot set IGMP maximum groups for routed ports, switch virtual interfaces (SVIs), or ports that belong to an EtherChannel group.
Examples
This example shows how to limit the number of IGMP groups that an interface can join to 25.
Switch(config)# interface gigabitethernet1/0/12
Switch(config-if)# ip igmp max-groups 25
You can verify your setting by using the show running-config privileged EXEC command and by specifying an interface.
Related Commands
ip igmp profile
Use the ip igmp profile global configuration command on the switch stack or on a standalone switch to create an Internet Group Management Protocol (IGMP) profile and enter IGMP profile configuration mode. From this mode, you can specify the configuration of the IGMP profile to be used for filtering IGMP membership reports from a switchport. Use the no form of this command to delete the IGMP profile.
ip igmp profile profile number
no ip igmp profile profile number
Syntax Description
profile number |
The IGMP profile number being configured. The range is 1 to 4294967295. |
Defaults
No IGMP profiles are defined. When configured, the default action for matching an IGMP profile is to deny matching addresses.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
When you are in IGMP profile configuration mode, you can create the profile by using these commands:
•deny: specifies that matching addresses are denied; this is the default condition.
•exit: exits from igmp-profile configuration mode.
•no: negates a command or resets to its defaults.
•permit: specifies that matching addresses are permitted.
•range: specifies a range of IP addresses for the profile. This can be a single IP address or a range with a start and an end address.
When entering a range, enter the low IP multicast address, a space, and the high IP multicast address.
You can apply an IGMP profile to one or more Layer 2 interfaces, but each interface can have only one profile applied to it.
Examples
This example shows how to configure IGMP profile 40 that permits the specified range of IP multicast addresses.
Switch(config)# ip igmp profile 40
Switch(config-igmp-profile)# permit
Switch(config-igmp-profile)# range 233.1.1.1 233.255.255.255
You can verify your settings by using the show ip igmp profile privileged EXEC command.
Related Commands
|
|
---|---|
Applies the IGMP profile to the specified interface. |
|
Displays the characteristics of all IGMP profiles or the specified IGMP profile number. |
ip igmp snooping
Use the ip igmp snooping global configuration command on the switch stack or on a standalone switch to globally enable Internet Group Management Protocol (IGMP) snooping on the switch or to enable it on a VLAN. Use the command with keywords to enable and configure IGMP snooping on a VLAN interface. Use the no form of this command to disable IGMP snooping or to reset the parameters to the default settings.
ip igmp snooping [vlan vlan-id [immediate-leave | mrouter {interface interface-id | learn {cgmp | pim-dvmrp}} | static ip-address interface interface-id]]
no ip igmp snooping [vlan vlan-id [immediate-leave | mrouter {interface interface-id | learn {cgmp | pim-dvmrp}} | static ip-address interface interface-id]]
Syntax Description
Note Though visible in the command-line help string, the source-only-learning and tcn keywords are not supported.
Defaults
IGMP snooping is globally enabled on the switch.
IGMP snooping is enabled on VLAN interfaces.
IGMP immediate-leave processing is disabled.
The default learning method is pim-dvmrp—to snoop IGMP queries and PIM-DVMRP packets.
By default, there are no ports specified as members of a static multicast group.
By default, there are no multicast router ports.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
When IGMP snooping is enabled globally, it is enabled in all the existing VLAN interfaces. When IGMP snooping is disabled globally, it is disabled on all the existing VLAN interfaces.
You should only configure the Immediate Leave feature when there is a maximum of one receiver on every port in the VLAN. The configuration is saved in nonvolatile RAM (NVRAM).
The Immediate Leave feature is supported only with IGMP version 2 hosts.
The CGMP learn method is useful for reducing control traffic.
The static keyword is used for configuring the IGMP member ports statically.
The enabled configuration (globally or per VLAN), the learn method, and the static ports and groups are saved in nonvolatile RAM (NVRAM).
Examples
This example shows how to globally enable IGMP snooping:
Switch(config)# ip igmp snooping
This example shows how to globally disable IGMP snooping:
Switch(config)# no ip igmp snooping
This example shows how to enable IGMP snooping on VLAN 1:
Switch(config)# ip igmp snooping vlan 1
This example shows how to disable IGMP snooping on VLAN 1:
Switch(config)# no ip igmp snooping vlan 1
This example shows how to enable IGMP immediate-leave processing on VLAN 1:
Switch(config)# ip igmp snooping vlan 1 immediate-leave
This example shows how to disable IGMP immediate-leave processing on VLAN 1:
Switch(config)# no ip igmp snooping vlan 1 immediate-leave
This example shows how to configure Gigabit Ethernet interface 2 on stack member 1 as a multicast router port:
Switch(config)# ip igmp snooping vlan 1 mrouter interface gigabitethernet1/0/2
This example shows how to specify the multicast router learning method as CGMP:
Switch(config)# no ip igmp snooping vlan 1 mrouter learn cgmp
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
|
|
---|---|
Enables IGMP report suppression. |
|
Displays the snooping configuration. |
|
Displays the IGMP snooping router ports. |
|
Displays IGMP snooping multicast information. |
ip igmp snooping report-suppression
Use the ip igmp snooping report-supression global configuration command on the switch stack or on a standalone switch to enable Internet Group Management Protocol (IGMP) report suppression. Use the no form of this command to disable IGMP report suppression and forward all IGMP reports to multicast routers.
ip igmp snooping report-suppression
no ip igmp snooping report-suppression
Syntax Description
This command has no arguments or keywords.
Defaults
IGMP report suppression is enabled. The switch sends only one IGMP report per multicast router query to the multicast devices.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(19)EA1 |
This command was introduced. |
Usage Guidelines
When IGMP report suppression is enabled, the switch sends only one IGMP report per multicast router query to the multicast devices. The switch sends the first IGMP report from all hosts for a group to all the multicast routers and does not send the remaining IGMP reports to the multicast routers. If a mulitcast router query includes requests for IGMPv1 and IGMPv2 reports, the switch sensd both types of reports. IGMP report suppression prevents duplicate reports from being sent to the multicast devices.
If you disable IGMP report suppression by entering the no ip igmp snooping report-suppression command, all IGMP reports are forwarded to all the multicast routers.
Examples
This example shows how to disable report suppression:
Switch(config)# no ip igmp snooping report-suppression
This example shows how to enable report suppression:
Switch(config)# ip igmp snooping report-suppression
You can verify your settings by entering the show ip igmp snooping privileged EXEC command.
Related Commands
ip ssh
Use the ip ssh global configuration command on the switch stack or on a standalone switch to configure the switch to run Secure Shell (SSH) version 1 or SSH version 2. Use the no form of this command to return to the default setting.
ip ssh [v1 | v2]
no ip ssh [v1 | v2]
This command is available only when your switch is running the cryptographic (encrypted) software image.
Syntax Description
v1 |
Configure the switch to run SSH version 1 (SSHv1). This is the default. |
v2 |
Configure the switch to run SSH version 2 (SSHv1). |
Defaults
The default version is SSH version 1.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(19)EA1 |
This command was introduced. |
Usage Guidelines
If your switch is running SSH version 1, the switch can support the SSH server or the SSH client. If your switch is running SSH version 2, the switch can support only the SSH server. For more information about the SSH server and the SSH client, refer to the software configuration guide for this release.
Follow these guidelines when configuring the switch to run SSH version 1 or SSH version 2:
•When you are connecting to a remote device through a secure, encrypted connection by using the SSH client, make sure your switch runs SSH version 1.
•If a switch is configured as an SSHv2 server, a remote device running SSH version 2 can use the switch for authentication when the device is connecting to another device through a secure, encrypted connection.
•An RSA key pair generated by a SSHv1 server can be used by an SSHv2 server, and the reverse.
Examples
This example shows how to configure the switch to run SSH version 2:
Switch(config)# ip ssh v2
You can verify your settings by entering the show ip ssh or show ssh privileged EXEC command.
Related Commands
lacp port-priority
Use the lacp port-priority interface configuration command on the switch stack or on a standalone switch to configure the port priority for the Link Aggregation Control Protocol (LACP). Use the no form of this command to return to the default setting.
lacp port-priority priority
no lacp port-priority
Syntax Description
priority |
Port priority for LACP. The range is 1 to 65535. |
Defaults
The default is 32768.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
This command takes effect only on EtherChannel interfaces that are already configured for LACP.
The software assigns to every link between systems that operate LACP a unique priority made up of the system priority, system ID, port priority, and the port number. In priority comparisons, numerically lower values have higher priority. The priority determines which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating.
Ports are considered for active use in aggregation in link-priority order starting with the port attached to the highest priority link. Each port is selected for active use if the preceding higher priority selections can also be maintained. Otherwise, the port is selected for standby mode. Use the show etherchannel summary privileged EXEC command to see which ports are in the hot-standby mode (denoted with an H port-state flag).
The lower the priority, the more likely that the interface will be used for LACP transmission.
For information about configuring LACP on physical interfaces, refer to the "Configuring EtherChannels" chapter in the software configuration guide for this release.
Examples
This example shows how to configure the LACP port priority on Gigabit Ethernet interface 0/1 on stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# lacp port-priority 1000
You can verify your settings by entering the show lacp [channel-group-number] internal privileged EXEC command.
Related Commands
|
|
---|---|
Assigns an Ethernet interface to an EtherChannel group. |
|
Configures the LACP system priority. |
|
show lacp [channel-group-number] internal |
Displays internal information for all channel groups or for the specified channel group. |
lacp system-priority
Use the lacp system-priority global configuration command on the switch stack or on a standalone switch to configure the system priority for the Link Aggregation Control Protocol (LACP). Use the no form of this command to return to the default setting.
lacp system-priority priority
no lacp system-priority
Syntax Description
priority |
System priority for LACP. The range is 1 to 65535. |
Defaults
The default is 32768.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
Although this is a global configuration command, the priority takes effect only on EtherChannels that have physical interfaces that are already configured for LACP.
The software assigns to every link between systems that operate LACP a unique priority made up of the system priority, system ID, port priority, and the port number. In priority comparisons, numerically lower values have higher priority. The priority determines which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating.
Ports are considered for active use in aggregation in link-priority order, starting with the port attached to the highest priority link. Each port is selected for active use if the preceding higher priority selections can also be maintained. Otherwise, the port is selected for standby mode. Use the show etherchannel summary privileged EXEC command to see which ports are in the hot-standby mode (denoted with an H port-state flag).
The lower the priority, the more likely that the interface will be used for LACP transmission.
For more information about configuring LACP on physical interfaces, refer to the "Configuring EtherChannels" chapter in the software configuration guide for this release.
Examples
This example shows how to set the LACP system priority:
Switch(config)# lacp system-priority 20000
You can verify your settings by entering the show lacp sys-id privileged EXEC command.
Related Commands
|
|
---|---|
Assigns an Ethernet interface to an EtherChannel group. |
|
Configures the LACP port priority. |
|
show lacp sys-id |
Display the system identifier that is being used by LACP. |
logging file
Use the logging file global configuration command on the switch stack or on a standalone switch to set logging file parameters. Use the no form of this command to return to the default setting.
logging file filesystem:filename [max-file-size [min-file-size]] [severity-level-number | type]
no logging file filesystem:filename [severity-level-number | type]
Syntax Description
Defaults
The minimum file size is 2048 bytes; the maximum file size is 4096 bytes.
The default severity level is 7 (debugging messages and numerically lower levels).
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The log file is stored in ASCII text format in an internal buffer on a standalone switch, and in the case of a switch stack, on the stack master. If a standalone switch or the stack master fails, the log is lost unless you had previously saved it to Flash memory by using the logging file flash:filename global configuration command.
The log file is stored in ASCII text format in an internal buffer on the switch. You can access logged system messages by using the switch command-line interface (CLI) or by saving them to a properly configured syslog server. If the switch fails, the log is lost unless you had previously saved it to Flash memory by using the logging file flash:filename global configuration command.
After saving the log to Flash memory by using the logging file flash:filename global configuration command, you can use the more flash:filename privileged EXEC command to display its contents.
The command rejects the minimum file size if it is greater than the maximum file size minus 1024; the minimum file size then becomes the maximum file size minus 1024.
Specifying a level causes messages at that level and numerically lower levels to be displayed.
Examples
This example shows how to save informational log messages to a file in Flash memory:
Switch(config)# logging file flash:logfile informational
You can verify your setting by entering the show running-config privileged EXEC command.
Related Commands
mac access-group
Use the mac access-group interface configuration command on the switch stack or on a standalone switch to apply a MAC access control list (ACL) to a Layer 2 interface. Use the no form of this command to remove all MAC ACLs or the specified MAC ACL from the interface. You create the MAC ACL by using the mac access-list extended global configuration command.
mac access-group {name} in
no mac access-group {name}
Syntax Description
name |
Specify a named MAC access list. |
in |
Specify that the ACL is applied in the ingress direction. Outbound ACLs are not supported on Layer 2 interfaces. |
Defaults
No MAC ACL is applied to the interface.
Command Modes
Interface configuration (Layer 2 interfaces only)
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
You can apply MAC ACLs only to ingress Layer 2 interfaces. You cannot apply MAC ACLs to Layer 3 interfaces.
On Layer 2 interfaces, you can filter IP traffic by using IP access lists and non-IP traffic by using MAC access lists. You can filter both IP and non-IP traffic on the same Layer 2 interface by applying both an IP ACL and a MAC ACL to the interface. You can apply no more than one IP access list and one MAC access list to the same Layer 2 interface.
If a MAC ACL is already configured on a Layer 2 interface and you apply a new MAC ACL to the interface, the new ACL replaces the previously configured one.
If you apply an ACL to a Layer 2 interface on a switch, and the switch has an input Layer 3 ACL or a VLAN map applied to a VLAN that the interface is a member of, the ACL applied to the Layer 2 interface takes precedence.
When an inbound packet is received on an interface with a MAC ACL applied, the switch checks the match conditions in the ACL. If the conditions are matched, the switch forwards or drops the packet, according to the ACL.
If the specified ACL does not exist, the switch forwards all packets.
Note For more information about configuring MAC extended ACLs, refer to the "Configuring Network Security with ACLs" chapter in the software configuration guide for this release.
Examples
This example shows how to apply a MAC extended ACL named macacl2 to an interface:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mac access-group macacl2 in
You can verify your settings by entering the show mac access-group privileged EXEC command. You can view configured ACLs on the switch by entering the show access-lists privileged EXEC command.
Related Commands
mac access-list extended
Use the mac access-list extended global configuration command on the switch stack or on a standalone switch to create an access list based on MAC addresses for non-IP traffic. Using this command puts you in the extended MAC access list configuration mode. Use the no form of this command to return to the default setting.
Note You cannot apply named MAC extended ACLs to Layer 3 interfaces.
mac access-list extended name
no mac access-list extended name
Syntax Description
name |
Assign a name to the MAC extended access list. |
Defaults
By default, there are no MAC access lists created.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
MAC named extended lists are used with VLAN maps and class maps.
You can apply named MAC extended ACLs to VLAN maps or to Layer 2 interfaces; you cannot apply named MAC extended ACLs to Layer 3 interfaces.
Entering the mac access-list extended command enables the MAC-access list configuration mode. These configuration commands are available:
•default: sets a command to its default.
•deny: specifies packets to reject. For more information, see the deny MAC-access list configuration command.
•exit: exits from MAC-access list configuration mode.
•no: negates a command or sets its defaults.
•permit: specifies packets to forward. For more information, see the permit command.
Note For more information about MAC extended access lists, refer to the software configuration guide for this release.
Examples
This example shows how to create a MAC named extended access list named mac1 and to enter extended MAC access list configuration mode:
Switch(config)# mac access-list extended mac1
Switch(config-ext-macl)#
This example shows how to delete MAC named extended access list mac1:
Switch(config)# no mac access-list extended mac1
You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
mac address-table aging-time
Use the mac address-table aging-time global configuration command on the switch stack or on a standalone switch to set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated. Use the no form of this command to return to the default setting. The aging time applies to all VLANs or a specified VLAN.
mac address-table aging-time {0 | 10-1000000} [vlan vlan-id]
no mac address-table aging-time {0 | 10-1000000} [vlan vlan-id]
Note Beginning with Cisco IOS Release 12.1(19)EA1, the mac address-table aging-time command replaces the mac-address-table aging-time command (with the hyphen). The mac- address-table aging-time command (with the hyphen) will become obsolete in a future release.
Syntax Description
Defaults
The default is 300 seconds.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(19)EA1 |
The mac-address-table aging-time command was replaced by the mac address-table aging-time command. |
Usage Guidelines
If hosts do not send continuously, increase the aging time to record the dynamic entries for a longer time. Increasing the time can reduce the possibility of flooding when the hosts send again.
If you do not specify a specific VLAN, this command sets the aging time for all VLANs.
Examples
This example shows how to set the aging time to 200 seconds for all VLANs:
Switch(config)# mac address-table aging-time 200
You can verify your setting by entering the show mac address-table aging-time privileged EXEC command.
Related Commands
|
|
---|---|
Displays the MAC address table aging time for all VLANs or the specified VLAN. |
mac address-table notification
Use the mac address-table notification global configuration command on the switch stack or on a standalone switch to enable the MAC address notification feature on the switch stack. Use the no form of this command to return to the default setting.
mac address-table notification [history-size value] | [interval value]
no mac address-table notification [history-size | interval]
Note Beginning with Cisco IOS Release 12.1(19)EA1, the mac address-table notification command replaces the mac-address-table notification command (with the hyphen). The mac- address-table notification command (with the hyphen) will become obsolete in a future release.
Syntax Description
Defaults
By default, the MAC address notification feature is disabled.
The default trap interval value is 1 second.
The default number of entries in the history table is 1.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(19)EA1 |
The mac-address-table notification command was replaced by the mac address-table notification command. |
Usage Guidelines
The MAC address notification feature sends Simple Network Management Protocol (SNMP) traps to the network management system (NMS) whenever a new MAC address is added or an old address is deleted from the forwarding tables. MAC notifications are generated only for dynamic and secure MAC addresses. Events are not generated for self addresses, multicast addresses, or other static addresses.
When you configure the history-size option, the existing MAC address history table is deleted, and a new table is created.
You enable the MAC address notification feature by using the mac address-table notification command. You must also enable MAC address notification traps on an interface by using the snmp trap mac-notification interface configuration command and configure the switch to send MAC address traps to the NMS by using the snmp-server enable traps mac-notification global configuration command.
Examples
This example shows how to enable the MAC address-table notification feature, set the interval time to 60 seconds, and set the history-size to 100 entries:
Switch(config)# mac address-table notification
Switch(config)# mac address-table notification interval 60
Switch(config)# mac address-table notification history-size 100
You can verify your settings by entering the show mac address-table notification privileged EXEC command.
Related Commands
|
|
---|---|
clear mac address-table notification |
Clears the MAC address notification global counters. |
Displays the MAC address notification settings on all interfaces or on the specified interface. |
|
Sends the SNMP MAC notification traps when the mac-notification keyword is appended. |
|
Enables the SNMP MAC notification trap on a specific interface. |
mac address-table static
Use the mac address-table static global configuration command on the switch stack or on a standalone switch to add static addresses to the MAC address table. Use the no form of this command to remove static entries from the table.
mac address-table static mac-addr vlan vlan-id interface interface-id
no mac address-table static mac-addr vlan vlan-id interface interface-id
Note Beginning with Cisco IOS Release 12.1(19)EA1, the mac address-table static command replaces the mac-address-table static command (with the hyphen). The mac- address-table static command (with the hyphen) will become obsolete in a future release.
Syntax Description
Defaults
No static addresses are configured.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(19)EA1 |
The mac-address-table static command was replaced by the mac address-table static command. |
Examples
This example shows how to add the static address c2f3.220a.12f4 to the MAC address table. When a packet is received in VLAN 4 with this MAC address as its destination, the packet is forwarded to the specified interface:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 interface gigabitethernet6/0/1
You can verify your setting by entering the show mac address-table privileged EXEC command.
Related Commands
|
|
---|---|
Displays static MAC address table entries only. |
mac address-table static drop
Use the mac address-table static drop global configuration command on the switch stack or on a standalone switch to enable unicast MAC address filtering and to configure the switch to drop traffic with a specific source or destination MAC address. Use the no form of this command to return to the default setting.
mac address-table static mac-addr vlan vlan-id drop
no mac address-table static mac-addr vlan vlan-id
Syntax Description
Defaults
Unicast MAC address filtering is disabled. The switch does not drop traffic for specific source or destination MAC addresses.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(19)EA1 |
This command was first introduced. |
Usage Guidelines
Follow these guidelines when using this feature:
•Multicast MAC addresses, broadcast MAC addresses, and router MAC addresses are not supported. Packets that are forwarded to the CPU are also not supported.
•If you configure a unicast MAC address as a static address and then configure the switch to drop packets with this MAC address or the reverse, the second command that you entered overrides the first command.
Examples
This example shows how to enable unicast MAC address filtering and to configure the switch to drop packets that have a source or destination address of c2f3.220a.12f4. When a packet is received in VLAN 4 with this MAC address as its source or destination, the packet is dropped:
Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 drop
This example shows how to disable unicast MAC address filtering:
Switch(config)# no mac address-table static c2f3.220a.12f4 vlan 4
You can verify your setting by entering the show mac address-table static privileged EXEC command.
Related Commands
|
|
---|---|
Displays static MAC address table entries only. |
match (access-map configuration)
Use the match access-map configuration command on the switch stack or on a standalone switch to set the VLAN map to match packets against one or more access lists. Use the no form of this command to remove the match parameters.
match {ip address {name | number} [name | number] [name | number]...} | {mac address {name} [name] [name]...}
no match {ip address {name | number} [name | number] [name | number]...} | {mac address {name} [name] [name]...}
Syntax Description
Defaults
The default action is to have no match parameters applied to a VLAN map.
Command Modes
Access-map configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You enter access-map configuration mode by using the vlan access-map global configuration command.
You must enter one access list name or number; others are optional. You can match packets against one or more access lists. Matching any of the lists counts as a match of the entry.
In access-map configuration mode, use the match command to define the match conditions for a VLAN map applied to a VLAN. Use the action command to set the action that occurs when the packet matches the conditions.
Packets are matched only against access lists of the same protocol type; IP packets are matched against IP access lists, and all other packets are matched against MAC access lists.
Both IP and MAC addresses can be specified for the same map entry.
Examples
This example shows how to define and apply a VLAN access map vmap4 to VLANs 5 and 6 that will cause the interface to drop an IP packet if the packet matches the conditions defined in access list al2.
Switch(config)# vlan access-map vmap4
Switch(config-access-map)# match ip address al2
Switch(config-access-map)# action drop
Switch(config-access-map)# exit
Switch(config)# vlan filter vmap4 vlan-list 5-6
You can verify your settings by entering the show vlan access-map privileged EXEC command.
Related Commands
match (class-map configuration)
Use the match class-map configuration command on the switch stack or on a standalone switch to define the match criteria to classify traffic. Use the no form of this command to remove the match criteria.
match {access-group acl-index-or-name | ip dscp dscp-list | ip precedence ip-precedence-list}
no match {access-group acl-index-or-name | ip dscp dscp-list | ip precedence ip-precedence-list}
Syntax Description
Note Though visible in the command-line help strings, the any, class-map, destination-address, input-interface, mpls, not, protocol, and source-address keywords are not supported.
Defaults
No match criteria are defined.
Command Modes
Class-map configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The match command is used to specify which fields in the incoming packets are examined to classify the packets. Only the IP access group or the MAC access group matching to the Ether Type/Len are supported.
To define packet classification on a physical-port basis, only one match command per class map is supported. In this situation, the match-all and match-any keywords are equivalent.
For the match ip dscp dscp-list or the match ip precedence ip-precedence-list command, you can enter a mnemonic name for a commonly-used value. For example, you can enter the match ip dscp af11 command, which is the same as entering the match ip dscp 10 command. You can enter the match ip precedence critical command, which is the same as entering the match ip precedence 5 command. For a list of supported mnemonics, enter the match ip dscp ? or the match ip precedence ? command to see the command-line help strings.
This example shows how to create a class map called class2, which matches all the incoming traffic with DSCP values of 10, 11, and 12:
Switch(config)# class-map class2
Switch(config-cmap)# match ip dscp 10 11 12
Switch(config-cmap)# exit
This example shows how to create a class map called class3, which matches all the incoming traffic with IP-precedence values of 5, 6, and 7:
Switch(config)# class-map class3
Switch(config-cmap)# match ip precedence 5 6 7
Switch(config-cmap)# exit
This example shows how to delete the IP-precedence match criteria and to classify traffic using acl1:
Switch(config)# class-map class2
Switch(config-cmap)# match ip precedence 5 6 7
Switch(config-cmap)# no match ip precedence
Switch(config-cmap)# match access-group acl1
Switch(config-cmap)# exit
You can verify your settings by entering the show class-map privileged EXEC command.
Related Commands
|
|
---|---|
Creates a class map to be used for matching packets to the class whose name you specify. |
|
Displays quality of service (QoS) class maps. |
mdix auto
Use the mdix auto interface configuration command on the switch stack or on a standalone switch to enable the automatic media-dependent-interface crossover (Auto-MDIX) feature on the interface. When Auto-MDIX is enabled, the interface automatically detects the required cable connection type (straight-through or crossover) and configures the connection appropriately. Use the no form of this command to disable Auto-MDIX.
mdix auto
no mdix auto
Syntax Description
This command has no arguments or keywords.
Defaults
The default is Auto-MDIX disabled.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(14)EA1 |
This command was first introduced. |
Usage Guidelines
When you enable Auto-MDIX on an interface, you must also set the speed and duplex on the interface to auto so that the feature operates correctly.
When Auto-MDIX (along with autonegotiation of speed and duplex) is enabled on one or both of connected interfaces, link up occurs, even if the cable type (straight through or crossover) is incorrect.
Auto-MDIX is supported on all 10/100 and 10/100/1000-Mbps interfaces and on 10/100/1000BASE-T/TX small form-factor pluggable (SFP) module interfaces. It is not supported on 1000BASE-SX or -LX SFP module interfaces.
Examples
This example shows how to enable Auto-MDIX on Gigabit Ethernet interface 0/1 on stack member 1:
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# speed auto
Switch(config-if)# duplex auto
Switch(config-if)# mdix auto
Switch(config-if)# end
You can verify the operational state of Auto-MDIX on the interface by entering the show controllers ethernet-controller interface-id phy privileged EXEC command.
Related Commands
|
|
---|---|
show controllers ethernet-controller interface-id phy |
Displays general information about internal registers of an interface, including the operational state of Auto-MDIX. |
mls qos
Use the mls qos global configuration command on the switch stack or on a standalone switch to enable quality of service (QoS) for the entire switch. When the mls qos command is entered, QoS is enabled with the default parameters on all ports in the system. Use the no form of this command to reset all the QoS-related statistics and to disable the QoS features for the entire switch.
mls qos
no mls qos
Syntax Description
This command has no arguments or keywords.
Defaults
QoS is disabled. There is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).
When QoS is enabled with the mls qos global configuration command and all other QoS settings are set to their defaults, traffic is classified as best effort (the DSCP and CoS value is set to 0) without any policing. No policy maps are configured. The default port trust state on all ports is untrusted. The default ingress and egress queue settings are in effect.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
QoS must be globally enabled to use QoS classification, policing, mark down or drop, queueing, and traffic shaping features. You can create a policy-map and attach it to a port before entering the mls qos command. However, until you enter the mls qos command, QoS processing is disabled.
Policy-maps and class-maps used to configure QoS are not deleted from the configuration by the no mls qos command, but entries corresponding to policy maps are removed from the switch hardware to save system resources. To re-enable QoS with the previous configurations, use the mls qos command.
Toggling the QoS status of the switch with this command modifies (reallocates) the sizes of the queues. During the queue size modification, the queue is temporarily shut down during the hardware reconfiguration, and the switch drops newly arrived packets for this queue.
Examples
This example shows how to enable QoS on the switch:
Switch(config)# mls qos
You can verify your settings by entering the show mls qos privileged EXEC command.
Related Commands
|
|
---|---|
Displays QoS information. |
mls qos aggregate-policer
Use the mls qos aggregate-policer global configuration command on the switch stack or on a standalone switch to define policer parameters, which can be shared by multiple classes within the same policy map. A policer defines a maximum permissible rate of transmission, a maximum burst size for transmissions, and an action to take if either maximum is exceeded. Use the no form of this command to delete an aggregate policer.
mls qos aggregate-policer aggregate-policer-name rate-bps burst-byte exceed-action {drop | policed-dscp-transmit}
no mls qos aggregate-policer aggregate-policer-name
Syntax Description
Defaults
No aggregate policers are defined.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Define an aggregate policer if the policer is shared with multiple classes.
Policers for a port cannot be shared with other policers for another port; traffic from two different ports cannot be aggregated for policing purposes.
The port ASIC device, which controls more than one physical port, supports 256 policers (255 policers plus 1 no policer). The maximum number of policers supported per port is 64. Policers are allocated on demand by the software and are constrained by the hardware and ASIC boundaries. You cannot reserve policers per port (there is no guarantee that a port will be assigned to any policer).
You apply an aggregate policer to multiple classes in the same policy map; you cannot use an aggregate policer across different policy maps.
You cannot delete an aggregate policer if it is being used in a policy map. You must first use the no police aggregate aggregate-policer-name policy-map class configuration command to delete the aggregate policer from all policy maps before using the no mls qos aggregate-policer aggregate-policer-name command.
Policing uses a token-bucket algorithm. You configure the bucket depth (the maximum burst that is tolerated before the bucket overflows) by using the burst-byte option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. You configure how fast (the average rate) that the tokens are removed from the bucket by using the rate-bps option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. For more information, refer to the software configuration guide for this release.
Examples
This example shows how to define the aggregate policer parameters and how to apply the policer to multiple classes in a policy map:
Switch(config)# mls qos aggregate-policer agg_policer1 10000 1000000 exceed-action drop
Switch(config)# policy-map policy2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police aggregate agg_policer2
Switch(config-pmap-c)# exit
You can verify your settings by entering the show mls qos aggregate-policer privileged EXEC command.
Related Commands
|
|
---|---|
Creates a policer that is shared by different classes. |
|
Displays the quality of service (QoS) aggregate policer configuration. |
mls qos cos
Use the mls qos cos interface configuration command on the switch stack or on a standalone switch to define the default class of service (CoS) value of a port or to assign the default CoS to all incoming packets on the port. Use the no form of this command to return to the default setting.
mls qos cos {default-cos | override}
no mls qos cos {default-cos | override}
Syntax Description
Defaults
The default CoS value for a port is 0.
CoS override is disabled.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can use the default value to assign a CoS and Differentiated Services Code Point (DSCP) value to all incoming packets that are untagged (if the incoming packet does not have a CoS value). You also can assign a default CoS and DSCP value to all incoming packets by using the override keyword.
Use the override keyword when all incoming packets on certain ports deserve higher or lower priority than packets entering from other ports. Even if a port is previously set to trust DSCP, CoS, or IP precedence, this command overrides the previously configured trust state, and all the incoming CoS values are assigned the default CoS value configured with the mls qos cos command. If an incoming packet is tagged, the CoS value of the packet is modified with the default CoS of the port at the ingress port.
Examples
This example shows how to configure the default port CoS to 4 on Gigabit Ethernet interface 0/1 of stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust cos
Switch(config-if)# mls qos cos 4
This example shows how to assign all the packets entering a port to the default port CoS value of 4 on Gigabit Ethernet interface 0/1 of stack member 2:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos cos 4
Switch(config-if)# mls qos cos override
You can verify your settings by entering the show mls qos interface privileged EXEC command.
Related Commands
|
|
---|---|
Displays quality of service (QoS) information. |
mls qos dscp-mutation
Use the mls qos dscp-mutation interface configuration command on the switch stack or on a standalone switch to apply a Differentiated Services Code Point (DSCP)-to-DSCP-mutation map to a DSCP-trusted port. Use the no form of this command to return the map to the default settings (no DSCP mutation).
mls qos dscp-mutation dscp-mutation-name
no mls qos dscp-mutation dscp-mutation-name
Syntax Description
dscp-mutation-name |
Name of the DSCP-to-DSCP-mutation map. This map was previously defined with the mls qos map dscp-mutation global configuration command. |
Defaults
The default DSCP-to-DSCP-mutation map is a null map, which maps incoming DSCPs to the same DSCP values.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
If two quality of service (QoS) domains have different DSCP definitions, use the DSCP-to-DSCP-mutation map to translate one set of DSCP values to match the definition of another domain. You apply the DSCP-to-DSCP-mutation map to the receiving interface (ingress mutation) at the boundary of a quality of service (QoS) administrative domain.
With ingress mutation, the new DSCP value overwrites the one in the packet, and QoS handles the packet with this new value. The switch sends the packet out the interface with the new DSCP value.
You can configure multiple DSCP-to-DSCP-mutation maps on ingress ports.
You apply the map only to DSCP-trusted ports. If you apply the DSCP mutation map to an untrusted port, to class of service (CoS) or IP-precedence trusted port, the command has no immediate effect until the port becomes DSCP-trusted.
Examples
This example shows how to define the DSCP-to-DSCP-mutation map named dscpmutation1and to apply the map to a port on stack member 3:
Switch(config)# mls qos map dscp-mutation dscpmutation1 10 11 12 13 to 30
Switch(config)# interface gigabitethernet3/0/1
Switch(config-if)# mls qos trust dscp
Switch(config-if)# mls qos dscp-mutation dscpmutation1
This example show how to remove the DSCP-to-DSCP-mutation map name dscpmutation1 from the port and to reset the map to the default:
Switch(config-if)# no mls qos dscp-mutation dscpmutation1
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Related Commands
|
|
---|---|
mls qos map dscp-mutation |
Defines the DSCP-to-DSCP-mutation map. |
Configures the port trust state. |
|
Displays QoS mapping information. |
mls qos map
Use the mls qos map global configuration command on the switch stack or on a standalone switch to define the class of service (CoS)-to-Differentiated Services Code Point (DSCP) map, DSCP-to-CoS map, the DSCP-to-DSCP-mutation map, the IP-precedence-to-DSCP map, and the policed-DSCP map. Use the no form of this command to return to the default map.
mls qos map {cos-dscp dscp1...dscp8 | dscp-cos dscp-list to cos | dscp-mutation dscp-mutation-name in-dscp to out-dscp | ip-prec-dscp dscp1...dscp8 | policed-dscp dscp-list to mark-down-dscp}
no mls qos map {cos-dscp | dscp-cos | dscp-mutation dscp-mutation-name | ip-prec-dscp | policed-dscp}
Syntax Description
Defaults
Table 2-6 shows the default CoS-to-DSCP map:
CoS Value |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
DSCP Value |
0 |
8 |
16 |
24 |
32 |
40 |
48 |
56 |
Table 2-7 shows the default DSCP-to-CoS map:
DSCP Value |
0-7 |
8-15 |
16-23 |
24-31 |
32-39 |
40-47 |
48-55 |
56-63 |
CoS Value |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
Table 2-8 shows the default IP-precedence-to-DSCP map:
IP Precedence Value |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
DSCP Value |
0 |
8 |
16 |
24 |
32 |
40 |
48 |
56 |
The default DSCP-to-DSCP-mutation map is a null map, which maps an incoming DSCP value to the same DSCP value.
The default policed-DSCP map is a null map, which maps an incoming DSCP value to the same DSCP value.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
All the maps are globally defined. All the maps, except the DSCP-to-DSCP-mutation map, are applied to all ports. The DSCP-to-DSCP-mutation map is applied to a specific port.
Examples
This example shows how to define the IP-precedence-to-DSCP map and to map IP-precedence values 0 to 7 to DSCP values of 0, 10, 20, 30, 40, 50, 55, and 60:
Switch# configure terminal
Switch(config)# mls qos map ip-prec-dscp 0 10 20 30 40 50 55 60
This example shows how to define the policed-DSCP map. DSCP values 1, 2, 3, 4, 5, and 6 are marked down to DSCP value 0. Marked DSCP values that not explicitly configured are not modified:
Switch# configure terminal
Switch(config)# mls qos map policed-dscp 1 2 3 4 5 6 to 0
This example shows how to define the DSCP-to-CoS map. DSCP values 20, 21, 22, 23, and 24 are mapped to CoS 1. DSCP values 10, 11, 12, 13, 14, 15, 16, and 17 are mapped to CoS 0:
Switch# configure terminal
Switch(config)# mls qos map dscp-cos 20 21 22 23 24 to 1
Switch(config)# mls qos map dscp-cos 10 11 12 13 14 15 16 17 to 0
This example shows how to define the CoS-to-DSCP map. CoS values 0 to 7 are mapped to DSCP values 0, 5, 10, 15, 20, 25, 30, and 35:
Switch# configure terminal
Switch(config)# mls qos map cos-dscp 0 5 10 15 20 25 30 35
This example shows how to define the DSCP-to-DSCP-mutation map. All the entries that are not explicitly configured are not modified (remain as specified in the null map):
Switch# configure terminal
Switch(config)# mls qos map dscp-mutation mutation1 1 2 3 4 5 6 7 to 10
Switch(config)# mls qos map dscp-mutation mutation1 8 9 10 11 12 13 to 10
Switch(config)# mls qos map dscp-mutation mutation1 20 21 22 to 20
Switch(config)# mls qos map dscp-mutation mutation1 0 31 32 33 34 to 30
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Related Commands
|
|
---|---|
Applies a DSCP-to-DSCP-mutation map to a DSCP-trusted port. |
|
Displays quality of service (QoS) mapping information. |
mls qos queue-set output buffers
Use the mls qos queue-set output buffers global configuration command on the switch stack or on a standalone switch to allocate buffers to a queue-set (four egress queues per port). Use the no form of this command to return to the default setting.
mls qos queue-set output qset-id buffers allocation1 ... allocation4
no mls qos queue-set output qset-id buffers
Syntax Description
Defaults
All allocation values are equally mapped among the four queues (25, 25, 25, 25). Each queue has 1/4 of the buffer space.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Specify four allocation values, and separate each with a space.
Allocate buffers according to the importance of the traffic; for example, give a large percentage of the buffer to the queue with the highest-priority traffic.
To configure different classes of traffic with different characteristics, use this command with the mls qos queue-set output qset-id threshold global configuration command.
Note The egress queue default settings are suitable for most situations. You should change them only when you have a thorough understanding of the egress queues and if these settings do not meet your QoS solution.
Examples
This example shows how to map Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1 to queue-set 2. It allocates 40 percent of the buffer space to egress queue 1 and 20 percent to egress queues 2, 3, and 4:
Switch(config)# mls qos queue-set output 2 buffers 40 20 20 20
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show mls qos queue-set privileged EXEC command.
Related Commands
|
|
---|---|
Configures the weighted tail-drop (WTD) thresholds, guarantees the availability of buffers, and configures the maximum memory allocation to a queue-set. |
|
Maps a port to a queue-set. |
|
show mls qos interface buffers |
Displays quality of service (QoS) information. |
Displays egress queue settings for the queue-set. |
mls qos queue-set output threshold
Use the mls qos queue-set output threshold global configuration command on the switch stack or on a standalone switch to configure the weighted tail-drop (WTD) thresholds, to guarantee the availability of buffers, and to configure the maximum memory allocation to a queue-set (four egress queues per port). Use the no form of this command to return to the default setting.
mls qos queue-set output qset-id threshold queue-id drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold
no mls qos queue-set output qset-id threshold [queue-id]
Syntax Description
Defaults
When quality of service (QoS) is enabled, WTD is enabled.
Table 2-9 shows the default WTD threshold settings.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Use the mls qos queue-set output qset-id buffers global configuration command to allocate a fixed number of buffers to the four queues in a queue-set.
The drop-threshold percentages can exceed 100 percent and can be up to the maximum (if the maximum threshold exceeds 100 percent).
Note The egress queue default settings are suitable for most situations. You should change them only when you have a thorough understanding of the egress queues and if these settings do not meet your QoS solution.
The switch uses a buffer allocation scheme to reserve a minimum amount of buffers for each egress queue, to prevent any queue or port from consuming all the buffers and depriving other queues, and to determine whether to grant buffer space to a requesting queue. The switch determines whether the target queue has not consumed more buffers than its reserved amount (under-limit), whether it has consumed all of its maximum buffers (over-limit), and whether the common pool is empty (no free buffers) or not empty (free buffers). If the queue is not over-limit, the switch can allocate buffer space from the reserved pool or from the common pool (if it is not empty). If there are no free buffers in the common pool or if the queue is over-limit, the switch drops the frame.
Examples
This example shows how to map Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1 to queue-set 2. It configures the drop thresholds for queue 2 to 40 and 60 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory, and configures 200 percent as the maximum memory this queue can have before packets are dropped:
Switch(config)# mls qos queue-set output 2 threshold 2 40 60 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show mls qos queue-set privileged EXEC command.
Related Commands
|
|
---|---|
Allocates buffers to a queue-set. |
|
Maps a port to a queue-set. |
|
show mls qos interface buffers |
Displays QoS information. |
Displays egress queue settings for the queue-set. |
mls qos srr-queue input bandwidth
Use the mls qos srr-queue input bandwidth global configuration command on the switch stack or on a standalone switch to assign shaped round robin (SRR) weights to an ingress queue. The ratio of the weights is the ratio of the frequency in which the SRR scheduler dequeues packets from each queue. Use the no form of this command to return to the default setting.
mls qos srr-queue input bandwidth weight1 weight2
no mls qos srr-queue input bandwidth
Syntax Description
Defaults
Weight1 and weight2 are 4 (1/2 of the bandwidth is equally shared between the two queues).
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
SRR services the priority queue for its configured weight as specified by the bandwidth keyword in the mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command. Then SRR shares the remaining bandwidth with both ingress queues and services them as specified by the weights configured with the mls qos srr-queue input bandwidth weight1 weight2 global configuration command.
You specify which ingress queue is the priority queue by using the mls qos srr-queue input priority-queue global configuration command.
Examples
This example shows how to assign the ingress bandwidth for the queues in the stack. Priority queueing is disabled, and the shared bandwidth ratio allocated to queue 1 is 25/(25+75) and to queue 2 is 75/(25+75):
Switch(config)# mls qos srr-queue input priority-queue 2 bandwidth 0
Switch(config)# mls qos srr-queue input bandwidth 25 75
In this example, queue 2 has three times the bandwidth of queue 1; queue 2 is serviced three times as often as queue 1.
This example shows how to assign the ingress bandwidths for the queues in the stack. Queue 1 is the priority queue with 10 percent of the bandwidth allocated to it. The bandwidth ratio allocated to queues 1 and 2 is 4/(4+4). SRR services queue 1 (the priority queue) first for its configured 10 percent bandwidth. Then SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and 2 by allocating 45 percent to each queue:
Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10
Switch(config)# mls qos srr-queue input bandwidth 4 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing or the show mls qos input-queue privileged EXEC command.
Related Commands
|
|
---|---|
Allocates the buffers between the ingress queues. |
|
Maps class of service (CoS) values to an ingress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps Differentiated Services Code Point (DSCP) values to an ingress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the ingress priority queue and guarantees bandwidth. |
|
Assigns weighted tail-drop (WTD) threshold percentages to an ingress queue. |
|
Displays ingress queue settings. |
|
show mls qos interface queueing |
Displays quality of service (QoS) information. |
mls qos srr-queue input buffers
Use the mls qos srr-queue input buffers global configuration command on the switch stack or on a standalone switch to allocate the buffers between the ingress queues. Use the no form of this command to return to the default setting.
mls qos srr-queue input buffers percentage1 percentage2
no mls qos srr-queue input buffers
Syntax Description
percentage1 percentage2 |
Percentage of buffers allocated to ingress queues 1 and 2. The range is 0 to 100. Separate each value with a space. |
Defaults
Ninety percent of the buffers is allocated to queue 1, and 10 percent of the buffers is allocated to queue 2.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You should allocate the buffers so that the queues can handle any incoming bursty traffic.
Examples
This example shows how to allocate 60 percent of the buffer space to ingress queue 1 and 40 percent of the buffer space to ingress queue 2:
Switch(config)# mls qos srr-queue input buffers 60 40
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show mls qos input-queue privileged EXEC command.
Related Commands
|
|
---|---|
Assigns shaped round robin (SRR) weights to an ingress queue. |
|
Maps class of service (CoS) values to an ingress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps Differentiated Services Code Point (DSCP) values to an ingress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the ingress priority queue and guarantees bandwidth. |
|
Assigns weighted tail-drop (WTD) threshold percentages to an ingress queue. |
|
Displays ingress queue settings. |
|
show mls qos interface buffers |
Displays quality of service (QoS) information. |
mls qos srr-queue input cos-map
Use the mls qos srr-queue input cos-map global configuration command on the switch stack or on a standalone switch to map class of service (CoS) values to an ingress queue or to map CoS values to a queue and to a threshold ID. Use the no form of this command to return to the default setting.
mls qos srr-queue input cos-map queue queue-id {cos1...cos8 | threshold threshold-id cos1...cos8}
no mls qos srr-queue input cos-map
Syntax Description
Defaults
Table 2-10 shows the default CoS input queue threshold map:
CoS Value |
0-4 |
5 |
6, 7 |
Queue ID - Threshold ID |
1 - 1 |
2 - 1 |
1 - 1 |
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The CoS assigned at the ingress port selects an ingress or egress queue and threshold.
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state. You can assign two weighted tail-drop (WTD) threshold percentages to an ingress queue by using the mls qos srr-queue input threshold global configuration command.
You can map each CoS value to a different queue and threshold combination, allowing the frame to follow different behavior.
Examples
This example shows how to map CoS values 0 to 3 to ingress queue 1 and to threshold ID 1 with a drop threshold of 50 percent. It maps CoS values 4 and 5 to ingress queue 1 and to threshold ID 2 with a drop threshold of 70 percent:
Switch(config)# mls qos srr-queue input cos-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos srr-queue input cos-map queue 1 threshold 2 4 5
Switch(config)# mls qos srr-queue input threshold 1 50 70
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Related Commands
mls qos srr-queue input dscp-map
Use the mls qos srr-queue input dscp-map global configuration command on the switch stack or on a standalone switch to map Differentiated Services Code Point (DSCP) values to an ingress queue or to map DSCP values to a queue and to a threshold ID. Use the no form of this command to return to the default setting.
mls qos srr-queue input dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id dscp1...dscp8}
no mls qos srr-queue input dscp-map
Syntax Description
Defaults
Table 2-11 shows the default DSCP input queue threshold map:
DSCP Value |
0-39 |
40-47 |
48-63 |
Queue ID - Threshold ID |
1 - 1 |
2 - 1 |
1 - 1 |
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The DSCP assigned at the ingress port selects an ingress or egress queue and threshold.
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state. You can assign two weighted tail-drop (WTD) threshold percentages to an ingress queue by using the mls qos srr-queue input threshold global configuration command.
You can map each DSCP value to a different queue and threshold combination, allowing the frame to follow different behavior.
You can map up to eight DSCP values per command.
Examples
This example shows how to map DSCP values 0 to 6 to ingress queue 1 and to threshold 1 with a drop threshold of 50 percent. It maps DSCP values 20 to 26 to ingress queue 1 and to threshold 2 with a drop threshold of 70 percent:
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 1 0 1 2 3 4 5 6
Switch(config)# mls qos srr-queue input dscp-map queue 1 threshold 2 20 21 22 23 24 25 26
Switch(config)# mls qos srr-queue input threshold 1 50 70
You can verify your settings by entering the show mls qos maps privileged EXEC command.
Related Commands
mls qos srr-queue input priority-queue
Use the mls qos srr-queue input priority-queue global configuration command on the switch stack or on a standalone switch to configure the ingress priority queue and to guarantee bandwidth on the stackinternal ring if the ring is congested. Use the no form of this command to return to the default setting.
mls qos srr-queue input priority-queue queue-id bandwidth weight
no mls qos srr-queue input priority-queue queue-id
Syntax Description
queue-id |
Ingress queue ID. The range is 1 to 2. |
bandwidth weight |
Bandwidth percentage of the stackinternal ring. The range is 0 to 40. |
Defaults
The priority queue is queue 2, and 10 percent of the bandwidth is allocated to it.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You should use the priority queue only for traffic that needs to be expedited (for example, voice traffic, which needs minimum delay and jitter).
The priority queue is guaranteed part of the bandwidth on the stackinternal ring, which reduces the delay and jitter under heavy network traffic on an oversubscribed ringstack (when there is more traffic than the backplane can carry, and the queues are full and dropping frames).
The amount of bandwidth that can be guaranteed is restricted because a large value affects the entire stack and can degrade the stack performance.
Shaped round robin (SRR) services the priority queue for its configured weight as specified by the bandwidth keyword in the mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command. Then SRR shares the remaining bandwidth with both ingress queues and services them as specified by the weights configured with the mls qos srr-queue input bandwidth weight1 weight2 global configuration command.
To disable priority queueing, set the bandwidth weigh to 0, for example, mls qos srr-queue input priority-queue queue-id bandwidth 0.
Examples
This example shows how to assign the ingress bandwidths for the queues in the stack. Queue 1 is the priority queue with 10 percent of the bandwidth allocated to it. The bandwidth ratio allocated to queues 1 and 2 is 4/(4+4). SRR services queue 1 (the priority queue) first for its configured 10 percent bandwidth. Then SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and 2 by allocating 45 percent to each queue:
Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10
Switch(config)# mls qos srr-queue input bandwidth 4 4
You can verify your settings by entering the show mls qos interface [interface-id] queueing or the show mls qos input-queue privileged EXEC command.
Related Commands
|
|
---|---|
Assigns shaped round robin (SRR) weights to an ingress queue. |
|
Allocates the buffers between the ingress queues. |
|
Maps class of service (CoS) values to an ingress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps Differentiated Services Code Point (DSCP) values to an ingress queue or maps DSCP values to a queue and to a threshold ID. |
|
Assigns weighted tail-drop (WTD) threshold percentages to an ingress queue. |
|
Displays ingress queue settings. |
|
show mls qos interface queueing |
Displays quality of service (QoS) information. |
mls qos srr-queue input threshold
Use the mls qos srr-queue input threshold global configuration command on the switch stack or on a standalone switch to assign weighted tail-drop (WTD) threshold percentages to an ingress queue. Use the no form of this command to return to the default setting.
mls qos srr-queue input threshold queue-id threshold-percentage1 threshold-percentage2
no mls qos srr-queue input threshold queue-id
Syntax Description
Defaults
When quality of service (QoS) is enabled, WTD is enabled.
The two WTD thresholds are set to 100 percent.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
QoS uses the CoS-to-threshold map or the DSCP-to-threshold map to determine which class of service (CoS) or Differentiated Services Code Points (DSCPs) values are mapped to threshold 1 and to threshold 2. If threshold 1 is exceeded, packets with CoS or DSCPs assigned to this threshold are dropped until the threshold is no longer exceeded. However, packets assigned to threshold 2 continue to be queued and sent as long as the second threshold is not exceeded.
Each queue has two configurable (explicit) drop threshold and one preset (implicit) drop threshold (full).
You configure the CoS-to-threshold map by using the mls qos srr-queue input cos-map global configuration command. You configure the DSCP-to-threshold map by using the mls qos srr-queue input dscp-map global configuration command.
Examples
This example shows how to configure the tail-drop thresholds for the two queues. The queue 1 thresholds are 50 percent and 100 percent, and the queue 2 thresholds are 70 percent and 100 percent:
Switch(config)# mls qos srr-queue input threshold 1 50 100
Switch(config)# mls qos srr-queue input threshold 2 70 100
You can verify your settings by entering the show mls qos interface [interface-id] buffers or the show mls qos input-queue privileged EXEC command.
Related Commands
|
|
---|---|
Assigns shaped round robin (SRR) weights to an ingress queue. |
|
Allocates the buffers between the ingress queues. |
|
Maps class of service (CoS) values to an ingress queue or maps CoS values to a queue and to a threshold ID. |
|
Maps Differentiated Services Code Point (DSCP) values to an ingress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the ingress priority queue and guarantees bandwidth. |
|
Displays ingress queue settings. |
|
show mls qos interface buffers |
Displays quality of service (QoS) information. |
mls qos srr-queue output cos-map
Use the mls qos srr-queue output cos-map global configuration command on the switch stack or on a standalone switch to map class of service (CoS) values to an egress queue or to map CoS values to a queue and to a threshold ID. Use the no form of this command to return to the default setting.
mls qos srr-queue output cos-map queue queue-id {cos1...cos8 | threshold threshold-id cos1...cos8}
no mls qos srr-queue output cos-map
Syntax Description
Defaults
Table 2-12 shows the default CoS output queue threshold map:
CoS Value |
0, 1 |
2, 3 |
4 |
5 |
6, 7 |
Queue ID - Threshold ID |
2 - 1 |
3 - 1 |
4 - 1 |
1 -1 |
4 - 1 |
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state.
Note The egress queue default settings are suitable for most situations. You should change them only when you have a thorough understanding of the egress queues and if these settings do not meet your quality of service (QoS) solution.
You can assign two weighted tail-drop (WTD) threshold percentages to an egress queue by using the mls qos queue-set output qset-id threshold global configuration command.
You can map each CoS value to a different queue and threshold combination, allowing the frame to follow different behavior.
Examples
This example shows how to map Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1 to queue-set 1. It maps CoS values 0 to 3 to egress queue 1 and to threshold ID 1. It configures the drop thresholds for queue 1 to 50 and 70 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory, and configures 200 percent as the maximum memory that this queue can have before packets are dropped.
Switch(config)# mls qos srr-queue output cos-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos queue-set output 1 threshold 1 50 70 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# queue-set 1
You can verify your settings by entering the show mls qos maps, the show mls qos interface [interface-id] buffers, or the show mls qos queue-set privileged EXEC command.
Related Commands
|
|
---|---|
Maps Differentiated Services Code Point (DSCP) values to an egress queue or maps DSCP values to a queue and to a threshold ID. |
|
Configures the WTD thresholds, guarantees the availability of buffers, and configures the maximum memory allocation to a queue-set. |
|
Maps a port to a queue-set. |
|
show mls qos interface buffers |
Displays QoS information. |
Displays QoS mapping information. |
|
Displays egress queue settings for the queue-set. |
mls qos srr-queue output dscp-map
Use the mls qos srr-queue output dscp-map global configuration command on the switch stack or on a standalone switch to map Differentiated Services Code Point (DSCP) values to an egress or to map DSCP values to a queue and to a threshold ID. Use the no form of this command to return to the default setting.
mls qos srr-queue output dscp-map queue queue-id {dscp1...dscp8 | threshold threshold-id dscp1...dscp8}
no mls qos srr-queue output dscp-map
Syntax Description
Defaults
Table 2-13 shows the default DSCP output queue threshold map:
DSCP Value |
0-15 |
16-31 |
32-39 |
40-47 |
48-63 |
Queue ID - Threshold ID |
2 - 1 |
3 - 1 |
4 - 1 |
1 - 1 |
4 - 1 |
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The drop-threshold percentage for threshold 3 is predefined. It is set to the queue-full state.
Note The egress queue default settings are suitable for most situations. You should change them only when you have a thorough understanding of the egress queues and if these settings do not meet your QoS solution.
You can assign two weighted tail-drop (WTD) threshold percentages to an egress queue by using the mls qos queue-set output qset-id threshold global configuration command.
You can map each DSCP value to a different queue and threshold combination, allowing the frame to follow different behavior.
You can map up to eight DSCP values per command.
Examples
This example shows how to map Fast Ethernet interface 0/1 on stack member 2Gigabit Ethernet interface 0/1 to queue-set 1. It maps DSCP values 0 to 3 to egress queue 1 and to threshold ID 1. It configures the drop thresholds for queue 1 to 50 and 70 percent of the allocated memory, guarantees (reserves) 100 percent of the allocated memory, and configures 200 percent as the maximum memory that this queue can have before packets are dropped.
Switch(config)# mls qos srr-queue output dscp-map queue 1 threshold 1 0 1 2 3
Switch(config)# mls qos queue-set output 1 threshold 1 50 70 100 200
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# queue-set 1
You can verify your settings by entering the show mls qos maps, the show mls qos interface [interface-id] buffers, or the show mls qos queue-set privileged EXEC command.
Related Commands
|
|
---|---|
Maps class of service (CoS) values to an egress queue or maps CoS values to a queue and to a threshold ID. |
|
Configures the WTD thresholds, guarantees the availability of buffers, and configures the maximum memory allocation to a queue-set. |
|
Maps a port to a queue-set. |
|
show mls qos interface buffers |
Displays quality of service (QoS) information. |
Displays QoS mapping information. |
|
Displays egress queue settings for the queue-set. |
mls qos trust
Use the mls qos trust interface configuration command on the switch stack or on a standalone switch to configure the port trust state. Ingress traffic can be trusted, and classification is performed by examining the packet Differentiated Services Code Point (DSCP), class of service (CoS), or IP-precedence field. Use the no form of this command to return a port to its untrusted state.
mls qos trust [cos | device cisco-phone | dscp | ip-precedence]
no mls qos trust [cos | device | dscp | ip-precedence]
Syntax Description
Defaults
The port is not trusted. If no keyword is specified when the command is entered, the default is dscp.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
The device cisco-phone keywords were added. |
Usage Guidelines
Packets entering a quality of service (QoS) domain are classified at the edge of the domain. When the packets are classified at the edge, the switch port within the QoS domain can be configured to one of the trusted states because there is no need to classify the packets at every switch within the domain. Use this command to specify whether the port is trusted and which fields of the packet to use to classify traffic.
When a port is configured with trust DSCP or trust IP precedence and the incoming packet is a non-IP packet, the CoS-to-DSCP map is used to derive the corresponding DSCP value from the CoS value. The CoS can be the packet CoS for trunk ports or the port default CoS for nontrunk ports.
If the DSCP is trusted, the DSCP field of the IP packet is not modified. However, it is still possible that the CoS value of the packet is modified (according to DSCP-to-CoS map).
If the CoS is trusted, the CoS field of the packet is not modified, but the DSCP can be modified (according to CoS-to-DSCP map) if the packet is an IP packet.
The trusted boundary feature prevents security problems if users disconnect their PCs from networked Cisco IP phones and connect them to the switch port to take advantage of trusted CoS settings. You must globally enable the Cisco Discovery Protocol (CDP) on the switch and on the interface connected to the IP phone. If the phone is not detected, trusted boundary disables the trusted setting on the switch port and prevents misuse of a high-priority queue. If you configure the trust setting for DSCP or IP precedence, the DSCP or IP precedence values in the incoming packets are trusted. If you configure the mls qos cos override interface configuration command on the switch port connected to the IP phone, the switch overrides the CoS of the incoming voice and data packets and assigns the default CoS value to them.
For an inter-QoS domain boundary, you can configure the port to the DSCP-trusted state and apply the DSCP-to-DSCP-mutation map if the DSCP values are different between the QoS domains.
Classification using a port trust state (for example, mls qos trust [cos | dscp | ip-precedence] and a policy map (for example, service-policy input policy-map-name) are mutually exclusive. The last one configured overwrites the previous configuration.
Examples
This example shows how to configure a port on stack member 2 to trust the IP precedence field in the incoming packet:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust ip-precedence
This example shows how to specify that the Cisco IP phone connected on a port on stack member 2 is a trusted device:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# mls qos trust device cisco-phone
You can verify your settings by entering the show mls qos interface privileged EXEC command.
Related Commands
monitor session
Use the monitor session global configuration command on the switch stack or on a standalone switch to start a new Switched Port Analyzer (SPAN) session or Remote SPAN (RSPAN) source or destination session, to enable ingress traffic on the destination port for a network security device (such as a Cisco IDS Sensor Appliance), to add or delete interfaces or VLANs to or from an existing SPAN or RSPAN session, and to limit (filter) SPAN source traffic to specific VLANs. Use the no form of this command to remove the SPAN or RSPAN session or to remove source or destination interfaces or filters from the SPAN or RSPAN session. For destination interfaces, the encapsulation replicate keywords are ignored with the no form of the command.
monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id}
monitor session session_number filter vlan vlan-id [, | -]
monitor session session_number source {interface interface-id [, | -] [both | rx | tx]} | {vlan vlan-id [, | -] [both | rx | tx]}| {remote vlan vlan-id}
no monitor session {session_number | all | local | remote}
no monitor session session_number destination {interface interface-id [, | -] [encapsulation replicate] [ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id}]} | {remote vlan vlan-id}
no monitor session session_number filter vlan vlan-id [, | -]
no monitor session session_number source {interface interface-id [, | -] [both | rx | tx]} | {vlan vlan-id [, | -] [both | rx | tx]} | {remote vlan vlan-id}
Syntax Description
Defaults
No monitor sessions are configured.
On a source interface, the default is to monitor both received and transmitted traffic.
On a trunk interface used as a source port, all VLANs are monitored.
If encapsulation replicate is not specified on a local SPAN destination port, packets are sent in native form with no encapsulation tag.
Ingress forwarding is disabled on destination ports.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
12.1(14)EA1 |
The ingress {dot1q vlan vlan-id | isl | untagged vlan vlan-id | vlan vlan-id} keywords were added. |
Usage Guidelines
Traffic that enters or leaves source ports or source VLANs can be monitored by using SPAN or RSPAN. Traffic routed to source ports or source VLANs cannot be monitored.
You can set a combined maximum of two local SPAN sessions and RSPAN source sessions. You can have a total of 66 SPAN and RSPAN sessions on a switch or switch stack.
You can have a maximum of 64 destination ports on a switch stack.
Each session can include multiple ingress or egress source ports or VLANs, but you cannot combine source ports and source VLANs in a single session. Each session can include multiple destination ports.
When you use VLAN-based SPAN (VSPAN) to analyze network traffic in a VLAN or set of VLANs, all active ports in the source VLANs become source ports for the SPAN or RSPAN session. Trunk ports are included as source ports for VSPAN, and only packets with the monitored VLAN ID are sent to the destination port.
You can monitor traffic on a single port or VLAN or on a series or range of ports or VLANs. You select a series or range of interfaces or VLANs by using the [, | -] options.
If you specify a series of VLANs or interfaces, you must enter a space before and after the comma. If you specify a range of VLANs or interfaces, you must enter a space before and after the hyphen (-).
EtherChannel ports cannot be configured as SPAN or RSPAN destination ports. A physical port that is a member of an EtherChannel group can be used as a destination port, but it cannot participate in the EtherChannel group while it is as a SPAN destination.
You can monitor individual ports while they participate in an EtherChannel, or you can monitor the entire EtherChannel bundle by specifying the port-channel number as the RSPAN source interface.
A port used as a destination port cannot be a SPAN or RSPAN source, nor can a port be a destination port for more than one session at a time.
You can enable 802.1X on a port that is a SPAN or RSPAN destination port; however, 802.1X is disabled until the port is removed as a SPAN destination. (If 802.1X is not available on the port, the switch returns an error message.) You can enable 802.1X on a SPAN or RSPAN source port.
VLAN filtering refers to analyzing network traffic on a selected set of VLANs on trunk source ports. By default, all VLANs are monitored on trunk source ports. You can use the monitor session session_number filter vlan vlan-id command to limit SPAN traffic on trunk source ports to only the specified VLANs.
VLAN monitoring and VLAN filtering are mutually exclusive. If a VLAN is a source, VLAN filtering cannot be enabled. If VLAN filtering is configured, a VLAN cannot become a source.
If ingress traffic forwarding is enabled for a network security device, the destination port forwards traffic at Layer 2.
Destination ports can be configured to act in these ways:
•When you enter monitor session session_number destination interface interface-id with no other keywords, egress encapsulation is untagged, and ingress forwarding is not enabled.
•When you enter monitor session session_number destination interface interface-id encapsulation replicate with no other keywords, egress encapsulation replicates the source interface encapsulation; ingress forwarding is not enabled. (This applies to local SPAN only; RSPAN does not support encapsulation replication.)
•When you enter monitor session session_number destination interface interface-id encapsulation replicate ingress, egress encapsulation replicates the source interface encapsulation; ingress encapsulation depends on the keywords that follow—dot1q, isl, or untagged. (This applies to local SPAN only; RSPAN does not support encapsulation replication.)
•When you enter monitor session session_number destination interface interface-id ingress, egress encapsulation is untagged; ingress encapsulation depends on the keywords that follow—dot1q, isl, or untagged.
Examples
This example shows how to create a local SPAN session 1 to monitor both sent and received traffic on source interface Gigabit Ethernet 1 on stack member 1 to destination interface Gigabit Ethernet 8 on stack member 2:
Switch(config)#
monitor session 1 source interface gigabitethernet1/0/1 both
Switch(config)# monitor session 1 destination interface gigabitethernet2/0/8
This example shows how to delete a destination port from an existing local SPAN session:
Switch(config)#
no monitor session 2 destination gigabitethernet1/0/4
This example shows how to limit SPAN traffic in an existing session only to specific VLANs:
Switch(config)#
monitor session 1 filter vlan 100 - 304
This example shows how to configure RSPAN source session 1 to monitor multiple source interfaces and to configure the destination RSPAN VLAN 900.
Switch(config)# monitor session 1 source interface gigabitethernet1/0/10 ,
gigabitethernet1/0/12
Switch(config)# monitor session 1 source interface gigabitethernet2/0/2 rx
Switch(config)# monitor session 1 source interface port-channel 2 tx
Switch(config)# monitor session 1 destination remote vlan 900
Switch(config)# end
This example shows how to configure an RSPAN destination session 10 in the switch receiving the monitored traffic.
Switch(config)# monitor session 10 source remote vlan 900
Switch(config)# monitor session 10 destination interface gigabitethernet1/0/10
This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a security device that supports 802.1Q encapsulation. Egress traffic replicates the source; ingress traffic uses 802.1Q encapsulation.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/5 encapsulation
replicate ingress dot1q vlan 5
This example shows how to configure the destination port for ingress traffic on VLAN 5 by using a security device that does not support encapsulation. Egress traffic replicates the source encapsulation; ingress traffic is untagged.
Switch(config)# monitor session 2 destination interface gigabitethernet1/0/5 encapsulation
replicate ingress untagged vlan 5
You can verify your settings by entering the show monitor privileged EXEC command. You can view SPAN and RSPAN configuration on the switch by entering the show running-config privileged EXEC command. SPAN information appears near the end of the output.
Related Commands
mvr (global configuration)
Use the mvr global configuration command without keywords on the switch stack or on a standalone switch to enable the multicast VLAN registration (MVR) feature on the switch. Use the command with keywords to set the MVR mode for a switch, configure the MVR IP multicast address, set the maximum time to wait for a query reply before removing a port from group membership, and to specify the MVR multicast VLAN. Use the no form of this command to return to the default settings.
mvr [group ip-address [count] | mode [compatible | dynamic] | querytime value | vlan vlan-id]
no mvr [group ip-address | mode [compatible | dynamic] | querytime value | vlan vlan-id]
Syntax Description
Defaults
MVR is disabled by default.
The default MVR mode is compatible mode.
No IP multicast addresses are configured on the switch by default.
The default group ip address count is 0.
The default query response time is 5 tenths of or one-half second.
The default multicast VLAN for MVR is VLAN 1.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
A maximum of 256 MVR multicast groups can be configured on a switch.
Use the mvr group command to statically set up all the IP multicast addresses that will take part in MVR. Any multicast data sent to a configured multicast address is sent to all the source ports on the switch and to all receiver ports that have registered to receive data on that IP multicast address.
MVR supports aliased IP multicast addresses on the switch. However, if the switch is interoperating with Catalyst 3550 or Catalyst 3500 XL switches, you should not configure IP addresses that alias between themselves or with the reserved IP multicast addresses (in the range 224.0.0.xxx).
The mvr querytime command applies only to receiver ports.
If the switch MVR is interoperating with Catalyst 2900 XL or Catalyst 3500 XL switches, set the multicast mode to compatible.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
MVR can coexist with IGMP snooping on a switch.
Multicast routing and MVR cannot coexist on a switch. If you enable multicast routing and a multicast routing protocol while MVR is enabled, MVR is disabled and a warning message is displayed. If you try to enable MVR while multicast routing and a multicast routing protocol are enabled, the operation to enable MVR is cancelled with an Error message.
Examples
This example shows how to enable MVR:
Switch(config)# mvr
This example shows how to disable MVR:
Switch(config)# no mvr
Use the show mvr privileged EXEC command to display the current setting for maximum multicast groups.
This example shows how to configure 228.1.23.4 as an IP multicast address:
Switch(config)# mvr group 228.1.23.4
This example shows how to configure ten contiguous IP multicast groups with multicast addresses from 228.1.23.1 to 228.1.23.10:
Switch(config)# mvr group 228.1.23.1 10
This example shows how to delete the previously configured ten IP multicast addresses:
Switch(config)# no mvr group 228.1.23.1 10
This example shows how to delete all previously configured IP multicast addresses:
Switch(config)# no mvr group
Use the show mvr members privileged EXEC command to display the IP multicast group addresses configured on the switch.
This example shows how to set the maximum query response time as one second (10 tenths):
Switch(config)# mvr querytime 10
This example shows how to return the maximum query response time to the default setting of one-half second:
Switch(config)# no mvr querytime
This example shows how to set VLAN 2 as the multicast VLAN:
Switch(config)# mvr vlan 2
You can verify your settings by entering the show mvr privileged EXEC command.
Related Commands
mvr (interface configuration)
Use the mvr interface configuration command on the switch stack or on a standalone switch to configure a Layer 2 port as a multicast VLAN registration (MVR) receiver or source port and set the immediate leave feature, and statically assign a port to an IP multicast VLAN and IP address. Use the no form of this command to return to the default settings.
mvr [immediate | type {receiver | source} | vlan vlan-id group [ip-address]]
no mvr [immediate | type {source | receiver}| vlan vlan-id group [ip-address]]
Syntax Description
Defaults
A port is configured as neither receiver nor source by default.
The Immediate Leave feature is disabled on all ports by default.
No receiver port is a member of any configured multicast group by default.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
Configure a port as a source port if that port should be able to both send and receive multicast data bound for the configured multicast groups. Multicast data is received on all ports configured as source ports.
Receiver ports cannot be trunk ports. Receiver ports on a switch can be in different VLANs, but should not belong to the multicast VLAN.
A port that is not taking part in MVR should not be configured as an MVR receiver port or source port. A non-MVR port is a normal switch port, able to send and receive multicast data with normal switch behavior.
When Immediate Leave is enabled, a receiver port leaves a multicast group more quickly. Without Immediate Leave, when the switch receives an IGMP leave message from a group on a receiver port, it sends out an IGMP MAC-based query on that port and waits for IGMP group membership reports. If no reports are received in a configured time period, the receiver port is removed from multicast group membership. With Immediate Leave, an IGMP MAC-based query is not sent from the receiver port on which the IGMP leave was received. As soon as the leave message is received, the receiver port is removed from multicast group membership, which speeds up leave latency.
The Immediate Leave feature should be enabled only on receiver ports to which a single receiver device is connected.
The mvr vlan group command statically configures ports to receive multicast traffic sent to the IP multicast address. A port statically configured as a member of group remains a member of the group until statically removed. In compatible mode, this command applies only to receiver ports; in dynamic mode, it can also apply to source ports. Receiver ports can also dynamically join multicast groups by using IGMP join messages.
When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.
Examples
This example shows how to configure Gigabit Ethernet port 0/1 on stack member 1 as an MVR receiver port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr type receiver
This example shows how to configure Gigabit Ethernet port 0/2 on stack member 1 as an MVR source port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr type source
This example shows how to remove port 0/1 on stack member 1 as an MVR port:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if))# no mvr
This example shows how to display configured receiver ports and source ports.
Switch# show mvr interface
Port Type Status Immediate Leave
---- ---- ------- ---------------
Gi1/0/1 SOURCE ACTIVE/UP DISABLED
Gi1/0/2 RECEIVER ACTIVE/DOWN DISABLED
Gi1/0/5 RECEIVER ACTIVE/UP ENABLED
This example shows how to enable Immediate Leave on Gigabit Ethernet port 1/0/1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr immediate
This example shows how to disable Immediate Leave on Gigabit Ethernet port 0/1on stack member 1:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr immediate
This example shows how to add Gigabit Ethernet port 1/0/2 on VLAN 1 as a static member of IP multicast group 228.1.23.4:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan1 group 230.1.23.4
This example shows how to remove this port from membership:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr vlan5 group 228.1.23.4
This example shows how to remove this port from all IP multicast groups:
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr vlan5 group
This example shows the result if Gigabit Ethernet port 0/2 on stack member 1 is not a receiver port:
Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan 1 group 230.1.23.4
Interface Gi
1/0/2 not configured as a receiver interface
You can verify your settings by entering the show mvr members privileged EXEC command.
Related Commands
pagp learn-method
Use the pagp learn-method interface configuration command on the switch stack or on a standalone switch to learn the source address of incoming packets received from an EtherChannel port. Use the no form of this command to return to the default setting.
pagp learn-method {aggregation-port | physical-port}
no pagp learn-method
Syntax Description
Defaults
The default is aggregation-port (logical port channel).
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The learn method must be configured the same at both ends of the link.
Note The Catalyst 3750Catalyst 2970 switch supports address learning only on aggregate ports even though the physical-port keyword is provided in the command-line interface (CLI). The pagp learn-method and the pagp port-priority interface configuration commands have no effect on the switch hardware, but they are required for PAgP interoperability with devices that only support address learning by physical ports, such as the Catalyst 1900 switch.
When the link partner to the Catalyst 3750Catalyst 2970 switch is a physical learner, we recommend that you configure the switch as a physical-port learner by using the pagp learn-method physical-port interface configuration command and to set the load-distribution method based on the source MAC address by using the port-channel load-balance src-mac global configuration command. Use the pagp learn-method interface configuration command only in this situation.
Examples
This example shows how to set the learning method to learn the address on the physical port within the EtherChannel:
Switch(config-if)#
pagp learn-method physical-port
This example shows how to set the learning method to learn the address on the port-channel within the EtherChannel:
Switch(config-if)#
pagp learn-method aggregation-port
You can verify your settings by entering the show running-config privileged EXEC command or the show pagp channel-group-number internal privileged EXEC command.
Related Commands
pagp port-priority
Use the pagp port-priority interface configuration command on the switch stack or on a standalone switch to select an interface over which all Port Aggregation Protocol (PAgP) traffic through the EtherChannel is sent. If all unused interfaces in the EtherChannel are in hot-standby mode, they can be placed into operation if the currently selected interface and link fails. Use the no form of this command to return to the default setting.
pagp port-priority priority
no pagp port-priority
Syntax Description
priority |
A priority number ranging from 0 to 255. |
Defaults
The default is 128.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The physical port with the highest priority that is operational and has membership in the same EtherChannel is the one selected for PAgP transmission.
Note The Catalyst 3750Catalyst 2970 switch supports address learning only on aggregate ports even though the physical-port keyword is provided in the command-line interface (CLI). The pagp learn-method and the pagp port-priority interface configuration commands have no effect on the switch hardware, but they are required for PAgP interoperability with devices that only support address learning by physical ports, such as the Catalyst 1900 switch.
When the link partner to the Catalyst 3750Catalyst 2970 switch is a physical learner, we recommend that you configure the switch as a physical-port learner by using the pagp learn-method physical-port interface configuration command and to set the load-distribution method based on the source MAC address by using the port-channel load-balance src-mac global configuration command. Use the pagp learn-method interface configuration command only in this situation.
Examples
This example shows how to set the port priority to 200:
Switch(config-if)#
pagp port-priority 200
You can verify your setting by entering the show running-config privileged EXEC command or the show pagp channel-group-number internal privileged EXEC command.
Related Commands
permit
Use the permit MAC-access list configuration command on the switch stack or on a standalone switch to allow non-IP traffic to be forwarded if the conditions are matched. Use the no form of this command to remove a permit condition from the extended MAC access list.
{permit | deny} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | cos cos | aarp | amber | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo | vines-ip | xns-idp]
no {permit | deny} {any | host src-MAC-addr | src-MAC-addr mask} {any | host dst-MAC-addr | dst-MAC-addr mask} [type mask | cos cos | aarp | amber | dec-spanning | decnet-iv | diagnostic | dsm | etype-6000 | etype-8042 | lat | lavc-sca | lsap lsap mask | mop-console | mop-dump | msdos | mumps | netbios | vines-echo |vines-ip | xns-idp]
Note Though visible in the command-line help strings, appletalk is not supported as a matching condition.
Syntax Description
To filter IPX traffic, you use the type mask or lsap lsap mask keywords, depending on the type of IPX encapsulation being used. Filter criteria for IPX encapsulation types as specified in Novell terminology and Cisco IOS terminology are listed in Table 2-14.
Defaults
This command has no defaults. However; the default action for a MAC-named ACL is to deny.
Command Modes
MAC-access list configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You enter MAC-access list configuration mode by using the mac access-list extended global configuration command.
If you use the host keyword, you cannot enter an address mask; if you do not use the any or host keywords, you must enter an address mask.
After an access control entry (ACE) is added to an access control list, an implied deny-any-any condition exists at the end of the list. That is, if there are no matches, the packets are denied. However, before the first ACE is added, the list permits all packets.
Note For more information about MAC named extended access lists, refer to the software configuration guide for this release.
Examples
This example shows how to define the MAC name extended access list to allow NETBIOS traffic from any source to MAC address 00c0.00a0.03fa. Traffic matching this list is allowed.
Switch(config-ext-macl)# permit any host 00c0.00a0.03fa netbios
This example shows how to remove the permit condition from the MAC name extended access list:
Switch(config-ext-macl)# no permit any 00c0.00a0.03fa 0000.0000.0000 netbios
This example permits all packets with Ethertype 0x4321:
Switch(config-ext-macl)# permit any any 0x4321 0
You can verify your settings by entering the show access-lists privileged EXEC command.
Related Commands
police
Use the police policy-map class configuration command on the switch stack or on a standalone switch to define a policer for classified traffic. A policer defines a maximum permissible rate of transmission, a maximum burst size for transmissions, and an action to take if either maximum is exceeded. Use the no form of this command to remove an existing policer.
police rate-bps burst-byte [exceed-action {drop | policed-dscp-transmit}]
no police rate-bps burst-byte [exceed-action {drop | policed-dscp-transmit}]
Syntax Description
Defaults
No policers are defined.
Command Modes
Policy-map class configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The port ASIC device, which controls more than one physical port, supports 256 policers (255 policers plus 1 no policer). The maximum number of policers supported per port is 64. Policers are allocated on demand by the software and are constrained by the hardware and ASIC boundaries. You cannot reserve policers per port. There is no guarantee that a port will be assigned to any policer.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Policing uses a token-bucket algorithm. You configure the bucket depth (the maximum burst that is tolerated before the bucket overflows) by using the burst-byte option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. You configure how quickly (the average rate) the tokens are removed from the bucket by using the rate-bps option of the police policy-map class configuration command or the mls qos aggregate-policer global configuration command. For more information, refer to the software configuration guide for this release.
Examples
This example shows how to configure a policer that drops packets if traffic exceeds 1 Mbps average rate with a burst size of 20 KB. The DSCPs of incoming packets are trusted, and there is no packet modification.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 45
Switch(config-pmap-c)# police 1000000 20000 exceed-action drop
Switch(config-pmap-c)# exit
This example shows how to configure a policer, which marks down the DSCPs with the values defined in policed-DSCP map and sends the packet:
Switch(config)# policy-map policy2
Switch(config-pmap)# class class2
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
|
|
---|---|
Defines a traffic classification match criteria (through the police, set, and trust policy-map class configuration commands) for the specified class-map name. |
|
mls qos map policed-dscp |
Applies a policed-DSCP map to a DSCP-trusted port. |
Creates or modifies a policy map that can be attached to multiple interfaces to specify a service policy. |
|
Classifies IP traffic by setting a DSCP or IP-precedence value in the packet. |
|
Displays quality of service (QoS) policy maps. |
|
Defines a trust state for traffic classified through the class policy-map configuration or the class-map global configuration command. |
police aggregate
Use the police aggregate policy-map class configuration command on the switch stack or on a standalone switch to apply an aggregate policer to multiple classes in the same policy map. A policer defines a maximum permissible rate of transmission, a maximum burst size for transmissions, and an action to take if either maximum is exceeded. Use the no form of this command to remove the specified policer.
police aggregate aggregate-policer-name
no police aggregate aggregate-policer-name
Syntax Description
aggregate-policer-name |
Name of the aggregate policer. |
Defaults
No aggregate policers are defined.
Command Modes
Policy-map class configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The port ASIC device, which controls more than one physical port, supports 256 policers (255 policers plus 1 no policer). The maximum number of policers supported per port is 64. Policers are allocated on demand by the software and are constrained by the hardware and ASIC boundaries. You cannot reserve policers per port. There is no guarantee that a port will be assigned to any policer.
You set aggregate policer parameters by using the mls qos aggregate-policer global configuration command. You apply an aggregate policer to multiple classes in the same policy map; you cannot use an aggregate policer across different policy maps.
To return to policy-map configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Examples
This example shows how to define the aggregate policer parameters and to apply the policer to multiple classes in a policy map:
Switch(config)# mls qos aggregate-policer agg_policer1 10000 1000000 exceed-action drop
Switch(config)# policy-map policy2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police aggregate agg_policer1
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police aggregate agg_policer2
Switch(config-pmap-c)# exit
You can verify your settings by entering the show mls qos aggregate-policer privileged EXEC command.
Related Commands
|
|
---|---|
Defines policer parameters, which can be shared by multiple classes within a policy map. |
|
Displays the quality of service (QoS) aggregate policer configuration. |
policy-map
Use the policy-map global configuration command on the switch stack or on a standalone switch to create or modify a policy map that can be attached to multiple interfaces and to enter policy-map configuration mode. Use the no form of this command to delete an existing policy map and to return to global configuration mode.
policy-map policy-map-name
no policy-map policy-map-name
Syntax Description
policy-map-name |
Name of the policy map. |
Defaults
No policy maps are defined.
The default behavior is to set the Differentiated Services Code Point (DSCP) to 0 if the packet is an IP packet and to set the class of service (CoS) to 0 if the packet is tagged. No policing is performed.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
After entering the policy-map command, you enter policy-map configuration mode, and these configuration commands are available:
•class: defines the classification match criteria for the specified class map. For more information, see the "class" section.
•description: describes the policy map (up to 200 characters).
•exit: exits policy-map configuration mode and returns you to global configuration mode.
•no: removes a previously defined policy map.
•rename: renames the current policy map.
To return to global configuration mode, use the exit command. To return to privileged EXEC mode, use the end command.
Before configuring policies for classes whose match criteria are defined in a class map, use the policy-map command to specify the name of the policy map to be created, added to, or modified. Entering the policy-map command also enables the policy-map configuration mode in which you can configure or modify the class policies for that policy map.
You can configure class policies in a policy map only if the classes have match criteria defined for them. To configure the match criteria for a class, use the class-map global configuration and match class-map configuration commands. You define packet classification on a physical-port basis.
Only one policy map per ingress interface is supported. You can apply the same policy map to multiple interfaces.
Examples
This example shows how to create a policy map called policy1. When attached to the ingress direction, it matches all the incoming traffic defined in class1, sets the IP DSCP to 10, and polices the traffic at an average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP value obtained from the policed-DSCP map and then sent.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
This example shows how to configure multiple classes in a policy map called policymap2:
Switch(config)# policy-map policymap2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set ip dscp 10
Switch(config-pmap-c)# police 100000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 100000 20000 exceed-action drop
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# set ip dscp 0 (no policer)
Switch(config-pmap-c)# exit
This example shows how to delete policymap2:
Switch(config)# no policy-map policymap2
You can verify your settings by entering the show policy-map privileged EXEC command.
Related Commands
port-channel load-balance
Use the port-channel load-balance global configuration command on the switch stack or on a standalone switch to set the load-distribution method among the ports in the EtherChannel. Use the no form of this command to return to the default setting.
port-channel load-balance {dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac}
no port-channel load-balance
Syntax Description
Defaults
The default is src-mac.
Command Modes
Global configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
For information about when to use these forwarding methods, refer to the "Configuring EtherChannels" chapter in the software guide for this release.
Examples
This example shows how to set the load-distribution method to dst-mac:
Switch(config)#
port-channel load-balance dst-mac
You can verify your setting by entering the show running-config privileged EXEC command or the show etherchannel load-balance privileged EXEC command.
Related Commands
priority-queue
Use the priority-queue interface configuration command to enable the egress expedite queue on an interface. Use the no form of this command to return to the default setting.
priority-queue out
no priority-queue out
Syntax Description
out |
Enable the egress expedite queue. |
Defaults
The egress expedite queue is disabled.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(19)EA1 |
This command was first introduced. |
Usage Guidelines
When you configure the priority-queue out command, the shaped round robin (SRR) weight ratios are affected because there is one fewer queue participating in SRR. This means that weight1 in the srr-queue bandwidth shape or the srr-queue bandwidth shape interface configuration command is ignored (not used in the ratio calculation). The expedite queue is a priority queue, and it is serviced until empty before the other queues are serviced.
Follow these guidelines when the expedite queue is enabled or the egress queues are serviced based on their SRR weights:
•If the egress expedite queue is enabled, it overrides the SRR shaped and shared weights for queue 1.
•If the egress expedite queue is disabled and the SRR shaped and shared weights are configured, the shaped mode overrides the shared mode for queue 1, and SRR services this queue in shaped mode.
•If the egress expedite queue is disabled and the SRR shaped weights are not configured, SRR services the queue in shared mode.
Examples
This example shows how to enable the egress expedite queue when the SRR weights are configured. The egress expedite queue overrides the configured SRR weights.
Switch(config)# interface fastethernet1/0/7
Switch(config-if)# srr-queue bandwidth shape 25 0 0 0
Switch(config-if)# srr-queue bandwidth share 30 20 25 25
Switch(config-if)# priority-queue out
Switch(config-if)# end
Switch> show mls qos interface fastethernet1/0/7 queueing
FastEthernet1/0/7
Egress Priority Queue :enabled
Shaped queue weights (absolute) : 25 0 0 0
Shared queue weights : 25 25 25 25
The port bandwidth is limited to: 100%
The port is mapped to qset : 1
This example shows how to disable the egress expedite queue after the SRR shaped and shared weights are configured. The shaped mode overrides the shared mode.
Switch(config)# interface fastethernet1/0/8
Switch(config-if)# srr-queue bandwidth shape 25 0 0 0
Switch(config-if)# srr-queue bandwidth share 30 20 25 25
Switch(config-if)# no priority-queue out
Switch(config-if)# end
Switch> show mls qos interface fastethernet1/0/8 queueing
FastEthernet1/0/8
Egress Priority Queue :disabled
Shaped queue weights (absolute) : 25 0 0 0
Shared queue weights : 25 25 25 25
The port bandwidth is limited to: 100%
The port is mapped to qset : 1
You can verify your settings by entering the show mls qos interface interface-id queueing or the show running-config privileged EXEC command.
Related Commands
|
|
---|---|
show mls qos interface queueing |
Displays the queueing strategy (SRR, priority queueing), the weights corresponding to the queues, and the CoS-to-egress-queue map. |
Assigns the shaped weights and enables bandwidth shaping on the four egress queues mapped to a port. |
|
Assigns the shared weights and enables bandwidth sharing on the four egress queues mapped to a port. |
queue-set
Use the queue-set interface configuration command on the switch stack or on a standalone switch to map a port to a queue-set. Use the no form of this command to return to the default setting.
queue-set qset-id
no queue-set qset-id
Syntax Description
qset-id |
ID of the queue-set. Each port belongs to a queue-set, which defines all the characteristics of the four egress queues per port. The range is 1 to 2. |
Defaults
The queue-set ID is 1.
Command Modes
Interface configuration
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to map Fast Ethernet port 0/1 on stack member 2Gigabit Ethernet port 0/1 to queue-set 2:
Switch(config)# interface fastethernet2/0/1
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# queue-set 2
You can verify your settings by entering the show mls qos interface [interface-id] buffers privileged EXEC command.
Related Commands
|
|
---|---|
Allocates buffers to a queue-set. |
|
Configures the weighted tail-drop (WTD) thresholds, guarantees the availability of buffers, and configures the maximum memory allocation to a queue-set. |
|
show mls qos interface buffers |
Displays quality of service (QoS) information. |
rcommand
Use the rcommand user EXEC command on the switch stack or on the cluster command switch to start a Telnet session and to execute commands on a cluster member switch from the cluster command switch or the switch stack. To end the session, enter the exit command.
rcommand {n | commander | mac-address hw-addr}
Syntax Description
Command Modes
User EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
This command is available only on the cluster command switch stack or cluster command switch.
If the switch is the cluster command switch but the cluster member switch n does not exist, an error message appears. To obtain the switch number, enter the show cluster members privileged EXEC command on the cluster command switch.
You can use this command to access a cluster member switch from the cluster command-switch prompt or to access a cluster command switch from the member-switch prompt.
For Catalyst 2900 XL, 3500 XL, 2950, 2970, 3550, and 3750 switches, the Telnet session accesses the member-switch command-line interface (CLI) at the same privilege level as on the cluster command switch. For example, if you execute this command at user level on the cluster command switch, the cluster member switch is accessed at user level. If you use this command on the cluster command switch at privileged level, the command accesses the remote device at privileged level. If you use an intermediate enable-level lower than privileged, access to the cluster member switch is at user level.
For Catalyst 1900 and 2820 switches running standard edition software, the Telnet session accesses the menu console (the menu-driven interface) if the cluster command switch is at privilege level 15. If the cluster command switch is at privilege level 1, you are prompted for the password before being able to access the menu console. Cluster command switch privilege levels map to the cluster member switches running standard edition software as follows:
•If the cluster command switch privilege level is from 1 to 14, the cluster member switch is accessed at privilege level 1.
•If the cluster command switch privilege level is 15, the cluster member switch is accessed at privilege level 15.
The Catalyst 1900 and 2820 CLI is available only on switches running Enterprise Edition Software.
This command will not work if the vty lines of the cluster command switch have access-class configurations.
You are not prompted for a password because the cluster member switches inherited the password of the cluster command switch when they joined the cluster.
Examples
This example shows how to start a session with member 3. All subsequent commands are directed to member 3 until you enter the exit command or close the session.
Switch# rcommand 3
Switch-3# show version
Cisco Internet Operating System Software ...
...
Switch-3# exit
Switch#
Related Commands
|
|
---|---|
Displays information about the cluster members. |
reload
Use the reload privileged EXEC command to reset the stack member and applies a configuration change into effect.
reload [LINE | at | cancel | in | slot stack-member-number | standby-cpu]
Syntax Description
Defaults
Immediately resets the stack member and puts a configuration change into effect.
Command Modes
Privilege EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Examples
This example shows how to reload the switch stack:
Switch(config)# reload
System configuration has been modified. Save? [yes/no]: y
Proceed to reload the whole Stack? [confirm] y
This example shows how to reload a specific stack member:
Switch(config)# reload slot 6
Proceed with reload? [confirm]y
Related Commands
|
|
---|---|
Accesses a specific stack member. |
|
Changes the stack member priority value. |
|
Changes the stack member number. |
|
Displays information about the switch stack and its stack members. |
remote command
Use the remote command privileged EXEC command to monitor all or specified stack members.
remote command [all | stack-member-number] LINE
Syntax Description
stack-member-number |
Specify the stack member. The range is 1 to 9. |
all |
Apply to all stack members. |
LINE |
Specify the command to execute. |
Command Modes
Privileged EXEC
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
The commands (such as debug, show, or clear) you use in the LINE command-to-execute string apply to a specific stack member or to the switch stack.
Examples
This example shows how to execute the undebug command on the switch stack:
Switch(config)# remote command all undebug all
Switch :1 :
------------
All possible debugging has been turned off
Switch :5 :
------------
All possible debugging has been turned off
Switch :9 :
------------
All possible debugging has been turned off
This example shows how to execute the debug udld event command on stack member 5:
Switch(config)# remote command 5 undebug all
Switch :5 :
------------
UDLD events debugging is on
Related Commands
|
|
---|---|
Accesses a specific stack member. |
|
Changes the stack member priority value. |
|
Changes the stack member number. |
|
Displays information about the switch stack and its stack members. |
remote-span
Use the remote-span VLAN configuration command on the switch stack or on a standalone switch to configure a VLAN as a Remote Switched Port Analyzer (RSPAN) VLAN. Use the no form of this command to remove the RSPAN designation from the VLAN.
remote-span
no remote-span
Syntax Description
This command has no arguments or keywords.
Defaults
No RSPAN VLANs are defined.
Command Modes
VLAN configuration (config-VLAN)
Command History
|
|
---|---|
12.1(11)AX |
This command was first introduced. |
Usage Guidelines
You can configure RSPAN VLANs only in config-VLAN mode (entered by using the vlan global configuration command), not the VLAN configuration mode entered by using the vlan database privileged EXEC command.
If VTP is enabled, the RSPAN feature is propagated by VLAN Trunking Protocol (VTP) for VLAN-IDs that are lower than 1005. If the RSPAN VLAN ID is in the extended range, you must manually configure intermediate switches (those in the RSPAN VLAN between the source switch and the destination switch).
Before you configure the RSPAN remote-span command, use the vlan (global configuration) command to create the VLAN.
The RSPAN VLAN has these characteristics:
•No MAC address learning occurs on it.
•RSPAN VLAN traffic flows only on trunk ports.
•Spanning Tree Protocol (STP) can run in the RSPAN VLAN, but it does not run on RSPAN destination ports.
When an existing VLAN is configured as an RSPAN VLAN, the VLAN is first deleted and then recreated as an RSPAN VLAN. Any access ports are made inactive until the RSPAN feature is disabled.
Examples
This example shows how to configure a VLAN as an RSPAN VLAN.
Switch(config)# vlan 901
Switch(config-vlan)# remote-span
This example shows how to remove the RSPAN feature from a VLAN.
Switch(config)# vlan 901
Switch(config-vlan)# no remote-span
You can verify your settings by entering the show vlan remote-span user EXEC command.