Port channel e2a and e2c - Vlan for SVM, CIFS, NFS - Failover enabled
Access Port e2b - vlan iSCSIA - no failover, uses MPIO for HA
Access Port e2d - vlan iSCSIB - no failover, uses MPIO for HA
In this configuration, the iSCSI LIFs for node na2-01 are unreachable. If I migrate any LIF (CIFS/NFS/SVM) over to na2-01 the iSCSI LIFs are reachable again. Would like to know why the port channel LIFs location would have an affect on the non-port channel LIFs reachability?
I would put e2a/e2b/e2c/e2d into a port channel (multimode_lacp) TAG all your VLANS, including iSCSI-A and iSCSI-B Configure the switch to use an ACTIVE port-channel -> this indicates LACP (DO NOT use mode on!) Also, if possible, on the port channel at the switch, be sure to set spanning-tree to port type edge trunk (if cisco) Your data LIFs should work as long as the switch is configured. It might be helpful to post the following: system node run -node * options cdpd.enable on system node run -node * options lldp.enable on (wait 3 full minutes) set diag network device-discovery show -port e2* -sort-by protocol net int show -vserver na2-svm1 -field failover-policy, broadcast-domain
LLDP is probably not enabled on switch and not sure CDP is on for the access ports (iSCSI). Will get network team to look at that in the morning. All IPs are pingable when everything is on their home node (Steady state). It is just when the port channel interfaces are not. As long as I move one back to node 1, the iSCSI IPs become reachable. Does not seem logical why one would affect the other. The network is Cisco ACI. All ports look healthy in the unreachable state. Best practice for iSCSI is not use a port-channel.
NetApp did not have a default route for the iSCSI network, so it decided that it would send that traffic out one of the default routes which was over the port channel. The Cisco ACI fabric thought it was ok to route any subnet no matter what vlan it came in on. Looks like an issue with both ACI and NetApp.