|
|
Use the set rsmautostate command to enable/disable line protocol state determination of the RSM(s) due to port state changes. When you enable rsmautostate, VLAN interfaces on the RSM are active only when there is at least one other active interface within the Catalyst 5000 series switch. This could be a physical end-user port, a trunk connection for which the VLAN is active, or even another RSM with an equivalent VLAN interface.
set rsmautostate {enable | disable}
enable | Keyword to activate line protocol state determination. |
disable | Keyword to deactivate line protocol state determination. |
The default configuration has line protocol state determination disabled.
Switch command.
Privileged.
This feature is useful for discontinuing the advertisement of routing paths when access to them is severed (either through fault or administrative disabling).
If you disable rsmautostate, you might have to use the shutdown/no shutdown Cisco IOS command to disable and then restart the VLAN interface to bring the RSM back up.
This example shows how to enable the line protocol state determination of the RSM:
Console> (enable) set rsmautostate enable
Console> (enable)
This example shows how to disable the line protocol state determination of the RSM:
Console> (enable) set rsmautostate disable
Console> (enable)
Use the set snmp community command to set SNMP communities and associated access types.
set snmp community {read-only | read-write | read-write-all} [community_string]
read-only | Keyword to assign read-only access to the specified SNMP community. |
read-write | Keyword to assign read-write access to the specified SNMP community. |
read-write-all | Keyword to assign read-write access to the specified SNMP community. |
community_string | (Optional) Name of the SNMP community. |
The default configuration has the following communities and access types defined:
Switch command.
Privileged.
There are three configurable SNMP communities, one for each access type. If you do not specify the community string, the community string configured for that access type is cleared.
This example shows how to set read-write access to the SNMP community called yappledapple:
Console> (enable) set snmp community read-write yappledapple
SNMP read-write community string set. Console> (enable)
This example shows how to clear the community string defined for read-only access:
Console> (enable) set snmp community read-only
SNMP read-only community string cleared. Console> (enable)
Use the set snmp extendedrmon command to enable or disable the Network Analysis Module.
set snmp extendedrmon {enable | disable}
enable | Keyword to enable the Network Analysis Module. |
disable | Keyword to disable the Network Analysis Module. |
The default is enabled.
Switch command.
Privileged.
This example shows how to enable the Network Analysis Module:
Console> (enable) set snmp extendedrmon enable
Snmp extended RMON module enabled Console> (enable)
This example shows how to disable the Network Analysis Module:
Console> (enable) set snmp extendedrmon disable
Snmp extended RMON module disabled Console> (enable)
Use the set snmp extendedrmon netflow command to enable or disable the Network Analysis Module to receive the NDE stream from an NFFC or NFFC II installed in the Catalyst 5000 series switch and present the resulting statistics on reserved ifIndex.3000.
set snmp extendedrmon netflow {enable password | disable}
enable | Keyword to allow the Network Analysis Module to receive the NDE stream from an NFFC or NFFC II installed in the Catalyst 5000 series switch. |
password | NetFlow Monitor registration password. |
disable | Keyword to prevent the Network Analysis Module from receiving the NDE stream. |
The default is SNMP-extended RMON NetFlow disabled.
Switch command.
Privileged.
To enable the NetFlow Monitor option, purchase a NetFlow Monitor option license from your Cisco sales representative. This option license has a registration key and URL on it. Access the URL and enter the registration key and the MAC address of the Network Analysis Module to generate the password for your Network Analysis Module.
This example shows how to enable SNMP-extended RMON NetFlow support:
Console> (enable) set snmp extendedrmon netflow enable <password>
Snmp extended RMON netflow enabled Console> (enable)
This example shows how to disable SNMP-extended RMON NetFlow support:
Console> (enable) set snmp extendedrmon netflow disable
Snmp extended RMON netflow disabled Console> (enable)
Use the set snmp extendedrmon vlanagent command to enable or disable the VLANagent option. If the VLANagent option is enabled, the Network Analysis Module aggregates statistics by VLAN as well as by port.
set snmp extendedrmon vlanagent {enable | disable}
enable | Keyword to activate SNMP-extended RMON VLANagent support. |
disable | Keyword to deactivate SNMP-extended RMON VLANagent support. |
The default is SNMP-extended RMON VLANagent disabled.
Switch command.
Privileged.
The VLANagent option imposes an increased load on the Network Analysis Module and might not be suitable for use on a heavily loaded switch or when the switch is configured to analyze a high volume of network traffic.
This example shows how to enable extended RMON VLANagent support:
Console> (enable) set snmp extendedrmon vlanagent enable
Snmp extended RMON vlanagent enabled Console> (enable)
This example shows how to disable extended RMON VLANagent support:
Console> (enable) set snmp extendedrmon vlanagent disable
Snmp extended RMON vlanagent disabled Console> (enable)
Use the set snmp extendedrmon vlanmode command to enable or disable the VLAN monitor option. If the VLAN monitor option is enabled, the Network Analysis Module aggregates statistics by VLAN, rather than by source MAC address.
set snmp extendedrmon vlanmode {enable | disable}
enable | Keyword to activate SNMP-extended RMON VLAN mode support. |
disable | Keyword to deactivate SNMP-extended RMON VLAN mode support. |
The default is SNMP-extended RMON VLAN mode disabled.
Switch command.
Privileged.
This example shows how to enable extended-RMON VLAN mode support:
Console> (enable) set snmp extendedrmon vlanmode enable
Snmp extended RMON vlanmode enabled Console> (enable)
This example shows how to disable extended-RMON VLAN mode support:
Console> (enable) set snmp extendedrmon vlanmode disable
Snmp extended RMON vlanmode disabled Console> (enable)
Use the set snmp rmon command to enable or disable SNMP RMON support.
set snmp rmon {enable | disable}
enable | Keyword to activate SNMP RMON support. |
disable | Keyword to deactivate SNMP RMON support. |
The default for RMON support is disabled.
Switch command.
Privileged.
RMON statistics are collected on a segment basis instead of a repeater-port basis for the Catalyst 5000 series group switching Ethernet modules (WS-X5020 and WS-X5223).
The RMON feature deinstalls the domains for all of the interfaces on an Ethernet module that has been removed from the system.
RMON is supported on Ethernet, Fast Ethernet, Gigabit Ethernet, and Token Ring switch ports.
When RMON is enabled, the supported RMON groups for Ethernet ports are Statistics, History, Alarms, and Events, as specified in RFC 1757.
When RMON is enabled, the supported RMON groups for Token Ring ports are Mac-Layer Statistics, Promiscuous Statistics, Mac-Layer History, Promiscuous History, Ring Station Order Table, Alarms, and Events, as specified in RFC 1513 and RFC 1757.
Use of this command requires a separate software license.
This example shows how to enable RMON support:
Console> (enable) set snmp rmon enable
SNMP RMON support enabled. Console> (enable)
This example shows how to disable RMON support:
Console> (enable) set snmp rmon disable
SNMP RMON support disabled. Console> (enable)
Use the set snmp trap command to enable or disable the different SNMP traps on the system or to add an entry into the SNMP authentication trap receiver table.
set snmp trap {enable | disable} [all | module | chassis | bridge | repeater | auth | vtp | ippermit | vmps | config | entity | stpx]
enable | Keyword to activate SNMP traps. |
disable | Keyword to deactivate SNMP traps. |
all | (Optional) Keyword to specify all trap types. |
module | (Optional) Keyword to specify the moduleUp and moduleDown traps from the CISCO-STACK-MIB. |
chassis | (Optional) Keyword to specify the chassisAlarmOn and chassisAlarmOff traps from the CISCO-STACK-MIB. |
bridge | (Optional) Keyword to specify the newRoot and topologyChange traps from RFC 1493 (the BRIDGE-MIB). |
repeater | (Optional) Keyword to specify the rptrHealth, rptrGroupChange, and rptrResetEvent traps from RFC 1516 (the SNMP-REPEATER-MIB). |
auth | (Optional) Keyword to specify the authenticationFailure trap from RFC 1157. |
vtp | (Optional) Keyword to specify the VTP from the CISCO-VTP-MIB. |
ippermit | (Optional) Keyword to specify the IP Permit Denied access from the CISCO-STACK-MIB. |
vmps | (Optional) Keyword to specify the vmVmpsChange trap from the CISCO-VLAN-MEMBERSHIP-MIB. |
config | (Optional) Keyword to specify the sysConfigChange trap from the CISCO-STACK-MIB. |
entity | (Optional) Keyword to specify the entityMIB trap from the ENTITY-MIB. |
stpx | (Optional) Keyword to specify the STPX trap. |
rcvr_addr | IP address or IP alias of the system to receive SNMP traps. |
rcvr_community | Community string to use when sending authentication traps. |
The default configuration has SNMP traps disabled.
Switch command.
Privileged.
An IP permit trap is sent when unauthorized access based on the IP permit list is attempted.
Use the show snmp command to verify the appropriate traps were configured.
This example shows how to enable SNMP chassis traps:
Console> (enable) set snmp trap enable chassis
SNMP chassis alarm traps enabled. Console> (enable)
This example shows how to enable all traps:
Console> (enable) set snmp trap enable
All SNMP traps enabled. Console> (enable)
This example shows how to disable SNMP chassis traps:
Console> (enable) set snmp trap disable chassis
SNMP chassis alarm traps disabled. Console> (enable)
This example shows how to add an entry in the SNMP trap receiver table:
Console> (enable) set snmp trap 192.122.173.42 public
SNMP trap receiver added. Console> (enable)
clear ip permit
clear port filter
set ip permit
show ip permit
show port counters
show snmp
test snmp trap
Use the set span command to enable or disable SPAN and to set up the switch port and VLAN analyzer.
set span enable
enable | Keyword to enable SPAN. |
disable | Keyword to disable SPAN. |
src_mod | Monitored module (SPAN source). |
src_ports | Monitored port(s) (SPAN source). |
src_vlan | Monitored VLAN (SPAN source). |
dest_mod | Monitoring module (SPAN destination). |
dest_port | Monitoring port (SPAN destination). |
rx | (Optional) Keyword to specify that information received at the source is monitored. |
tx | (Optional) Keyword to specify that information transmitted from the source is monitored. |
both | (Optional) Keyword to specify that information both transmitted from the source and received at the source is monitored. |
inpkts enable | (Optional) Keywords to enable the receiving of normal inbound traffic on the SPAN destination port. |
inpkts disable | (Optional) Keywords to disable the receiving of normal inbound traffic on the SPAN destination port. |
The default configuration has SPAN port monitoring disabled, port 1/1 as the monitoring port (SPAN destination), VLAN 1 as the monitored VLAN (SPAN source), inbound traffic on the SPAN destination port disabled, and both transmit and receive packets monitored. If the parameter inpkts is not specified, the default is disable. If the parameter rx, tx, or both is not specified, the default is both.
Switch command.
Privileged.
After SPAN is enabled, if no parameters were ever set, system defaults are used. If nondefault parameters are stored in NVRAM, these defaults are used.
Use either a dedicated RMON probe (such as the Catalyst 5000 series Network Analysis Module) or a network analyzer to monitor ports.
If you specify multiple SPAN source ports, the ports must belong to the same VLAN.
Use the inpkts keyword with the enable option to allow the SPAN destination port to receive normal incoming traffic in addition to the traffic mirrored from the SPAN source. Use the disable option to prevent the SPAN destination port from receiving normal incoming traffic.
You can specify an RSM port as the SPAN source port. However, you cannot specify an RSM port as the SPAN destination port.
If you are configuring SPAN on the Catalyst 5000 series Gigabit EtherChannel switching module (WS-X5403), the source and destination ports must be on the same module. This restriction does not apply to the three-port Gigabit Ethernet module (WS-X5403).
The Token Ring destination must have a Token Ring source.
The Token Ring VLAN source must be a TrCRF type.
This example shows how to configure SPAN so that both the transmit traffic and receive traffic on the source port (1/1) is mirrored to the destination port (2/1), and how to verify the SPAN configuration:
Console> (enable) set span 1/1 2/1
Enabled monitoring of Port 1/1 transmit/receive traffic by Port 2/1 Console> (enable) show span
Status : enabled Admin Source : Port 1/1 Oper Source : Port 1/1 Destination : Port 2/1 Direction : transmit/receive Incoming Packets: disabled Console> (enable)
This example shows how to set VLAN 522 as the SPAN source and port 2/1 as the SPAN destination:
Console> (enable) set span 522 2/1
Enabled monitoring of VLAN 522 transmit/receive traffic by Port 2/1 Console> (enable) show span
Status : enabled Admin Source : VLAN 522 Oper Source : Port 3/1-2 Destination : Port 2/1 Direction : transmit/receive Incoming Packets: disabled Console> (enable)
This example shows how to set VLAN 522 as the SPAN source and port 2/12 as the SPAN destination. Only transmit traffic is monitored. Normal incoming packets on the SPAN destination port are allowed.
Console> (enable) set span 522 2/12 tx inpkts enable
SPAN destination port incoming packets enabled. Enabled monitoring of VLAN 522 transmit traffic by Port 2/12 Console> (enable) show span
Status : enabled Admin Source : VLAN 522 Oper Source : Port 2/1-2 Destination : Port 2/12 Direction : transmit Incoming Packets: enabled Console> (enable)
Use the set spantree backbonefast command to enable or disable the spanning-tree Backbone Fast Convergence feature.
set spantree backbonefast {enable | disable}
enable | Keyword to enable Backbone Fast Convergence. |
disable | Keyword to disable Backbone Fast Convergence. |
The default configuration has Backbone Fast Convergence disabled.
Switch command.
Privileged.
Backbone Fast Convergence is not supported on Token Ring VLANs.
For Backbone Fast Convergence to work, you must enable it on all switches in the network.
This example shows how to enable Backbone Fast Convergence:
Console> (enable) set spantree backbonefast enable
Backbonefast enabled for all VLANs. Console> (enable)
Use the set spantree disable command to disable the spanning-tree algorithm for a VLAN or all VLANs.
set spantree disable [vlan] [all]
vlan | (Optional) Number of the VLAN. If the VLAN number is not specified, the default, VLAN 1, is used. |
all | (Optional) Keyword to specify all VLANs. |
The default configuration has all spanning trees enabled.
Switch command.
Privileged.
The all option is supported only on systems configured with a Supervisor Engine III, Supervisor Engine III FSX, or Supervisor Engine III FLX and an NFFC or NFFC II. You can not enable or disable spanning tree on a per VLAN basis.
This example shows how to disable the spanning-tree algorithm for VLAN 1:
Console> (enable) set spantree disable 1
VLAN 1 bridge spanning tree disabled. Console> (enable)
set spantree enable
show spantree
Use the set spantree enable command to enable the spanning-tree algorithm for a VLAN or all VLANs.
set spantree enable [vlan] [all]
vlan | (Optional) Number of the VLAN. If the VLAN number is not specified, the default, VLAN 1, is used. |
all | (Optional) Keyword to specify all VLANs. |
The default configuration has all spanning trees enabled.
Switch command.
Privileged.
The all option is supported only on systems configured with a Supervisor Engine III, Supervisor Engine III FSX, or Supervisor Engine III FLX and an NFFC or NFFC II. You can not enable or disable spanning tree on a per VLAN basis.
This example shows how to activate the spanning-tree algorithm for VLAN 1:
Console> (enable) set spantree enable 1
VLAN 1 bridge spanning tree enabled. Console> (enable)
set spantree disable
show spantree
Use the set spantree fwddelay command to set the bridge forward delay for a VLAN.
set spantree fwddelay delay [vlan]
delay | Number of seconds (4 to 30) for the bridge forward delay. |
vlan | (Optional) Number of the VLAN; if a VLAN number is not specified, VLAN 1 is assumed. |
The default configuration has the bridge forward delay set to 15 seconds for all VLANs.
Switch command.
Privileged.
This example shows how to set the bridge forward delay for VLAN 100 to 16 seconds:
Console> (enable) set spantree fwddelay 16 100
Spantree 100 forward delay set to 16 seconds. Console> (enable)
Use the set spantree hello command to set the bridge hello time for a VLAN.
set spantree hello interval [vlan]
interval | Number of seconds (1 to 10) the system waits before sending a bridge hello message (a multicast message indicating that the system is active). |
vlan | (Optional) Number of the VLAN; if a VLAN number is not specified, VLAN 1 is assumed. |
The default configuration has the bridge hello time set to two seconds for all VLANs.
Switch command.
Privileged.
This example shows how to set the spantree hello time for VLAN 100 to three seconds:
Console> (enable) set spantree hello 3 100
Spantree 100 hello time set to 3 seconds. Console> (enable)
Use the set spantree maxage command to set the bridge maximum aging time for a VLAN.
set spantree maxage agingtime [vlan]
agingtime | Maximum number of seconds (6 to 40) that the system retains the information received from other bridges through Spanning-Tree Protocol. |
vlan | (Optional) Number of the VLAN; if a VLAN number is not specified, VLAN 1 is assumed. |
The default configuration is 20 seconds for all VLANs.
Switch command.
Privileged.
This example shows how to set the maximum aging time for VLAN 1000 to 25 seconds:
Console> (enable) set spantree maxage 25 1000
Spantree 1000 max aging time set to 25 seconds. Console> (enable)
Use the set spantree multicast-address command to specify the bridge functional address instead of the IEEE Spanning-Tree Protocol address when you configure a TrBRF to use the IEEE Spanning-Tree Protocol.
set spantree multicast-address trbrf_num {ieee | ibm}
trbrf_num | Number of the TrBRF for which you are setting the address. |
ieee | Keyword to specify use of the IEEE Spanning-Tree Protocol address. |
ibm | Keyword to specify use of the IBM Spanning-Tree Protocol address. |
The default configuration has IEEE.
Switch command.
Privileged.
This command applies only to Token Ring modules and only to a TrBRF that runs IEEE Spanning-Tree Protocol.
The following example shows how to specify the bridge functional address to be used:
Console> (enable) set spantree multicast-address ibm
Use the set spantree portcost command to set the path cost for a port or TrCRF.
set spantree portcost {mod_num/port_num | trcrf} cost
mod_num | Number of the module. |
port_num | Number of the port on the module. |
trcrf | Number of the TrCRF for which you are setting the path cost. |
cost | Number from 0 to 65535 that indicates the cost of the path; zero (0) is low cost and 65535 is high cost. |
The default configuration is as follows:
10-Gbps module port cost = 2
1-Gbp module port cost = 4
622-Mbps module port cost = 6
155-Mbps module port cost = 14
100-Mbps module port cost = 19
45-Mbps module port cost = 39
16-Mbp module port cost = 80
10-Mbps module port cost = 100
4-Mbps module port cost = 250
10/100-Mbps module port cost = See "Usage Guidelines"
4/16-Mbps module port cost = See "Usage Guidelines"
Switch command.
Privileged.
The Spanning-Tree Protocol uses port path costs to determine which port to select as a forwarding port. You should assign lower numbers to ports attached to faster media (such as full duplex) and higher numbers to ports attached to slower media. The possible range is 0 to 65535.
For 10/100 and 4/16 modules, the default port cost is set automatically depending on the current speed of the port. For example, if a 10/100 port is working at 10 Mbps, the port cost is 100. If the port speed changes to 100 Mbps, the port cost adjusts automatically to 19.
The following example shows how to set the port cost for port 12 on module 2 to 19:
Console> (enable) set spantree portcost 2/12 19
Spantree port 2/12 path cost set to 19. Console> (enable)
Use the set spantree portfast command to allow a port that is connected to a single workstation or PC to start faster when it is connected.
set spantree portfast mod_num/port_num {enable | disable}
mod_num | Number of the module. |
port_num | Number of the port on the module. |
enable | Keyword to enable the spanning-tree port fast-start feature on the port. |
disable | Keyword to disable the spanning-tree port fast-start feature on the port. |
The default configuration has the port fast-start feature disabled.
Switch command.
Privileged.
When a port configured with the spantree portfast enable command is connected, the port immediately enters the spanning-tree forwarding state rather than going through the normal spanning-tree states such as listening and learning. Use this command on ports that are connected to a single workstation or PC only; do not use it on ports that are connected to networking devices such as hubs, routers, switches, bridges, or concentrators.
This example shows how to enable the spanning-tree port fast-start feature on port 2 on module 1:
Console> (enable) set spantree portfast 1/2 enable
Warning: Spantree port fast start should only be enabled on ports connected to a single host. Connecting hubs, concentrators, switches, bridges, etc. to a fast start port can cause temporary spanning tree loops. Use with caution. Spantree port 1/2 fast start enabled. Console> (enable)
Use the set spantree portpri command to set the bridge priority for a spanning-tree port or TrCRF.
set spantree portpri {mod_num/port_num | trcrf} [priority | trcrf_priority]
mod_num | Number of the module. |
port_num | Number of the port on the module. |
trcrf | Keyword to specify the number of the TrCRF for which you are setting the bridge priority. |
priority | (Optional) Number that represents the cost of a link in a spanning-tree bridge. The priority level is from 0 (high) to 63 (low). |
trcrf_priority | (Optional) Number that represents the cost of the TrCRF. The priority level is from 0 (high) to 7 (low). |
The default configuration has all ports with bridge priority set to 32.
Switch command.
Privileged.
The specified bridge priority on an ATM port applies to all emulated LANs on that port.
This example shows how to set the priority of port 1 on module 4 to 63:
Console> (enable) set spantree portpri 4/1 63
Bridge port 4/1 priority set to 63. Console> (enable)
Use the set spantree portstate command to manually set the state of a TrCRF.
set spantree portstate trcrf {block | forward | auto} [trbrf]
trcrf | Number of the TrCRF for which you are manually setting the state. |
block | forward | auto | Keywords to set the TrCRF to a blocked state (block), forwarding state (forward), or to have the Spanning-Tree Protocol determine the correct state automatically (auto). |
trbrf | (Optional) Number of the parent TrBRF. |
There is no default configuration for this command.
Switch command.
Privileged.
Use this command only to set the port state when the TrCRF is in SRT mode and the TrBRF is running the IBM Spanning-Tree Protocol, or the TrCRF is in SRB mode and the TrBRF is running the IEEE Spanning-Tree Protocol.
When you enable Spanning-Tree Protocol, every switch in the network goes through the blocking state and the transitory states of listening and learning at power up. If properly configured, the ports then stabilize to the forwarding or blocking state. However, with TrBRFs and TrCRFs, there are two exceptions to this rule that require you to manually set the state of the logical ports of a TrBRF:
If either condition exists, use the set spantree portstate command to manually set the state of a TrCRF to blocked or forwarding mode or set the Spanning-Tree Protocol to determine the correct state automatically.
This example shows the manual setting of TrCRF 900 to a forwarding state:
Console> (enable) set spantree portstate 900 forward
reserve_nvram : requested by block = 0 reserve_nvram : granted to block = 0 release_nvram : releasing block = 0 Console> (enable)
show spantree
show spantree portstate
Use the set spantree portvlancost command to assign a lower path cost to a set of VLANs on a port.
set spantree portvlancost mod_num/port_num [cost cost] [vlan_list]
mod_num | Number of the module. |
port_num | Number of the port. |
cost cost | (Optional) Keyword to indicate the path cost. The portvlancost applies only to trunk ports. |
vlan_list | (Optional) If you do not list a VLAN explicitly, the VLANs listed in prior invocations of this command are affected. If no cost is listed explicitly, and previous cost values are specified in prior invocations, then the portvlancost is set to 1 less than the current port cost for a port. However, this may not assure load balancing in all cases. |
The value specified is used as the path cost of the port for the specified set of VLANs. The rest of the VLANs have a path cost equal to the port path cost, set via the set spantree portcost command (if not set, the value is the default path cost of the port).
Switch command.
Privileged.
These examples show various ways to use the set spantree portvlancost command:
Console> (enable) set spantree portvlancost 2/10 cost 25 1-20
Cannot set portvlancost to a higher value than the port cost, 10, for port 2/10. Console> (enable) Console> (enable) set spantree portvlancost 2/10 1-20
Port 2/10 VLANs 1-20 have a path cost of 9. Console> (enable) Console> (enable) set spantree portvlancost 2/10 cost 4 1-20
Port 2/10 VLANs 1-20 have path cost 4. Port 2/10 VLANs 21-1000 have path cost 10. Console> (enable) Console> (enable) set spantree portvlancost 2/10 cost 6 21
Port 2/10 VLANs 1-21 have path cost 6. Port 2/10 VLANs 22-1000 have path cost 10. Console> (enable)
These examples show how to use the set spantree portvlancost command without explicitly specifying cost:
Console> (enable) set spantree portvlancost 1/2
Port 1/2 VLANs 1-1005 have path cost 3100. Console> (enable) Console> (enable) set spantree portvlancost 1/2 21
Port 1/2 VLANs 1-20,22-1005 have path cost 3100. Port 1/2 VLANs 21 have path cost 3099. Console> (enable)
Use the set spantree portvlanpri command to set the port priority for a subset of VLANs in the trunk port.
set spantree portvlanpri mod_num/port_num priority [vlans]
mod_num | Number of the module. |
port_num | Number of the port. |
priority | Number that represents the cost of a link in a spanning-tree bridge. The priority level is from 0 to 63, with 0 indicating high priority and 63 indicating low priority. |
vlans | (Optional) VLANs that use the specified priority level. |
The default configuration has the port VLAN priority set to 0, with no VLANs specified.
Switch command.
Privileged.
Use this command to add VLANs to a specified port priority level. Subsequent calls to this command do not replace VLANs that are already set at a specified port priority level.
This feature is not supported for the RSM.
The set spantree portvlanpri command applies only to trunk ports. Do not use Token Ring ports as trunk ports. If you enter this command, you see this message:
Port xx is not a trunk-capable port
This example shows how to set the port priority for module 1, port 2, on VLANs 21 to 40:
Console> (enable) set spantree portvlanpri 1/2 16 21-40
Port 1/2 vlans 3,6-20,41-1000 using portpri 32 Port 1/2 vlans 1-2,4-5,21-40 using portpri 16 Console> (enable)
clear spantree portvlancost
show spantree
Use the set spantree priority command to set the bridge priority for a VLAN.
set spantree priority bridge_priority [vlan]
bridge_priority | Number representing the priority of the bridge. The priority level is from 0 to 65535, with 0 indicating high priority and 65535 indicating low priority. |
vlan | (Optional) Number of the VLAN. If you do not specify a VLAN number, VLAN 1 is used. |
The default configuration has the bridge priority set to 32768.
Switch command.
Privileged.
This feature is not supported for the RSM.
This example shows how to set the bridge priority of VLAN 1 to 4096:
Console> (enable) set spantree priority 4096
VLAN 1 bridge priority set to 4096. Console> (enable)
Use the set spantree root command to set the primary or secondary root for specific VLANs or for all VLANs of the switch.
set spantree root [secondary] [vlan_list] [dia network_diameter]
secondary | (Optional) Keyword to designate this switch as a secondary root, should the primary root fail. |
vlan_list | (Optional) Number of the VLAN. If you do not specify a VLAN number, VLAN 1 is used. |
dia network_diameter | (Optional) Keyword to specify the maximum number of bridges between any two points of attachment of end stations. Valid values of network diameter are 1 through 7. |
hello hello_time | (Optional) Keyword to specify in seconds, the duration between generation of configuration messages by the root switch. |
If the secondary keyword is not specified, the default is to make the switch the primary root.
The default value of the network diameter is 7.
If not specified, the current value of hello_time from the NVRAM is used.
This command is run on backbone or distribution switches.
You can run the secondary root many times, to create backup switches in case of a root failure.
The secondary command reduces the bridge priority value to 16384.
This command increases path costs to a value greater than 3000.
Switch command.
Privileged.
This example shows how to use the set spantree root command:
Console>(enable) set spantree root 1-10 dia 4
VLANs 1-10 bridge priority set to 8192 VLANs 1-10 bridge max aging time set to 14 seconds. VLANs 1-10 bridge hello time set to 2 seconds. VLANs 1-10 bridge forward delay set to 9 seconds. Switch is now the root switch for active VLANs 1-6. Console> (enable)
This example shows that setting the bridge priority to 8192 was not sufficient to make this switch the root. So, the priority was further reduced to 7192 (100 less than the current root switch) to make this switch the root switch. However, reducing it to this value did not make it the root switch for active VLANs 16 and 17.
Console>(enable) set spantree root 11-20.
VLANs 11-20 bridge priority set to 7192 VLANs 11-10 bridge max aging time set to 20 seconds. VLANs 1-10 bridge hello time set to 2 seconds. VLANs 1-10 bridge forward delay set to 13 seconds. Switch is now the root switch for active VLANs 11-15,18-20. Switch could not become root switch for active VLAN 16-17. Console> (enable) Console>(enable) set spantree root secondary 22,24 dia 5 hello 1
VLANs 22,24 bridge priority set to 16384. VLANs 22,24 bridge max aging time set to 10 seconds. VLANs 22,24 bridge hello time set to 1 second. VLANs 22,24 bridge forward delay set to 7 seconds. Console> (enable)
Use the set spantree uplinkfast command to enable fast switchover to alternate ports when the root port fails. This command applies to a switch, not to a WAN.
set spantree uplinkfast {enable | disable} [rate station_update_rate] [all-protocols off | on]
enable | Keyword to enable fast switchover. |
disable | Keyword to disable fast switchover. |
rate | (Optional) Keyword to specify the number of multicast packets transmitted per 100 ms when an alternate port is chosen after the root port goes down. |
station_update_rate | (Optional) Number of multicast packets transmitted per 100 ms when an alternate port is chosen after the root port goes down. |
all-protocols | (Optional) Keyword to specify whether or not to generate multicast packets for all protocols (IP, IPX, Appletalk, and Layer 2 packets). |
off | (Optional) Keyword to turn off the all-protocols feature. |
on | (Optional) Keyword to turn on the all-protocols feature. |
The default station_update_rate is 15 packets per 100 ms.
Switch command.
Privileged.
The set spantree uplinkfast enable command has the following results:
If you run set spantree uplinkfast enable on a switch that has this feature already enabled, only the station update rate is updated. The rest of the parameters are not modified.
If you run set spantree uplinkfast disable on a switch, the uplinkfast feature is disabled but the switch priority and port cost values are not reset to the factory defaults. To reset the values to the factory defaults, enter the clear spantree uplinkfast command.
The default station_update_rate value is 15 packets per 100 ms, which is equivalent to a 1 percent load on a 10-Mbps Ethernet port. If you specify this value as 0, the switch does not generate station-update-rate packets.
You do not have to turn on the all-protocols feature on Catalyst 5000 series switches that have both the uplinkfast and protocol filtering features enabled. The all-protocols feature should be used only on Catalyst 5000 series switches that have uplinkfast enabled but do not have protocol filtering enabled, and that have upstream switches in the network using protocol filtering enabled. Since the switch with uplinkfast does not have protocol filtering, you must enter the all-protocols option to inform the uplinkfast feature whether or not to generate multicast packets for all protocols.
This example shows how to enable spantree uplinkfast and specify the number of multicast packets transmitted to 40 packets per 100 ms:
Console>(enable) set spantree uplinkfast enable rate 40
VLANs 1-1000 bridge priority set to 49152. The port cost and portvlancost of all ports increased to above 3000. Station update rate set to 40 packets/100ms. uplinkfast turned on for bridge. Console> (enable)
This example shows how to disable the spantree uplinkfast feature:
console> (enable) set spantree uplinkfast disable
Uplinkfast disabled for switch. Use clear spantree uplinkfast to return stp parameters to default. console>(enable) clear spantree uplink This command will cause all portcosts, portvlancosts, and the bridge priority on all vlans to be set to default. Do you want to continue (y/n) [n]? y VLANs 1-1005 bridge priority set to 32768. The port cost of all bridge ports set to default value. The portvlancost of all bridge ports set to default value. uplinkfast disabled for bridge. Console> (enable)
This example shows how to turn on the all-protocols feature:
Console> (enable) set spantree uplinkfast enable all-protocols on
uplinkfast update packets enabled for all protocols. uplinkfast already enabled for bridge. Console> (enable)
This example shows how to turn off the all-protocols feature:
Console> (enable) set spantree uplinkfast enable all-protocols off
uplinkfast all-protocols field set to off. uplinkfast already enabled for bridge. Console> (enable)
Use the set standbyports command to enable or disable the standby ports feature. The standby ports feature allows the ports on the standby supervisor engine module to pass traffic. If this feature is disabled, the ports are in standby mode.
set standbyports enable | disable
enable | Keyword to enable the standby ports feature. |
disable | Keyword to disable the standby ports feature. |
The default is disabled. However, if upgrading from supervisor engine software release 4.1 or 4.2, the standby ports feature remains enabled.
Switch command.
Privileged.
This example shows how to enable the standby ports feature:
Console> (enable) set standbyports enable
Standby ports feature enabled. Please wait while the standby ports are coming up. Console> (enable)
This example shows how to disable the standby ports feature:
Console> (enable) set standbyports disable
Standby ports feature disabled. Console> (enable)
|
|