-
Cisco IOS Interface and Hardware Component Command Reference
-
Introduction
-
A through B
-
cable bundle through clock mode
-
clock rate through cut-through
-
D through E
-
F through H
-
I through K
-
l2 vfi manual through loopback (PA-MC-8TE1 + port adapter)
-
loopback (T1 interface) through nrzi-encoding
-
O through R
-
scramble through service-module t1 lbo
-
service-module t1 linecode through show controllers satellite
-
show controllers serial through show hw-module slot proc cpu
-
show hw-module slot tech-support through show interfaces vg-anylan
-
show interfaces vlan mapping through show scp
-
show service-module serial through standby port
-
squelch through system jumbomtu
-
t1 through tug-2 e1 unframed
-
tunnel bandwidth through yellow
-
Table Of Contents
password (satellite initial configuration)
platform cwan acl software-switched
platform ip features sequential
port-channel hash-distribution
port-channel load-balance mpls
port-channel load-balancing vlan-manual
port-channel standalone-disable
pos flag s1-byte rx-communicate
outbound data-pid
Note
Effective with Cisco IOS Release 12.4(2)T, this command is superseded by the outbound pid management command. The outbound data-pid command is still available, but use of the outbound pid management command is recommended.
To specify the outbound data packet identification (PID) number, use the outbound data-pid command in satellite initial configuration mode. To remove the PID number configuration, use the no form of this command.
outbound data-pid number
no outbound data-pid
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
12.3(14)T
This command was introduced.
12.4(2)T
This command was superseded by the outbound pid management command.
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the outbound data PID number:
Router(sat-init-config)# outbound data-pid 3000outbound data-rate
To specify the VSAT data rate, use the outbound data-rate command in satellite initial configuration mode. To remove the data rate configuration, use the no form of this command.
outbound data-rate rate
no outbound data-rate
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the VSAT data rate:
Router(sat-init-config)# outbound data-rate 450000outbound frequency
To specify the VSAT outbound frequency, use the outbound frequency command in satellite initial configuration mode. To remove the outbound frequency configuration, use the no form of this command.
outbound frequency frequency
no outbound frequency
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound frequency:
Router(sat-init-config)# outbound frequency 950000outbound id
To specify the VSAT outbound ID, use the outbound id command in satellite initial configuration mode. To remove the outbound ID configuration, use the no form of this command.
outbound id number
no outbound id
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound ID:
Router(sat-init-config)# outbound id 95outbound modulation-type
To specify the VSAT modulation type, use the outbound modulation-type command in satellite initial configuration mode. To remove the VSAT modulation type configuration, use the no form of this command.
outbound modulation-type {DVB | TURBO_QPSK | 8PSK}
no outbound modulation-type
Syntax Description
DVB
Digital Video Broadcasting for satellite.
TURBO_QPSK
Turbo-coded quadrature Phase Shift Keying.
8PSK
Phase Shift Keying.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT modulation type:
Router(sat-init-config)# outbound modulation-type DVBoutbound sync ip address
To specify the outbound synchronization IP address, use the outbound sync ip address command in satellite initial configuration mode. To remove the outbound synchronization IP address configuration, use the no form of this command.
outbound sync ip address address
no outbound sync ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the outbound synchronization IP address:
Router(sat-init-config)# outbound sync ip address 10.2.2.2outbound viterbi-rate
To specify the VSAT Viterbi code rate, use the outbound viterbi-rate command in satellite initial configuration mode. To return to the default rate, use the no form of this command.
outbound viterbi-rate rate
no outbound viterbi-rate
Syntax Description
rate
Viterbi code rate. It can be one of the following values:
•
•
•
•
•
•
•
•
•
•
•
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT Viterbi code rate:
Router(sat-init-config)# outbound viterbi-rate 3/4(2.6)overhead j0
To specify the Regenerator Section (RS) Trace identifier (J0), use the overhead j0 command in controller configuration mode. To restore the default value, use the no form of this command.
overhead j0 {transmit | receive} string
no overhead j0 {transmit | receive} string
Syntax Description
Defaults
The default value is 1, and no peer authentication is performed.
Command Modes
Controller configuration
Command History
12.0(17)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T, and the transmit and receive keywords were added.
Usage Guidelines
RS trace is a maintenance feature of SONET. One byte (J0) of the Section overhead associated with each SONET frame is used to carry information identifying the transmitting equipment.
Use this command for peer authentication and continuity testing between two STM-1 optical peers. If the authentication string sent by the originating peer does not match the configured string on the receiving peer, the SONET controller will not come up on the receiving peer. Alarm logs on the originating peer will show that it has RS-Trace Identifier Mismatch (RS-TIM).
Examples
The following example shows how to configure J0 overhead in both the transmit and receive directions on a STM-1 trunk card:
Router(config)# controller sonet 2/0Router(config-controller)# overhead j0 transmit 22Router(config-controller)# overhead j0 receive 34The following example shows how to set the RS Trace identifier to 82:
Router(config-controller)# overhead j0 transmit 82overhead j1
To configure the message length and the message text of the High Order Path Trace identifier (J1), use the overhead j1 command in controller configuration or path configuration mode. To restore the default value, use the no form of this command.
overhead j1 length {16 | 64} {transmit-message | receive-message} string
no overhead j1 length {16 | 64} {transmit-message | receive-message} string
Syntax Description
Defaults
The default message length is 16 for SDH framing and 64 for SONET framing.
No peer authentication is performed.Command Modes
SDH Framing with AU-4 Mapping
Controller configuration
SDH Framing with AU-3 Mapping, or SONET Framing
Path configuration
Command History
12.0(17)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T, and the transmit-message and receive-message keywords were added.
Usage Guidelines
Path trace is a maintenance feature of SONET/SDH. One byte (J1) of the Path overhead associated with each path in the SONET/SDH frame is used to carry information identifying the originating Path Terminating Equipment (PTE).
Where you configure the Path Trace identifier depends on the framing (SDH or SONET) and the AUG mapping. In SDH with AU-4 mapping, the Path Trace identifier is configured at the SONET controller level. In SDH with AU-3 mapping or in SONET framing, the Path Trace identifier is configured at the path level.
In accordance with SONET and SDH standard requirements, the Path Trace message you enter is manipulated as follows:
•
•
Use this command for peer authentication and continuity testing between two STM-1 optical peers. If the authentication string sent by the originating peer does not match the configured string on the receiving peer, the Path (and all E1 controllers within the path) will not come up on the receiving peer. Alarm logs on the originating peer will show that it has High Order Path-Trace Identifier Mismatch (HP-TIM).
Examples
The following example shows J1 configuration in SDH framing with AU-4 AUG mapping. The overhead j1 command sets the message length to 16, and specifies the message text as metro_SF:
Router(config-controller)# au-4 1Router(config-ctrlr-au4)# overhead j1 length 16 transmit-message metro_SFThe following example shows J1 configuration in SDH framing with AU-3 AUG mapping. The overhead j1 command sets the message length to 16, and specifies the message text as metro_LA:
Router(config)# controller sonet 4/0Router(config-controller)# au-3 3Router(config-ctrlr-au3)# overhead j1 length 16 receive-message metro_LThe following example shows J1 configuration in SONET framing in STS-1 mode. The overhead j1 command sets the message length to 64, and specifies the message text:
Router(config)# controller sonet 4/0Router(config-controller)# sts-1 3Router(config-ctrlr-sts1)# overhead j1 length 64 transmit-message metro_washington gsr_0057/4/3The following example shows how to configure j1 overhead in both the transmit and receive directions:
Router(config)# controller sonet 2/0Router(config-controller)# overhead j1 length 2 transmit-message 22Router(config-controller)# overhead j1 length 2 receive-message 34password (satellite initial configuration)
To define or to change the password of the NM-1VSAT-GILAT network module required to enter satellite initial configuration mode, use the password command in the satellite initial configuration mode.
password password
Syntax Description
Command Default
The factory-supplied default password is active.
Command Modes
Satellite initial configuration.
Command History
12.4(11)XJ2
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
The NM-1VSAT-GILAT network module has a factory-supplied unique default password to enter satellite initial configuration mode for initial configuration. During this configuration, the password command is used to set a user-defined password for subsequent entries to satellite initial configuration mode. The user-defined password consists of up to 32 alphanumeric characters.
Examples
The following example shows how to enter a user-defined password:
Router(sat-init-config)# password vsatuserpayload-compression
To enable payload compression, use the payload-compression command in CEM configuration mode. To disable payload compression, use the no form of this command.
payload-compression
no payload-compression
Syntax Description
This command has no arguments or keywords.
Command Default
Payload compression is disabled by default.
Command Modes
CEM configuration
Command History
Usage Guidelines
Payload compression can be enabled only for a maximum of 3 Mbps per network module.
Examples
The following example demonstrates how to enable payload compression.
Router(config-cem)# payload-compression
Related Commands
cem
Enters circuit emulation configuration mode.
payload-size
Configures payload size.
show cem
Displays CEM statistics.
payload-size
To configure the payload size of a circuit emulation (CEM) over IP (CEoIP) packet, use the payload-size command in CEM configuration mode. To restore the default payload size, use the no form of this command.
payload-size size
no payload-size
Syntax Description
Command Default
The default payload size for a serial channel is 32 bytes. Defaults for T1 and E1 channels are shown in Table 17 and Table 18.
Table 17 Default Payload Size for N*64-kbps T1/E1 Channels
Table 18 Default Payload Size for N*56-kbps T1 Channels
Command Modes
CEM configuration
Command History
Usage Guidelines
Use this command to configure the size of each CEoIP packet. Smaller sizes reduce delay but diminish efficiency.
Note
by the user will be automatically changed to match the above requirement, and a console message
will inform the user of this change.Examples
The following example demonstrates how to configure a payload size of 224.
Router(config-cem)# payload-size 224Related Commands
cem
Enters circuit emulation configuration mode.
payload-compression
Enables payload compression.
show cem
Displays CEM channel statistics.
physical-interface
To create a physical subinterface and to associate it with the Virtual Multipoint Interface (VMI) on a router, use the physical-interface command in interface configuration mode. To return to the default mode, use the no form of this command.
physical-interface interface-type/slot
no physical-interface interface-type/slot
Syntax Description
Command Default
No physical interface exists.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The physical-interface command supports the subinterfaces and VLANs associated with an interface. This command also allows VMI interface to operate over encapsulated interfaces, if required. Only one physical interface can be assigned to a VMI interface. Because there is very high number of VMI interfaces that can be used, assign a new VMI for each physical interface.
Examples
The following example shows how to create a physical subinterface:
Router(config)# interface vmi1Router(config-if)# physical-interface FastEthernet0/1Related Commands
physical-layer
To specify the mode of a slow-speed serial interface on a router as either synchronous or asynchronous, use the physical-layer command in interface configuration mode. To return the interface to the default mode of synchronous, use the no form of this command.
physical-layer {sync | async}
no physical-layer
Syntax Description
sync
Places the interface in synchronous mode. This is the default.
async
Places the interface in asynchronous mode.
Defaults
Synchronous mode
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies only to low-speed serial interfaces available on Cisco 2520 through Cisco 2523 series routers.
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
•
•
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces.
When you enter this command, it does not appear in the output of more system:running-config and more nvram:startup-config commands because the command is a physical-layer command.
Examples
The following example shows how to change a low-speed serial interface from synchronous to asynchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncRelated Commands
platform cwan acl software-switched
To allow ACLs to be applied to packets that are software-switched between WAN cards and the route processor, use the platform cwan acl software-switched command in global configuration mode. To have ACLs applied only to packets that are hardware-switched between WAN cards and the route processor, use the no form of this command.
platform cwan acl software-switched{egress | ingress}
no platform cwan acl software-switched{egress | ingress}
Syntax Description
egress
Allows ACLs to be applied to software-switched egress WAN packets.
ingress
Allows ACLs to be applied to software-switched ingress WAN packets.
Command Default
ACLs are not applied to packets that are software-switched between WAN cards and the route processor. ACLs are applied only to packets that are hardware-switched between WAN cards and the route processor.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
By default, software-switched WAN packets are not subjected to ACL lookup in the ACL TCAM and are therefore not affected by hardware-only features. As a result, VACL capture will fail for software-switched WAN packets. The platform cwan acl software-switched command allows ACLs to be applied to ingress or egress software-switched WAN packets.
When you use the platform cwan acl software-switched command to allow VACL capture, these limitations apply:
Note
Examples
This example shows how to enable ACLs for software-switched ingress WAN packets:
Router(config)# platform cwan acl software-switched ingressRelated Commands
show platform acl software-switched
Displays whether ACLs are enabled for software-switched WAN packets.
platform ip features sequential
To enable Internet Protocol (IP) precedence-based or differentiated services code point (DSCP)-based egress quality of service (QoS) filtering to use any IP precedence or DSCP policing or marking changes made by ingress policy feature card (PFC) QoS, use the platform ip features sequential command in interface configuration mode. To return to the default settings, use the no form of this command.
platform ip features sequential [access-group {ip-acl-name | ip-acl-number}]
no platform ip features sequential [access-group {ip-acl-name | ip-acl-number}]
Syntax Description
Defaults
IP precedence-based or DSCP-based egress QoS filtering uses received IP precedence or DSCP values and does not use any IP precedence or DSCP changes made by ingress QoS as the result of policing or marking.
Command Modes
Interface configuration
Command History
12.2(18)SXE
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Caution
The enhanced egress-QoS filtering enables the IP precedence-based or DSCP-based egress-QoS filtering to use any IP precedence or DSCP policing or marking changes made by ingress QoS.
The nonenhanced egress-QoS filtering behavior is the normal Catalyst 6500 series switch or the Catalyst 6500 series switch behavior when QoS is applied in the hardware.
The PFC3 provides egress PFC QoS only for Layer 3-switched and routed traffic on egress Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces).
You configure enhanced egress QoS filtering on ingress Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces).
To enable enhanced egress QoS filtering only for the traffic filtered by a specific standard, extended named, or extended numbered IP ACL, enter the IP ACL name or number.
If you do not enter an IP ACL name or number, enhanced egress QoS filtering is enabled for all IP ingress IP traffic on the interface.
Note
Note
Note
To verify configuration, use the show running-config interface command.
Examples
The following example shows how to enable enhanced egress-QoS filtering:
Router(config-if)# platform ip features sequentialRouter(config-if)#The following example shows how to disable enhanced egress-QoS filtering:
Router(config-if)# no platform ip features sequentialRouter(config-if)#Related Commands
show running-config interface
Displays the contents of the currently running configuration file.
platform scp retry interval
To enable Switch-Module Configuration Protocol (SCP) fast retry and set the fast-retry interval, use the platform scp retry interval command in global configuration mode. To disable SCP fast retry, use the no form of this command.
platform scp retry interval timeout-value
no platform scp retry interval
Syntax Description
Defaults
2000 milliseconds
Command Modes
Global configuration
Command History
12.2(18)SXD
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Note
Examples
This example shows how to enable SCP fast retry and set the fast-retry interval:
Router(config)# platform scp retry interval 600Router(config)#port (interface)
To enable an interface on a PA-4R-DTR port adapter to operate as a concentrator port, use the port command in interface configuration mode. To restore the default station mode, use the no form of this command.
port
no port
Syntax Description
This command has no arguments or keywords.
Defaults
Station mode
Command Modes
Interface configuration
Command History
Usage Guidelines
By default, the interfaces of the PA-4R-DTR operate as Token Ring stations. Station mode is the typical operating mode. Use this command to enable an interface to operate as a concentrator port.
Examples
The following example configures the PA-4R-DTR ports to operate in concentrator mode on a Cisco 7000 series router:
Router(config)# interface tokenring 3/0/0Router(config-if)# portport access-map
To create a port access map or enter port access-map command mode, use the port access-map command in global configuration mode. To remove a mapping sequence or the entire map, use the no form of this command.
port access-map name [seq#]
no port access-map name [seq#]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.2(14)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
If you enter the sequence number of an existing map sequence, you enter port access-map mode. If you do not specify a sequence number, a number is automatically assigned. You can enter one match clause and one action clause per map sequence.
If you enter the no port access-map name [seq#] command without entering a sequence number, the whole map is removed.
Once you enter port access-map mode, the following commands are available:
•
•
•
•
•
•
Examples
This example shows how to enter port access-map mode:
Router(config)# port access-map tedRouter(config-port-map)#Related Commands
action
Sets the packet action clause.
match
Specifies the match clause by selecting one or more ACLs for a VLAN access-map sequence.
port-channel hash-distribution
To set the hash distribution algorithm method, use the port-channel hash-distribution command in global configuration mode. To return to the default settings, use the no or default form of this command.
port-channel hash-distribution {adaptive | fixed}
{no | default} port-channel hash-distribution
Syntax Description
Command Default
The hash distribution algorithm method is set to fixed.
Command Modes
Global configuration (config)
Command History
12.2(33)SXH
This command was introduced.
12.2(33)SRC
This command was integrated into Cisco IOS Release 12.2(33)SRC.
Usage Guidelines
The EtherChannel load distribution algorithm uses the bundle select register in the port ASIC to determine the port for each outgoing packet. When you use the adaptive algorithm, it does not require the bundle select register to be changed for existing member ports. When you use the fixed algorithm and you either add or delete a port from the EtherChannel, the switch updates the bundle select register for each port in the EtherChannel. This update causes a short outage on each port.
Note
Examples
The following example shows how to set the hash distribution algorithm method to adaptive:
Router(config)# port-channel hash-distribution adaptiveport-channel load-balance
To set the load distribution method among the ports in a bundle, use the port-channel load-balance command in global configuration mode. To reset the load distribution to the default settings, use the no form of this command.
port-channel load-balance method module slot
no port-channel load-balance
Syntax Description
Command Default
The default method is src-dst-ip.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Valid method values are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
The port-channel load-balance method module slot command is supported on DFC systems only.
The port-channel per-module load-balance command allows you to enable or disable port-channel load-balancing on a per-module basis. You can enter the port-channel load-balance method module slot command to specify the load-balancing method on a specific module after you have entered the port-channel per-module load-balance command.
The following keywords are supported on systems that are in PFC3C or PFC3CXL mode (PFC3C or PFC3CXL with no DFC3A or DFC3B/BXL) only:
•
•
•
Note
Examples
The following example shows how to set the load-distribution method to dst-ip:
Router(config)# port-channel load-balance dst-ipThe following example shows how to set the load-distribution method on a specific module:
Router(config)# port-channel load-balance dst-ip module 2The following example shows how to set the load-distribution method excluding the VLAN option:
Router(config)# port-channel load-balance dst-ip exclude vlanRelated Commands
port-channel load-balance mpls
To set the load-distribution method among the ports in the bundle for Multiprotocol Label Switching (MPLS) packets, use the port-channel load-balance mpls command in global configuration mode. To reset the load distribution to the default settings, use the no form of this command.
port-channel load-balance mpls {label | label-ip}
no port-channel load-balance mpls
Syntax Description
Defaults
label-ip
Command Modes
Global configuration
Command History
12.2(14)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
If you select label, these guidelines apply:
•
•
If you select label-ip, these guidelines apply:
•
•
•
Examples
This example shows how to set the load-distribution method to label-ip:
Router(config)# port-channel load-balance mpls label-ipRouter(config)#Related Commands
interface port-channel
Creates a port-channel virtual interface and enters interface configuration mode.
show etherchannel
Displays the EtherChannel information for a channel.
port-channel load-balancing vlan-manual
To apply the VLAN-manual load-balancing method globally to all Gigabit EtherChannel (GEC) interfaces, use the port-channel load-balancing vlan-manual command in global configuration mode. To reset to the default, use the no form of this command.
port-channel load-balancing vlan-manual
no port-channel load-balancing
Syntax Description
This command has no arguments or keywords.
Command Default
Flow-based load balancing is enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The port-channel load-balancing vlan-manual command applies the VLAN-manual load-balancing method globally to all port channels on the router. If you do not use this command to explicitly set the global load-balancing method to VLAN-manual, the load-balancing method is set to flow-based.
The load-balancing method enabled on a port channel with the load-balancing command takes precedence over this command.
Load balancing uses the concept of buckets to map traffic flows to the member links of a port channel. The different traffic flows are mapped to the buckets and each bucket has one active member link associated with it. All flows that are mapped to a bucket use the member link associated with that bucket.
There are two methods of load balancing on a GEC interface:
•
•
Examples
This example shows how to set the load-balancing method to VLAN-manual:
Router(config)# port-channel load-balancing vlan-manualRelated Commands
port-channel load-defer
To configure the port load share deferral interval for all port channels, use the port-channel load-defer command in global configuration mode. To reset the port defer interval to the default setting, use the no form of this command.
port-channel load-defer seconds
no port-channel load-defer
Syntax Description
Defaults
The port defer interval is 120 seconds.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
To reduce data loss following a stateful switchover (SSO), port load share deferral can be enabled by entering the port-channel port load-defer command on a port channel of a switch that is connected by a multichassis EtherChannel (MEC) to a virtual switching system (VSS). Port load share deferral temporarily prevents the switch from forwarding data traffic to MEC member ports on a failed chassis of the VSS while the VSS recovers from the SSO.
The load share deferral interval is determined by a single global timer configurable by the port-channel load-defer command. After an SSO switchover, a period of several seconds to several minutes can be required for the reinitialization of line cards and the reestablishment of forwarding tables, particularly multicast topologies.
The valid range of seconds is 1 to 1800 seconds; the default is 120 seconds.
Examples
This example shows how to set the global port deferral interval to 60 seconds:
Router(config)# port-channel load-defer 60Router(config)#This example shows how to verify the configuration of the port deferral interval on a port channel:
Router# show etherchannel 50 port-channelPort-channels in the group:----------------------Port-channel: Po50 (Primary Aggregator)------------Age of the Port-channel = 0d:00h:22m:20sLogical slot/port = 46/5 Number of ports = 3HotStandBy port = nullPort state = Port-channel Ag-InuseProtocol = LACPFast-switchover = disabledLoad share deferral = enabled defer period = 60 sec time left = 57 secRouter#Related Commands
port-channel min-links
To specify that a minimum number of bundled ports in an EtherChannel is required before the channel can be active, use the port-channel min-links command in interface configuration mode. To return to the default settings, use the no form of this command.
port-channel min-links min-num
no port-channel min-links
Syntax Description
min-num
Minimum number of bundled ports in a channel that is required before the channel can be active; valid values are from 2 to 8.
Defaults
min-num is 1.
Command Modes
Interface configuration
Command History
12.2(18)SXF
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is supported on LACP (802.3ad) ports only. More than one LACP secondary-port channel can belong to the same channel group. This command is applied to all port channels in the same group.
If fewer links than the specified number are available, the port-channel interface does not become active.
Use the show running-config command to verify the configuration.
Examples
This example shows how to specify that a minimum number of bundled ports in an EtherChannel is required before the channel can be active:
Router(config-if)# port-channel min-links 3Router(config-if)#Related Commands
show running-config
Displays the status and configuration of the module or Layer 2 VLAN.
port-channel port load-defer
To enable the temporary deferral of port load sharing during the connection or reconnection of a port channel, use the port-channel port load-defer command in interface configuration mode. To disable the deferral of port load sharing on a port channel, use the no form of this command.
port-channel port load-defer
no port-channel port load-defer
Syntax Description
This command has no arguments or keywords.
Defaults
The port load share deferral feature is not enabled on a port channel.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
To reduce data loss following a stateful switchover (SSO), port load share deferral can be enabled on a port channel of a switch that is connected by a multichassis EtherChannel (MEC) to a virtual switching system (VSS). The load share deferral interval prevents the switch from forwarding data traffic to MEC member ports on a failed chassis of the VSS while the VSS recovers from the SSO.
When load share deferral is enabled on a port channel, the assignment of a member port's load share is delayed for a period that is configurable globally by the port-channel load-defer command. During the deferral period, the load share of a deferred member port is set to 0. In this state, the deferred port is capable of receiving data and control traffic, and of sending control traffic, but the port is prevented from sending data traffic over the MEC to the VSS. Upon expiration of the global deferral timer, the deferred member port exits the deferral state and the port assumes its normal configured load share.
Load share deferral is applied only if at least one other member port of the port channel is currently active with a nonzero load share. If a port enabled for load share deferral is the first member bringing up the EtherChannel, the deferral feature does not apply and the port will forward traffic immediately.
The load share deferral interval is determined by a single global timer configurable from 1 to 1800 seconds by the port-channel load-defer command. The default interval is 120 seconds. After an SSO switchover, a period of several seconds to several minutes can be required for the reinitialization of line cards and the reestablishment of forwarding tables, particularly multicast topologies.
Examples
This example shows how to enable the load share deferral feature on port channel 50 of a switch that is an MEC peer to a VSS:
Router(config)# interface port-channel 50Router(config-if)# port-channel port load-deferThis will enable the load share deferral feature on this port-channel.The port-channel should connect to a Virtual Switch (VSS).Do you wish to proceed? [yes/no]: yesRouter(config-if)#This example shows how to verify the state of the port deferral feature on a port channel:
Router# show etherchannel 50 port-channelPort-channels in the group:----------------------Port-channel: Po50 (Primary Aggregator)------------Age of the Port-channel = 0d:00h:22m:20sLogical slot/port = 46/5 Number of ports = 3HotStandBy port = nullPort state = Port-channel Ag-InuseProtocol = LACPFast-switchover = disabledLoad share deferral = enabled defer period = 120 sec time left = 57 secRouter#Related Commands
port-channel standalone-disable
To disable the EtherChannel standalone option in a port channel, use the port-channel standalone-disable command in interface configuration mode. To enable this option, use the no form of this command.
port-channel standalone-disable
no port-channel standalone-disable
Syntax Description
This command has no arguments or keywords.
Command Default
The standalone option is enabled.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The port-channel standalone-disable command is supported on Catalyst 6000 routers. This command can be used only when the port channel protocol type is Link Aggregation Control Protocol (LACP). This command enables you to change the current behavior when a physical port cannot bundle an LACP EtherChannel.
Examples
The following example shows how to disable the EtherChannel standalone option in a port channel:
Router(config-if)# port-channel standalone-disableRelated Commands
pos ais-shut
To send the line alarm indication signal (LAIS) when the Packet-over-SONET (POS) interface is placed in any administrative shutdown state, use the pos ais-shut command in interface configuration mode.
pos ais-shut
Syntax Description
This command has no arguments or keywords.
Defaults
No LAIS is sent.
Command Modes
Interface configuration
Command History
Usage Guidelines
In Automatic Protection Switching (APS) environments, LAIS can be used to force a protection switch. This command forces an APS switch when the interface is placed in the administrative shutdown state.
For more information on APS, refer to the "Configuring Serial Interfaces" chapter in the Cisco IOS Interface and Hardware Component Configuration Guide.
This command does not have a no form.
Examples
The following example forces the alarm indication on POS OC-3 interface 0 in slot 3:
Router(config)# interface pos 3/0Router(config-if)# shutdownRouter(config-if)# pos ais-shutpos delay triggers
To enable a POS alarm trigger delay, or to enable path level alarms as triggers to bring the POS line card protocol to down, use the pos delay triggers command in POS interface configuration mode. To disable POS alarm trigger delays, use the no form of this command.
pos delay triggers [line ms | path ms]
no pos delay triggers [line ms | path ms]
Syntax Description
Command Default
POS line level alarm triggers are enabled by default. If a POS line level alarm trigger occurs and no configuration changes have been made using the pos delay triggers line ms command, the line protocol is set to down immediately with no delay.
POS path level alarm triggers are disabled by default. A path level alarm will not set the line protocol to down unless the pos delay triggers path command has been entered.
If no ms value is entered but pos delay triggers line command is configured, the default ms value for line level triggers is 100 ms.
If no ms value is entered and pos delay triggers path is enabled, the default ms value is set at 100 ms for path level triggers.
Command Modes
POS interface configuration
Command History
Usage Guidelines
A trigger is an alarm that, when asserted, causes the line protocol to go down.
When one or more triggers are asserted, the line protocol of the interface goes down. The POS Alarm Trigger Delay feature provides the option to delay triggering of the line protocol of the interface from going down when an alarm triggers the line protocol to go down. For instance, if you configure the POS alarm delay for 150 ms, the line protocol will not go down for 150 ms after receiving the trigger. If the trigger alarm stays up for more than 150 ms, the link is brought down as it is now. If the trigger alarm clears before 150 ms, the line protocol is not brought down.
By default, the following line and section alarms are triggers for the line protocol to go down:
•
•
•
For line and section alarm triggers, the line protocol of the POS card is brought down immediately if a trigger is received and no POS alarm trigger delay is specified. The delay can be set anywhere from 50 to 10000 ms. If POS alarm triggering is configured but no ms value is entered, the POS alarm trigger delay is 100 ms.
The following path alarms are not triggers by default. These path alarms, however, can be configured as triggers:
•
•
The POS Alarm Trigger Delay feature can be used to configure these alarms as triggers, as well as to configure the exact POS alarm trigger delay for these triggers. The default delay values for these triggers, if no value is specified, is also 100 ms.
Examples
In the following configuration example, the POS line card will wait 50 ms after receiving a line level trigger before setting the line protocol to down. If the alarm that began the line level trigger clears during that 50 ms, the line protocol will remain up. If the alarm that began the line trigger remains after that 50 ms, the line protocol will go down.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface pos 1/0Router(config-if)# pos delay triggers line 50In the following configuration example, the POS line card will wait 110 ms after receiving a path trigger before setting the line protocol to down. If the alarm that began the path trigger clears during that 110 ms, the line protocol will remain up. If the alarm that began the path trigger remains after 110 ms, the line protocol will go down.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface pos 1/0Router(config-if)# pos delay triggers path 110In the following example, the show controllers pos slot/interface-number detail command is used to verify the POS alarm trigger delay. In this particular example, the delay is 100 ms (italicized for emphasis below) for both line level triggers and path level triggers.
Router# show controllers pos 4/0 detailPOS4/0
SECTION
LOF = 0 LOS = 0 BIP(B1) = 22
LINE
AIS = 0 RDI = 0 FEBE = 21 BIP(B2) = 38
PATH
AIS = 0 RDI = 1 FEBE = 25 BIP(B3) = 31
PLM = 0 UNEQ = 0 TIM = 0 TIU = 0
LOP = 0 NEWPTR = 4 PSE = 2 NSE = 3
Active Defects:None
Active Alarms: None
Alarm reporting enabled for:SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
Line triggers delayed 100 ms
Path triggers delayed 100 ms...Related Commands
show controllers pos slot/interface-number detail
Shows the content of POS controllers, including the amount of delay for line triggers.
pos flag
To set the SONET overhead bytes in the frame header to meet a specific standards requirement or to ensure interoperability with the equipment of another vendor, use the pos flag command in interface configuration mode. To remove the setting of the SONET overhead bytes, use the no form of this command.
pos flag {c2 | j0 | s1s0} value
no pos flag {c2 | j0 | s1s0} value
Syntax Description
Defaults
The default c2 value is 0xCF.
The default sls0 value is 0.Command Modes
Interface configuration
Command History
Usage Guidelines
Use the following values to tell the SONET transmission equipment the payload type:
•
•
•
•
Examples
The following example sets the path signal identifier used to identify the payload content type to ATM on the pos interface in slot 9:
Router(config)# interface pos 9/0Router(config-if)# pos flag c2 0x13Router(config-if)# endpos flag s1-byte rx-communicate
To direct the router to switch to internal clocking when it receives an S1 SONET overhead byte with a value of 0xF, use the pos flag s1-byte rx-communicate command in interface configuration mode. To disable this capability, use the no form of this command.
pos flag s1-byte rx-communicate
no pos flag s1-byte rx-communicate
Command Default
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The pos flag s1-byte rx-communicate command directs the router to switch the clock source to internal when it receives an S1 SONET overhead byte with a value of 0xF. When the S1 SONET overhead byte changes from 0xF to any other value, the clock source reverts back to the clock source specified in the user configuration.
The S1 SONET overhead byte is ignored by the receiving router unless the pos flag s1-byte rx-communicate command is issued.
Examples
The following example directs the router to switch to internal clocking when it receives an S1 SONET overhead byte with a value of 0xF:
pos flag s1-byte rx-communicateRelated Commands
pos flag s1-byte tx
To control the transmission of the S1 SONET overhead byte, use the pos flag s1-byte tx command in interface configuration mode.
pos flag s1-byte tx value
Syntax Description
Command Default
The default is 0x0.
Command Modes
Interface configuration
Command History
Usage Guidelines
In most situations, the default value for the S1 SONET overhead byte does not need to be changed. Refer to the SONET standards for information about the possible values for the S1 SONET overhead byte and the definition of each value.
Examples
The following example sets the S1 SONET overhead byte to 0xF:
pos flag s1-byte tx 0xFRelated Commands
pos framing
To specify the framing used on the POS (Packet-over-SONET) interface, use the pos framing command in interface configuration mode. To return to the default SONET STS-3c framing mode, use the no form of this command.
pos framing {sdh | sonet}
no pos framing
Syntax Description
sdh
Selects SDH STM-1 framing. This framing mode is typically used in Europe.
sonet
Selects SONET STS-3c framing. This is the default.
Defaults
SONET STS-3c framing
Command Modes
Interface configuration
Command History
Examples
The following example configures the interface for SDH STM-1 framing:
Router(config)# interface pos 3/0Router(config-if)# pos framing sdhRouter(config-if)# no shutdownRelated Commands
clock source (interface)
Controls the clock used by a G.703-E1 interface.
interface
Configures an interface type, and enters interface configuration mode.
pos report
To permit selected SONET alarms to be logged to the console for a POS (Packet-over-SONET) interface, use the pos report command in interface configuration mode. To disable logging of select SONET alarms, use the no form of this command.
pos report {b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
no pos report {b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
Syntax Description
Defaults
The following alarms are reported by default:
•
•
•
•
•
•
•
Command Modes
Interface configuration
Command History
Usage Guidelines
Reporting an alarm means that the alarm can be logged to the console. Just because an alarm is permitted to be logged does not guarantee that it is logged. SONET alarm hierarchy rules dictate that only the most severe alarm of an alarm group is reported. Whether an alarm is reported or not, you can view the current state of a defect by checking the "Active Defects" line from the show controllers pos command output. A defect is a problem indication that is a candidate for an alarm.
For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the bit interleaved parity error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
PAIS is sent by line terminating equipment (LTE) to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
PLOP is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF) enabled indications.
SLOF is detected when a severely error framing (SEF) defect on the incoming SONET signal persists for 3 milliseconds.
SLOS is detected when an all-zeros pattern on the incoming SONET signal lasts 19 plus or minus 3 microseconds or longer. This defect might also be reported if the received signal level drops below the specified threshold.
To determine the alarms that are reported on the interface, use the show controllers pos command.
Examples
The following example enables reporting of SD-BER and LAIS alarms on the interface:
Router(config)# interface pos 3/0/0Router(config-if)# pos report sd-berRouter(config-if)# pos report laisRouter(config-if)# endRelated Commands
interface
Configures an interface type, and enters interface configuration mode.
show controllers pos
Displays information about the POS controllers.
pos scramble-atm
To enable SONET payload scrambling on a POS (Packet-over-SONET) interface, use the pos scramble-atm command in interface configuration mode. To disable scrambling, use the no form of this command.
pos scramble-atm
no pos scramble-atm
Syntax Description
This command has no arguments or keywords.
Defaults
Scrambling is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
SONET payload scrambling applies a self-synchronous scrambler (x43+1) to the Synchronous Payload Envelope (SPE) of the interface to ensure sufficient bit transition density. Both ends of the connection must use the same scrambling algorithm. When enabling POS scrambling on a VIP2 POSIP on the Cisco 7500 series router that has a hardware revision of 1.5 or higher, you can specify CRC 16 only (that is, CRC 32 is currently not supported).
To determine the hardware revision of the POSIP, use the show diag command.
To determine whether scrambling is enabled on the interface, use the show interface pos command or the show running-config command.
Note
Examples
The following example enables scrambling on the interface:
Router(config)# interface pos 3/0Router(config-if)# pos scramble-atmRouter(config-if)# no shutdownRouter(config-if)# endRelated Commands
pos threshold
To set the bit-error rate (BER) threshold values of the specified alarms for a POS (Packet-Over-SONET) interface, use the pos threshold command in interface configuration mode. To return to the default setting, use the no form of this command.
pos threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate
no pos threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate
Syntax Description
Defaults
The default rate is 6 for b1-tca, b2-tca, b3-tca, and sd-ber.
The default rate is 3 (10e-3) for sf-ber.Command Modes
Interface configuration
Command History
Usage Guidelines
For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the bit interleaved parity error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
SF-BER and SD-BER are sourced from B2 BIP-8 error counts (as is B2-TCA). However, SF-BER and SD-BER feed into the automatic protection switching (APS) machine and can lead to a protection switch (if APS is configured).
B1-TCA, B2-TCA, and B3-TCA do nothing more than print a log message to the console (if reports for them are enabled).
To determine the BER thresholds configured on the interface, use the show controllers pos command.
Examples
The following example configures thresholds on the interface:
Router(config)# interface pos 3/0/0Router(config-if)# pos threshold sd-ber 8Router(config-if)# pos threshold sf-ber 4Router(config-if)# pos threshold b1-tca 4Router(config-if)# endRelated Commands
power enable
To turn on power for the modules, use the power enable command in global configuration mode. To power down a module, use the no form of this command.
power enable module slot
no power enable module slot
Syntax Description<
Defaults
Enabled
Command Modes
Global configuration
Command History
Usage Guidelines
When you enter the no power enable module slot command to power down a module, the module's configuration is not saved.
When you enter the no power enable module slot command to power down an empty slot, the configuration is saved.
The slot argument designates the module number. Valid values for slot depend on the chassis that is 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 determine how inline power is applied to the device on the specified switch port, use the power inline command in interface configuration mode. To return the setting to its default, use the no form of this command.
power inline {auto [max max-milliwatts] | never | police | static [max max-milliwatts]}
no power inline [police]
Syntax Description
Command Default
Power is applied when a telephone is detected on the port (auto).
max-milliwatts is 15400 milliwatts.
Inline power policing is disabled.Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The police keyword appears if you have a WS-F6K-48-AF or other inline power daughter card that supports power monitoring and inline power policing.
Inline power is supported only on switch ports that are connected to an IP phone. Before you enable inline power on a switch port, you must enter the switchport command.
The following information applies to WS-F6K-48-AF and WS-F6K-GE48-AF inline power cards:
•
Note
•
Examples
The following example shows how to set the inline power to the off mode on a switch port:
Router(config)# interface fastethernet5/1Router(config-if)# switchportRouter(config-if)# power inline neverThe following example shows how to allocate power from the system power pool to a switch port:
Router(config)# interface fastethernet5/1Router(config-if)# switchportRouter(config-if)# power inline static max 15000The following example shows how to turn on inline power policing to a switch port:
Router(config)# interface gigabitethernet6/3Router(config-if)# switchportRouter(config-if)# power inline policeRelated Commands
power redundancy-mode
To set the power-supply redundancy mode, use the power redundancy-mode command in global configuration mode.
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
Examples
This example shows how to set the power supplies to the no-redundancy mode:
Router(config)# power redundancy-mode combinedRouter(config)#This example shows how to set the power supplies to the redundancy mode:
Router(config)# power redundancy-mode redundantRouter(config)#Related Commands
ppp link
To generate the Point-to-Point Protocol (PPP) Link Control Protocol (LCP) down and keepalive-failure link traps or enable calls to the interface-reset vector, use the ppp link command in interface configuration mode. To disable the PPP LCP down and keepalive-failure link traps or calls to the interface-reset vector, use the no form of this command.
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 and keepalive-failure link traps.
Defaults
The defaults are as follows:
•
•
Command Modes
Interface configuration
Command History
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 720.
The no ppp link trap command disables the sending of the link traps when the LCP goes down.
In the event that 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 the 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)#ppp multilink mrru
To configure the maximum receive reconstructed unit (MRRU) value negotiated on a Multilink PPP (MLP) bundle, use the ppp multilink mrru command in interface configuration mode. To remove the configured MRRU, use the no form of this command.
ppp multilink mrru [local | remote] bytes
no ppp multilink mrru [local | remote] bytes
Syntax Description
Defaults
The default values for the local MRRU are the value of the multilink group interface maximum transmission unit (MTU) for multilink group members, and 1524 bytes for all other interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows the MRRU value to be configured on MLP interfaces and member links. This command is useful for interfaces running an application such as IP Security (IPsec), where the addition of the IPsec header causes the packet to exceed the 1500-byte MTU of a typical IP packet.
When using a large-bundle interface MTU size, you must ensure that the individual frames-per-fragment size passed to the link interfaces is not greater than the link interface MTU setting or the peer MRRU setting. This size limit can be achieved in one of the following two ways:
•
•
When MLP is configured, several physical interfaces can constitute one logical connection to the peer. To represent the logical connection, software provides a logical interface, often called the bundle interface. This interface will have the IP address, for instance, and the MTU setting of the interface that IP uses when it is deciding whether to fragment an IP datagram that needs to be forwarded. The physical interfaces forward individual MLP fragments or frames that are given to them by the bundle interface.
The result of having to decide whether to fragment a packet is that, whereas with simple PPP the interface MTU must not exceed the peer's MRRU, with MLP the MTU size of the bundle interface must not exceed the MRRU setting of the peer.
The MRRU settings on both sides need not be equal, but the "must not exceed" rule just specified must be followed; otherwise a system might send several fragments that, when reconstructed as a frame, will be too large for the peer's receive buffer.
Once you configure the MRRU on the bundle interface, you enable the router to receive large reconstructed MLP frames. You may want to configure the bundle MTU so that the router can send large MLP frames, although it is not strictly necessary. The maximum recommended value for the bundle MTU is the value of the peer's MTU. The software will automatically reduce the bundle interface MTU if necessary to avoid violating the peer's MRRU.
When the bundle interface MTU is tuned to a higher number, then depending upon the fragmentation configuration, the link interface may be given larger frames to send. There are two possible solutions to this problem, as follows:
•
•
Note
Examples
The following example shows how to configure MRRU negotiation on a virtual template with synchronous serial interfaces. The example also applies to asynchronous serial interfaces.
multilink virtual-template 1!interface virtual-template 1ip address 10.13.1.1 255.255.255.0mtu 1600!interface serial 0/0ppp multilinkppp multilink mrru local 1600mtu 1600!interface serial 0/1ppp multilinkppp multilink mrru local 1600mtu 1600
The following example shows how to configure MRRU negotiation on multilink groups:
interface multilink 10ip address 10.13.1.1 255.255.255.0ppp multilink mrru local 1600mtu 1600!interface serial 0/0ppp multilinkmultilink-group 10mtu 1600!interface serial 0/1ppp multilinkmultilink-group 10mtu 1600The following example shows how to configure MRRU negotiation on dialer interfaces:
Note
interface dialer 1ip address 10.13.1.1 255.255.255.0encapsulation pppdialer remote-name 2610-2dialer idle-timeout 30 inbounddialer string 5550101dialer pool 1dialer-group 1no cdp enableppp multilinkppp multilink mrru local 1600Related Commands
pri-group
To specify ISDN PRI on a channelized E1 or T1 card on a Cisco 7500 series router, use the pri-group command in controller configuration mode. To remove the ISDN PRI, use the no form of this command.
pri-group [timeslots range]
no pri-group
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
When you configure ISDN PRI, you must first specify an ISDN switch type for PRI and an E1 or T1 controller.
Examples
The following example specifies ISDN PRI on T1 slot 1, port 0:
Router# isdn switch-type primary-4essRouter(config)# controllers t1 1/0Router(config-controller)# framing esfRouter(config-controller)# linecode b8zsRouter(config-controller)# pri-group timeslots 2-6Related Commands
pulse-time
To enable pulsing data terminal ready (DTR) signal intervals on the serial interfaces, use the pulse-time command in interface configuration mode. To restore the default interval, use the no form of this command.
pulse-time [msec] seconds
no pulse-time
Syntax Description
Defaults
0 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
When the serial line protocol goes down (for example, because of loss of synchronization), the interface hardware is reset and the DTR signal is held inactive for at least the specified interval. This function is useful for handling encrypting or other similar devices that use the toggling of the DTR signal to resynchronize.
Use the optional msec keyword to specify the DTR signal interval in milliseconds. A signal interval set to milliseconds is recommended on High-Speed Serial Interfaces (HSSIs).
Examples
The following example enables DTR pulse signals for 3 seconds on serial interface 2:
Router(config)# interface serial 2Router(config-if)# pulse-time 3The following example enables DTR pulse signals for 150 milliseconds on HSSI interface 2/1/0:
Router(config)# interface hssi 2/1/0Router(config-if)# pulse-time msec 150redundancy
To enter redundancy configuration mode, use the redundancy command in global configuration mode.
redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
No default behaviors or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the redundancy command to enter redundancy configuration mode, where you can define aspects of redundancy such as shelf redundancy for the Cisco AS5800 universal access server.
Cisco 10000 Series Router
Before configuring line card redundancy, install the Y-cables. Before deconfiguring redundancy, remove the Y-cables.
The following restrictions apply to line card redundancy on the Cisco 10000 series router:
•
•
•
Cisco 7600 Series Router
From redundancy configuration mode, you can enter the main CPU submode to manually synchronize the configurations that are used by the two supervisor engines.
From the main CPU submode, you can use the auto-sync command to use all of the redundancy commands that are applicable to the main CPU.
To select the type of redundancy mode, use the mode command.
Nonstop forwarding (NSF) with stateful switchover (SSO) redundancy mode supports IPv4. NSF with SSO redundancy mode does not support IPv6, INternetwork Packet Exchange (IPX), and Multiprotocol Label Switching (MPLS).
Examples
The following example enables redundancy mode:
Router(config)# redundancyRouter(config-red)#The following example assigns the configured router shelf to the redundancy pair designated as 25. This command must be issued on both router shelves in the redundant router-shelf pair:
Router(config)# redundancyRouter(config-red)# failover group-number 25Cisco 10000 Series Router
The following example configures two 4-port channelized T3 half eight line cards that are installed in line card slot 2 for one-to-one redundancy:
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 2/1 primaryRouter(config-red-lc)# member subslot 2/0 secondaryCisco 7600 Series Router
The following example shows how to enter the main CPU submode:
Router (config)# redundancyRouter (config-r)# main-cpuRouter (config-r-mc)#Related Commands
redundancy force-switchover
To force the standby Route Processor (RP) to assume the role of the active RP, use the redundancy force-switchover command in privileged EXEC mode.
redundancy force-switchover [main-cpu]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Note
Use the redundancy force-switchover command to switch control of a router from the active RP to the standby RP. Both the active and standby RPs must have a high availability Cisco IOS image installed and must be configured for RPR redundancy mode before the redundancy force-switchover command can be used. Before the system switches over, it verifies that the standby RP is ready to take over.
When you use the redundancy force-switchover command and the current running configuration is different from the startup configuration, the system prompts you to save the running configuration before the switchover is performed.
On Cisco 7600 series routers, 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 a router Processor Redundancy Plus (RPR+) switchover. The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine.
Examples
The following example shows a switchover from the active RP to the standby RP on a Cisco 7513 router with RPR configured:
Router# configure terminalRouter(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# hw-module slot 6 image slot0:rsp-pv-mzRouter(config)# slave auto-sync configRouter(config)# redundancyRouter(config-r)# mode rprRouter(config-r)# endRouter# copy running-config startup-configRouter# redundancy force-switchoverThe following example shows how to perform a manual switchover from the active to the standby RP (NSE-100) when the running configuration is different from the startup configuration:
Router# redundancy force-switchoverSystem configuration has been modified. Save? [yes/no]:yBuilding configuration...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK]Proceed with switchover to standby NSE? [confirm]y00:07:35:%SYS-5-SWITCHOVER:Switchover requestedThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is the same as the startup configuration:
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]00:07:35:%SYS-5-SWITCHOVER:Switchover requestedRelated Commands
redundancy handover
To hand over control of resources (slots and cards) from a route-switch-controller (RSC) card to its peer RSC card, use the redundancy handover command in privileged EXEC mode.
redundancy handover {cancel | {peer-resources | shelf-resources}
[busyout-period mins] [at hh:mm [{day month | month day} year]]}Syntax Description
Defaults
Control remains with the assigned RSC.
Command Modes
Privileged EXEC
Command History
12.2(2)XB1
This command was introduced.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
To use this command, you must have two RSC cards installed on your Cisco AS5850 and you must be connected to one of them in handover-split mode. This command can be run from either RSC and can specify that slots be handed over to the peer RSC.
After handover and subsequent restoration of the failed RSC, connect to the active RSC and use this command to return control of cards to the previously failed but now restored RSC.
Note that when you enter the command with the shelf-resources option, the RSC reloads.
Examples
The following example hands over control, to the peer RSC, of the slots and cards on the corresponding side of the chassis. Note the prompt to confirm clearing of calls, handover, and reload on the last line.
Router# redundancy handover shelf-resources busyout-period 10 at 22:00 3 Sep 2005Newly entered handover schedule:Busyout period at 22:00:00 PDT Sat Sep 3 2005 for a duration of 10 minutesHandover pending at 22:10:00 PDT Sat Sep 3 2005Clear calls, handover and reload as specified above? yRelated Commands
redundancy stateful
To configure stateful failover for tunnels using IP Security (IPSec), use the redundancy stateful command in crypto map configuration mode. To disable stateful failover for tunnel protection, use the no form of this command.
redundancy standby-group-name stateful
no redundancy standby-group-name stateful
Syntax Description
Defaults
Stateful failover is not enabled for IPSec tunnels.
Command Modes
Crypto map configuration
Command History
Usage Guidelines
The redundancy stateful command uses an existing IPSec profile (which is specified via the crypto ipsec profile command) to configure IPSec stateful failover for tunnel protection. (You do not configure the tunnel interface as you would with a crypto map configuration.) IPSec stateful failover enables you to define a backup IPSec peer (secondary) to take over the tasks of the active (primary) router if the active router is deemed unavailable.
The tunnel source address must be a VIP address, and it must not be an interface name.
Examples
The following example shows how to configure stateful failover for tunnel protection:
crypto ipsec profile peer-profileredundancy HA-out statefulinterface Tunnel1ip unnumbered Loopback0tunnel source 209.165.201.3tunnel destination 10.0.0.5tunnel protection ipsec profile peer-profile!interface Ethernet0/0ip address 209.165.201.1 255.255.255.224standby 1 ip 209.165.201.3standby 1 name HA-outRelated Commands
crypto ipsec profile
Defines the IPSec parameters that are to be used for IPSec encryption between two routers and enters crypto map configuration mode.
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 in privileged EXEC mode.
remote command {module num | standby-rp | switch} command
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The module num keyword and argument designate the module number. Valid values depend on the chassis that is used. For example, if you have a 13-slot chassis, valid values are from 1 to 13. The module num keyword and argument are supported on DFC-equipped modules and the standby supervisor engine only.
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 show calendar command from the standby route processor:
Router# remote command standby-rp show calendarSwitch-sp#09:52:50 UTC Mon Nov 12 2001Router#Related Commands
remote login
Accesses the Catalyst 6500 series switch console or a specific module.
remote login
To access the Catalyst 6500 series switch console or a specific module, use the remote login command in privileged EXEC mode.
remote login {module num | standby-rp | switch}
Syntax Description
module num
Specifies the module to access; see the "Usage Guidelines" section for valid values.
standby-rp
Specifies the standby route processor.
switch
Specifies the active switch processor.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
The module num keyword and argument designate the module number. Valid values depend on the chassis that is used. For example, if you have a 13-slot chassis, valid values are from 1 to 13. The module num keyword and argument are supported on DFC-equipped modules and the standby 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.
When you execute the remote login standby-rp command, the prompt changes to Router-sdby#.
When you execute the remote login switch command, the prompt changes to Switch-sp#.
The remote login module num command is identical to the attach command.
There are two ways to end the session:
•
Switch-sp# exit[Connection to Switch closed by foreign host]Router#•
Switch-sp# ^CSwitch-sp# ^CSwitch-sp# ^CTerminate 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 1Trying Switch ...Entering CONSOLE for SwitchType "^C^C^C" to end this sessionSwitch-sp#This example shows how to perform a remote login to the Catalyst 6500 series switch processor:
Router# remote login switchTrying Switch ...Entering CONSOLE for SwitchType "^C^C^C" to end this sessionSwitch-sp#This example shows how to perform a remote login to the standby route processor:
Router# remote login standby-rpTrying Switch ...Entering CONSOLE for SwitchType "^C^C^C" to end this sessionRouter-sdby#Related Commands
remote-span
To configure a virtual local area network (VLAN) as a remote switched port analyzer (RSPAN) VLAN, use the remote-span command in config-VLAN mode. To remove the RSPAN designation, use the no form of this command.
remote-span
no remote-span
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Config-VLAN mode
Command History
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-spanRouter(config-vlan)This example shows how to remove the RSPAN designation:
Router(config-vlan)# no remote-spanRouter(config-vlan)Related Commands
reset (alarm-interface)
To reset the CPU in the alarm interface controller (AIC), use the reset command in alarm-interface mode.
reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Alarm-interface
Command History
12.2(2)XG
This command was introduced on the Cisco 2600 series and Cisco 3600 series.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Usage Guidelines
A change in the AIC IP configuration might not take effect until the next time the card is started. Use the reset command to restart the card. This command does not have a no form.
Examples
The following example shows a message that might be returned after the reset command is entered:
Router(alarm-aic)# resetSelected card in slot 1 restartedRelated Commands
retry
To define the amount of time that must elapse before a connection is attempted to a failed server, use the retry command in interface configuration mode. To change the connection-reassignment threshold and client threshold to the default settings, use the no form of this command.
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
Examples
This example shows how to specify a retry timer of 30 seconds:
Router(config)# ip slb serverfarm serverfarm-nameRouter(config-slb-sfarm)# real 10.1.1.1Cisco-7600(config-slb-real)# retry 30#This example shows how to revert to the default value:
Cisco-7600(config-slb-real)# no retryRouter(config-if)#Related Commands
ring-speed
To set the ring speed for the CSC-1R and CSC-2R Token Ring interfaces, use the ring-speed command in interface configuration mode.
ring-speed speed
Syntax Description
speed
Integer that specifies the ring speed, either 4 for 4-Mbps operation or 16 for 16-Mbps operation. The default is 16.
Defaults
16-Mbps operation
Caution
the ring to beacon, which makes the ring nonoperational.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command does not have a no form.
Examples
The following example shows how to sets the ring speed to 4 Mbps on a Token Ring interfaces:
Router(config)# interface tokenring 0Router(config-if)# ring-speed 4
