-
Cisco 7600 Series Router Cisco IOS Command Reference, 12.1E
-
Index
-
Preface
-
Command-Line Interface
-
action to cd
-
Cisco 7600 Series Router Cisco IOS Commands
-
BRC
-
channel-group to clear catalyst6000
-
clear counters to debug callback
-
debug cca to duplex
-
erase to mls aging
-
mls exclude to pagp port-priority
-
policy-map to protocol filtering
-
rcv-queue to show bootflash
-
shutdown vlan to time-range
-
show bootvar to show ip cache
-
show ip cef to show mls asic
-
show mls cef to show qm-sp
-
show queueing to show vtp
-
title
-
udld to username
-
verify to wrr-queue bandwidth
-
wrr-queue cos-map to wrr-queue threshold
-
Acronyms
-
Acknowledgments for Open-Source Software
-
Table Of Contents
22policy-map
To access QoS policy map configuration mode to configure the QoS policy map, use the policy-map command. Use the no form of this command to delete a policy map.
policy-map policy-map-name
no policy-map policy-map-name
Syntax Description
policy-map-name
Policy map name. See the "Usage Guidelines" section for descriptions of the policy-map subcommands.
Defaults
The defaults are as follows:
•
extended-burst-bytes is equal to burst-bytes.
•
•
•
•
Command Modes
Global configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
In QoS policy-map configuration mode, these configuration commands are available:
•
•
•
•
•
Table 2-20 describes the class syntax.
Valid values for action are as follows:
•
•
•
The pir peak-rate-bps corresponds to the extended burst rate.
The pir, extended-burst-bytes, and violate-action keywords and arguments are not supported in microflow policing or in systems configured with a Supervisor Engine 1 with Layer 3 Switching Engine (PFC), except for the default values.
The violate-action parameter is not supported in systems configured with a Supervisor Engine 1 with Layer 3 Switching Engine (PFC), but you can enter the command if the parameters match the exceed-action parameters.
PFC QoS does not support the bandwidth, priority, queue-limit, random-detect, or set keywords in policy map classes.
Examples
This example shows how to create a policy map named max-pol-ipp5 that uses a previously configured class-map named ipp5, how to configure trust received IP precedence values, and configure a maximum-capacity aggregate policer and a microflow policer:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map max-pol-ipp5Router(config-pmap)# class ipp5Router(config-pmap-c)# trust ip-precedenceRouter(config-pmap-c)# police 2000000000 2000000 8000000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmitRouter(config-pmap-c)# police flow 10000000 10000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmitRouter(config-pmap-c)# endRouter#Related Commands
class-map
service-policy input
show class-map
show policy-map
show policy-map interfaceport-channel load-balance
To set the load-distribution method among the ports in the bundle, use the port-channel load-balance command. Use the no form of this command to reset the load distribution to the default settings.
port-channel load-balance method
no port-channel load-balance
Syntax Description
Defaults
method is src-dst-ip.
Command Modes
Global configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Valid method values are as follows:
•
•
•
•
•
•
•
•
•
Examples
This example shows how to set the load distribution method to dst-ip:
Router(config)# port-channel load-balance dst-ipRouter(config)#Related Commands
interface port-channel
show etherchannelpower enable
To turn on power for the modules, use the power enable command. Use the no form of this command to power down a module.
power enable {module slot}
no power enable {module slot}
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
12.1(23)E
This command was changed to allow you to disable power to empty slots.
Usage Guidelines
When you enter the no power enable module slot command to power down a module, the module's configuration is not saved.
You can also use this command to disable power to an empty slot. This command allows you to reserve power that might have been supplied to in an empty slot and prevent higher consumption in the other slots.
The slot argument designates the module number. Valid values for slot depend on the chassis used. For example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
This example shows how to turn on the power for a module that was previously powered down:
Router(config)# power enable module 5Router(config)#This example shows how to power down a module:
Router(config)# no power enable module 5Router(config)#Related Commands
power inline
To configure the administrative mode of the inline power on an interface, use the power inline command.
power inline {auto | never}
Syntax Description
auto
Turns on the device discovery protocol and applies power to the device, if found.
never
Turns off the device discovery protocol and stops supplying power to the device.
Defaults
auto
Command Modes
Interface configuration
Command History
12.1(13)E
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to set the inline power to the off mode on an interface:
Router(config-if)# interface fastethernet5/1Router(config-if)# switchportRouter(config-if)# power inline neverRelated Commands
power redundancy-mode
To set the power-supply redundancy mode, use the power redundancy-mode command.
power redundancy-mode {combined | redundant}
Syntax Description
combined
Specifies no redundancy (combine power-supply outputs).
redundant
Specifies redundancy (either power supply can operate the system).
Defaults
redundant
Command Modes
Global configuration
Command History
12.1(8a)E3
Support for this command was introduced on the Cisco 7600 series routers.
Examples
This example shows how to set power supplies to the no-redundancy mode:
Router(config)# power redundancy-mode combinedRouter(config)#This example shows how to set power supplies to the redundancy mode:
Router(config)# power redundancy-mode redundantRouter(config)#Related Commands
ppp link
To generate PPP LCP down/keepalive failure link traps or enable calls to the interface reset vector, use the ppp link command. Use the no form of this command to disable PPP LCP down/keepalive failure link traps or calls to the interface reset vector.
ppp link {reset | trap}
no ppp link {reset | trap}
Syntax Description
reset
Specifies calls to the interface reset vector.
trap
Specifies the PPP LCP down/keepalive failure link traps.
Defaults
The defaults are as follows:
•
•
Command Modes
Interface configuration
Command History
12.1(19)E
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
The no ppp link trap command disables the sending of the link traps when the LCP goes down.
In the event the PPP calls the interface reset vector while the LCP is configured or closed, Up/Down status messages will display on the console. If a leased-line configuration is up but the peer is not responding, PPP may call the interface reset vector once per minute. This situation may result in the Up/Down status messages on the console. Use the no ppp link reset command to disable calls to the interface reset vector. PPP will continue to attempt to negotiate with the peer, but the interface will not be reset between each attempt.
Examples
This example shows how to enable calls to the interface reset vector:
Router(config-if)# ppp link resetRouter(config-if)#This example shows how to disable calls to the interface reset vector:
Router(config-if)# no ppp link resetRouter(config-if)#This example shows how to generate PPP LCP down/keepalive failure link traps:
Router(config-if)# ppp link trapRouter(config-if)#This example shows how to disable the sending of the link traps when the LCP goes down:
Router(config-if)# no ppp link trapRouter(config-if)#private-vlan
To configure PVLANs and the association between a PVLAN and a secondary VLAN, use the private-vlan command. Use the no form of this command to return to the default settings.
private-vlan {isolated | community | primary}
private-vlan association secondary-vlan-list | {add secondary-vlan-list} | {remove secondary-vlan-list}
no private-vlan {association | isolated | community | primary}
Syntax Description
Defaults
No PVLANs are configured.
Command Modes
config-VLAN submode
Command History
12.1(8a)EX
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
Caution
You cannot configure VLAN 1 or VLANs 1001 to 1005 as PVLANs.
VTP does not support PVLANs. You must configure PVLANs on each device where you want PVLAN ports.
The secondary-vlan-list parameter cannot contain spaces. It can contain multiple comma-separated items. Each item can be a single PVLAN ID or a hyphenated range of PVLAN IDs. The secondary-vlan-list parameter can contain multiple community VLAN IDs.
The secondary-vlan-list parameter can contain only one isolated VLAN ID. A PVLAN is a set of private ports characterized by using a common set of VLAN number pairs. Each pair is made up of at least two special unidirectional VLANs and is used by isolated ports and/or by a community of ports to communicate with routers.
An isolated VLAN is a VLAN that is used by isolated ports to communicate with promiscuous ports. An isolated VLAN's traffic is blocked on all other private ports in the same VLAN. Its traffic can only be received by standard trunking ports and promiscuous ports that are assigned to the corresponding primary VLAN.
A promiscuous port is defined as a private port that is assigned to a primary VLAN.
A primary VLAN is defined as the VLAN that is used to convey the traffic from the routers to customer end stations on private ports.
A community VLAN is defined as the VLAN that carries the traffic among community ports and from community ports to the promiscuous ports on the corresponding primary VLAN.
For Ethernet 10-Mb, 10/100-Mb, and 100-Mb modules, within groups of 12 ports (1-12, 13-24, 25-36, and 37-48), you cannot configure ports as isolated or community PVLAN ports when one port is a trunk, a SPAN destination, or a promiscuous PVLAN port.
Only one isolated vlan-id may be specified, while multiple community VLANs are allowed. Isolated and community VLANs can only be associated with one VLAN. The associated VLAN list may not contain primary VLANs. Similarly, a VLAN that is already associated to a primary VLAN cannot be configured itself as a primary VLAN.
The private-vlan commands do not take effect until you exit the config-VLAN submode.
If you delete either the primary or secondary VLAN, the ports associated with the VLAN become inactive.
Examples
This example shows how to create a PVLAN relationship between the primary VLAN 14, the isolated VLAN 19, and the community VLANs 20 and 21:
Router(config) # vlan 19Router(config-vlan) # private-vlan isolatedRouter(config) # vlan 20Router(config-vlan) # private-vlan communityRouter(config-vlan) # private-vlan communityRouter(config) # vlan 14Router(config-vlan) # private-vlan primaryRouter(config-vlan) # private-vlan association 19-21This example shows how to remove an isolated VLAN and community VLAN 20 from the PVLAN association:
Router(config) # vlan 14Router(config-vlan) # private-vlan association remove 18,20Router(config-vlan) #This example shows how to remove a PVLAN relationship and deletes the primary VLAN. The associated secondary VLANs are not deleted.
Router(config-vlan) # no private-vlan 14Router(config-vlan) #Related Commands
show vlan
show vlan private-vlanprivate-vlan mapping
To create a mapping between the primary and the secondary VLANs so that both VLANs share the same primary VLAN SVI, use the private-vlan mapping command. Use the no form of this command to remove all PVLAN mappings from the SVI.
private-vlan mapping {[secondary-vlan-list | {add secondary-vlan-list} | {remove secondary-vlan-list}]}
no private-vlan mapping
Syntax Description
Defaults
No PVLAN SVI mapping is configured.
Command Modes
Interface configuration
Command History
12.1(8a)EX
Support for this command was introduced on the Cisco 7600 series routers.
Usage Guidelines
The PVLAN mapping interface configuration command affects traffic that is switched in software on the MSFC or MSFC2. The private-vlan mapping interface configuration command does not configure Layer 3 switching on the PFC or PFC2.
The secondary-vlan-list parameter cannot contain spaces; it can contain multiple comma-separated items. Each item can be a single PVLAN ID or a hyphenated range of PVLAN IDs.
This command is valid in the interface configuration mode of the primary VLAN.
The SVI of the primary VLAN is created at Layer 3.
Traffic received on the secondary VLAN is routed by the SVI of the primary VLAN.
The SVIs of existing secondary VLANs do not function and are considered as down after you enter this command.
A secondary SVI can only be mapped to one primary SVI. If you configure the primary VLAN as a secondary VLAN, all the SVIs specified in this command are brought down.
If you configure a mapping between two VLANs that do not have a valid Layer 2 association, the mapping configuration does not take effect.
Examples
This example shows how to map the interface of VLAN 20 to the SVI of VLAN 18:
Router(config)# interface vlan 18Router(config-if)# private-vlan mapping 18 20Router(config-if)#This example shows how to permit routing of secondary VLAN ingress traffic from PVLANs 303 through 307, 309, and 440 and verify the configuration:
Router# configure terminalRouter(config)# interface vlan 202Router(config-if)# private-vlan mapping add 303-307,309,440Router(config-if)# endRouter# show interfaces private-vlan mappingInterface Secondary VLAN Type--------- -------------- -----------------vlan202 303 communityvlan202 304 communityvlan202 305 communityvlan202 306 communityvlan202 307 communityvlan202 309 communityvlan202 440 isolatedRouter#This example shows the displayed error message if the VLAN you are adding is already mapped to the SVI of VLAN 18. You must delete the mapping from the SVI of VLAN 18 first.
Router(config)# interface vlan 19Router(config-if)# private-vlan mapping 19 add 21Command rejected: The interface for VLAN 21 is already mapped as s secondary.Router(config-if)#This example shows how to remove all PVLAN mappings from the SVI of VLAN 19:
Router(config)# interface vlan 19Router(config-if)# no private-vlan mappingRouter(config-if)#
Related Commands
show interfaces private-vlan mapping
show vlan
show vlan private-vlanprivate-vlan synchronize
To map secondary VLANs to the same instance as the primary VLAN, use the private-vlan synchronize command.
private-vlan synchronize
Syntax Description
This command has no keywords or arguments.
Defaults
This command has no default settings.
Command Modes
MST configuration submode
Command History
Usage Guidelines
If you do not map VLANs to the same instance as the associated primary VLAN when you exit the MST configuration submode, a warning message displays and lists the secondary VLANs that are not mapped to the same instance as the associated primary VLAN. The private-vlan synchronize command automatically maps all secondary VLANs to the same instance as the associated primary VLANs.
Examples
This example assumes that a primary VLAN 2 and a secondary VLAN 3 are associated to VLAN 2, and that all VLANs are mapped to the CIST instance 1. This example also shows the output if you try to change the mapping for the primary VLAN 2 only:
Router(config)# spanning-tree mst configurationRouter(config-mst)# instance 1 vlan 2Router(config-mst)# exitThese secondary vlans are not mapped to the same instance as their primary:-> 3This example shows how to initialize PVLAN synchronization:
Router(config-mst)# private-vlan synchronizeRouter(config-mst)#Related Commands
protocol-filtering
To enable protocol filtering, use the protocol-filtering command. Use the no form of this command to disable protocol filtering.
protocol-filtering
no protocol-filtering
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
Usage Guidelines
Layer 3 protocol filtering is supported with a Supervisor Engine 1.
Layer 3 protocol filtering is not supported with a Supervisor Engine 2.
Examples
This example shows how to enable the protocol filtering feature:
Router(config)# protocol-filteringRouter(config)#Related Commands
