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.
All,I wanted to throw an issue that we are experiencing out there to the community to see if anyone else is experiencing similar issues. Note, Layer 3 switching not enabled at this time on the stack.Environment:In our environment, we have a stack of...
I believe we got to the bottom of the issue. We tracked down all of the small "5-port non-Meraki switches" that were being used and disconnected them from the network. Fingers crossed, it's been about a week now without any issues. vMotioning has ...
That's certainly what it's looking like. The forwarding tables aren't updating properly both with VM's and now standalone devices. Rebooting the entire switch stack fixes the issue; however, eventually the issue comes back. I should mention that I ha...
Just throwing out an update. Originally I had thought that this was just related to our ESX teamed NIC's. I updated the iDrac firmware on one of my ESX hosts and after rebooting the iDrac interface I can no longer communicate with it's IP address f...
@calebbaker,They are not aggregated. We are using "Route Based on Originating Port ID" for our load balancing method. We don't have a need for using the "Route Based on IP Hash" algorithm as we would be adding more complexity to the environment tha...
@Philip D'Ath,I have had customers running in this configuration before as well without any issues. That's why I find it a bit perplexing.All switches are running FW 10.40.
