Cisco 861 port can't up (with IOS 15.0(1)M4)

[richard.liu]

Dear all:

very simply problem but let CCIE cry............

I got new 861 (no wireless) with IOS 15.0(1)M4

and we found the routing port (WAN port) Fast ethernet 4 .......

step 1. you plug RJ45 Cable into Fast Ethernet 4 and your Notebook(without firewall), and  config it simply:

R(config)# int f 4

R(config-if)# ip add 10.0.0.1 255.255.255.0

and now you can ping 10.0.0.2(your Notebook) , for example, you got "!!!!!"

step 2. you  pull out th RJ45 Cable on Fast Ethernet 4 , and then plug the same RJ45 back into Fast Ethernet 4

R#sh ip int bri

Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet4              10.0.0.1           YES unset  up                      up  

and now you ping 10.0.0.2 , you got "....."

your NB can't ping 10.0.0.1 , neither

step3. you wait 30 mintunes, and now you ping 10.0.0.2 , you got "....."

your NB can't ping 10.0.0.1 , neither

step4. now you use showdown  no showdown

R(config)# int f 4

R(config-if)# sh

R(config-if)# no sh

it's working again!!

and now you can ping 10.0.0.2 , you got "!!!!!"

your NB can ping 10.0.0.1, too !

we try speed 100 , speed 10 , speed auto... duplex full, duplex auto..... all the same problem !!

Can Somebody tell me how to fix this bug?

(It is a bug? Right?)

[Edison Ortiz]

According to the documentation, those are Layer2 ports and the IP address must be placed on the SVI.

http://www.cisco.com/en/US/docs/routers/access/800/860-880-890/software/configuration/guide/vlanconf.html

Edit:

I see you are dealing with the FE4 port. You may have a defective port. I suggest opening a TAC case.

[brantlibrary]

Just purchased a Cisco 861 running same IOS and have the exact same issue on FE4

Everytime the cable is disconnected, the only way to resume connectivity is to do a shutdown and then no shutdown on this interface.

It also will not work hard set to 100 / Full Duplex (or any mix and match), it only will respond on AUTO. Otherwise the port appears to go active, but 2-3 seconds later responds with a PROTCOL Down message.

Did you have any luck with TAC on this ?

[richard.liu]

It's IOS bug!

After change IOS to 15.1(3)  (suggation by Cisco SE , otherwise Cisco SE will help to open a TAC for this!)

It's fix!!

You can try 12.4T series , tha't fix bug, too!

FYI

[brantlibrary]

Richard,

Thanks for the quick reply, I will give that a shot.

Thanks  in advance.