Table Of Contents
clear controllers ethernet-controller
clear mac-address-table notification
hw-module slot module-slot # upgrade lre
lre upgrade default family device-family binary
mac-address-table notification
show controllers ethernet-controller
show controllers lre cpe protected
show controllers lre interface-id actual
show controllers lre interface-id admin
show controllers lre log level
show controllers lre version mfg
show local ethernet-statistics
show mac-address-table notification
show remote ethernet-statistics
snmp-server enable traps mac-notification
snmp-server enable traps vlan-membership
spanning-tree portfast bpduguard
switchport trunk encapsulation
tacacs-server dns-alias-lookup
Cisco IOS Commands
abort
Use the abort VLAN database command to abandon the proposed VLAN database, exit VLAN database mode, and return to privileged EXEC mode.
abort
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
VLAN database
Command History
Usage Guidelines
If you have added, deleted, or modified VLAN parameters in VLAN database mode but you do not want to keep the changes, the abort command causes all the changes to be abandoned. The VLAN configuration that was running before you entered VLAN database mode continues to be used.
Examples
This example shows how to abandon the proposed VLAN database and to exit to the privileged EXEC mode:
Switch(vlan)# abortSwitch#You can verify that no VLAN database changes occurred by entering the show vlan brief user EXEC command.
Related Commands
apply
Use the apply VLAN database command to implement the proposed VLAN database to increment the database configuration revision number, to propagate it throughout the administrative domain, and to remain in VLAN database mode.
apply
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
VLAN database
Command History
Usage Guidelines
The apply command implements the configuration changes that you made after you entered VLAN database mode and uses them for the running configuration. This command keeps you in VLAN database mode.
You cannot use this command when the switch is in the VLAN Trunking Protocol (VTP) client mode.
Examples
This example shows how to implement the proposed VLAN database as the running database:
Switch(vlan)# applyYou can verify that VLAN database changes occurred by entering the show vlan user EXEC command.
Related Commands
cgmp
Use the cgmp global configuration command to enable Cisco Group Management Protocol (CGMP) and other CGMP options. Use the no form of this command to disable CGMP and its options.
cgmp {leave-processing | holdtime time | reserved}
no cgmp {leave-processing | holdtime | reserved}
Syntax Description
Defaults
CGMP is enabled.
Fast Leave is disabled.
The hold time is 300 seconds.
Reserved addresses are allowed as group destination addresses.
Command Modes
Global configuration
Command History
11.2(8)SA3
This command was first introduced.
12.0(5)XP
The reserved keyword was added.
Usage Guidelines
CGMP must be enabled before the Fast Leave option can be enabled.
Examples
This example shows how to disable CGMP:
Switch(config)# no cgmpThis example shows how to disable the Fast Leave option:
Switch(config)# no cgmp leave-processingThis example shows how to set 400 seconds as the length of time the switch waits before ceasing to exchange messages with a router:
Switch(config)# cgmp holdtime 400This example shows how to remove the amount of time the switch waits before ceasing to exchange messages with a router:
Switch(config)# no cgmp holdtimeThis example shows how to exclude reserved addresses from the group destination address for compatibility with Catalyst 5000 series switches.
Switch(config)# no cgmp reservedYou can verify the previous commands by entering the show cgmp user EXEC command.
Related Commands
Deletes information that the switch learned by using CGMP.
Displays the state of the CGMP-learned multicast groups and routers.
clear cgmp
Use the clear cgmp privileged EXEC command to delete information that was learned by the switch by using the Cisco Group Management Protocol (CGMP).
clear cgmp [vlan vlan-id] | [group [address] | router [address]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using clear cgmp with no arguments deletes all groups and routers in all VLANs.
Examples
This example shows how to delete all groups and routers on VLAN 2:
Switch# clear cgmp vlan 2This example shows how to delete all groups on all VLANs:
Switch# clear cgmp groupThis example shows how to delete a router address on VLAN 2:
Switch# clear cgmp vlan 2 router 0012.1234.1234You can verify the previous commands by entering the show cgmp user EXEC command.
Related Commands
Enables CGMP and the Fast Leave option and sets the router port aging time.
Displays the state of the CGMP-learned multicast groups and routers.
clear controllers ethernet-controller
Use the clear controllers ethernet-controller privileged EXEC command to delete the Ethernet link transmit and receive statistics on a switch port and on a Long-Reach Ethernet (LRE) customer premises equipment (CPE) device.
clear controllers ethernet-controller [interface-id]
Syntax Description
Defaults
There is no default.
Command Modes
Privileged EXEC
Command History
12.0(5)WC1
This command was first introduced.
12.0(5)WC4
This command was extended to support the Cisco 585 LRE CPE device.
Usage Guidelines
Using the clear controllers ethernet-controller command without specifying a switch port clears the Ethernet link statistics for all ports on the switch. If you use this command on a switch LRE port, it clears the statistics on the Ethernet port on the Cisco 575 LRE CPE device or on all four Ethernet ports on the Cisco 585 LRE CPE device. The Cisco 585 LRE CPE Ethernet ports cannot be cleared on a per-port basis.
The CPE Ethernet link is the connection between the CPE Ethernet port and the remote Ethernet device (such as a PC) connected to it. It is not the link between the switch LRE port and the LRE CPE device.
It takes the switch several seconds to clear all of the ports. The switch LRE ports take longer to clear than all the other port types.
Examples
This example shows how to use the clear controllers ethernet-controller command to delete the Ethernet link statistics on Fast Ethernet port 0/1:
Switch# clear controllers ethernet-controller FastEthernet 0/1Switch#This example shows how to use the clear controllers ethernet-controller command to delete the Ethernet link statistics between the LRE CPE device and the remote Ethernet device. The LRE CPE device is connected to switch LRE port 1:
Switch# clear controllers ethernet-controller lo0/1Switch#You can verify that information was deleted by entering the show controllers ethernet-controller user EXEC command.
Related Commands
Displays the Ethernet link transmit and receive statistics on a Fast Ethernet or switch LRE port.
clear controllers lre log
Use the clear controllers lre log privileged EXEC command to delete the history of link, configuration, and timer events for a specific Long-Reach Ethernet (LRE) port or for all switch LRE ports.
clear controllers lre log [interface-id]
Syntax Description
Defaults
There is no default.
Command Modes
Privileged EXEC
Command History
12.0(5)WC1
This command was first introduced.
12.0(5)WC4
This command was extended to support the Cisco 585 LRE customer premises equipment (CPE) device.
Usage Guidelines
Using the clear controllers lre log command but without specifying a switch LRE port deletes the history of events on all switch LRE ports.
Examples
This example shows how to use the clear controllers lre log command to delete the history of events on switch LRE port 3:
Switch# clear controllers lre log longReachEthernet 0/3Switch#You can verify that information was deleted by entering the show controllers lre log privileged EXEC command.
Related Commands
Displays the history of link, configuration, and timer events for a specific switch LRE port or for all LRE ports on the switch.
clear ip address
Use the clear ip address privileged EXEC command to delete an IP address for a switch without disabling the IP processing.
clear ip address [vlan vlan-id]
Syntax Description
vlan vlan-id
(Optional) Delete an IP address only within the specified VLAN.
Valid IDs are from 1 to 1000; do not enter leading zeros.
Command Modes
Privileged EXEC
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
Usage Guidelines
A switch can have one IP address.
The IP address of the switch can be accessed only by nodes connected to ports that belong to the management VLAN. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
If your switch receives its IP address from a Bootstrap Protocol (BOOTP) or Dynamic Host Configuration Protocol (DHCP) server and you delete the switch IP address by using the clear ip address command, the BOOTP or DHCP server reassigns the address.
Examples
This example shows how to clear the IP address for the switch on VLAN 1:
Switch# clear ip address vlan 1You can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
clear lre rate selection
Use the clear lre rate selection privileged EXEC command to reset the rate selection setting and to restart rate selection for a specific Long-Reach Ethernet (LRE) port or for all switch LRE ports.
clear lre rate selection [lock] [interface-id]
Syntax Description
lock
(Optional) Rate selection runs on all ports that have rate selection enabled, including ports that are locked.
interface-id
(Optional) ID of the switch LRE port.
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Using the clear lre rate selection command without specifying a switch LRE port runs rate selection on all switch LRE ports that have rate selection enabled except those ports with locked profiles. Specifying the lock keyword runs rate selection on all profiles, including those that are locked.
Examples
This example shows how to use the clear lre rate selection command to reset the rate selection setting and to restart rate selection on port 1.
Switch# clear lre rate selection lo0/1Switch#This example shows how to reset and to restart rate selection on all ports, including any locked ports.
Switch# clear lre rate selection lockSwitch#This example shows how to reset and to restart rate selection on port 1, overriding the locked status.
Switch# clear lre rate selection lock lo0/1Switch#Related Commands
Enables rate selection on a specific port.
Assigns a rate selection sequence for a specific port.
Assigns a rate selection sequence for the entire switch.
clear mac-address-table
Use the clear mac-address-table privileged EXEC command to delete entries from the MAC address table.
clear mac-address-table [static | dynamic | secure] [address hw-addr] [interface interface]
[atm slot/port] [vlan vlan-id]Syntax Description
Command Modes
Privileged EXEC
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
11.2(8)SA5
The atm keyword was added.
Usage Guidelines
This command deletes entries from the global MAC address table. Specific subsets can be deleted by using the optional keywords and values. If more than one optional keyword is used, all of the conditions in the argument must be true for that entry to be deleted.
Examples
This example shows how to delete static addresses on port fa0/7:
Switch# clear mac-address-table static interface fa0/7This example shows how to delete all secure addresses in VLAN 3:
Switch# clear mac-address-table secure vlan 3This example shows how to delete address 0099.7766.5544 from all ports in all VLANs. If the address exists in multiple VLANs or multiple ports, all the instances are deleted.
Switch# clear mac-address-table address 0099.7766.5544This example shows how to delete address 0099.7766.5544 only in VLAN 2:
Switch# clear mac-address-table address 0099.7766.5544 vlan 2This example shows how to delete the secure MAC address 00c0.00a0.03fa associated with the ATM port in expansion slot 2:
Switch(config)# clear mac-address-table secure 00c0.00a0.03fa atm 2/1This example shows how to delete the static address 00c0.00a0.03fa associated with the ATM port in expansion slot 2:
Switch(config)# clear mac-address-table static 00c0.00a0.03fa atm 2/1You can verify the previous commands by entering the show mac-address-table user EXEC command.
Related Commands
clear mac-address-table notification
Use the clear mac-address-table notification privileged EXEC command to clear the addresses maintained by the MAC address notification feature.
clear mac-address-table notification
Syntax Description
This command has no keywords or options.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears the counters for the MAC addresses added, the MAC addresses removed, and the number of traps sent to the NMS counters on the switch. This command does not clear the history table on the switch.
Related Commands
clear vmps statistics
Use the clear vmps statistics privileged EXEC command to clear the statistics maintained by the VLAN Query Protocol (VQP) client.
clear vmps statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear VLAN Membership Policy Server (VMPS) statistics:
Switch# clear vmps statisticsYou can verify the previous command by entering the show vmps statistics privileged EXEC command.
Related Commands
Displays the VLAN Query Protocol (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 to clear the VLAN Trunking Protocol (VTP) and pruning counters.
clear vtp counters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the VTP counters:
Switch# clear vtp countersYou can verify the previous command by entering the show vtp counters user EXEC command.
Related Commands
show vtp counters
Display general information about the VTP management domain, status, and counters.
cluster commander-address
You do not need to enter this command. The command switch automatically provides its MAC address to member switches when these switches join the cluster. The member switch adds this information and other cluster information to its running configuration file. Enter the no form of this global configuration command from the member switch console port to remove it 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
11.2(8)SA6
This command was first introduced.
12.0(5)XU
The member and name keywords were added.
Usage Guidelines
A cluster member can belong to only one command switch.
The member switch retains the identity of the command switch during a system reload by using the mac-address parameter.
You can enter the no form on a member switch to remove it from the cluster during debugging or recovery procedures. You would normally use this command from the member switch console port only when the member has lost communication with the command switch. With normal switch configuration, we recommend that you remove member switches only by entering the no cluster member n global configuration command on the command switch.
When a standby command-switch becomes active (becomes the 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-es3# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch-es3(config)# no cluster commander-addressYou can verify the previous command by entering the show cluster command in user EXEC mode.
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 command switch to set the hop-count limit for extended discovery of candidate switches. Use the no form of this command to set the hop count to the default value.
cluster discovery hop-count number
no cluster discovery hop-count
default cluster discovery hop-count
Syntax Description
Defaults
The hop count is set to 3.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch. This command does not operate on member switches.
If the hop count is set to 1, it disables extended discovery. The 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 member switch and the first discovered candidate switch.
Examples
This example shows how to set the hop count limit to 4. This command is entered on the command switch.
Switch(config)# cluster discovery hop-count 4You can verify the previous command by entering the show cluster command in user EXEC mode.
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 to enable it as the cluster command switch, assign a cluster name, and optionally assign a member number to it. Use the no form of the command to remove all members and to make the command switch a candidate switch.
cluster enable name [command-switch-member-number]
no cluster enable
default cluster enable
Syntax Description
Defaults
The switch is not a command switch.
No cluster name is defined.
The member number is 0 when this is the command switch.
Command Modes
Global configuration
Command History
11.2(8)SA6
This command was first introduced.
12.0(5)XU
The command-switch-member-number variable was added.
Usage Guidelines
This command runs 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 command switch. If the switch is already configured as the command switch, this command changes the cluster name if it is different from the previous name.
Examples
This example shows how to enable the command switch, to name the cluster, and to set the command switch member number to 4.
Switch(config)# cluster enable Engineering-IDF4 4You can verify the previous command by entering the show cluster command in user EXEC mode on the 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 command switch to set the duration in seconds before a switch (either the command or 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
default cluster holdtime
Syntax Description
Defaults
The holdtime is 80 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command with the cluster timer global configuration command only on the command switch. The 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 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 command switch.
Switch(config)# cluster timer 3Switch(config)# cluster holdtime 30You can verify the previous commands by entering the show cluster command in user EXEC mode.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
cluster management-vlan
Use the cluster management-vlan global configuration command on the command switch to change the management VLAN for the entire cluster. Use the no form of this command to change the management VLAN to VLAN 1.
cluster management-vlan n
no cluster management-vlan
default cluster management-vlan
Syntax Description
n
VLAN ID of the new management VLAN. Valid VLAN IDs are from 1 to 1001.
no
Set the management VLAN to VLAN 1.
default
Set the management VLAN to VLAN 1.
Defaults
The default management VLAN is VLAN 1.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch. This command changes the management VLAN of the command switch and member switches. Member switches must have either a trunk connection or connection to the new command-switch management VLAN to maintain communication with the command switch.
This command is not written to the configuration file.
Examples
This example shows how to change the management VLAN to VLAN 5 on the entire cluster.
Switch(config)# cluster management-vlan 5You can verify the previous command by entering the show interface vlan number user EXEC command.
Related Commands
Shuts down the management VLAN interface and enables the new management VLAN interface on an individual switch.
cluster member
Use the cluster member global configuration command on the command switch to add members 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]
no cluster member n
default cluster member n
Syntax Description
Defaults
A newly enabled command switch has no associated cluster members.
Command Modes
Global configuration
Command History
Usage Guidelines
Enter this command only on the command switch to add a member to or remove a member from the cluster. If you enter this command on a switch other than the 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 command switch selects the next available member number and assigns it to the switch 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 command-switch password.
If a switch does not have a configured host name, the command switch appends a member number to the command-switch host name and assigns it to the member switch.
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.
Switch(config)# cluster member 2 mac-address 00E0.1E00.2222 password keyThis example shows how to add a switch with MAC address 00E0.1E00.3333 to the cluster. This switch does not have a password. The command switch selects the next available member number and assigns it to the switch joining the cluster.
Switch(config)# cluster member mac-address 00E0.1E00.3333You can verify the previous command by entering the show cluster members command in user EXEC mode on the 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 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
default cluster run
Syntax Description
Defaults
Clustering is enabled on all switches.
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter the no cluster run command on a command switch, the command switch is disabled. Clustering is disabled, and the switch is incapable of becoming a candidate switch.
When you enter the no cluster run command on a member switch, it is removed from the cluster. Clustering is disabled, and the switch is incapable of becoming 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 command switch:
Switch(config)# no cluster runYou can verify the previous command by entering the show cluster command in user EXEC mode.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
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 command switch redundancy by binding the Hot Standby Router Protocol (HSRP) standby group to the cluster. Use the no form of this command to unbind the cluster from the HSRP standby group.
cluster standby-group HSRP-group-name
no cluster standby-group
default cluster standby-group
Syntax Description
Defaults
The cluster is not bound to any HSRP group.
Command Modes
Global configuration
Command History
Usage Guidelines
You must enter this command only on the command switch. If you enter it on a member switch, an error message appears.
The command switch propagates the cluster-HSRP binding information to all members. Each 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.
Examples
This example shows how to bind the HSRP group named my_hsrp to the cluster. This command is entered on the command switch.
Switch(config)# cluster standby-group my_hsrpThis example shows the error message when this command is entered on a command switch and the specified HSRP standby group does not exist:
Switch(config)# cluster standby-group my_hsrp%ERROR: Standby group (my_hsrp) doesn't existThis example shows the error message when this command is entered on a member switch.
Switch(config)# cluster standby-group my_hsrp%ERROR: This command runs on a cluster command switchYou can verify the previous commands by entering the show cluster command in user EXEC mode.
Related Commands
standby ip
Enables HSRP on the interface.
Displays the cluster status and a summary of the cluster to which the switch belongs.
show standby
Displays standby group information.
cluster timer
Use the cluster timer global configuration command on the 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
default cluster timer
Syntax Description
Defaults
The interval is 8 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command with the cluster holdtime global configuration command only on the command switch. The 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 command switch.
Switch(config)# cluster timer 3Switch(config)# cluster holdtime 30You can verify the previous commands by entering the show cluster user EXEC command.
Related Commands
Displays the cluster status and a summary of the cluster to which the switch belongs.
controller LongReachEthernet
Use the controller LongReachEthernet global configuration command to enter controller configuration mode.
controller LongReachEthernet ctrlr#
Syntax Description
ctrlr#
The Long-Reach Ethernet (LRE) controller number. Controller numbers are device-specific. Valid entries are 0 to 23 for the Catalyst 2900 LRE XL.
Defaults
There is no default.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enter controller submode. An LRE controller is the LRE chipset in the switch.
Examples
This example shows how to enter controller configuration mode for controller 0.
Switch(config)# controller Lo 0Switch(config-controller)#Related Commands
Configures upgrades on either end of an LRE link.
Prevents an upgrade of the local customer premises equipment (CPE) controller and all remote CPE devices connected to it.
cpe protected
Use the cpe protected interface configuration command to restrict data traffic to individual ports on Cisco 585 LRE customer premises equipment (CPE) ports. Use the no form of this command to allow different ports on the same CPE device to exchange data directly.
cpe protected [port id]
no cpe protected [port id]
Syntax Description
port id
(Optional) The CPE Ethernet port identifier. Valid values vary from 1 to 4, depending on CPE device.
Defaults
The default is no cpe protected.
Command Modes
Interface configuration
Command History
Usage Guidelines
To ensure that data traffic from one CPE port is not accessed on any of the other three ports, use the cpe protected command. The cpe protected command restricts CPE traffic, either at the CPE device level or at the individual port level for data security. By specifying the cpe protected command without a CPE port, data is protected for all applicable CPE ports. By specifying the additional port id parameters, you can protect an indivdual CPE Ethernet port.
When protecting individual CPE ports, always specify a minimum of two ports. A single port that is configured as protected has no effect. Data traffic does not flow between two ports that are protected.
Examples
This example show how to protect CPE port 1 on Long-Reach Ethernet 0/1:
Switch# configure terminalSwitch(config)# interface long 0/2Switch(config-if)# cpe protected port 1Switch(config-if)#Related Commands
debug lre
Use the debug lre privileged EXEC command to enable debugging of Long-Reach Ethernet (LRE)-related events. Use the no form to disable debugging.
debug lre [controller | errors | profile | state | timing]
no debug lre [controller | profile | state | timing]
Syntax Description
Defaults
The default is off.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you use the debug lre command without providing a specific debug option, all LRE debug options are enabled. Conversely, if you use the no debug lre command without providing a specific debug option, all LRE debug options are disabled.
You can enable and disable the LRE debug options on individual ports for the controller, profile, and state debug options. For example, the debug lre state interface-id command debugs the state transition events on a specific port. If a specific port is not provided, the debug option applies to all switch LRE ports.
To troubleshoot LRE connectivity problems, use the debug lre state command to display the state machine transitions and the debug lre errors command to display other information that might explain unusual occurrences that could be affecting connectivity.
Examples
This example shows how to use the command to enable LRE controller event debugging on all switch LRE ports:
Switch# debug lre controllerLRE Controller Events debugging is onThis is an example of output when the debug lre state option is enabled.
*Mar 1 02:11:39: LRE: Lo0/3: FSM_PROFILE_LINKUP: event:EVT_PORT_CONFIG_CHANGE*Mar 1 02:11:40: LRE: Lo0/3: FSM_PROFILE_APPLIED: event:EVT_LRE_LINK_DOWN*Mar 1 02:11:41: LRE: Lo0/3: FSM_PROFILE_APPLIED: event:EVT_LRE_LINK_UPThis example shows how to disable LRE controller event debugging:
Switch# no debug lre controllerThis example shows show to enable debugging with timing information:
Switch# debug lre timingLRE Timing Information debugging is onSwitch#Related Commands
delete
Use the delete privileged EXEC command to delete a file from the file system.
delete {device:}filename
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
A colon (:) follows the device variable. Do not enter spaces after the colon.
Examples
This example shows how to delete the file atm_image from the file system for an ATM
module installed in slot 1:Switch# delete slot1:atm_imageThis example shows how to delete a file from the switch Flash memory:
Switch# delete flash:filenameYou can verify that the file was removed by entering the show flash: user EXEC command.
Related Commands
duplex
Use the duplex interface configuration command 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 {full | half | auto}
no duplex
Syntax Description
full
Port is in full-duplex mode.
half
Port is in half-duplex mode.
auto
Port automatically detects whether it should run in full- or half-duplex mode.
Defaults
For 10/100, 100BASE-FX, and Gigabit ports, the default is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
Certain ports can be configured as 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.
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.
If both the speed and duplex are set to specific values, autonegotiation is disabled.
This command is not supported on the ATM module.
For CPE Ethernet ports, the default is half duplex with back pressure. You can change the duplex setting on the Cisco 575 LRE CPE device, but not on the Cisco 585 LRE CPE device. Duplex autonegotiation is supported on the Cisco 575 LRE CPE device, but not on the Cisco 585 LRE CPE device.
Note
For guidelines on setting the switch speed and duplex parameters, refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example shows how to set port 1 on a Fast Ethernet module installed in slot 2 to full duplex:
Switch(config)# interface fastethernet2/1Switch(config-if)# duplex fullThis example shows how to set port 1 on a Gigabit Ethernet module installed in slot 2 to full duplex:
Switch(config)# interface gigabitethernet2/1Switch(config-if)# duplex fullYou can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
show running-config
Displays the running configuration on the switch.
Specifies the speed of a Fast Ethernet port.
errdisable detect cause
Use the errdisable detect cause global configuration command to enable error disable detection for a UniDirectional Link Detection (UDLD) cause. Use the no form of this command to disable the error disable detection feature.
errdisable detect cause {udld}
no errdisable detect cause {udld}
Syntax Description
Defaults
Detection is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (udld) 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.
Use the errdisable recovery global configuration command to set a recovery mechanism for the cause. The switch re-enables the interface and tries the operation again 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 udld error-disable cause:
Switch(config)# errdisable detect cause udldYou can verify your setting by entering the show errdisable detect user EXEC command.
Related Commands
errdisable recovery
Use the errdisable recovery global configuration command to configure the recovery mechanism variables. Use the no form of this command to return to the default setting.
errdisable recovery {cause {udld} | {interval interval}
no errdisable recovery {cause {udld} | {interval interval}
Syntax Description
Defaults
Recovery is disabled for all causes.
The default recovery interval is 300 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
A cause (udld) 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.
Use this command to set a recovery mechanism for the cause. The switch re-enables the interface and tries the operation again 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 the recovery timer for the udld error-disable cause:
Switch(config)# errdisable recovery cause udldThis example shows how to set the timer to 500 seconds:
Switch(config)# errdisable recovery interval 500You can verify your settings by entering the show errdisable recovery privileged EXEC command.
Related Commands
exit
Use the exit VLAN database command to implement the proposed VLAN database, to increment the database configuration number, to propagate it throughout the administrative domain, and to return to privileged EXEC mode.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
VLAN database
Command History
Usage Guidelines
The exit command implements all the configuration changes that you made since you entered VLAN database mode and uses them for the running configuration. This command returns you to privileged EXEC mode.
Examples
This example shows how to implement the proposed VLAN database and to exit to privileged EXEC mode:
Switch(vlan)# exitSwitch#You can verify the previous command by entering the show vlan brief user EXEC command.
Related Commands
flowcontrol
Use the flowcontrol interface configuration command on Gigabit Ethernet ports to control traffic rates during congestion. Use the no form of this command to disable flow control on the port.
flowcontrol {asymmetric | symmetric}
no flowcontrol
Syntax Description
Defaults
The default is asymmetric.
Command Modes
Interface configuration
Command History
Examples
This example shows how to configure the local port to support any level of flow control by the remote port:
Switch(config-if)# flowcontrolThis example shows how to configure the local port to control the traffic flow from the remote port:
Switch(config-if)# flowcontrol asymmetricYou can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
show interface [interface-id] flow-control
Displays flow-control information for the specified port.
hw-module slot module-slot # upgrade lre
Use the hw-module slot module-slot # lre upgrade lre privileged EXEC command to perform firmware upgrades on Long-Reach Ethernet (LRE) systems.
hw-module slot module-slot # upgrade lre [force] [{local ctrlr unit # | remote interface-id}]
Syntax Description
Defaults
No default is defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the hw-module slot module-slot # upgrade lre command to start an LRE upgrade these ways:
•
•
•
The force option allows users to upgrade an LRE binary on a local LRE controller or a remote LRE CPE device even though the device is already running the version of the desired LRE binary. The default behavior is not to upgrade LRE binaries that are already up-to-date.
During an upgrade, users on the LRE links being upgraded experience a temporary disruption of Ethernet connectivity. All LRE local and remote upgrades run concurrently and take 3 to 6 minutes to complete.
The IOS CLI remains available while an LRE upgrade is in progress.
Once started, an LRE upgrade can only be stopped by physically changing the remote CPE device or by reloading the IOS software on the Ethernet switch.
Under most circumstances, configuration for upgrades is not necessary.
Examples
This example shows how to start a system-wide LRE upgrade:
Switch# hw-module slot 0 upgrade lreYou are about to start an LRE upgrade on all LRE interfaces.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/1.Starting remote upgrade on CPE Lo0/2Starting remote upgrade on CPE Lo0/3Starting remote upgrade on CPE Lo0/4Starting remote upgrade on CPE Lo0/5Starting remote upgrade on CPE Lo0/6Starting remote upgrade on CPE Lo0/7Starting remote upgrade on CPE Lo0/8Starting upgrade on local controller LongReachEthernet 0Starting remote upgrade on CPE Lo0/9Starting remote upgrade on CPE Lo0/10Starting remote upgrade on CPE Lo0/11Starting remote upgrade on CPE Lo0/12Starting remote upgrade on CPE Lo0/13Starting remote upgrade on CPE Lo0/14Starting remote upgrade on CPE Lo0/15Starting remote upgrade on CPE Lo0/16Starting upgrade on local controller LongReachEthernet 1Starting remote upgrade on CPE Lo0/17Starting remote upgrade on CPE Lo0/18Starting remote upgrade on CPE Lo0/19Starting remote upgrade on CPE Lo0/20Starting remote upgrade on CPE Lo0/21Starting remote upgrade on CPE Lo0/22Starting remote upgrade on CPE Lo0/23Starting remote upgrade on CPE Lo0/24Starting upgrade on local controller LongReachEthernet 2This example shows how to start an LRE upgrade on a single LRE controller in a switch. In this example, LongRangeEthernet 0 causes an LRE upgrade on controller 0 in the switch.
Switch# hw-module slot 0 upgrade lre local lo 0You are about to start an LRE upgrade on local controller LongReachEthernet 0.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting Upgrade on local controller LongReachEthernet 0This example shows how to start an LRE upgrade on a single CPE device. In this example, LongRangeEthernet 0/1 causes an LRE upgrade to run on the CPE device connected to LRE link LongRangeEthernet 0/1.
Switch# hw-module slot 0 upgrade lre remote lo 0/1You are about to start an LRE upgrade on CPE Lo0/1.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/1This example shows what happens when you attempt to upgrade firmware without using the force option.
Switch# hw-module slot 0 upgrade lre remote lo 0/1You are about to start an LRE upgrade on CPE Lo0/1.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:No upgrade required on CPE Lo0/1This example shows the output when you attempt to upgrade current firmware on a CPE device by using the force option:
Switch# hw-module slot 0 upgrade lre force remote lo 0/1You are about to start an LRE upgrade on CPE Lo0/1.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/1Switch#Related Commands
interface
Use the interface global configuration command to configure an interface type, to create a switch virtual interface to be used as the management VLAN interface, and to enter interface configuration mode.
interface type slot/port | vlan number
no interface type slot/port | vlan number
Syntax Description
Defaults
The default management VLAN interface is VLAN 1.
Command Modes
Global configuration
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
Usage Guidelines
When creating a management VLAN interface, a space between vlan and number is accepted.
Only one management VLAN interface can be active.
You cannot delete the management VLAN 1 interface.
Before bringing up a new management VLAN interface with the no shutdown command, you must enter the shutdown command to disable the old one.
You can use the management command to shut down the active management VLAN interface and to enable the newly created management VLAN interface.
You can configure the management VLAN interface on static-access, multi-VLAN, dynamic-access, and trunk ports.
Examples
This example shows how to enable the switch to act on ATM interface 1/2:
Switch(config)# interface atm 1/2Switch(config-if)#This example shows how to change the management VLAN from VLAN 1 to VLAN 3. Enter this series of commands only from the console. If you enter these commands through a Telnet session, the shutdown command disconnects the session, and you cannot to use IP to access the system.
Switch# configure terminalSwitch(config)# interface vlan 3Switch(config-subif)# ip address 172.20.128.176 255.255.255.0Switch(config-subif)# exitSwitch(config-if)# exitSwitch(config)# interface vlan 1Switch(config-subif)# shutdownSwitch(config-subif)# exitSwitch(config-if)# exitSwitch(config)# interface vlan 3Switch(config-subif)# no shutdownSwitch(config-subif)# exitSwitch(config-if)# exitThis example shows how to change the management VLAN from VLAN 1 to VLAN 3 through a Telnet session. In this situation, the management command shuts down VLAN 1 and brings up VLAN 3. The Telnet session must be re-established through the new management VLAN.
Switch# configure terminalSwitch(config)# interface vlan 3Switch(config-subif)# ip address 172.20.128.176 255.255.255.0Switch(config-subif)# managementThis example shows how to copy the IP address and the network mask information from the current management VLAN to VLAN 3 and to make VLAN 3 the new management VLAN:
Switch# configure terminalSwitch(config)# interface vlan 3Switch(config-subif)# managementYou can verify the previous commands by entering the show interface and show interface vlan number commands in user EXEC mode.
Related Commands
ip address
Use the ip address interface configuration command to set an IP address for a switch. Use the no form of this command to remove an IP address or to disable IP processing.
ip address ip-address subnet-mask
no ip address ip-address subnet-mask
Syntax Description
Defaults
No IP address is defined for the switch.
Command Modes
Interface configuration
Command History
Usage Guidelines
A switch can have one IP address.
The IP address of the switch can be accessed only by nodes connected to ports that belong to the management VLAN. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
If you remove the IP address through a Telnet session, your connection to the switch will be lost.
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.
Examples
This example shows how to configure the IP address for the switch on a subnetted network:
Switch(config)# interface vlan 1Switch(config-if)# ip address 172.20.128.2 255.255.255.0You can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
show running-config
Displays the running configuration on the switch.
Deletes an IP address for a switch without disabling the IP processing.
ip igmp filter
Use the ip igmp filter interface configuration command to apply an Internet Group Management Protocol (IGMP) profile to an interface and to prevent hosts on an interface from joining one or more IP multicast groups. Use the no form of this command to remove a specified profile from an interface.
ip igmp filter profile number
no ip igmp filter profile number
Syntax Description
Defaults
No IGMP filtering profiles are assigned to an interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
The same IGMP profile can be applied to more than one switch port interface.
Examples
This example shows how to apply an IGMP filtering profile to an interface:
Switch(config-if)# ip igmp filter 30You can verify your settings by entering the show ip igmp profile profile number user EXEC command.
Related Commands
ip igmp max-groups
Use the ip igmp max-groups interface configuration command to specify the maximum number of Internet Group Management Protocol (IGMP) groups that can be active on a port.
ip igmp max-groups number
Syntax Description
number
The maximum number of IGMP filtering groups that can be active on a port. The range is from 0 to 256.
Defaults
No maximum number of IGMP groups are defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
There is no limit to the number of multicast groups that a port can join.
If 0 is specified as the maxgroups value for an interface, that interface cannot join any multicast groups.
Examples
This example shows how to limit the number of IGMP groups that an interface can join to 25.
Switch(config)# interface fastethernet 0/12Switch(config-if)# ip igmp max-groups 25You can verify your setting by using the show running-configuration privileged EXEC command and by specifying an interface.
Switch# show running-config interface fastethernet 0/12Building configuration...Current configuration :124 bytes!interface FastEthernet0/12no ip addressshutdownsnmp trap link-statusip igmp max-groups 25ip igmp filter 22endYou can verify your settings by entering the show running-config interface interface configuration command.
Related Commands
Applies an IGMP filtering profile to an interface.
Displays the details of an IGMP filtering profile entry.
ip igmp profile
Use the ip igmp profile global configuration command to create an Internet Group Management Protocol (IGMP) profile and to enter IGMP profile configuration mode. From this mode, you can specify the configuration of the IGMP profile. Use the no form of this command and a profile number to delete an IGMP profile.
ip igmp profile profile number
no ip igmp profile profile number
Syntax Description
Defaults
No IGMP profiles are defined. When a profile configured, the default action is to deny the addresses in the profile.
Command Modes
Global configuration
Command History
Usage Guidelines
When you are in IGMP profile configuration mode, you can create the profile by using these keywords:
•
•
•
•
•
Examples
This example shows how to create an IGMP filtering profile:
host1# config terminalEnter configuration commands, one per line. End with CNTL/Z.host1(config)# ip igmp profile 30host1(config-igmp-profile)#host1(config-igmp-profile)# denyhost1(config-igmp-profile)# range 233.1.1.1 233.255.255.255host1(config-igmp-profile)# range 235.1.1.1 235.255.255.255host1(config-igmp-profile)# endhost1#Related Commands
login authentication
Use the login authentication line configuration command to enable authentication, authorization, and accounting (AAA) for logins. Use the no form of this command to either disable Terminal Access Controller Access Control System Plus (TACACS+) authentication for logins or to return to the default.
login authentication {default | list-name}
no login {default | list-name}
Syntax Description
default
Use the default list created with the AAA authentication login command.
list-name
Use the indicated list created with the AAA authentication login command.
Defaults
Login authentication is disabled.
Command Modes
Line configuration
Command History
Usage Guidelines
To create a default list that is used if no list is specified in the login authentication command, use the default keyword followed by the methods that you want used in default situations. The default method list is automatically applied to all interfaces.
Examples
This example shows how to specify TACACS+ as the default method for user authentication during login:
Switch(config)# aaa new-modelSwitch(config)# aaa authentication login default tacacsSwitch(config)# line vty 0 4Switch(config-line)# login authentication default tacacsYou can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
lre log
Use the lre log interface configuration command to specify the mode in which LRE events are logged. Use the no form of the command to turn off logging of events.
lre log {disable | event | extended | normal | maximum}
no lre log {disable | event | extended | normal | maximum}
Syntax Description
Defaults
The default is normal.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is not needed for nominal operation of the switch. However, it can be used as a diagnostic tool to analyze activity on the switch.
The maximum number of events that can be logged on a per-port basis is 50. Eventually, the log overwrites itself when full.
Examples
This example of the lre log command shows how to disable the log:
Switch (config)# interface lo0/1Switch(config-if)# lre log disableSwitch (config-if)#This example of the lre log command shows how to set logging for state machines:
Switch (config)# interface lo0/1Switch(config-if)# lre log eventSwitch (config-if)#This example of the lre log command shows how to extend event logging to include all possible parameters:
Switch (config)# interface lo0/1Switch(config-if)# lre log extendedSwitch (config-if)#This example of the lre log command shows how to add some typical parameters to logging events for state machines:
Switch (config)# interface lo0/1Switch(config-if)# lre log normalSwitch (config-if)#This example of the lre log command shows how to not allow logging to be disabled:
Switch (config)# interface lo0/1Switch(config-if)# no lre logSwitch (config-if)#Related Commands
lre patchfile
Use the lre patchfile global configuration command to specify the Long-Reach Ethernet (LRE) patch file used when the switch starts up.
lre patchfile patchfile-name
no lre patchfile patchfile-name
Caution
Syntax Description
Defaults
The default name of the LRE patch file is flash:e2rb.bin.
Command Modes
Global configuration mode
Command History
12.0(5)WC1
This command was first introduced.
12.0(5)WC6
The no keyword was added.
Usage Guidelines
The switch LRE interface might require software maintenance releases referred to as patches. Each patch provides a complete set of LRE features. To take advantage of the full feature set, the LRE switch and the connected CPE device should use the same patch version. Currently, patch 50 is supported.
If you use this command to change to a different patch file, the change takes effect on the next reload only if you have saved this change to the startup configuration.
If you rename the patch file, use the new name when using this command.
If you use the no keyword, the patchfile is ignored when the system starts.
Use the show controllers lre version privileged EXEC command to display the patch version used by the LRE switch and the CPE devices.
Examples
This example shows how to use the lre patchfile e2rb.bin command:
Switch(config)# lre patchfile flash:e2rb.binSwitch(config)#Related Commands
Displays the version number of the hardware, software, and patch software components of the switch LRE interface and the CPE LRE interface.
Enable debugging of LRE-related events.
lre persistence
Use the lre persistence interface configuration command to set the amount of delay before the link reports a link failure. Use the no form of the command to return to the default settting.
lre persistence delay
no lre persistence delay
Syntax Description
Defaults
The default is 3 seconds.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
Enter the lre persistence command before the link enters the profile link-up mode. If the link is already in the profile link-up mode when you enter the persistence value, the new value does not go into effect immediately. Instead, it becomes effective after the profile link goes down and then comes back up again.
Examples:
This example of the lre persistence command establishes a 1-second delay before the link reports a failure:
Switch(config)# interface lo0/1Switch(config-if)# lre persistence 1Switch(config-if)#Related Commands
lre profile
Use the lre profile interface configuration command to add a Long-Reach Ethernet (LRE) profile to a to a specific switch LRE port. Use the no form of this command to return the port to the default profile.
lre profile profile-name
no lre profile profile-name
Syntax Description
Defaults
The LRE-10 private profile is the default profile on each switch LRE port.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
You can use a private profile if the LRE switch is not used with equipment connected to a public switched telephone network (PSTN). The switch supports a variety of private profiles that offer different link speeds and maximum distances. In general, the higher the link speed, the shorter the maximum distance. Private profiles are assigned on a per-port basis. The ports on an LRE switch can be assigned the same or different private profiles.
Each switch LRE port always has a private profile assigned to it. The LRE-10 profile is the default. Public profiles have priority over private profiles. If you assign a public profile to the switch, the switch uses the public profile and ignores any private profile assigned to the switch LRE ports. If a public profile is configured on the switch and you want the switch LRE ports to use private profiles, you must first disable the public profile by using the no lre profile global global configuration command.
When you assign a different profile to a switch LRE port, the port immediately applies and uses the newly assigned profile.
Before you add an LRE switch to a cluster, make sure that you assign it the same public profile that is used by other LRE switches in the cluster. A configuration conflict occurs if a switch cluster has LRE switches using both private and public profiles. If one LRE switch in a cluster is assigned a public profile, all LRE switches in that cluster must have that same public profile. A cluster can have a mix of LRE switches using different private profiles. For more information about clusters, refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
For a complete list of considerations for using LRE profiles, refer to the "LRE Links and LRE Profiles" section in the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example shows how to assign the LRE-4 private profile to the switch LRE port 1:
Switch(config)# interface lo0/1Switch(config-if)# lre profile LRE-15Switch(config-if)#Related Commands
Assigns a public profile to all switch LRE ports.
Displays information about the LRE profiles available on the switch.
show controllers lre profile details
Displays information about how the LRE profiles are assigned to the switch LRE ports.
lre profile global
Use the lre profile global global configuration command to assign a Long-Reach Ethernet (LRE) public profile to all switch LRE ports.
lre profile global profile-name
no lre profile global
Syntax Description
Defaults
No default is defined.
Command Modes
Global configuration mode
Command History
12.0(5)WC1
This command was first introduced.
12.0(5)WC4
This command was extended to support the Cisco 585 LRE CPE device
Usage Guidelines
We strongly recommend using a public profile if the switch is used with equipment directly connected to a public switched telephone network (PSTN) without a private branch exchange (PBX) between the LRE switch and the public telephone lines. When the switch is configured with a public profile, all LRE ports use the same configuration to prevent the switch from causing interference with the other lines on the PSTN.
Note
Note
The standards for spectral profiles have not yet been ratified. The PUBLIC-ANSI profile corresponds to ANSI Plan 998. The PUBLIC-ETSI profile corresponds to ETSI Plan 997. Both plans are draft standards. ANSI and ETSI requirements can vary. The PUBLIC-ANSI and PUBLIC-ETSI profiles are not meant to apply to all conditions. Contact Cisco Systems for the latest information about standards ratification or for updates to the public profiles.
Each switch LRE port always has a private profile assigned to it. The LRE-10 profile is the default. Public profiles have priority over private profiles. If you assign a public profile to the switch, the switch uses the public profile and ignores any private profile assigned to the switch LRE ports. If a public profile is configured on the switch and you want the switch LRE ports to use private profiles, you must first disable the public profile by using the no lre profile global global configuration command.
When you assign a different profile to a switch LRE port, the port immediately resets and uses the newly assigned profile.
Before you add an LRE switch to a cluster, make sure that you assign it the same public profile that is used by other LRE switches in the cluster. A configuration conflict occurs if a switch cluster has LRE switches using both private and public profiles. If one LRE switch in a cluster is assigned a public profile, all LRE switches in that cluster must have that same public profile. A cluster can have a mix of LRE switches using different private profiles. For more information about clusters, refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
For a complete list of considerations for using LRE profiles, refer to the "LRE Links and LRE Profiles" section in the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example shows how to use the lre profile global PUBLIC-ANSI command:
Switch(config)# lre profile global PUBLIC-ANSIYou can verify your settings by entering the show controllers lre profile privileged EXEC command.
Related Commands
Assigns a private profile to a specific switch LRE port.
Displays information about the LRE profiles available on the switch.
show controllers lre profile details
Displays information about how the LRE profiles are assigned to the switch LRE ports.
lre rate selection sequence
Use the lre rate selection sequence global configuration command to assign the rate selection sequence for the entire switch. Use the no form of the command to delete the assigned sequence.
lre rate selection sequence sequenceName
no lre rate selection sequence sequenceName
Syntax Description
Defaults
No default is defined.
Command Modes
Global configuration mode
Command History
Usage Guidelines
The lre rate selection sequence command applies the sequence to all port that have rate selection enabled. The command is rejected if the sequence is not configured with a profile.
When rate selection is enabled, profiles and sequences follow a predefined priority scheme that determines the rate for a port or for the entire switch. These are the priority levels with rate selection enabled, from highest to lowest:
1.
2.
3.
4.
Examples
This example shows how to specify the sequence named lre-seq-upstream:
Switch(config)# lre rate selection sequence lre-seq-upstreamSwitch(config)#Related Commands
lre reset
Use the lre reset interface configuration command to reset the switch Long-Reach Ethernet (LRE) interface or the Cisco LRE customer premises equipment (CPE) interface.
lre reset [local | remote | micro]
Syntax Description
local
Resets the switch LRE interface.
remote
Resets the LRE interface for the CPE device.
micro
Resets the microcontroller in the Cisco 585 CPE device.
Defaults
No default is defined.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
Use this command to troubleshoot LRE port performance.
The lre reset micro command is not supported on the Cisco 575 LRE CPE device.
Examples
This example shows how to reset switch LRE port 1:
Switch(config)# interface lo0/1Switch(config-if)# lre reset localThis example shows how to reset the Cisco 575 LRE CPE device that is connected to switch LRE port 1:
Switch(config)# interface lo0/1Switch(config-if)# lre reset remoteThis example shows how to reset the Cisco 585 LRE CPE device that is connected to switch LRE port 1:
Switch(config)# interface lo0/1Switch(config-if)# lre reset microRelated Commands
lre sequence
Use the lre sequence global configuration command to define a new sequence and to enter sequence configuration mode. Use the no form of the command to delete a user-configured sequence.
lre sequence sequence-name
no lre sequence sequence-name
Syntax Description
Defaults
No default is defined.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command creates a new sequence when the sequence name specified in the command does not match any of the existing configured sequences. When the sequence-name specified in the command matches a configured sequence, a new sequence is not created.
The profiles can be edited from the sequence configuration mode. However, the system-defined sequences cannot be edited. If the sequence specified in this command is a system-defined sequence, the command is rejected. An error message appears if the sequence name matches the name of a system-defined sequence. Use the exit command to return to global configuration mode.
Examples
This example shows how to specify the a user-defined sequence called myseq.
Switch# configure tSwitch(config)# lre sequence myseqSwitch(config-seq)#This example shows how to create a user-defined sequence called corpseq, with two profiles in that sequence.
Switch# configure tSwitch(config)# lre sequence corpseqSwitch(config-seq)# profile lre-15-5Switch(config-seq)# profile lre-15-3Switch(config-seq)# exitSwitch(config)#This example show the error message when trying to edit a system-defined sequence.
Switch(config)# lre sequence lre-seq-complete-reachError:Sequence LRE-SEQ-COMPLETE-REACH is a system defined sequence. Cannot editthis sequenceSwitch(config)#This example shows how a user-defined sequence is deleted.
Switch# configure tSwitch(config)# no lre sequence myseqSwitch(config-seq)# exitSwitch(config)#Related Commands
lre shutdown
Use the lre shutdown interface configuration command to disable the Long-Reach Ethernet (LRE) transmitter of an LRE interface.
lre shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
Use this command to disable the LRE transmitter of an LRE interface. Under some circumstances, the power emitted by switch LRE ports can affect other switch LRE ports. We recommend that you use this commnd to shut down ports that are not connected to CPE devices. Use this command to also disable access to the switch from a particular port.
Examples
This example shows how to deactivate the LRE link on switch LRE port 1:
Switch(config)# interface lo0/1Switch(config-if)# lre shutdownRelated Commands
lre upgrade default family device-family binary
Use the lre upgrade default family global configuration command to define a map between a Long-Reach Ethernet (LRE) device type and an LRE binary.
lre upgrade default family device-family [model model [revision revision]]
binary LRE binaryno lre upgrade default family device-family [model model [revision revision]]
binary LRE binarySyntax Description
Defaults
No default is defined. The system selects the binary file.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Use the lre upgrade default family device-family binary configuration command to override the default behavior for upgrading LRE firmware. This command is useful when you want to upgrade all CPE devices or local controllers of a given family to an LRE binary version.
Note
Examples
This example shows how to configure all CISCO585-LRE CPE devices to upgrade and use LRE binary file CISCO-585-LRE_vdslsngl_51.00.00:
Switch(config)# lre upgrade default family CISCO585-LRE binary CISCO585-LRE_vdslsngl_51.00.00.binSwitch(config)#Related Commands
mac-address-table aging-time
Use the mac-address-table aging-time global configuration command 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 use the default aging-time interval. The aging time applies to all VLANs.
mac-address-table aging-time age
no mac-address-table aging-time
Syntax Description
Defaults
The default is 300 seconds.
Command Modes
Global configuration
Command History
Usage Guidelines
If hosts do not transmit continuously, increase the aging time to record the dynamic entries for a longer time. This can reduce the possibility of flooding when the hosts transmit again.
Examples
This example shows how to set the aging time to 200 seconds:
Switch(config)# mac-address-table aging-time 200You can verify the previous command by entering the show mac-address-table user EXEC command.
Related Commands
mac-address-table dynamic
Use the mac-address-table dynamic global configuration command to add dynamic addresses to the MAC address table. Dynamic addresses are automatically added to the address table and dropped from it when they are not in use. Use the no form of this command to remove dynamic entries from the MAC address table.
mac-address-table dynamic hw-addr interface [atm slot/port] [vlan vlan-id]
no mac-address-table dynamic hw-addr [vlan vlan-id]
Syntax Description
Command Modes
Global configuration
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
11.2(8)SA5
The atm keyword was added.
Usage Guidelines
If the variable vlan-id is omitted and the no form of the command is used, the MAC address is removed from all VLANs.
Examples
This example shows how to add a MAC address on port fa1/1 to VLAN 4:
Switch(config)# mac-address-table dynamic 00c0.00a0.03fa fa1/1 vlan 4You can verify the previous command by entering the show mac-address-table user EXEC command.
Related Commands
mac-address-table notification
Use the mac-address-table notification global configuration command to enable the MAC address notification feature and to configure the notification-trap interval or history table. Use the no form of this command to disable this feature or return to the default setting.
mac-address-table notification [interval seconds] | [history-size value]
no mac-address-table notification [interval seconds] | [history-size value]
Syntax Description
Defaults
MAC notification feature is disabled.
The default trap interval value is one second.
The default number of entries in the history table is one.
Command Modes
Global configuration
Command History
Usage Guidelines
The MAC notification feature sends SNMP traps when a MAC address is learned or deleted from the forwarding tables.
Note
Use the mac-address-table notification command without keywords to enable or disable the feature.
Use this command with the interval or history-size keywords to configure the trap interval or the maximum number of entries in the MAC notification history table.
Note
Use the no mac-address-table notification interval global configuration command to reset the MAC notification history table size to the default of 1 second.
Use the no mac-address-table notification history-size global configuration command to reset the MAC notification history table size to the default of one.
Examples
This example shows how to enable the MAC notification feature:
Switch(config)# mac-address-table notificationThis example shows how to set the notification trap interval to 60 seconds:
Switch(config)# mac-address-table notification interval 60This example shows how to set the number of entries in the history table to 32:
Switch(config)# mac-address-table notification history-size 32You can verify this command by entering the show mac-address-table notification user EXEC command.
Related Commands
mac-address-table secure
Use the mac-address-table secure global configuration command to add secure addresses to the MAC address table. Use the no form of this command to remove secure entries from the MAC address table.
mac-address-table secure hw-addr interface [atm slot/port] [vlan vlan-id]
no mac-address-table secure hw-addr [vlan vlan-id]
Syntax Description
Command Modes
Global configuration
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
11.2(8)SA5
The atm keyword was added.
Usage Guidelines
Secure addresses can be assigned only to one port at a time. Therefore, if a secure address table entry for the specified MAC address and VLAN already exists on another port, it is removed from that port and assigned to the specified one.
Dynamic-access ports cannot be configured with secure addresses.
Examples
This example shows how to add a secure MAC address to VLAN 6 of port fa1/1:
Switch(config)# mac-address-table secure 00c0.00a0.03fa fa1/1 vlan 6This example shows how to add a secure MAC address to ATM port 2/1:
Switch(config)# mac-address-table secure 00c0.00a0.03fa atm 2/1You can verify the previous command by entering the show mac-address-table user EXEC command.
Related Commands
mac-address-table static
Use the mac-address-table static global configuration command to add static addresses to the MAC address table. Use the no form of this command to remove static entries from the MAC address table.
mac-address-table static hw-addr in-port out-port-list [atm slot/port] [vlan vlan-id]
no mac-address-table static hw-addr [in-port in-port] [out-port-list out-port-list] [vlan vlan-id]
Syntax Description
Command Modes
Global configuration
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
11.2(8)SA5
The atm keyword was added.
Usage Guidelines
When a packet is received on the input port, it is forwarded to the VLAN of each port that you specify for the out-port-list. Different input ports can have different output-port lists for each static address. Adding a static address already defined as one modifies the port map (vlan and out-port-list) for the input port specified.
If the variable vlan-id is omitted and the no form of the command is used, the MAC address is removed from all VLANs.
Traffic from a static address is only accepted from a port defined in the in-port variable.
Dynamic-access ports cannot be configured as the source or destination port in a static address entry.
Examples
This example shows how to add a static address with port 1 as an input port and ports 2 and 8 of VLAN 4 as output ports:
Switch(config)# mac-address-table static c2f3.220a.12f4 fa0/1 fa0/2 fa0/8 vlan 4You can verify the previous command by entering the show mac-address-table user EXEC command.
Related Commands
management
Use the management interface configuration command to shut down the current management VLAN interface and to enable the new management VLAN interface. The management VLAN is the VLAN used for managing a cluster of switches. To use this VLAN for switch management, apply this VLAN to a switched virtual interface or to the management interface. The default management VLAN is VLAN 1; however, it can be changed to a new management interface on a different VLAN with valid IDs from 1 to 1001.
This command also copies the current management VLAN IP information to the new management VLAN interface if no new IP address or network mask is provided. It also copies the cluster standby group configuration to the new management VLAN.
management
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
No default management or no management command exists to return the management VLAN to its default state.
The management command is not written to the configuration file, and it is not displayed in the output of the show running-config privileged EXEC command.
Before entering the management command, make sure that these conditions exist:
•
•
•
Use the management command to change the management VLAN on a single switch. Use the global cluster management-vlan n configuration command on the command switch to change the management VLAN on the entire cluster.
Examples
This example shows how to shut down the current management VLAN interface and start VLAN 2 as the management VLAN:
Switch# configure terminalSwitch(config)# interface vlan 2Switch(config-subif)# ip address 172.20.128.176 255.255.255.0Switch(config-subif)# managementSwitch(config-subif)# exitSwitch(config)#This example shows how to copy the IP address and network mask from the current management VLAN to VLAN 2 and make VLAN 2 the management VLAN:
Switch# configure terminalSwitch(config)# interface vlan 2Switch(config-subif)# managementSwitch(config-subif)# exitSwitch(config)#You can verify the previous command by entering the show interface vlan number user EXEC command.
Related Commands
Changes the management VLAN for the entire cluster.
interface vlan
Configures an interface type, creates a switch virtual interface to be used as the management VLAN interface, and enters interface configuration mode.
show interface vlan number
Displays the administrative and operational status of a switching (nonrouting) port.
margin
Use the margin interface configuration command to specify the margin value used to determine link quality during Long-Reach Ethernet (LRE) rate selection. Use the no form of this command to restore the default value.
margin {downstream value | upstream value}
no margin {downstream value | upstream value}
Syntax Description
downstream value
The value at the remote end of the link. Valid entries are from 0 to 10 dB.
upstream value
The value at the local end of the link. Valid entries are from 0 to 10 dB.
Defaults
The default is 0 dB.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
When rate selection is running, the signal-to-noise ratio (SNR) shows the link quality. The switch does not provide any internal mechanism to assure link quality. There can be different requirements for link quality, depending on the required bit-error rate and the noise level of the environment. A noisier environment would require a higher SNR to be able to provide a stable link. A lower bit-error rate would require a higher SNR. Typically a 6-dB margin provides an error rate of 10-21 bits.
In order to provide link stability, you should add a margin to the required SNR. You can configure your margins to an amount that is appropriate for the noise level of your environment. Increasing the margin requirement can cause the system to choose a lower profile, which would in turn translate to a lower rate but with a longer reach.
The switch does not guarantee any margins after a link is activated. Margins are only guaranteed when the link is established. When a link is activated, if the SNR requirements do not match the configured margin level, the link is not established.
Downstream means the remote end of the link and upstream the local end. The link has to satisfy both the local and remote margin requirements. If either one is not met, the link is advertised as down. This command has no significance if rate selection is not running on this interface.
Note
For a full discussion of link stability and margins, refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example shows how to specify a margin of 2 dB for both upstream and downstream. If the SNR is 2 dB above the theoretical minimum for the chosen profile when the link is established, the link is classified as down, and the next profile in the sequence is attempted.
Switch(config-if)# margin upstream 2 downstream 2Switch(config-if)#This example shows show to specify a margin of 1 dB for downstream:
Switch(config-if)# margin downstream 1Switch(config-if)#Related Commands
Assigns a rate selection sequence for the entire switch.
Enables rate selection on a specific port.
Assigns a rate selection sequence for a specific port.
mvr (global configuration)
Use the mvr global configuration command without keywords to enable the multicast VLAN registration (MVR) feature on the switch. Use the no form of this command to disable MVR and its options.
Use the command with keywords to 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 the commands to return the switch to the default settings.
mvr [group ip-address [count] [querytime value] [vlan vlan-id] ]
no mvr [group ip-address [count] [querytime value] [vlan vlan-id] ]
Syntax Description
Defaults
MVR is disabled.
The switch hardware determines the maximum number of MVR entries.
No IP multicast addresses are configured on the switch.
The default count is 1.
The default query response time is 0.5 second.
The default multicast VLAN is VLAN 1.
Command Modes
Global configuration
Command History
Usage Guidelines
The switch hardware determines the maximum number of MVR entries.
Use the mvr group command to statically set 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.
Note
The mvr querytime parameter applies only to receiver ports. You should configure the query time before enabling MVR and configuring the static multicast groups. You can change the query time after MVR is enabled, but you receive a warning message:
Warning: Changing MVR query response time while MVR is running.Set the MVR multicast VLAN before the multicast addresses are configured. If it is necessary to change the multicast VLAN, disable MVR, change the VLAN number, and then reenable MVR. Previously configured groups are restored.
Examples
This example shows how to enable MVR:
Switch(config)# mvrThis example shows how to disable MVR:
Switch(config)# no mvrUse the show mvr privileged EXEC command to display the 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.4This command fails because of address aliasing:
Switch(config)# mvr group 230.1.23.4Cannot add this IP address - aliases with previously configured IP address 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 10This example shows how to delete the previously configured ten IP multicast addresses:
Switch(config)# no mvr group 228.1.23.1 10This example shows how to delete all previously configured IP multicast addresses:
Switch(config)# no mvr groupUse the command show mvr members to display the IP multicast group addresses configured on the switch.
This example shows how to set the maximum query response time as 1 second (10 tenths):
Switch(config)# mvr querytime 10This example shows how to return the maximum query response time to the default setting of 0.5 second:
Switch(config)# no mvr querytimeThis example shows how to set VLAN 2 as the multicast VLAN:
Switch(config)# mvr vlan 2You can verify your settings by entering the show mvr privileged EXEC command.
Related Commands
mvr (interface configuration)
Use the mvr interface configuration command to configure a port as a multicast VLAN registration (MVR) receiver or source port and set the Immediate Leave feature.
Use the no form of the commands to return the port to the default settings.
mvr {type {source | receiver} | immediate}
no mvr {type {source | receiver} | immediate}
Syntax Description
Defaults
A port is configured as neither receiver nor source.
The Immediate Leave feature is disabled on all ports.
No receiver port is a member of any configured multicast group.
Command Modes
Interface configuration
Command History
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.
Configure a port as a receiver port if that port should only be able to receive multicast data and should not be able to send multicast data to the configured multicast groups. None of the receiver ports receives multicast data unless it sends an Internet Group Management Protocol (IGMP) group join message for a multicast group.
Note
A port that is not taking part in MVR should not be configured as an MVR receiver port or source port. This port is a normal switch port and is able to send and receive multicast data with normal switch behavior.
The Immediate Leave feature applies only to receiver ports. When the Immediate Leave feature is enabled, a receiver port leaves a multicast group more quickly. When the switch receives an IGMP leave message from a group on a receiver port, it sends out an IGMP 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 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, thus speeding up leave latency.
Enable the Immediate Leave feature only on receiver ports to which a single receiver device is connected.
All receiver ports must be on the same VLAN and cannot be trunk ports. A receiver configured as a static member of a multicast group remains a member until statically removed from membership.
MVR does not support IGMP dynamic joins. You must configure static multicast addresses for receiver ports.
The receiver VLAN is the VLAN to which the first configured receiver port belongs. If the first receiver port is a dynamic port with an unassigned VLAN, it becomes an inactive receiver port and does not take part in MVR until it is assigned to the receiver VLAN. The receiver VLAN is reset whenever there are no remaining receiver ports on the switch (active or inactive), which means that the receiver VLAN might change every time the first receiver port is configured.
Examples
This example shows how to configure port 0/1 as an MVR receiver port:
Switch(config)# interface FastEthernet 0/1Switch(config-if)# mvr type receiverThis example shows how to configure port 0/3 as an MVR source port:
Switch(config)# interface FastEthernet 0/3Switch(config-if)# mvr type sourceThis example shows how to remove port 0/1 from taking part in MVR:
Switch(config)# interface FastEthernet 0/1Switch(config-if))# no mvrThis example shows how to display configured receiver ports and source ports.:
Switch# show mvr interface
MVR PORTSPort: Fa0/1 Type: RECEIVER Status: ACTIVEPort: Fa0/2 Type: RECEIVER Status: ACTIVEPort: Fa0/3 Type: SOURCE Status: ACTIVEThis example shows how to enable Immediate Leave on Fast Ethernet port 0/1:
Switch(config)# interface FastEthernet 0/1Switch(config-if)# mvr immediateThis example shows how to disable Immediate Leave on port 0/1:
Switch(config)# interface FastEthernet 0/1Switch(config-if)# no mvr immediateTo display whether or not Immediate Leave is enabled on an interface, use the command show mvr for the interface as in this example:
Switch# show mvr interface fastethernet 0/1Interface: Fa0/1Immediate Leave: FALSEUse the show mvr members privileged EXEC command to display the multicast group address, the VLAN, and the receiver port.
Related Commands
ntp broadcast client
Use the ntp broadcast client interface configuration command to allow the system to receive Network Time Protocol (NTP) broadcast packets on an interface. Use the no form of the command to disable this capability.
ntp broadcast client
no ntp broadcast client
Syntax Description
This command has no arguments or keywords.
Defaults
Broadcast client mode is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to allow the system to listen to broadcast packets on an interface-by-interface basis. Enter this command on the management VLAN interface. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
Examples
This example shows how to synchronize the router to NTP packets that are broadcast on interface VLAN1:
Switch(config-if)# interface vlan1Switch(config-if)# ntp broadcast clientYou can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
ntp broadcast destination
Use the ntp broadcast destination interface configuration command to configure a Network Time Protocol (NTP) server or peer to restrict the broadcast of NTP frames to the IP address of a designated client or a peer. Use the no form of the command to return the setting to its default.
ntp broadcast destination IP-address
no ntp broadcast destination
Syntax Description
Defaults
No IP address or host name is assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter this command on the management VLAN interface. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
Examples
This example shows how to restrict the broadcast of NTP frames to a specific IP address:
Switch(config-if)# interface vlan1Switch(config-if)# ntp broadcast destination 172.20.128.176Related Commands
ntp broadcast key
Use the ntp broadcast key interface configuration command to configure a Network Time Protocol (NTP) server or peer to broadcast NTP frames with the authentication key that is embedded in the NTP packet. Use the no form of the command to return the setting to its default.
ntp broadcast key number
no ntp broadcast key
Syntax Description
number
The NTP authentication key that is embedded in the NTP packet. The range is from 0 to 4294967295.
Defaults
No NTP broadcast key is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enter this command on the management VLAN interface. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
Examples
This example shows how to assign an authentication key to outgoing NTP frames:
Switch(config)# interface vlan1Switch(config-if)# ntp broadcast key 1Related Commands
ntp broadcast version
Use the ntp broadcast interface configuration command to specify that a specific interface should send Network Time Protocol (NTP) broadcast packets. Use the no form of the command to disable this capability.
ntp broadcast version number
no ntp broadcast
Syntax Description
Defaults
Version 3 is the default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Cisco IOS uses NTP version 3 by default. If the network (NTP server) is using NTP version 2, and synchronization does not occur, use NTP version 2.
Enter this command on the management VLAN interface. By default, the management VLAN is VLAN 1, but you can configure a different VLAN as the management VLAN.
Examples
This example shows how to configure interface VLAN 1 to send NTP version 2 packets:
Switch(config-if)# interface vlan1Switch(config-if)# ntp broadcast version 2You can verify the previous commands by entering the show running-config privileged EXEC command.
Related Commands
Allows the system to receive NTP broadcast packets on an interface.
show running-config
Displays the running configuration on the switch.
ntp max-associations
Use the ntp max-associations global configuration command to set the maximum number of Network Time Protocol (NTP) associations that are allowed on a server. Use the no form of this command to disable this feature.
ntp max-associations [number]
no ntp max-associations
Syntax Description
Defaults
The number of NTP associations is 100.
Command Modes
Global configuration
Command History
Usage Guidelines
This command can control the number of peers that can use the switch to synchronize to it through NTP.
After you enable a switch as an NTP server, use this command to set the maximum number of associations that are allowed on a server.
Examples
This example shows how to set the maximum number of NTP associations to 44:
Switch(config)# ntp max-associations 44You can verify the previous command by entering the show running-config privileged EXEC command.
Related Commands
ntp source
Use the ntp source global configuration command to use a particular source address in Network Time Protocol (NTP) packets. Use the no form of this command to remove the specified source address.
ntp source interface
no ntp source
Syntax Description
Defaults
No source address is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command when you want to use a particular source IP address for all NTP packets. The address is taken from the specified interface. This command is useful if the address on an interface cannot be used as the destination for reply packets. If the source keyword is present on an ntp server or ntp peer command, that value overrides the global value.
Examples
This example shows how to configure the switch to use the IP address of VLAN1 as the source address of all outgoing NTP packets:
Switch(config)# ntp source vlan1You can verify the previous command by entering the show running-config privileged EXEC command.
Related Commands
Allows the switch system clock to be synchronized by a time server.
show running-config
Displays the running configuration on the switch.
port block
Use the port block interface configuration command to block the flooding of unknown unicast or multicast packets to a port. Use the no form of this command to resume normal forwarding.
port block {unicast | multicast}
no port block {unicast | multicast}
Syntax Description
unicast
Packets with unknown unicast addresses are not forwarded to this port.
multicast
Packets with unknown multicast addresses are not forwarded to this port.
Defaults
Flood unknown unicast and multicast packets to all ports.
Command Modes
Interface configuration
Command History
Usage Guidelines
The port block command cannot be entered for a network port.
If a trunk port is not a network port, the unicast keyword applies. The multicast keyword is supported on trunk ports. Both port block features affect all the VLANs associated with the trunk port.
Examples
This example shows how to block the forwarding of multicast and unicast packets to a port:
Switch(config-if)# port block unicastSwitch(config-if)# port block multicastYou can verify the previous commands by entering the show port block user EXEC command.
Related Commands
port group
Use the port group interface configuration command to assign a port to a Fast EtherChannel or Gigabit EtherChannel port group. Up to 12 port groups can be created on a switch. Any number of ports can belong to a destination-based port group. Up to eight ports can belong to a source-based port group. Use the no form of this command to remove a port from a port group.
port group group-number [distribution {source | destination}]
no port group
Syntax Description
Defaults
Port does not belong to a port group.
The default forwarding method is source.
Command Modes
Interface configuration
Command History
Usage Guidelines
An Asynchronous Transfer Mode (ATM) port is the only port that cannot belong to a port group. For all other ports, these restrictions apply:
•
•
•
•
•
•
When a group is first formed, the switch automatically sets these parameters to be the same on all ports:
•
•
•
•
•
•
•
•
•
•
Configuration of the first port added to the group is used when setting the above parameters for other ports in the group. After a group is formed, changing any parameter in the above list changes the parameter on all other ports.
Use the distribution keyword to customize the port group to your particular environment. The forwarding method you choose depends on how your network is configured. However, source-based forwarding works best for most network configurations.
This command is not supported on the ATM modules or on Long-Reach Ethernet (LRE) ports..
Examples
This example shows how to add a port to a port group by using the default source-based forwarding:
Switch(config-if)# port group 1This example shows how to add a port to a group by using destination-based forwarding:
Switch(config-if)# port group 2 distribution destinationYou can verify the previous commands by entering the show port group user EXEC command.
Related Commands
port monitor
Use the port monitor interface configuration command to enable Switch Port Analyzer (SPAN) port monitoring on a port. Use the no form of this command to return the port to its default value.
port monitor [interface | vlan vlan-id]
no port monitor [interface | vlan vlan-id]
Syntax Description
Defaults
Port does not monitor any other ports.
Command Modes
Interface configuration
Command History
11.2(8)SA
This command was first introduced.
11.2(8)SA3
The vlan keyword was added.
Usage Guidelines
Enabling port monitoring without specifying a port causes all other ports in the same VLAN to be monitored.
Entering the port monitor vlan 1 command causes monitoring of all traffic to and from the IP address configured on VLAN 1.
Asynchronous Transfer Mode (ATM) ports are the only ports that cannot be monitor ports. However, you can monitor ATM ports. These restrictions apply for ports that have port-monitoring capability:
•
•
•
•
•
•
Examples
This example shows how to enable port monitoring on port fa0/2:
Switch(config-if)# port monitor fa0/2You can verify the previous command by entering the show port monitor user EXEC command.
Related Commands
port network
Use the port network interface configuration command to define a port as the switch network port. All traffic with unknown unicast addresses is forwarded to the network port on the same VLAN. Use the no form of this command to return the port to the default value.
port network
no port network
Syntax Description
This command has no arguments or keywords.
Defaults
No network port is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
These restrictions apply to network ports:
•
•
•
•
•
•
Examples
This example shows how to set a port as a network port:
Switch(config-if)# port networkYou can verify the previous command by entering the show port network privileged EXEC command.
Related Commands
port protected
Use the port protected interface configuration command to isolate unicast, multicast, and broadcast traffic at Layer 2 from other protected ports on the same switch. Use the no form of the command to disable the protected port.
port protected
no port protected
Syntax Description
This command has no keywords or arguments.
Defaults
No protected port is defined.
A protected port does not forward any unicast, multicast, or broadcast traffic to any other protected port.
A protected port continues to forward and receive unicast, multicast, and broadcast traffic to and from unprotected ports.
Command Modes
Interface configuration
Command History
Usage Guidelines
The port protection feature is local to the switch; communication between protected ports on the same switch is possible only through a Layer 3 device. To prevent communication between protected ports on different switches, you must configure the protected ports for unique VLANs on each switch and configure a trunk link between the switches.
A protected port cannot be a network port.
Port monitoring does not work if both the monitor and monitored ports are protected ports.
A protected port is different from a secure port.
Examples
This example shows how to enable a protected port on interface fa0/3:
Switch(config)# interface fa0/3Switch(config-if)# port protectedYou can verify the previous command by entering the show port protected user EXEC command.
Related Commands
port security
Use the port security interface configuration command to enable port security on a port, to set the aging time for dynamic and static secure address entries, and to restrict the use of the port to a user-defined group of stations. Use the no form of this command to return the port to its default value.
port security [action {shutdown | trap} | aging | max-mac-count addresses]
no port security
Syntax Description
Defaults
Port security is disabled.
When enabled, the default action is to generate an SNMP trap.
The port security aging feature is disabled. The default time is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
To enable aging for all dynamic and static secure addresses on a particular port, set the aging time to a value other than 0 for that port.
If you specify trap, use the snmp-server host global configuration command to configure the SNMP trap host to receive traps.
These restrictions apply to secure ports:
•
•
•
•
•
•
Examples
This example shows how to enable port security and what action the port takes in case of an address violation (shutdown).
Switch(config-if)# port security action shutdownThis example shows how to set the port security aging time to 2 hours on port 1.
Switch(config)# interface fa0/1Switch(config-if)# port security aging time 120This example shows how to set the maximum number of addresses that the port can learn to 8.
Switch(config-if)# port security max-mac-count 8You can verify the previous commands by entering the show port security privileged EXEC command.
Related Commands
port storm-control
Use the port storm-control interface configuration command to enable broadcast, multicast, or unicast storm control on a port. Use the no form of this command to disable storm control or one of the storm-control parameters on the port.
port storm-control {broadcast | multicast | unicast} {{action {filter | shutdown} | threshold {rising rising-number falling falling-number} | trap}}
no port storm-control {broadcast | multicast | unicast}
Syntax Description
Defaults
Broadcast, multicast, and unicast storm control are disabled.
The rising thresholds are 500 broadcast packets per second, 2500 multicast packets per second, and 5000 unicast packets per second.
The falling thresholds are 250 broadcast packets per second, 1200 multicast packets per second, and 2500 unicast packets per second.
Command Modes
Interface configuration
Command History
11.2(8)SA
This command was first introduced.
12.0(5)XU
The multicast, unicast, action, and shutdown keywords were added.
Usage Guidelines
Do not set the rising and falling thresholds to the same value.
Examples
This example shows how to enable broadcast storm control on a port. In this example, transmission is inhibited when the number of broadcast packets arriving on the port reaches 1000 and is restarted when the number drops to 200.
Switch(config-if)# port storm-control broadcast threshold rising 1000 falling 200You can verify the previous command by entering the show port storm-control user EXEC command.
Related Commands
power inline
Use the power inline interface configuration command to determine how inline power is applied to the device on the specified Fast Ethernet port of the Catalyst 3524-PWR XL switch. Use the no form of this command to return the setting to its default.
power inline {auto | never}
no power inline
Syntax Description
Defaults
Power is applied when a telephone is detected on the port (auto).
Command Modes
Interface configuration
Command History
Examples
This example shows how to always apply power to the port:
Switch(config-if)# power inline autoYou can verify the previous command by entering the show power inline privileged EXEC command.
Related Commands
Displays the power status for the specified port or for all ports.
switchport priority extend
Determines how the inline device connected to the specified port handles priority traffic received on its incoming port.
Configures the voice VLAN on the port.
profile
Use the profile sequence configuration command to add a Long-Reach Ethernet (LRE) profile to a rate selection sequence. Use the no form of this command to delete a profile from the sequence.
profile profile-name
no profile profile-name
Syntax Description
Defaults
The default is LRE-10.
Command Modes
Sequence mode
Command History
Usage Guidelines
When you add an LRE profile to a sequence, the profile is added to a first-in, first-out (FIFO) queue. Rate selection attempts to establish a link with the first profile in the queue. If the link is not established in that profile, rate selection uses the next profile in the queue.
You cannot add a profile in the middle of the sequence or queue. You cannot add or delete a profile from a system-defined sequence. In order to add a profile to a user-defined sequence in the middle of a sequence, you would first need to delete the most recent profiles.
Although you can delete a profile from a sequence, you cannot change a sequence configuration if it is in use by an interface. You also cannot add or delete a profile from a system-defined sequence.
For a complete list of considerations for using LRE profiles and profile sequences, refer to the "LRE Links and LRE Profiles" section in the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example shows how to assign the LRE-4 profile to the SEQ2DOWNSYM sequence:
Switch(config)# lre sequence seq2downSwitch(config-seq)# profile LRE-4Switch(config-seq)#Related Commands
rate selection
Use the rate selection interface configuration command to enable rate selection on a port. Use the no form of this command to disable rate selection on ports already configured for rate selection.
rate selection
no rate selection
Syntax Description
This command has no arguments or keywords.
Defaults
The default is that rate selection is enabled.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
Use this command to enable rate selection on a port. The rate selection command does not cause rate selection to start. To start rate selection, a sequence needs to be assigned to a port. This command does not specify a sequence. Use the rate selection sequence command or the lre rate selection sequence command to specify a sequence.
If rate selection is disabled on the switch and a global sequence is also configured on the switch, configuring rate selection at the port sequence level causes rate selction to run. Rate selection runs because the port sequences have precedence over global sequences.
Examples
This example shows how to disable the rate selection feature on a port.
Switch(config-if)# no rate selectionSwitch(config-if)#Related Commands
rate selection profile lock
Use the rate selection profile lock interface configuration command to lock a profile in a port that is enabled for rate selection. Use the no form of the command to unlock a profile in a port.
rate selection profile lock
no rate selection profile lock
Syntax Description
This command has no arguments or keywords.
Command Modes
Interface configuration mode
Command History
Usage Guidelines
This command does not enable rate selection. It only has significance when a sequence is assigned to a port.
If rate selection is already converged on the port, this command causes the profile chosen by rate selection to immediately lock. During the lock process, the name of the profile appends to the end of this command. For example, if rate selection converges on LRE-15 and you enter this command, the resulting locked configuration looks like this:
rate selection profile lock LRE-15If rate selection is not already converged on the port, this command has no immediate effect. However, when rate selection converges for that port, the profile is locked immediately, and the output of the running configuration is saved as in this example.
Examples
This example locks a profile to a port that is running rate selection:
Switch(config-if)# rate selection profile lockSwitch(config-if)#Related Commands
Assigns a sequence on a port.
Assigns a sequence for the entire switch.
show controllers lre status sequence
Displays information about the profiles and sequences when the sequence parameter is specified.
rate selection sequence
Use the rate selection sequence interface configuration command to assign a sequence to a port and to start rate selection. The no form of the command removes a specific rate selection sequence on a port.
rate selection sequence sequenceName
no rate selection sequence sequenceName
Syntax Description
Command Modes
Interface configuration mode
Command History
Usage Guidelines
A sequence is a list of profiles. Using this command overrides the default profile of LRE-10 and assigns a sequence of your choice.
When rate selection is enabled, profiles and sequences follow a predefined priority scheme that determines the rate for a port or for the entire switch. These are the priority levels with rate selection enabled, from highest to lowest:
1.
2.
3.
4.
Cisco provides a set of preconfigured sequences, called system-defined sequences. System-defined sequences cannot be modified. Users can create and modify their own sequences by using the lre profile command.
For further details on profiles, sequences and their priority scheme, see Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide.
Examples
This example of the rate selection sequence command applies the sequence, CISCO-COMPLETE-SEQUENCE to the port:
Switch(config-if)# rate selection sequence CISCO-COMPLETE-SEQUENCESwitch(config-if)#Related Commands
Enables rate selection on ports already configured for rate selection.
Displays the list of sequences.
rcommand
Use the rcommand user EXEC command to start a Telnet session and to enter commands on a member switch from the command switch. To end the session, enter the exit command.
rcommand {n | commander | mac-address hw-addr}
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
If the switch is the command switch but the member switch n does not exist, an error message appears. To obtain the switch number, enter the show cluster members privileged EXEC command from the command switch.
You can use this command to access a member switch from the command-switch prompt or to access a command switch from the member-switch prompt.
For Catalyst 2900 XL and Catalyst 3500 XL switches, the Telnet session accesses the member-switch command-line interface (CLI) at the same privilege level as on the command switch. For example, if you enter this command at user level on the cluster command switch, the member switch is accessed at user level. If you use this command on the 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 member switch is at user level.
For Catalyst 1900 and Catalyst 2820 switches running standard edition software, the Telnet session accesses the menu console (the menu-driven interface) if the command switch is at privilege level 15. If the command switch is at privilege level 1, you are prompted for the password before being able to access the menu console. Command switch privilege levels map to the member switches running standard edition software as follows:
•
•
The Catalyst 1900 and Catalyst 2820 CLI is available only on switches running Enterprise Edition Software.
This command does not work if the vty lines of the command switch have access-class configurations.
You are not prompted for a password because the member switches inherited the password of the 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 3Switch-3> show versionCisco Internet Operating System Software ......Switch-3> exitSwitch>Related Commands
reset
Use the reset VLAN database command to abandon the proposed VLAN database and to remain in VLAN database mode. This command resets the proposed database to the currently implemented VLAN database on the switch.
reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default is defined.
Command Modes
VLAN database
Command History
Examples
This example shows how to abandon the proposed VLAN database and to reset to the VLAN database:
Switch(vlan)# resetSwitch(vlan)#You can verify the previous command by entering the show changes and show proposed VLAN database commands.
Related Commands
rmon collection stats
Use the rmon collection stats interface configuration command to collect Ethernet group statistics. The Ethernet group statistics include utilization statistics about broadcast and multicast packets, and error statistics about Cyclic Redundancy Check (CRC) alignment errors and collisions. Use the no form of this command to return to the default setting.
rmon collection stats index [owner name]
no rmon collection stats index [owner name]
Syntax Description
index
Remote Network Monitoring (RMON) collection control index. The range is from 1 to 65535.
owner name
(Optional) Owner of the RMON collection.
Defaults
The RMON statistics collection is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The RMON statistics collection command is based on hardware counters.
Examples
This example shows how to collect RMON statistics for the owner root on interface fa01:
Switch(config)# interface fa0/1Switch(config-if)# rmon collection stats 2 owner rootYou can verify this command by entering the show rmon statistics command in user EXEC mode.
Related Commands
show rmon statistics
Displays RMON statistics.
Refer to the Cisco IOS Release 12.0 documentation on Cisco.com for information about this command.
session
Use the session privileged EXEC command to log into the Asynchronous Transfer Mode (ATM) module operating system and to start a command-line interface (CLI) session. Enter the exit command, or press Ctrl-G to return to the switch command-line interface.
session number
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to log in to the ATM module number 1:
Switch# session 1Related Commands
show cgmp
Use the show cgmp user EXEC command to display the state of the Cisco Group Management Protocol (CGMP)-learned multicast groups and routers.
show cgmp [state | holdtime | [vlan vlan-id] | [group [address] | router [address]]] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
User EXEC
Command History
Usage Guidelines
This command displays CGMP information about known routers and groups, as well as whether CGMP is enabled, whether Fast Leave is enabled, and the value of the router timeout. If show cgmp is entered with no arguments, all information appears.
Examples
This is an example of output from the show cgmp command.
Switch> show cgmpCGMP is running.CGMP Fast Leave is not running.CGMP Allow reserved address to join GDA.Default router timeout is 300 sec.vLAN IGMP MAC Address Interfaces------ ----------------- -----------1 0100.5e01.0203 Fa0/81 0100.5e00.0128 Fa0/8vLAN IGMP Router Expire Interface------ ----------------- -------- ----------1 0060.5cf3.d1b3 197 sec Fa0/8Related Commands
Enables CGMP. Also enables and disables the Fast Leave parameter and sets the router port aging time.
Deletes information that was learned by the switch by using CGMP.
show changes
Use the show changes VLAN database command to display the differences between the VLAN database on the switch and the proposed VLAN database. You can also display the differences between the two for a selected VLAN.
show changes [vlan-id] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
VLAN database
Command History
Examples
This is an example of output from the show changes command. It displays the differences between the current and proposed databases.
Switch(vlan)# show changesDELETED:VLAN ISL Id: 4Name: VLAN0004Media Type: EthernetVLAN 802.10 Id: 100004State: OperationalMTU: 1500DELETED:VLAN ISL Id: 6Name: VLAN0006Media Type: EthernetVLAN 802.10 Id: 100006State: OperationalMTU: 1500
