Initially Configuring the Cisco DSLAM

              Restricted Rights Legend
 
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
 
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
 
 
 
Cisco Internetwork Operating System Software
IOS (tm) PNNI Software (LS-WP-M), Version XX.X(X.X.WAX.X.XX)
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Tue 11Jan-98 02:59 by
Image text-base: 0x600108D0, data-base: 0x603EE000
 
8192K bytes of Flash internal SIMM (Sector size 256K).
 
Press RETURN to get started!
 

cisco ASP1 (R4600) processor with 16384K bytes of memory.
 
Cisco Internetwork Operating System Software
IOS (tm) PNNI Software (LS-WP-M), Version XX.X(X.X.WAX.X.XX)
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Tue 11-Jan-98 02:59 by
Image text-base: 0x600108D0, data-base: 0x603EE000
 
8192K bytes of Flash internal SIMM (Sector size 256K).
 
 
Press RETURN to get started!
 

The DSLAM should now be operating correctly and transferring data.

The default addressing scheme includes:

• Authority and format identifier (AFI)—1 byte

• Cisco specific International Code Designator (ICD)—2 bytes

• Cisco specific information—4 bytes

• Cisco switch ID—6 bytes (used to distinguish multiple switches). The first 13 bytes of the address is a switch prefix used by ILMI in assigning addresses to end stations connected to User-Network Interface (UNI) ports.

• MAC address of the switch—6 bytes (used to distinguish multiple end system identifier [ESI] addresses). Both the DSLAM ID and ESI MAC address fields in the ATM address are the same, but they may not be the same as the address printed on the chassis label. Use the ATM address fields when you configure the ATM addressing scheme.

• Selector (SEL) equals 0—1 byte

If you use the default address format, these features and implications apply:

• The default address format enables you to manually configure other switches to be used in a single-level PNNI routing domain consisting primarily of autoconfigured Cisco ATM switches. You must use a globally unique MAC address to generate the ATM address.

• You can assign the same MAC address for bytes 8 through 13 and bytes 14 through 19.

• To achieve scalable ATM routing, you need two addresses when you connect to a large ATM network with multiple levels of PNNI hierarchy.

• Do not use summary addresses with fewer than 13 bytes with autoconfigured ATM addresses. Other switches with autoconfigured ATM addresses that match the DSLAM summary can exist outside of the default peer group.

Caution ATM addressing can lead to conflicts if you do not configure it correctly. For example, if you configure a new ATM address, you must remove the old one from the configuration.

When the switch initially powers on without previous configuration data, the ATM interfaces configure automatically on the physical ports. The DSLAM uses ILMI and the physical card type to automatically derive:

• ATM interface type

• UNI version

• Maximum virtual path identifier (VPI) and virtual channel identifier (VCI) bits

• ATM interface side

• ATM UNI type

The default IP address is none.

Enter your Internet address in dotted decimal format for each interface you plan to configure.

You define subnet mask bits as a decimal number between

• 0 and 22 for Class A addresses

• 0 and 14 for Class B addresses

• 0 and 6 for Class C addresses

Note   Do not specify 1 as the number of bits for the subnet field. That specification is reserved by Internet conventions.

To configure the IP address, perform these tasks, beginning in global configuration mode:

Step	Command	Task
1.	interface ethernet slot/port	Select the interface to be configured.
2.	ip address A.B.C.D sub_net_A.B.C.D	Configure the IP and subnetwork address.

Example

This example shows how to configure the Ethernet CPU interface 0/0 with IP address 172.20.40.93 and subnetwork mask 255.255.255.0, and displays the interface information:

DSLAM# config term
Enter configuration commands, one per line.  End with CNTL/Z.
DSLAM(config)# 
DSLAM(config)# interface ethernet ?
  <0-13>  Ethernet interface number
/
 
DSLAM(config)# interface ethernet 0/0 ?
  <cr>
 
DSLAM(config)# interface ethernet 0/0
DSLAM(config-if)# ip address ?
  A.B.C.D  IP address
 
DSLAM(config-if)# ip address 172.20.40.93 ?
A.B.C.D IP subnet mask
 
DSLAM(config-if)# ip address 172.20.40.93 255.255.255.0
DSLAM(config-if)#
 
DSLAM# show interface ethernet 0/0
Ethernet 0/0 is up, line protocol is up
  Hardware is SonicT, address is 0040.0b0a.1080 (bia 0040.0b0a.1080)
  Internet address is 172.20.40.93/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:07, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     58426 packets input, 18346098 bytes, 0 no buffer
     Received 58373 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 input packets with dribble condition detected
     9350 packets output, 915319 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
 

Command	Task
ping ip ip_address	Test the configuration using the ping command. The ping command sends an echo request to the host specified in the command line.

For example, to test Ethernet connectivity from the DSLAM to a workstation with an IP address of 172.20.40.201, enter the command ping ip 172.20.40.201. If the DSLAM receives a response, this message appears:

DSLAM# ping ip 172.20.40.201
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.20.40.201, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms

Because the port providing the network clock source could fail, Cisco IOS software provides the ability to configure additional interfaces as clock sources with priorities 1 to 4.

These sections describe network clocking:

Command	Task
network-clock-select priority {BITS | system |atmslot/port}	Configure the priority of a timing source. Priority values are 1 to 4. The trunk, ATM 0/1, is the only ATM interface that can serve as a timing source.
network-clock-select BITS {T1 | E1} margin}	Configure the type and margin, in decibels, of the BITS line. Margin values vary according to the length of the T1/E1 line.
network-clock-select revertive	Configure the system to revert to a higher priority timing source when it becomes available.

Examples

This example sets up the DSLAM's building-integrated time source (BITS) interface as the highest-priority clock source, then configures the BITS interface for T1 at 0.6db (0 to 133 feet, or 0 to 40.5 meters).

DSLAM# config term
Enter configuration commands, one per line.  End with CNTL/Z.
DSLAM(config)# network-clock-select 1 BITS
DSLAM(config)# network-clock-select BITS T1 0.6db
 

This example configures interface 0/1, the trunk, as the second-highest priority timing source.

DSLAM# config term
Enter configuration commands, one per line.  End with CNTL/Z.
DSLAM(config)# network-clock-select 2 atm 0/1
 

This example configures the DSLAM's own system clock as the third-highest priority timing source.

DSLAM# config term
Enter configuration commands, one per line.  End with CNTL/Z.
DSLAM(config)# network-clock-select 3 system
 

This example shows how to configure the network clock to revert back to the highest priority clock source after a failure:

DSLAM(config)# network-clock-select revertive
DSLAM(config)#

DSLAM(config)# atm route 47.0091.8100.567.0000.0ca7.ce01 atm 0/1
DSLAM(config)# 

Step	Command	Task
1.	clock set hh:mm:ss day month year	Set the internal clock.
2.	configure [terminal]	Enter global configuration mode from the terminal.
3.	hostname name	Set the system name.

Examples

This example shows how to configure the time, date, and month using the clock set command:

DSLAM# clock set 15:01:00 17 October 1997
 

This example shows how to configure the host name using the hostname command:

DSLAM# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
DSLAM(config)# hostname Publications
Publications#
 

This example shows how to confirm the clock setting using the show clock command:

Publications# show clock
.15:03:12.015 UTC Fri Oct 17 1997
Publications#

• SNMP manager

• SNMP agent

• Management Information Bases (MIBs)

The SNMP manager can be part of a network management system (NMS), such as CiscoWorks.

The agent and MIB reside on the DSLAM. To configure SNMP on the DSLAM, you define the relationship between the manager and the agent.

An agent can send unsolicited traps to the manager. Traps are messages that alert the SNMP manager to a condition on the network. Traps can indicate improper user authentication, restarts, link status (up or down), closing of a TCP connection, or loss of connection to a neighbor router or DSLAM.

Cisco provides its own MIB with every system. One of the set of MIB objects provided is the Cisco Entity Asset MIB that enables the SNMP manager to gather data on system card descriptions, serial numbers, hardware and software revision levels, and slot locations.

Although SNMPv2 offers more robust support than SNMPv1, Cisco continues to support SNMPv1. Not all management stations have migrated to SNMPv2, and you must configure the relationship between the agent and the manager to use the version of SNMP supported by the management station.

SNMPv1 offers a community-based form of security defined through an IP address access control list and password. SNMPv2 offers richer security configured through an access policy that defines the relationship between a single manager and agent. SNMPv2 security includes message authentication support using the Message Digest 5 (MD5) algorithm, but because of the Data Encryption Standard (DES) export restrictions, it does not include encryption support through DES. SNMPv2 security provides data origin authentication, ensures data integrity, and protects against message stream modification.

In addition to enhanced security, SNMPv2 support includes a bulk retrieval mechanism and more detailed error message reporting to management stations. The bulk retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trips required.

The SNMPv2 improved error handling support includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes now report the error type. Three kinds of exceptions are also reported:

• No such object exceptions

• No such instance exceptions

• End of MIB view exceptions

There is no specific command to enable SNMP. The first snmp-server command that you enter enables both versions of SNMP.

To configure SNMP support, perform the tasks in the appropriate sections:

• Configuring for both SNMPv1 and SNMPv2

• Configuring SNMPv2 Support

• Configuring SNMPv1 Support

To configure the relationship between the agent and the manager on the DSLAM, you need to know the version of the SNMP protocol that the management station supports. An agent can communicate with multiple managers, so you can configure the Cisco IOS software to support communications with one management station using the SNMPv1 protocol and another using the SNMPv2 protocol.

Command	Task
no snmp-server	Disable SNMP agent operation.

Step 2   Define a context to identify the object resources that can be acted on.

Step 3   Define a party for both the manager and the agent to identify them.

Step 4   Using the definitions created in the previous tasks, configure the access policy that characterizes the communications that can occur between the manager and the agent. The privileges that you define for the access policy depend on whether the agent is defined as the source or the destination. For example:

• When the agent party is defined as the destination in an access policy, the access policy privileges define the management operations that the agent will accept from the manager and perform in relation to the object resources.

• When the agent party is defined as the source in an access policy, the access policy privileges define the responses and traps that the agent can send to the manager.

• The top arrow, leading from the manager to the agent, shows the types of requests the manager can send to the agent.

• The bottom arrow, leading from the agent to the manager, shows the kind of information that the agent can send to the manager.

The agent sends trap messages to the manager in response to certain network conditions. Trap messages are unsolicited and are not related to the request/response communication exchange between the manager and the agent that occurs in relation to MIB variables. For any given manager and agent relationship, the privileges defined in the access policy constrain communications to a specific set of operations.

You must create access policies for

• Each new agent you install

• On an agent when you install new management stations

Each time a network address changes on a management station, you must reconfigure the access policy to reflect the new information for the management station.

Command	Task
snmp-server view view-name oid-tree {included | excluded}	Create or modify a view record.

To remove a view record, use the no snmp-server view command.

Command	Task
snmp-server context context-name context-oid view-name	Create or modify a context record.

To remove a context entry, use the no snmp-server context command. Specify only the name of the context. The name identifies the context to be deleted.

Command	Task
snmp-server party party-name party-oid [protocol-address] [packetsize size] [local | remote] [authentication md5 key [clock clock] [lifetimelifetime]	Create or modify a party record.

To remove a party record, use the no snmp-server party command.

Command	Task
snmp-server access-policy destination-party source-party context privileges	Create or modify an access policy.

Command	Task
snmp-server trap-source interface	Specify the source interface (and hence IP address) of the trap message.
snmp-server access-policy destination-party source-party context privileges	Specify the access policy that defines the traps that the agent can send to the manager.
snmp-server trap-authentication [snmpv1 | snmpv2]	Establish trap message authentication.
snmp-server trap-timeout seconds	Define how often to resend trap messages on the retransmission queue.
snmp-server queue-length length	Establish the message queue length for each trap host.

Because SNMP traps are inherently unreliable but too important to lose, the DSLAM stores at least one syslog message (the most recent trap), in a history table. You can specify the level of syslog traps (Cisco Syslog MIB) stored in the history table and sent to the SNMP network management station.

Using the snmp-server community command, specify a string and, optionally, a MIB view and an access list. The string is used as a password. The MIB view defines the subset of all MIB objects that the given community can access. The access list identifies the IP addresses of systems on which SNMPv1 managers reside that might use the community string to gain access to the SNMPv1 agent.

To configure support for SNMPv1, perform the tasks in these sections:

To configure a community string, use this command in global configuration mode:

Command	Task
snmp-server community string [view view-name] [ro|rw] [access-list number]	Define the community access string.

You can configure one or more community strings. To remove a specific community string, use the no snmp-server community command.

Step	Command	Task
1.	snmp-server trap-source interface	Specify the source interface (and IP address) of the trap message.
2.	snmp-server host address community-string [trap-type]	Specify the recipient of the trap message.
3.	snmp-server trap-authentication [snmpv1 | snmp2]	Establish trap message authentication.
4.	snmp-server trap-timeout seconds	Define how often to resend trap messages on the retransmission queue.
5.	snmp-server queue-length length	Establish the message queue length for each trap host.

Because SNMP traps are inherently unreliable but too important to lose, at least one syslog message, the DSLAM stores the most recent trap in a history table. You can specify the level of syslog traps (Cisco Syslog MIB) stored in the history table and sent to the SNMP network management station.

• Provides visibility of individual nodal activity

• Allows you to monitor all nodes and their interaction on a LAN segment

RMON, used in conjunction with the SNMP agent in the DSLAM, allows you to

• View traffic that flows through the DSLAM

• View segment traffic not necessarily destined for the DSLAM

Combining RMON alarms and events with existing MIBs allows you to choose where monitoring occurs.

RMON can be very data- and processor-intensive. Measure usage effects to ensure that DSLAM performance is not degraded and to minimize excessive management traffic overhead. Native mode is less intensive than promiscuous mode.

Cisco IOS software images are available in versions with or without the explicit RMON option. Images without the explicit RMON option include limited RMON support (RMON alarms and event groups only). Images with the RMON option include support for all nine groups (statistics, history, alarms, hosts, hostTopN, matrix, filter, capture, and event). As a security precaution, support for the packet capture group allows capture of packet header information only; data payloads are not captured.

Note   This section describes general SNMP RMON configuration. See "Configuring ATM Accounting and ATM RMON," for ATM RMON configuration.

To set an RMON alarm or event, use one of these commands in global configuration mode:

Command	Task
rmon alarm number variable interval {delta | absolute} rising-threshold value [event-number] falling-thresholdvalue [event-number] [owner string]	Set an alarm on a MIB object.
rmon event number [log] [trap community] [descriptionstring] [owner string]	Add or remove an event in the RMON event table.

You can set an alarm on any MIB object in the access server. To disable an alarm, you must enable the no form of this command on each alarm you configure. You cannot disable all the alarms you configure at one time.

Refer to RFC 1757 to learn more about alarms and events and how they interact with each other.

Command	Task
show rmon or show rmon task	Display general RMON statistics.
show rmon alarms	Display the RMON alarm table.
show rmon events	Display the RMON event table.

Examples

This example shows how to enable the rmon event command:

DSLAM# rmon event 1 log trap eventtrap description "High ifOutErrors" owner sdurham 

This example shows how to configure this RMON event:

• RMON event number 1

• Defined as High ifOutErrors

• Generates a log entry when the event is triggered by an alarm

• User sdurham owns the row that is created in the event table by this command

• Generates a SNMP trap when the event is triggered

This example shows how to configure an RMON alarm using the rmon alarm command:

DSLAM# rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1 falling-threshold 0 owner jjjohnson
 

This example shows how to configure this RMON alarm:

• RMON alarm number 10.

• The alarm monitors the MIB variable ifEntry.20.1 one time every 20 seconds until the alarm is disabled and checks the change in the rise or fall of the variable.

• If the ifEntry.20.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered.

• The alarm in turn triggers event number 1, which is configured using the rmon event command.

Possible events include a log entry or an SNMP trap. If the ifEntry.20.1 value changes by 0, the alarm is reset and can be triggered again.

DSLAM# copy running-config startup-config
Building configuration...
[OK]

DSLAM# show hardware
 
Chassis Type: Unknown Chassis Type
 
Slot 1 : EMPTY                                   Slot 17: EMPTY
Slot 2 : EMPTY                                   Slot 18: EMPTY
Slot 3 : EMPTY                                   Slot 19: EMPTY
Slot 4 : EMPTY                                   Slot 20: EMPTY
Slot 5 : EMPTY                                   Slot 21: EMPTY
Slot 6 : EMPTY                                   Slot 22: EMPTY
Slot 7 : EMPTY                                   Slot 23: EMPTY
Slot 8 : EMPTY                                   Slot 24: EMPTY
Slot 9 : EMPTY                                   Slot 25: EMPTY
Slot 10: EMPTY                                   Slot 26: EMPTY
Slot 11: NI-2-155SM-155SM                        Slot 27: EMPTY
Slot 12: EMPTY                                   Slot 28: EMPTY
Slot 13: EMPTY                                   Slot 29: EMPTY
Slot 14: EMPTY                                   Slot 30: EMPTY
Slot 15: EMPTY                                   Slot 31: EMPTY
Slot 16: EMPTY                                   Slot 32: EMPTY
 
Fan Module 1: Not Present   2: Not Present
 
Power Supply Module 1:  Not Present   2:  Not Present

DSLAM# show interface ethernet 0/0
Ethernet0/0 is up, line protocol is up
  Hardware is SonicT, address is 0000.0000.0000 (bia 0000.0000.0000)
  Internet address is 172.20.52.20/26
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set, keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 1000 bits/sec, 2 packets/sec
  5 minute output rate 0 bits/sec, 1 packets/sec
     69435 packets input, 4256035 bytes, 0 no buffer
     Received 43798 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 input packets with dribble condition detected
     203273 packets output, 24079764 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

DSLAM# show atm addresses
 
DSLAM Address(es):
  47.009181000000007BF4447801.007BF4447801.00 active
 
Soft VC Address(es):
  47.0091.8100.0000.007b.f444.7801.4000.0c80.0010.00 ATM0/1
  47.0091.8100.0000.007b.f444.7801.4000.0c80.0020.00 ATM0/2
 
ILMI Switch Prefix(es):
  47.0091.8100.0000.007b.f444.7801
 
ILMI Configured Interface Prefix(es):
 
LECS Address(es):
 

Command	Task
ping ip ip_address	Test the configuration using the ping command. The ping command sends an echo request to the host specified in the command line.

For example, to test Ethernet connectivity from the DSLAM to a workstation with an IP address of 172.20.40.201, enter the command ping ip 172.20.40.201. If the DSLAM receives a response, this message appears:

DSLAM# ping ip 172.20.40.201
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.20.40.201, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1000 ms

DSLAM# ping atm interface atm 0/1 5 seg-loopback
 
Type escape sequence to abort.
Sending Seg-Loopback 5, 53-byte OAM Echoes to a neighbour,timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
DSLAM#

DSLAM# show atm interface
 
Interface:      ATM0/0          Port-type:      cpu
IF Status:      UP              Admin Status:   up
Automation :-config:    disabled        AutoCfgState:   not applicable
IF-Side:        not applicable  IF-type:        not applicable
Uni-type:       not applicable  Uni-version:    not applicable
Max-VPI-bits:   8               Max-VCI-bits:   14
Max-VP:         0               Max-VC:         16383
ConfMaxSvpcVpi: 0               CurrMaxSvpcVpi: 0
ConfMaxSvccVpi: 0               CurrMaxSvccVpi: 0
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      3        0       0       0       0        0       0          3          1
Logical ports(VP-tunnels):     0
Input cells:    0               Output cells:   0
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
 
 
Interface:      ATM0/1          Port-type:      suni_dual
IF Status:      UP              Admin Status:   up
Automation :-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
ConfMaxSvpcVpi: 255             CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255             CurrMaxSvccVpi: 255
ConfMinSvccVci: 35              CurrMinSvccVci: 35
Svc Upc Intent: pass            Signalling:     Enabled
ATM Address for Soft VC: 47.0091.8100.0000.007b.f444.7801.4000.0c80.0010.00
Configured virtual links:
  PVCLs SoftVCLs   SVCLs   TVCLs   PVPLs SoftVPLs   SVPLs Total-Cfgd Inst-Conns
      1        0       0       0       0        0       0          1          1
Logical ports(VP-tunnels):     0
Input cells:    1112            Output cells:   0
5 minute input rate:             0 bits/sec,       0 cells/sec
5 minute output rate:            0 bits/sec,       0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
 
         [additional interfaces deleted]

DSLAM# show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint, MP2P=Multipoint to Point)
 
Type     PVCs SoftPVCs     SVCs     TVCs     PVPs SoftPVPs     SVPs      Total
P2P         1        0        0        0        0        0        0          1
P2MP        0        0        0        0        0        0        0          0
MP2P        0        0        0        0        0        0        0          0
                                      TOTAL INSTALLED CONNECTIONS =          1
 
PER-INTERFACE STATUS SUMMARY AT 10:27:54 EDT Thu Jun 10 1999:
   Interface      IF         Admin  Automation :-Cfg    ILMI Addr     SSCOP    Hello
     Name       Status      Status    Status    Reg State     State    State
------------- -------- ------------ -------- ------------ --------- --------
ATM0/0              UP           up      n/a  UpAndNormal      Idle      n/a
ATM0/1              UP           up      n/a          n/a      Idle down    
ATM0/2            DOWN         down  waiting          n/a      Idle      n/a

DSLAM# show atm vc
Interface    VPI   VCI   Type    X-Interface  X-VPI X-VCI  Encap Status
ATM0/0       0     36     PVC     ATM0/2       0     16    ILMI   DOWN
ATM0/0       0     38     PVC     ATM0/2       0     5     QSAAL  DOWN
ATM0/0       0     500    PVC     ATM0/1       0     500   SNAP   UP
ATM0/1       0     500    PVC     ATM0/0       0     500   SNAP   UP
ATM0/2       0     5      PVC     ATM0/0       0     38    QSAAL  DOWN
ATM0/2       0     16     PVC     ATM0/0       0     36    ILMI   DOWN
 

DSLAM# show running-config
Building configuration...
 
Current configuration:
!
! No configuration change since last restart
!
version XX.X
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service internal
!
hostname ni2-3
!
enable password lab
!
!
dmt-profile default
network-clock-select 1 ATM0/1
network-clock-select 2 system
ip subnet-zero
ip host-routing
ip domain-name cisco.com
ip name-server 171.69.204.11
!
atm address 47.0091.8100.0000.007b.f444.7801.007b.f444.7801.00
atm router pnni
 no aesa embedded-number left-justified
 node 1 level 56 lowest
  redistribute atm-static
!
clock timezone EST -5
clock summer-time EDT recurring
!
process-max-time 200
!
interface ATM0/0
 ip address 70.0.0.2 255.0.0.0
 no ip directed-broadcast
 map-group test
 atm cac service-category abr deny
 atm maxvp-number 0
!
interface Ethernet0/0
 ip address 172.27.32.157 255.255.255.0
 no ip directed-broadcast
 no ip proxy-arp
 no keepalive
!
interface ATM0/1
 no ip address
 no ip directed-broadcast
 no atm auto-configuration
 no atm ilmi-keepalive
 no atm address-registration
 no atm ilmi-enable
 atm cac service-category abr deny
 atm manual-well-known-vc
 atm nni
 atm pvc 0 500  interface  ATM0/0 0 500  encap aal5snap
 atm oam 0 500 seg-loopback 
!
interface ATM0/2
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm cac service-category abr deny
!
ip default-gateway 172.27.144.4
ip classless
!
!
map-list test
 ip 70.0.0.1 atm-vc 500
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password lab
 login
!
sntp server 171.69.204.139
end

DSLAM# show startup-config
Using 1657 out of 522232 bytes
!
! Last configuration change at 11:35:31 EDT Thu Jun 3 1999
! NVRAM config last updated at 11:40:08 EDT Thu Jun 3 1999
!
version XX.X
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service internal
!
hostname ni2-3
!
enable password lab
!
!
dmt-profile default
network-clock-select 1 ATM0/1
network-clock-select 2 system
ip subnet-zero
ip host-routing
ip domain-name cisco.com
ip name-server 171.69.204.11
!
atm address 47.0091.8100.0000.007b.f444.7801.007b.f444.7801.00
atm router pnni
 no aesa embedded-number left-justified
 node 1 level 56 lowest
  redistribute atm-static
!
clock timezone EST -5
clock summer-time EDT recurring
!
process-max-time 200
!
interface ATM0/0
 ip address 70.0.0.2 255.0.0.0
 no ip directed-broadcast
 map-group test
 atm cac service-category abr deny
 atm maxvp-number 0
!
interface Ethernet0/0
 ip address 172.27.32.157 255.255.255.0
 no ip directed-broadcast
 no ip proxy-arp
 no keepalive
!
interface ATM0/1
 no ip address
 no ip directed-broadcast
 no atm auto-configuration
 no atm ilmi-keepalive
 no atm address-registration
 no atm ilmi-enable
 atm cac service-category abr deny
 atm manual-well-known-vc
 atm nni
 atm pvc 0 500  interface  ATM0/0 0 500  encap aal5snap
 atm oam 0 500 seg-loopback 
!
interface ATM0/2
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm cac service-category abr deny
!
ip default-gateway 172.27.144.4
ip classless
!
!
map-list test
 ip 70.0.0.1 atm-vc 500
!
line con 0
 exec-timeout 0 0
 transport input none
line aux 0
line vty 0 4
 exec-timeout 0 0
 password lab
 login
!
sntp server 171.69.204.139
end