HHC Networks delivers optical communication equipment, carrier switches, OTN routers, industrial PoE switches, and smart city infrastructure across Africa and Europe.
HOME / Core Switch Upgrade Solution - HHC Networks & Smart City Solutions
Core Switch Upgrade Solution - HHC Networks & Smart City Solutions [PDF]
Growing traffic demands are putting more pressure on campus core Ethernet switches. Here in the first part of this series, we examine the steps needed to plan for a core switch upgrade.
I am migrating our core switches next weekend and was looking for some advice on the actual move itself. I am moving our current Cisco core stack to a new core stack.
This has led us to look at our core switch, which we currently only have one. We are now looking at upgrading this switch as well as adding a second switch for load balancing and redundancy.
I am looking to replace a single Cisco 3850 serving as our core switch. Currently, there is a single Nexus 9300 connected to it, where our virtualization and storage environments connect via
As this is a replacement upgrade, both switches which are core switches will have the same IP addresses configured on them. So far I have two options that come to mind and would like
We are upgrading our core soon (connect the Classroom) going from a central single 5406 to Merraki utilizing 12 x MS355 split over 3 locations in a Tri-Core format for redundancy.
1) Bring up the new core switch stack or chassis next to or above the current one. 2) Bring the bulk of basic configurations over and map interfaces properly and triple check
My current core switches (2 x Aruba 3810M) are 6 years old and limited in their connection options. Adding in SFP+ modules will not give me enough connections for the servers,
Solved: Hi, I will be updating the firmware on our Meraki switches soon. This will require rebooting of switches. Should I shut down all VMs as best practice or it is not required? Will the VMs
If your hosts have uplinks to to 2 separate switches, they will reboot alternately and therefore the hosts and VM''s should see minimal impact. This assumes your hypervisor pathing is