Nexus LACP EtherChannel ports error disabled reason "Error Disabled"

[Bradley Fox]

I have a Nexus 3172T NX-OS v9.3(8) with two ports bundled in an LACP EtherChannel.  The other end of this is a Windows 2019 server with Windows LACP NIC teaming setup.  This has been working fine for quite some time then suddenly I'm finding this server totally locked up (it's a backup server with two 10GB Copper NICs).  After a forced reboot of the server, it's coming back not connected to the network.  I look at the switch and it says both ports are error disabled.  Shut, no shut them and everything is good again for a while.  When I issue the command "sh int status err-disabled" it shows the reason as "Error Disabled".

I'm trying to find out WHY the ports are being disabled.  Is there something else that needs to be turned on to show me the error disabled reason?  On my Catalyst switches with IOS I can see the actual reason.

Scrubbed configs:

interface port-channel2
description To SERVERNAME
switchport access vlan ###
spanning-tree port type edge

interface Ethernet1/1
description To SERVERNAME NIC1
switchport access vlan ###
spanning-tree port type edge
channel-group 2 mode active
no shutdown

interface Ethernet1/2
description To SERVERNAME NIC2
switchport access vlan ###
spanning-tree port type edge
channel-group 2 mode active
no shutdown

[marce1000]

 - Check logs on the nexus too when this happens and or show the related messages , 

 M.

[balaji.bandi]

This not anything do with the switch, you need to see what causing error disabled. post complete log along with below output

show etherchannel 2 summary

show etherchannel 2 summary switch ports

follow other steps :

interface port-channel 2

shutdown

interface Ethernet1/2

shutdown

at this stage we shutdown only port part of port-channel 2

interface port-channel2

no shutdown

post the outcome - is the channel come up ? or still err disabled?

[Bradley Fox]

The EtherChannel is up now; a shut, no shut on e1/1 and e1/2 fixes the issue but I can't figure out why it's being disabled in the first place.

Config requested:

sh port-channel summary interface po2
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
b - BFD Session Wait
S - Switched R - Routed
U - Up (port-channel)
p - Up in delay-lacp mode (member)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port-channel Type Protocol Member Ports
--------------------------------------------------------------------------------
2 Po2(SU) Eth LACP Eth1/1(P) Eth1/2(P)

[balaji.bandi]

check on the windows Server side, rather more focusing on the switch side you will not get much information.

since switch see end device has some loop / or other reasons  and making error disabled - to protect the  switch.

check on Server is there any config change or any updates.

what logs you see on server side ?  ( seen same issue many times, most of the time i see on server side, due to upgrades or updates this caused issue what i have seen my experience)

[MHM Cisco World]

switch# show interface status err-disabled <<- check this command see what make port errdisable

[Bradley Fox]

The result of this command just shows the reason as "Error Disabled" as mentioned in my original post.

[MHM Cisco World]

show spanning tree interface e1/1 & e1/2
share it here if you can ?

[Bradley Fox]

The port type is set to edge which should shut down STP on those ports.  The output is below.

No spanning tree information available for Ethernet1/1

No spanning tree information available for Ethernet1/2

[marce1000 · Accepted solution]

 - As stated use show logging on the Nexus and look for related logs. As far as Windows is concerned use eventvwr , pay attention too system and or networking events (category) and examine accordingly.

 M.

[Bradley Fox]

I didn't have file logging enabled on the switch as we were running Prime, unfortunately, my Prime server bit the dust a couple weeks ago and I haven't had the opportunity to rebuild it.  File logging has been turned on so I can look at logs the next time it happens.  I've already been through event viewer and the Lifecycle Controller logs and there's nothing in there that would indicate any networking issues (that doesn't mean there isn't, just that it's not getting logged).

I'm relatively sure the issue isn't with the switch but when my Catalyst switches put ports into err-disabled mode they tell me why (usually loopback or flapping) instead of just saying "Error Disabled".  This is my only NX-OS switch and it's just different enough from IOS to frustrate me to no end.

[balaji.bandi]

even nexus provide the reason when that occurs and what is the reason.

if you configured error disable recover, it does automatically recover also - but personally i would not do that.

we need to look both the side - to find a fix. ( I am sure you going to put foward steps to logging more details so the incident never occurs again)

[MHM Cisco World]

errdisable recovery interval 60
errdisable recovery cause all 
show interface status errdisable 
then 
no errdisable recovery cause all 

 can you do above steps, please do No errdisbale recovery cause all after you show interface status errdisable. 

[Bradley Fox]

---

@MHM Cisco World wrote:

errdisable recovery interval 60
errdisable recovery cause all 
show interface status errdisable 
then 
no errdisable recovery cause all 

 can you do above steps, please do No errdisbale recovery cause all after you show interface status errdisable. 

---

Since the etherchannel is functional right now, should I do this before it goes into err again or once I see it in err, issue these commands?  I don't want it to recover before I get a chance to look but don't know if this will work once the port has been err-disabled.  Thanks!

[MHM Cisco World]

When port go to errdisable before you shut/no shut try my way the port automatic recovery and you can see what was the reason make port go to errdisable status.

You are welcome