A tale of NetApp and Wireshark discoveryPosted: February 13, 2015 | Author: VirtuallyMikeB | Filed under: NetApp, Networking, Storage | Tags: e0M, interface.blocked, NetApp, netapp packet capture, options interface, pktt, pluralsight, storage vmotion requirements, vmotion requirements, wireshark | Leave a comment
–==For those interested, Pluralsight has an excellent video training course called Introduction to Wireshark. I highly recommend Pluralsight as the go-to source for IT video training!==–
I was cleaning up a client’s /etc/rc file yesterday while preparing to move some IP addresses to different interfaces and I noticed they had configured the vMotion network as a VLAN interface on both controllers. This isn’t right because the vMotion network only needs to exist between ESXi hosts – the storage array never touches the traffic. Storage vMotion doesn’t use the vMotion network either. It uses the storage network, whether IP- or FC-based.
I wanted to see if the interface was being used at all and fortunately, NetApp has a command for that. The ifstat command shows the count of frames received and transmitted on any or all interfaces, total bytes for each, and the number of multicasts or broadcasts. So in this case, it looked something like:
NETAPP-A> ifstat VIF-A-79 -- interface VIF-A-79 (22 hours, 57 minutes, 50 seconds) -- RECEIVE Total frames: 150k | Total bytes: 10924k | Multi/broadcast: 21869 TRANSMIT Total frames: 4767k | Total bytes: 7177m | Multi/broadcast: 138 Queue overflows: 0 DEVICE Vlan ID: 79 | Phy Iface: VIF-A