Cisco 2511 - Ethernet port troubleshooting

You should be using a crossover cable.

Jason0352

Make sure your laptop's ip address is in the same IP subnet as your cisco router.
For example give your laptop an ip address of:
10.10.1.1 with a subnet of 255.255.255.0 and see if you're able to ping the router from your laptop.

Jason0352 wrote: »

Make sure your laptop's ip address is in the same IP subnet as your cisco router.
For example give your laptop an ip address of:
10.10.1.1 with a subnet of 255.255.255.0 and see if you're able to ping the router from your laptop.

yes, laptop ip address is 10.1.1.8 subnet 255.255.255.0

router ip 10.1.1.18 255.255.255.0

i can't ping the router IP from the router itself. so, i guess the problem is in the router itself. i'm hoping that it is not a hardware problem

Since my xp machine can detect if the cable/adapter is plugged or removed from the router, i guess it shouldn't be the hw problem?

Terminal#sh int e0
Ethernet0 is up, line protocol is down
Hardware is Lance, address is 0000.0c47.75ab (bia 0000.0c47.75ab)
Internet address is 10.1.1.18 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 146/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:05:47, output 0:00:07, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3 packets input, 759 bytes, 0 no buffer
Received 3 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
83 packets output, 5235 bytes, 0 underruns
83 output errors, 0 collisions, 3 interface resets, 0 restarts
0 output buffer failures, 0 output buffers swapped out

superkingkong wrote: »

yes, laptop ip address is 10.1.1.8 subnet 255.255.255.0

router ip 10.1.1.18 255.255.255.0

i can't ping the router IP from the router itself. so, i guess the problem is in the router itself. i'm hoping that it is not a hardware problem

Since my xp machine can detect if the cable/adapter is plugged or removed from the router, i guess it shouldn't be the hw problem?

Terminal#sh int e0
Ethernet0 is up, line protocol is down
Hardware is Lance, address is 0000.0c47.75ab (bia 0000.0c47.75ab)
Internet address is 10.1.1.18 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 146/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 4:00:00
Last input 0:05:47, output 0:00:07, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3 packets input, 759 bytes, 0 no buffer
Received 3 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
83 packets output, 5235 bytes, 0 underruns
83 output errors, 0 collisions, 3 interface resets, 0 restarts
0 output buffer failures, 0 output buffers swapped out

Have you tried another interface/Do you have another interface? Do you have the default gateway on your laptop set to your routers interface's IP address?

If you can't ping the IP Address of the interface from within the router, I would suspect an issue with the interface itself. Create a loopback interface, and give it any ip address/mask. Then try to ping that. If you can ping the loopback fine, but still can not ping the e0 interface, I would suspect a hardware issue. If you can't ping the loopback, show us your config.

In fact, show us your config anyway.

chmorin wrote: »

Have you tried another interface/Do you have another interface? Do you have the default gateway on your laptop set to your routers interface's IP address?

If you can't ping the IP Address of the interface from within the router, I would suspect an issue with the interface itself. Create a loopback interface, and give it any ip address/mask. Then try to ping that. If you can ping the loopback fine, but still can not ping the e0 interface, I would suspect a hardware issue. If you can't ping the loopback, show us your config.

In fact, show us your config anyway.

how do i create and ping a loopback? sorry, i'm new.

my config? you mean startup-config? it's almost empty.
here :

sh ver
Cisco Internetwork Operating System Software
IOS (tm) 3000 Software (IGS-J-L), Version 10.3(5), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Tue 08-Aug-95 19:07 by nitin
Image text-base: 0x0302DAD4, data-base: 0x00001000

ROM: System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE
ROM: 3000 Bootstrap Software (IGS-RXBOOT), Version 10.2(8a), RELEASE SOFTWARE (f
c1)

Terminal uptime is 0 minutes
System restarted by reload
System image file is "flash:2511.10.3.5", booted via flash

cisco 2500 (68030) processor (revision D) with 16380K/2048K bytes of memory.
Processor board serial number 02279336
SuperLAT software copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software (copyright 1994 by TGV Inc).
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
Bridging software.
Authorized for Enterprise software set. (0x0)
1 Ethernet/IEEE 802.3 interface.
2 Serial network interfaces.
16 terminal lines.
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read ONLY)

Configuration register is 0x2102

Terminal#sh startup-config
Using 476 out of 32762 bytes
!
version 10.3
service tcp-small-servers
!
hostname Terminal
!
enable secret 5 $1$RSNI$kDpIzFUP0GoPd1Iy29xGz1
enable password san
!
!
interface Ethernet0
ip address 10.1.1.18 255.255.255.0
no ip route-cache
no mop enabled
!
interface Serial0
no ip address
no ip route-cache
shutdown
!
interface Serial1
no ip address
no ip route-cache
shutdown
!
!
!
line con 0
line 1 16
transport input all
line aux 0
transport input all
line vty 0 4
password cisco
login
!
end

Terminal#

superkingkong wrote: »

how do i create and ping a loopback? sorry, i'm new.

To create a loopback, just type int loopback 0 (doesn't have to be 0) from global config mode. Once that is created, just configure an IP address and subnet mask as normal. You don't need to use the no shut command on loopbacks.

Thanks wbosher.

Terminal#config t
Enter configuration commands, one per line. End with CNTL/Z.
Terminal(config)#int loopback 0
Terminal(config-if)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
Terminal(config-if)#ip address 10.1.1.28 255.255.255.0
10.1.1.0 overlaps with Ethernet0
Terminal(config-if)#ip address 10.1.2.28 255.255.255.0
Terminal(config-if)#exit
Terminal(config)#exit
%SYS-5-CONFIG_I: Configured from console by console
Terminal#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Ethernet0 10.1.1.18 YES NVRAM up down
Loopback0 10.1.2.28 YES manual up up
Serial0 unassigned YES not set administratively down down
Serial1 unassigned YES not set administratively down down
Terminal#ping 10.1.2.28
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.28, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Terminal#ping 10.1.1.18
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.18, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

hmmm......

May want to drag an CC*P in on this from somewhere out there. My conclusion is the port is bad, but I am likly missing a detail like I usually do. Time to wait for a professional.

Terminal#sh int e0
Ethernet0 is up, line protocol is down

Line protocol is down, that's probably why you can't ping it. Are you sure you're using a crossover cable? Have you got a switch or something you can plug in to see if that will bring it up?

wbosher wrote: »

Line protocol is down, that's probably why you can't ping it. Are you sure you're using a crossover cable? Have you got a switch or something you can plug in to see if that will bring it up?

Let me try something.

chmorin wrote: »

He is trying to ping the interface. Not the host.

I just read on another forum that if the line protocol is down, you can't even ping the interface locally. I'm at work at the moment, so I can't test it on my own gear, but that's what I've just read.

Well I just ran it in a lab.

Router>
Router>
Router>ena
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int fa0/0
Router(config-if)#ip add
Router(config-if)#ip address 192.168.1.1 255.255.255.0
Router(config-if)#no shut
Router(config-if)#exit
Router(config)#
Router(config)#
Router(config)#
Router(config)#
*Mar  1 00:00:44.631: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state t                     o up
*Mar  1 00:00:45.631: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern                     et0/0, changed state to upexit
Router#
Router#
Router#ping
*Mar  1 00:00:46.859: %SYS-5-CONFIG_I: Configured from console by console192.168                     .1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Router#show ip int brief
Interface                  IP-Address      OK? Method Status                Prot                     ocol
FastEthernet0/0            192.168.1.1     YES manual up                    up                       
FastEthernet0/1            unassigned      YES unset  administratively down down                     
Router#

The line protocol should be up for him, even if it is not plugged into a host.

chmorin wrote: »

The line protocol should be up for him, even if it is not plugged into a host.

That's why I'm wondering if he's using a straight through cable instead of a crossover.

Try unplugging the cable and see what happens.

I need to correct myself, aparently the simulated environment isn't very accurate about this. I turned on my router and tested it out.

The first ping was when I had the interface not pluged in, and the second is when it was plugged into my switch.

Router>
Router>
Router>
Router>ena
Router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#int fa0/0
Router(config-if)#ip add
Router(config-if)#ip address 192.168.1.1 255.255.255.0
Router(config-if)#no shut
Router(config-if)#^Z
Router#
Router#
Router#
00:00:51: %SYS-5-CONFIG_I: Configured from console by console
00:00:53: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
Router#
Router#
Router#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#
Router#
Router#
Router#show ip int brief
Router#show ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            192.168.1.1     YES manual up                    down
Serial0/0                  unassigned      YES unset  administratively down down
Router#show ip int brief
00:01:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
00:01:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            192.168.1.1     YES manual up                    down
Serial0/0                  unassigned      YES unset  administratively down down
Router#show ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            192.168.1.1     YES manual up                    down
Serial0/0                  unassigned      YES unset  administratively down down
Router#
00:01:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router#
Router#
Router#
Router#ping 192.168.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Router#show ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            192.168.1.1     YES manual up                    up  
Serial0/0                  unassigned      YES unset  administratively down down
Router#

You need to have the interface connected to a host for it to work. Make sure you have correct cabling.

Selfmade

sounds like a layer 1 issue to me

I ran into those numerous times in class doing the labbing when other guys were cabling us up, oftentimes we had to set the cables properly, they would just jam in whatever cable and not even look to see what type of cable it was or what device they were using the cable for. Led to a lot of mismatches.

Kind of ridiculous!!!

just know your cable types and test the cable to make sure it's functional, try different ports if you determine the cable is good and then configure them to see if it works.

mikej412

superkingkong wrote: »

On the router side, the LEDs are lighted up on the adapter.

What kind of Transceiver is it? Which LEDs -- all of them or just some of them? Is one of them labeled Link?

Hi mikej412,

The transceiver is a Centrecom.
Yes, the link, power and polarity lighted up when i plug in the utp cable (connected on the other end). When i remove the cable, the link led is down.

I have another cisco 2503 and i've been using the same straight cable and the transceiver successfully.

Guys,

it's a straight cable. I plug in direct from laptop to routers to configure them. So far, all my routers (cisco 2503, 2620xm, 3640) have been successful, except this one (Cisco 2511).

So based on your recommendation, i tried to connect using straight cable from laptop-cisco2950-cisco2511.

When i plug in the cable from cisco 2950 to cisco 2511, both ends led lighted up. On cisco 2950, it shows line up, protocol up.

but on cisco 2511, it shows line up, protocol up initially, then protocol will go down after a while.

On 2950, it port remains up all the time, although cisco 2511 line protocol is down.

When line protocol is up on cisco 2511, i still can't ping neither its own interface (10.1.1.1

nor the laptop and the switch.

i'm not sure what could be the problem.

software error? if it's port problem, how come when i plug-in the cable, the switch was able to detect it and line/protocol went up?

probably if i can upgrade the ios to a later version, problem could be fixed?

well, since the ethernet port is not working now, i'm not able to use it with tftp. I did lots of search on xmodem transfer, all they are saying is xmodem command or copy xmodem flash, which the cisco 2511 are not capable off. no such command on that old ios, 10.3

any help?

thank a lots guys.

So based on your recommendation, i tried to connect using straight cable from laptop-cisco2950-cisco2511.

We want you to console into your router through the console interface, and have a crossover cable connecting the computer to the routers ethernet interface.

well, since the ethernet port is not working now, i'm not able to use it with tftp. I did lots of search on xmodem transfer, all they are saying is xmodem command or copy xmodem flash, which the cisco 2511 are not capable off. no such command on that old ios, 10.3

Can the 2511 use the archive command?

eg: archive tar /xtract tftp://192.168.1.x/filename.tar flash:

There are other tftp commands to. Like copy.

eg: copy tftp://192.168.1.x/filename.x flash:

Hi,

I've connected the laptop to cisco 2511 using crossover cable. i still can't ping its own interface.

Since my ethernet is not working, i can't connect to any tftp at all, since it uses ip address. I think the only way of getting a new ios onto the cisco 2511 is through xmodem. or any other ways?

thanks.

New Findings:

I went into boot mode,
router(boot)#
and i unplugged my transceiver and replug it

my int e0 would go up for about 30secs.
during that 30secs or so, i managed to ping the e0 interface from the router itself. but i still couldn't ping my laptop.

I tried with a cross cable and straight cable. during that 30secs, i can ping the e0 int (10.1.1.1

using both cable but not to my laptop (10.1.1.

superkingkong wrote: »

Hi,

I've connected the laptop to cisco 2511 using crossover cable. i still can't ping its own interface.

Since my ethernet is not working, i can't connect to any tftp at all, since it uses ip address. I think the only way of getting a new ios onto the cisco 2511 is through xmodem. or any other ways?

thanks.

Do you have another Ethernet transceiver to try? It's possible that the AUI port is fine but the transceiver is bad.

And if that isn't the problem, then is there any way that you can connect to another network with a tftp server through one of the serial interfaces? You only have to use the Ethernet interface if you're upgrading the IOS from ROMMON.

alan2308 wrote: »

Do you have another Ethernet transceiver to try? It's possible that the AUI port is fine but the transceiver is bad.

And if that isn't the problem, then is there any way that you can connect to another network with a tftp server through one of the serial interfaces? You only have to use the Ethernet interface if you're upgrading the IOS from ROMMON.

the transceiver is working. I've just used it with my cisco 2503.

how can i connect my serial ports (2511) to my network?

thanks.

superkingkong wrote: »

the transceiver is working. I've just used it with my cisco 2503.

how can i connect my serial ports (2511) to my network?

thanks.

You connect one of the Serial ports to another router. The router itself can act as a tftp server or it can connect to a LAN which as a tftp server.

But, if you don't have another router you can use or you don't have the correct cable, then I guess this is all a moot point.`

alan2308 wrote: »

You connect one of the Serial ports to another router. The router itself can act as a tftp server or it can connect to a LAN which as a tftp server.

But, if you don't have another router you can use or you don't have the correct cable, then I guess this is all a moot point.`

oh, i would love to try. I have another 2503 and i have a dce/dte serial cable.

so, care to guide me through so i can get a new ios in and see if the ethernet problem still persists.

I'm just a beginner. so, i will not know the commands to do it.

Hope you can help ,thanks.

Here's the doc from Cisco. The router to router example transfers the IOS image directly from the flash of a 2500 series router to another 2500 series router, so this should be perfect for you as long as the 2511 has sufficient RAM and Flash for the image that's currently on the 2503.

How To Copy a System Image from One Device to Another - Cisco Systems

hi,

how do i configure the s0 int/serial dce/dte cable?

i tried to assign the ip address to it.

line up but protocol down on both routers

thanks

The router with the DCE end of the cable also needs a clock rate assigned to the serial interface. If you don't know off hand which router has the DCE end, just assign a clock rate on both routers, it'll just be ignored on the one that doesn't need it.

router# conf t
router(config)# int Serial0/0
router(config-if)#clock rate 64000

But instead of 64000, pick the highest supported one. "Clock rate ?" will show you all the supported rates.

alan2308 wrote: »

The router with the DCE end of the cable also needs a clock rate assigned to the serial interface. If you don't know off hand which router has the DCE end, just assign a clock rate on both routers, it'll just be ignored on the one that doesn't need it.

router# conf t
router(config)# int Serial0/0
router(config-if)#clock rate 64000

But instead of 64000, pick the highest supported one. "Clock rate ?" will show you all the supported rates.

just a short question, if it is configured properly, am i supposed to ping the other party's ip address and vice-versa?

thanks.

Yes, both routers should be able to ping one another.