2x Nexus 5548UP + 2x B22HP FEX modules single-homed connected. IOS 5.2(1)N1(6). Seems to be a cosmetic issue and is an annoyance. I'm unsure whether this is normal FEX behaviour or something specific to these B22HP cards (which is basically a FEX for a HP-UX blade-chassis).
I am constantly getting log entries per the below:
2009 Mar 9 12:10:39 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/15 is down (Administratively down)
2009 Mar 9 12:10:50 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/3 is down (Administratively down)
2009 Mar 9 12:11:00 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/4 is down (Administratively down)
2009 Mar 9 12:11:10 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/5 is down (Administratively down)
2009 Mar 9 12:11:20 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/6 is down (Administratively down)
2009 Mar 9 12:11:30 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/11 is down (Administratively down)
2009 Mar 9 12:11:40 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/12 is down (Administratively down)
2009 Mar 9 12:11:50 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/13 is down (Administratively down)
2009 Mar 9 12:12:00 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/14 is down (Administratively down)
2009 Mar 9 12:12:10 N5K-SW02 %ETHPORT-3-IF_DOWN_ADMIN_DOWN: Interface Ethernet102/1/15 is down (Administratively down)
Note that the above ports are all "administratively down" on purpose and are not changing state. The above repeat constantly about once every 2mins or so for each NIC. If the ports are not administrately down we get similar issues but with a different error message and again every 2 mins.
PLEASE NOTE: These ports are all meant to be down as they relate to blade slots that are empty.
2014 Oct 18 12:05:18 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/14 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:05:28 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/15 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:05:38 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/3 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:05:48 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/4 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:05:58 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/5 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:08 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/6 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:18 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/11 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:28 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/12 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:38 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/13 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:48 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/14 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:06:58 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/15 is down (Error disabled. Reason:ekeying triggered)
2014 Oct 18 12:07:08 N5K-SW01%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/3 is down (Error disabled. Reason:ekeying triggered)
We don't get any repeating log entries for ports that are "up" just the ones that are "down" or "admin down".
Anyone have any ideas? This seems to be cosmetic however since this is a fresh build and as I don't like cutting over to something with constant errors I'd really like this answered.
