Table Of Contents

rcv-queue cos-map

rcv-queue queue-limit

rcv-queue random-detect

rcv-queue threshold

redundancy

redundancy force-switchover

reload

remote command

remote login

remote-span

reset

retry

revision

rmon alarm

rmon event

scheduler allocate

service counters max age

service-policy input

session slot

set ip dscp

set ip precedence (policy-map)

show

show adjacency

show arp

show asic-version

show bootflash:

22

rcv-queue cos-map

To map CoS values to the standard receive-queue drop thresholds, use the rcv-queue cos-map command. Use the no form of this command to remove the mapping.

rcv-queue cos-map queue-id threshold-id cos-1 ... cos-n

no rcv-queue cos-map queue-id threshold-id

Syntax Description

queue-id	Queue ID; the valid value is 1.
threshold-id	Threshold ID; valid values are from 1 to 4.
cos-1 ... cos-n	CoS values; valid values are from 0 to 7.

Defaults

The defaults are as follows:

queue	threshold	cos-map	queue	threshold	cos-map
With QoS Disabled			With QoS Enabled
1	1	0,1, 2,3,4,5,6,7	1	1	0,1
1	2		1	2	2,3
1	3		1	3	4
1	4		1	4	6,7
2	1	5	2	1	5

Command Modes

Interface configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(19)E1	This command was changed to support the 1q2t ingress LAN interface.

Usage Guidelines

The cos-n value is defined by the module and port type. When you enter the cos-n value, note that the higher values indicate higher priorities.

This command is effective on trusted ports only.

Always set threshold 2 on a 1q2t ingress LAN port to 100 percent.

Examples

This example shows how to map the CoS values 0 and 1 to threshold 1 in the standard receive queue:

Router (config-if)# rcv-queue cos-map 1 1 0 1

  cos-map configured on:  Gi1/1 Gi1/2

Router(config-if)#

Related Commands

show queueing interface

rcv-queue queue-limit

To set the size ratio between the strict-priority and standard receive queues, use the rcv-queue queue-limit command. Use the no form of this command to return to the default settings.

rcv-queue queue-limit {q-limit-1} {q-limit-2}

no rcv-queue queue-limit

Syntax Description

q-limit-1	Standard queue weight; valid values are from 1 and 100 percent.
q-limit-2	Strict-priority queue weight; see the "Usage Guidelines" section for valid values.

Defaults

The defaults are as follows:

•80 percent for low priority

•20 percent for strict priority

Command Modes

Interface configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(8a)EX	The acceptable minimum value of the strict-priority queue weight changed.

Usage Guidelines

Valid strict-priority weight values are from 1 to 100 percent, except on 1p1q8t ingress LAN ports, where valid values for the strict-priority queue are from 3 to 100 percent.

The rcv-queue queue-limit command configures ports on a per-ASIC basis.

Estimate the mix of strict-priority-to-standard traffic on your network (for example, 80-percent standard traffic and 20-percent strict-priority traffic) and use the estimated percentages as queue weights.

Examples

This example shows how to set the receive-queue size ratio for Gigabit Ethernet interface 1/2:

Router# configure terminal 

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# interface gigabitethernet 1/2 

Router(config-if)# rcv-queue queue-limit 75 15 

Router(config-if)# end 

Router# 

Related Commands

show queueing interface

rcv-queue random-detect

To specify the minimum and maximum threshold for the specified receive queues on 1q4t, 1p1q4t, and 1p1q0t interfaces, use the rcv-queue random-detect command. Use the no form of this command to return to the default settings.

rcv-queue random-detect {max-threshold | min-threshold} queue-id threshold-percent-1 ... threshold-percent-n

no rcv-queue random-detect {max-threshold | min-threshold} queue-id

Syntax Description

max-threshold	Specifies the maximum threshold.
min-threshold	Specifies the minimum threshold.
queue-id	Queue ID; the valid value is 1.
threshold-percent-1 threshold-percent-n	Threshold weights; valid values are from 1 to 100 percent.

Defaults

If you disable QoS, the default is that all thresholds are set to 100 percent.

If you enable QoS, the following default thresholds apply:

•1q4t ingress LAN interfaces have this default drop-threshold configuration:

–Using receive-queue drop threshold 1, the Catalyst 6500 series switch drops incoming frames with CoS 0 or 1 when the receive-queue buffer is 50 percent or more full.

–Using receive-queue drop threshold 2, the Catalyst 6500 series switch drops incoming frames with CoS 2 or 3 when the receive-queue buffer is 60 percent or more full.

–Using receive-queue drop threshold 3, the Catalyst 6500 series switch drops incoming frames with CoS 4 or 5 when the receive-queue buffer is 80 percent or more full.

–Using receive-queue drop threshold 4, the Catalyst 6500 series switch drops incoming frames with CoS 6 or 7 when the receive-queue buffer is 100 percent full.

•1p1q4t ingress LAN interfaces have this default drop-threshold configuration:

–Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the standard receive queue.

–Using standard receive-queue drop threshold 1, the Catalyst 6500 series switch drops incoming frames with CoS 0 or 1 when the receive-queue buffer is 50 percent or more full.

–Using standard receive-queue drop threshold 2, the Catalyst 6500 series switch drops incoming frames with CoS 2 or 3 when the receive-queue buffer is 60 percent or more full.

–Using standard receive-queue drop threshold 3, the Catalyst 6500 series switch drops incoming frames with CoS 4 when the receive-queue buffer is 80 percent or more full.

–Using standard receive-queue drop threshold 4, the Catalyst 6500 series switch drops incoming frames with CoS 6 or 7 when the receive-queue buffer is 100 percent full.

–Frames with CoS 5 go to the strict-priority receive queue (queue 2), where the Catalyst 6500 series switch drops incoming frames only when the strict-priority receive-queue buffer is 100 percent full.

•1p1q0t ingress LAN interfaces have this default drop-threshold configuration:

–Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the standard receive queue. The Catalyst 6500 series switch drops incoming frames when the receive-queue buffer is 100 percent full.

–Frames with CoS 5 go to the strict-priority receive queue (queue 2), where the Catalyst 6500 series switch drops incoming frames only when the strict-priority receive-queue buffer is 100 percent full.

Command Modes

Interface configuration

Command History

Release	Modification
12.1(8a)EX	Support for this command was introduced on the Supervisor Engine 2.

Usage Guidelines

The 1q4t interface indicates one standard queue with four thresholds. The 1p1q4t interface indicates one strict-priority queue and one standard queue with four thresholds. The 1p1q0t interface indicates one strict-priority queue and one standard queue with no configurable threshold (effectively, a tail-drop threshold at 100 percent).

The threshold in the strict-priority queue is not configurable.

Each threshold has a low and a high threshold value.

The threshold values are a percentage of the receive-queue capacity.

For additional information on configuring receive-queue thresholds, refer to the QoS chapter in the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide.

Examples

This example shows how to configure the low-priority receive-queue thresholds:

Router (config-if)# rcv-queue random-detect max-threshold 1 60 100

Router (config-if)# 

Related Commands

show queueing interface

rcv-queue threshold

To configure drop-threshold percentages for the standard receive queues on 1p1q4t and 1p1q0t interfaces, use the rcv-queue threshold command. Use the no form of this command to return thresholds to the default settings.

rcv-queue threshold queue-id threshold-percent-1 ... threshold-percent-n

no rcv-queue threshold

Syntax Description

queue-id	Queue ID; the valid value is 1.
threshold- percent-1 ... threshold- percent-n	Threshold ID; valid values are from 1 to 100 percent.

Defaults

The defaults for the 1p1q4t and 1p1q0t configurations are as follows:

•QoS assigns all traffic with CoS 5 to the strict-priority queue.

•QoS assigns all other traffic to the standard queue.

The default for the 1q4t and 1q2t configurations is that QoS assigns all traffic to the standard queue.

If you enable QoS, the following default thresholds apply:

•1p1q4t interfaces have this default drop-threshold configuration:

–Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the standard receive queue.

–Using standard receive-queue drop threshold 1, the Catalyst 6500 series switch drops incoming frames with CoS 0 or 1 when the receive-queue buffer is 50 percent or more full.

–Using standard receive-queue drop threshold 2, the Catalyst 6500 series switch drops incoming frames with CoS 2 or 3 when the receive-queue buffer is 60 percent or more full.

–Using standard receive-queue drop threshold 3, the Catalyst 6500 series switch drops incoming frames with CoS 4 when the receive-queue buffer is 80 percent or more full.

–Using standard receive-queue drop threshold 4, the Catalyst 6500 series switch drops incoming frames with CoS 6 or 7 when the receive-queue buffer is 100 percent full.

–Frames with CoS 5 go to the strict-priority receive queue (queue 2), where the Catalyst 6500 series switch drops incoming frames only when the strict-priority receive-queue buffer is 100 percent full.

•1p1q0t interfaces have this default drop-threshold configuration:

–Frames with CoS 0, 1, 2, 3, 4, 6, or 7 go to the standard receive queue. The Catalyst 6500 series switch drops incoming frames when the receive-queue buffer is 100 percent full.

–Frames with CoS 5 go to the strict-priority receive queue (queue 2), where the Catalyst 6500 series switch drops incoming frames only when the strict-priority receive-queue buffer is 100 percent full.

•1q2t interfaces have this default drop-threshold configuration:

–Frames with CoS 0, 1, 2, 3, 4, 5, 6, or 7 go to the standard receive queue.

–Using standard receive-queue drop threshold 1, the Catalyst 6500 series switch drops incoming frames with CoS 0, 1, 2, 3, or 4 when the receive-queue buffer is 80 percent or more full.

–Using standard receive-queue drop threshold 2, the Catalyst 6500 series switch drops incoming frames with CoS 5, 6, or 7 when the receive-queue buffer is 100 percent or more full.

---

Note The 100-percent threshold may be actually changed by the module to 98 percent to allow BPDU traffic to proceed. The BPDU threshold is factory set at 100 percent.

---

Command Modes

Interface configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(5c)EX	This command was changed to support the 1p1q0t interface.
12.1(19)E1	This command was changed to support the 1q2t ingress LAN interface.

Usage Guidelines

The queue-id value is always 1.

A value of 10 indicates a threshold when the buffer is 10 percent full.

Always set threshold 4 to 100 percent.

Always set threshold 2 on a 1q2t ingress LAN port to 100 percent.

Receive thresholds take effect only on ports whose trust state is trust cos.

Configure the 1q4t receive-queue tail-drop threshold percentages with the wrr-queue threshold command.

Examples

This example shows how to configure the receive-queue drop thresholds for Gigabit Ethernet interface 1/1:

Router(config-if)# rcv-queue threshold 1 60 75 85 100 

Router(config-if)# 

Related Commands

show queueing interface
wrr-queue threshold

redundancy

To enter redundancy configuration mode, use the redundancy command. From this mode, you can enter the main CPU submode to manually synchronize the configurations that are used by the two supervisor engines.

redundancy

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Global configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

After you are in redundancy mode, you can enter the main CPU submode. From this mode, you can use the auto-sync command to use all of the redundancy commands applicable to the main CPU.

Examples

This example shows how to enter redundancy mode:

Router (config)# redundancy

Router(config-r)#

This example shows how to enter the main CPU submode:

Router (config)# redundancy

Router (config-r)# main-cpu

Router (config-r-mc)# 

Related Commands

auto-sync

redundancy force-switchover

To force a switchover from the active to the standby supervisor engine, use the redundancy force-switchover command.

redundancy force-switchover

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(11b)EX	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(13)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

Before using this command, refer to the "Performing a Fast Software Upgrade (FSU)" section of the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide for additional information.

The redundancy force-switchover command conducts a manual switchover to the redundant supervisor engine. The redundant supervisor engine becomes the new active supervisor engine running the new Cisco IOS image. The modules are reset and the module software is downloaded from the new active supervisor engine.

The active and redundant supervisor engines do not reset on an RPR+ switchover.

The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine.

Examples

This example shows how to switch over manually from the active to the standby supervisor engine:

Router# redundancy force-switchover

Router# 

Related Commands

mode
redundancy
show redundancy

reload

To reload the entire Catalyst 6500 series switch, use the reload command.

reload [text | in [hh:]mm [text] | at hh:mm [month day | day month] [text] | cancel]

Syntax Description

text	(Optional) Reason for the reload; the string can be from 1 to 255 characters.
in [hh:]mm	(Optional) Delays a Catalyst 6500 series switch reload for a specific amount of time.
at hh:mm	(Optional) Schedules a Catalyst 6500 series switch reload to take place at the specified time (using a 24-hour clock).
month	(Optional) Name of the month; any number of characters in a unique string.
day	(Optional) Number of the day; valid values are from 1 to 31.
cancel	(Optional) Cancels a scheduled reload.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(11b)EX	This command was changed from reloading the supervisor engine only to reloading the entire Catalyst 6500 series switch.

Usage Guidelines

The reload command halts the system. If the system is set to restart on error, it reboots itself. Use the reload command after configuration information is entered into a file and saved to the startup configuration.

When you schedule a reload to occur at a later time (using the in keyword), it must take place within approximately 24 days.

When specifying the reload time (using the at keyword), if you specify the month and day, the reload takes place at the specified time and date. If you do not specify the month and day, the reload takes place at the specified time on the current day (if the specified time is later than the current time), or on the next day (if the specified time is earlier than the current time). Specifying 00:00 schedules the reload for midnight. The reload must take place within approximately 24 days.

If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you say "yes" in this situation, the system goes to setup mode upon reload.

You can use the at keyword if the system clock has been set on the MSM (either through NTP, the hardware calendar, or manually). The time is relative to the configured time zone on the MSM. To schedule reloads across several MSMs to occur simultaneously, you must synchronize the time on each MSM with NTP.

To display information about a scheduled reload, use the show reload command.

Examples

This example shows how to reload the Catalyst 6500 series switch immediately:

Router# reload

Router#

This example shows how to reload the Catalyst 6500 series switch in 10 minutes:

Router# reload in 10

Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)

Proceed with reload? [confirm]

Router#

This example shows how to reload the Catalyst 6500 series switch at 1:00 p.m. today:

Router# reload at 13:00

Router# Reload scheduled for 13:00:00 PDT Fri Apr 21 1996 (in 1 hour and 2 minutes)

Proceed with reload? [confirm]

Router#

This example shows how to reload the Catalyst 6500 series switch on April 20 at 2:00 a.m.:

Router# reload at 02:00 apr 20

Router# Reload scheduled for 02:00:00 PDT Sat Apr 20 1996 (in 38 hours and 9 minutes)

Proceed with reload? [confirm]

Router#

This example shows how to cancel a pending reload:

Router# reload cancel

%Reload cancelled.

Router#

Related Commands

copy system:running-config nvram:startup-config (refer to the Cisco IOS Release 12.1 Command Reference)
show reload (refer to the Cisco IOS Release 12.1 Command Reference)

remote command

To execute a Catalyst 6500 series switch command directly on the switch console or a specified module without having to log into the Catalyst 6500 series switch first, use the remote command command.

remote command {module mod} | switch} command

Syntax Description

module mod	Specifies the module; see the "Usage Guidelines" section for valid values.
switch	Specifies the switch console.
command	Command to be executed.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(5c)EX	The switch and module num keywords and arguments were added to support DFC-equipped modules.

Usage Guidelines

The module num keyword and argument designate the module and port number. Valid values depend on the chassis and module used. For example, if you have a 48-port 10/100BASE-T Ethernet module installed in a 13-slot chassis, valid values for the module number are from 2 to 13 and valid values for the port number are from 1 to 48.

When you execute the remote command switch command, the prompt changes to Switch-sp#.

This command is supported on DFC-equipped modules and the supervisor engine only.

This command does not support command completion, but you can use shortened forms of the command (for example, entering sh for show).

Examples

This example shows how to execute the Catalyst 6500 series switch command from the route processor:

Router# remote command switch show calendar

Switch-sp#

09:52:50 UTC Mon Nov 12 2001

Router#                               

Related Commands

remote login

remote login

To access the Catalyst 6500 series switch console or a specific module, use the remote login command.

remote login {module num | switch}

Syntax Description

module num	Specifies the module to access; see the "Usage Guidelines" section for valid values.
switch	Accesses the Catalyst 6500 series switch console.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(5c)EX	The switch and module num keywords and argument were added.

Usage Guidelines

---

Caution When you enter the attach or remote login command to access another console from your switch, if you enter global or interface configuration mode commands, the switch might reset.

---

The module num keyword and argument designate the module number. Valid values depend on the chassis used. For example, if you have a 13-slot chassis, valid values are from 1 to 13.

This command is supported on DFC-equipped modules and the supervisor engine only.

When you execute the remote login module num command, the prompt changes to Router-dfcx# or Switch-sp#, depending on the type of module to which you are connecting.

The remote login module num command is identical to the attach command.

There are two ways to end the session:

•You can enter the exit command as follows:

Switch-sp# exit

[Connection to Switch closed by foreign host]

Router#

•You can press Ctrl-C three times as follows:

Switch-sp# ^C

Switch-sp# ^C

Switch-sp# ^C

Terminate remote login session? [confirm] y

[Connection to Switch closed by local host]

Router#

Examples

This example shows how to perform a remote login to a specific module:

Router# remote login module 1

Trying Switch ...

Entering CONSOLE for Switch

Type "^C^C^C" to end this session

Switch-sp#

This example shows how to perform a remote login to the Catalyst 6500 series switch console:

Router# remote login switch

Trying Switch ...

Entering CONSOLE for Switch

Type "^C^C^C" to end this session

Switch-sp# 

Related Commands

attach

remote-span

To configure a VLAN as an RSPAN VLAN, use the remote-span command. Use the no form of this command to remove the RSPAN designation.

remote-span

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default settings.

Command Modes

config-VLAN

Command History

Release	Modification
12.1(13)E	Support for this command was introduced on the Catalyst 6500 series switches.

Usage Guidelines

This command is not supported in the VLAN database mode.

You can enter the show vlan remote-span command to display the RSPAN VLANs in the Catalyst 6500 series switch.

Examples

This example shows how to configure a VLAN as an RSPAN VLAN:

Router(config-vlan)# remote-span

Router(config-vlan)

This example shows how to remove the RSPAN designation:

Router(config-vlan)# no remote-span

Router(config-vlan)

Related Commands

show vlan remote-span

reset

To leave the proposed new VLAN database, remain in VLAN configuration mode, and reset the proposed new database so that it is identical to the current VLAN database, use the reset command.

reset

Syntax Description

This command has no keywords or arguments.

Defaults

This command has no default settings.

Command Modes

VLAN configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to cause the proposed new VLAN database to be abandoned and reset to the current VLAN database:

Router(vlan)# reset

RESET completed.

Router(vlan)#         

retry

To define the amount of time that must elapse before a connection is attempted to a failed server, use the retry command. Use the no form of this command to change the connection reassignment threshold and client threshold to the default settings.

retry retry-value

no retry

Syntax Description

retry-value

Amount of time, in seconds, that must elapse after the detection of a server failure before a new connection is attempted to the server; valid values are from 1 to 3600.

Defaults

retry-value is 60.

Command Modes

Real server configuration submode

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Examples

This example shows how to define the retry timer:

Router(config-if)# retry 145

Router(config-if)#

This example shows how to revert to the default settings:

Router(config-if)# no retry

Router(config-if)#

Related Commands

faildetect numconns (refer to the Cisco IOS Release 12.1 Command Reference)
inservice (refer to the Cisco IOS Release 12.1 Command Reference)
maxconns (real server configuration submode)

revision

To set the MST configuration revision number, use the revision command. Use the no form of this command to return to the default settings.

revision version

no revision

Syntax Description

version

Configuration revision number; valid values are from 0 to 65535.

Defaults

version is 0.

Command Modes

MST configuration submode

Command History

Release	Modification
12.1(11b)EX	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(13)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

Two Catalyst 6500 series switches that have the same configuration but different configuration revision numbers are considered to be part of two different regions.

---

Caution Be careful when using the revision command to set the MST configuration revision number because a mistake would put the switch in a different region.

---

Examples

This example shows how to set the configuration revision number:

Router(config-mst)# revision 5

Router(config-mst)# 

Related Commands

instance
name
show
show spanning-tree
spanning-tree mst configuration

rmon alarm

To set an alarm on any MIB object, use the rmon alarm command. Use the no form of this command to disable the alarm.

rmon alarm number variable interval {delta | absolute} rising-threshold value [event-number] falling-threshold value [event-number] [owner string]

no rmon alarm number

Syntax Description

number	Alarm number that is identical to the alarmIndex in the alarmTable in the RMON MIB; valid values are from 1 to 65535.
variable	MIB object to monitor; this value translates into the alarmVariable used in the alarmTable of the RMON MIB.
interval	Time in seconds that the alarm monitors the MIB variable. This value is identical to the alarmInterval used in the alarmTable of the RMON MIB; valid values are from 1 to 4294967295.
delta	Specifies the change between MIB variables; this value affects the alarmSampleType in the alarmTable of the RMON MIB.
absolute	Specifies each MIB variable directly; this value affects the alarmSampleType in the alarmTable of the RMON MIB.
rising-threshold value	Specifies the value at which the alarm is triggered; valid values are from -2147483648 to 2147483647.
event-number	(Optional) Event number to trigger when the rising or falling threshold exceeds its limit. This value is identical to the alarmRisingEventIndex or the alarmFallingEventIndex in the alarmTable of the RMON MIB; valid values are from 1 to 65535.
falling-threshold value	Specifies the value at which the alarm is reset; valid values are from -2147483648 to 2147483647.
owner string	(Optional) Specifies the owner for the alarm; this value is identical to the alarmOwner in the alarmTable of the RMON MIB.

Defaults

No alarms are configured.

Command Modes

Global configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

You must specify the MIB object as a dotted decimal value after the entry sequence (for example, ifEntry.10.1). You cannot specify the variable name and the instance (for example, ifInOctets.1) or the entire dotted decimal notation. The variable must be of the form entry integer.instance.

To disable the RMON alarms, you must use the no form of the command on each configured alarm. For example, enter the no rmon alarm 1 command, where the 1 identifies which alarm is to be removed.

Refer to RFC 1757 for more information about the RMON alarm group.

Examples

This example shows how to configure an RMON alarm using the rmon alarm command:

Router(config)# rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1 
falling-threshold 0

     owner jjohnson

This example shows how to configure an RMON alarm number 10. The alarm monitors the MIB variable ifEntry.20.1 once every 20 seconds until the alarm is disabled and checks the change in the variable's rise or fall. If the ifEntry.20.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. Possible events include a log entry or SNMP trap. If the ifEntry.20.1 value changes by 0 (falling-threshold 0), the alarm is reset and can be triggered again.

Related Commands

rmon (refer to the Cisco IOS Release 12.1 Command Reference)
rmon event
show rmon (refer to the Cisco IOS Release 12.1 Command Reference)

rmon event

To add or remove an event in the RMON event table that is associated with an RMON event number, use the rmon event command. Use the no form of this command to disable RMON on the interface.

rmon event number [log] [trap community] [description string] [owner string]

no rmon event number

Syntax Description

number	Assigned event number that is identical to the eventIndex in the eventTable in the RMON MIB; valid values are from 1 to 65535.
log	(Optional) Generates an RMON log entry when the event is triggered and sets the eventType in the RMON MIB to log or log-and-trap.
trap community	(Optional) Specifies the SNMP community string that is used for this trap.
description string	(Optional) Specifies a description of the event that is identical to the event description in the eventTable of the RMON MIB.
owner string	(Optional) Specifies the owner of this event that is identical to the eventOwner in the eventTable of the RMON MIB.

Defaults

No alarms are configured.

Command Modes

Global configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

Refer to RFC 1757 for more information about the RMON MIB.

Use the trap community option to configure the setting of the eventType in the RMON MIB for this row as either snmp-trap or log-and-trap. This value is identical to the eventCommunityValue in the eventTable in the RMON MIB.

Examples

This example shows how to enable the rmon event command:

Router(config)# rmon event 1 log trap eventtrap description "High ifOutErrors" owner 
sdurham 

This example configuration creates RMON event number 1, which is defined as High ifOutErrors, and generates a log entry when the event is triggered by an alarm. The user sdurham owns the row that is created in the event table by this command. This configuration also generates an SNMP trap when the event is triggered.

Related Commands

rmon (refer to the Cisco IOS Release 12.1 Command Reference)
rmon alarm
show rmon (refer to the Cisco IOS Release 12.1 Command Reference)

scheduler allocate

To guarantee CPU time for process tasks, use the scheduler allocate command. Use the no form of this command to return to the default settings.

scheduler allocate interrupt-time process-time

no scheduler allocate

Syntax Description

interrupt-time	Integer (in microseconds) that limits the maximum number of microseconds to spend on fast switching within any one network interrupt context; valid values are from 400 to 60000 microseconds.
process-time	Integer (in microseconds) that guarantees the minimum number of microseconds to spend at the process level when network interrupts are disabled; valid values are from 100 to 4000.

Defaults

The defaults are as follows:

•interrupt-time is 4000 microseconds

•process-time is 800 microseconds

Command Modes

Global configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.
12.1(13)E10	This command was changed as follows: •The process-time default setting was changed from 200 microseconds to 800 microseconds. •The no scheduler allocate action was changed to return to the default settings.
12.1(20)E	The changes noted in Release 12.1(13)E10 do not apply to Releases 12.1(14)E, 12.1(19)E1, and 12.1(19)E1. In these releases, the following apply: •The process-time default setting is 200 microseconds. •The no scheduler allocate command disables interrupt throttling.

Usage Guidelines

---

Caution We recommend that you do not change the default values.

---

Entering the scheduler allocate command without arguments is the same as entering the no scheduler allocate or the default scheduler allocate command.

Examples

This example shows how to make 20 percent of the CPU available for process tasks:

Router-config# scheduler allocate 2000 500

Router-config#

service counters max age

To set the statistics retrieval time, use the service counters max age command. Use the no form of this command to return to the default settings.

service counters max age seconds

Syntax Description

seconds

Specifies the maximum age of the statistics retrieved from the CLI or SNMP; valid values are from 1 to 60 seconds.

Defaults

5 seconds

Command Modes

Global configuration

Command History

Release	Modification
12.1(23)E	Support for this command was introduced on the Catalyst 6500 series switches.

Usage Guidelines

---

Note If you decrease the statistics retrieval interval from the default setting (5 seconds), congestion may form in situations where frequent SNMP (SMNP bulk) retrievals occur.

---

Examples

This example shows how to set the statistics retrieval interval:

Router(config)# service counters max age 10

Router(config)# 

This example shows how to return to the default settings:

Router(config)# no service counters max age

Router(config)# 

service-policy input

To attach a policy map to an interface, use the service-policy input command. Use the no form of this command to remove a policy map from an interface.

service-policy input policy-map name

no service-policy input policy-map name

Syntax Description

policy-map name

Name of a previously configured policy map.

Defaults

No policy map is attached.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(7)XE	Support for this command was introduced on the Catalyst 6500 series switches.
12.1(1)E	Support for this command on the Catalyst 6500 series switches was extended to the 12.1 E release.

Usage Guidelines

Although the CLI allows you to configure PFC-based QoS on the WAN ports on the OC-12 ATM OSMs and on the WAN ports on the channelized OSMs, PFC-based QoS is not supported on the WAN ports on these OSMs.

The Catalyst 6500 series switches do not support the output service-policy keyword on Ethernet interfaces.

PFC QoS does not support the output service-policy keyword.

Examples

This example shows how to attach a policy map to a Fast Ethernet interface:

Router(config)# interface fastethernet 5/20

Router(config-if)# service-policy input pmap1

Router(config-if)# 

Related Commands

class-map
policy-map

session slot

To open a session with a module (for example, the MSM, NAM, or ATM), use the session slot command. This command allows you to use the module-specific CLI.

session slot mod {processor processor-id}

Syntax Description

mod	Slot number.