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

Table Of Contents

Configuring ATM Accounting and ATM RMON

Configuring ATM Accounting

ATM Accounting Overview

Configuring Global ATM Accounting

Enabling ATM Accounting on an Interface

Configuring the ATM Accounting Selection Table

Configuring ATM Accounting Files

Controlling ATM Accounting Data Collection

Configuring ATM Accounting SNMP Traps

Using TFTP to Copy the ATM Accounting File

Configuring ATM RMON

RMON Overview

Configuring Port Select Groups

Adding Interfaces to a Port Select Group

Enabling Data Collection

Configuring an RMON Event

Configuring an RMON Alarm


Configuring ATM Accounting and ATM RMON

This chapter describes the ATM accounting and Remote Monitoring (RMON) features used with Cisco DSLAMs with NI-2, and includes these sections:

• Configuring ATM Accounting

• Configuring ATM RMON

Configuring ATM Accounting

This section describes how to enable and configure the ATM accounting feature in the DSLAM.

ATM Accounting Overview

The ATM accounting feature provides accounting and billing services for virtual circuits (VCs) used on the DSLAM. You enable ATM accounting on an edge switch (or DSLAM) to monitor call setup and traffic activity. A specific interface can be configured to monitor either incoming or outgoing or incoming and outgoing VC use. Figure 14-1 shows a typical ATM accounting environment.

Figure 14-1 ATM Accounting Environment

The edge switches or DSLAMs, connected to the exterior Internet, are connections that require monitoring for accounting and billing purposes.

Switching speeds and number of VCs supported by the DSLAM while monitoring virtual circuit use for accounting purposes can cause the amount of data to be gathered to reach the megabyte range. With such a large amount of data in the ATM accounting files, using traditional Simple Network Management Protocol (SNMP) methods of data retrieval is not feasible. You can store the collected accounting information in a file which you can retrieve using a file transfer protocol. SNMP provides management control of the selection and collection of accounting data. Figure 14-2 shows an interface, filtering, and file configuration example.

Figure 14-2 Interface and File Management for ATM Accounting

A file used for data collection actually corresponds to two memory buffers:

•One buffer is actively saving data.

•The second buffer is passive and ready to have its data either retrieved using Trivial File Transport Protocol (TFTP) or overwritten when the currently active file reaches its maximum capacity.

Using TFTP to download the file is the same process used to download Cisco IOS images and configuration files from the Flash memory to a host.

Configuring Global ATM Accounting

You must enable the ATM accounting feature to start gathering ATM accounting virtual circuit call setup and use data. The ATM accounting feature runs in the background and captures configured accounting data for VC changes such as calling party, called party, or start time and connection type information for specific interfaces to a file.

Caution Enabling ATM accounting could slow the basic operation of the DSLAM.

Note Even if you disable ATM accounting globally, other ATM accounting commands, both global and for individual interfaces, remain in the configuration file.

Use the following commands configure ATM accounting.

Command
Task

atm accounting enable

In global configuration mode, enable ATM accounting for the DSLAM.

show running-config

In privileged EXEC mode, display the ATM accounting status.


Enabling ATM Accounting on an Interface

After you enable ATM accounting, you must configure specific ingress or egress interfaces, usually on edge switches or DSLAMs connected to the external network, to start gathering the ATM accounting data.

To enable ATM accounting on a specific interface, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select the interface to be configured.

2.

atm accounting

Enable ATM accounting on the selected interface.


Example

This example shows how to enable ATM accounting on ATM interface 20/0 and displays the result:

DSLAM(config)# interface atm 20/0
DSLAM(config-if)# atm accounting
DSLAM# show running-config
Building configuration...

Current configuration:
!

<Information Deleted>

!
interface ATM20/0
no keepalive
atm accounting
!
--More--
!
<information deleted>

Configuring the ATM Accounting Selection Table

The ATM accounting selection table determines the connection data to be gathered from the DSLAM. To configure the ATM accounting selection entries, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

atm accounting selection 1

Configure the ATM accounting selection index number and change to accounting selection mode.

2.

default [connection-type | list]

Reset the ATM accounting selection table configuration to the default.

3.

connection-types [pvc | pvp | spvc-originator | spvc-target | spvp-originator | spvp-target | svc-in | svc-out | svp-in | svp-out]

Configure the accounting connection types.

4.

list hexadecimal_number

Configure the list of ATM accounting MIB objects to collect1 .

1 The MIB objects are listed in the ATM Accounting Information MIB publication.


The atm accounting selection command creates or modifies an entry in the selection table by specifying the fields of the entry.

Note A default selection entry is automatically configured during initial startup and cannot be deleted.

Some features of the ATM selection table configuration include

•An entry in the selection table points to a data collection file.

•A selection entry cannot be deleted when data collection is active.

•A selection entry can point to a nonexistent file, in which case the entry is considered inactive.

•One selection entry can apply to more than one type of VC (for example, SVC and PVC).

•If you modify a selection entry list, the new value is used the next time the data collection cycle begins (for example, the next time the ATM accounting collection file swap occurs).

Note These ATM accounting MIB objects are not supported:

— atmAcctngTransmittedClp0Cells (object number 16)
— atmAcctngReceivedClp0Cells (object number 18)
— atmAcctngCallingPartySubAddress (object number 31)
— atmAcctngCalledPartySubAddress (object number 32)
— atmAcctngRecordCrc16 (object number 33)

Examples

Example
Task
DSLAM(config)# atm accounting selection 1
DSLAM(config-acct-sel)# connection-types spvc-originator

Change to ATM accounting selection configuration mode and add the SVPC originator connection type entry to selection entry 1.

DSLAM(config)# atm accounting selection 1
DSLAM(config-acct-sel)# default connection-types

Change to ATM accounting selection configuration mode and reset the connection types for selection entry 1.

DSLAM(config)# atm accounting selection 1
DSLAM(config-acct-sel)# default list

Change to ATM accounting selection configuration mode and configure the selection list to include all objects.

DSLAM(config)# atm accounting selection 1
DSLAM(config-acct-sel)# list 00001000

Change to ATM accounting selection configuration mode and configure the selection list to include object number 20 (atmAcctngTransmitTrafficDescriptorParam1).

DSLAM# show atm accounting

ATM Accounting Info: AdminStatus - UP; OperStatus : UP
Trap Threshold - 90 percent (4500000 bytes)
Interfaces:
File Entry 1: Name acctng_file1
Descr: atm accounting data
Min-age (seconds): 3600
Failed_attempt : C0
Sizes: Active 69 bytes (#records 0); Ready 73 bytes (#records 0)
selection Entry -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - 00.00.10.00
Selection entry 1, connType - F0.00
Active selection -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00
Debug output
Sig API: Err - 0
New_Conn: OK - 0; Err - 0
Rel_Conn: OK - 0; Err - 0
New_Leg: OK - 0; Err - 0
Rel_Leg: OK - 0; Err - 0
New_Party: OK - 0; Err - 0
Rel_Party: OK - 0; Err - 0

Shows the ATM accounting status using the show atm accounting EXEC command.


Configuring ATM Accounting Files

The ATM accounting data being gathered from the configured selection control table should be directed to a specific ATM accounting file. To configure the ATM accounting files and change to ATM accounting file configuration mode, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

atm accounting file filename

Configure the ATM accounting file and change to accounting file configuration mode.

2.

collection-modes {on-release | periodic}

Configure the time to write to the accounting file.

3.

default [min-age]

Reset the ATM accounting file configuration to the default.

4.

description 64_characters

Configure a short description for the ATM accounting file.

5.

enable

Enable ATM accounting for a specific file.

6.

failed-attempts {none | regular | soft}

Configure whether to record failed connection attempts.

7.

interval {60-86400}

Configure the interval for periodic collection, in seconds.

8.

min-age minutes

Configure the ATM accounting file minimum age of the VC.


Note You can configure only one ATM accounting file, and you cannot delete that file.

Examples

Example
Task
DSLAM(config)# atm accounting file acctng_file1
DSLAM(config-acct-file)# collection-mode on-release

Enable ATM accounting file configuration mode for acctng_file1 and reconfigure the collection mode on release of a connection.

DSLAM(config)# atm accounting file acctng_file1
DSLAM(config-acct-file)# default min-age

Enable ATM accounting file configuration mode for acctng_file1 and reconfigure the minimum age to the default value.

DSLAM(config)# atm accounting file acctng_file1
DSLAM(config-acct-file)# description Main accounting file for engineering

Enable ATM accounting file configuration mode for acctng_file1 and configure a short description to be displayed in the show atm accounting file display and the file header.

DSLAM(config)# atm accounting file acctng_file1
DSLAM(config-acct-file)# enable

Enable ATM accounting file configuration mode for acctng_file1.

DSLAM(config)# atm accounting file acctng_file1
DSLAM(config-acct-file)# interval 3600

Enable ATM accounting file configuration mode for acctng_file1 to collect connection data every hour.

DSLAM# show atm accounting
ATM Accounting Info: AdminStatus - UP; OperStatus : UP
Trap Threshold - 90 percent (4500000 bytes)
Interfaces:
File Entry 1: Name acctng_file1
Descr: atm accounting data
Min-age (seconds): 3600
Failed_attempt : C0
Sizes: Active 69 bytes (#records 0); Ready 73 bytes (#records 0)
selection Entry -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00
Active selection -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00

Debug output
Sig API: Err - 0
New_Conn: OK - 0; Err - 0
Rel_Conn: OK - 0; Err - 0
New_Leg: OK - 0; Err - 0
Rel_Leg: OK - 0; Err - 0
New_Party: OK - 0; Err - 0
Rel_Party: OK - 0; Err - 0

This example shows the ATM accounting file status using the show atm accounting privileged EXEC command.


Controlling ATM Accounting Data Collection

To configure ATM accounting collection, use this command in privileged EXEC mode:

Command
Task

atm accounting collection {collect-now | swap} filename

Configure the ATM accounting data collection.


Examples

Example
Task
DSLAM# atm accounting collection collect-now accntg_file1

Collect into the specified file all VCs older than the minimum age VCs and displays the result.

DSLAM# atm accounting collection swap acctng_file1
DSLAM# show atm accounting

ATM Accounting Info: AdminStatus - UP; OperStatus : DOWN
Trap Threshold - 90 percent (4500000 bytes)
Interfaces:
File Entry 1: Name acctng_file1
Descr: atm accounting data
Min-age (seconds): 3600
Failed_attempt : C0
No file buffers initialized
selection Entry -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00
Active selection -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00

Debug output
Sig API: Err - 0
New_Conn: OK - 0; Err - 0
Rel_Conn: OK - 0; Err - 0
New_Leg: OK - 0; Err - 0
Rel_Leg: OK - 0; Err - 0
New_Party: OK - 0; Err - 0
Rel_Party: OK - 0; Err - 0

Swap the buffers corresponding to the file named acctng_file1.


Configuring ATM Accounting SNMP Traps

This section describes configuring the SNMP server and traps for ATM accounting.

Using an SNMP network management system to monitor the status of the ATM accounting file being created requires two tasks:

•Configuring ATM Accounting Trap Generation

•Configuring SNMP Server for ATM Accounting

Configuring ATM Accounting Trap Generation

To configure ATM accounting SNMP traps, use this command in global configuration mode:

Command
Task

atm accounting trap threshold percent-value

Configure the ATM accounting file size threshold to generate an SNMP trap.


Example

This example configures ATM accounting SNMP traps to be sent when the file size reaches 85 percent full and displays the result:

DSLAM(config)# atm accounting trap threshold 85
DSLAM# show atm accounting
ATM Accounting Info: AdminStatus - UP; OperStatus : UP
Trap Threshold - 90 percent (4500000 bytes)
Interfaces:
File Entry 1: Name acctng_file1
Descr: atm accounting data
Min-age (seconds): 3600
Failed_attempt : C0
Sizes: Active 69 bytes (#records 0); Ready 73 bytes (#records 0)
selection Entry -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00
Active selection -
Selection entry 1, subtree - 1.3.6.1.4.1.9.10.18.1.1
Selection entry 1, list - FF.FE.BF.FC
Selection entry 1, connType - F0.00

Debug output
Sig API: Err - 0
New_Conn: OK - 0; Err - 0
Rel_Conn: OK - 0; Err - 0
New_Leg: OK - 0; Err - 0
Rel_Leg: OK - 0; Err - 0
New_Party: OK - 0; Err - 0
Rel_Party: OK - 0; Err - 0

Configuring SNMP Server for ATM Accounting

This section describes configuring the SNMP server ATM accounting traps.

To configure SNMP ATM accounting traps, perform these tasks in global configuration mode:

Step
Command
Task

1.

snmp-server enable traps atm-accounting

Enable SNMP server ATM accounting trap generation.

2.

snmp-server host ip_address [community-string] atm-accounting

Configure the ATM accounting file size threshold to generate an SNMP trap.


Example

This example shows how to enable SNMP server ATM accounting traps and configure the SNMP server host at IP address 1.2.3.4 with community string public for ATM accounting:

DSLAM(config)# snmp-server enable traps atm-accounting
DSLAM(config)# snmp-server host 1.2.3.4 public atm-accounting

Displaying SNMP Server ATM Accounting Configuration

To display the SNMP server ATM accounting configuration, use this privileged EXEC command:

Command
Task

show running-config

Display the SNMP server ATM accounting configuration.


Example

This example shows the SNMP server ATM accounting configuration using the show running-config privileged EXEC command:

DSLAM# show running-config
Building configuration...

Current configuration:
!
version XX.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM
!
!
username dplatz
ip rcmd rcp-enable
ip rcmd remote-host dplatz 171.69.194.9 dplatz
ip rcmd remote-username dplatz
atm template-alias byte_wise 47.9*f8.33...
atm template-alias bit_set 47.9f9(1*0*)88ab...
atm template-alias training 47.1328...
atm accounting enable
atm accounting trap threshold 85
!
<Information Deleted>

no ip classless
atm route 47.0091.8100.0000.0000.0ca7.ce01... ATM3/0/0
snmp-server enable traps chassis-fail
snmp-server enable traps chassis-change
snmp-server enable traps atm-accounting
snmp-server host 1.2.3.4 public atm-accounting
!
line con 0
line aux 0
line vty 0 4
login
!
end

Using TFTP to Copy the ATM Accounting File

After the ATM accounting file is written to DRAM, you must configure TFTP to allow network requests to copy the accounting information to a host for processing. To do this, use this command in global configuration mode:

Command
Task

tftp-server atm-accounting filename ip_access_num

Use TFTP to copy the ATM accounting file to an IP host.


Example

This example allows the TFTP service to copy the ATM accounting file acctng_file1 to the IP access belonging to requesting host number 1:

DSLAM(config)# tftp-server atm-accounting acctng_file1 1

Configuring ATM RMON

This section describes the process you use to configure ATM RMON on the DSLAM.

RMON Overview

The ATM RMON feature allows you to monitor network traffic for fault monitoring or capacity planning. The ATM RMON feature is an extension of an existing, well-known RMON standard and provides high-level per-host and per-conversation statistics in a standards-track MIB similar to these RMON MIBs:

•RMON-1 MIB—RFC 1757

•RMON-2 MIB—RFC 2021 and 2074

The ATM-RMON counter uses the per-VC counters already maintained in the hardware and polled by the software. The ATM RMON agent can report cell traffic statistics by monitoring connection management activity. At connection setup and release time, some ATM-RMON bookkeeping code executes. The amount of information varies, depending on the ATM RMON configuration. The ATM-RMON bookkeeping capability significantly reduces the CPU requirements for ATM-RMON, and allows collecting statistics on several or all of the DSLAM ports at one time.

The ATM-RMON agent uses the 64-bit version of each cell counter if 64-bit counter support is present in the SNMP master-agent library.

Configuring Port Select Groups

RMON used to allow the collection of connection information on a per-interface basis only. ATM RMON allows a group of ports to be configured as an aggregate. The port select group defines this collection unit used by the ATM RMON agent to gather host and matrix connection data. For example, in Figure 14-3, agent 1 includes a port selection group 1 made up of ports.

Figure 14-3 ATM RMON Port Select Group Examples

Before any data collection can begin, you must define an active port select group. To configure and access port select group structures, you can use the command-line interface (CLI) and SNMP modules.

To configure an RMON port selection group, use this command in global configuration mode:

Command
Task

atm rmon portselgrp number {descr label |
host-prio value_1-3 | host-scope value_1-3 |
matrix-prio value_1-3 | matrix-scope value_1-3 |
maxhost number | maxmatrix number |
nostats [label | value_1-3 | value_1-3 | value_1-3 | value_1-3 | number | number | owner] |
owner name}

Configure the ATM RMON port selection group.


Example

This example configures port selection group 7 with these values and displays the result:

•Maximum host count of 500

•Maximum matrix count of 2000

•Host priority of 1

•Owner name "nms 3"

DSLAM(config)# atm rmon portselgrp 7 maxhost 500 maxmatrix 2000 host-prio 1 owner "nms 3"
DSLAM# show atm rmon stats 3
PortSelGrp: 3 Collection: Enabled Drops: 0
CBR/VBR: calls: 0/0 cells: 0 connTime: 0 days 00:00:00
ABR/UBR: calls: 0/0 cells: 0 connTime: 0 days 00:00:00

Adding Interfaces to a Port Select Group

Before the port selection group can begin gathering host and matrix connection information, you must add an interface or group of interfaces to the port selection group.

To add an interface to an ATM RMON port selection group, use these commands, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select the interface to be configured.

2.

atm rmon collect port_sel_group

Configure the interface to an ATM RMON port selection group.


Examples

Example
Task
DSLAM(config)# interface atm 0/0
DSLAM(config-if)# atm rmon collect 6
DSLAM# show atm rmon host 6
PortSelGrp: 6 Collection: Enabled Drops: 0

Add ATM interface 0/0 to ATM RMON port selection group 6 and displays the result.

DSLAM# show atm rmon matrix 6
PortSelGrp: 6 Collection: Enabled Drops: 0

Display the ATM RMON matrix configuration for port selection group 6 using the show atm rmon matrix command from user EXEC mode.

DSLAM# show atm rmon stats 6
PortSelGrp: 6 Collection: Enabled Drops: 0
CBR/VBR: calls: 0/0 cells: 0 connTime: 0 days 00:00:00
ABR/UBR: calls: 0/0 cells: 0 connTime: 0 days 00:00:00

Display the ATM RMON statistics configuration for port selection group 6 using the show atm rmon stats command from user EXEC mode.

DSLAM# show atm rmon status
PortSelGrp: 1 Status: Enabled Hosts: 4/no-max Matrix: 4/no-max
ATM0/0 ATM0/1
PortSelGrp: 2 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max
ATM0/2
PortSelGrp: 3 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max
ATM1/1 ATM1/2
PortSelGrp: 4 Status: Enabled Hosts: 0/1 Matrix: 0/5
ATM0/1
PortSelGrp: 5 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max
ATM0/2
PortSelGrp: 6 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max
ATM0/0
PortSelGrp: 7 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max
ATM0/0
PortSelGrp: 8 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max

PortSelGrp: 9 Status: Enabled Hosts: 0/no-max Matrix: 0/no-max

Display the ATM RMON status for all port selection groups using the show atm rmon status command from user EXEC mode.


Enabling Data Collection

Use the atm rmon enable command to start ATM RMON data collection.

Note If you disable ATM RMON the configuration remains but becomes inactive (similar to using the shutdown command on an interface).

To enable ATM RMON data collection, use this command in global configuration mode:

Command
Task

atm rmon enable

Enable ATM RMON.


Example

This example shows the ATM RMON configuration using the show running-config privileged EXEC command:

DSLAM# show running-config
Building configuration...

Current configuration:
!

<information deleted>

ip default-gateway 172.20.53.206
no ip classless
snmp-server community public RW
snmp-server location racka-cs:2016
snmp-server contact abierman
atm rmon portselgrp 1 host-scope 3 matrix-scope 3
atm rmon portselgrp 2 host-scope 3 matrix-scope 3 descr "router port 2" owner
rubble"
atm rmon portselgrp 3 host-scope 3 matrix-scope 3 descr "test" owner "bam_bam"
atm rmon portselgrp 4 maxhost 1 maxmatrix 5 host-scope 1 descr "no active ports" owner "wilma"
atm rmon portselgrp 5
atm rmon portselgrp 6 matrix-prio 1
atm rmon portselgrp 7 host-scope 3 matrix-scope 3 descr "CPU port" owner "pebbles"
atm rmon portselgrp 8
atm rmon portselgrp 9
atm rmon enable
!
line con 0
exec-timeout 0 0
line aux 0
transport input all
line vty 0 4
login
!
end

Configuring an RMON Event

To configure an RMON event, use this command in global configuration mode:

Command
Task

rmon event number {description name |
log [description name | owner name |
trap community_string] | owner name |
trap community_string}

Configure an RMON event.


Example

This example shows how to configure a generated RMON event and displays the result:

•Named 1

•Description string test

•Owner "nms 3"

•SNMP trap with the community string test

DSLAM(config)# rmon event 1 description test owner nms_3 trap test
DSLAM# show rmon events
Event 1 is active, owned by nms_3
Description is test
Event firing causes trap to community test, last fired 00:00:00

Configuring an RMON Alarm

You can configure RMON alarm generation if any of the configured parameters are met.

To configure RMON alarms, use this command in global configuration mode:

Command
Task

rmon alarm number mib_object interval {absolute rising-threshold value falling-threshold value owner name |
delta rising-threshold value falling-threshold value owner name}

Configure the ATM RMON alarm.


Example

This example configures RMON alarm number 1 to generate an alarm and displays the result:

•If the MIB atmHostHCCells exceed 500

•If each sample, in absolute mode, shows:

–Rising threshold exceeding 10,000

–Falling threshold falling below 1000

•The RMON alarm number 1 sends the alarm to the owner "nms 3"

DSLAM(config)# rmon alarm 1 atmHostInHCCells 500 absolute rising-threshold 10000 falling-threshold 1000 owner "nms 3"
DSLAM# show rmon alarms events
Event 1 is active, owned by nms 3
Description is test
Event firing causes trap to community test, last fired 00:00:00
Alarm table is empty

hometocprevnextglossaryfeedbacksearchhelp

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