errorDisabled status on a Cisco Nexus 5020 NX-OS 5.0(2)N2(1)

[matthew.sanders]

Any ideas how to NOT USE errdisable or allow the FCoE switch to put a port / interface / VFC  into an error disabled state?

I do not see any command(s) to NOT use this feature.

thanks

matt

[Prashanth Krishnappa]

You can disable errordisable condition only for certain causes. Here are the options.

F340.24.10-5548-1(config)# no errdisable detect cause ?

  all           Enable error detection on all cases

  inline-power  Enable error disable detection for POE

  link-flap     Enable error disable detection on linkstate-flapping

  loopback      Enable error disable detection on loopback

But you can enable recovery if needed

F340.24.10-5548-1(config)# errdisable recovery cause ?

  all                Enable timer to recover from all causes

  bpduguard          Enable timer to recover from BPDU Guard error disable state

  failed-port-state  Enable timer to recover from stp set port state failure

  inline-power       Enable timer to recover from POE disabled state

  link-flap          Enable timer to recover from linkstate flapping

  pause-rate-limit   Enable timer to recover from pause rate limit error disabled state

  udld               Enable timer to recover from udld error disabled state

F340.24.10-5548-1(config)#

Any particular condition you are after?

[matthew.sanders]

!! THAT's WHAT I WAS LOOKING FOR !!  Can't believe I overlooked using the "no.."

Thank you, it's set now to:

  NO ERRDISABLE DETECT CAUSE ALL

  exit

  copy run start

Done!

Being in DVT all I do is cause errors and failures, so I need it to not mess up a test by disabling an interface, never.