cc/td/doc/product/dsl_prod/6400
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring ATM Interfaces

Configuring ATM Interfaces

This chapter tells you how to explicitly configure ATM interfaces for the Cisco 6400 node line card (NLC), rather than depending on Interim Local Management Interface (ILMI) auto-configuration (which senses the peer interface type and configures the system interfaces appropriately).

The network configuration modifications described in this chapter are used to explicitly specify your ATM network operation. The Cisco 6400 defaults to a working configuration suitable for most networks. However, you might need to customize the configuration for your network.


Note For a description of the commands mentioned in this chapter, refer to "Command Reference," and the Cisco IOS Release 12.0 Command Reference documents.

7.1 Overview of NLC Configuration

The plug-and-play mechanisms of the Cisco 6400 allow it to come up automatically. All configuration information for NLCs can be saved between hot swaps and switch reboots, while interface types are automatically discovered by the switch, eliminating mandatory manual configuration.

In the Cisco 6400, port IDs specify the actual physical location of each port on the system. The address is composed of a three-part number in the format slot/subslot/port. The first number identifies the slot in which the card is installed. Card slots are numbered 1 to 8 from left to right. The second number identifies the subslot number. The NLCs are numbered 0 and 1, with 0 being the top NLC facing the front of the system. The third number identifies the physical port number on the module. The port numbers always begin at 0 and are numbered from the top port to the bottom port, facing the back of the switch.

Interface ports maintain the same port ID regardless of whether other cards are installed or removed. However, when you move an NLC to a different slot, the first number in the address changes to reflect the new slot number.

7.2 Disabling Auto-Configuration

Auto-configuration determines the interface type each time an interface initially comes up.

You must disable the auto-configuration feature on an interface before you configure the NLC interface---for example, if you want to configure the interface to be a User-to-Network Interface (UNI).

To disable auto-configuration on an interface, use the following commands starting in global configuration mode:
Step Command Task

1 . 

interface atm slot/subslot/port [.vpt #]

Select the interface to be configured.

2 . 

no atm auto-configuration

Disable auto-configuration on the interface.

Example

The following example shows how to disable auto-configuration on interface ATM 1/0/0:

Switch(config)# interface atm 1/0/0
Switch(config-if)# no atm auto-configuration 
Switch(config-if)#
%ATM-6-ILMINOAUTOCFG: ILMI(ATM1/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart.
Switch(config-if)# ^z
Switch#

7.2.1 Displaying Auto-Configuration

To show the interface auto-configuration, use the following command in privileged EXEC mode:
Command Task

show atm interface atm slot/subslot/port

Show the ATM interface configuration.

Example

The following example shows how to display the auto-configuration status of OC-3 ATM interface 1/0/0 when it is disabled:

Switch# atm interface atm 1/0/0
 
Interface:      ATM1/0/0        Port-type:    oc3suni
IF Status:      UP              Admin Status: up
Auto-config:    disabled        AutoCfgState: not applicable
IF-Side:        Network         IF-type:      NNI
Uni-type:       not applicable  Uni-version:  not applicable
Max-VPI-bits:   8               Max-VCI-bits: 14
Max-VP:         255             Max-VC:       16383
Svc Upc Intent: pass            Signalling:   Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0040.0b0a.2b81.4000.0c80.8000.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   PVPLs SoftVPLs   SVPLs  Total-Cfgd  Installed-Conns
      3        0       0       0        0       0           3                3
Logical ports(VP-tunnels):     0
Input cells:    234663          Output cells: 235483
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 153211, Output AAL5 pkts: 153626, AAL5 crc errors: 0
 
Switch#

7.2.2 Default NLC Interface Values

When autoconfiguration is disabled, each NLC interface assumes a default configuration. Table 7-1 lists the default configuration values for each type of NLC.


Table 7-1:
Field OC-3 Default OC-12 Default DS3 Default

ATM interface type

UNI

UNI

UNI

UNI version

3.0

3.0

3.0

Maximum VPI bits

8

8

8

Maximum VCI bits

14

14

14

ATM interface side

network

network

network

ATM UNI type

private

private

private

Clock source

network-derived

network-derived

network-derived

Framing

sts-3c

sts-12c

cbit-adm

Cell payload scrambling

on

on

off

Synchronous Transfer Signal (STS) stream scrambling

on

on

---

Line buildout

---

---

short

Auto-ferf (all)

---

---

on

Default Configuration for Node Line Cards

7.3 Network Interface Types


Note Whenever a change in the interface protocol (such as UNI, NNI, or IISP), side, or version is configured, ATM signaling and ILMI are restarted on the interface. When ATM signaling is restarted, all switched virtual connections (SVCs) across the interface are cleared; permanent virtual connections are not affected.

7.3.1 UNI Interfaces

The UNI specification defines communications between ATM end stations (such as workstations and routers) and ATM switches in private ATM networks. The NSP interface to each NRP must also be configured as a UNI interface.

To configure a UNI interface between the Cisco 6400 and the DSLAM connected across an NLC port, use the atm uni command in interface configuration mode (see Figure 7-1).


Figure 7-1: UNI Interface Example



Note The UNI interface is the default for NLCs designed for the Cisco 6400. See the section
"Displaying Auto-Configuration" for a complete description of the default configuration.

To manually configure an interface as UNI, perform the following tasks, beginning in global configuration mode:
Step Command Task

1 . 

interface atm slot/subslot/port

Specify an ATM interface and enter interface configuration mode.

2 . 

atm uni [side {private | public} type {network | user} version {3.0 | 3.1 | 4.0}]

Configure the UNI side, type, or version.

3 . 

atm maxvpi-bits 0-8

Modify the maximum VPI bits configuration.

4 . 

atm maxvci-bits 0-14

Modify the maximum VCI bits configuration.

The following example shows how to disable auto-configuration and manually configure an NLC interface as the private side of a user UNI:

Switch(config)# interface atm 3/0/0
Switch(config-if)# no atm auto-configuration
Switch(config-if)# 
%ATM-6-ILMINOAUTOCFG: ILMI(ATM3/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart.
Switch(config-if)# atm uni side user type private version 4.0
Switch(config-if)# 
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/0/0.
Switch(config-if)# ^z
Switch# 

7.3.2 NNI Interfaces

This section describes the configuration of a Network-to-Network Interface (NNI) connection between two switches, such as the private NNI interface between two Central Office Cisco 6400 systems. Figure 7-2 is a detail of the sample network segment being configured.


Figure 7-2: Private NNI Interface Example


You must configure private NNI connections between the ATM switches to allow for route discovery and topology analysis between the switches.

To manually configure an interface as private NNI, perform the following tasks, beginning in global configuration mode:
Step Command Task

1 . 

interface atm slot/subslot/port

Specify an ATM interface and enter interface configuration mode.

2 . 

atm nni

Modify the ATM interface side, type, or version.

3 . 

atm maxvpi-bits 0-8

Modify the maximum VPI bits configuration.

4 . 

atm maxvci-bits 0-14

Modify the maximum VCI bits configuration.

Example

The following example shows how to disable auto-configuration and manually configure an NLC interface as NNI:

Switch(config)# interface atm 3/0/0
Switch(config-if)# no atm auto-configuration
Switch(config-if)# 
%ATM-6-ILMINOAUTOCFG: ILMI(ATM3/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart.
Switch(config-if)# atm nni
Switch(config-if)# 
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/0/0.
Switch(config-if)# ^z
Switch# 

7.3.3 IISP Interfaces

This section describes the procedure for configuring the Interim Interswitch Signaling Protocol (IISP) interface from the Cisco 6400 to the first switch in the ATM cloud. Figure 7-3 shows an example of this type of network configuration.


Figure 7-3: IISP Network Segment Example


Some ATM switches do not support the Private Network-to-Network Interface (PNNI) protocol. You can provide switched virtual circuit (SVC) support by configuring the interface to use IISP.

To manually change any of the default configuration values, perform the following tasks, beginning in global configuration mode:
Step Command Task

1 . 

configure [terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2 . 

interface atm slot/subslot/port

Specify an ATM interface and enter interface configuration mode.

3 . 

atm iisp [side {network | user}]
[version {3.0 | 3.1 | 4.0}]

Configure the ATM IISP interface.

4 . 

atm maxvpi-bits 0-8

Modify the maximum VPI bits configuration.

5 . 

atm maxvci-bits 0-14

Modify the maximum VCI bits configuration.

6 . 

exit

Exit interface configuration mode.

7 . 

atm route prefix atm-address-prefix atm slot/subslot/port[.sub_inter #]

Configure the ATM route address prefix.

Example

The following example shows how to disable auto-configuration and manually configure an NLC interface as the user side of an IISP:

Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface atm 3/0/0
Switch(config-if)# no atm auto-configuration
Switch(config-if)# 
%ATM-6-ILMINOAUTOCFG: ILMI(ATM3/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart.
Switch(config-if)# atm iisp side user
Switch(config-if)# 
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/0/0.
Switch(config-if)# exit
Switch(config)# atm route 47.0091.8100.0000.0000.0ca7.ce01 atm 3/0/0
Switch(config)# ^z
Switch# 

7.4 Interface Clocking Options

Each port on an NLC can be configured to support the following clocking options:

To configure an interface to receive its transmit clocking, use the following EXEC commands:
Step Command Task
1

configure [terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2

interface atm slot/subslot/port

Select the interface to be configured.

3

clock source {free-running | loop-timed | network-derived}

Configure the interface network clock source.

See "Configuring the Node Switch Processor," for detailed information about clocking on the Cisco 6400.

Example

The following example shows how to configure ATM interface 4/0/0 to receive its transmit clocking from a network-derived source:

Switch(config)# interface atm 4/0/0
Switch(config-if)# clock source network-derived
Switch(config-if)#

7.5 SONET Interface Options

There are two NLCs available that support Synchronous Optical Network (SONET) connections, the OC-3 NLC and the OC-12 NLC. The ports on both NLCs can be configured as redundant links using the switch routing protocols. The OC-12 NLC supports SC-type connectors, while the OC-3 NLC supports SC-type and unshielded twisted-pair (UTP) connectors. Both NLCs have receive and transmit LEDs on each port to give quick, visual indications of port status and operation. For detailed network management support, comprehensive statistics gathering and alarm monitoring capabilities are provided, building on the sophisticated manageability mechanisms of SONET/SDH.

To manually change any of the default configuration values, perform the following tasks, beginning in global configuration mode:
Step Command Task

1 . 

configure [terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2 . 

interface atm slot/subslot/port

Specify an ATM interface and enter interface configuration mode.

3 . 

sonet {stm-1 | sts-3c | stm-4 | sts-12c}

Configure the SONET framing mode.

4 . 

[no] scrambling {cell-payload | sts-stream}

Enable or disable the scrambling modes.

Example

The following example shows how to disable cell-payload scrambling and STS-stream scrambling for the OC-3 interface 1/0/0. It also shows how to change the SONET mode of operation to Synchronous Digital Hierarchy/Synchronous Transfer Module 1 (SDH/STM-1).

Switch(config)# interface atm 1/0/0
Switch(config-if)# no scrambling cell-payload
Switch(config-if)# no scrambling sts-stream
Switch(config-if)# sonet stm-1
Switch(config-if)# exit
Switch(config)# 
 

7.6 DS3 Interface Options

The DS3 NLC provides two 45-Mbps bidirectional ports for connection to network services using coaxial cable.You can install two DS3s in each carrier module, which can then be installed in slot 1 through slot 8 of a Cisco 6400 chassis.

To manually change any of the default configuration values, perform the following tasks, beginning in global configuration mode:
Step Command Task

1 . 

configure [terminal]

At the privileged EXEC prompt, enter configuration mode from the terminal.

2 . 

interface atm slot/subslot/port

Specify an ATM interface and enter interface configuration mode.

3 . 

framing {cbitadm | cbitplcp | m23adm | m23plcp}

Modify the framing mode.

4 . 

[no] scambling cell-payload

Enable or disable the scambling mode.

5 . 

lbo {long | short}

Modify the line build-out.

6 . 

[no] auto-ferf {ais | lcd | los | oof | red}

Modify the auto-FERF configuration.

Examples

The following example shows how to configure cbit-adm framing mode and short line buildout for the DS3 interface 3/0/0:

Switch(config)# interface atm 3/0/0
Switch(config-if)# framing cbitadm
Switch(config-if)# lbo short
Switch(config-if)# exit

7.7 Troubleshooting the Interface Configuration

Table 7-2 describes commands that you can use to confirm that the hardware, software, and interfaces for the Cisco 6400 are configured as intended:


Table 7-2:
Command Description

show version

Confirm the correct version and type of software is installed.

show hardware

Confirm the type of hardware installed in the system.

show atm addresses

Confirm the ATM address is configured correctly.

ping atm

Test for connectivity between the switch and a host.

show atm interface

Confirm the ATM interfaces are configured correctly.

show atm status

Confirm the status of the ATM interfaces.

show atm vc

Confirm the status of ATM virtual interfaces.

show system:running-config

Confirm the configuration being used is configured correctly.

show nvram:startup-config

Confirm the configuration saved in NVRAM is configured correctly.

show controller atm

Confirm interface controller memory addressing.

Configuration Testing Commands
Examples

In the following example, the OC-3 physical interface configuration is displayed through use of the show controller command:

Switch# show controller atm 7/0/0
Redundancy NOT Enabled on interface
IF Name: ATM7/0/0    Chip Base Address(es): A8B08000, 0 Port type: OC3    Port rate: 155 Mbps    Port medium: SM Fiber
Port status:Good Signal    Loopback:None    Flags:8308
TX Led: Traffic Pattern    RX Led: Traffic Pattern  TX clock source:  network-derived
Framing mode:  sts-3c
Cell payload scrambling on
Sts-stream scrambling on
 
OC3 counters (based on active port):
 
  Key: txcell - # cells transmitted
       rxcell - # cells received
       b1     - # section BIP-8 errors
       b2     - # line BIP-8 errors
       b3     - # path BIP-8 errors
       ocd    - # out-of-cell delineation errors - not implemented
       g1     - # path FEBE errors
       z2     - # line FEBE errors
       chcs   - # correctable HEC errors
       uhcs   - # uncorrectable HEC errors
 
txcell:290, rxcell:286
b1:0, b2:0, b3:0, ocd:0
g1:0, z2:0, chcs:0, uhcs:0
 
OC3 errored secs:
b1:0, b2:0, b3:0, ocd:0
g1:0, z2:0, chcs:0, uhcs:0
 
OC3 error-free secs:
b1:565, b2:565, b3:565, ocd:0
g1:565, z2:565, chcs:565, uhcs:565
 
Clock reg:AF
 
  mr 0x61, mcfgr 0x71, misr 0x00, 
  mcmr 0x07, mctlr 0x00, cscsr 0x50, 
  crcsr 0x20, rsop_cier 0x00, rsop_sisr 0x00, 
  tsop_ctlr 0x80, tsop_diagr 0x80, rlop_csr 0x00, 
  rlop_ieisr 0x00, rlop_febe0r 0x00, rlop_febe1r 0x00, 
  rlop_febe2r 0x00, tlop_ctlr 0x00, tlop_diagr 0x00, 
  tx_k1 0x00, tx_k2 0x00, rpop_scr 0x00, 
  rpop_isr 0x00, rpop_ier 0x00, rpop_pslr 0x13, 
  rpop_pfebe0r 0x00, rpop_pfebe1r 0x00, tpop_cdr 0x00, 
tpop_pcr 0x00, tpop_ap0r 0x00, tpop_ap1r 0x90, 
  tpop_pslr 0x13, tpop_psr 0x00, racp_csr 0x04, 
  racp_iesr 0x01, racp_mhpr 0x00, racp_mhmr 0x00, 
  racp_checr 0x00, racp_uhecr 0x00, racp_rcc0r 0x00, 
  racp_rcc1r 0x00, racp_rcc2r 0x00, racp_cfgr 0xFC, 
  tacp_csr 0x04, tacp_iuchpr 0x00, tacp_iucpopr 0x6A, 
  tacp_fctlr 0x00, tacp_tcc0r 0x00, tacp_tcc1r 0x00, 
  tacp_tcc2r 0x00, tacp_cfgr 0x08, rase_ie 0x00, 
  rase_is 0x00, rase_cc 0x00, rase_sfap1 0x00, 
  rase_sfap2 0x00, rase_sfap3 0x00, rase_sfst1 0x00, 
  rase_sfst2 0x00, rase_sfdt1 0x00, rase_sfdt2 0x00, 
  rase_sfct1 0x00, rase_sfct2 0x00, rase_rK1 0x00, 
  rase_rK2 0x00, rase_rS1 0x00, 
  phy_tx_cnt:293, phy_rx_cnt:286
IDB apshsb:
 flags: 0x80000007, line_state: 0x0, failure_channel: 0x1
 k1: 0x0, k2 0x0, ber: 0x0, alarm_state: 0x0
CHANNEL7/0/0 apssb:
 flags: 40000000, channel_stat: 1
SLOS
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
SLOF
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
LAIS
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
LRDI
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
PAIS
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
PRDI
count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
PLOP
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
BER_SF
 count: 0, asserted: 0x0, report: 0x1
 reported: 0x0, default_report: 0x1
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
BER_SD
 count: 0, asserted: 0x0, report: 0x0
 reported: 0x0, default_report: 0x0
 clr itvl: 0, set itvl: 0, cur BER: 0, thresh: 0
 tts: 0, ttc: 0, dc: 0 lc: 0, lv: 0, leps: 0
 
 
 Switch#
 


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Nov 15 12:42:58 PST 1999
Copyright 1989-1999©Cisco Systems Inc.