Hi Tim,

This is typical behavior when using Frame Relay in a main serial interface. 
This is because unless you are using a point a point sub interface the 
router relys on map statements or classes to map layer 3 ip addresses to 
layer 2 DLCIs in the frame cloud -- even though you have given the 
interface its ip with 'ip address'. You can get around it at follows :

Scenario 1:

interface serial 0
         ip address 10.1.1.1 255.255.255.0
         encap frame
         frame map ip 10.1.1.1 100                       <-- Will allow you 
to ping yourself
         frame map ip 10.1.1.2 100                       <-- Will allow you 
to ping your neighbor

or

interface serial 0
         no ip address
         encap frame
!
int ser 0.1 point-to-point
         ip address 10.1.1.1 255.255.255.252     <-- Hey its point to 
point, save yerself some IP addresses
         frame interface-dlci 100

Cheers

jim.

At 11:27 PM 12/03/2000 -0800, Tim Ross wrote:
>I have been upgrading a couple 3104 routers (2 serial port, 1 ether, 1 
>BRI) and got them up and running on 11.1 IOS as DTE devices into an AGS+ 
>operating as a frame-switch. The two 3104's can ping each other, but can't 
>ping its own serial port. This is the first time that I have had this 
>happen. I can ping a remote serial port, but not the local serial port. 
>Can someone explain why this happens? Since this, I have upgraded the (2) 
>3104's to IOS ver 12.0.9 and am having worse problems, but am still 
>curious about the local router unable to ping its own ser0 port.
>
>Thanks,
>Tim

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to