08-22-2012 02:28 AM
Hi,
We have several ME-3400 switches in our network. Recently a couple of them have made interfaces go into errordisable mode for reasons we don't quite understand. This happens when the equipment connected to the interface is restarted. Here is the logged error:
.Aug 21 08:49:15 METDST: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to up
.Aug 21 08:49:16 METDST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/3, changed state to up
.Aug 21 08:49:16 METDST: %PM-4-ERR_DISABLE: invalid-policy error detected on Fa0/3, putting Fa0/3 in err-disable state
.Aug 21 08:49:16 METDST: pm_start_recover: invalid operErrReason for Fa0/3
.Aug 21 08:49:17 METDST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/3, changed state to down
.Aug 21 08:49:18 METDST: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
The error indicates that there is some sort of problem with the policy attached to the interface. Here's the interface policy-map:
switch#show policy-map int fast0/3
FastEthernet0/3
Service-policy input: 50Mbit-inn
Class-map: 50Mbit-inn (match-all)
0 packets
Match: access-group 102
police cir 55500000 bc 420000
conform-action transmit
exceed-action drop
conform: 197364 (packets) exceed: 0 (packets)
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Service-policy output: 50Mbit-ut-3p
Class-map: res-voip-out (match-any)
0 packets
Match: ip dscp cs5 (40) ef (46)
Priority
police cir 100000 bc 8000
conform-action transmit
exceed-action drop
conform: 0 (packets) exceed: 0 (packets)
Output Queue:
Max queue-limit default threshold: 48
Tail Packets Drop: 0
Class-map: res-video-out (match-any)
395086 packets
Match: ip dscp cs3 (24)
Match: ip dscp cs3 (24) cs4 (32) af41 (34) af43 (38)
Traffic Shaping
Average Rate Traffic Shaping
CIR 100000 (bps)
Output Queue:
Max queue-limit default threshold: 48
Tail Packets Drop: 0
Class-map: res-internet-out (match-any)
188427 packets
Match: ip dscp default (0)
Traffic Shaping
Average Rate Traffic Shaping
CIR 50000000 (bps)
Queue Limit
queue-limit 544 (packets)
Output Queue:
Max queue-limit default threshold: 544
Tail Packets Drop: 0
Class-map: class-default (match-any)
2 packets
Match: any
Output Queue:
Max queue-limit default threshold: 48
Tail Packets Drop: 0
Traffic Shaping
Average Rate Traffic Shaping
CIR 100000 (bps)
Output Queue:
Max queue-limit default threshold: 48
Tail Packets Drop: 0
switch#
Does this make sense to any of you? We can't seem to find the reason for this, and it is quite annoying.
Thanks in advance!
-Thomas
08-23-2012 01:26 AM
I think I have found the solution to this problem. Certain kinds of network equipment will, however briefly, first connect at 10Mbps when negotiating speed on an interface set to auto/auto. If your service policy is set to 10Mbps or higher, the port will errdisable. This happens because the speed of the interface must be higher than the limits set by the policy.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide