Nexus 9504 & N9K-X9736C-FX= Line Card

[ThariqAli]

I was wondering why the first 17 ports are showing MACSEC failure when we are not running MACSEC?

Eth1/1          1       eth  trunk  down    MACSEC failure           auto(D) 1

Eth1/2          1       eth  access down    MACSEC failure           auto(D) --

Eth1/3          1       eth  access down    MACSEC failure           auto(D) --

Eth1/4          1       eth  access down    MACSEC failure           auto(D) --

Eth1/5          1       eth  access down    MACSEC failure           auto(D) --

Eth1/6          1       eth  access down    MACSEC failure           auto(D) --

Eth1/7          1       eth  access down    MACSEC failure           auto(D) --

Eth1/8          1       eth  access down    MACSEC failure           auto(D) --

Eth1/9          1       eth  access down    MACSEC failure           auto(D) --

Eth1/10         1       eth  access down    MACSEC failure           auto(D) --

Eth1/11         1       eth  access down    MACSEC failure           auto(D) --

Eth1/12         1       eth  access down    MACSEC failure           auto(D) --

Eth1/13         1       eth  access down    MACSEC failure           auto(D) --

Eth1/14         1       eth  access down    MACSEC failure           auto(D) --

Eth1/15         1       eth  access down    MACSEC failure           auto(D) --

Eth1/16         1       eth  access down    MACSEC failure           auto(D) --

Eth1/17         1       eth  access down    MACSEC failure           auto(D) --

Eth1/18         1       eth  access down    XCVR not inserted        auto(D) --

Eth1/19         1       eth  access down    XCVR not inserted        auto(D) --

Eth1/20         1       eth  access down    XCVR not inserted        auto(D) --

Eth1/21         1       eth  access down    XCVR not inserted        auto(D) --

[mlobue]

Hi,

Could you please verify what version of NXOS your N9k is running. The symptoms you are experiencing appear to match a known defect. You can view the defect here https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr42254.

The workaround is to configure "diagnostic bootup level minimum" in global configuration, save the configuration and then reload the switch.

Switch(config)# diagnostic bootup level minimal

Please note that this is just an observation. It is difficult to say for sure that this is the issue you are facing without knowing the current code version your switch is running.