From: Nodir Nazarov (nodir@xxxxxxxxxxxx)
Date: Thu Jan 25 2001 - 17:55:25 GMT-3
Hello, everyone,
I would like to thank you all for your help in solving this still odd
situation. Here is what I found out:
T3 controller was connected to one circuit provider which had cross
connect to another circuit provider which in turn had it from third
provider where it actually fans out to different T1s. After insisting on
double and tripple checks they found "hard loop" somewhere in between.
Again this is exactly what I was told. They released that loop and
everything is now flying !
The telco engineer could not explain me why I could see routers from T3
controller if the circuit was looped somewhere in between (I don't think
he even believed me). Any ideas ?
Thank you all again for very valuable inputs !
Nodir
On Thu, 25 Jan 2001, Rick Burts wrote:
> Are you sure that CDP sees neighbors at both ends.
> Could you send output of show cdp neighbor detail for both.
> I am especially interested in what cdp sees at R1.
> The symptoms kind of sound like a problem with the receive
> pair at R1.
>
> Rick
>
> Rick Burts, CCSI CCIE 4615 burts@mentortech.com
> Mentor Technologies 240-568-6500 ext 6652
> 133 National Business Parkway 240-568-6515 fax
> Annapolis Junction, Md 20701
>
> Chesapeake Network Solutions has now become Mentor Technologies.
> Mentor Technologies is a certified Cisco Training Partner and also
> a Cisco Professional Services partner.
> We offer most of the Cisco training courses.
> We also offer training in Checkpoint Firewall software and
> Fore Systems (now Marconi) and MicroMuse.
> We also provide network consulting services including
> design, management, and problem solving.
> We have 22 CCIEs on our staff.
> We offer the breakthrough VLAB remote access technology for
> access to pratice configuration on real equipment.
>
> On Mon, 22 Jan 2001, Nodir Nazarov wrote:
>
> >
> > Hello, I need help in supposedly simplest configuration.
> >
> > I have 2 sites connected via T1.
> >
> >
> > R1<------------------>R2,
> > 192.168.1.2 192.168.1.1
> >
> > Where R1 has T1 and R2 has T1 channel in DS3. R1 - c2620. R2 - 7206vxr.I
> > have been doing similar scenario many many times and had no problem. This
> > time however I see both serials up/up but I can't ping. When I ping from
> > R2 to R1 this is what I got on R2:
> >
> > 15w3d: IP: s=192.168.1.1 (local), d=192.168.1.2 (Serial1/0/8:0), len 100,
> > sending.
> > 15w3d: IP: s=192.168.1.1 (local), d=192.168.1.2 (Serial1/0/8:0), len 100,
> > sending.
> > 15w3d: IP: s=192.168.1.1 (local), d=192.168.1.2 (Serial1/0/8:0), len 100,
> > sending.
> >
> > When I ask to ping from R1 to R2 I see on R2:
> >
> >
> > 15w3d: IP: s=192.168.1.2 (Serial1/0/8:0), d=192.168.1.1 (Serial1/0/8:0),
> > len 100, rcvd 3
> > 15w3d: IP: s=192.168.1.1 (local), d=192.168.1.2 (Serial1/0/8:0), len 100,
> > sending
> > 15w3d: IP: s=192.168.1.2 (Serial1/0/8:0), d=192.168.1.1 (Serial1/0/8:0),
> > len 100, rcvd 3
> > 15w3d: IP: s=192.168.1.1 (local), d=192.168.1.2 (Serial1/0/8:0), len 100,
> > sending
> >
> > But no success. On both interfaces - no errors at all. I can see the
> > routers through cdp. Encapsulation on both ends - hdlc. No access lists at
> > all, vanilla configuration.
> >
> > I know you will ask details about the other end, but all it has is:
> >
> > int se 0/0
> > ip address 192.168.1.2 255.255.255.0
> >
> > I am afraid to get something like this on the lab. Aren't you ??
> >
> > Nodir
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:44 GMT-3