Table Of Contents

Configuring the OC3 ATM Line Card

Using the EXEC Command Interpreter

Configuring the Interfaces

Shutting Down an Interface

Performing a Basic Configuration

Checking the Configuration

Using show Commands to Verify the New Interface Status

Using the ping Command to Verify Network Connection

Using loopback Commands

Performing an Advanced Configuration

Configuring the OC3 ATM Line Card for OC-3

Configuring VCs

Configuring PVCs

Configuring SVCs

Configuring Classical IP and ARP over ATM

Customizing the OC3 ATM Line Card

Setting the MTU Size

Configuring an ATM Interface for Local Loopback

Configuring an ATM Interface for External Loopback

Checking the Advanced Configuration

Traffic Management

Testing and Troubleshooting the OC3 ATM Line Card

OC3 ATM Line Card Statistics

Using the Debug ATM Commands

Commands That Display ATM Information

ATM Configuration Examples

Example of PVCs with AAL5 and LLC/SNAP Encapsulation

Example of PVCs in a Fully Meshed Network

Example of SVCs in a Fully Meshed Network

Connecting Two OC3 ATM Line Cards Back to Back

Upgrading Your Bootdisk Image

CLI-Controlled OIR

Configuring the OC3 ATM Line Card

---

To continue your OC3 ATM line card installation, you must configure the OC-3 interface. This chapter contains the following sections:

• Using the EXEC Command Interpreter

• Configuring the Interfaces

• Checking the Configuration

• Performing an Advanced Configuration

• Customizing the OC3 ATM Line Card

• Checking the Advanced Configuration

• Traffic Management

• Testing and Troubleshooting the OC3 ATM Line Card

• ATM Configuration Examples

• Upgrading Your Bootdisk Image

• CLI-Controlled OIR

Using the EXEC Command Interpreter

You modify the configuration of your router through the software command interpreter called the EXEC (also called enable mode). You must enter the privileged level of the EXEC command interpreter with the enable command before you can use the configure command to configure a new interface or change the existing configuration of an interface. The system prompts you for a password if one has been set.

---

Tip The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>).

---

At the console terminal, use the following procedure to enter the privileged level:

---

Step 1 At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a privileged-level password as follows:

Router> enable

Password:

Step 2 Enter the password (the password is case sensitive). For security purposes, the password is not displayed.

When you enter the correct password, the system displays the privileged-level system prompt (#):

Router#




---

Configuring the Interfaces

After you verify that the new OC3 ATM line card is installed correctly (the STATUS LED goes on), use the privileged-level configure command to configure the new interface. Have the following information available:

•Protocols you plan to route on the new interface

•IP addresses, if you plan to configure the interface for IP routing

•Bridging protocols you plan to use

If you installed a new OC3 ATM line card or if you want to change the configuration of an existing interface, you must enter configuration mode to configure the new interface. If you replaced an OC3 ATM line card that was previously configured, the system recognizes the new interface and brings it up in its existing configuration.

For a summary of the configuration options available and instructions for configuring the interface on an OC3 ATM line card, refer to the appropriate configuration publications listed in "Related Documentation".

You execute configuration commands from the privileged level of the EXEC command interpreter, which usually requires password access. Contact your system administrator, if necessary, to obtain password access. (See Using the EXEC Command Interpreter for an explanation of the privileged level of the EXEC.)

This section contains the following subsections:

• Shutting Down an Interface

• Performing a Basic Configuration

Shutting Down an Interface

Before you replace an interface cable, replace line cards, or remove an interface that you will not replace, use the shutdown command to shut down (disable) the interfaces. When you shut down an interface, it is designated administratively down in the show command displays.

Follow these steps to shut down an interface on the supported platform:

---

Step 1 Enter the privileged level of the EXEC command interpreter (also called enable mode). (See the "Using the EXEC Command Interpreter" section for instructions.)

Step 2 At the privileged-level prompt, enter configuration mode and specify that the console terminal is the source of the configuration subcommands, as follows:

Router# configure terminal

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

Router(config)#




Step 3 Shut down the interface by entering the interface atm subcommand, then enter the shutdown command. Table 4-1 shows the command syntax.

When you have finished, press Ctrl-Z—hold down the Control key while you press Z—or enter end or exit to exit configuration mode and return to the EXEC command interpreter.

Table 4-1 Syntax of the shutdown Command 

Platform	Command	Example
Cisco 7304 router	interface atm followed by slot/port (slot-number/ interface-port-number)	The example is for interface 0 on an OC3 ATM line card in slot 4. Router(config-if)# interface atm 4/0 Router(config-if)# shutdown Ctrl-Z Router#

Step 4 Write the new configuration to NVRAM as follows:

Router# copy running-config startup-config

[OK]

Router#




The system displays an OK message when the configuration has been stored in NVRAM.

Step 5 Verify that the new interface is in the correct state (shut down) using the show interfaces command (followed by the interface type and interface address) to display the specific interface. Table 4-2 provides an example.

Table 4-2 Examples of the show interfaces atm Command 

Platform	Command	Example
Cisco 7304 routers	show interfaces atm, followed by slot/port (slot-number/ interface-port-number)	The example is for interface 0 on an OC3 ATM line card in slot 4. Router# show interfaces atm 4/0 ATM 4/0 is administratively down, line protocol is down [Additional display text omitted from this example]

Step 6 Enable the interface by doing the following:

a. Repeat Step 3 to enable an interface. Substitute the no shutdown command for the shutdown command.

b. Repeat Step 4 to write the new configuration to memory. Use the copy running-config startup-config command.

c. Repeat Step 5 to verify that the interface is in the correct state. Use the
show interfaces atm command followed by the interface address of the interface.

---

For complete descriptions of software configuration commands, refer to the publications listed in "Related Documentation".

Performing a Basic Configuration

The following steps describe a basic interface configuration. Press the Return key after each step unless otherwise noted. At any time, you can exit the privileged level and return to the user level by entering disable at the prompt as follows:

Router# disable

Router>




Follow these steps to perform a basic configuration:

---

Step 1 At the privileged-level prompt, enter configuration mode and specify that the console terminal will be the source of the configuration subcommands, as follows:

Router# configure terminal

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

Router(config)#




Step 2 Specify the first interface to configure by entering the interface atm subcommand, followed by the interface address of the interface you plan to configure. Table 4-3 gives an example.

Table 4-3 Examples of the interface atm Subcommand 

Platform	Command	Example
Cisco 7304 routers	interface atm, followed by slot/port (slot-number/ interface-port-number)	The example is for the interface of an OC3 ATM line card in slot 4. Router(config)# interface atm 4/0 Router(config-if)#

Step 3 Assign an IP address and subnet mask to the interface (if IP routing is enabled on the system) by using the ip address subcommand, as in the following example:

Router(config-if)# ip address 10.0.0.0 255.255.255.0




Step 4 Add any additional configuration subcommands required to enable routing protocols and set the interface characteristics.

Step 5 Enable the interfaces using the no shutdown command. (See Shutting Down an Interface.)

Step 6 After including all of the configuration subcommands to complete your configuration, press Ctrl-Z or enter end or exit to exit the configuration mode and return to the EXEC command interpreter prompt.

Step 7 Write the new configuration to NVRAM as follows:

Router# copy running-config startup-config

[OK]

Router#




---

The system displays an OK message when the configuration has been stored in NVRAM.

---

Tip If you are going to disconnect or reconfigure the ATM interface cable, use the shutdown command before doing so. After reattaching the ATM interface cable, use the no shutdown command to bring up the ATM interface.

---

Checking the Configuration

After configuring the interface, use the show commands to display the status of the new interface and use the ping and loopback commands to check connectivity. This section includes the following subsections:

• Using show Commands to Verify the New Interface Status

• Using the ping Command to Verify Network Connection

• Using loopback Commands

Using show Commands to Verify the New Interface Status

Table 4-4 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the OC3 ATM line card appears in them correctly. Sample displays of the output of selected show commands appear in the sections that follow. For complete command descriptions and examples, refer to the publications listed in "Related Documentation".

Table 4-4 Using show Commands 

Command	Function	Example
show version or show hardware	Displays system hardware configuration, the number of each interface type installed, Cisco IOS software version, names and sources of configuration files, and boot images	Router# show version
show controllers	Displays all the current interface processors and their interfaces	Router# show controllers
show diag slot	Displays types of line cards installed in your system and information about a specific chassis slot	Router# show diag 2
show c7300	Displays types of line cards with status information for each installed line card	Router# show c7300
show interfaces atm interface-port-number	Displays status information about a specific ATM interface in a Cisco 7304 router	Router# show interfaces atm 3/1
show protocols	Displays protocols configured for the entire system and for specific interfaces	Router# show protocols
show running-config	Displays the running configuration file	Router# show running-config
show startup-config	Displays the configuration stored in NVRAM	Router# show startup-config

---

Note If an interface is shut down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the interface is properly connected and terminated. If you still have problems bringing up the interface, contact a service representative for assistance.

---

This section includes the following subsections:

• Using the show version or show hardware Commands

• Using the show diag Command

• Using the show c7300 Command

• Using the show interfaces Command

Choose the subsection appropriate for your system. Proceed to "Using the ping Command to Verify Network Connection" when you have finished using the show commands.

Using the show version or show hardware Commands

Display the configuration of the system hardware, the number of each interface type installed, the Cisco IOS software version, the names and sources of configuration files, and the boot images, by using the show version (or show hardware) command.

---

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples .

---

Cisco 7304 Router

Following is an example of the show version command from a Cisco 7304 router with the OC3 ATM line card:

Router# show version

Cisco Internetwork Operating System Software

IOS (tm) 7300 Software (C7300-IS-M), Version 12.1(20020129:220814) [ra-ws2 103]

Copyright (c) 1986-2002 by cisco Systems, Inc.

Compiled Mon 04-Feb-02 11:19 by ra

Image text-base: 0x40008970, data-base: 0x414E0000




ROM: System Bootstrap, Version 12.1(20011026:021245) [hih-rommon_1_1 101], DEVELOPMENT SOFTWARE

Currently running ROMMON from ROM 1

BOOTLDR: 7300 Software (C7300-BOOT-M), Version 12.1(1.23.158), CISCO DEVELOPMENT TEST VERSION




c7300router uptime is 2 minutes

System returned to ROM by power-on

System image file is "tftp://223.255.254.254/muck/ra/c7300-is-mz"




cisco 7300 (NSE100) processor (revision B) with 114688K/16384K bytes of memory.

Processor board ID SCA053200L0

R7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2, 1024KB L3 Cache

4 slot midplane, Version 65.48




Last reset from power-on

Bridging software.

X.25 software, Version 3.0.0.

PXF processor tmc0 running 'system:pxf/ucode1' v1.6 is active

PXF processor tmc1 running 'system:pxf/ucode1' v1.6 is active

1 FastEthernet/IEEE 802.3 interface(s)

2 Gigabit Ethernet/IEEE 802.3 interface(s)

4 ATM network interface(s)

509K bytes of non-volatile configuration memory.




16064K bytes of ATA compact flash in bootdisk (Sector size 512 bytes).

31360K bytes of ATA compact flash in disk0 (Sector size 512 bytes).

Configuration register is 0x100

Router




Using the show diag Command

Display the types of line cards installed in your system (and specific information about each) using the show diag slot command, where slot is the line card slot in a Cisco 7304.

---

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.

---

Cisco 7304 Router

Following is an example of the show diag slot command for an OC3 ATM line card in slot 2 of a Cisco 7304 router:

Router# show diag 2

Slot 2:

OC3 ATM Multimode Line Card, 2 ports

Line Card state: Active

Insertion time: 00:03:21 ago

Bandwidth points: 32

EEPROM contents at hardware discovery:

Hardware Revision : 2.0

Unknown Field (type 0046): 00 00

PCB Serial Number : CAB0549LNKQ

Part Number : 73-6828-02

Board Revision : A0

Fab Version : 02

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Deviation Number : 0-0

Product Number : 7300-2OC3ATM-MM

Top Assy. Part Number : 68-0000-00

Manufacturing Test Data : 00 00 00 00 00 00 00 00

Field Diagnostics Data : 00 00 00 00 00 00 00 00

Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmV

Calibration values :

EEPROM format version 4 EEPROM contents (hex):

0x00: 04 FF 40 03 74 41 02 00 46 00 00 C1 8B 43 41 42

0x10: 30 35 34 39 4C 4E 4B 51 82 49 1A AC 02 42 41 30

0x20: 02 02 03 00 81 00 00 00 00 04 00 80 00 00 00 00

0x30: CB 94 37 33 30 30 2D 32 4F 43 33 41 54 4D 2D 4D

0x40: 4D 20 20 20 20 20 87 44 00 00 00 C4 08 00 00 00

0x50: 00 00 00 00 00 C5 08 00 00 00 00 00 00 00 00 C8

0x60: 09 00 00 00 00 00 00 00 00 00 C7 7C F6 44 3F 30

0x70: 00 00 00 00 00 00 00 00 00 00 00 00 07 08 64 32

0x80: 28 37 26 09 C4 64 32 28 32 DD 0C E4 64 32 28 43

0x90: 24 2E E0 AA 82 64 F4 24 00 00 00 00 00 00 00 00

0xA0: 00 00 00 00 00 00 F4 C8 FF FF FF FF FF FF FF FF

0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FPGA information:

Current FPGA version : 0.3

IOS bundled FPGA version : 0.10

Using the show c7300 Command

Display the types of line cards installed in your system, their status, and insertion time by using the show c7300 command.

---

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.

---

Cisco 7304 Router

Following is an example of the show c7300 command for a Cisco 7304 router:

Router# show c7300




Slot Card Type Status Insertion time

---- --------- ------ --------------

0,1 NSE100 Active 3d02h ago

2,3 NSE100 Standby 3d02h ago

4 2OC3-ATM Active 3d02h ago





The FPGA versions for the cards listed above are current




System is compliant with hardware configuration guidelines.




Network IO Interrupt Throttling:

throttle count=0, timer count=0

active=0, configured=1

netint usec=3999, netint mask usec=200




Router#




Using the show interfaces Command

The show interfaces command displays status information (including the physical slot and interface address) for the interfaces you specify. The example that follows specifies ATM interfaces.

For complete descriptions of interface subcommands and the configuration options available for Cisco 7304 interfaces, refer to the publications listed in the "Related Documentation"section.

---

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.

---

Cisco 7304 Router

Following is an example of the show interfaces atm command used with a Cisco 7304 router. In this example, the OC3 ATM line card is installed in slot 4 of a Cisco 7304 router:

Router# show interfaces atm 4/0

ATM4/0 is up, line protocol is up

Hardware is OC-3 ATM

Internet address is 40.1.1.40/24

MTU 4470 bytes, sub MTU 4470, BW 149760 Kbit, DLY 80 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ATM, loopback not set

Keepalive not supported

Encapsulation(s): AAL5

2048 maximum active VCs, 10 current VCCs

VC idle disconnect time: 300 seconds

0 carrier transitions

Last input 00:00:41, output 00:00:41, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue :0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

38 packets input, 4256 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

38 packets output, 4104 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

Using the ping Command to Verify Network Connection

Using the ping command, you can verify that an interface port is functioning properly. This section provides a brief description of this command. Refer to the publications listed in the "Related Documentation" section on page viii for detailed command descriptions and examples.

The ping command sends echo request packets out to a remote device at an IP address that you specify. After sending an echo request, the system waits a specified time for the remote device to reply. Each echo reply is displayed as an exclamation point (!) on the console terminal; each request that is not returned before the specified timeout is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate a bad connection.

Following is an example of a successful ping command to a remote server with the address 10.0.0.10:

Router# ping 10.0.0.10 <Return>

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echoes to 10.0.0.10, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms

Router#




If the connection fails, verify that you have the correct IP address for the destination and that the device is active (powered on), and repeat the ping command.

Using loopback Commands

The loopback test allows you to troubleshoot, detect, and isolate equipment malfunctions by testing the connection between the OC-3c interface and a remote device. The loop subcommand places an interface in internal loopback (also called local loopback) or line loopback mode, which enables test packets that are generated from the ping command to loop through a remote device or a cable. If the packets complete the loop, the connection is good. If not, you can isolate a fault to the remote device or the cable in the path of the loopback test.

Configuring an Interface for Internal Loopback

The default loopback setting is for no loopback. With internal (or local) loopback, packets from the router are looped back in the framer. Outgoing data gets looped back to the router interface without actually being transmitted. Internal loopback is useful for checking that the OC3 POS line card is working. To configure an interface for internal loopback, enter the loop internal command:

Router(config)# interface atm 3/0

Router(config-if)# loop internal




To disable internal loopback, enter the no loop internal command.

Configuring an Interface for Line Loopback

The default loopback setting is for no loopback. With line loopback, the receive (RX) fiber is logically connected to the transmit (TX) optical fiber cable so that packets from the remote router are looped back to it. Incoming data gets looped around and retransmitted without actually being received. To configure an interface for line loopback, enter the loop line command:

Router(config)# interface atm 3/0

Router(config-if)# loop line




To disable line loopback, enter the no loop line command.

Performing an Advanced Configuration

The following sections include steps for configuring and customizing various ATM features of your OC3 ATM line card:

• Configuring the OC3 ATM Line Card for OC-3

• Configuring VCs

• Configuring PVCs

• Configuring SVCs

• Configuring Classical IP and ARP over ATM

Configuring the OC3 ATM Line Card for OC-3

To configure the OC3 ATM line card for OC-3, perform the following tasks in interface configuration mode:

	Command	Purpose
Step 1	Router# interface atm slot/port	Specify an ATM interface to configure. To use these commands, you need to be in interface configuration mode. (For the appropriate interface address to use for your system, see  Table 4-3.)
Step 2	Router(config-if)# atm clock internal	Select the transmit clock source. This can be internal or derived from the receive clock through use of the no form of the command. By default, the receive clock source is used for the transmit clock.
Step 3	Router(config-if)# atm sonet stm-1	Specify SONET framing: STM-1 (optional). Use the no form of this command to return to the default, STS-3c framing.

Configuring VCs

Virtual circuits (VCs) are point-to-point connections between remote hosts and routers. A VC is established for each ATM end node with which the router communicates. The characteristics of the VC are established when the VC is created and include the following:

•Quality of service (QoS)

•ATM adaptation layer 5 (AAL5)

•Encapsulation type (logical link control [LLC], Subnetwork Address Protocol [SNAP], multiplexer [MUX], Network Level Protocol ID [NLPID], Integrated Local Management Interface [ILMI], Switched Multimegabit Data Service [SMDS], and ITU-T Q.2931 Signaling ATM Adaptation Layer [QSAAL])

When you assign a class of service to a VC for QoS management, the following default priority levels apply:

•Operation, Administration, and Maintenance (OAM) and signaling (highest level)

•Non-real-time variable bit rate (nrt-VBR)

•Unspecified bit rate (UBR), ILMI (lowest level)

Each VC supports the following router functions:

•Multiprotocol (AppleTalk, CLNS, DECnet, IP, IPX, VINES, XNS)

•Fast switching of IP packets

•Optimum, flow, and Cisco Express Forwarding (CEF) switching of IP packets

•Pseudobroadcast support for multicast packets

By default, fast switching is enabled on all OC3 ATM line card interfaces. These switching features can be turned off with interface configuration commands. Optimum, flow, or CEF switching must be explicitly enabled for each interface.

Configuring PVCs

To use a permanent virtual circuit (PVC), you must configure the PVC in both the router and the ATM switch. PVCs remain active until the circuit is removed from either configuration.

When a PVC is configured, all of the configuration options are passed on to the OC3 ATM line card. You can write these PVCs into nonvolatile RAM (NVRAM); they are used when the system image is reloaded.

Some ATM switches might have point-to-multipoint PVCs that do the equivalent of broadcasting. If a point-to-multipoint PVC exists, it can be used as the sole broadcast PVC for all multicast requests.

To configure a PVC, perform the two required tasks in the following sections:

• Creating a PVC

• Mapping a Protocol Address to a PVC

Creating a PVC

When you create any PVC, you create a virtual circuit descriptor (VCD) (a unique number) and attach it to the virtual path identifier (VPI) and virtual channel identifier (VCI). A VCD is an OC3 ATM line card-specific mechanism that identifies to the OC3 ATM line card the VPI-VCI pair to be used for a particular packet. The OC3 ATM line card requires this feature in order to manage the packets for transmission. The number chosen for the VCD is independent of the VPI-VCI pair used.

To create a PVC on the OC3 ATM line card interface, enter the following subcommand in interface configuration mode:

Command	Purpose
Router (config-if)# pvc [name] vpi/vci [ilmi | qsaal | letransport]	Configures a new ATM PVC by assigning a name (optional) and VPI/VCI numbers. Enters interface-ATM-VC configuration mode. Optionally configures ILMI, QSAAL, or SMDS encapsulation.

pvc [name] vpi/vci [ilmi | qsaal | l2transport]

The command values are as follows:

•vpi—The ATM network VPI to use for this VC in the range of 0 through 255.

•vci—The ATM network VCI to use for this VC in the range of 0 through 65,535.

•ilmi—Interim Local Management Interface (ILMI) use so that the router can receive SNMP traps and new network prefixes. The recommended vpi and vci values for the ILMI PVC are 0 and 16, respectively.

•qsaal—Used to configure an ATM main interface that uses SVC.

•l2transport—Layer 2 transport ATM virtual circuit configuration submode

Optional Commands

ATM Adaption Layer and Encapsulation

•aal-encap—(Optional) Configure the ATM adaptation layer (AAL) and encapsulation types:

–aal5snap: AAL5 + LLC/SNAP encapsulation. AAL5 Logical Link Control/Subnetwork Access Protocol (LLC/SNAP) encapsulation supports Inverse ARP and incorporates the LLC/SNAP that precedes the protocol datagram. This allows the multiple protocols to transverse the same PVC.

---

Note aal5snap is the default encapsulation and the most widely used because it allows multiple protocols to be carried over one PVC.

---

•aal5mux: AAL5 + MUX encapsulation. AAL5 MUX encapsulation supports only a single protocol (IP or IPX) per PVC.

–aal5ciscoppp: For Cisco's proprietary PPP over ATM, aal5ciscoppp supports only Cisco routers with ATM or asymmetric digital subscriber line (ADSL) interfaces. Use this type of encapsulation when PPP authentication is desired.

–aal5nlpid: AAL5 Network Layer Protocol Identification (NLPID) encapsulation allows ATM interfaces to interoperate with High-Speed Serial Interfaces (HSSIs) that are using an ATM data service unit (ADSU) and running ATM-Data Exchange Interface (DXI).

Other Optional Commands

•burst—(Optional) The burst cell size is an integer value, in the range 1 through 64,000. This value is the maximum number of ATM cells that the virtual circuit can transmit to the network at the peak rate of the PVC.

•oam seconds—(Optional) Specifies how often to generate an OAM F5 loopback cell from this virtual circuit. The default value is 10 seconds.

•inarp minutes—(Optional) Specifies how often inverse Address Resolution Protocol (ARP) datagrams will be sent on this virtual circuit. The default value is 15 minutes.

The pvc command creates PVC n and attaches the PVC to VPI and VCI. When you create any PVC, you also specify the ATM adaptation layer (AAL) and encapsulation. The AAL used is specified by aal and encapsulation by encap.

The peak and average rate selection values are specified in kilobits per second. Omitting peak and average values causes the PVC and those values to default to the line rate, with the peak and average values being equal.

You can configure the PVC for communication with ILMI, which enables the router to receive Simple Network Management Protocol (SNMP) traps and new network prefixes. Refer to the Wide-Area Networking Configuration Guide for details.

You can also configure the PVC to send OAM F5 loopback cells, which verify connectivity on the virtual circuit. The remote end must respond by echoing back such cells.

The following example creates a PVC on interface 0 in a Cisco 7304 router with a line card in slot 4 with VPI 0 and VCI 6. The PVC uses AAL AAL5-MUX with IP.

Router# config terminal

Router(config)# interface ATM4/0.1 point-to-multipoint

Router(config-subif)# ip address 10.1.1.1 255.255.255.252

Router(config-subif)# pvc 0/6

Router(config-if-atm-vc)# encapsulation aal5mux ip




See examples of PVC configurations in "ATM Configuration Examples".

Mapping a Protocol Address to a PVC

This section describes the procedure for mapping a protocol address to a PVC, which is a required task if you are configuring a PVC. The ATM interface supports a static mapping scheme that identifies the ATM addresses of remote hosts or routers. An address is specified as a virtual circuit descriptor (VCD) for a PVC (or network service access point [NSAP] address for SVC operation).

You enter mapping commands as groups. You first create a map list and then associate it with an interface. Begin the following steps in global configuration mode:

	Command	Purpose
Step 1	Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#	To enter these commands, you need to be in configuration mode.
Step 2	Router(config)# interface atm4/1.1 point-to-point	Creates a subinterface.
Step 3	Router(config-subif)#pvc 1/100	Create pvc vpi+1, pvic=100
Step 4	Router(config-if-atm-vc)#protocol ip 10.1.1.2 broadcast	Map IP porptocol with broadcast option
Step 5	Router(config-if-atm-vc)#Exit Router#	ip config EXIT

A map list can contain multiple map entries. The broadcast keyword specifies that this map entry is to be used when the corresponding protocol sends broadcast packets to the interface (for example, any network routing protocol updates). If you do not specify broadcast, the ATM software is prevented from sending routing protocol updates to the remote hosts.

If you do specify broadcast but do not set up point-to-multipoint signaling, pseudobroadcasting is enabled. To eliminate pseudobroadcasting and set up point-to-multipoint signaling on virtual circuits configured for broadcasting, refer to the Wide-Area Networking Configuration Guide.

You can create multiple map lists and associate them with one ATM interface only. You must create different map lists to associate with different interfaces. See the ATM Configuration Examples.

For further information on configuring ATM line cards for PVCs, refer to Wide-Area Networking Configuration Guide.

Configuring SVCs

ATM switched virtual circuit (SVC) service operates much like X.25 SVC service, although ATM allows much higher throughput. Virtual circuits are created and released dynamically, providing user bandwidth on demand. This service requires a signaling protocol between the router and the switch.

The ATM signaling software provides a method of dynamically establishing, maintaining, and clearing ATM connections at the User-Network Interface (UNI). The ATM signaling software conforms to the ATM Forum UNI 3.0 specification.

In UNI mode, the user is the router, and the network is an ATM switch. This is an important distinction. The Cisco router does not perform ATM-level call routing. Instead, the ATM switch does the ATM call routing, and the router routes packets through the resulting circuit. The router is viewed as the user and the LAN interconnection device at the end of the circuit, and the ATM switch is viewed as the network.

Figure 4-1 illustrates the router position in a basic ATM environment. The router is used primarily to interconnect LANs through an ATM network. Workstation C in Figure 4-1 is connected directly to the destination ATM switch. You can connect not only routers to ATM switches, but also any computer with an ATM interface that conforms to the ATM Forum UNI specification.

Figure 4-1 Basic ATM Environment

To use SVCs, complete the required tasks in the following sections:

• Configuring the PVC That Performs SVC Call Setup

• Configuring the Network Service Access Point Address

For further information on configuring the OC3 ATM line card for SVCs, see the Wide-Area Networking Configuration Guide.

Configuring the PVC That Performs SVC Call Setup

Unlike X.25 service, which uses in-band signaling (connection establishment done on the same circuit as data transfer), ATM uses out-of-band signaling. One dedicated PVC exists between the router and the ATM switch, over which all SVC call establishment and call termination requests flow. After the call is established, data transfer occurs over the SVC, from router to router. The signaling that accomplishes the call setup and teardown is called Layer 3 signaling or the Q.2931 protocol.

For out-of-band signaling, a signaling PVC must be configured before any SVCs can be set up. In Figure 4-2, a signaling PVC from the source router to the ATM switch is used to set up two SVCs. This is a fully meshed network; workstations A, B, and C can all communicate with one another.

Figure 4-2 One or More SVCs Require a Signaling PVC

To configure the signaling PVC for all SVC connections, enter the following command in interface configuration mode:

pvc [name] vpi/vci qsaal

---

Note This signaling PVC can be set up on a major interface only, not on the subinterfaces.

---

The VPI and VCI values must be configured consistently with the local switch. The standard value of VPI is 0; the standard value of VCI is 5.

See the "Example of SVCs in a Fully Meshed Network" section for a sample ATM signaling configuration.

Configuring the Network Service Access Point Address

Every ATM interface involved with signaling must be configured with a network service access point (NSAP) address. The NSAP address is the ATM address of the interface and must be unique across the network.

You can do one of the following to configure an NSAP address:

•Configure the complete NSAP address manually

•Configure the ESI and Selector fields

To configure the ESI and Selector fields, you must also configure a PVC to communicate with the switch through ILMI. The switch then provides the Prefix field of the NSAP address.

Configuring the Complete NSAP Address Manually

When you configure the ATM NSAP address manually, you must enter the entire address in hexadecimal format; that is, each digit entered represents a hexadecimal digit. To represent the complete NSAP address, you must enter 40 hexadecimal digits in the following format:

XX.XXXX.XX.XXXXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.XX

---

Note All ATM NSAP addresses must be entered in the dotted hexadecimal format shown, which conforms to the UNI specification.

---

Because the interface has no default NSAP address, you must configure the NSAP address for SVCs. To set the ATM interface source NSAP address, enter the following command in interface configuration mode:

nsap-address nsap-address

The following is an example of an NSAP address assigned to ATM interface 4/0 on a Cisco 7304 router:

Router (config-if)# interface atm 4/0

Router (config-if)# atm nsap-address AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12




You can display the ATM address for the interface by executing the show interfaces atm command.

Configuring the ESI and Selector Fields

You can configure the router to get the NSAP address prefix from the switch; however, the switch must be capable of delivering the NSAP address prefix to the router through ILMI, and the router must be configured with a PVC for communication with the switch through ILMI.

To configure the router to get the NSAP prefix from the switch and use locally entered values for the remaining fields of the address, complete the following tasks in interface configuration mode:

	Command	Purpose
Step 1	Router# interface atm slot/port	Specify an ATM interface to configure. To use these commands, you need to be in interface configuration mode.
Step 2	Router(config-if)# pvc vcd 0 16 ilmi	Configure an ILMI PVC on an ATM main interface for communicating with the switch by using ILMI. (For the appropriate interface address to use for your system, see  Table 4-3.)
Step 3	Router(config-if)# atm esi-address esi.selector	Enter the ESI and selector fields of the NSAP address.

In the atm esi-address command, the esi argument is 6 hexadecimal bytes long (12 digits), and the selector argument is 1 hexadecimal byte long (2 digits).

In the following example on a Cisco 7304 router, the ESI and Selector field values are assigned, and the ILMI PVC is set up:

Router(config-if)# interface atm 4/0

Router(config-if)# pvc 2 0 16 ilmi

Router(config-if)# atm esi-address 345678901234.12

Configuring Classical IP and ARP over ATM

Cisco implements both the ATM Address Resolution Protocol (ARP) server and ATM ARP client functions described in RFC 1577. RFC 1577 models an ATM network as a logical IP subnetwork on a LAN.

The tasks required to configure classical IP and ARP over ATM depend on whether there are SVCs or PVCs in the environment. For further information, refer to the Wide-Area Networking Configuration Guide.

Customizing the OC3 ATM Line Card

You can customize the OC3 ATM line card. The features you can customize have default values that will probably suit your environment and not need to be changed. However, you might need to enter configuration commands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. Perform the tasks in the following sections if you need to customize the OC3 ATM line card:

• Setting the MTU Size

• Configuring an ATM Interface for Local Loopback

• Configuring an ATM Interface for External Loopback

---

Note For the commands that follow, you need to be in interface configuration mode. To enter interface configuration mode, use the interface atm subcommand, followed by the interface address of the ATM interface you plan to configure. (For information on the interface atm subcommand and the interface address to use, see  Table 4-3.)

---

Setting the MTU Size

Each ATM interface has a default maximum packet size or maximum transmission unit (MTU) size. On the OC3 ATM line card, this number defaults to 4470 bytes, the range being 64 through 9216 bytes. To set the maximum MTU size, enter the following command in interface configuration mode:

Router(config-if)# mtu bytes

Configuring an ATM Interface for Local Loopback

To configure an ATM interface for local loopback (useful for checking that the OC3 ATM line card is working by looping the transmit data back to the receive data), use the following command:

Router(config-if)# loopback diagnostic

Router(config-if)# no loopback diagnostic




The no form of the command turns off local loopback.

Configuring an ATM Interface for External Loopback

To configure an ATM interface for external loopback (useful for checking that the OC3 ATM line card is working by looping the receive data back to the transmit data), use the following command:

Router(config-if)# loopback line

Router(config-if)# no loopback line




To configure an ATM interface for external loopback at the cell level, use the following command:

Router(config-if)# loopback cell

Router(config-if)# no loopback cell




To configure an ATM interface for external loopback at the payload level, use the following command:

Router(config-if)# loopback payload

Router(config-if)# no loopback payload




The no form of each command turns off external loopback.

Checking the Advanced Configuration

After configuring the new interface, you can display its status. You can also display the current state of the ATM network and connected virtual circuits. To show current virtual circuits and traffic information, enter the following commands in EXEC mode. (For information about EXEC mode, see the "Using the EXEC Command Interpreter" section.)

	Command	Purpose
Step 1	Router# show atm interface atm slot-number/0	Display ATM-specific information about an ATM interface.
Step 2	Router# show atm map	Display the configured list of ATM static maps to remote hosts on an ATM network.
Step 3	Router# show atm traffic	Display information about global traffic to and from all ATM networks connected to the router. Display a list of counters of all ATM traffic on this router.
Step 4	Router# show atm vc [vcd]	Display ATM virtual circuit information about all PVCs and SVCs (or a specific virtual circuit).
Step 5	Router# show sscop1	Display details for the ATM interface.
Step 6	Router# show atm arp-server	Display ATM ARP server table.
Step 7	Router# show atm ilmi-status	Display ATM ILMI information.

1 SSCOP = Service-Specific Connection-Oriented Protocol.

Traffic Management

The OC3 ATM line card supports the traffic-shaping parameters defined in Table 4-5. This ensures that generated traffic conforms to the ATM Forum Traffic Management Specification Version 4.0.

Table 4-5 Traffic-Shaping Parameters and Ranges

Traffic Parameter	Range	Default
Peak Rate •OC-3c	38 kbps to 77.5 Mbps and 155 Mbps	If the peak rate is not defined, each new VC is set to the maximum physical layer rate.
Average Rate	38 kbps < average < peak rate	Average = peak rate.
Maximum Burst Size	1 to 64,000	Equal to the OC3 ATM line card MTU size. (User-configurable on ATM interface only.)

---

Note The OC3 ATM line card supports UBR and nrt-VBR traffic only.

---

Testing and Troubleshooting the OC3 ATM Line Card

The following sections provide suggested guidelines for troubleshooting the OC3 ATM line card. Use the ping command to verify network connectivity, the debug commands to help solve network problems, and the show commands to display the current state of the network.

OC3 ATM Line Card Statistics

The OC3 ATM line card maintains a count of certain errors and tracks the ATM controller facility performance. In addition to keeping a count of these errors, the OC3 ATM line card also takes snapshots of the last VCI/VPI that caused the error. Each OC3 ATM line card error counter is made up of 16 bits. Errors counted include the following:

•CRC errors

•Giants received

•No buffers available

•Framing errors

•Application layer or physical layer errors

•Packet timeout errors on receive

The OC3 ATM line card provides line card-specific error statistics through the show interfaces atm command.

---

Note For examples of the show interfaces atm command for the supported platform, see the "Using the show interfaces Command" section.

---

The show controllers atm command displays the ATM framing information and ATM facility performance statistics.

The following is an example of the show controllers atm command from a Cisco 7304 router:

Router# show controllers atm 4/0

Interface ATM4/0 is up

Hardware is OC-3 ATM, bandwidth OC3 (155000Kbps)

Framer is PMC PM5351 S/UNI-TETRA (155-TETRA). SAR device is MXT4400 TSP

PortMakerI AAL5 SAR firmware version for MXT4400 Reassembly SAR:

major 0x1, minor 0x5, patch 0x0E, code level 0x0C

PortMakerI AAL5 SAR firmware version for MXT4400 Segmemtation SAR:

major 0x1, minor 0x5, patch 0x0E, code level 0x0C

hwidb = 0x43553890, ds = 0x435F0CE0, ds_vp = 0x435553E0, ds_vc = 0x4369E200

slot 4, slotunit 0, fci_type 0x0374, ticks 1000

atm_db_flags = 0x00048308

Current VCC count: current=10, peak=10

Framer Information:

Framing mode: SONET OC3 STS-3C. Clock source: line. Loopback mode: none.

RXCP received cells: 2064, TXCP transmitted cells: 353253850

Facility alarm:

Phy stats:

sbip lbip lfebe pbip pfebe hcse

--------------------------------------------------------------

9 12 l9 1 1 0

sbip: Section BIP8

lbip: Line BIP8/24

lfebe: Line FEBE

pbip: Path BIP8

pfebe: Path FEBE

hcse: Rx Cell HCS Error

Reassembler Counters:

RXBytes: 75924

RXCellsUnopenedChannel: 0

RXPacketsCRC32Error: 0

RXPacketsLECIDMatch: 0

RXCellsCRC10Error: 0

RXPacketsNoBuffers: 0

RXPacketsTrailerLen: 0

RXPacketsAbort: 0

RXPacketsMPSError: 0

RXPacketsDeEncapError: 0

Segmenter Counters:

TXBytes: 75924

TXPacketsMPSError: 0

Line Card FPGA Counters:

RXPackets: 688 RXBytes: 75924

TXPackets: 688 TXBytes: 75924




Using the Debug ATM Commands

The following debug commands help to solve ATM network problems.

•To create a dump of all protocol packets, use the debug atm packet command. The command displays the contents of the SNAP/NLPID/SMDS header followed by the first 40 bytes of a packet in hexadecimal format.

Router# debug atm packet




•To display errors, use the debug atm errors command. The command displays information from all detected ATM errors. This includes such errors as encapsulation failures and errors during ATM configuration.

Router# debug atm errors




•To display ATM events, use the debug atm events command. The command displays event changes to the OC3 ATM line card; reset, VC configurations, and OC3 ATM line card configurations are displayed.

Router# debug atm events




•To display information about OAM cells, use the debug atm oam command. The command displays the contents of OAM cells as they arrive from the network.

Router# debug atm oam




After using a debug command, turn off debugging with the no debug command.

Commands That Display ATM Information

You can use ATM show commands to display the current state of the ATM network and the connected VCs.

•To show current VCs and traffic information, use the show atm vc [vcd] command. Specifying a VCD displays specific information about that VCD.

Router# show atm vc [vcd]




•To show current information about an ATM interface, use the show atm interfaces command. The command displays ATM-specific information about an interface.

Router# show atm interfaces




•To show current ATM traffic, use the show atm traffic command. The command displays global information about traffic to and from all ATM networks connected to the router.

Router# show atm traffic




•To show the current ATM mapping, use the show atm map command. The command displays the active list of ATM static maps to remote hosts on an ATM network.

Router# show atm map




show atm vc

Use the show atm vc command to display the following types of statistics for all PVCs.

Router# show atm vc

VCD / Peak Avg/Min Burst

Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts

4/0.1 1 1 10000 PVC SNAP UBR 149760 UP

4/0.2 2 1 10001 PVC SNAP UBR 149760 UP

4/0.3 3 1 10002 PVC SNAP UBR 149760 UP

4/0.4 4 1 10003 PVC SNAP UBR 149760 UP

4/0.5 5 1 10004 PVC SNAP UBR 149760 UP




show atm vc 2

Use the show atm vc n command, where n is the VCD unique index value, to display statistics for a given PVC.

Router# show atm vc 2

ATM4/0.2: VCD: 2, VPI: 1, VCI: 10001

UBR, PeakRate: 149760

AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0

OAM frequency: 0 second(s)

InARP frequency: 15 minutes(s)

Transmit priority 4

InPkts: 15332898, OutPkts: 15332754, InBytes: 3519887760, OutBytes: 3519877324

InPRoc: 0, OutPRoc: 1

InFast: 46, OutFast: 233, InAS: 0, OutAS: 0

InPktDrops: 0, OutPktDrops: 0/0/0 (holdq/outputq/total)

InByteDrops: 0, OutByteDrops: 0

CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0

Out CLP=1 Pkts: 0

OAM cells received: 0

OAM cells sent: 0

Status: UP

VC 2 doesn't exist on interface ATM4/1

Router#

show interfaces atm

Use the show interfaces atm command to display statistics for the ATM interface you specify.

---

Note For examples of the show interfaces atm command for all supported platforms, see the "Using the show interfaces Command".

---

Use the show atm interface atm command to display statistics for the ATM interface you specify by its interface address.

Router#show atm interface atm 4/1.1




Interface ATM4/1:

AAL enabled: AAL5 , Maximum VCs: 2047, Current VCCs: 0




Maximum Transmit Channels: 0

Max. Datagram Size: 4528

PLIM Type: SONET - 155000Kbps, TX clocking: LINE

Cell-payload scrambling: ON

sts-stream scrambling: ON

0 input, 0 output, 0 IN fast, 0 OUT fast, 0 out drop

Avail bw = 155000

Config. is ACTIVE

router#

show atm interface atm

Use the show atm interface atm command to display statistics for the ATM interface you specify by its interface address.

Router# show atm interface atm 0/0




ATM interface ATM 0/0:

AAL enabled: AAL5, Maximum VCs: 2048, Current VCCs: 12

Max. Datagram Size:4528, MIDs/VC: 1024

PLIM Type:DS3 - 45Mbps, Framing is C-bit ADM,

DS3 lbo: short, TX clocking: LINE

Scrambling: OFF

227585 input, 227585 output, 0 IN fast, 0 OUT fast

Config. is ACTIVE




Use the show sscop command to display SSCOP details for the ATM interface.

Use the show version command to display the configuration of the system hardware (the number of each interface processor type installed), the software version, the names and sources of configuration files, and the boot images.

---

Note For examples of the show version command for all supported platforms, see "Using the show version or show hardware Commands".

---

Use the show protocols command to display the global (system-wide) and interface-specific status of any configured Layer 3 protocol.

Use the show running-config command to display the currently running OC3 ATM line card configuration in RAM:

Router# show running-config

interface ATM4/0

no ip address

!

interface ATM4/0.1 point-to-point

ip address 10.1.1.1 255.255.255.252

pvc 1/10000

encapsulation aal5snap

!

ATM Configuration Examples

The following sections contain examples of ATM interface configurations. For detailed configuration examples, refer to the router software publications listed in Related Documentation.

• Example of PVCs with AAL5 and LLC/SNAP Encapsulation

• Example of PVCs in a Fully Meshed Network

• Example of SVCs in a Fully Meshed Network

• Connecting Two OC3 ATM Line Cards Back to Back

For examples of emulated LAN configurations, refer to the Wide-Area Networking Configuration Guide.

Example of PVCs with AAL5 and LLC/SNAP Encapsulation

In the following example, PVC 5 is created on ATM interface 3/0 using LLC/SNAP encapsulation over AAL5. ATM interface 3/0 (IP address 10.0.0.1 255.0.0.0) connects with the ATM interface (IP address 10.0.0.2 255.0.0.0) at the other end of the connection. The static map list named atm1 declares that the next node is a broadcast point for multicast packets from IP.

interface ATM 3/0

ip address 10.0.0.1 255.0.0.0

map-group atm1

atm pvc 5 0 1 aal5snap

!

no ip classless

!

map-list atm1

ip 10.0.0.2 atm-vc 1 broadcast




The following example shows a typical ATM configuration for a PVC:

interface ATM 4/0

ip address 10.0.0.1 255.0.0.0

map-group atm

atm pvc 1 1 1 aal5snap

atm pvc 2 2 2 aal5snap

atm pvc 6 6 6 aal5snap

atm pvc 7 7 7 aal5snap

clns router iso-igrp comet

!

Router iso-igrp comet

net 47.0004.0001.0000.0c00.6666.00

!

Router igrp 109

network 10.255.255.255

!

ip domain-name CISCO.COM

!

map-list atm

ip 10.0.0.2 atm-vc 7 broadcast

clns 47.0004.0001.0000.0c00.6e26.00 atm-vc 6 broadcast




Example of PVCs in a Fully Meshed Network

Figure 4-3 shows a fully meshed network. The configurations for Routers A, B, and C follow. In this example, the routers are configured to use PVCs. Fully meshed indicates that each network node has either a physical circuit or a virtual circuit connecting it to every other network node. The two map-list statements configured in Router A identify the ATM addresses of Routers B and C. The two map-list statements in Router B identify the ATM addresses of Routers A and C. The two map-list statements in Router C identify the ATM addresses of Routers A and B.

Figure 4-3 Fully Meshed ATM Configuration Example

Router A

ip routing

interface atm 4/0.1 multipoint

ip address 10.21.168.1 255.255.255.0

pvc 0/10

encapsulation aal2snap

protocol ip 10.21.168.1 broadcast

pvc 0/30

encapsulation aal5snap

protocol ip 10.21.168.3 broadcast

Router B

ip routing

!

interface atm 2/0.1 multipoint

ip address 10.21.168.2 255.255.255.0

pvc 0/10

encapsulation aal2snap

protocol ip 10.21.168.1 broadcast

pvc 0/30

encapsulation aal5snap

protocol ip 10.21.168.3 broadcast

Router C

ip routing

interface atm 4/0.1 multipoint

ip address 10.21.168.3 255.255.255.0

pvc 0/20

encapsulation aal5snap

protocol ip 10.21.168.1 broadcast

pvc 0/30

encapsulation aal5snap

protocol ip 10.21.168.2 broadcast




Example of SVCs in a Fully Meshed Network

The following example is also a configuration for the fully meshed network shown in Figure 4-3, but one in which SVCs are used. PVC 1 is the signaling PVC.

Router A

interface atm 4/0

ip address 10.16.168.1 255.255.255.0

atm nsap-address AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12

atm maxvc 1024

pvc 0/5 qsaal

exit

!

svc svc-1 nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13

protocol ip 10.16.168.2

exit

!

svc svc-2 nsap CA.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12

protocol ip 10.16.168.3

exit

Router B

interface atm 2/0

ip address 10.16.168.2 255.255.255.0

atm nsap-address BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13

atm maxvc 1024

pvc 0/5 qsaal

exit

!

svc svc-1 nsap AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12

protocol ip 10.16.168.1

exit

!

svc svc-2 nsap CA.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12

protocol ip 10.16.168.3

exit

Router C

interface atm 4/0

ip address 10.16.168.3 255.255.255.0

atm nsap-address CA.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12

atm maxvc 1024

pvc 0/5 qsaal

exit

!

svc nsap AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12

protocol ip 10.16.168.1

exit

!

svc nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13

protocol ip 10.16.168.2

exit

Connecting Two OC3 ATM Line Cards Back to Back

Two routers, each containing an OC3 ATM line card, can be connected directly with a standard cable, which allows you to verify the operation of the ATM port or to directly link the routers to build a larger node.

To connect two routers, attach the cable between the ATM port on one and the ATM port on the other.

By default, the OC3 ATM line card "expects" a connected ATM switch to provide transmit clocking. To specify that the OC3 ATM line card generates the transmit clock internally for SONET physical layer interface module (PLIM) operation, add the atm clock internal command to your configuration.

---

Note For OC-3c (SONET) interfaces, one of the OC3 ATM line cards in each router must be configured to supply its internal clock to the line.

---

The following is an example of configuration file commands for two routers connected through their OC-3c interface:

First Router

interface atm 3/0

atm clock internal

interface atm3/0.1 point-to-point

ip address 10.0.0.1 255.0.0.0

pvc 1/5

encapsulation aal5snap

protocol ip 10.0.0.2 broadcast

Second Router

interface atm 3/0

interface atm3/0.1 point-to-point

ip address 10.0.0.2 255.0.0.0

pvc 1/5

encapsulation aal5snap

Upgrading Your Bootdisk Image

The boot image contains a subset of the Cisco IOS software. This image is used to perform network booting or to load Cisco IOS images onto the router. This image is also used if the system cannot find a valid system image.

When you upgrade your Cisco IOS software to the minimum required software release (see Table 2-1 on page 2-2), we recommend that you also upgrade your bootdisk image. To upgrade your boot image, you can copy the new boot image from a network server to boot memory on your router. To copy a boot image from a Trivial File Transfer Protocol (TFTP) server to boot memory, complete the tasks shown in the following table:

	Command	Purpose
Step 1	Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#	Specify that the terminal is the source for commands, and enter configuration mode. To enter the commands that follow, you need to be in configuration mode.
Step 2	Router(config)# show flash all	(Optional) If you do not already know it, learn the exact spelling of the system image filename in bootdisk memory.
Step 3	Router(config)# copy flash tftp	Make a backup copy of the current bootdisk image.
Step 4	Router(config)# copy tftp flash	Copy a boot image to bootdisk memory.
Step 5	Router(config)# ip-address or name	When prompted, enter the IP address or domain name of the server.

For further information, such as how to set up the TFTP server, refer to the Configuration Fundamentals Configuration Guide.

CLI-Controlled OIR

Line cards can be removed from the Cisco 7304 router without disrupting data flow by using the hw-module slot slot # stop/start command in EXEC mode. The hw-module slot slot # stop command will stop traffic, shut down all line card interfaces, and deactivate the line card. The hw-module slot slot # start command resets the line card, puts the line card back online, and turns off the OIR LED.

---

Note Upon insertion of a line card, the system will automatically activate the card. The hw-module slot slot # start command is only necessary when reactivating an installed line card that has been deactivated with the hw-module slot slot # stop command.

---

To remove and install an active line card in slot 2, proceed as follows:

Router# hw-module slot 2 stop

When the OIR LED turns green, the line card in slot 2 has been deactivated and can be physically removed and replaced with a new line card (see Line Card Removal and Installation.)

When the new line card is inserted in slot 2 it is automatically reset, put online, and the OIR LED is turned off.

Posted: Tue Jun 28 09:56:55 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.