Cisco 2501 ethernet failure? 1

[NettableWalker]

Hi,

I've got a 2501 off eBay for my CCNP and the ethernet interface seems to have packed up after only a few days. Sh Int says up and up, but a ping to 127.0.0.1 fails....

What does this mean? is it knackered?

I've never had anything fail a loopback ping before, is this pretty definitive?

Any help, or locations of rubbish bins to throw it in would be gratefully received.
Cheers

 

[ADB100]

I have just tried this on my DSL router and a ping to 127.0.0.1 fails - I am not sure this should work anyway - 127.0.0.0/8 is a reserved address used internally on end-system IP Hosts isn't it?

Configure the Ethernet interface with a valid IP address on a network with another IP device in the same network/subnet and see if you can ping the hosts.

Andy

 

[jneiberger]

Hellbabe, do you really have 127.0.0.1 configured on your Ethernet interface? As Andy said, this is reserved for loopback addresses and shouldn't be used on a physical interface.

 

[NettableWalker]

No, of course i haven§t got that ip address on an interface.

I merely suggested that i had tried to ping everything connected to the interface and then tried the loopback IP address which at least in the case of windows hosts will test the TCP-IP protocol stack on an interface.

E0 began to work the next day in another setup anyway, and then later stopped working again.

Am i right in thinking that a 2500 E0 interface will not work if connected to a 100MB switch, does it not autosense speed.

 

[jneiberger]

A couple of things:

1. The Ethernet interface on the 2500 is 10/half only; it is not a FastEthernet interface and does not support autonegotiation

2. You must manually configure loopback addresses on the router. Pinging 127.0.0.1 will have no effect unless you have configured that address on a loopback interface.