|
|
This publication contains instructions for installing and configuring the Cisco OC-12 ATM line card on a Cisco 10000 Edge Services Router (ESR). If you are not familiar with the Cisco 10000 router, see the Cisco 10000 ESR System Description, and the Cisco 10000 ESR Hardware Installation Guide for additional information.
The following sections are included in this configuration guide:
The OC-12 ATM line card is a trunk uplink for the Cisco 10000 which provides IP packet routing over ATM virtual circuit connections using a single mode fiber intermediate reach SC connector (Figure 1).
The OC-12 ATM line card is a standard implementation of ATM over SONET switching and supports the following features:
Before you perform any of the procedures in this guide, we recommend that you:
Before you begin the line card installation procedure, review the safety guidelines in this section to avoid injuring yourself or damaging the equipment. Before you install, configure, or perform maintenance on the router, you should also review the safety warnings listed in the Cisco 10000 ESR Hardware Installation Guide.
Safety warnings appear throughout this publication in procedures that, if performed incorrectly, may harm you. A warning symbol precedes each warning statement. The following warning is an example of a safety warning. It identifies the warning symbol and associates it with a bodily injury hazard.
 |
Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device. |
 |
Note If you need translations of the safety warning, see the Cisco 10000 ESR Hardware Installation Guide. |
This section contains guidelines for the following:
The Cisco 10000 system is hot-swappable, which means you can remove and replace line cards while the system is operating. It is not necessary to notify the software or reset the system power. This feature allows you to add, remove, or replace line cards while the system maintains all routing information and ensures session preservation.
 |
Caution To avoid erroneous failure messages, remove or insert only one line card at a time. Also, after you insert or remove a line card, allow at least 15 seconds before you insert or remove another line card so that the system can reinitialize and note the current configuration of all interfaces. |
|
Caution To prevent electrostatic discharge (ESD) damage, handle line cards by the faceplate or the card carrier edges only. Avoid touching the line card printed circuit board, components, or any connector pins. |
You must configure a new installation of the OC-12 ATM line card using the configure command. For information about configuring the OC-12 ATM line card, see the Cisco 10000 ESR Software Configuration Guide.
If an OC-12 ATM line card is replaced (in the same slot), the system automatically downloads the necessary configuration information from the PRE; there is no need to configure the new line card. After the information is downloaded, the system recognizes only those interfaces that match the previous OC-12 ATM line card configuration (those configured as Up).
You need the following tools and equipment to install the OC-12 ATM line card:
This section describes how to install or replace the OC-12 line card in the Cisco 10000 chassis. It contains the following procedures:
Use the following procedure to remove the front cover from the system. If your system does not use a front cover, go to the "Installing an OC-12 ATM Line Card" section.
Repeat this procedure for all four bezel plugs and then remove the plugs.
Step 2 Remove the cover by lifting it up slightly and then pulling it toward you (Figure 3).
Use the following procedure to install the OC-12 ATM line card into any of the eight line card slots (slots 1through 4 and slots 5 through 8) available in the Cisco 10000 chassis.
|
Note If you are replacing the OC-12 ATM line card, see the "Removing an OC-12 ATM Line Card" section before you begin this procedure. |
Step 2 Loosen the top and bottom captive screws on the blank faceplate and slide it out of the slot (Figure 5).
Step 3 Grasp the faceplate of the line card with one hand and place your other hand under the card carrier (to support the weight of the card). Position the card in front of the card cage slot.
Step 4 Carefully align the upper and lower edges of the line card with the upper and lower guides in the chassis, and slide the line card into the slot until you can feel it begin to seat in the backplane connectors (Figure 6).
Step 5 Simultaneously pivot both ejector levers toward each other (until they are parallel to the faceplate) to firmly seat the card in the backplane (Figure 7).
The line card cycles through its power-on self-test. The Fail LED stays on briefly (2 to 3 seconds) and then shuts off. If the Fail LED remains on, go to the "Troubleshooting the Installation" section.
Step 6 Secure the line card in the chassis by tightening the top and bottom captive screws (Figure 8).
|
Caution To ensure that there is adequate space for additional line cards, always tighten the captive screws on each newly installed line card before you insert any additional line cards. These screws prevent accidental removal and provide proper grounding for electromagnetic interference (EMI) shielding. |
After the OC-12 ATM line card is successfully installed, you can configure the card for network use. For information about configuring the OC-12 ATM line card, see the Cisco 10000 ESR Software Configuration Guide.
|
Note You do not need to configure the OC-12 ATM line card if you plan to perform a replacement installation in the same chassis slot. The system automatically downloads the necessary configuration information from the PRE. |
Use the following procedure to remove a faulty OC-12 ATM line card from the chassis:
Step 2 Loosen the top and bottom captive screws on the line card (Figure 10).
Step 3 Simultaneously pivot both ejector levers away from each other to disengage the line card from the backplane (Figure 11).
Step 4 Slide the line card out of the slot and place it on an antistatic surface, or in an antistatic bag.
Step 5 See the "Installing an OC-12 ATM Line Card" section for instructions to install a new line card.
If you are not installing a replacement line card, install a blank faceplate in the slot.
|
Warning Do not operate the system unless all slots contain a line card or a blank faceplate. Blank faceplates are necessary in empty slots to prevent exposure to hazardous voltages, to reduce electromagnetic interference (EMI) that may disrupt other equipment, and to direct the flow of cooling air through the chassis. |
Refer to Figure 12 and Table 1 for descriptions of the LEDs on the OC-12 ATM line card. Follow the instructions in Table 2 to troubleshoot the installation.
| LED | Status | Description |
|---|---|---|
Fail | Yellow Off | A major failure has disabled the line card. The line card is functioning properly. |
Enable | Green Off | The port is enabled for data traffic. The port is not enabled for data traffic. |
Alarm | Yellow | Indicates an alarm condition at the OC-12 level. No alarm condition. |
Loop | Yellow Off | Port is in a loopback state and not enabled for data traffic. Port is not in a loopback state. |
Rx (receiving) | Green Off | The port is receiving traffic. The port is not receiving traffic. |
Tx (transmit) | Green Off | Transmitting traffic. Not transmitting traffic. |
Carrier | Green Off | Carrier detected. Carrier not detected. |
| Symptom | Possible Cause | Corrective Action |
|---|---|---|
Power entry modules (PEMs), fans, and other line cards do not operate | 1. Disconnected power cord. 2. Power switch is in the Off position. | 1. Check that all power cords are properly connected to both the Cisco 10000 system and at the power connection end. 2. Set the PEM power switches to the On position. |
The Fail LED does not light during the power-on self-test | 1. The line card is not properly seated. 2. Bad line card slot or backplane connector. | 1. Be sure the ejector levers are fully closed and that the captive screws have been tightened. 2. Remove the line card and install it in another chassis slot. |
Line card does not operate properly | 1. Bad line card slot or backplane connector. 2. Bad fiber-optic cable. 3. Bad line card. | 1. Remove the line card and install it in another chassis slot. 2. Replace the cable. 3. Replace the line card. |
This section describes the procedures for configuring a Cisco 10000 ESR OC-12 ATM line card (Figure 13). In addition, this section includes a table of default values and interface configuration examples. Principal ATM commands are also described.
|
Note For information about Quality of Service (QoS) for the OC-12 ATM line card, see the Cisco 10000 ESR Software Configuration Guide. |
Table 3 lists default configuration values for the OC-12 ATM line card. The commands marked with an asterisk (*) are described in the Cisco IOS Command Reference. The other commands are among those described in this chapter.
This table includes the command used to modify a default value, and provides information about values to set on the remote end of the connection.
| Command Name | Default Setting | Command Syntax | Remote Side Setting |
|---|---|---|---|
mtu (maximum transmission unit)* | 9180 bytes | [no] mtu bytes | same |
atm clock internal | no atm clock internal | [no] atm clock internal | opposite |
loopback | loopback none | [no] loopback [line | diagnostic {parallel | path | serial}] | — |
pvc encapsulation | aal5snap | encapsulation [aal5snap | aal5mux ip] | same |
To specify an interface number in a configuration command, use the syntax in Table 4 to identify interfaces on the OC-12 ATM line card.
Type of Interface | Slot | Subslot | Port | Subinterface |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
Examples:
Router(config)# interface atm 2/0/0 Router(config-if)# pvc 0/200 Router(config-if-atm-vc)#
Router(config)# interface atm 7/0/0.1 Router(config-subif)# pvc 0/101 Router(config-if-atm-vc)#
This section provides sample procedures for creating subinterfaces, permanent virtual circuits (PVCs), virtual circuit (VC) classes, and for enabling Integrated Local Management Interface (ILMI).
Use the following procedure to create a subinterface.
In the following example, multipoint subinterface number 1 is created on an OC-12 ATM line card in slot 2.
Router(config)# interface atm 2/0/0.1 multipoint Router(config-subif)#
Step 2 Assign an IP address and subnet mask to the interface using the ip address configuration subcommand, as shown in the following example:
Router(config-subif)# ip address 172.27.48.209 255.255.0.0 Router(config-subif)#
You have created interface 2/0/0.1. To enter this interface, use the following command:
Router(config)# interface atm 2/0/0.1 Router(config-subif)#
You can create up multiple PVCs on the OC-12 ATM interface. You can create PVCs on the main interface or on a subinterface.
To create a PVC
Use the pvc command to specify a virtual path identifier (VPI) value between 0 and 255 and a virtual channel identifier (VCI) value between 0 and 65535. The following example creates a PVC with a VPI value of 0 and VCI value of 100 on a subinterface.
Router(config-subif)# pvc 0/100 Router(config-if-atm-vc)#
Step 2 Assign a peer IP address to the PVC using the protocol ip configuration subcommand, as in the following example:
Router(config-if-atm-vc)# protocol ip 172.16.32.49 Router(config-if-atm-vc)#
This procedure demonstrates how to create an ATM VC class. An ATM VC class is a PVC boilerplate—a PVC description that you can apply to one or more PVCs.
Router(config)# vc-class atm boston Router(config-vc-class)#
Step 2 Enter commands to describe the ATM VC class named boston. This example shows how to specify that the class uses AAL5+MUX encapsulation and configure a variable bit rate-nonreal time (VBR-NRT) PVC.
Router(config-vc-class)# encaps aal5mux ip Router(config-vc-class)# vbr-nrt 30000 20000 128 Router(config-vc-class)# exit Router(config)#
You have created a VC class named boston. The next procedure describes how to apply this class to a PVC or subinterface.
You can apply a VC class (created in the previous procedure) to a PVC or an interface.
Router(config)# interface atm 5/0/0.1 Router(config-subif)# class-int boston Router(config-subif)#
Router(config)# interface atm 5/0/0.2 Router(config-subif)# pvc 0/102 Router(config-if-atm-vc)# class-vc boston Router(config-if-atm-vc)#
You have completed the steps for assigning a VC class to a PVC.
You can enable ILMI to automatically discover PVCs on neighboring switches and duplicate those PVC entries on the OC-12 ATM line card.
To enable ILMI
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/16 ilmi Router(config-if-atm-vc)# exit Router(config-if)#
Step 2 In the following example, ILMI PVC discovery is enabled for the OC-12 ATM line card.
Router(config-if)# atm ilmi-pvc-discovery
You have completed the steps required for running ILMI PVC discovery. You can use the show atm pvc command to display the PVCs on the Cisco 10000 ESR.
This section offers general information on completing a configuration of an OC-12 ATM line card.
Step 2 After you have included all of the configuration subcommands to complete the configuration, enter Ctrl-Z (hold down the Control key while you press Z) to exit configuration mode.
Step 3 Write the new configuration to memory:
Router# copy running-config startup-config
The system displays an OK message when the configuration is stored. After you have completed your configuration, you can check it by using show commands.
The OC-12 ATM line card consists of a single OC-12 interface. You can put all the PVCs on this interface, or you can create subinterfaces. This section describes the principal commands for customizing interfaces and PVCs:
A PVC boilerplate is a PVC description that you can apply to one or more PVCs or interfaces.
To create a PVC boilerplate, use the global configuration mode vc-class atm command.
vc-class atm class_name
Where class_name is any word that describes the class.
After you create the class, you enter VC class configuration mode. In this mode, you describe the action you want the class to take by entering commands and arguments. These commands and arguments are described in the "ATM PVC Commands" section.
In the following example, an ATM VC class named cambridge is created and defined. This example shows how to specify that the class uses AAL5+MUX encapsulation and a VBR-NRT PVC.
Router(config)# vc-class atm cambridge Router(config-vc-class)# encaps aal5mux ip Router(config-vc-class)# vbr-nrt 30000 20000 128 Router(config-vc-class)# exit Router(config)#
For information on applying a VC class name, see the "Attaching an ATM VC Class to an Interface" section and the "Attaching an ATM VC Class to a PVC" section.
This section describes principal commands for configuring ATM interfaces and subinterfaces. This section describes the following global configuration commands:
Use the interface command to divide the OC-12 ATM interface into multiple subinterfaces to simplify management of the card, create interfaces with different MTU sizes, and create connections to different networks.
interface atm slot/subslot/port.subinterface type no interface atm slot/subslot/port.subinterface type
Where:
To enter the subinterface at a later time, you do not need to specify the type.
To remove a subinterface and its PVCs, use the no interface command. To change a subinterface type, you must first remove the subinterface.
Examples:
Router(config)# interface atm 1/0/0.1 point-to-point Router(config-subif)#
Router(config)# interface atm 1/0/0.1 Router(config-subif)#
Router(config)# interface atm 4/0/0.2 multipoint Router(config-subif)#
Table 5 provides the configuration commands used to configure the multipoint connections in the network shown in Figure 14.
| Router A | Router B | Router C |
|---|---|---|
interface atm 4/0/0.2 multi ip address 131.108.168.1 | interface atm 2/0/0.1 multi ip address 131.108.168.2 | interface atm 5/0/0.1 multi ip address 131.108.168.3 |
To attach an ATM VC class to an interface, use the class-int command. If you customize a PVC, its customization takes precedence over the interface class.
class-int class_name
Where class_name is the name of the class created using the global configuration class-vc atm command.
In the following example, a VC class named cambridge is created and attached to subinterface 3/0/0.1.
Router(config)# vc-class atm cambridge Router(config-vc-class)# encaps aal5mux ip Router(config-vc-class)# vbr-nrt 30000 20000 128 Router(config-vc-class)# exit Router(config)# interface atm 3/0/0.1 Router(config-subif)# class-int cambridge
To create a permanent virtual path (PVP) used to multiplex one or more VBR-NRT VCs, use the atm pvp interface configuration command.
atm pvp vpi peak-rate [no-f4-oam] no atm pvp vpi
Where:
To verify the configuration of a PVP, use the show atm vp EXEC command.
The following example shows how to create a PVP with a peak rate of 50000 Kbps. The subsequent VCs created are multiplexed onto this virtual path.
Router(config)# interface atm 7/0/0 Router(config-if)# atm pvp 25 50000 Router(config-if)# pvc 25/100 Router(config-if-atm-vc)# vbr-nrt 10000 5000 16 Router(config-if-atm-vc)# exit Router(config-if)# pvc 25/101 Router(config-if-atm-vc)# vbr-nrt 10000 5000 16 Router(config-if-atm-vc)# exit Router(config-if)# pvc 25/102 Router(config-if-atm-vc)# vbr-nrt 10000 5000 16 Router(config-if-atm-vc)# exit Router(config)#
You can create a unspecified bit rate (UBR) PVC by entering the pvc command:
pvc [word] [vpi_value/]{vci_value} [ilmi]
Where:
By default, the pvc command creates a UBR PVC; to create a VBR-NRT PVC, see the "Configuring VBR-NRT" section.
|
Note You can only create one PVC on a point-to-point interface. Multiple PVCs can be created on a multipoint interface. |
Examples:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 105 Router(config-if-atm-vc)
Router(config)# interface atm 5/0/0.1 Router(config-subif)# pvc 2/102 Router(config-if-atm-vc)#
Use the atm ilmi-enable interface configuration command to enable the ILMI on a port.
atm ilmi-enable no atm ilmi-enable
The default is ILMI is enabled, but you should disable the ILMI if the peer does not support ILMI. In order for peers to exchange ILMI information, you must create PVC 0/16, using the ilmi argument.
The following example disables ILMI:
Router(config)# interface atm 5/0/0 Router(config-if)# no atm ilmi-enable
To activate ATM PVC discovery, use the atm ilmi-pvc-discovery interface configuration command. This command causes ILMI-compliant devices to propagate PVCs.
atm ilmi-pvc-discovery [subinterface] no atm ilmi-pvc-discovery [subinterface]
Where:
|
Note The subinterface argument associates PVCs only with subinterfaces that have already been created. If there is no subinterface for a VPI value, the system associates the PVC with the main interface. |
The following example shows how to enable PVC Discovery on the ATM main interface 7/0/0 on an OC-12 ATM line card that has ILMI enabled.
Router(config)# interface atm 7/0/0 Router(config-if)# pvc 0/16 ilmi Router(config-if-atm-vc)# exit Router(config-if)# atm ilmi-pvc-discovery
To specify the ILMI keep-alive rate, enter the atm ilmi-keepalive command.
atm ilmi-keepalive [seconds [retry counts]]
Where:
The default value for seconds is 5000 and for retry counts is 4.
The following example shows how to enable ILMI keepalives for the ATM interface 5/0/0:
Router(config)# interface atm 5/0/0 Router(config-if)# atm ilmi-keepalive 10000 retry 3
To configure the clock source as internal, use the atm clock internal command:
atm clock internal no atm clock internal
The default clock setting is no atm clock internal, which means that clocking is derived from the line.
In the following example, clocking is set from the router.
Router(config)# interface atm 5/0/0 Router(config-if)# atm clock internal
To specify the ATM flag value for the s1s0 bit, use the atm flag s1s0 command. This command is typically used to meet a standards requirement or to ensure interoperability with another vendor's equipment.
atm flag s1s0 value
Where:
The default s1s0 value is 0.
The following example assigns a value of 2 to the ATM flag:
Router(config)# interface atm 5/0/0 Router(config-if)# atm flag s1s0 2
To specify an ATM scrambling mode, use the atm scrambling command:
atm scrambling [cell-payload | sts-stream] no atm scrambling [cell-payload | sts-stream]
Where
By default, the system scrambles both the cell payload and the STS stream.
The following example shows how to scramble the payload of the cell:
Router(config)# interface atm 5/0/0 Router(config-if)# atm scrambling cell-payload
To control selected SONET alarms so that they are logged to the console for an ATM interface, use the atm report interface configuration command.
atm report {b1-tca | b2-tca | b3-tca | lais | lcd | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
no atm report {b1-tca | b2-tca | b3-tca | lais | lcd | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
Where:
To disable logging of select SONET alarms, use the no form of this command.
Reporting an alarm means that the alarm can be logged to the console. Not all alarms are 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 atm command output. A defect is a problem indication that is a candidate for an alarm.
The following example shows how to enable reporting of SD-BER and LAIS alarms on the interface:
Router(config)# interface atm 3/0/0 Router(config-if)# atm report sd-ber Router(config-if)# atm report lais Router(config-if)# end Router#
Specify the bit error rate (BER) threshold by using the atm threshold command:
atm threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} value
Where:
The default for all thresholds, except sf-ber, is 10-6. The default for sf-ber is 10-3.
The following example shows how to specify the B1 BER threshold crossing alarm value of 4:
Router(config)# interface atm 5/0/0 Router(config-if)# atm threshold b1-tca 4
You can run a loopback by using the loopback command:
loopback {line | diagnostic {parallel | path | serial}}
no loopback {line | diagnostic {parallel | path | serial}}
Where:
The following example shows hot to run the diagnostic serial loopback:
Router(config)# interface atm 5/0/0 Router(config-if)# loopback diagnostic serial
After you create a PVC using the pvc command, you can customize the PVC or a VC class by using the commands described in this section.
Use the protocol ip command in interface-ATM-VC configuration mode or VC-class configuration mode to do one or both of the following:
protocol ip {protocol-address | inarp} [[no] broadcast]
no protocol ip {protocol-address | inarp} [[no] broadcast]
Where:
Use the no form of this command to remove a static map or disable Inverse ARP.
|
Note Use the inarp command to configure Inverse ARP frequency. |
The following example shows how to specify IP protocol on an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# protocol ip 172.16.32.49
To configure broadcast packet duplication and transmission for an ATM PVC or VC class, use the broadcast command.
The broadcast command is not used to enable ATM cell-level multicast, broadcast, replication, or to set up the broadcast of user level traffic. The broadcast command indicates which PVC (or PVCs) sends out broadcast traffic. This is typically limited to traffic associated with routing protocols and routing updates (for example, OSPF hello packets).
|
Note The broadcast argument within the protocol ip command takes precedence over the broadcast command. See the "Specifying the Protocol" section for additional information about the protocol ip command. |
Use the default form of this command to restore the default behavior described below.
broadcast no broadcast The default is broadcast. Use the no form of this command to disable transmission of broadcast packets.
For PVCs created under point-to-point subinterfaces, broadcast is enabled by default. For PVCs created under multipoint subinterfaces, you should use the broadcast command if you want to propagate IP routes (only the first PVC on a multipoint interface receives broadcast traffic).
The following example shows how to use the broadcast command to restore the default behavior:
Router(config)# interface atm 5/0/0.4 Router(config-subif)# pvc 0/105 Router(config-if-atm-vc)# broadcast Router(config-if-atm-vc)#
To configure the Inverse ARP time period for an ATM PVC or VC class, use the inarp command in interface-ATM-VC configuration mode or VC-class configuration mode.
inarp minutes no inarp minutes
Where minutes is the Inverse ARP frequency from 1 to 60 minutes.
The default frequency is 15 minutes.
Use the no form of this command to restore the default Inverse ARP time period behavior.
|
Note This command is supported only for AAL5+SNAP encapsulation (the default) when Inverse ARP is enabled. Use the encapsulation command to configure AAL5+SNAP encapsulation and the protocol command to enable Inverse ARP. |
The following example shows how to specify an Inverse ARP frequency of 40 minutes on an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# inarp 40
To attach an ATM VC class to a PVC, use the class-vc command.
class-vc name
Where:
The following example shows how to assign an ATM VC class named boston to an ATM PVC:
Router(config)# interface atm 5/0/0.4 Router(config-subif)# pvc 2/100 Router(config-if-atm-vc)# class-vc boston
To configure the variable bit rate-nonreal time (VBR-NRT) traffic management type and specify output peak cell rate, output sustainable cell rate, and output maximum burst cell size for an ATM PVC or VC class, use the vbr-nrt command. Use vbr-nrt in interface-ATM-VC configuration mode or VC-class configuration mode.
vbr-nrt peak_cell_rate sustainable_cell_rate maximum_burst_size no vbr-nrt peak_cell_rate sustainable_cell_rate maximum_burst_size
Where:
The default class of service is unspecified bit rate (UBR) running at the maximum line rate of the physical interface.
Use the no form of this command to remove the VBR-NRT parameters and return the PVC to its default of unspecified bit rate (UBR).
You can create up to 254 VBR-NRT PVCs on an OC-12 ATM line card.
The following example shows how to configure the VBR-NRT traffic parameters on an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# vbr-nrt 50000 20000 200
To specify the ATM adaptation layer (AAL) and encapsulation type for an ATM PVC or VC class, use the encapsulation command in interface-ATM-VC configuration mode or VC-class configuration mode.
encapsulation {aal5mux ip | aal5snap}
no encapsulation {aal5mux ip | aal5snap}
Where:
Use the no form of this command to remove an encapsulation from a PVC or VC class.
The following example shows how to specify aal5mux ip encapsulation for an ATM PVC:
Router(config)# interface atm 5/0/0.4 Router(config-subif)# pvc 0/105 Router(config-if-atm-vc)# encaps aal5mux ip
To enable ILMI management on an ATM PVC, use the ilmi manage command in interface-ATM-VC configuration mode or VC-class configuration mode. This command changes the convergence of higher-level protocols based on link-state changes.
ilmi manage no ilmi manage Use the no form of this command to disable ILMI management.
The following example shows how to enable ILMI management on an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# ilmi manage
To configure OAM retry, use the oam retry command in interface-ATM-VC configuration mode or VC-class configuration mode.
oam retry up_value [down_value frequency] no oam retry up_value [down_value frequency]
Where:
Use the no form of the command to remove oam retry parameters.
The following example shows how to configure OAM retry to an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# oam retry 10 10 5
To enable end-to-end F5 OAM loopback cell generation and OAM management for an ATM PVC or VC class, use the oam-pvc command in interface-ATM-VC configuration mode or VC-class configuration mode.
oam-pvc [manage] [frequency] no oam-pvc [manage] [frequency]
Where
The default value is 10 seconds.
Use the no form of this command to disable generation of OAM loopback cells and OAM management.
The following example enables OAM loopback cell and OAM management to an ATM PVC:
Router(config)# interface atm 5/0/0 Router(config-if)# pvc 0/105 Router(config-if-atm-vc)# oam-pvc 300
show atm vc
Use the show atm vc command to display information about the VCs on the interface.
Router#show atm vc
VCD / Peak Avg/Min Burst
Interface Name VPI VCI Type Encaps Kbps Kbps Cells Sts
2/0/0 1 0 16 PVC ILMI 599040 UP
2/0/0 9 0 100 PVC MUX 599040 UP
2/0/0.2 7 2 32 PVC SNAP 599040 UP
2/0/0 8 2 33 PVC SNAP 599040 UP
2/0/0 18 2 100 PVC SNAP 599040 UP
2/0/0.2 6 4 24 PVC SNAP 599040 UP
2/0/0 2 25 3 PVC F4-OAM 50000 UP
2/0/0 3 25 4 PVC F4-OAM 50000 UP
2/0/0 14 25 100 PVC SNAP 50000 50000 0 UP
2/0/0 16 25 101 PVC SNAP 50000 50000 0 UP
2/0/0 17 25 102 PVC SNAP 50000 50000 0 UP
2/0/0 10 26 3 PVC F4-OAM 50000 UP
2/0/0 11 26 4 PVC F4-OAM 50000 UP
2/0/0 12 27 3 PVC F4-OAM 50000 UP
2/0/0 13 27 4 PVC F4-OAM 50000 UP
2/0/0 19 33 100 PVC SNAP 10000 8000 10 UP
Router#
show atm vp
Use the show atm vp command to display information about the VPs on the interface.
Router#show atm vp
Data CES Peak CES
Interface VPI VCs VCs Kbps Kbps Status
ATM2/0/0 25 3 0 50000 0 ACTIVE
ATM2/0/0 26 0 0 50000 0 ACTIVE
ATM2/0/0 27 0 0 50000 0 ACTIVE
Router#
show atm pvc
Use the show atm pvc vpi_number/vci_number command to display detailed information about a specific PVC.
Router#show atm pvc 0/100 ATM2/0/0: VCD: 9, VPI: 0, VCI: 100 UBR, PeakRate: 599040 AAL5-MUX, etype:0x800, Flags: 0xC23, VCmode: 0x0 OAM frequency: 0 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Disabled OAM VC state: Not Managed ILMI VC state: Not Managed InARP DISABLED InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0 InPRoc: 0, OutPRoc: 0, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0 InPktDrops: 0, OutPktDrops: 0 Out CLP=1 Pkts: 0 OAM cells received: 0 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 OAM cells sent: 0 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 OAM cell drops: 0 PVC Discovery: NOT_VERIFIED Status: UP Router#
The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco's installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Cisco's written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact the Cisco Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Access Registrar, AccessPath, Are You Ready, ATM Director, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, iQuick Study, iQ Readiness Scorecard, The iQ Logo, Kernel Proxy, MGX, Natural Network Viewer, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert Logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Collision Free, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document/website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any of its resellers. (0008R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Thu Sep 21 13:56:38 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.