Distributed ATM OAM Support (dOAM)

Table Of Contents

Distributed ATM OAM Support (dOAM)

Contents

Restrictions for Distributed ATM OAM Support (dOAM)

Information About Distributed ATM OAM Support (dOAM)

CPU Involvement in OAM Processing

General dOAM Line Card Architecture

How to Configure Distributed ATM OAM Support (dOAM)

Configuring dOAM Processing

Verifying OAM Configuration and State Information in the Line Card

Examples

Troubleshooting dOAM Configuration

Examples

Debugging Transfer of Configuration Information

Examples

Configuration Examples Distributed ATM OAM Support (dOAM)

Distributed ATM OAM Support (dOAM) Configuration: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

atm oam distributed

debug atm oam

debug atm xdr

debug atm xdr atm

show atm oam

Distributed ATM OAM Support (dOAM)

The Distributed ATM OAM Support (dOAM) feature distributes Operations, Administration, and Maintenance (OAM) cell processing to the line cards instead of the Route Processor (RP), thus lowering the CPU load on the RP.

Feature History for the Distributed ATM OAM Support (dOAM) Feature

Release

Modification

12.0(28)S

This feature was introduced.

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Restrictions for Distributed ATM OAM Support (dOAM)

•Information About Distributed ATM OAM Support (dOAM)

•How to Configure Distributed ATM OAM Support (dOAM)

•Configuration Examples Distributed ATM OAM Support (dOAM)

•Additional References

•Command Reference

Restrictions for Distributed ATM OAM Support (dOAM)

The following restrictions apply to the Distributed ATM OAM Support (dOAM) feature:

•This feature supports Engine3 and Engine2 8-port OC-3 ATM line cards on the Cisco 12000 Series Internet Router platform.

•The OAM functionalities supported are as follows:

–F5 segment

–F5 End-to-End

–F5 Alarm Indication Signal (AIS) cells / Remote Defect Indication (RDI) cells

–OAM enhancements made to support Any Transport over MPLS (AToM), including OAM emulation and AIS generation

•This feature does not support Engine0 4xOC3, Engine0 1xOC12, and Engine2 4xOC12 ATM line cards.

•The OAM functionalities that are not distributed to the line card but continued to be handled by the RP are as follows:

–F4 segment

–F4 End-to-End

–OAM F5 CC

Information About Distributed ATM OAM Support (dOAM)

To configure distributed OAM (dOAM) processing, you should understand the following concepts:

•CPU Involvement in OAM Processing

•General dOAM Line Card Architecture

CPU Involvement in OAM Processing

OAM processing on the RPs for a large number of virtual circuits (VCs) is CPU intensive. Most of the CPU processing goes into transferring OAM cells from the line card to the RP and back. Distributing the processing of OAM cells to the line card on the router reduces the load on the CPU.

General dOAM Line Card Architecture

The following schema describes the process of distributing OAM processing to the line cards.

•Transfer of configuration information from the RP to the line card.

The configuration information from the RP is transferred to the line card using eXternal Data Representation (XDR) messages, see Figure 1. XDR is the standard for machine-independent data structures developed by Sun Microsystems. A configuration message is sent whenever OAM is configured or OAM parameters are changed for a VC. Multiple configuration messages received within the time span of the configuration message transfer interval are aggregated in the RP and sent to the line card. The default configuration message transfer interval is 4000 milliseconds (ms).

Figure 1 Transfer of Configuration Information on dOAM Line Cards

•Transfer of counter information from the line card to the route processor.

The OAM counters are transferred from the line card to the RP periodically. The default interval at which the counters are transferred is 2000 ms.

•Transfer of state change information from the line card to the RP.

All OAM state change information in the line card is transferred to the RP on expiry of the notification interval. The notification interval is the time the line card waits to aggregate state change notifications to the RP. The default value is 4000 ms. The state change message in the RP causes the RP to take appropriate actions such as bringing down or bringing up the virtual circuit state.

The work flow of OAM cell processing on the line cards is as follows:

•OAM configuration information is transferred from the RP to the appropriate line card.

•OAM processing based on this configuration happens in the line card.

•Upon an OAM state change, notification is delivered to the RP from the line card.

•According to the state change notification, the RP brings down or brings up a virtual circuit.

How to Configure Distributed ATM OAM Support (dOAM)

See the following sections for the configuration tasks for this feature. Because this feature is enabled by default, the tasks in this list are all optional.

•Configuring dOAM Processing

•Verifying OAM Configuration and State Information in the Line Card

•Troubleshooting dOAM Configuration

Configuring dOAM Processing

By default, distribution of OAM processing is enabled. To modify the configuration and notification intervals, use the atm oam distributed command.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atm interface-number

4. atm oam distributed [config-interval configuration-interval-number notif-interval notification-interval-number]

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface atm interface number
Example:

Router(config-router)# interface atm1/1

Enters interface configuration mode.
Step 4
atm oam distributed [config-interval 
configuration-interval-number notif-interval 
notification-interval-number]
Example:

Router(config-if)# atm oam distributed config-interval 2000 notif-interval 3000
Distributes the OAM processing to the line cards.

•By default, a value of 4000 ms is applied to both the configuration interval and the notification interval.
Verifying OAM Configuration and State Information in the Line Card

This section helps you to verify your OAM configuration and OAM VC state information in the RP and the line card.

To verify the OAM status information in the line card, compare the output of the show atm oam command with that of the show atm pvc vpi/vci command in the RP.

SUMMARY STEPS

1. enable

2. attach slot-number

3. enable

4. show atm oam {atm interface-number vcd-number | auto-detect atm interface-number | stats atm interface-number}

DETAILED STEPS
Command or Action

Purpose
Step 1
enable
Example:

Router> enable
Enables privileged EXEC mode in the RP.

•Enter your password if prompted.
Step 2

attach slot-number
Example:

Router# attach 1

Connects to the line card in slot 1.

Step 3

enable
Example:

LC-Slot1> enable

Enables privileged EXEC mode in the line card.

•Enter your password if prompted.

Step 4

show atm oam {atm interface-number vcd-number | auto-detect atm interface-number | stats atm interface-number}
Example:

LC-Slot1# show atm oam stats atm1

Displays OAM configuration and OAM status information.

•auto-detect atm—Displays the number of VCs in different autodetection and OAM VC states.

•stats atm—Displays the number of VCs in different OAM VC states.
Examples

The following is a sample output from the show atm oam command. It provides OAM configuration and OAM status information.
LC-Slot1# show atm oam atm1 44
ATM1: VCD: 44 VPI: 0, VCI: 64
OAM frequency: 0 second(s) OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Disabled
OAM VC state: Not Managed
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0
F5 InAIS: 0, F5 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0
F5 OutAIS: 0, F5 OutRDI: 0
OAM cell drops: 0
Troubleshooting dOAM Configuration

This section helps you troubleshoot your configuration. To display debugging information about OAM events and OAM cell contents, use the debug atm oam command.

Note Before issuing debug commands, see the "Important Information on Debug Commands" technical note located at this URL: http://www.cisco.com/warp/public/793/access_dial/debug.html.

SUMMARY STEPS

1. enable

2. attach line-card

3. enable

4. debug atm oam {packet interface vcd | event interface vcd}

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode in the RP.

•Enter your password if prompted.
Step 2
Attach slot-number
Example:

Router# attach 1
Connects to the line card in slot 1.
Step 3

enable
Example:

LC-Slot1> enable

Enables privileged EXEC mode in the line card.

•Enter your password if prompted.
Step 4
debug atm oam {packet atm interface-number 
vcd-number | event atm interface-number 
vcd-number}
Example:

LC-Slot1# debug atm oam packet atm1 3
LC-Slot1# debug atm oam event atm1 28
Displays debugging information about ATM OAM distributed processes.

•packet atm—Displays specific debugging information about ATM OAM cell contents.

•event atm—Displays specific debugging information about ATM OAM events.
Examples

The following debug output displays contents of an OAM cell:
LC-Slot1# debug atm oam packet atm1 28
SLOT 1:19:40:11: ATM OAM(ATM1) : VPI/VCI 0/102, type 1, func 8,pti 5
SLOT 1:19:40:11: Count 399 Length 56 
 0x8 0x1C 0x0 0x3 0x0 0x0 0x6 0x6A 0x18 0x1 0x0 0x0 0x0 0x38 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 
0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 
0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x3 0x47
SLOT 1:19:40:11:      
The following debug output displays the OAM events.
LC-Slot1# debug atm oam event atm1 28
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:25, PT 5
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:25, PT 5
SLOT 1:19:37:02: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:37:02: ATM OAM(ATM1): Timer: VC 0/102 Status:2 CTag:67 Tries:0
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:68
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:0 CTag:68, PT 5
Debugging Transfer of Configuration Information

To display debugging information about the transfer of OAM configuration information from the RP to the line card and OAM status change notification from the line card to the RP, use the debug atm xdr command on either the RP or the line card.

SUMMARY STEPS

1. enable

2. debug atm xdr

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

debug atm xdr
Example:

Router# debug atm xdr

Displays debugging information about the transfer of OAM configuration information from the RP to the line card.

Examples

The following output example displays debugging information about the transfer of OAM configuration information from the RP to the line card.

On the Route Processor
2d01h: atm_rp_lc_timer(ATM1/1): Timer exp msg type 1
2d01h: atm_send_rp_lc_xdr(ATM1/1): sending msg ATM_RP_LC_OAM_CONF to slot 1
2d01h: atm_send_rp_lc_xdr(ATM1/1): vcd start 81, end 81 
2d01h: atm_send_rp_lc_xdr: oam manage 1, auto 0, emulation 0 
2d01h: OAM VC State Down Retry 
2d01h: oam_freq 10, retry freq 1, down retry 5, up retry 3
On the Line Card
SLOT 1:19:15:07: atm_lc_msg(ATM1): msg_sub 1, msg 44, slot 1
SLOT 1:19:15:07: atm_lc_oam_conf(ATM1): configuring start_vcd 28, end_vcd 28 
SLOT 1:19:15:07: atm_lc_oam_conf: oam manage 1, auto 0 cell emulation 0 
SLOT 1:19:15:07: oam_vc_state 0,
SLOT 1:19:15:07: oam_freq 15, retry freq 1, down retry 5, up retry 3
SLOT 1:19:15:07: oam ais rdi down 1 ais rate 0
Configuration Examples Distributed ATM OAM Support (dOAM)

This section contains the following configuration example:

•Distributed ATM OAM Support (dOAM) Configuration: Example

Distributed ATM OAM Support (dOAM) Configuration: Example

The following is a sample configuration containing the atm oam distributed command:

Note If the configuration-interval and notification-interval arguments are set to the default, the atm oam distributed command will not be visible in the show run interface interface-number command output.
Router# show run interface atm1/1
Building configuration...
Current configuration : 196 bytes
!
interface ATM1/1
no ip address
no ip directed-broadcast
atm oam distributed conf-interval 6000 notif-interval 2000
no atm enable-ilmi-trap
no atm ilmi-keepalive
end
The following is a sample configuration for the no form of the atm oam distributed command:

Note Use the shutdown or no shutdown command before issuing this command. Disabling distributed OAM processing is not recommended.
Router# show run interface atm1/1
Building configuration...
Current configuration : 160 bytes
!
interface ATM1/1
no ip address
no ip directed-broadcast
no atm oam distributed
no atm enable-ilmi-trap
no atm ilmi-keepalive
end
Additional References

The following sections provide references related to the Distributed ATM OAM Support (dOAM) feature.

Related Documents

Related Topic

Document Title

Sample PVC configurations with and without OAM

Using OAM for PVC Management sample configuration

Configuring ATM OAM traffic reduction

ATM OAM Traffic Reduction, Release 12.0(23)S feature document

Detecting failures when using OAM cells and PVC management

Troubleshooting PVC Failures When Using OAM Cells and PVC Management technical note

Configuring WAN

Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2

WAN command reference, including complete command syntax, command mode, command history, defaults, usage guidelines, and examples

Cisco IOS Wide-Area Networking Command Reference, Release 12.2

Standards

Standards¹

Title

ITU-T Specification I.610 (ITU-T specification for B-ISDN operation and maintenance principles and functions)

I.610 Series I: Integrated Services Digital Network, Maintenance principles

¹Not all supported standards are listed.

MIBs

MIBs

MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFCs

Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—

Technical Assistance

Description

Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml

Command Reference

This section documents new commands introduced by the Distributed ATM OAM Support (dOAM) feature.

•atm oam distributed

•debug atm oam

•debug atm xdr

•debug atm xdr atm

•show atm oam

atm oam distributed

To distribute Operations, Administration, and Maintenance (OAM) processing to the line cards, use the atm oam distributed command in interface configuration mode. Distributing of OAM processing to the line cards is enabled by default. To disable the distribution of OAM processing to the line cards, use the no form of the command.

atm oam distributed [config-interval configuration-interval] [notif-interval notification-interval]
no atm oam distributed [config-interval configuration-interval] [notif-interval notification-interval]
Syntax Description

config-interval configuration-interval

(Optional) Configuration interval, in milliseconds. Range: 1000 to 60000. Default: 4000.

notif-interval notification-interval

(Optional) Notification interval, in milliseconds. Range: 1000 to 60000. Default: 4000.

Defaults

Distributing of OAM processing to the line cards is enabled by default.

Command Modes

Interface configuration mode

Command History

Release

Modification

12.0(28)S

This command was introduced.

Usage Guidelines

By default, the distribution of OAM processing to the line cards is enabled. To modify the configuration and notification intervals, you must provide a configuration interval value and a notification interval value.

If you use the no form of this command, the OAM processing will be done in the Route Processor (RP) rather than on the line card.

Examples

The following example shows distributing OAM processing to the line cards with the configuration and notification intervals both set at the default value of 4000 milliseconds (ms):
Router(config-if)# atm oam distributed
The following example shows distributing OAM processing to the line cards with the configuration interval set to 1000 ms and the notification interval set to 1000 ms:
Router(config-if)# atm oam distributed config-interval 1000 notif-interval 1000
Related Commands

Command

Description

debug atm oam

Displays debugging output for ATM OAM events and OAM packets.

debug atm xdr

Displays debugging information about the transfer of OAM configuration information from the RP to the line card and OAM status change notification from the line card to the RP.

show atm oam

Displays the OAM status information in the line card.

debug atm oam

To turn on debugging output for ATM Operations, Administration, and Maintenance (OAM) distributed processes, use the debug atm oam command in privileged EXEC mode. To turn off debugging output, use the no form of this command.

debug atm oam {event atm interface-number | packet atm interface-number}
no debug atm oam {event atm interface-number | packet atm interface-number}
Syntax Description

event

Debugs ATM OAM events.

packet

Debugs ATM OAM cells.

atm interface-number

ATM interface name.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(28)S

This command was introduced.

Usage Guidelines

Use the event keyword to debug OAM events and the packet keyword to debug OAM cell contents.

Examples

The following example turns on debugging messages for ATM OAM packets:
LC-Slot1# debug atm oam packet atm1 28
SLOT 1:19:40:11: ATM OAM(ATM1) : VPI/VCI 0/102, type 1, func 8,pti 5
SLOT 1:19:40:11: Count 399 Length 56 
 0x8 0x1C 0x0 0x3 0x0 0x0 0x6 0x6A 0x18 0x1 0x0 0x0 0x0 0x38 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 
0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 
0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x6A 0x3 0x47
Table 1 describes the significant fields shown in the display

Table 1 debug atm oam Packet Field Descriptions

Field

Description

0x81C0003

Internal use.

0x0

GFC (4 bits).

0x00

VPI (8 bits).

0x0066

VCI (16 bits).

0xA

Payload type field (PTI) (First 3 bits).

0x1

OAM Fault management cell (4 bits).

0x8

OAM Loopback indicator (4 bits).

0x01

Loopback indicator value (8 bits).

0x00000038

Loopback unique ID, sequence number (32 bits).

0xFF6A

Fs and 6A required in the remaining ATM cell, per UNI3.0.

The following example turns on debugging messages for ATM OAM events:
LC-Slot1# debug atm oam event atm1 28
LC-Slot1#
SLOT 1:19:36:11: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:11: ATM OAM(ATM1): Timer: VC 0/102 Status:2 CTag:5D Tries:0
SLOT 1:19:36:11: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:5E
LC-Slot1#
SLOT 1:19:36:26: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:26: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:5E Tries:0
SLOT 1:19:36:26: atm_lc_oam_setstate(ATM1): VC 0/102: newstate = Down Retry ! This is the 
initial state after configuration
SLOT 1:19:36:26: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:5F
SLOT 1:19:36:27: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:27: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:5F Tries:1
SLOT 1:19:36:27: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:60
SLOT 1:19:36:28: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:28: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:60 Tries:2
SLOT 1:19:36:28: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:61
SLOT 1:19:36:29: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:29: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:61 Tries:3
SLOT 1:19:36:29: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:62
SLOT 1:19:36:30: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:30: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:62 Tries:4
SLOT 1:19:36:30: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:63
SLOT 1:19:36:31: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:31: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:63 Tries:5
SLOT 1:19:36:31: atm_lc_oam_setstate(ATM1): VC 0/102: newstate = Not Verified ! 5 retries 
and no answers ! PVC declared down
SLOT 1:19:36:31: ATM(ATM1): VC 0/102 failed to echo OAM. 6 tries
SLOT 1:19:36:31: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:64
LC-Slot1#
LC-Slot1#
SLOT 1:19:36:46: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:36:46: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:64 Tries:6
SLOT 1:19:36:46: ATM(ATM1): VC 0/102 failed to echo OAM. 7 tries
SLOT 1:19:36:46: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:65
LC-Slot1#
SLOT 1:19:36:58: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:21, PT 5
SLOT 1:19:36:58: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:21, PT 5
SLOT 1:19:36:59: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:22, PT 5
SLOT 1:19:36:59: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:22, PT 5
SLOT 1:19:37:00: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:23, PT 5
SLOT 1:19:37:00: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:23, PT 5
SLOT 1:19:37:01: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:37:01: ATM OAM(ATM1): Timer: VC 0/102 Status:1 CTag:65 Tries:7
SLOT 1:19:37:01: ATM(ATM1): VC 0/102 failed to echo OAM. 8 tries
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:66
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:0 CTag:66, PT 5
SLOT 1:19:37:01: atm_lc_oam_setstate(ATM1): VC 0/102: newstate = Up Retry ! Received a 
response to the loop-back cell
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:24, PT 5
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:24, PT 5
SLOT 1:19:37:01: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:37:01: ATM OAM(ATM1): Timer: VC 0/102 Status:2 CTag:66 Tries:0
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:67
SLOT 1:19:37:01: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:0 CTag:67, PT 5
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:1 CTag:25, PT 5
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:25, PT 5
SLOT 1:19:37:02: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:37:02: ATM OAM(ATM1): Timer: VC 0/102 Status:2 CTag:67 Tries:0
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:68
SLOT 1:19:37:02: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:0 CTag:68, PT 5
SLOT 1:19:37:03: ATM Timer Process(ATM1): VCD 28End Loopbk exp
SLOT 1:19:37:03: ATM OAM(ATM1): Timer: VC 0/102 Status:2 CTag:68 Tries:0
SLOT 1:19:37:03: ATM OAM LOOP(ATM1) O: VC 0/102 CTag:69
SLOT 1:19:37:03: ATM OAM LOOP(ATM1) I: VC 0/102 LoopInd:0 CTag:69, PT 5
SLOT 1:19:37:03: atm_lc_oam_setstate(ATM1): VC 0/102: newstate = Verified ! PVC is 
declared up again
Router# show atm pvc 0/102
VC 0/102 doesn't exist on interface ATM1/0 - cannot display
ATM1/1: VCD: 28, VPI: 0, VCI: 102
UBR, PeakRate: N/A (UBR VC)
AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0
OAM frequency: 15 second(s), OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3
OAM END CC retry frequency: 30 second(s), 
OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3
OAM SEGMENT CC retry frequency: 30 second(s), 
OAM Loopback status: OAM Received
OAM VC state: Verified
ILMI VC state: Not Managed
OAM END CC status: OAM CC Ready
OAM END CC VC state: Verified
OAM SEGMENT CC status: OAM CC Ready
OAM SEGMENT CC VC state: Verified
VC is managed by OAM.
InARP frequency: 15 minutes(s)
InPkts: 0, OutPkts: 0, InBytes: 0, OutBytes: 0
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
Out CLP=1 Pkts: 0
OAM cells received: 53
F5 InEndloop: 53, F5 InSegloop: 0, 
F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 0, F5 InRDI: 0
OAM cells sent: 137
F5 OutEndloop: 137, F5 OutSegloop: 0, 
F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutAIS: 0, F5 OutRDI: 0
OAM cell drops: 0
Status: UP
Table 2 describes the significant field shown in the display.

.

Table 2 debug atm oam Event Field Descriptions

Field

Description

OAM VC state

Displays the current OAM VC state.

•OAM_VC_DOWNRETRY = 0. Loopback has failed. Retry sending loopbacks with retry frequency. VC is still UP.

•OAM_VC_VERIFIED = 1. Loopbacks are successful.

•OAM_VC_NOTVERIFIED = 2. Not verified by loopback, AIS / RDI conditions are cleared.

•OAM_VC_UPRETRY = 3. The previous loopback succeeded. Retry sending loopbacks with retry frequency. VC is DOWN.

•OAM_VC_AISRDI = 4. Received AIS / RDI. Loopbacks are not sent in this state.

Related Commands

Command

Description

atm oam distributed

Distributes the OAM processing to the line cards.

debug atm oam

Displays the debugging output of ATM OAM distributed processes.

debug atm packet

Displays debugging information about OAM cell contents.

debug atm xdr

Displays debugging information about the transfer of OAM configuration information from the RP to the line card and OAM status change notification from the line card to the RP.

show atm oam

Displays the OAM configuration and status information in the line card.

debug atm xdr

To debug the transfer of Operations, Administration, and Maintenance (OAM) configuration information from the Route Processor (RP) to the line card and to debug OAM status change notification from the line card to the RP, use the debug atm xdr command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug atm xdr
no debug atm xdr
Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(28)S

This command was introduced.

Usage Guidelines

Do not use this command in a highly scalable environment. Use this command in the RP.

Examples

The following is sample output of the debug atm xdr command on the RP.
2d01h: atm_rp_lc_timer(ATM1/1): Timer exp msg type 1
2d01h: atm_send_rp_lc_xdr(ATM1/1): sending msg ATM_RP_LC_OAM_CONF to slot 1
2d01h: atm_send_rp_lc_xdr(ATM1/1): vcd start 81, end 81 ! Transferring configuration 
information of PVC with VCD 81
2d01h: atm_send_rp_lc_xdr: oam manage 1, auto 0, emulation 0 
2d01h: OAM VC State Down Retry 
2d01h: oam_freq 10, retry freq 1, down retry 5, up retry 3
Table 3 describes the significant fields shown in the display.

Table 3 debug atm xdr Configuration Field Descriptions

Field

Description

vcd start

Starting VCD of the aggregated configuration message.

oam manage

Displays 1 when OAM is managed, and 0 otherwise.

auto

Displays 1 when autodetection is enabled, and 0 otherwise.

emulation

Displays 1 when OAM emulation is enabled, and 0 otherwise.

OAM VC state

OAM virtual circuit (VC) state information.

oam_freq

OAM loopback frequency, in seconds.

retry freq

OAM loop-back retry frequency, in seconds.

down retry

Down retry count.

up retry

Up retry count.

The following is sample output of the debug atm xdr command on the RP. The OAM status notification example in interface "atm1/1" is given below:
1w2d: atm_rp_distributed: type 50, len 21, slot 1, unit 1 subtype 1
1w2d: atm_rp_distributed(ATM1/1): msg ATM_LC_RP_VC_STATUS, len 21, slot 1, slot_unit 1
1w2d: atm_rp_oam_vc_status(ATM1/1):state 2, num_vc 1
Table 4 describes the significant fields shown in the display.

Table 4 debug atm xdr Notification Field Descriptions

Field

Description

ATM_LC_RP_VC_STATUS

Status notification message.

state

OAM VC state.

num_vc

Number of VCs in the specified state.

Related Commands

Command

Description

atm oam distributed

Distributes the OAM processing to the line cards.

debug atm oam

Displays the debugging output of ATM OAM distributed processes.

debug atm event

Displays debugging information about OAM events.

debug atm packet

Displays debugging information about OAM cell contents.

show atm oam

Displays the OAM status information in the line card.

debug atm xdr atm

To debug the transfer of Operations, Administration, and Maintenance (OAM) configuration information from the Route Processor (RP) to the line card and to debug OAM status change notification from the line card to the RP, use the debug atm xdr atm command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug atm xdr atm interface-number
no debug atm xdr atm interface-number
Syntax Description

atm interface-number

ATM interface name.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(28)S

This command was introduced.

Usage Guidelines

Do not use this command in a highly scalable environment. Use this command in the line card.

Examples

The following is sample output of the debug atm xdr atm command when enabled on the line card.
SLOT 1:19:15:07: atm_lc_msg(ATM1): msg_sub 1, msg 44, slot 1
SLOT 1:19:15:07: atm_lc_oam_conf(ATM1): configuring start_vcd 28, end_vcd 28 ! OAM 
Configuration information for VCs in the range between start_vcd and end_vcd.
SLOT 1:19:15:07: atm_lc_oam_conf: oam manage 1, auto 0 cell emulation 0 ! OAM parameter 
values.
SLOT 1:19:15:07: oam_vc_state 0,
SLOT 1:19:15:07: oam_freq 15, retry freq 1, down retry 5, up retry 3
SLOT 1:19:15:07: oam ais rdi down 1 ais rate 0
LC-Slot1#
Table 5 describes the significant fields shown in the display.

Table 5 debug atm xdr atm Field Descriptions

Field

Description

oam manage

Displays 1 when OAM management is enabled, and 0 otherwise.

auto

Displays 1 when auto-detect is enabled, and 0 otherwise.

cell emulation

Displays 1 when OAM cell emulation is enabled, and 0 otherwise.

Related Commands

Command

Description

atm oam distributed

Distributes the OAM processing to the line cards.

debug atm event

Displays debugging information about OAM events.

debug atm oam

Displays the debugging output of ATM OAM distributed processes.

debug atm packet

Displays the debugging information of OAM cell contents.

show atm oam

Displays the OAM status information in the line card.

show atm oam

To display the Operations, Administration, and Maintenance (OAM) status information in the line card, use the show atm oam command in privileged EXEC mode.

show atm oam {atm interface-number vcd-number | auto-detect atm interface-number | stats atm interface-number}
Syntax Description

atm

Displays the OAM configuration and virtual circuit state information for the interface and VCD supplied.

auto-detect atm

Displays the number of VCs in the different autodetection states on a particular interface.

stats atm

Displays the number of VCs in different OAM VC states on a particular interface.

interface-number

ATM interface number.

vcd-number

VCD value. Range: 1 to 65536.

Defaults

If the interface number is not specified, the details of all the interfaces are displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(28)S

This command was introduced.

Usage Guidelines

Use this command to find out OAM configuration, OAM virtual circuit (VC) state, autodetection states of VCs, and the number of VCs in different OAM states.

Examples

The following sample output displays the number of VCs in different OAM virtual circuit states on the interface "atm1":
LC-Slot1# show atm oam stats atm1
ATM OAM statistics on ATM1
  OAM Loopback statistics:
    DownRetry    : 4
    UpRetry      : 0
    Verified     : 1995
    Not Verified : 12
The following sample output displays the number of VCs in different autodetection and OAM VC states on the interface "atm1":
LC-Slot1# show atm oam auto-detect atm1
ATM OAM statistics on ATM1
  OAM Loopback statistics:
    DownRetry    : 4
    UpRetry      : 0
    Verified     : 1995
    Not Verified : 12
  Auto Detection statistics:
    ATM OAM AUTO DETECT INIT   : 2046 
    ATM OAM SENDING MONITORING : 0
    ATM OAM MONITORING         : 0
  Verified and Not Monitoring: 1995
The following sample output displays OAM configuration and OAM status information:
LC-Slot1# show atm oam atm1 44
ATM1: VCD: 44 VPI: 0, VCI: 64
OAM frequency: 0 second(s) OAM retry frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Disabled
OAM VC state: Not Managed
OAM cells received: 0
F5 InEndloop: 0, F5 InSegloop: 0
F5 InAIS: 0, F5 InRDI: 0
OAM cells sent: 0
F5 OutEndloop: 0, F5 OutSegloop: 0
F5 OutAIS: 0, F5 OutRDI: 0
OAM cell drops: 0
Table 6 show atm oam Field Descriptions

Field

Description

OAM frequency

The frequency (in seconds) at which F5 command loop back cells are generated.

OAM retry frequency

The frequency (in seconds) at which end-to-end F5 loopback cells should be transmitted when a change in UP/DOWN state is being verified. For example, if a permanent virtual circuit (PVC) is up and a loopback cell response is not received after the frequency specified using the oam-pvc command, loopback cells are sent at the retry-frequency to verify whether or not the PVC is down.

OAM up retry count

Number of consecutive end-to-end F5 OAM loopback cell responses that must be received in order to change a PVC state to up.

OAM down retry count

Number of consecutive end-to-end F5 OAM loopback cell responses that are not received in order to change a PVC state to down.

OAM Loopback status

Status of end-to-end F5 OAM loopback cell generation for this VC. This field will have one of the following values:

•OAM Disabled—End-to-End F5 OAM loopback cell generation is disabled.

•OAM Sent—OAM cell was sent.

•OAM Received—OAM cell was received.

•OAM Failed—OAM reply was not received within the frequency period or contained a bad correlation tag.

OAM VC state

This field will have one of the following states for this VC:

•AIS/RDI—The VC received Alarm Indication Signal (AIS) cells / Remote Defect Indication (RDI) cells. End-to-end F5 OAM loopback cells are not sent in this state.

•Down Retry—An OAM loopback failed. End-to-end F5 OAM loopback cells are sent at retry frequency to verify that the VC is really down. After the specified number of unsuccessful retries, the VC goes to the Not Verified state.

•Not Managed—VC is not being managed by OAM.

•Not Verified—VC has not been verified by end-to-end F5 OAM loopback cells. AIS and RDI conditions are cleared.

•Up Retry—An OAM loopback was successful. End-to-end F5 OAM loopback cells are sent at retry frequency to verify that the VC is really up. After the specified number of successive and successful loopback retries, the VC goes to the Verified state.

•Verified—Loopbacks are successful. AIS/RDI cell was not received.

OAM cells received

Total number of OAM cells received on this virtual circuit.

F5 InEndloop

Number of end-to-end F5 OAM loopback cells received.

F5 InSegloop

Number of segment F5 OAM loopback cells received.

F5 InAIS

Number of F5 OAM AIS cells received.

F5 InRDI

Number of F5 OAM RDI cells received.

F5 OutEndloop

Number of end-to-end F5 OAM loopback cells sent.

F5 OutSegloop

Number of segment F5 OAM loopback cells sent.

F5 OutRDI

Number of F5 OAM RDI cells sent.

OAM cell drops

Number of OAM cells dropped (or flushed).

Related Commands

Command

Description

atm oam distributed

Distributes the OAM processing to the line cards.

debug atm oam

Displays the debugging output of ATM OAM distributed processes.

debug atm xdr

Displays debugging information about the transfer of OAM configuration information from the RP to the line card and OAM status change notification from the line card to the RP.

show atm oam auto-detect

Displays the number of number of VCs in different autodetection states.

show atm pvc

Displays all ATM PVCs and traffic information.

show atm vc summary

Displays the number of VCs in different OAM VC states on a particular interface.

Copyright © 2004 Cisco Systems, Inc. All rights reserved.

Cisco IOS Software Releases 12.0 S

Distributed ATM OAM Support (dOAM)

Hierarchical Navigation

Downloads

Table Of Contents

Distributed ATM OAM Support (dOAM)

Contents

Restrictions for Distributed ATM OAM Support (dOAM)

Information About Distributed ATM OAM Support (dOAM)

CPU Involvement in OAM Processing

General dOAM Line Card Architecture

How to Configure Distributed ATM OAM Support (dOAM)

Configuring dOAM Processing

SUMMARY STEPS

DETAILED STEPS

Verifying OAM Configuration and State Information in the Line Card

SUMMARY STEPS

DETAILED STEPS

Examples

Troubleshooting dOAM Configuration

SUMMARY STEPS

DETAILED STEPS

Examples

Debugging Transfer of Configuration Information

SUMMARY STEPS

DETAILED STEPS

Examples

Configuration Examples Distributed ATM OAM Support (dOAM)

Distributed ATM OAM Support (dOAM) Configuration: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

atm oam distributed

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug atm oam

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug atm xdr

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

debug atm xdr atm

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show atm oam

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

Copyright © 2004 Cisco Systems, Inc. All rights reserved.

Programs

Programs

Programs

Programs