I found CDP very useful for troubleshooting, interface up-down, you have layer one, if
CDP is enable on both ends, show cdp neighbors will tell you if also layer 2 is
available. Is of no use when back-to-back connections but very handy when connected
thru
a real cloud.
Daniel Cotts wrote:
> The answer is usually on CCO if you can find it. Start with this:
> http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/tr1915.htm
>
> down, down is not good. Take care of the physical connectivity first. up,
> down at least says that you have layer one. Use the show controllers s 0
> (notice the space between the "s" and the "0". In older IOS that needed to
> be there.) to verify the the interface sees the cable. You'll want the same
> encapsulation on both ends. Default is HDLC. Verify that with a show int s0.
> Once you have a link use show cdp neighbor to see the other end. IP doesn't
> have to be working. You may have an addressing problem. Make a list of every
> possible problem that you can imagine. Write down the steps that you think
> will lead to verifying that condition as correct or not. Start
> troubleshooting. If you fix a real problem and yet the link doesn't work -
> continue troubleshooting. There may be two problems. Let me digress ....
> A farmer in Vermont met his friend in the General Store. He said that he had
> a problem. A skunk had wandered into his house. He wanted to get rid of it;
> but didn't want to get sprayed. "No problem!", said his friend. "Skunks love
> carrots. Buy a bunch of carrots. Cut them into small pieces and make a trail
> from the house into the woods. Use a board to make a ramp down your front
> steps. The skunk will start eating the carrots and soon will march right out
> of the house." Several days later they met at the store. "You're right" the
> farmer said,"skunks love carrots." "So you got rid of him", said the friend.
> "No, now I've got two skunks!" was the reply.
> Sometimes you've got two skunks. Believe in your troubleshooting abilities
> and keep going. Good luck.
>
> > -----Original Message-----
> > From: Charles Paver [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, January 28, 2001 6:38 PM
> > To: [EMAIL PROTECTED]
> > Subject: 2502 router problem
> >
> >
> > Hi. Im practicing at home, and am encountering the
> > following problem:
> >
> > I have one 2502 router, has 1 t.ring port and 2 serial
> > ports
> >
> > Also, have one 2513 with 2 aui ports, 2 serial ports.
> >
> > Now, Both of these guys are connected via serial port.
> > serial0 on the 2513 is going to serial1 on the 2502.
> > I can ping the 2502 FROM the 2513 successfully, but
> > cannot ping the 2513 FROM the 2502. Also, I made sure
> > that they are on the same network and using the same
> > subnet.
> > The 2502 router has the dce end of the cable, so I set
> > the clock rate at 64000 and the bandwidth at 64.
> > However, I did not do anything with the 2513!
> >
> > The subnets are identical, and both start with
> > 192.168.0. I also set the telnet password, line vty 0
> > 4, login, password xxxxx.
> >
> > And when I typed in show interface (using the console
> > cable) on the 2502, it says down,down. Both routers
> > are turned on. Im wondering if I can telnet into a
> > router if I have the console port plugged in via
> > hyperterminal simultaneous, while trying to telnet
> > FROM router to router?
> >
> > Now, the 2502 cannot be put on the ethernet, I
> > understand. But should nt I be able to telnet into it
> > from the 2513? I can ping successfully one way! The
> > other way says 0 percent.
> >
> > Thanks!
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - Buy the things you want at great prices.
> > http://auctions.yahoo.com/
> >
> > _________________________________
> > 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]
