Port gets LINEPROTO-5-UPDOWN often

Unanswered Question
Apr 21st, 2009
User Badges:

Hi, I have a 3750-24PS-E switch to which I have HID EdgeReader 40 (card access controllers running Linux BusyBox). On one of them, the switch often sends in the logs:


Apr 21 10:43:03 ... 1214: 17w3d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 21 10:43:05 ... 1215: 17w3d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up


without %LINK-3-UPDOWN lines. Just the protocol goes down/up, not the link itself.


The counters for the port shows:


Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards

Fa1/0/6 0 0 0 0 0 0


Port Single-Col Multi-Col Late-Col Excess-Col Carri-Sen Runts Giants

Fa1/0/6 0 0 0 0 0 0 0


and on the linux side, cat /proc/net/dev shows:


Inter-| Receive | Transmit

face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed

lo: 32896 408 0 0 0 0 0 0 32896 408 0 0 0 0 0 0

eth0: 3831171 40278 0 0 0 0 0 0 4189806 40355 0 0 0 0 0 0


I'm at lost at figuring why the protocol goes down like this. Any help would be appreciated.


Thanks.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sylvaing1 Wed, 04/22/2009 - 10:28
User Badges:

Hi, I've activated more logging on the port in question and here is what I got :


Apr 22 13:17:16 ... 1235: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 22 13:17:17 ... 1236: 17w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 22 13:17:18 ... 1237: 17w4d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to down

Apr 22 13:17:19 ... 1238: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 22 13:17:19 ... 1239: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 22 13:17:21 ... 1240: 17w4d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to up

Apr 22 13:17:21 ... 1241: 17w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 22 13:17:29 ... 1242: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 22 13:17:30 ... 1243: 17w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 22 13:17:32 ... 1244: 17w4d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to down

Apr 22 13:17:32 ... 1245: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 22 13:17:32 ... 1246: 17w4d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 22 13:17:34 ... 1247: 17w4d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to up

Apr 22 13:17:34 ... 1248: 17w4d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up


Hopefully, this will trigger a bit more responses ;-)


Thanks.

jedavis Wed, 04/22/2009 - 11:26
User Badges:

I am a little confused. You said that there were no %LINK-3-UPDOWN messages. Yet there they are.


-Jeff

sylvaing1 Wed, 04/22/2009 - 11:39
User Badges:

Well, looks like that one turned out to be a bad example. Ok, how about that one?


Apr 22 14:35:07 ... 1249: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 22 14:35:08 ... 1250: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 22 14:35:09 ... 1251: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 22 14:35:09 ... 1252: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 22 14:35:11 ... 1253: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed


No %LINK-3-UPDOWN messages there...


sylvaing1 Thu, 04/23/2009 - 07:43
User Badges:

I do get %LINK-3-UPDOWN from time to time. Here's the logs for the last 3 hours...


Apr 23 08:42:36 ... 1261: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 08:42:37 ... 1262: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 08:42:39 ... 1263: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 08:42:39 ... 1264: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 08:42:40 ... 1265: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 23 09:52:24 ... 1266: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 09:52:25 ... 1267: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 09:52:27 ... 1268: 17w5d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to down

Apr 23 09:52:27 ... 1269: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 09:52:27 ... 1270: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 09:52:29 ... 1271: 17w5d: %LINK-3-UPDOWN: Interface FastEthernet1/0/6, changed state to up

Apr 23 09:52:29 ... 1272: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 23 09:52:45 ... 1273: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 09:52:46 ... 1274: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 09:52:47 ... 1275: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 09:52:47 ... 1276: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 09:52:49 ... 1277: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 23 10:26:20 ... 1278: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 10:26:21 ... 1279: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 10:26:22 ... 1280: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 10:26:22 ... 1281: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 10:26:23 ... 1282: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 23 11:15:20 ... 1283: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 11:15:21 ... 1284: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 11:15:23 ... 1285: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 11:15:23 ... 1286: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 11:15:24 ... 1287: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up

Apr 23 11:39:00 ... 1288: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from forwarding to disabled

Apr 23 11:39:01 ... 1289: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to down

Apr 23 11:39:03 ... 1290: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from disabled to blocking

Apr 23 11:39:03 ... 1291: 17w5d: %SPANTREE-6-PORT_STATE: Port Fa1/0/6 instance 2108 moving from blocking to forwarding

Apr 23 11:39:04 ... 1292: 17w5d: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/6, changed state to up


Out of 6 times the protocol went down, only once did the link go down.



Leo Laohoo Wed, 04/22/2009 - 14:52
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Try enabling "spanning-tree bpduguard enable" on both ports.

sylvaing1 Wed, 04/22/2009 - 16:01
User Badges:

Both ports? That port is connected to a device (a Linux base card access controller), not another switch.



DialerString_2 Thu, 04/23/2009 - 10:12
User Badges:
  • Bronze, 100 points or more

Try new patch cable if you haven't already.

sylvaing1 Thu, 04/23/2009 - 15:09
User Badges:

Yeah, I already tried that. I switched port today and now it's the new port (Fa1/0/7) that is ill behaving.


The unit at the other end was also changed. The only thing that is the same is the switch itself and the cable run between the patch panel and the unit itself (which is terminated by a RG45 connector connected directly into the unit).

Aaron Richardson Tue, 09/17/2013 - 11:16
User Badges:

I had this same problem with an HID Edgereader.  When I looked up the edgereader, it showed that it  was PoE or DC power available.  The device we had was plugged into the DC power supply.  When I shut PoE off of the port, it resolved the issue.  The HID Edgereader cannot be plugged in both places.

Actions

This Discussion