-
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
Interface and Hardware Component Commands
apply (satellite initial configuration)
Interface and Hardware Component Commands
alarm-interface
To enter alarm-interface mode and configure the alarm interface controller (AIC), use the alarm-interface command in global configuration mode. To leave alarm-interface mode, use the exit command.
alarm-interface slot-number
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.2(2)XG
This command was introduced for the Cisco 2600 series and the Cisco 3600 series.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Examples
The following examples show how the alarm-interface command is used in conjunction with the ip address and the reset commands:
Router(config)# alarm-interface 5Router(config-aic)# ip address 10.2.130.105A 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, as in the following example:
Router(config-aic)# resetAlarm Interface Card in slot 5 restartedRouter(config-aic)# endRelated Commands
ip address
Sets a primary or secondary IP address for an interface.
reset
Resets the AIC CPU.
als
To enable the Automatic Laser Shutdown (ALS) mode, use the als command in interface configuration mode. To disable ALS mode, use the no form of this command.
als
no als
Syntax Description
This command has no arguments or keywords.
Command Default
ALS is disabled.
Command Modes
Interface configuration (config-if)
Command History
12.2(33)SRD1
This command was introduced on the Cisco 7600 series router for the ES+ line cards.
Examples
The following example shows how to enable ALS:
Router> enableRouter# configure terminalRouter(config)# interface tengigabitethernet 2/1Router(config-if)# alsRelated Commands
als restart
To request an Automatic Laser Shutdown (ALS) restart mode, use the als restart command in interface configuration mode. To disable an ALS restart mode, use the no form of this command.
als restart {mode | pulse}
no als restart {mode | pulse}
Syntax Description
Command Default
Command default is automatic.
Command Modes
Interface configuration (config-if)
Command History
12.2(33)SRD1
This command was introduced on the Cisco 7600 series router for the ES+ line cards.
Examples
The following example restarts the ALS mode:
Router> enableRouter# configure terminalRouter(config)# interface tengigabitethernet 2/1Router(config-if)# alsRouter(config-if)# als restart modeRelated Commands
als restart mode
To select the Automatic Laser Shutdown (ALS) restart mode, use the als restart mode command in interface configuration mode. To reset to the command default mode, use the no form of this command.
als restart mode {automatic | manual}
no als restart mode {automatic | manual}
Syntax Description
Command Default
Command default is automatic.
Command Modes
Interface configuration (config-if)
Command History
12.2(33)SRD1
This command was introduced on the Cisco 7600 series router for the ES+ line cards.
Usage Guidelines
In manual restart, you request a single restart pulse from the ALS agent. In automatic restart, you configure the ALS agent to send a periodic restart pulse.
Examples
The following example shows how to select automatic mode:
Router> enableRouter# configure terminalRouter(config)# interface tengigabitethernet 2/1Router(config-if)# alsRouter(config-if)# als restart mode automaticRelated Commands
als restart pulse
To select the Automatic Laser Shutdown (ALS) pulse mode, use the als restart pulse command in inteface configuration mode. To disable an ALS pulse mode, use the no form of this command.
als restart pulse {interval seconds | width seconds}
no als restart pulse {interval seconds | width seconds}
Syntax Description
Command Default
Pulse interval default is 300 seconds.
Pulse width default is 200 seconds.Command Modes
Interface configuration (config-if)
Command History
12.2(33)SRD1
This command was introduced on the Cisco 7600 series router for the ES+ line cards.
Usage Guidelines
If a particular platform/OS/interface/controller has the capability to support two ranges, one range for Wave Division Multiplexing (WDM) and another for non-WDM, use the following pulse width ranges:
•
WDM: 60 - 200 (default: 100)
•
The recovery pulse interval is the period between the rising edge of pulses. The pulse interval needs to be greater than the pulse width. If a particular platform/OS/interface/controller has the capability to support two ranges, one range for WDM and another for non-WDM, use the following pulse width ranges:
•
•
Examples
The following example shows how to select an ALS pulse interval:
Router> enableRouter# configure terminalRouter(config)# interface tengigabitethernet 2/1Router(config-if)# alsRouter(config-if)# als restart modeRouter(config-if)# als restart mode automaticRouter(config-if)# als restart pulse interval 2000The following example shows how to select an ALS pulse width:
Router> enableRouter# configure terminalRouter(config)# interface tengigabitethernet 2/1Router(config-if)# alsRouter(config-if)# als restart modeRouter(config-if)# als restart mode automaticRouter(config-if)# als restart pulse width 200Related Commands
analysis-module monitoring
To enable Network Analysis Module (NAM) packet monitoring on an interface, use the analysis-module monitoring command in interface configuration mode. To disable NAM packet monitoring, use the no form of this command.
analysis-module monitoring
no analysis-module monitoring
Syntax Description
This command has no arguments or keywords.
Defaults
NAM packet monitoring is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable NAM packet monitoring on an interface, Cisco Express Forwarding (CEF) sends an extra copy of each IP packet that is received or sent on that interface to the NAM through the analysis module interface on the router and then through the internal NM-NAM interface.
Note
Interconnect (PCI) bandwidth. Therefore, Cisco recommends that you use the internal NAM interface
to monitor WAN interfaces and that you use the external NAM interface to monitor LAN interfaces.Examples
The following example shows how to enable NAM packet monitoring on a serial interface:
Router(config)# interface serial 0/0Router(config-if)# analysis-module monitoringapply (satellite initial configuration)
To save new or changed satellite initial configuration parameters and to reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the apply command in satellite initial configuration mode.
apply
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration mode
Command History
Usage Guidelines
The apply command saves any new or changed satellite initial configuration parameters to the nonvolatile memory of the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) and initiates a network module software reset. Commands entered in satellite initial configuration mode do not appear in the router configuration.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module's nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Note
Examples
The following example shows what appears when you enter the apply command after changing some initial configuration parameters:
Router(sat-init-config)# applyApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router(sat-init-config)#The following example shows what appears when you enter the apply command when no parameters have been changed:
Router(sat-init-config)# apply% No new or changed parameters to apply.Router(sat-init-config)#Related Commands
aps authenticate
To enable authentication and specify the string that must be present to accept any packet on the out-of-band (OOB) communications channel on a Packet-over-SONET (POS) interface, use the aps authenticate command in interface configuration mode. To disable authentication, use the no form of this command.
aps authenticate string
no aps authenticate
Syntax Description
string
Text that must be present to accept the packet on a protected or working interface. A maximum of eight alphanumeric characters are accepted.
Defaults
Authentication is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps authenticate command to ensure that only valid packets are accepted on the OOB communications channel.
The aps authenticate command must be configured on both the working and protect interfaces.
Examples
The following example shows how to enable authentication on POS interface 0 in slot 4:
Router# configure terminalRouter(config)# interface pos 4/0/0Router(config-if)# aps working 1Router(config-if)# aps authenticate sanjoseRouter(config-if)# endRelated Commands
aps protect
Enables a POS interface as a protect interface.
aps working
Configures a POS interface as a working interface.
aps clear sonet
To remove all externally initiated SONET automatic protection switching (APS) commands configured on a Cisco AS5850, use the aps clear sonet command in privileged EXEC mode.
aps clear sonet slot/port
Syntax Description
slot
Slot number on an STM-1 trunk card.
/port
SONET port number on an STM-1 trunk card. The slash mark is required between the slot argument and the port argument.
Defaults
No APS switch commands are removed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the aps clear sonet command to remove any SONET APS commands, such as the aps force sonet command, that could switch the working fiber to the protect fiber on an STM-1 trunk card.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to remove all externally initiated SONET APS switch commands:
Router# aps clear sonet 1/0Related Commands
aps force
To manually switch the specified circuit to a protect interface, unless a request of equal or higher priority is in effect, use the aps force command in interface configuration mode. To cancel the switch, use the no form of this command.
aps force circuit-number
no aps force circuit-number
Syntax Description
Defaults
No circuit is switched.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps force command to manually switch the interface to a protect interface when you are not using the aps revert command. For example, if you need to change the fiber connection, you can manually force the working interface to switch to the protect interface.
In a one-plus-one (1+1) configuration only, you can use the aps force 0 command to force traffic from the protect interface back onto the working interface.
The aps force command has a higher priority than any of the signal failures or the aps manual command.
The aps force command is configured only on protect interfaces.
Examples
The following example shows how to force the circuit on POS interface 0 in slot 3 (a protect interface) back onto a working interface:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps protect 10/30/1/1Router(config-if)# aps force 1Router(config-if)# endRelated Commands
aps force sonet
To force a specified port to switch to the alternate port within a redundant pair unless a request of equal or higher priority is in effect, use the aps force sonet command in privileged EXEC mode.
aps force sonet slot/port from {protection | working}
Syntax Description
Defaults
No port is switched.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Forced is a defined APS request priority level. The request succeeds if no higher priority request (lockout is the only higher priority request) is posted. The aps force sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface on which you want to issue the aps force sonet command. The aps force sonet command has a higher priority than any of the signal failures or the aps manual sonet command.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to force the protect port in the SONET controller to become an active port:
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps force sonet 1/0 from workingRelated Commands
aps group
To allow more than one protect and working interface to be supported on a router, use the aps group command in interface configuration mode. To remove a group, use the no form of this command.
aps group group-number
no aps group group-number
Syntax Description
Defaults
No groups exist.
Note
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps group command to specify more than one working and protect interfaces on a router, for example, working channel for group 0 and protect channel for group 1 on one router, and working channel for group 1 and protect channel for group 0 on another router.
The default group number is 0. The aps group 0 command does not imply that no groups exist.
The aps group command must be configured on both the protect and working interfaces.
Examples
The following example shows hw to configure two working/protect interface pairs. Working interface (3/0/0) is configured in group 10 (the protect interface for this working interface is configured on another router), and protect interface (2/0/1) is configured in group 20.
Router# configure terminalRouter(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.6 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 3/0/0Router(config-if)# aps group 10Router(config-if)# aps working 1Router(config-if)# exitRouter(config)# interface pos 2/0/1Router(config-if)# aps group 20Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# endOn the second router, protect interface (4/0/0) is configured in group 10, and working interface (5/0/0) is configured in group 20 (the protect interface for this working interface is configured on another router).
Router(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.7 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 4/0/0Router(config-if)# aps group 10Router(config-if)# aps protect 1 10.7.7.6Router(config-if)# exitRouter(config)# interface pos 5/0/0Router(config-if)# aps group 20Router(config-if)# aps working 1Router(config-if)# endRelated Commands
aps protect
Enables a POS interface as a protect interface.
aps working
Configures a POS interface as a working interface.
aps lockout
To prevent a working interface from switching to a protect interface, use the aps lockout command in interface configuration mode. To remove the lockout, use the no form of this command.
aps lockout circuit-number
no aps lockout circuit-number
Syntax Description
Defaults
No lockout exists.
Command Modes
Interface configuration
Command History
Usage Guidelines
The aps lockout command is configured only on protect interfaces.
Examples
The following example shows how to lock out POS interface 3/0/0 (that is, prevents the circuit from switching to a protect interface if the working circuit becomes unavailable):
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# aps lockout 1Router(config-if)# endRelated Commands
aps protect
Enables a POS interface as a protect interface.
aps working
Configures a POS interface as a working interface.
aps lockout sonet
To prevent a working port from switching to a protect port unless a request of equal or higher priority is in effect, use the aps lockout sonet command in privileged EXEC mode.
aps lockout sonet slot/port
Syntax Description
slot
Slot number on an STM-1 trunk card.
/port
SONET port number on an STM-1 trunk card. The slash mark is required between the slot argument and the port argument.
Defaults
No lockout exists; that is, a working port is not prevented from switching to a protect port.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Lockout is defined as the highest APS request priority level.
The aps lockout sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface from which the protect port is to be locked out. When the specified port is locked out, SONET APS switching from the working port is not allowed.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to lock out SONET port 1/0 (prevents SONET APS switching to a protect interface if the working circuit becomes unavailable):
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps lockout sonet 1/0Related Commands
aps manual
To manually switch a circuit to a protect interface, use the aps manual command in interface configuration mode. To cancel the switch, use the no form of this command.
aps manual circuit-number
no aps manual circuit-number
Syntax Description
Defaults
No circuit is switched.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps manual command to manually switch the interface to a protect interface. For example, you can use this feature when you need to perform maintenance on the working channel. If a protection switch is already up, you can also use the aps manual command to revert the communication link back to the working interface before the wait to restore (WTR) time has expired. The WTR time period is set by the aps revert command.
In a one-plus-one (1+1) configuration only, you can use the aps manual 0 command to force traffic from the protect interface back onto the working interface.
The aps manual command is a lower priority than any of the signal failures or the aps force command.
Examples
The following example shows how to force the circuit on POS interface 0 in slot 3 (a working interface) back onto the protect interface:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps working 1Router(config-if)# aps manual 1Router(config-if)# endRelated Commands
aps manual sonet
To manually switch to the alternate port within a redundant pair unless a request of equal or higher priority is in effect, use the aps manual sonet command in privileged EXEC mode.
aps manual sonet slot/port from {protection | working}
Syntax Description
Defaults
No port is switched.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the aps manual sonet command to manually switch the active port to the alternate port. For example, you can use this command when you need to perform maintenance on the working port.
Manual is a defined APS request priority level. The request succeeds if no higher priority request is posted. The aps manual sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface on which you want to issue the aps manual sonet command. The aps manual sonet command has a lower priority than any of the signal failures or the aps force sonet command.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to manually switch the working port, SONET port 1/0, to the protect port:
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps manual sonet 1/0 from workingRelated Commands
aps protect
To enable a POS interface as a protect interface, use the aps protect command in interface configuration mode. To remove the POS interface as a protect interface, use the no form of this command.
aps protect circuit-number ip-address
no aps protect circuit-number ip-address
Syntax Description
circuit-number
Number of the circuit to enable as a protect interface.
ip-address
IP address of the router that has the working POS interface.
Defaults
No circuit is protected.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps protect command to configure the POS interface used by a working interface if the working interface becomes unavailable because of a router failure, degradation or loss of channel signal, or manual intervention.
Caution
interface from becoming the active circuit and disabling the working circuit when it is finally discovered.
Examples
The following example shows how to configure circuit 1 on POS interface 5/0/0 as a protect interface for the working interface on the router with the IP address of 10.7.7.7. For information on how to configure the working interface, refer to the aps working command.
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# endRelated Commands
aps protect (SONET)
To enable automatic protection switching (APS) on a SONET port in an STM-1 trunk card, use the aps protect command in controller configuration mode. To disable APS on the SONET port, use the no form of this command.
aps protect
no aps protect
Syntax Description
This command has no arguments or keywords.
Defaults
APS is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the aps protect command to enable APS on a protect SONET port as a working port if the working port becomes unavailable because of a fiber failure, degradation or loss of channel signal, or manual intervention.
Examples
The following example shows how to enable APS on SONET port 0/1 in an STM-1 trunk card.
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRelated Commands
aps unidirectional
Configures a protect SONET port for unidirectional mode.
show controllers sonet
Displays information about SONET controllers.
aps revert
To enable automatic switchover from the protect interface to the working interface after the working interface becomes available, use the aps revert command in interface configuration mode. To disable automatic switchover, use the no form of this command.
aps revert minutes
no aps revert
Syntax Description
minutes
Number of minutes until the circuit is switched back to the working interface after the working interface is available.
Defaults
Automatic switchover is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps revert command to return the circuit to the working interface when it becomes available.
The aps revert command is configured only on protect interfaces.
Examples
The following example shows how to enable circuit 1 on POS interface 5/0/0 to revert to the working interface after the working interface has been available for 3 minutes:
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# aps revert 3Router(config-if)# endRelated Commands
aps timers
To change the time between hello packets and the time before the protect interface process declares a working interface router to be down, use the aps timers command in interface configuration mode. To return to the default timers, use the no form of this command.
aps timers seconds1 seconds2
no aps timers
Syntax Description
Defaults
Hello time is 1 second
Hold time is 3 seconds.Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps timers command to control the time between an automatic switchover from the protect interface to the working interface after the working interface becomes available.
Normally, the hold time is greater than or equal to three times the hello time.
The aps timers command is configured only on protect interfaces.
Examples
The following example shows how to specify a hello time of 2 seconds and a hold time of 6 seconds on circuit 1 on POS interface 5/0/0:
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps working 1Router(config-if)# aps timers 2 6Router(config-if)# endaps unidirectional
To configure a protect interface for unidirectional mode, use the aps unidirectional command in controller configuration or interface configuration mode. To return to the default, bidirectional mode, use the no form of this command.
aps unidirectional
no aps unidirectional
Syntax Description
This command has no arguments or keywords.
Defaults
Bidirectional mode
Command Modes
Controller configuration
Interface configurationCommand History
Usage Guidelines
The aps unidirectional command is configured only on protect interfaces.
Use the aps unidirectional command when you must interoperate with SONET network equipment, add/drop multiplexors (ADMs) that supports unidirectional mode.
Note
happens automatically when the SONET network equipment is in bidirectional mode.Examples
The following example shows how to configure POS interface 3/0/0 for unidirectional mode on a Cisco 12000 series router:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps unidirectionalRouter(config-if)# aps protect 1 10.7.7.7Router(config-if)# endThe following example shows how to configure SONET port 0/0 for unidirectional mode on a Cisco AS5850 universal gateway using an STM-1 trunk card:
Router# configure terminalRouter(config)# controller sonet 0/0Router(config-controller)# aps protectRouter(config-controller)# aps unidirectionalRouter(config-controller)# endaps working
To configure a Packet over SONET (POS) interface as a working interface, use the aps working command in interface configuration mode. To remove the protect option from the POS interface, use the no form of this command.
aps working circuit-number
no aps working circuit-number
Syntax Description
Defaults
No circuit is configured as working.
Command Modes
Interface configuration
Command History
Usage Guidelines
When a working interface becomes unavailable because of a router failure, degradation or loss of channel signal, or manual intervention, the circuit is switched to the protect interface to maintain the connection.
To enable the circuit on the protect interface to switch back to the working interface after the working interface becomes available again, use the aps revert command in interface configuration mode.
Caution
Examples
The following example shows how to configure POS interface 0 in slot 4 as a working interface. For information on how to configure the protect interface, refer to the aps protect command.
Router# configure terminalRouter(config)# interface pos 4/0/0Router(config-if)# aps working 1Router(config-if)# endRelated Commands
associate slot
To logically associate slots for automatic protection switching (APS) processor redundancy, use the associate slot command in redundancy configuration mode. To disable slot associations, use the no form of this command.
Single Router APS—Cisco 10000 Series Routers and Cisco uBR10012 Universal Broadband Router
associate slot slot-one [slot-two]
no associate slot slot-one [slot-two]
Multirouter APS—Cisco 10000 Series Routers
associate slot slot-one mr-aps
no associate slot slot-one mr-aps
Syntax Description
Defaults
No slots are associated.
Command Modes
Redundancy configuration
Command History
Usage Guidelines
Cisco 10000 Series Router
Use the associate command to associate two cards for single-router APS or multirouter APS redundancy protection. Multirouter APS support is specific to the Cisco 10000 series router. Use the mr-aps keyword in a multirouter APS configuration to allow a protect interface on a second router to be a backup for a working interface on the first router.
The associated slots must use the same type of interface module and must support APS redundancy. The cards also must be located in adjacent slots, for example slots 3 and 4.
Cisco uBR10012 Universal Broadband Router
The two cards must be in adjacent slots, with the working card in slot 1 or 3, and the backup card in slot 2 or 4, respectively. The two cards must be identical cards and must support APS redundancy (such as the OC-12 POS line card).
Note
Examples
Single Router APS Example
The following example shows how to associate two slots in the same router in a single router APS configuration:
redundancyassociate slot 3 4Multirouter APS Example on the Cisco 10000 Series Router Only
The following example shows how to associate two separate slots in different routers in a multirouter APS configuration:
! Associate slot 3 on first router for APS redundancy!redundancyassociate slot 3 mr-aps!! Associate slot 2 on second router for APS redundancy!redundancyassociate slot 2 mr-apsRelated Commands
association
To configure an association between current node and a remote node, use the association command in interprocess communication (IPC) zone configuration mode. To disable this functionality, use the no form of this command.
association association-ID
no association association-ID
Syntax Description
association-ID
Association ID assignment. The value range is from 1 through 255. The association ID must be unique within a specific zone.
Command Default
No association between a current node and a remote node exists.
Command Modes
IPC zone configuration
Command History
Usage Guidelines
Use the association command to configure an association between current node and a remote node. There can be multiple associations within a zone.
Examples
The following example configures an association with an ID of 1:
Router(config-ipczone)# association 1Related Commands
ipc zone default
Enters IPC zone configuration mode.
show ipc
Displays IPC statistics.
atm sonet
To set the mode of operation and thus control the type of the ATM cell used for cell-rate decoupling on the SONET physical layer interface module (PLIM), use the atm sonet command in interface configuration mode. To restore the default Synchronous Transport Signal level 12, concatenated (STS-12c) operation, use the no form of this command.
atm sonet [stm-4]
no atm sonet [stm-4]
Syntax Description
stm-4
(Optional) Synchronous Digital Hierarchy/Synchronous Transport Signal level 4 (SDH/STM-4) operation (ITU-T specification).
Defaults
STS-12c
Command Modes
Interface configuration
Command History
Usage Guidelines
Use STM-4 in applications in which SDH framing is required.
Use the default (STS-12c) in applications in which the ATM switch requires "unassigned cells" for rate adaptation. An unassigned cell contains 32 zeros.
Examples
The following example shows how to set the mode of operation to SONET STM-4 on ATM interface 3/0:
Router(config)# interface atm 3/0Router(config-if)# atm sonet stm-4Router(config-if)# endau-3
To configure a particular Administrative Unit type 3 (AU-3) of an E1 line that has been mapped to an AU-3, use the au-3 command in controller configuration mode.
au-3 au-3-number
Syntax Description
Defaults
No default behavior or values
Command Modes
Controller configuration
Command History
Usage Guidelines
An administrative unit group (AUG) of an STM-1 can be derived from either AU-3s or an AU-4. Use the aug mapping au-3 configuration controller command to map the AUG to an AU-3 with the following muxing/alignment/mapping:
C-12 <--> VC-12 <--> TU-12 <--> TUG-2 <--> VC-3 <--> AU-3 <--> AUG
Configuring the au-3 command enables you to enter configuration controller au3 command mode and creates a serial interface with the following name format:
slot/port-adapter/port.au-3-number/tug-2-number/e1-number
The aug mapping au-3 and au-3 commands are available only when Synchronous Digital Hierarchy (SDH) framing is configured.
Examples
The following example shows how to configure AUG mapping to be derived from an AU-3 and selects AU-3 3 to configure as a serial interface:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-3Router(config-ctrlr-au3)# au-3 3Related Commands
au-4 tug-3
Specifies a TUG-3 for configuration.
aug mapping
Configures the AUG mapping mode of the PA-MC-STM-1 to AU-3.
au-4 tug-3
To specify the Administrative Unit type 4 (AU-4) and Tributary Unit group type 3 (TUG-3) number of an E1 line that has been mapped to an AU-4, use the au-4 tug-3 command in controller configuration mode.
au-4 au-4-number tug-3 tug-3-number
Syntax Description
au-4-number
Number in the range from 1 to x where x is the STM level. Default is 1.
tug-3-number
Number in the range from 1 to 3.
Defaults
Default au-4-number value for the STM-1 card is 1.
Command Modes
Controller configuration
Command History
Usage Guidelines
An AUG of an STM-1 can be derived from either AU-3s or an AU-4. Use the aug mapping au-4 configuration controller command to map the AUG to a TUG-3 with the following muxing/alignment/mapping:
C-12 <--> VC-12 <--> TU-12< --> TUG-2 <--> TUG-3 <--> VC-4 <--> AU-4 <--> AUG
Configuring the au-4 command enables you to enter configuration controller tug3 command mode and creates a serial interface with the following name format:
slot/port-adapter/port.au-4-number/tug-2-number/e1-number
The aug mapping au-4 and au-4 tug-3 commands are available only when SDH framing is configured.
Examples
The following example shows how to configure AUG mapping to be derived from a TUG-3 and selects TUG-3 1 of AU-4 1:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-ctrlr-tug3)# au-4 1 tug-3 1Related Commands
au-3
Specifies an AU-3 for configuration.
aug mapping
Configures the AUG mapping mode.
aug mapping
To configure administrative unit group (AUG) mapping when Synchronous Digital Hierarchy (SDH) framing is selected, use the aug mapping command in controller configuration mode.
aug mapping {au-3 | au-4}
Syntax Description
Defaults
au-4
Command Modes
Controller configuration
Command History
Usage Guidelines
In SDH, there are two possible mapping/multiplexing schemes for most payload types: ANSI and ETSI.
In ANSI mapping, the Low Order payloads are aggregated into a VC-3 High Order Path. An AU pointer is added to the VC-3 to create an AU-3. Three such AU-3s are then synchronously multiplexed into an AUG. The multiplexing scheme is as follows:
... VC-3 <-> AU-3 (x3) <-> AUG <-> STM-1
SDH ANSI mapping is very similar to the SONET frame structure.
In ETSI mapping, the Low Order payloads are aggregated into a VC-4 High Order Path. An AU pointer is added to the VC-4 to create an AU-4 (Administrative Unit type 4). One AU-4 is "multiplexed" into an AUG (AU group), which is to say, the AUG is, in fact, equivalent to an AU-4. The multiplexing scheme is as follows:
... TUG-3 (x3) <-> VC-4 <-> AU-4 (x1) <-> STM-1
This command is available only when SDH framing is configured.
This command does not have a no form because data must flow using one of the two mapping/multiplexing schemes.
Examples
The following example shows how to configure AU-3 mapping for the STM-1 trunk card:
Router(config)# controller sonet 1/0Router(config-controller)# aug mapping au-3auto-polarity
To enable automatic receiver polarity reversal on a hub port connected to an Ethernet interface of a Cisco 2505 or Cisco 2507 router, use the auto-polarity command in hub configuration mode. To disable this function, use the no form of this command.
auto-polarity
no auto-polarity
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Hub configuration
Command History
Usage Guidelines
This command applies to a port on an Ethernet hub only.
Examples
The following example shows how to enable automatic receiver polarity reversal on hub 0, ports 1 through 3:
Router(config)# hub ethernet 0 1 3Router(config-hub)# auto-polarityRelated Commands
hub
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
b2 sd-ber
To set the signal degrade bit-error rate (BER) threshold values, use the b2 sd-ber command in controller configuration mode. To return to the default setting, use the no form of this command.
b2 sd-ber rate
no b2 sd-ber
Syntax Description
rate
Bit-error rate from 3 to 9 (10-n). The value of 9 represents better quality, and the value of 3 represents lower quality. The default is 6.
Defaults
rate: 6
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the threshold for degradation of quality of signal with b2 errors.
Examples
The following example shows how to configure a signal degrade BER threshold value of 7 on the SONET controller:
Router(config)# controller sonet 1/0Router(config-controller)# b2 sd-ber 7Related Commands
b2 sf-ber
To set the signal failure bit-error rate (BER) threshold values, use the b2 sf-ber command in controller configuration mode. To return to the default setting, use the no form of this command.
b2 sf-ber rate
no b2 sf-ber rate
Syntax Description
rate
Bit-error rate from 3 to 9 (10-n). The value of 9 represents better quality, and the value of 3 represents lower quality. The default is 3.
Defaults
rate: 3
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the threshold for failure of quality of signal with b2 errors. The value of 9 represents better quality and the value of 3 represents lower quality.
Examples
The following example shows how to configure a signal failure BER threshold value of 7 on the SONET controller:
Router(config)# controller sonet 1/0Router(config-controller)# b2 sf-ber 7Related Commands
backup delay
To define how much time should elapse before a secondary line status changes after a primary line status has changed, use the backup delay command in interface configuration mode. To return to the default so that as soon as the primary fails, the secondary is immediately brought up without delay, use the no form of this command.
backup delay {enable-delay-period | never} {disable-delay-period | never}
no backup delay {enable-delay-period | never} {disable-delay-period | never}
Syntax Description
Defaults
0 second delay
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRB1
This command was integrated into Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
For environments in which spurious signal disruptions appear as intermittent lost carrier signals, we recommend that you enable some delay before activating and deactivating a secondary line.
For the Cisco 7600 Backup Interface for Flexible UNI feature to work correctly, the enable and disable backup delay must be 0.
Examples
The following example sets a 10-second delay on deactivating the secondary line (serial interface 0); however, the line is activated immediately.
interface serial 0backup delay 0 10backup interface
To configure an interface as a secondary or dial backup, use the backup interface command in interface configuration mode. To disable the interface from serving as a backup, use the no form of this command.
Cisco 7200 Series and Cisco 7500 Series Routers Only
backup interface slot/port-adapter/port
no backup interface slot/port-adapter/port
Other Cisco Routers
backup interface type number
no backup interface type number
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
11.0
This command was introduced.
12.2(33)SRB1
This command was integrated into Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
The interface you define with this command can back up only one other interface.
Routers support only serial and ISDN backup interfaces. Access servers support both asynchronous and serial backup interfaces.
In Cisco IOS Release 12.2(33)SRB1 and later releases, you can configure a backup interface for Gigabit Ethernet on the Cisco 7600 router. The configurations on the primary and backup interfaces must match or the backup interface does not work. Note, however, that if the interface configuration includes the xconnect command, you must specify a different virtual circuit ID (VCID) on the primary and backup interfaces.
Examples
The following example sets serial 1 as the backup line to serial 0:
interface serial 0backup interface serial 1The following example sets gigabitEthernet4/0/1 as the backup interface for gigabitEthernet3/0/1 on the Cisco 7600 router:
interface gigabitEthernet 3/0/1backup interface gigabitEthernet 4/0/1Related Commands
backup interface atm
To back up a locally switched ATM connection, use the backup interface atm command in the connect submode. To deconfigure the active routing policy set, leaving the SBE with no active routing policy set, use the no form of this command.
backup interface atm x/y/z vpi/vci
no backup interface atm x/y/z vpi/vci
Syntax Description
Defaults
No default behavior or values.
Command Modes
Connect submode (config-connection)
Command History
Usage Guidelines
•
•
•
•
Examples
The following is an example of a ATM virtual path local switching backup:
Router(config)# connect ATM atm2/0/0 0 atm3/0/0 0Router(config-connection)# backup interface atm 4/0/0 1The following is an example of a ATM virtual channel local switching backup:
Router(config)# connect ATM atm2/0/0 24/56 atm3/0/0 24/57Router(config-connection)# backup interface atm 4/0/0 25/58Related Commands
backup interface cem
To back up a locally switched CEM connection, use the backup interface cem command in the connect submode. To deconfigure the locally switched CEM connection backup, use the no form of this command.
backup interface cem x/y/z cemckt
no backup interface cem x/y/z cemckt
Syntax Description
interface
Identifies the interface.
cem x/y/z
Specifies the CEM interface slot, subslot, and port to be backed up.
cemckt
Specifies the backup location for the CEM.
Defaults
No default behavior or values.
Command Modes
Connect submode (config-connection)
Command History
Usage Guidelines
•
•
•
•
•
•
•
Examples
The following is an example of a CEM local switching backup:
Router(config)# connect cema cem4/3/0 0 cem2/0/0 0Router(config-connection)# backup interface cem 2/0/0 1Related Commands
backup load
To set a traffic load threshold for dial backup service, use the backup load command in interface configuration mode. To return to the default value, use the no form of this command.
backup load {enable-threshold | never} {disable-load | never}
no backup load {enable-threshold | never} {disable-load | never}
Syntax Description
Defaults
No threshold is defined.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRB1
This command was integrated into Cisco IOS Release 12.2(33)SRB1.
Usage Guidelines
When the transmitted or received load on the primary line is greater than the value assigned to the enable-threshold argument, the secondary line is enabled.
The secondary line is disabled when one of the following conditions occurs:
•
•
If the never keyword is used instead of an enable-threshold argument, the secondary line is never activated because of traffic load. If the never keyword is used instead of a disable-load argument, the secondary line is never activated because of traffic load.
Examples
The following example sets the traffic load threshold to 60 percent of the primary line serial 0. When that load is exceeded, the secondary line is activated and will not be deactivated until the combined load is less than 5 percent of the primary bandwidth.
interface serial 0backup load 60 5backup interface serial 1bandwidth (interface)
To set the inherited and received bandwidth values for an interface, use the bandwidth command in interface configuration mode. To restore the default values, use the no form of this command.
bandwidth {kbps | inherit [kbps] | receive[kbps]}
no bandwidth {kbps | inherit [kbps] | receive[kbps]}
Syntax Description
Command Default
Default bandwidth values are set during startup. The bandwidth values can be displayed using the show interfaces or show ipv6 interface command. If the receive keyword is not used, by default, the transmit and receive bandwidths are the same.
Command Modes
Interface configuration
Command History
Usage Guidelines
Bandwidth Information
The bandwidth command sets an informational parameter to communicate only the current bandwidth to the higher-level protocols; you cannot adjust the actual bandwidth of an interface using this command.
Note
Changing Bandwidth
For some media, such as Ethernet, the bandwidth is fixed; for other media, such as serial lines, you can change the actual bandwidth by adjusting hardware. For both classes of media, you can use the bandwidth command to communicate the current bandwidth to the higher-level protocols.
Bandwidth Inheritance
Before the introduction of the bandwidth inherit command option, when the bandwidth value was changed on the main interface, existing subinterfaces did not inherit the bandwidth value from the main interface. If the subinterface was created before the bandwidth was changed on the main interface, then the subinterface would receive the default bandwidth of the main interface, not the configured bandwidth. Additionally, if the router was subsequently reloaded, the bandwidth of the subinterface would then change to the bandwidth configured on the main interface.
The bandwidth inherit command controls how a subinterface inherits the bandwidth of its main interface. This functionality eliminates the inconsistencies related to whether the router has been reloaded and what the order was in entering the commands.
The no bandwidth inherit command enables all subinterfaces to inherit the default bandwidth of the main interface, regardless of the configured bandwidth. If a bandwidth is not configured on a subinterface, and you use the bandwidth inherit command, all subinterfaces will inherit the current bandwidth of the main interface. If you configure a new bandwidth on the main interface, all subinterfaces will use this new value.
If you do not configure a bandwidth on the subinterface and you configure the bandwidth inherit kbps command on the main interface, the subinterfaces will inherit the specified bandwidth.
In all cases, if an interface has an explicit bandwidth setting configured, then that interface will use that setting, regardless of whether the bandwidth inheritance setting is in effect.
Bandwidth Receipt
Some interfaces (such as ADSL, V.35, RS-449, and HSSI serial interfaces) can operate with different transmit and receive bandwidths. The bandwidth receive command permits this type of asymmetric operation. For example, for ADSL, the lower layer detects the two bandwidth values and configures the IDB accordingly. Other interface drivers, particularly serial interface cards on low- and midrange-platforms) can operate in this asymmetric bandwidth mode but cannot measure their clock rates. In these cases, administrative configuration is necessary for asymmetric operations.
Examples
The following example shows how to set the full bandwidth for DS3 transmissions:
Router(config)# interface serial 0Router(config-if)# bandwidth 44736The following example shows how to set the receive bandwidth:
Router(config)# interface serial 0Router(config-if)# bandwidth receive 1000Related Commands
show interfaces
Displays statistics for all interfaces configured on the router.
show ipv6 interface
Displays statistics for all interfaces configured on the IPv6 router.
bert abort
To end a bit error rate testing session, use the bert abort command in privileged EXEC mode.
bert abort
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the bert abort command to cancel bit error rate testing on each port of the Cisco AS5300 router.
The bit error rate test (BERT) feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern.
Examples
The following is sample output from the bert abort command when no bit error rate test is running:
Router# bert abortRouter#17:53:33: There is no BERT Test running ....The following is sample output from the bert abort command when a bit error rate test is running:
Router# bert abortDo you really want to abort the current BERT [confirm] Y17:56:56: %BERT-6-BERT_RESULTS: Controller T1 0 Profile default : The Test wasaborted by UserRelated Commands
Starts a bit error rate test for a particular port.
Sets up various bit error rate testing profiles.
bert controller
To start a bit error rate test (BERT) for a particular port, use the bert controller command in privileged EXEC mode.
bert controller [type-controller] {last-controller | profile [number | default]}
Syntax Description
Defaults
number: 0
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the bert controller command to start a bit error rate test for a particular port on a Cisco AS5300 router.
Quality Testing
The BERT feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern.
E1 Controllers
The E1 controller cannot be set in loopback mode from the Cisco AS5300. For the bert controller command to work correctly with the E1 controller, the controller must be configured as a channel group or channel-associated signaling (CAS) and the line must be configured as a remote loop from the switch side of the link.
Examples
The following is sample output from the bert controller command:
Router# bert controller T1 profile defaultPress <Return> to start the BERT [confirm] Y17:55:34: %BERT-6-BERT_START: Starting BERT on Interface 0 with Profile defaultData in current interval (10 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTable 1 describes the significant fields shown in the display.
Related Commands
bert abort
Aborts a bit error rate testing session.
bert pattern (T1/E1)
Sets up various bit error rate testing profiles.
bert errors
To transmit bit error ratio test (BERT) errors while running any BERT pattern, use the bert error command in interface configuration mode.
bert errors [number]
Syntax Description
Defaults
Default is 1.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to test link availability by injecting a fixed number of bert errors when a pattern is running and check that the same number of errors were received on the remote end.
Examples
This example injects 200 BERT errors in a running bit pattern on slot 5, subslot 0.
Router# configure terminalRouter(config)# interface serial 5/0/0Router(config-if)# bert errors 200Related Commands
bert pattern
Starts a BERT pattern on a port.
show controller serial
Displays serial line statistics.
bert pattern
To start a BERT pattern on a port, use the bert pattern command in interface configuration mode. Use the no bert pattern command to stop the sequence.
bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1 | qrss} interval minutes}
no bert pattern {0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1 | qrss} interval minutes}
Syntax Description
Defaults
Bert is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the bert pattern commamd to start or stop a specific bit pattern. To test link availability, start a pattern on one end and put the remote end in network loopback and verify that there are no bert errors.
Examples
This example starts a bert pattern on slot 5, bay 0.
Router# configure terminalRouter(config)# int serial 5/0/0Router(config-if)# bert pattern 0sRelated Commands
bert pattern (T1/E1)
To enable a bit error rate test (BERT) pattern on a T1 or E1 line, use the bert pattern command in controller configuration mode. To disable a BER test pattern, use the no form of this command.
bert pattern pattern interval time
no bert pattern pattern interval time
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
BER testing is supported on each of the T1 or E1 lines, is done only over an unframed T1 or E1 signal, and is run on only one port at a time.
To view the BER test results, use the show controllers atm EXEC command. The BERT results include the following information:
•
•
•
•
•
•
When the T1 or E1 line has a BER test running, the line state is DOWN and the status field shows the current/last result of the test.
The bert pattern command is not written to NVRAM because this command is only used to test the T1 or E1 line for a short predefined interval, and to avoid accidentally saving the command.
Examples
The following example shows how to run a BERT pattern of all zeros on a Cisco 7200 series router for 30 minutes on the T1 controller in slot 1:
Router(config)# controller T1 1/0Router(config-if)# bert pattern 0s interval 30Related Commands
show controllers atm
Displays information about T1/E1 links in Cisco 7100 series routers, Cisco 7200 series routers, and Cisco 7500 series routers.
bert pattern (T3/E3)
To enable a bit error rate test (BERT) pattern on a T3 or E3 controller, use the bert pattern command in controller configuration mode. To disable a BER test pattern, use the no form of this command.
bert pattern pattern interval time
no bert pattern
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
BER testing is supported on T3/E3 links and is done only over framed T3 or E3 signals, unless E3 framing is in bypass mode.
To display the BER test results, use the show controllers t3 or show controllers e3 EXEC command. The BER test results include the following information:
•
•
•
•
•
•
When the T3 or E3 line has a BER test running, the line state is DOWN and the status field shows the current or last result of the test.
The bert pattern command is not written to NVRAM because this command is used only to test the T3 or E3 line for a short predefined interval, and to avoid accidentally saving the command.
Examples
The following example shows how to run a BERT pattern of all zeros for 30 minutes on the T3 controller in slot 1:
Router(config)# controller T3 1/0Router(config-if)# bert pattern 0s interval 30Related Commands
show controllers e3
Displays information about E3 controllers.
show controllers t3
Displays information about T3 controllers.
bert profile
To set up various bit error rate testing profiles, use the bert profile command in global configuration mode. To disable the particular bit error rate test (BERT) profile indicated by profile number, use the no form of this command.
bert profile number pattern pattern threshold threshold error-injection err-inj duration time
no bert profile number pattern pattern threshold threshold error-injection err-inj duration time
Syntax Description
Defaults
The default profile created internally by the system has parameters that cannot be changed. This profile has been defined so that you can execute BERT on a line without having to configure a new profile. The default profile is displayed when the running configuration is displayed and is not stored in NVRAM:
bert profile number pattern 220-0151QRSS threshold 10^-6 error-injection none duration 10
Command Modes
Global configuration
Command History
Usage Guidelines
Use the bert profile command to set up bit error rate testing profiles for the Cisco AS5300 router.
The bit error rate test (BERT) feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern. A BERT profile is a set of parameters related to a BERT test and is stored as part of the configuration in NVRAM. You can define up to 15 BERT profiles on the system. By setting up the BERT profiles in this way, you do not have to enter the parameters each time you want to run a BERT—just select the number of the BERT profile that you want to run.
Examples
The following example shows a configured BERT profile number 1 to have a 0s test pattern, with a 10-2 threshold, no error injection, and a duration of 125 minutes:
Router(config)# bert profile 1 pattern 0s threshold 10^-2 error-injection none duration 125Related Commands
Aborts a bit error rate testing session.
Starts a bit error rate test for a particular port.
bridge-domain
To enable RFC 1483 ATM bridging or RFC 1490 Frame Relay bridging to map a bridged VLAN to an ATM permanent virtual circuit (PVC) or Frame Relay data-link connection identifier (DLCI), use the bridge-domain command in Frame Relay DLCI configuration, interface configuration, interface ATM VC configuration, or PVC range configuration mode. To disable bridging, use the no form of this command.
bridge-domain vlan-id [access | dot1q [tag] | dot1q-tunnel] [broadcast] [ignore-bpdu-pid] [pvst-tlv CE-vlan] [increment] [lan-fcs] [split-horizon]
no bridge-domain vlan-id
Syntax Description
Defaults
Bridging is disabled.
Command Modes
Frame Relay DLCI configuration
Interface configuration—Only the dot1q and dot1q-tunnel keywords are supported in interface configuration mode.
Interface ATM VC configuration
PVC range configurationCommand History
Usage Guidelines
RFC 1483 bridging on ATM interfaces supports the point-to-point bridging of Layer 2 packet data units (PDUs) over Ethernet networks. RFC 1490 Frame Relay bridging on Packet over SONET (POS) or serial interfaces that are configured for Frame Relay encapsulation provides bridging of Frame Relay packets over Ethernet networks.
The Cisco 7600 router can transmit BPDUs with a PID of either 0x00-0E or 0x00-07. When the router connects to a device that is fully compliant with RFC 1483 Appendix B, in which the IEEE BPDUs are sent and received by the other device using a PID of 0x00-0E, you must not use the ignore-bpdu-pid keyword.
If you do not enter the ignore-bpdu-pid keyword, the PVC between the devices operates in compliance with RFC 1483 Appendix B. This is referred to as strict mode. Entering the ignore-bpdu-pid keyword creates loose mode. Both modes are described as follows:
•
•
Cisco-proprietary PVST+ BPDUs are always sent out on data frames using a PID of 0x00-07, regardless of whether you enter the ignore-bpdu-pid keyword.
Use the ignore-bpdu-pid keyword when connecting to devices such as ATM digital subscriber line (DSL) modems that send PVST (or 802.1D) BPDUs with a PID of 0x00-07.
The pvst-tlv keyword enables BPDU translation when the router interoperates with devices that understand only PVST or IEEE Spanning Tree Protocol. Because the Catalyst 6500 series switch ATM modules support PVST+ only, you must use the pvst-tlv keyword when connecting to a Catalyst 5000 family switch that understands only PVST on its ATM modules, or when connecting with other Cisco IOS routers that understand IEEE format only.
When the router or switch is transmitting, the pvst-tlv keyword translates PVST+ BPDUs into IEEE BPDUs.
When the router or switch is receiving, the pvst-tlv keyword translates IEEE BPDUs into PVST+ BPDUs.
Note
To preserve class of service (CoS) information across the ATM network, use the dot1q option. This configuration uses IEEE 802.1Q tagging to preserve the VLAN ID and packet headers as they are transported across the ATM network.
To enable service providers to use a single VLAN to support customers that have multiple VLANs, while preserving customer VLAN IDs and segregating traffic in different customer VLANs, use the dot1q-tunnel option on the service provider router. Then use the dot1q option on the customer routers.
Note
RFC 1483 bridging is supported on AAL5-MUX and AAL5-LLC Subnetwork Access Protocol (SNAP) encapsulated PVCs. RFC-1483 bridged PVCs must terminate on the ATM interface, and the bridged traffic must be forwarded over an Ethernet interface, unless the split-horizon option is used, which allows bridging of traffic across bridged PVCs.
Note
In interface configuration mode, only the dot1q and dot1q-tunnel keyword options are supported.
Examples
The following example shows a PVC being configured for IEEE 802.1Q VLAN bridging using a VLAN ID of 99:
Router# configure terminalRouter(config)# interface ATM6/2Router(config-if)# pvc 2/101Router(config-if-atm-vc)# bridge-domain 99 dot1qRouter(config-if-atm-vc)# endThe following example shows how to enable BPDU translation when a Catalyst 6500 series switch is connected to a device that understands only IEEE BPDUs in an RFC 1483-compliant topology:
Router(config-if-atm-vc)# bridge-domain 100 pvst-tlv 150The ignore-bpdu-pid keyword is not used because the device operates in an RFC 1483-compliant topology for IEEE BPDUs.
The following example shows how to enable BPDU translation when a Catalyst 5500 ATM module is a device that understands only PVST BPDUs in a non-RFC1483-compliant topology. When a Catalyst 6500 series switch is connected to a Catalyst 5500 ATM module, you must enter both keywords.
Router(config-if-atm-vc)# bridge-domain 100 ignore-bpdu-pid pvst-tlv 150To enable BPDU translation for the Layer 2 Protocol Tunneling (L2PT) topologies, use the following command:
Router(config-if-atm-vc)# bridge-domain 100 dot1q-tunnel ignore-bpdu-pid pvst-tlv 150The following example shows a range of PVCs being configured, with the bridge domain number being incremented for each PVC in the range:
Router(config)# interface atm 8/0.100Router(config-subif)# range pvc 102/100 102/199Router(config-if-atm-range)# bridge-domain 102 incrementRelated Commands
bre-connect
Enables the BRE over a PVC or SVC.
show atm pvc
Displays the configuration of a particular PVC.
bridge-domain (subinterface)
To enable bridging across Gigabit Ethernet subinterfaces, use the bridge-domain command in subinterface configuration mode. To disable bridging, use the no form of this command.
bridge-domain vlan-id {dot1q | dot1q-tunnel} [bpdu {drop | transparent}] [split-horizon]
no bridge-domain vlan-id {dot1q | dot1q-tunnel} [bpdu {drop | transparent}] [split-horizon]
Syntax Description
vlan-id
Specifies the number of the virtual LAN (VLAN) to be used in this bridging configuration. The valid range is from 2 to 4094.
dot1q
Enables IEEE 802.1Q tagging to preserve the class of service (CoS) information from the Ethernet frames across the ATM network. If not specified, the ingress side assumes a CoS value of 0 for QoS purposes.
dot1q-tunnel
Enables IEEE 802.1Q tunneling mode, so that service providers can use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
bpdu {drop | transparent}
(Optional) Specifies whether or not BPDUs are processed or dropped:
•
•
split-horizon
(Optional) Enables RFC 1483 split horizon mode to globally prevent bridging between PVCs in the same VLAN.
Defaults
Bridging is disabled.
Command Modes
Subinterface configuration
Command History
Usage Guidelines
This command has the following restrictions in Cisco IOS Release 12.2(33)SRA:
•
•
To enable service providers to use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated, use the dot1q-tunnel option on the service provider router. Then use the dot1q option on the customer routers.
Examples
The following example shows configuration of IEEE 802.1Q encapsulation for VLANs on Gigabit Ethernet subinterfaces with configuration of multipoint bridging (MPB). The MPB feature requires configuration of 802.1Q encapsulation on the subinterface.
The first subinterface bridges traffic on VLAN 100 and preserves CoS information in the packets by specifying the dot1q keyword.
Router(config)# interface GigabitEthernet 1/0/1.1Router(config-subif)# encapsulation dot1q 10Router(config-subif)# bridge-domain 100 dot1qThe second subinterface shows bridging of traffic on VLAN 200 in tunneling mode using the dot1q-tunnel keyword, which preserves the VLAN IDs of the bridged traffic.Router(config)# interface GigabitEthernet 2/0/2.2Router(config-subif)# encapsulation dot1q 20Router(config-subif)# bridge-domain 200 dot1q-tunnelThe following example shows bridging of traffic from different VLANs on two separate Gigabit Ethernet subinterfaces into the same VLAN. First, the bridging VLAN 100 is created using the vlan command. Then, the Gigabit Ethernet subinterfaces implement IEEE 802.1Q encapsulation on VLAN 10 and VLAN 20 and bridge the traffic from those VLANs onto VLAN 100 using the bridge-domain command:
Router(config)# vlan 100Router(config-vlan)# exit!Router(config)# interface GigabitEthernet 1/0/1.1Router(config-subif)# encapsulation dot1q 10Router(config-subif)# bridge-domain 100 dot1qRouter(config-subif)# exit!Router(config)# interface GigabitEthernet 1/0/2.1Router(config-subif)# encapsulation dot1q 20Router(config-subif)# bridge-domain 100 dot1qRelated Commands
