Re: ATM interface and line protocol is up but cannot ping

crisisman · ‎01-24-2004

Dear All,

I am wondering do any of you have any similar experience with ATM.

I am trying to setup an ATM connection to my upstream provider though a local telco ATM network. My router configuration have been verified by my upstream but we are not able to ping to each other.

All my ATM interfaces are up but when I used oam-pvc managed on the interface to my upstream, it went down/down. Even without the oam-pvc managed command, I am not able to ping myself. However, I am able to do that with a physical or logical loopback.

The telco have checked the connection from layer-1 to layer-2 and have found no problem. The telco when doing a physical loopback before the ATM cloud on my upstream is able to see data coming from them but the same cannot be said from my end.

Therefore, I am wondering where can the problem lies? I am using a 7206 running version 12.2 IOS. I have tried using 12.3 but the same result still appear. My upstream and I are configured to each other using a point-to-point setting and I have even forced the mapping of the PVC to IP by adding my own end IP address as the protocol ip under the PVC. But still not able to ping.

I would appreciate any assistance rendered. Thank you.

Vincent

Georg Pauwen · ‎01-24-2004

Hello Vincent,

not sure what your config looks like and if you have the keyword ´broadcast´ in your protocol statement:

protocol ip x.x.x.x broadcast

but if not, try and add it. If that doesn´t help, can you post your configuration ?

Regards,

Georg

crisisman · ‎01-24-2004

Hi Georg,

I have already added the broadcast but still not able to ping myself.

Below is my router config:

interface ATM3/0

description Starhub ATM 15Mbps Connection

bandwidth 15360

no ip address

ip verify unicast reverse-path

no ip redirects

no ip proxy-arp

no ip mroute-cache

load-interval 30

atm framing m23adm

no atm ilmi-keepalive

!

interface ATM3/0.1 point-to-point

description ATM 15Mb Connection to ANC

bandwidth 15360

ip address 203.192.163.142 255.255.255.252

no ip mroute-cache

pvc 1/104

protocol ip 203.192.163.141 broadcast

protocol ip 203.192.163.142 broadcast

vbr-nrt 6625 6625

oam-pvc manage

oam retry 1 1 5

encapsulation aal5snap

!

seilsz · ‎01-25-2004

Have you verified that your framing and cell scrambling settings are correct? Can you post the output from the following commands:

sh atm int a3/0

sh atm pvc 1/104

crisisman · ‎01-25-2004

Zeus>sh atm int a3/0

Interface ATM3/0:

AAL enabled: AAL5 , Maximum VCs: 4096, Current VCCs: 1

Maximum Transmit Channels: 0

Max. Datagram Size: 4528

PLIM Type: DS3 - 45000Kbps, Framing is M23 ADM,

DS3 lbo: short, TX clocking: LINE

Cell-payload scrambling: OFF

2 input, 10116 output, 0 IN fast, 0 OUT fast, 0 out dropVBR-NRT : 6625

Avail bw = 38375

Config. is ACTIVE

Zeus>sh atm int a3/0.1

Interface ATM3/0:

AAL enabled: AAL5 , Maximum VCs: 4096, Current VCCs: 1

Maximum Transmit Channels: 0

Max. Datagram Size: 4528

PLIM Type: DS3 - 45000Kbps, Framing is M23 ADM,

DS3 lbo: short, TX clocking: LINE

Cell-payload scrambling: OFF

2 input, 10117 output, 0 IN fast, 0 OUT fast, 0 out dropVBR-NRT : 6625

Avail bw = 38375

Config. is ACTIVE

Zeus>sh atm pvc 1/104

ATM3/0.1: VCD: 1, VPI: 1, VCI: 104

VBR-NRT, PeakRate: 6625, Average Rate: 6625, Burst Cells: 94

AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x0

OAM frequency: 10 second(s), OAM retry frequency: 5 second(s), OAM retry frequency: 5 second(s)

OAM up retry count: 1, OAM down retry count: 1

OAM Loopback status: OAM Sent

OAM VC state: Not Verified

ILMI VC state: Not Managed

VC is managed by OAM.

InARP frequency: 15 minutes(s)

Transmit priority 2

InPkts: 0, OutPkts: 1132, InBytes: 0, OutBytes: 81684

InPRoc: 0, OutPRoc: 1132

InFast: 0, OutFast: 0, InAS: 0, OutAS: 0

InPktDrops: 0, OutPktDrops: 0

CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0

Out CLP=1 Pkts: 0

OAM cells received: 2

F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0

F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0

OAM cells sent: 8986

F5 OutEndloop: 8986, F5 OutSegloop: 0, F5 OutRDI: 0

F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0

OAM cell drops: 2

Status: DOWN, State: NOT_VERIFIED

Zeus>

The down of pvc 1/104 is due to the oam-pvc manage. Once I remove it, the status will go back to up. Let me show you when that is remove:

Zeus#sh atm pvc 1/104

ATM3/0.1: VCD: 1, VPI: 1, VCI: 104

VBR-NRT, PeakRate: 6625, Average Rate: 6625, Burst Cells: 94

AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x0

OAM frequency: 0 second(s), OAM retry frequency: 5 second(s), OAM retry frequency: 5 second(s)

OAM up retry count: 1, OAM down retry count: 1

OAM Loopback status: OAM Disabled

OAM VC state: Not Managed

ILMI VC state: Not Managed

InARP frequency: 15 minutes(s)

Transmit priority 2

InPkts: 0, OutPkts: 1133, InBytes: 0, OutBytes: 81756

InPRoc: 0, OutPRoc: 1133

InFast: 0, OutFast: 0, InAS: 0, OutAS: 0

InPktDrops: 0, OutPktDrops: 0

CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0

Out CLP=1 Pkts: 0

OAM cells received: 2

F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0

F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0

OAM cells sent: 8994

F5 OutEndloop: 8994, F5 OutSegloop: 0, F5 OutRDI: 0

F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0

OAM cell drops: 2

Status: UP

Regards,

Vincent

marcusl · ‎01-25-2004

Hi,

Are you refering to IP ping or ATM ping? If you haven't done so already I would recommend you to verify the connection using ATM-ping, if responses are received. I've been in a situation where ATM-pings worked just fine but it was impossible to establish a IP-connection. This was due to a problem with the ISP, when I finally got to speak with the right person, they performed a reset in some part of their system and everything was back on track !

Best regards,

/M

crisisman · ‎01-25-2004

Hi Marcus,

How do you do an ATM ping? The ping that I am doing is a IP ping. That is pinging to an IP address.

I have spoken to the technical staff of the telco and they claim that they have even recommissioned the line but still to no avail.

seilsz · ‎01-25-2004

0 input packets and no errors ... I would lean towards a provider issue. Triple verify the VPI/VCI and the encapsulation type. You may also want to try 'no ilmi-enable' under interface ATM3/0.

BTW - You can ATM ping with 'ping atm'.

~Zach

crisisman · ‎01-25-2004

I have even gotten my upstream router config and have send them mine but still nothing.

I am not able to disable the ilmi-enable as that feature is not available with my IOS.

Just wondering ping atm does not provide ATM pinging feature. This is my result:

Zeus#ping atm

Translating "atm"...domain server (204.59.144.222) (204.59.1.222) (165.21.100.88) (165.21.83.88) (203.192.133.3) (203.192.133.4)

% Unrecognized host or address, or protocol not running.

Anyway, ATM ping is not important.

I would just like to enquire is there anything that is missing from my configuration that I need to add in so that the whole link would work. All the Cisco documentations on ATM configuration and troubleshooting that I can find have already been consulted but still I am not able to connect to my upstream through the telco.

Any assistance render would be appreciated.