Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
The interface is very strainful to my eyes color wise. Themes and/or color selections for fonts would be very much appreciated. I've consulted plenty of other folks who feel the same way.
I'm looking for some out of the box thinking here. Here's the setup:vSphere 5.1 Cluster4 x B200M2 in Chassis A4 x B200M2 in Chassis BChassis A has 2104XP IOM and does not use port-channeled connectivity.Chassis B has 2208XP IOM and DOES use port-chan...
I'm actually seeing the behavior reproduced for two domain controllers for this same Active Directory which reside at another datacenter, with similar blades and configurations (including mixed FIC/blade firmwares). Since that vSphere cluster is two ...
Kinda fascinating, I forgot for a second I had just vMotioned the VM to another host, going back the one its been running on for some time, we see lots more receive over errors. ~ # esxcli network nic stats get -n vmnic2NIC statistics for vmnic2 Pa...
Summary is accurate, I grabbed some stats off one of the hosts. For reference:vmnic0 and 1 are for Management onlyvmnic2 and 3 are for VDSvmnic5 and 6 are vMotion ~ # esxcli network nic stats get -n vmnic0NIC statistics for vmnic0 Packets received:...
Yes, errors show up between the FI and IOM.Errors can be seen on either A side or B side.VDS is set to route based on source port by default. I have also created duplicate port-groups as a test, that have difference active uplinks assigned. Example:P...