As far as IOS, the 3640 is most likely the culprit. This is one of the few
routers you "cannot" just dump Enterprise in & expect it to work with
whatever module you install.
Phil
----- Original Message -----
From: "David Sanderson" <[EMAIL PROTECTED]>
To: "'Circusnuts'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, January 10, 2001 11:42 PM
Subject: RE: PING TROUBLE
> Thank you, yes it was the 1602. I had them setup back to back to test
before
> sending the 1602 offsite. Even though I could ping from the 3640 to the
> 1602(and to both from the 1602) I could not ping the 3640 from the 3640
> until I added a route statement on the 1602. It's still a little puzzling.
> The 3640 must've had the route already because there is another
> interface(previously configured) on it in the same network 12.9.2.1 You
> also mentioned the IOS and maybe that had something to do with it; 1602 is
> I0S 12 and the 3640 is IOS 11.2(16)
>
> -----Original Message-----
> From: Circusnuts [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 09, 2001 3:37 PM
> To: hao vu; 'David Sanderson'; [EMAIL PROTECTED]
> Subject: Re: PING TROUBLE
>
> Ahh- this is a very hard thing to imagine. You are not not able to Ping
the
> 3600 interface because you're not able to get the correct response from
the
> 1600. Ping the 1600 from inside the 1600, then Ping the 3600 from the
1600.
> Your times will be higher with when Ping-ing the very router you are in.
> The return information comes from the opposing router. I would begin to
> investigate the 1600 as more the culprit, than the 3600. Of course this
> could be an IOS thing too. In production, your setup would almost never
> occur. Say with Frame Relay, these routers would be mapped in the Telco
> switch, in order to return a Ping on their own interface.
>
> Confused yet :-)
> Phil
>
> ----- Original Message -----
> From: "hao vu" <[EMAIL PROTECTED]>
> To: "'David Sanderson'" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, January 09, 2001 11:25 PM
> Subject: RE: PING TROUBLE
>
>
> > You might want to turn on debug then do the ping again.
> >
> > HTH
> >
> > HV
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > David Sanderson
> > Sent: Tuesday, January 09, 2001 4:12 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: PING TROUBLE
> >
> >
> > I have two routers, 3640 and 1602 both with T1 WIC's w/built in DSU/CSU.
> > They are connected back to back. The 3640 int s1/1 ip address is
> > 12.10.2.97/29 and the 1602 is 12.10.2.98/29. I can ping from the 1602
> both
> > 12.10.2.97 and 12.10.2.98 and from the 3600 I can ping the 1602 -
> > 12.10.2.98. But why can't I ping the 3640 interface from the 3640
> > (telnetted onto it)? I can't ping 12.10.2.97 from the 3640. I don't
see
> > any redirect or no icmp type configs to stop the ping. Any ideas?
Thanks
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>
> _________________________________
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
