From: pkm@xxxxxxxxxx
Date: Thu Feb 17 2000 - 22:45:42 GMT-3
I went to the ATM class and the teacher told us it was normal. His explanation
was
due to the nature of the ATM interface acting like a serial interface. I hope
it
helps but sure it is not scientific.
Sincerely,
Phillip Moulay
John Garrett wrote:
> When multiple PVCs are defined on an ATM interface, I use a map-list to make
> the remote address reachable. Why can't I ping my own interface address?
>
> I even tried a map statement pointing to my address over the same vc, hoping
to
> go out an come pack for a ping, but that did not work either.
>
> Here is some config:
>
> R1:
>
> interface ATM1/0
> ip address 172.30.1.4 255.255.255.0
> no ip directed-broadcast
> map-group ATM
> atm pvc 401 0 401 aal5snap inarp
> atm pvc 403 0 403 aal5snap
> atm pvc 418 0 418 aal5snap
> atm pvc 424 0 424 aal5snap inarp
>
> map-list ATM
> ip 172.30.1.24 atm-vc 424 broadcast
>
> R2:
>
> interface ATM1/0.129 point-to-point
> ip address 172.30.1.24 255.255.255.0
> atm pvc 424 0 424 aal5snap inarp
>
> map-list ATM
> ip 172.30.1.4 atm-vc 424
>
> In this configuration, R1 can ping 172.30.1.24, but not 172.30.1.4
> just the same, R2 can pint 172.30.1.4, but not 172.30.1.24.
>
> Any Ideas?
>
> John Garrett
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:53 GMT-3