I'm assuming in your first test that you weren't using subinterfaces and you
had correctly configured the IP address and DLCI. In that scenario, you
must have the remote end also correctly configured or you will not be able
to ping your local interface.
In the second scenario, I just did some testing to shed some light on this.
If you have a frame relay circuit that is successfully speadking to the
frame cloud, your main interface will be up/up. If you configure a
subinterface but do not assign a DLCI, it also will be up/up, but unusable.
If you then configure a DLCI that does not exist, it will go down/down.
That makes me think that when you configured the subinterface, you used a
DLCI that is not being advertised by the frame relay switch.
If you play with it some more and still have problems, perhaps you could
post the relevant portions of the config and let us take a look for you.
HTH,
John
> I am having a problem that I'm hoping someone can shed some light on. I
have
> a 256k frame relay ckt that if i configure for s0 it will show int s0 up
and
> line protocol up but won't allow me to ping int s0's ip address . If I
> configure the frame relay on a sub in s0.1 point-to-point , the s0 will
show
> up and up but the s0.1 is down and down. Any clues??? I'm perplexed
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_______________________________________________________
Send a cool gift with your E-Card
http://www.bluemountain.com/giftcenter/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
