cc/td/doc/product/core/cis7300/linecard
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring the 1-Port OC-12 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 Connectivity

Using loopback Commands

Performing an Advanced Configuration

Configuring the OC-12 ATM Line Card for OC-12c (STM-4c) Framing

About Configuring VCs

About Configuring PVCs

Configuring SVCs

Configuring Classical IP and ARP over ATM

Customizing the 1-Port OC-12 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 1-Port OC-12 ATM Line Card

1-Port OC-12 ATM Line Card Statistics

Using the debug atm Commands

Commands That Display ATM Information

More Troubleshooting 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 1-Port OC-12 ATM Line Cards Back to Back

Upgrading Your Bootdisk Image

CLI-Controlled OIR


Configuring the 1-Port OC-12 ATM Line Card

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

• Using the EXEC Command Interpreter

• Configuring the Interfaces

• Checking the Configuration

• Performing an Advanced Configuration

• Customizing the 1-Port OC-12 ATM Line Card

• Checking the Advanced Configuration

• Traffic Management

• Testing and Troubleshooting the 1-Port OC-12 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.

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 OC-12 ATM line card is installed correctly (the STATUS LED turns green), 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 OC-12 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 OC-12 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 OC-12 ATM line card, refer to the appropriate configuration publications listed in the Related Documentation section.

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 the "Using the EXEC Command Interpreter" section section 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:

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 commands, 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 command (followed by the interface address of the interface), and 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 Example 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 OC-12 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 new interface is now in the correct state (shut down) using the show interfaces atm command to display the specific interface.

Table 4-2 Example of the show interfaces atm Command

Platform
Command
Example

Cisco 7304 router

show interfaces atm followed by slot/port (slot-number/interface-port-number)

The example is for interface 0 on an OC-12 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 Reenable the interface by doing the following:

a. Repeat Step 3 to reenable 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 the "Related Documentation" section.

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 commands, 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 command, followed by the interface address of the interface you plan to configure. Table 4-3 shows an example.

Table 4-3 Example of the interface atm Command

Platform
Command
Example

Cisco 7304 routers

interface atm, followed by slot/port (slot-number/interface-port-number)

The example is for the interface 0 for the OC-12 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 command, as in the following example:

Router(config-if)# ip address 10.0.0.1 255.0.0.0

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

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

Step 6 After including all of the configuration commands 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.

Note 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 Connectivity

• 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 OC-12 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 the "Related Documentation" section.

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 4


show c7300

Displays types of line cards with status information for each installed line card

Router# show c7300


show interfaces atm interface-port-number/slot

Displays status information about a specific ATM interface in a Cisco 7304 router

Router# show interfaces atm 4/0


show protocols

Displays protocols configured for the entire system and for specific interfaces

Router# show protocols


show running-config

Displays the running configuration files

Router# show running-config


show startup-config

Displays the configuration stored in NVRAM

Router# show startup-config


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

• Using the ping Command to Verify Network Connectivity

• Using loopback Commands

Proceed to the "Using the ping Command to Verify Network Connectivity" section 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 only.

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

Router# show version

Cisco IOS Software, 7300 Software (C7300-JS-M), Version 12.2(25S2.041109.),
Copyright (c) 1986-2004 by Cisco Systems, Inc.
Compiled Tue 09-Nov-04 04:31 by

ROM: System Bootstrap, Version 12.1(12r)EX1, RELEASE SOFTWARE (fc1)
Currently running ROMMON from ROM 1
WS_REG_0 uptime is 1 hour, 5 minutes
Uptime for this control processor is 1 hour, 5 minutes
System returned to ROM by bus error at PC 0x41941398, address 0x20 at 20:10:58 UTC Thu Nov 11 2004
System image file is "disk0:c7300-js-mz.2004-11-09.x"

cisco 7300 (NSE100) processor (revision B) with 458752K/65536K bytes of memory.
Processor board ID SCA070200CS
R7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2, 1024KB L3 Cache
4 slot midplane, Version 67.49

Last reset from software reset or reload
PXF processor tmc0 'system:pxf/ucode1' is running ( v4.1 ).
PXF processor tmc1 'system:pxf/ucode1' is running ( v4.1 ).
1 FastEthernet interface
4 Gigabit Ethernet interfaces
2 ATM interfaces
509K bytes of non-volatile configuration memory.
31168K bytes of ATA compact flash in bootdisk (Sector size 512 bytes).
62976K bytes of ATA compact flash in disk0 (Sector size 512 bytes).
Standby route processor in slot 2 is down.
Configuration register is 0x2002 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.

Following is an example of the show diag slot command for an OC-12 ATM line card in slot 4 of a Cisco 7304 router:

Router# show diag 4
Slot 4:
OC12 ATM with SFP Line Card, 1 port
Line Card state: Active
Insertion time: 00:15:14 ago
Bandwidth points: 620000
EEPROM contents at hardware discovery:
Controller Type : 1223
Hardware Revision : 3.1
Boot Timeout : 0 msecs
PCB Serial Number : CSJ08407407
PCB Part Number : 73-6828-04
Board Revision : A0
Fab Version : 02
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Deviation Number : 0-0
Product Identifier (PID) : 7300-1OC12ATM
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 04 C7 41 03 01 46 00 00 C1 8B 43 53 4A
0x10: 30 38 34 30 37 34 30 37 82 49 1A AC 04 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 31 4F 43 31 32 41 54 4D 20
0x40: 20 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 49 44 35
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 B9 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
0x100: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x110: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x120: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x140: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FPGA information:
Current FPGA version : 00.19
IOS bundled FPGA version : 00.19
CPLD version : 00.06
Router#


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.

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) Up 01:06:35 ago
2,3 NSE100 (Standby) Down 01:06:33 ago
4 1OC12-ATM Active 01:06:30 ago
5 1OC12-ATM Active 01:06:29 ago

FPGA information:
Hardware FPGA version
Slot Card Type Version Bundled Flash Current
---- --------- -------- ------- ------- -------
0 NSE100 (MB) 02.01 01.07 01.07 01.07
0 NSE100 (DB) 02.01 01.07 01.07 01.07
4 1OC12-ATM 02.01 00.19 00.19 00.19
5 1OC12-ATM 02.01 00.19 00.19 00.19

* - Card needs an FPGA update
# - Card needs to be reloaded for the new FPGA to take effect

System is compliant with hardware configuration guidelines.

Network IO Interrupt Throttling:
throttle count=0, timer count=0
active=0, configured=1
netint usec=4000, 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 commands 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.

Following is an example of the show interfaces atm command used with a Cisco 7304 router. In this example, the OC-12 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-12 ATM, address is 000b.5f2d.2e80 (bia 000b.5f2d.2e80)
MTU 4470 bytes, sub MTU 4470, BW 599040 Kbit, DLY 80 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5
2047 maximum active VCs, 2040 current VCCs
VC idle disconnect time: 300 seconds
0 carrier transitions
Last input never, output 00:30:42, 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: None
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
2040 packets output, 57120 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
Router#


Using the ping Command to Verify Network Connectivity

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 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 time out 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-12 ATM interface and a remote device. The loop command 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 Diagnostic 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 receiver without actually being transmitted. Internal loopback is useful for checking that the OC-12 ATM line card is working. To configure an interface for internal loopback, enter the loop diagnostic command:

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

To disable internal loopback, enter the no loop diagnostic 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 OC-12 ATM line card:

• Configuring the OC-12 ATM Line Card for OC-12c (STM-4c) Framing

• About Configuring VCs

• About Configuring PVCs

• Configuring SVCs

• Configuring Classical IP and ARP over ATM

Configuring the OC-12 ATM Line Card for OC-12c (STM-4c) Framing

To configure the OC-12 ATM line card for OC-12c (STM-4c) framing, perform the following tasks in interface configuration mode:

 
Command
Purpose

Step 1 

Router# interface atm slot/port

Specifies an ATM interface to configure. To use these commands, you need to be in interface configuration mode. (See Table 4-3 for examples.)

Step 2 

Router(config-if)# atm clock internal

Select s 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-4c

Specifies SONET framing: STM-4c (optional). Use the no form of this command to return to the default, STS-12c framing.

Step 4 

Router(config-if)# exit

Exits configuration mode.

About 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

•Pseudo broadcast support for multicast packets

By default, fast switching is enabled on all OC-12 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.

About 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 OC-12 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

You can create the PVC on either the main interface or the subinterface.

For example, to create a PVC on the subinterface, you can use this syntax:

 
Command
Purpose

Step 1 

Router# configure terminal

Enters configuration mode

Step 2 

Router (config)# interface atm 1/0.100 point-to-point

Create a sub interface

Step 3 

Router (config-subif)# ip address 10.1.1.1 255.0.0.0

Creates link to ip address

Step 4 

Router (config)# pvc 1/300

Creates PVC (vpi+1, pvc=300)

Step 5 

Router (config)# encapsulation aal5snap

Creates AAL5SNAP encapsulation

Step 6 

Router (config)# control Z

Exits configuration mode

Optional Commands for ATM Adaptation Layer and Encapsulation

The following list of optional commands are used to 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 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).

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

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

Enters configuration mode

Step 2 

Router(config)# int atm 4/1.1 point-to-point

Creates a subinterface.

Step 3 

Router(config-subif)# pvc 1/100

Creates a PVC (vpi+1, pvic=100)

Step 4 

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

Create IP AAL5MUX encapsulation

Step 5 

Router(config-if-atm-vc)# protocol ip 10.1.1.2 broadcast

Maps the IP protocol with broadcast option

Step 6 

Router(config-if-atm-vc)# cntl Z

Router#

Exits configuration mode

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, pseudo broadcasting is enabled. To eliminate pseudo broadcasting and set up point-to-multipoint signaling on virtual circuits configured for broadcasting, refer to the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/wan_vcg.htm

For more information, see:

•Cisco IOS Configuration Fundamentals and Network Management Configuration Guide, Release 12.3 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/cfun_vcg.htm

•Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/fun_r/index.htm

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" section.

For further information on configuring the OC-12 ATM line card for PVCs, refer to the Wide-Area Networking Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/wan_vcg.htm

For more information about mapping and routing protocols, refer to the following information at the listed URLs:

•Multiple Routed Protocols Over ATM PVCs Using VC Multiplexing

http://www.cisco.com/warp/public/121/routed_rfc1483.html

•Multiple Routed Protocols over ATM PVCs Using LLC Encapsulation

http://www.cisco.com/warp/public/121/routed_LLC.html

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.

For more information about configuring SVCs, refer to Configuring ATM SVCs With Static Map Statements at the following URL:

http://www.cisco.com/warp/public/121/atm_svc.html

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

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

• Configuring the Network Service Access Point Address

For further information on configuring the OC-12 ATM line card for SVCs, see the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/wan_vcg.htm

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-1 Basic ATM Environment

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

Command
Purpose

pvc [name] vpi/vci qsaal

Configures the signaling PVC for an ATM main interface that uses SVCs.


Note This signaling PVC can be set up only on an ATM main interface, not on ATM subinterfaces.

Also see Configuring ATM at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/wan_c/wcdatm.htm

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.

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

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:

• Configuring the Complete NSAP Address Manually

• Configuring the ESI and Selector Fields

To configure the end system identifier (ESI) and Selector fields, you must also configure a PVC to communicate with the switch through Interim Local Management Interface (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:

Command
Purpose

nsap-address nsap-address

Configures the NSAP address for SVCs


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.

For more information, see Static and Dynamic Mapping at the following URL:

http://www.cisco.com/warp/public/121/atm_svc.html

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(config-if)# interface atm 4/0

Selects the interface

Step 2 

Router(config-if)# pvc FCC 0/16 ilmi

Configures an ILMI PVC on an ATM main interface for communicating with the switch by using ILMI. (See  Table 4-3 for an example.)

Step 3 

Router(config-if)# atm Asia-address esi.selector

Enters the end station ID (ESI) and selector fields of the NSAP address. End station ID field value in hexadecimal; 6 bytes long. Selector field value in hexadecimal; 1 byte long

Step 4 

Router (config-if)# exit

Returns to interface configuration mode

In the atm Asia-address command, the Asia 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 FCC 0/16 ilmi
Router(config-if)# atm Asia-address 345678901234.12
Router(config-if)# exit

Note The ESI address is local and is required to create and register a 20-byte NSAP address with the ATM switch.

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 Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/wan_vcg.htm

Customizing the 1-Port OC-12 ATM Line Card

You can customize the OC-12 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 OC-12 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 must be in interface configuration mode. To enter interface configuration mode, use the interface atm command, followed by the interface address of the ATM interface you plan to configure. (For information on the interface atm command 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 OC-12 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 OC-12 ATM line card is working by looping the transmit data back to the receive data), use the following command:

Router(config-if)# 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 OC-12 ATM line card is working by looping the receive data back to the transmit data), use the following command:

Router(config-if)# loopback line

The no form of each command turns off external loopback.

For more information, see Understanding Loopback Modes on Cisco Routers at the following URL:

http://www.cisco.com/warp/public/121/atmloopback.html

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.

 
Command
Purpose

Step 1 

Router# show atm interface atm slot-number/interface port number

Displays ATM-specific information about an ATM interface.

Step 2 

Router# show atm map

Displays the configured list of ATM static maps to remote hosts on an ATM network.

Step 3 

Router# show atm traffic

Displays 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]

Displays ATM virtual circuit information about all PVCs and SVCs (or a specific virtual circuit).

Step 5 

Router# show sscop1

Displays details for the ATM interface.

Step 6 

Router# show atm arp-server

Displays ATM ARP server table.

Step 7 

Router# show atm ilmi-status

Displays ATM ILMI information.

1 SSCOP = Service-Specific Connection-Oriented Protocol.

Traffic Management

The OC-12 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-12

38 kbps to 599040 kbps

If the peak rate is not defined, each new VC is set to the maximum physical layer rate.

Sustained Cell Rate (SCR) Average rate

38 kbps <SCR < 299520 for vbr-nrt

Average = peak rate

Maximum burst size

1 to 65,535

Equal to the OC-12 ATM line card MTU size. (User-configurable on ATM interface only.)


•ATM Forum Traffic Management Specification Version 4.0

ftp://ftp.atmforum.com/pub/approved-specs/af-tm-0056.000.pdf

•Understanding the VBR-nrt Service Category and Traffic Shaping for ATM VCs

http://www.cisco.com/warp/public/121/atm_vbrshape.shtml

Note The OC-12 ATM line card supports universal broadband router (UBR) and nrt-VBR traffic only.

Testing and Troubleshooting the 1-Port OC-12 ATM Line Card

The following sections provide suggested guidelines for troubleshooting the OC-12 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.

The following topics are covered in this section:

• "1-Port OC-12 ATM Line Card Statistics" section

• "Using the debug atm Commands" section

• "Commands That Display ATM Information" section

• "More Troubleshooting Information" section

1-Port OC-12 ATM Line Card Statistics

The OC-12 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 OC-12 ATM line card also takes snapshots of the last VCI/VPI that caused the error. Each OC-12 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 time-out errors on receive

You can use the following ATM commands to gather statistical information about the OC-12 ATM line card.

To display line card-specific error statistics, use the show interfaces atm command.

Router# show interface atm

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

To display the ATM framing information and ATM facility performance statistics, use the show controllers atm command.

Router# show controllers atm 4/0

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 administratively down
Hardware is OC-12 ATM, bandwidth OC12 (622000Kbps)
SFP is SFP_OC12_MM, Framer is PMC PM5357 S/UNI-SATURN (622-SATURN).
SAR device is MXT4400 TSP
PortMakerI AAL5 SAR firmware version for MXT4400 Reassembly SAR:
major 0x1, minor 0x6, patch 0x03, code level 0x00
PortMakerI AAL5 SAR firmware version for MXT4400 Segmemtation SAR:
major 0x1, minor 0x6, patch 0x03, code level 0x00
hwidb=0x45BEF610, ds=0x45BF0A40, ds_vp=0x45C49A00, ds_vc=0x45BF18C0
slot=4, slotunit=0, fci_type=0x04C7, ticks=405
atm_db_flags=0x00048300
Current VCC count: current=0, peak=100
Framer Information:
Framing mode: SONET OC12 STM-4. Clock source: line. Loopback mode: none.
Facility alarm: None
S1 byte: in synchronization
Phy stats:
sbip lbip lfebe pbip pfebe hcse
------------------------------------------------------------------------
86 294 282 65670 70241 0
sbip: Section BIP8
lbip: Line BIP8/96
lfebe: Line FEBE
pbip: Path BIP8
pfebe: Path FEBE
hcse: Rx Cell HCS Error
RXCP received cells: 89110445, TXCP transmitted cells: 602953649
PATH TRACE BUFFER : STABLE
Remote hostname :
Remote interface:
Remote IP addr :

Reassembler Counters:
RXBytes: 3920822400
RXCellsUnopenedChannel: 849
RXPacketsCRC32Error: 0
RXPacketsLECIDMatch: 0
RXCellsCRC10Error: 0
RXPacketsNoBuffers: 0
RXPacketsTrailerLen: 0
RXPacketsAbort: 0
RXPacketsMPSError: 0
RXPacketsDeEncapError: 0
RXPacketsReasmTO: 0
Segmenter Counters:
TXBytes: 3920829148
TXPacketsMPSError: 0
Line Card FPGA Counters:
RXPackets: 14851600 RXBytes: 3920822400 RxMTUPacketDrop: 0
TXPackets: 14851841 TXBytes: 3920829148 TXDataPacketDrop: 0
Router#


Using the debug atm Commands

Use the following debug atm commands help to solve ATM network problems.

Table 4-6 Using debug Commands 

Command
Function
Example

debug atm packet

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

debug atm error

Displays information from all detected ATM errors. This includes such errors as encapsulation failures and errors during ATM configuration.

Router# debug atm errors


debug atm events

Displays event changes to the OC-12 ATM line card; reset, VC configurations, and OC-12 ATM line card configurations are displayed.

Router# debug atm events


debug atm oam

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

The following commands display information about the OC-12 ATM line card.

Table 4-7 Using show Commands 

Command
Function
Example

show atm vc [vcd]

Displays current vc or vcd traffic information the vc or vdc# is the unique index value for the the vc or vdc.

Router# show atm vc [vcd]

show atm interfaces atm

Displays statistics for the ATM interface you specify by its interface address.

Router# show atm interfaces atm slot/port


show atm traffic

Displays global information about traffic to and from all ATM networks connected to the router.

Router# show atm traffic


show atm map

Displays the active list of ATM static maps to remote hosts on an ATM network.

Router# show atm map


show sscop atm

Displays SSCOP details for the ATM interface.

Router# show sscop atm 1/0

show protocols

Displays the global (system-wide) and interface-specific status of any configured Layer 3 protocol.

Router# show protocols

show running-config

Displays the currently running OC-12 ATM line card configuration in RAM.

Router# show running-config


Examples

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 100 PVC NLPID UBR 599040 UP
4/0.2 2 1 101 PVC NLPID UBR 599040 UP
4/0.3 3 1 102 PVC NLPID UBR 599040 UP
4/0.4 4 1 103 PVC NLPID UBR 599040 UP
4/0.5 5 1 104 PVC NLPID UBR 599040 UP
4/0.6 6 1 105 PVC NLPID UBR 599040 UP
4/0.7 7 1 106 PVC NLPID UBR 599040 UP
4/0.8 8 1 107 PVC NLPID UBR 599040 UP
4/0.9 9 1 108 PVC NLPID UBR 599040 UP
4/0.10 10 1 109 PVC NLPID UBR 599040 UP
4/0.11 11 1 110 PVC NLPID UBR 599040 UP
4/0.12 12 1 111 PVC NLPID UBR 599040 UP
4/0.13 13 1 112 PVC NLPID UBR 599040 UP
4/0.14 14 1 113 PVC NLPID UBR 599040 UP
4/0.15 15 1 114 PVC NLPID UBR 599040 UP
4/0.16 16 1 115 PVC NLPID UBR 599040 UP
4/0.17 17 1 116 PVC NLPID UBR 599040 UP
4/0.18 18 1 117 PVC NLPID UBR 599040 UP
4/0.19 19 1 118 PVC NLPID UBR 599040 UP

Router# show atm vcd 13

ATM4/0.13: VCD: 13, VPI: 1, VCI: 112
UBR, PeakRate: 599040
AAL5-NLPID, etype:0x2, Flags: 0xC21, VCmode: 0x0
OAM frequency: 0 second(s)
InARP DISABLED
Transmit priority 4
InPkts: 35926, OutPkts: 371, InBytes: 2371116, OutBytes: 24448
InPRoc: 0, OutPRoc: 1
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0
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
ATM5/0.2053: VCD: 13, VPI: 1, VCI: 2152
UBR, PeakRate: 599040
AAL5-NLPID, etype:0x2, Flags: 0xC21, VCmode: 0x0
OAM frequency: 0 second(s)
InARP DISABLED
Transmit priority 4
InPkts: 65133, OutPkts: 370, InBytes: 4298778, OutBytes: 24382
InPRoc: 0, OutPRoc: 1
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
InPktDrops: 0, OutPktDrops: 0
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
Router#


Router# show atm interface atm 4/0

Interface ATM4/0:
AAL enabled: AAL5 , Maximum VCs: 2047, Current VCCs: 2040

Maximum Transmit Channels: 0
Max. Datagram Size: 4528
PLIM Type: SONET - 622000Kbps, TX clocking: LINE
Cell-payload scrambling: ON
sts-stream scrambling: ON
0 input, 2040 output, 0 IN fast, 0 OUT fast, 0 out drop
Avail bw = 622000
Config. is ACTIVE
Router#


Router# show sscop atm 1/0

SSCOP details for interface ATM3/0
Current State = Idle, Uni version = 4.0
Send Sequence Number: Current = 0, Maximum = 30
Send Sequence Number Acked = 0
Rcv Sequence Number: Lower Edge = 0, Upper Edge = 0, Max = 30
Poll Sequence Number = 0, Poll Ack Sequence Number = 1
Vt(Pd) = 0 Vt(Sq) = 0
Timer_IDLE = 10 - Inactive
Timer_CC = 1 - Inactive
Timer_POLL = 1000 - Inactive
Timer_KEEPALIVE = 5 - Inactive
Timer_NO-RESPONSE = 45 - Inactive
Current Retry Count = 0, Maximum Retry Count = 10

For more information, see Understanding SSCOP Messages on Router ATM Interfaces at the following URL:

http://www.cisco.com/warp/public/121/sscop_messages.html

Router# show protocols

Global values:
Internet Protocol routing is enabled
DECNET routing is enabled
XNS routing is enabled
Appletalk routing is enabled
X.25 routing is enabled
Ethernet 0 is up, line protocol is up
Internet address is 192.168.1.1, subnet mask is 255.255.255.0
Decnet cost is 5
XNS address is 2001.AA00.0400.06CC
AppleTalk address is 4.129, zone Twilight
Serial 0 is up, line protocol is up
Internet address is 192.168.7.49, subnet mask is 255.255.255.240
Ethernet 1 is up, line protocol is up
Internet address is 192.168.2.1, subnet mask is 255.255.255.0
Decnet cost is 5
XNS address is 2002.AA00.0400.06CC
AppleTalk address is 254.132, zone Twilight
Serial 1 is down, line protocol is down
Internet address is 192.168.7.177, subnet mask is 255.255.255.240
AppleTalk address is 999.1, zone Magnolia Estates


For more information on the parameters or protocols shown in this sample output, see:

•Cisco IOS Network Protocols Configuration Guide, Part 1

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c/

•Network Protocols Configuration Guide, Part 2

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np2_c/

•Network Protocols Configuration Guide, Part 3

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np3_c/

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
!


More Troubleshooting Information

For more information about troubleshooting, see the following documents:

•Troubleshooting IP over ATM PVC Connectivity

http://www.cisco.com/warp/public/121/ipoveratm.html

•ATM PVC, SVC, Soft-PVC, and PVP Frequently Asked Questions

http://www.cisco.com/warp/public/121/pvcfaq_23520.html

•Configuring RFC 1577 and RFC 2225 Over SVCs

http://www.cisco.com/warp/public/121/1577svc_19150.html

•CRC Troubleshooting Guide for ATM Interfaces

http://www.cisco.com/warp/public/121/crc_tshooting.html

•Troubleshooting ATM PVCs in a WAN Environment

http://www.cisco.com/warp/public/121/newchapter.htm

ATM Configuration Examples

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

• 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 1-Port OC-12 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 172.21.168.1 255.255.255.0
pvc 0/10
encapsulation aal2snap
protocol ip 172.21.168.1 broadcast
pvc 0/30
encapsulation aal5snap
protocol ip 172.21.168.3 broadcast


Router B

ip routing
!
interface atm 2/0.1 multipoint
ip address 172.21.168.2 255.255.255.0
pvc 0/10
encapsulation aal2snap
protocol ip 172.21.168.1 broadcast
pvc 0/30
encapsulation aal5snap
protocol ip 172.21.168.3 broadcast



Router C

ip routing

interface atm 4/0.1 multipoint
ip address 172.21.168.3 255.255.255.0
pvc 0/20
encapsulation aal5snap
protocol ip 172.21.168.1 broadcast
pvc 0/30
encapsulation aal5snap
protocol ip 172.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 172.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 172.16.168.2
exit
!
svc svc-2 nsap CA.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12
protocol ip 172.16.168.3
exit



Router B

interface atm 2/0

ip address 172.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 172.16.168.1
exit
!
svc svc-2 nsap CA.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.12
protocol ip 172.16.168.3
exit


Router C

interface atm 4/0

ip address 172.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 172.16.168.1
exit
!
svc nsap BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1334.13
protocol ip 172.16.168.2
exit


Connecting Two 1-Port OC-12 ATM Line Cards Back to Back

Two routers, each containing an OC-12 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 OC-12 ATM line card "expects" a connected ATM switch to provide transmit clocking. To specify that the OC-12 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 OC-12 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
protocol ip 10.0.0.1 broadcast


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, 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 the bootdisk on your router. To copy a boot image from a Trivial File Transfer Protocol (TFTP) server to the bootdisk, 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)# dir bootdisk

(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 bootdisk: tftp

Make a backup copy of the current bootdisk image.

Step 4 

Router(config)# copy tftp bootdisk

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 4 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 the "Line Card Removal and Installation" section on page 3-3.)

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

hometocprevnextglossaryfeedbacksearchhelp

Posted: Tue Mar 1 11:06:19 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.