Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The ...Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The cluster port e0b on node Node01 has gone down unexpectedly. Wed Nov 15 18:25:34 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b.
Node port down as seen in sysconfig -a: Switch port down as seen in the switch log: 0/1 Enable 10G Full 10G Full Up Enable Enable long 0/2 Enable 10G Full Down Enable Enable long 0/3 Enable 10G Full 1...Node port down as seen in sysconfig -a: Switch port down as seen in the switch log: 0/1 Enable 10G Full 10G Full Up Enable Enable long 0/2 Enable 10G Full Down Enable Enable long 0/3 Enable 10G Full 10G Full Up Enable Enable long 0/4 Enable 10G Full 10G Full Up Enable Enable long Reseat of the cable between the node port and the switch port brings the link up but port goes down soon after. There is no free switch port available to move the cable to
12/4/2024 12:06:04 node1 ALERT vifmgr.lifdown.noports: LIF N2_NAS (on virtual server 3), IP address xxx.xxx.xxx.2, currently cannot be hosted on node node1, port a0a, or any of its failover targets, a...12/4/2024 12:06:04 node1 ALERT vifmgr.lifdown.noports: LIF N2_NAS (on virtual server 3), IP address xxx.xxx.xxx.2, currently cannot be hosted on node node1, port a0a, or any of its failover targets, and is being marked as down. 12/4/2024 12:06:04 node1 ALERT vifmgr.lifdown.noports: LIF N1_NAS (on virtual server 3), IP address xxx.xxx.xxx.1, currently cannot be hosted on node node1, port a0a, or any of its failover targets, and is being marked as down.