cc/td/doc/product/dsl_prod/ios_dsl/rel121
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Initially Configuring the Cisco DSLAM

Methods for Configuring the DSLAM

Port and Slot Configuration

Configuration Prerequisites

Verifying Installed DSLAM Software and Hardware

Configuring the BOOTP Server

Setting the Subtend Node Identifier

Configuring the ATM Address

Configuring ATM Addressing

Using the ATM Default Addressing Scheme

Manually Setting the ATM Address

Modifying the Physical Layer Configuration of the Default ATM Interface

Configuring IP Interface Parameters

Defining an IP address

Defining Subnet Mask Bits

Displaying an IP Address

Testing the Ethernet Connection

Configuring Network Clocking

Configuring Network Clock Priorities and Sources

Configuring the Transmit Clocking Source

Providing Clock Synchronization Services

Configuring the Network Routing

Configuring the Time, Date, and Month

Configuring SNMP Management

Configuring Support for Both SNMPv1 and SNMPv2

Configuring SNMPv2 Support

Configuring Support for SNMPv2

Creating or Modifying an SNMP View Record

Creating or Modifying an SNMP Context Record

Creating or Modifying an SNMPv2 User Record

Creating an SNMPv2 Access Policy

Defining SNMPv2 Trap Operations

Configuring SNMPv1 Support

Creating or Modifying Access Control for an SNMPv1 Community

Defining SNMP Trap Operations for SNMPv1

Configuring SNMP RMON Support

Storing the Configuration

Testing the Configuration

Confirming the Hardware Configuration

Confirming the Software Version

Confirming the Ethernet Configuration

Confirming the ATM Address

Testing the Ethernet Connection

Confirming the ATM Connections

Confirming the ATM Interface Configuration

Confirming the Interface Status

Confirming Virtual Channel Connections

Confirming the Running Configuration

Confirming the Saved Configuration


Initially Configuring the Cisco DSLAM

This chapter describes how to initially configure the Cisco DSLAMs, and includes these sections:

• Methods for Configuring the DSLAM

• Port and Slot Configuration

• Configuration Prerequisites

• Verifying Installed DSLAM Software and Hardware

• Configuring the BOOTP Server

• Setting the Subtend Node Identifier

• Configuring the ATM Address

• Configuring ATM Addressing

• Modifying the Physical Layer Configuration of the Default ATM Interface

• Configuring IP Interface Parameters

• Testing the Ethernet Connection

• Configuring Network Clocking

• Configuring the Network Routing

• Configuring the Time, Date, and Month

• Configuring Support for SNMPv2

• Configuring Support for SNMPv2

• Configuring SNMPv1 Support

• Configuring SNMP RMON Support

• Storing the Configuration

• Testing the Configuration

Methods for Configuring the DSLAM

The DSLAM default configuration is suitable for operation with most networks. By using network management applications and the text-based command-line interface (CLI), you can configure and customize all aspects of DSLAM operation to suit your needs.

The DSLAM ships with the ATM address autoconfigured, allowing the DSLAM to:

•Automatically configure attached end systems using the Interim Local Management Interface (ILMI) protocol

•Establish itself as a node in a single-level Private Network-Network Interface (PNNI) routing domain.

The ILMI and PNNI protocols allow the DSLAM to be entirely self-configured when you use these protocols with an IP address autoconfiguration mechanism such as BOOTP.

You must assign an IP address to allow up to eight simultaneous Telnet sessions to connect to the DSLAM or to use the Simple Network Management Protocol (SNMP) system for the DSLAM. The Ethernet IP address is assigned either manually or by a BOOTP server. See the "Configuring IP Interface Parameters" section.

You can use either of two methods for configuring a DSLAM ( Figure 3-1):

•From a local console or workstation—Connect to the console port or connect to the Ethernet port of a DSLAM. This connection allows you to issue CLI commands directly to the DSLAM chassis.

•From a remote console or workstation—Initiate a Telnet connection to a target DSLAM. Telnet allows you to remotely issue CLI commands to that chassis.

Figure 3-1 Two Methods of Configuring a DSLAM

Port and Slot Configuration

The DSLAM contains an NI-2 card and up to 34 line (modem) cards depending on the DSLAM. The slot configurations on the different DSLAMs are as follows:

•Cisco 6015

–six line card slots

–one NI-2 card slot

•Cisco 6100

–32 line card slots

–two NI-2 card slots (only one slot active)

•Cisco 6130

–32 line card slots

–two NI-2 card slots (to provide redundancy)

•Cisco 6160

–32 line card slots

–two NI-2 card slots (to provide redundancy)

•Cisco 6260

–30 line card slots

–two NI-2 card slots (to provide redundancy)

In all the chassis, the NI-2 card handles the network interfaces. The NI-2 card has either OC3 or DS3 interfaces.

Line cards are assigned ports 1 to 4 or 1 to 8 in consecutive slots. Table 3-1 lists NI-2 port assignments. Figure 3-2 shows the port connection arrangement.

Table 3-1 NI-2 Port Assignments

Port Type
OC3 Configuration
Assigned slot/port
DS3 Configuration
Assigned slot/port
Function

Switch, Ethernet

0/0

0/0

The ATM switch or Ethernet CPI port (internal).

Trunk

0/1

0/1

The trunk port connects to the network, either directly or through a subtended port in another DSLAM.

Subtend 1

0/2

0/2

A subtended port connects a second DSLAM to the network through a primary DSLAM. See Figure 3-3.

Subtend 2

N/A

0/3

The DS3 configuration has a second subtended port.


Figure 3-2 DSLAM Port Connections

Configuration Prerequisites

Obtain this information before you configure your DSLAM:

•To configure a BOOTP server to inform the DSLAM of its Ethernet IP address and mask, you need the Media Access Control (MAC) address of the Ethernet port.

•To configure a new ATM address for the DSLAM (an autoconfigured ATM address is assigned by Cisco), you need an ATM address assigned by your system administrator.

•If you are not using BOOTP, obtain an IP address and a subnet mask.

Verifying Installed DSLAM Software and Hardware

When you first power on your console and DSLAM, a screen similar to this appears:


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

The script then displays the banner information, including the software version, followed by the installed hardware configuration.

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.

Configuring the BOOTP Server

The BOOTP protocol automatically assigns an Ethernet IP address by adding the MAC and IP addresses of the Ethernet port to the BOOTP server configuration file. When the DSLAM boots, it automatically retrieves the IP address from the BOOTP server.

The DSLAM performs a BOOTP request only if the current IP address is set to 0.0.0.0. (This is the default for a new DSLAM or a DSLAM that has had its configuration file cleared using the erase startup-config command.)

To allow the DSLAM to retrieve its IP address from a BOOTP server you must first determine the MAC address of the DSLAM and then add that MAC address to the BOOTP configuration file on the BOOTP server.

Complete the following tasks to create a BOOTP server configuration file:

Step 1 Install the BOOTP server code on the workstation, if it is not already installed.

Step 2 Determine the MAC address from the label on the chassis.

Step 3 Add an entry in the BOOTP configuration file (usually /usr/etc/bootptab) for each DSLAM. Press Return after each entry to create a blank line between each entry. See the sample BOOTP configuration file that follows this table.

Step 4 Restart the DSLAM to automatically request the IP address from the BOOTP server.

Example

This example BOOTP configuration file shows the newly added DSLAM entry:

# /etc/bootptab: database for bootp server (/etc/bootpd)
#
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
# first field -- hostname
# (may be full domain name)
#
# hd -- home directory
# bf -- bootfile
# cs -- cookie servers
# ds -- domain name servers
# gw -- gateways
# ha -- hardware address
# ht -- hardware type
# im -- impress servers
# ip -- host IP address
# lg -- log servers
# lp -- LPR servers
# ns -- IEN-116 name servers
# rl -- resource location protocol servers
# sm -- subnet mask
# tc -- template host (points to similar host entry)
# to -- time offset (seconds)
# ts -- time servers

<display truncated>

#########################################################################
# Start of individual host entries
#########################################################################
Switch: tc=netcisco0: ha=0000.0ca7.ce00: ip=192.31.7.97:
dross: tc=netcisco0: ha=00000c000139: ip=192.31.7.26:

<information deleted>

Setting the Subtend Node Identifier

In a subtended network configuration, the subtend node acts as the host node connecting all the nodes to the network. This node is identified to the network using the subtend-id command.

To set the subtend node identifier, use the following command:

Command
Task

DSLAM# subtend-id node#

In priviledged EXEC mode, identify node# as the subtend host node.


Example

This example sets the DSL subtend node identifier to node 12:

DSLAM> enable
Password:
DSLAM# subtend-id 12

Configuring the ATM Address

The DSLAM is autoconfigured with an ATM address using a hierarchical addressing model similar to the OSI network service access point (NSAP) addresses. PNNI uses this hierarchy to construct ATM peer groups. ILMI uses the first 13 bytes of this address as the switch prefix that it registers with end systems.

Note If you manually change an ATM address, you must maintain the uniqueness of the address across the network.

Configuring ATM Addressing

This section describes the ATM addressing scheme and tells you how to

•Use the ATM default addressing scheme

•Manually set ATM addresses

Using the ATM Default Addressing Scheme

This section describes the default addressing scheme and the features and implications of using this scheme.

During the initial startup, the DSLAM generates an ATM address using the defaults shown in Figure 3-3.

Figure 3-3 ATM Address Format Defaults

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.

Manually Setting the ATM Address

You can configure a new ATM address that replaces the previous ATM address when running IISP software only, or that replaces the previous ATM address and generates a new PNNI node ID and peer group ID as follows:

•To configure a new ATM address that replaces the previous ATM address when running IISP software only, see the ATM Switch Router Software Configuration Guide, Chapter 10.

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_1/lhouse/sw_confg/ilmi_cnf.htm

•To configure a new ATM address that replaces the previous ATM address and generates a new PNNI node ID and peer group ID, see the ATM Switch Router Software Configuration Guide, Chapter 11.

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/12_1/lhouse/sw_confg/access.htm

You can configure multiple addresses for a single switch and use this configuration during ATM address migration. ILMI registers end systems with multiple prefixes during this period until you remove an old address. PNNI automatically summarizes all the switch prefixes in its reachable address advertisement.

For operation with ATM addresses other than the autoconfigured ATM address, use the atm address command to manually assign a 20-byte ATM address to the switch. The atm address command address_template variable can be a full 20-byte address or a 13-byte prefix followed by ellipses (...). Entering the ellipses automatically adds one of the switch's 6-byte MAC addresses in the ESI portion and 0 in the selector portion of the address.

Caution ATM addressing can lead to conflicts if you do not configure it correctly. For example,when configuring 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

You can accept the default ATM interface configuration or overwrite the default interface configuration using the CLI commands (see the ATM Switch Router Software Configuration Guide, Chapter 5 Configuring ATM Network Interfaces).

Modifying the Physical Layer Configuration of the Default ATM Interface

This section describes how to modify an ATM interface from the default configuration listed in Chapter 13, "Configuring In-Band Management." You can accept the ATM interface configuration or overwrite the default interface configuration using the CLI commands, which are described in ATM Switch Router Software Configuration Guide, Chapter 6, Configuring Virtual Connections.

Example

This example describes how to modify an OC-3 interface from the default settings to

•Disable scrambling cell-payload.

•Disable scrambling STS-streaming.

•Change Synchronous Optical Network (SONET) mode of operation from Synchronous Time Stamp level 3c (STS-3c) mode to Synchronous Transfer Module level 1 (STM-1).

To change the configuration of an ATM interface, follow these steps:

Step
Command
Task

1.

DSLAM# configure terminal

Enter global configuration mode.

2.

DSLAM(config)# interface atm slot/port

Select the physical interface to be configured and enter interface configuration mode.

3.

DSLAM(config-if)# no scrambling cell-payload

Disable cell-payload scrambling.

4.

DSLAM(config-if)# no scrambling sts-stream

Disable STS-stream scrambling.

5.

DSLAM(config-if)# sonet {stm-1 | sts-3c}

Configure SONET mode as SDH/STM-1.

6.

DSLAM(config-if)# end

Return to priviledged EXEC mode.

7.

DSLAM#

 

Example

This example shows how to disable cell-payload scrambling and STS-stream scrambling and changes the SONET mode of operation to Synchronous Digital Hierarchy/Synchronous Transfer Module 1 (SDH/STM-1) of OC-3 physical interface 0/0:

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

To display the physical interface configuration, use these privileged EXEC commands:

Command
Task

show controller atm slot/port

Show the physical layer configuration.

show running-config

Show the physical layer scrambling configuration.


Examples

This example displays the OC-3 physical interface configuration after you modify the defaults:

DSLAM# show controller atm 0/0
Interface ATM0/0 is up
Hardware is IDT252
PCI configuration registers:
bus_no=0, device_no=1
DeviceID=0x0004, VendorID=0x111D, Command=0x0006, Status=0x0290
Class=0x02/0x03/0x00, Revision=0x01, LatencyTimer=0x20, CacheLineSize=0x04
BaseAddr0=0x00000001, BaseAddr1=0x12001000, MaxLat=0x05, MinGnt=0x05
SubsysDeviceID=0x0000, SubsysVendorID=0x0000

slot 0, unit 0, subunit 0, fci_type 0x00000001,
max_pak_size 4528
particle size 576, pool size 400, cache size 1024, cache end 513
NICStAR registers:
data[0]: 76
config: 32A19838
status: F00404
rxStatQH: 3C17390
cellDropCt: 0
vpiVciLookupErrorCt: 0
invalidCellCt: 0
rawCellHead: 3CA7440
rawCellHandle: 3CDE004
timer: 7EAAE9
tstBase: 40000
txStatQB: 3C12000
txStatQH: 0
txStatQT: 3C12BC8
genPurpose: 8002
vpiVciMsbMask: 0
abrVbrSchTableDesc: 104C000
abrReadyQueuePtr: 0
vbrReadyQueuePtr: 0
rateTableDesc: 14000
txConnState: 70800068
currentTxSchAddr: 403D4
freeBufQueue0Sz: E000000A
freeBufQueue0Sz: E000000A
freeBufQueue1Sz: E000000B
RECEIVE CONNECTION TABLE:
VCD Control Buffer Handle DMA Address
35 E02A8000 0 0
36 E02A8000 0 0
37 E02A8000 0 0
38 E02A8000 0 0
39 E02A8000 0 0
40 E02A8000 0 0
41 E02A8000 0 0
42 E02A8000 0 0
43 FD2A8000 77 3C97F40
44 FD2A8000 FF 3CD10C0
45 E02A8000 0 0
46 E02A8000 0 0
47 E02A8000 0 0
48 E02A8000 0 0
49 E02A8000 0 0
50 E02A8000 0 0
51 E02A8000 0 0
52 E02A8000 0 0
53 E02A8000 0 0
54 E02A8000 0 0
55 FD2A8000 1B2 3CB7710
56 FD2A8000 176 3CC11F0
57 E02A8000 0 0
58 E02A8000 0 0
59 FD2A8000 1B5 3CB6F90
60 FD2A8000 194 3CA5BF0

enabled 0, disabled 0, throttled 0
vc_per_vp 4096, max_vp 1, max_vc 4096, total_vc 9594
Device values:
IDT252 device number 0, base addr 0xB2001000,
pci base off 0xA0DEAD01
TX Status Queue Base 0xA3C12000
TX Status Queue Tail 0xBF8
Segmentation Channel Queue 0xA3C14000
Rcv Stat Queue 0xA3C16000
Rcv Stat Queue tail A3C17490
FreeBufQ0Count 0 FreeBufQ0H 0 FreeBufQ0T 0
FreeBufQ1Count 2 FreeBufQ1H A3C18510 FreeBufQ1T A3C18BD0
Free Buff Queue 0 0xA3C18000
Free Buff Queue 1 0xA3C18100
Tx Buff Queue 0xA3C1A100


This example displays the OC-3 physical layer scrambling configuration after you modify the defaults:

DSLAM# show running-config
Building configuration...

Current configuration : 12235 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname DSLAM
!
boot system flash:ni2-dsl-mz.v121_7_da.20010416
slot 1 ATUC-1-4DMT
slot 2 ATUC-1-4DMT
slot 3 ATUC-1-4DMT
slot 4 ATUC-1-4DMT
slot 5 ATUC-1-4DMT
slot 6 ATUC-1-4DMT
slot 7 ATUC-1-4DMT
slot 8 ATUC-1-4DMT
slot 9 ATUC-4FLEXIDMT
slot 10 NI-2-DS3-T1E1
slot 12 ATUC-1-4DMT
slot 13 ATUC-4FLEXIDMT
slot 14 STUC-4-2B1Q-DIR-1
slot 15 STUC-4-2B1Q-DIR-1
slot 16 STUC-4-2B1Q-DIR-1
slot 17 STUC-4-2B1Q-DIR-1
slot 18 ATUC-1-DMT8
slot 19 ATUC-1-4DMT
slot 20 ATUC-1-DMT8
slot 21 ATUC-1-4DMT
slot 22 ATUC-1-4DMT
slot 23 ATUC-1-4DMT
slot 24 ATUC-1-4DMT
slot 25 ATUC-1-4DMT
slot 26 ATUC-1-4DMT
slot 27 ATUC-4FLEXIDMT
slot 28 ATUC-1-4DMT
slot 29 ATUC-1-DMT8
slot 30 ATUC-1-4DMT
slot 31 STUC-4-2B1Q-DIR-1
slot 32 ATUC-1-4DMT-I
no logging console
enable password cisco
!
!
!
!
!
!
dsl-profile default
alarms
dmt check-bytes interleaved downstream 4 upstream 6
dmt codeword-size downstream 16 upstream 8
sdsl bitrate 528
!
!
atm oam max-limit 1600
no atm oam intercept end-to-end
atm address 47.0091.8100.0000.0001.64ff.a980.0001.64ff.a980.00
atm router pnni
no aesa embedded-number left-justified
node 1 level 56 lowest
redistribute atm-static
!
atm ni2-switch trunk ATM0/IMA0
!
icm size 4194304
!
!
interface ATM0/0
no ip address
atm maxvp-number 0
atm maxvc-number 4096
atm maxvpi-bits 4
!
interface Ethernet0/0
ip address 172.21.186.145 255.255.255.192
!
interface ATM0/2
no ip address
no atm ilmi-keepalive
atm oam 0 5 seg-loopback
atm oam 0 16 seg-loopback
clock source loop-timed
framing crc4
lbo short gain10
ima-group 0
!
ip default-gateway 172.21.186.129
ip classless
ip route 0.0.0.0 0.0.0.0 172.21.186.129
no ip http server
!
!
line con 0
transport input none
line aux 0
line vty 0 4
password cisco
login
!
end


Configuring IP Interface Parameters

This section describes how to configure IP addresses on the DSLAM processor interfaces. You configure each IP address for one of the following types of connections:

•Ethernet port—Configure either from the BOOTP server or by using the ip address command in interface-configuration mode for the Ethernet 0/0 interface.

•Serial Line Internet Protocol/Point-to-Point Protocol (SLIP/PPP)—See Chapter 2, "Configuring Terminal Lines and Modem Support."

Note These IP connections are used only for network management.

To configure the DSLAM to communicate using the Ethernet interface, provide the IP address and subnet mask bits for the interface as described in this section.

Defining an IP address

This section provides a summary of IP addressing concepts for those who are familiar with IP addressing.

Internet addresses are 32-bit values assigned to hosts that use the IP protocols. These addresses are in dotted decimal format (four decimal numbers separated by periods), such as 192.17.5.100. Each number is an 8-bit value between 0 and 255.

IP addresses are divided into three classes. These classes differ in the number of bits allocated to the network and host portions of the address:

•The Class A Internet address format allocates the highest 8 bits to the network field and sets the highest-order bit to 0 (zero). The remaining 24 bits form the host field.

•The Class B Internet address allocates the highest 16 bits to the network field and sets the two highest-order bits to 1, 0. The remaining 16 bits form the host field.

•The Class C Internet address allocates the highest 24 bits to the network field and sets the three highest-order bits to 1, 1, 0. The remaining 8 bits form the host field.

The default IP address is none.

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

Defining Subnet Mask Bits

Subnetting is an extension of the Internet addressing scheme which allows multiple physical networks to exist within a single Class A, B, or C network. The subnet mask determines whether subnetting is in effect on a network. The usual practice is to use a few of the far-left bits in the host portion of the network address to assign a subnet field.

Internet addressing conventions allow a total of 24 host bits for Class A addresses, 16 host bits for Class B addresses, and 8 host bits for Class C addresses. When you are further subdividing your network (that is, subnetting your network), the number of host addressing bits is divided between subnetting bits and actual host address bits. You must specify a minimum of two host address bits, or the subnetwork is not populated by hosts.

Note Because all zeros in the host field specifies the entire network, subnetting with subnet address 0 is illegal and is strongly discouraged.

Table 3-2 provides a summary of subnetting parameters.

Table 3-2 Subnetting Parameters

First Class
First Byte
Network Bits
Host Bits
     
Max Subnet Bits
Min Address Bits

A

1 to 126

8

22

2

B

128 to 191

16

14

2


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# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
DSLAM(config)# interface ethernet 0/0
DSLAM(config-if)# ip address 172.20.40.93 255.255.255.0
DSLAM(config-if)# end
DSLAM# show interface ethernet 0/0
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 0001.64ff.a97f (bia 0001.64ff.a97f)
Internet address is 172.21.186.145/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 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
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 4000 bits/sec, 5 packets/sec
5 minute output rate 2000 bits/sec, 3 packets/sec
906236 packets input, 202482126 bytes, 0 no buffer
Received 889038 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
163965 packets output, 21172110 bytes, 0 underruns
0 output errors, 9 collisions, 1 interface resets
0 babbles, 0 late collision, 33 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out


Displaying an IP Address

Use the show running-config command to display the CPU IP address:

DSLAM# show running-config
Building configuration...

Current configuration:
!
version XX.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM
!
boot bootldr bootflash:/tftpboot/rbhide/ls-wp-mz.XXX-X.X.WA4.X.XX
!
ip host-routing
ip rcmd rcp-enable
ip rcmd rsh-enable
ip rcmd remote-username dplatz
ip domain-name cisco.com
ip name-server 198.92.30.32
atm filter-set tod1 index 4 permit time-of-day 0:0 0:0
atm qos default cbr max-cell-loss-ratio clp1plus0 12
atm qos default vbr-nrt max-cell-loss-ratio clp1plus0 12
atm address 47.0091.8100.0000.0041.0b0a.1081.0041.0b0a.1081.00
atm address 47.0091.8100.5670.0000.0000.0000.0040.0b0a.1081.00
atm route-optimization percentage-threshold 250
atm router pnni
node 1 level 56 lowest
redistribute atm-static
!

<Information Deleted>

!
interface ATM0/1
no keepalive
!
interface ATM0/0
no ip address
no keepalive
atm maxvp-number 0
atm pvc 0 any-vci encap aal5snap
!
interface Ethernet0/0
ip address 172.20.40.93 255.255.255.0
!
no ip classless
atm route 47.0091.8100.0000... ATM0/0 scope 1
atm route 47.0091.8100.0000.00... ATM0/0 e164-address 1234567
!
line con 0
line aux 0
line vty 0 4
login
!
end

Testing the Ethernet Connection

After you configure the IP addresses for the Ethernet interface, test for connectivity between the DSLAM and a host. The host can reside anywhere in your network. To test for Ethernet connectivity, use this command in EXEC mode:

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

Configuring Network Clocking

This section describes how to configure network clocking and network clocking for the DSLAM. Each port has a transmit clock and derives its receive clock from the receive data. You can configure transmit clocking for each port in one of these ways:

•Network derived—Transmit clocking is derived from the highest priority configured source, either from the internal clock (the default) or the public network.

•Loop-timed—Transmit clocking is derived from the receive clock source.

The DSLAM receives derived clocking, along with data, from a specified interface. For example, in Figure 3-4 the DSLAM extracts transmit clocking, configured as priority one, from the data received at interface 0/1 and distributed as the transmit clock to the rest of the DSLAM. Interface 0/2 then uses network-derived transmit clocking received from interface 0/1.

Figure 3-4 Transmit Clock Distribution

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.

If the network clock source interface stops responding, the software switches to the next highest-configured priority network clock source. For example, Figure 3-5 shows:

•DSLAM number two is configured to receive transmit clocking from an external reference clock source through interface 0/0.

•Interface 0/1 uses network-derived transmit clocking.

•The priority 1 transmit clock interface 0/0 fails.

•The priority 2 interface, 0/2, immediately starts providing the transmit clocking to the backplane and interface 0/1.

•If you configure the network-clock-select command as revertive when the priority 1 interface, 0/0, is functioning correctly for at least 1 minute, the interfaces using network-derived transmit clocking starts to receive their clocking again from interface 0/0.

Note The network clock is, by default, configured as non-revertive. Non-revertive means that if a clock fails, the software selects the next-higher clock until that clock fails, then the next-highest, and so forth. The algorithm to switch to the highest priority best clock only runs if you configure the network-clock-select command as revertive.

Figure 3-5 Transmit Clocking Priority Configuration Example

These sections describe network clocking:

• Configuring Network Clock Priorities and Sources

• Configuring the Transmit Clocking Source

• Providing Clock Synchronization Services

Configuring Network Clock Priorities and Sources

To configure the network clocking priorities and sources, use these command in global configuration mode:

Command
Task

network-clock-select priority {BITS | system | atm slot/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# configure terminal
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# configure terminal
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# configure terminal
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)#

Configuring the Transmit Clocking Source

To configure the location from which an interface receives its transmit clocking, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

DSLAM(config)# interface atm slot/port

Select the interface to be configured.

2.

DSLAM(config-if)# clock source {loop-timed | network-derived}

Configure the interface network clock source.


Note Network-derived means the highest-priority clock that is both configured and functional.

Examples

This example configures ATM interface 0/1 to receive its transmit clocking from a network-derived source:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# clock source network-derived
DSLAM(config-if)#

This example displays the network clocking configuration shown in Figure 4-3:

DSLAM# show network-clocks
PLL failed: 58886; PLL Passed: 1082982
FAIL: 0; NCO: F984; REF: F982; ERR: 2; ERR_D: 0; MAG: -1;
clock configuration is NON-Revertive
Priority 1 clock source: BITS clock
Priority 2 clock source: No clock
Priority 3 clock source: No clock
Priority 4 clock source: No clock
Priority 5 clock source: System clock

Current clock source:System clock, priority:5

Nettime Config Register Contents:
NDIV:FF SRC:2, SLOCK:0, TLOCK:0, NFAIL:0, E1:0, NSEL:0
Trunk LED Register CLK_SEL:3

BITS Register Contents:
CR1: CB, CR2: 0, CR3: 0, ICR: 0, TSR: C1, PSR: 31, ESR: 77, CR4: 0

BITS Source configured as: T1 Short Haul, 0-133ft/0.6db pulse, 100 ohm cable, 1n


This example displays the clock source configuration of ATM interface 0/2:

DSLAM# show running-config
Building configuration...

Current configuration:
!
version ZZ.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM
!
boot bootldr bootflash:/tftpboot/ls-wp-mz.11X-X.X.WA4.X.XX
!
network-clock-select 2 ATM0/1

<Information Deleted>

!
interface ATM0/2
no keepalive
atm manual-well-known-vc
atm access-group tod1 in
atm pvc 0 35 rx-cttr 3 tx-cttr 3 interface ATM0/2 0 any-vci encap qsaal
atm route-optimization soft-vc interval 360 time-of-day 18:0 5:0
 clock-source network-derived
!

<Information Deleted>

This example displays the interface controller status of interface 0/0:

DSLAM# show controllers atm 0/0
Interface ATM0/0 is up
Hardware is IDT252
PCI configuration registers:
bus_no=0, device_no=1
DeviceID=0x0004, VendorID=0x111D, Command=0x0006, Status=0x0290
Class=0x02/0x03/0x00, Revision=0x01, LatencyTimer=0x20, CacheLineSize=0x04
BaseAddr0=0x00000001, BaseAddr1=0x12001000, MaxLat=0x05, MinGnt=0x05
SubsysDeviceID=0x0000, SubsysVendorID=0x0000

slot 0, unit 0, subunit 0, fci_type 0x00000001,
max_pak_size 4528
particle size 576, pool size 400, cache size 1024, cache end 513
NICStAR registers:
data[0]: 15C
config: 32A19838
status: F00404
rxStatQH: 3C177F0
cellDropCt: 0
vpiVciLookupErrorCt: 0
invalidCellCt: 0
rawCellHead: 3C9F580
rawCellHandle: 3CDE004
timer: AE396C
tstBase: 40000
txStatQB: 3C12000
txStatQH: 0
txStatQT: 3C13600
genPurpose: 8002
vpiVciMsbMask: 0
abrVbrSchTableDesc: 104C000
abrReadyQueuePtr: 0
vbrReadyQueuePtr: 0
rateTableDesc: 14000
txConnState: 70800002
currentTxSchAddr: 42298
freeBufQueue0Sz: E000000A
freeBufQueue0Sz: E000000A
freeBufQueue1Sz: E000000B
RECEIVE CONNECTION TABLE:
VCD Control Buffer Handle DMA Address
35 E02A8000 0 0
36 E02A8000 0 0
37 E02A8000 0 0
38 E02A8000 0 0
39 E02A8000 0 0
40 E02A8000 0 0
41 E02A8000 0 0
42 E02A8000 0 0
43 FD2A8000 9B 3C98F00
44 FD2A8000 187 3CD0100
45 E02A8000 0 0
46 E02A8000 0 0
47 E02A8000 0 0
48 E02A8000 0 0
49 E02A8000 0 0
50 E02A8000 0 0
51 E02A8000 0 0
52 E02A8000 0 0
53 E02A8000 0 0
54 E02A8000 0 0
55 FD2A8000 1B2 3CB7710
56 FD2A8000 176 3CC11F0
57 E02A8000 0 0
58 E02A8000 0 0
59 FD2A8000 1B5 3CB6F90
60 FD2A8000 194 3CA5BF0

enabled 0, disabled 0, throttled 0
vc_per_vp 4096, max_vp 1, max_vc 4096, total_vc 9594
Device values:
IDT252 device number 0, base addr 0xB2001000,
pci base off 0xA0DEAD01
TX Status Queue Base 0xA3C12000
TX Status Queue Tail 0x1638
Segmentation Channel Queue 0xA3C14000
Rcv Stat Queue 0xA3C16000
Rcv Stat Queue tail A3C178A0
FreeBufQ0Count 0 FreeBufQ0H 0 FreeBufQ0T 0
FreeBufQ1Count 1 FreeBufQ1H A3C1A040 FreeBufQ1T A3C1A040
Free Buff Queue 0 0xA3C18000
Free Buff Queue 1 0xA3C18100
Tx Buff Queue 0xA3C1A100


Providing Clock Synchronization Services

Any module in a DSLAM chassis capable of receiving and distributing a network timing signal can propagate that signal to any similarly capable module in the chassis. These entities are capable of receiving and distributing a primary reference source (PRS) for the clock:

•A BITS clock through the I/O card

•An OC-3 in a DSLAM chassis

•A quad DS3 module in a DSLAM chassis that derives the clock from the trunk interface

Note A trunk port can propagate a clocking signal in either direction.

If you issue the network-clock-select command with the appropriate parameters, you can define a particular port in a DSLAM chassis (subject to the above limitations) to serve as the source of a PRS for the entire chassis or for other devices in the networking environment. This command is described in the "Configuring Network Clock Priorities and Sources" section.

You can also use the network-clock-select command to designate a particular port in a DSLAM chassis to serve as a master clock source for distributing a single clocking signal throughout the chassis or to other network devices. You can distribute this reference signal in any location the network needs to globally synchronize the flow of constant bit rate (CBR) data.

Configuring the Network Routing

For network routing, the default software image for the DSLAM contains the PNNI routing protocol. The PNNI protocol provides the route dissemination mechanism for complete plug-and-play capability. This section describes modifications you can make to the default PNNI or Interim-Interswitch Signaling Protocol (IISP) routing configurations.

Use the atm route command to configure a static route. Static route configuration allows ATM call setup requests to be forwarded on a specific interface if the addresses match a configured address prefix.

Note An interface must be UNI or IISP if it is configured with a static route. Static routes configured as PNNI interfaces default as down.

Example

This example shows how to use the atm route command to configure the 13-byte peer group prefix as 47.0091.8100.567.0000.0ca7.ce01 at interface 0/1:

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

Configuring the Time, Date, and Month

Although not required, you can set several system parameters as part of the initial system configuration. To set the system parameters, perform these tasks, beginning in privileged EXEC mode:

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 2000

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 2000
Publications#

Configuring SNMP Management

SNMP is an application-layer protocol that allows the SNMP manager and agent to communicate. SNMP provides a message format for sending information between an SNMP manager and an SNMP agent.

The SNMP system consists of three parts:

•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.

The SNMP agent contains MIB variables whose values the SNMP manager can request or change. A manager can get a value from an agent or store a value into an agent. The agent gathers data from the MIB, the repository for information about device parameters and network data. The agent can also respond to a manager's requests to get or set data.

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.

Figure 3-6 illustrates the communications relationship between the SNMP manager and agent.

Figure 3-6 Communication between an SNMP Agent and Manager

Figure 3-6 shows that a manager can send the agent requests to get and set MIB values. The agent can respond to these requests. Independent of this interaction, the agent can send unsolicited traps to the manager notifying the manager of network conditions.

Cisco supports the SNMP Version 1 protocol, referred to as SNMPv1, and the SNMP Version 2 protocol, referred to as SNMPv2. Cisco's implementation of SNMP supports all MIB II variables (as described in RFC 1213) and SNMP traps (as described in RFC 1215).

RFC 1447, "SNMPv2 Party MIB" (April 1993), describes the managed objects that correspond to the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies, as defined by the SNMPv2 Administrative Model. RFC 1450, "SNMPv2 MIB," (April 1993) describes the managed objects that instrument the behavior of an SNMPv2 implementation. Cisco supports the MIB variables as required by the conformance clauses specified in these MIBs.

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.

Configuring Support for Both SNMPv1 and SNMPv2

This section tells you how to configure support for both SNMPv1 and SNMPv2. The topics are:

•Establishing the contact, location, and serial number of the SNMP agent

•Defining the maximum SNMP agent packet size

•Monitoring SNMP status

•Disabling the SNMP agent

•Enabling the SNMP agent shutdown mechanism

Establishing the Contact, Location, and Serial Number of the SNMP Agent

You can set the system contact, location, and serial number of the SNMP agent so that these descriptions can be accessed through the configuration file. Use one or more of these commands in global configuration mode:

Command
Task

snmp-server contact text

Set the system contact string.

snmp-server location text

Set the system location string.

snmp-server chassis-id text

Set the system serial number.


Defining the Maximum SNMP Agent Packet Size

You can set the maximum packet size permitted when the SNMP agent is receiving a request or generating a reply. To do so, use this command in global configuration mode:

Command
Task

snmp-server packetsize byte-count

Establish the maximum packet size.


Monitoring SNMP Status

To monitor SNMP input and output statistics, including the number of illegal community string entries, errors, and requested variables, use this command in EXEC mode:

Command
Task

show snmp

Monitor SNMP status.


Disabling the SNMP Agent

To disable both versions of SNMP (SNMPv1 and SNMPv2) concurrently, use this command in global configuration mode:

Command
Task

no snmp-server

Disable SNMP agent operation.


Enabling the SNMP Agent Shutdown Mechanism

This section tells you how to enable a reload from the network after a system shutdown.

Using SNMP packets, a network management tool can send messages to users on both virtual terminals and the console. This facility operates in a similar fashion to the EXEC send command, but the SNMP request that causes the message to be issued to the users also specifies the action to be taken after the message is delivered. One possible action is a shutdown request. After a system shuts down, it is typically reloaded.

Reloading from the network is a powerful feature, and therefore is protected by the snmp-server system-shutdown global configuration command. If you do not issue this command, the shutdown mechanism does not enable.

To enable the SNMP agent shutdown mechanism, use this command in global configuration mode:

Command
Task

snmp-server system-shutdown

Use the SNMP message reload feature and request a system shutdown message.


To understand how to use this feature with SNMP requests, read the document mib.txt available by anonymous FTP from Cisco Connection Online.

Configuring SNMPv2 Support

SNMPv2 security requires that you create an access policy that defines the relationship between a manager and the agent. For each management station that the agent communicates with, you must create a separate access policy. Creating an access policy is a multiple-task process:

Step 1 If you do not want to use one of the predefined views, define a view to identify the objects that can be seen.

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.

Figure 3-7 shows the information exchanged between the manager and the agent.

Figure 3-7 Flow of Management Operations Requests, Responses, and Traps

•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.

Configuring Support for SNMPv2

To configure support for SNMPv2, perform the tasks described in the following sections:

• Creating or Modifying an SNMP View Record

• Creating or Modifying an SNMP Context Record

• Creating or Modifying an SNMPv2 User Record

• Creating an SNMPv2 Access Policy

• Defining SNMPv2 Trap Operations

After you create a record, you can modify the record contents by changing one or more of the record values. To do this, issue the command again, naming the record that you created originally. You must fully specify the record values, including the argument values, to remain unchanged.

Creating or Modifying an SNMP View Record

To create or modify an SNMP view record, use this command in global configuration mode:

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.

Creating or Modifying an SNMP Context Record

To create or modify an SNMP context record, use this command in global configuration mode:

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.

Creating or Modifying an SNMPv2 User Record

To create or modify an SNMPv2 user record, use this command in global configuration mode:

Command
Task

snmp-server user user-name user-oid [protocol-address] [packetsize size] [local | remote] [authentication md5 key [clock clock] [lifetime lifetime]

Create or modify a user record.


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

Creating an SNMPv2 Access Policy

To create or modify an SNMPv2 access policy, use this command in global configuration mode:

Command
Task

snmp-server access-policy destination-party source-party context privileges

Create or modify an access policy.


To remove an SNMPv2 access policy, use the no snmp-server access-policy command. Specify all three arguments to correctly identify the access policy to be deleted. A difference of one value constitutes a unique access policy entry.

Defining SNMPv2 Trap Operations

A trap is an unsolicited message sent by an SNMP agent to an SNMP manager indicating that some event has occurred. The SNMP trap operations allow you to configure the Cisco IOS software to send information to a network management application when a particular event occurs. You can specify these features for SNMPv2 agent trap operations:

•Source interface

•Recipient of the trap message

•Trap message authentication

•Trap types

•Retransmission interval

•Message (packet) queue length for each trap host

To define the recipient of the trap message, configure a user record for the manager, including the protocol address, and specify the user record as the destination user for the snmp-server access policy command.

To define traps for the agent to send to the manager, use one or more of these commands in global configuration mode:

Command
Task

snmp-server trap-source interface

Specify the source interface (and hence IP address) of the trap message.

snmp-server access-policy destination-user source-user context privileges

Specify the access policy that defines the traps that the agent can send to the manager.

snmp-server enable traps snmp 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.

Configuring SNMPv1 Support

If the SNMP manager supports only the SNMPv1 protocol, you must configure the relationship between the manager and the agent using SNMPv1 support.

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:

• Creating or Modifying Access Control for an SNMPv1 Community

• Defining SNMP Trap Operations for SNMPv1

Creating or Modifying Access Control for an SNMPv1 Community

You can configure a community string, which acts like a password, to permit access to the agent on the DSLAM. Optionally, you can associate a list of IP addresses with that community string to permit only managers with these IP addresses to use the string.

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.

Defining SNMP Trap Operations for SNMPv1

The SNMP trap operations allow a system administrator to configure the agent to send information to a manager when a particular event occurs. You can specify these features for SNMP server trap operations:

•Source interface

•Recipient

•Trap message authentication

•Trap types

•Retransmission interval

•Define the message (packet) queue length for each trap host

To define traps for the agent to send to the specified manager, perform these tasks in global configuration mode:

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 enable traps snmp authentication

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.

Configuring SNMP RMON Support

Remote Monitoring (RMON)

•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 the ATM Switch Router Software Configuration Guide, Chapter 14 , 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-threshold value [event-number] [owner string]

Set an alarm on a MIB object.

rmon event number [log] [trap community] [description string] [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.

To display the current RMON status, use these EXEC commands:

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.

Storing the Configuration

After you complete autoconfiguration and any manual configurations, copy the configuration into nonvolatile random-access memory (NVRAM). If you power off your DSLAM prior to saving the configuration in NVRAM you lose all manual configuration changes.

An example of the copy running-config command is:

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

Testing the Configuration

After you finish configuring the DSLAM, you can use the commands described in this section to confirm the hardware, software, and interface configuration:

•Confirming the Hardware Configuration

•Confirming the Software Version

•Confirming Power-on Diagnostics

•Confirming the Ethernet Configuration

•Confirming the ATM Address

•Testing the Ethernet Connection

•Confirming the ATM Connections

•Confirming the ATM Interface Configuration

•Confirming the Interface Status

•Confirming Virtual Channel Connections

•Confirming the Running Configuration

•Confirming the Saved Configuration

Confirming the Hardware Configuration

Use the show hardware command to confirm the correct hardware installation. For example:

DSLAM# show hardware
Chassis Type: C6260
I/O Card: 6260-E1-IO

Slot 1 : ATUC-1-4DMT Slot 17: STUC-4-2B1Q-DIR-1
Slot 2 : ATUC-1-4DMT Slot 18: ATUC-1-DMT8
Slot 3 : ATUC-1-4DMT Slot 19: ATUC-1-4DMT
Slot 4 : ATUC-1-4DMT Slot 20: ATUC-1-DMT8
Slot 5 : ATUC-1-4DMT Slot 21: ATUC-1-4DMT
Slot 6 : ATUC-1-4DMT Slot 22: ATUC-1-4DMT
Slot 7 : ATUC-1-4DMT Slot 23: ATUC-1-4DMT
Slot 8 : ATUC-1-4DMT Slot 24: ATUC-1-4DMT
Slot 9 : ATUC-4FLEXIDMT Slot 25: ATUC-1-4DMT
Slot 10: NI-2-DS3-T1E1 Slot 26: ATUC-1-4DMT
Slot 11: EMPTY Slot 27: ATUC-4FLEXIDMT
Slot 12: ATUC-1-4DMT Slot 28: ATUC-1-4DMT
Slot 13: ATUC-4FLEXIDMT Slot 29: ATUC-1-DMT8
Slot 14: STUC-4-2B1Q-DIR-1 Slot 30: ATUC-1-4DMT
Slot 15: STUC-4-2B1Q-DIR-1 Slot 31: STUC-4-2B1Q-DIR-1
Slot 16: STUC-4-2B1Q-DIR-1 Slot 32: ATUC-1-4DMT-I

Fan Module 1: Present 2: Present

Power Supply Module 1: 6260-PEM-AC
Power Supply Module 2: 6260-PEM-AC

Confirming the Software Version

Use the show version command to confirm the correct version and type of software and the configuration register are installed. For example:

DSLAM# show version
Cisco Internetwork Operating System Software
IOS (tm) NI2 Software (NI2-DSL-M), Experimental Version 12.1(20010416:212622) []
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Mon 16-Apr-01 17:26 by chrel
Image text-base: 0x800082C0, data-base: 0x8132A000

ROM: System Bootstrap, Version 12.0(5)DA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc)
BOOTFLASH: NI2 Software (NI2-DBOOT-M), Version 12.1(6)DA, EARLY DEPLOYMENT RELE)

6260_E1IMA uptime is 1 week, 6 days, 5 hours, 48 minutes
System returned to ROM by reload
System image file is "flash:ni2-dsl-mz.v121_7_da.20010416"

cisco 6260 (NI2) processor with 60416K/5120K bytes of memory.
RC64475 CPU at 100Mhz, Implementation 48, Rev 0.0
Bridging software.
1 Ethernet/IEEE 802.3 interface(s)
112 DMT DSL Port interface(s)
20 SDSL DSL Port interface(s)
13 ATM network interface(s)
522232 bytes of non-volatile configuration memory.

4096K bytes of Boot Flash (Sector size 128K).
16384K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2102

Confirming the Ethernet Configuration

Use the show interface ethernet command to confirm the Ethernet interface is configured correctly. For example:

DSLAM# show interface ethernet 0/0
Ethernet0/0 is up, line protocol is up
Hardware is AmdP2, address is 0001.64ff.a97f (bia 0001.64ff.a97f)
Internet address is 172.21.186.145/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 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
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 2000 bits/sec, 3 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
910869 packets input, 202979554 bytes, 0 no buffer
Received 890807 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
166029 packets output, 21332341 bytes, 0 underruns
0 output errors, 9 collisions, 1 interface resets
0 babbles, 0 late collision, 33 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

Confirming the ATM Address

Use the show atm addresses command to confirm correct configuration of the ATM address for the DSLAM. For example:

DSLAM# show atm addresses

Switch Address(es):
47.0091.8100.0000.0001.64ff.a980.0001.64ff.a980.00 active
NOTE: Switch addresses with selector bytes 01 through 7F
are reserved for use by PNNI routing

PNNI Local Node Address(es):
47.0091.8100.0000.0001.64ff.a980.0001.64ff.a980.01 Node 1

Soft VC Address(es):
47.0091.8100.0000.0001.64ff.a980.4000.0c98.0020.00 ATM0/2
47.0091.8100.0000.0001.64ff.a980.4000.0c98.0030.00 ATM0/3

Soft VC Address(es) for Frame Relay Interfaces :

ILMI Switch Prefix(es):
47.0091.8100.0000.0001.64ff.a980

ILMI Configured Interface Prefix(es):

LECS Address(es):

Testing the Ethernet Connection

After you configure the IP addresses for the Ethernet interface, test for connectivity between the DSLAM and a host. The host can reside in any location on your network. To test for Ethernet connectivity, use this command:

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

Confirming the ATM Connections

Use the ping atm command to confirm that the ATM interfaces are configured correctly. For example:

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#

Confirming the ATM Interface Configuration

Use the show atm interface command to confirm the atm interfaces are configured correctly. For example:

DSLAM# show atm interface

Interface: ATM0/0 Port-type: cpu
IF Status: UP Admin Status: UP
Auto-config: disabled AutoCfgState: not applicable
IF-Side: not applicable IF-type: not applicable
Uni-type: not applicable Uni-version: not applicable
Max-VPI-bits: 4 Max-VCI-bits: 14
Max-VP: 0 Max-VC: 4096
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
26 0 0 0 0 0 0 26 26
Logical ports(VP-tunnels): 0
Input cells: 106840 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/2 Port-type: e1_ima_link
IF Status: UP Admin Status: UP
Auto-config: enabled AutoCfgState: waiting for response from peer
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.0
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.0001.64ff.a980.4000.0c98.0020.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 0 0 1 0 0 3 2
Logical ports(VP-tunnels): 0
Input cells: 925 Output cells: 74
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]

Confirming the Interface Status

Use the show atm status command to confirm the status of ATM interfaces. For example:

DSLAM# show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint,)

Type PVCs SoftPVCs SVCs TVCs PVPs SoftPVPs SVPs Total
P2P 26 0 0 0 0 0 0 26
P2MP 0 0 0 0 0 0 0 0
MP2P 0 0 0 0 0 0 0 0
TOTAL INSTALLED CONNECTIONS = 26

PER-INTERFACE STATUS SUMMARY AT 07:15:04 UTC Wed Oct 18 2000:
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM0/0 UP up n/a UpAndNormal Idle n/a
ATM0/2 UP up waiting Restarting Idle n/a

Confirming Virtual Channel Connections

Use the show atm vc command to confirm the status of ATM virtual channels. For example:

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

Confirming the Running Configuration

Use the show running-config command to confirm that the configuration being used is configured correctly. For example:

DSLAM# show running-config
Building configuration...

Current configuration : 12407 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname 6260_E1IMA
!
boot system flash:ni2-dsl-mz.v121_7_da.20010416
slot 1 ATUC-1-4DMT
slot 2 ATUC-1-4DMT
slot 3 ATUC-1-4DMT
slot 4 ATUC-1-4DMT
slot 5 ATUC-1-4DMT
slot 6 ATUC-1-4DMT
slot 7 ATUC-1-4DMT
slot 8 ATUC-1-4DMT
slot 9 ATUC-4FLEXIDMT
slot 10 NI-2-DS3-T1E1
slot 12 ATUC-1-4DMT
slot 13 ATUC-4FLEXIDMT
slot 14 STUC-4-2B1Q-DIR-1
slot 15 STUC-4-2B1Q-DIR-1
slot 16 STUC-4-2B1Q-DIR-1
slot 17 STUC-4-2B1Q-DIR-1
slot 18 ATUC-1-DMT8
slot 19 ATUC-1-4DMT
slot 20 ATUC-1-DMT8
slot 21 ATUC-1-4DMT
slot 22 ATUC-1-4DMT
slot 23 ATUC-1-4DMT
slot 24 ATUC-1-4DMT
slot 25 ATUC-1-4DMT
slot 26 ATUC-1-4DMT
slot 27 ATUC-4FLEXIDMT
slot 28 ATUC-1-4DMT
slot 29 ATUC-1-DMT8
slot 30 ATUC-1-4DMT
slot 31 STUC-4-2B1Q-DIR-1
slot 32 ATUC-1-4DMT-I
no logging console
enable password cisco
!
!
!
!
!
!
dsl-profile default
alarms
dmt check-bytes interleaved downstream 4 upstream 6
dmt codeword-size downstream 16 upstream 8
sdsl bitrate 528
!
atm oam max-limit 1600
no atm oam intercept end-to-end
atm address 47.0091.8100.0000.0001.64ff.a980.0001.64ff.a980.00
atm router pnni
no aesa embedded-number left-justified
node 1 level 56 lowest
redistribute atm-static
!
atm ni2-switch trunk ATM0/IMA0
!
icm size 4194304
!
!
interface ATM0/0
no ip address
atm maxvp-number 0
atm maxvc-number 4096
atm maxvpi-bits 4
!
interface Ethernet0/0
ip address 172.21.186.145 255.255.255.0
!
interface ATM0/2
no ip address
no atm ilmi-keepalive
atm oam 0 5 seg-loopback
atm oam 0 16 seg-loopback
clock source loop-timed
framing crc4
lbo short gain10
ima-group 0
!
ip default-gateway 172.21.186.129
ip classless
ip route 0.0.0.0 0.0.0.0 172.21.186.129
no ip http server
!
atm route 47.0091.8100.5670.0000.ca7c.e01... ATM0/0
snmp-server trap-source ATM0/0
snmp-server enable traps config
snmp-server enable traps alarms
!
!
line con 0
transport input none
line aux 0
line vty 0 4
password cisco
login
!
end

Confirming the Saved Configuration

Use the show startup-config command to confirm that the configuration saved in NVRAM is configured correctly. For example:

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

hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Dec 3 14:15:06 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.