From: Baety Wayne A 30 SIG BN RS3 (cn) (BaetyWA@schofield.army.mil)
Date: Fri Jul 09 2004 - 15:59:03 GMT-3
Sorry, I didn't even look at what you had configured in the show ouput which
shows the retry intervals and frequencies to be the same. Besides the
situation is different than what I had previously stated. The fact that the
tags on the oam cells are complete different obviates this fact. R9 is
receiving a good reply to it's oam cells as they are sent and r6 is only
receiving a reply to 1/3 of it's oam traffic. If possible I would sniff the
output cells on r6 to see where the drop is occurring. I suspect the switch
is set up as well for oam management on both pvcs (input and ouput) and is
replying to the cells on r9 side at the configured rate but on r6's side at
a different rate. (segment oam enabled on r9's port but not on r6).
One more thing you can do in the interim is to remove oam-pvc manage on r6.
Only one side actually needs to be configured with it anyway, and cisco
devices will automatically reply to an oam loop cell w/o it being actually
configured on a pvc. You can then troubleshoot both sides single handedly.
I would start with disabling oam management on both switch ports. Which I'd
gather is what you are shooting for anyway.
Regards,
WAYNE A. BAETY, Contr, 30SIG BN
MCSE+I, MCSD, MCDBA, CCNP+Voice
Resident System Support Specialist
Office: (808) 655-6761
Cell: (808) 779-3776
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Baety Wayne A 30 SIG BN RS3 (cn)
Sent: Friday, July 09, 2004 8:36 AM
To: 'James'; ccielab@groupstudy.com
Subject: RE: Looking for a quick crash hint on ATM OAM
Well, a quick hint is that your reply oam cells include a time differential
in responses....From r6 to r9 the output rate is about 3 oam outs to 1 in.
Which means r6 is sending them 3 times as fast as r9 is replying.
From r9's perspective you're receiving a reply to each oam ouput almost as
soon as they are sent.
This tells me the physical connection is good but you need to adjust the oam
retry interval on r6 to be slower, or the oam retry interval on r9 to be
faster. (They should be the same)
WAYNE A. BAETY, Contr, 30SIG BN
MCSE+I, MCSD, MCDBA, CCNP+Voice
Resident System Support Specialist
Office: (808) 655-6761
Cell: (808) 779-3776
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
James
Sent: Friday, July 09, 2004 4:11 AM
To: ccielab@groupstudy.com
Subject: Looking for a quick crash hint on ATM OAM
Hi group,
I am having an issue with ATM OAM and was wondering if anyone could assist:
Situation as follows:
R6<----ATM----->R9
pvc0/313 pvc2/314
Circuit was up and running (I could ping both ends, etc) until I configured
OAM
to keep track of pvc, then OAM is shutting the pvc off... Any help is
appreciated. Thanks!
Output from R6:
r6# deb atm oam
ATM OAM cells debugging is on
Displaying all ATM oam data
r6#
02:54:14: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:1 CTag:1671 Tries:0
02:54:14: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:688
02:54:15: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:1 CTag:1672 Tries:1
02:54:15: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:689
02:54:16: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:1 CTag:1673 Tries:2
02:54:16: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:68A
02:54:16: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 0/313 LoopInd:0 CTag:68A
02:54:17: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:2 CTag:1674 Tries:0
02:54:17: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:68B
02:54:18: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:1 CTag:1675 Tries:0
02:54:18: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:68C
02:54:19: ATM OAM(ATM0.1): Timer: VCD#1 VC 0/313 Status:1 CTag:1676 Tries:1
02:54:19: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 0/313 CTag:68D
r6#sh in atm0.1
ATM0.1 is down, line protocol is down
Hardware is ATMizer BX-50
Description: to r9
Internet address is 172.16.56.5/30
MTU 4470 bytes, BW 155520 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM
20 packets input, 2116 bytes
23 packets output, 2176 bytes
1673 OAM cells input, 2760 OAM cells output
r6#sh in atm0
ATM0 is up, line protocol is up
Hardware is ATMizer BX-50
MTU 4470 bytes, sub MTU 4470, BW 155520 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5 AAL3/4, PVC mode
1023 maximum active VCs, 1 current VCCs
VC idle disconnect time: 300 seconds
Last input 00:34:55, 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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1758 packets input, 93372 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
3000 packets output, 164472 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
r6#sh atm pvc
VCD / Peak Avg/Min Burst
Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells
Sts
0.1 1 0 313 PVC SNAP UBR+ 1024 128
DOWN
r6#sh atm pvc 0/313
ATM0.1: VCD: 1, VPI: 0, VCI: 313
UBR+, PeakRate: 1024, Minimum Guaranteed Rate: 128
AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x1
OAM frequency: 10 second(s), OAM retry frequency: 1 second(s), OAM retry
frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Sent
OAM VC status: Up Retry
ILMI VC status: Not Managed
VC is managed by OAM.
InARP frequency: 15 minutes(s)
InPkts: 36, OutPkts: 40, InBytes: 3828, OutBytes: 3956
InPRoc: 36, OutPRoc: 40
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
OAM cells received: 1716
F5 InEndloop: 1716, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 2934
F5 OutEndloop: 2934, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: DOWN, State: NOT_VERIFIED
r6#sh run | be ATM
interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
description to r9
ip address 172.16.56.5 255.255.255.252
pvc 0/313
protocol ip 172.16.56.5
protocol ip 172.16.56.6 broadcast
ubr+ 1024 128
no broadcast
oam-pvc manage
encapsulation aal5snap
!
!
R9 Output:
r9#deb atm oam
ATM OAM cells debugging is on
Displaying all ATM oam data
r9#
02:55:09: ATM OAM(ATM0.1): Timer: VCD#1 VC 2/314 Status:2 CTag:1323 Tries:0
02:55:09: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:52C
02:55:09: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 2/314 LoopInd:1 CTag:6C5
02:55:09: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:6C5
02:55:10: ATM OAM(ATM0.1): Timer: VCD#1 VC 2/314 Status:1 CTag:1324 Tries:0
02:55:10: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:52D
02:55:10: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 2/314 LoopInd:1 CTag:6C6
02:55:10: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:6C6
02:55:11: ATM OAM(ATM0.1): Timer: VCD#1 VC 2/314 Status:1 CTag:1325 Tries:1
02:55:11: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:52E
02:55:11: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 2/314 LoopInd:1 CTag:6C7
02:55:11: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:6C7
02:55:12: ATM OAM(ATM0.1): Timer: VCD#1 VC 2/314 Status:1 CTag:1326 Tries:2
02:55:12: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:52F
02:55:12: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 2/314 LoopInd:0 CTag:52F
02:55:12: ATM OAM LOOP(ATM0.1) I: VCD#1 VC 2/314 LoopInd:1 CTag:6C8
02:55:12: ATM OAM LOOP(ATM0.1) O: VCD#1 VC 2/314 CTag:6C8
r9#sh in atm 0.1
ATM0.1 is down, line protocol is down
Hardware is ATMizer BX-50
Internet address is 172.16.56.6/30
MTU 4470 bytes, BW 155520 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM
21 packets input, 2112 bytes
29 packets output, 2804 bytes
2095 OAM cells input, 3114 OAM cells output
r9#sh in atm0
ATM0 is up, line protocol is up
Hardware is ATMizer BX-50
MTU 4470 bytes, sub MTU 4470, BW 155520 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5 AAL3/4, PVC mode
1023 maximum active VCs, 1 current VCCs
VC idle disconnect time: 300 seconds
Last input 00:17:16, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2119 packets input, 112124 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
3138 packets output, 170732 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
r9#sh atm pvc
VCD / Peak Avg/Min Burst
Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells
Sts
0.1 1 2 314 PVC SNAP UBR+ 1024 128
DOWN
r9#sh atm pvc 2/314
ATM0.1: VCD: 1, VPI: 2, VCI: 314
UBR+, PeakRate: 1024, Minimum Guaranteed Rate: 128
AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x1
OAM frequency: 10 second(s), OAM retry frequency: 1 second(s), OAM retry
frequency: 1 second(s)
OAM up retry count: 3, OAM down retry count: 5
OAM Loopback status: OAM Received
OAM VC state: Up Retry
ILMI VC state: Not Managed
VC is managed by OAM.
InARP frequency: 15 minutes(s)
InPkts: 37, OutPkts: 45, InBytes: 3860, OutBytes: 4516
InPRoc: 37, OutPRoc: 39
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
OAM cells received: 2145
F5 InEndloop: 2145, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0
F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0
OAM cells sent: 3194
F5 OutEndloop: 3194, F5 OutSegloop: 0, F5 OutRDI: 0
F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0
OAM cell drops: 0
Status: DOWN, State: NOT_VERIFIED
r9#sh run | be ATM
interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
ip address 172.16.56.6 255.255.255.252
pvc 2/314
protocol ip 172.16.56.5 broadcast
protocol ip 172.16.56.6
ubr+ 1024 128
no broadcast
oam-pvc manage
encapsulation aal5snap
!
!
-- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:51 GMT-3