Effect of allowing disjoint networks UCS L2 for existing pod

Servers within our UCS pod existing v2.0 (3 c) need new connection to a network of layer 2 in our datacenter. This network is not accessible to the Juniper switches to the North of our current 6248 fabric of interconnections.

After reading the documentation, it seems that "disjoint networks layer 2" may be the answer. If I understand correctly, we would have cable redundant connections to 6248 unused ports to switches that host this network of layer 2 and follow the guide associated with that vlan L2 these ports.

However, I also understand that I need to tweak the configs for our existing fabric and the fabric port channels B that hosts all the VLAN "normal." I fear that doing so may impact on the network for computers UCS hosts on these networks, or may necessitate a restart/reacknowledgement of existing hosts of UCS. Am I being too pessimistic?

See you soon,.

Paul

Hello Paul,

I would indeed provide a window of failure because you configure VIRTUAL LAN Manager to associate some VLANs for the uplinks on each FI, it will be re-pinn all vEths which will cause a slight disruption in traffic.  According to the degree of sensitivity are your applications they may or may not be affected - I'd do it wrong side of caution and take a maint 1 hour. window to set up and test accordingly.

By default, all them VLANS are allowed on all uplinks.  As soon as you add a VLAN to an uplink channel / port specifically via the VIRTUAL LAN Manager, he gets explicitly cut off the coast of all other channels of uplinks / port for FI.

A great way to check your configuration is once you have everything configured as you see, you vous connecter connect to the UCS CLI interface, "connect nxos" and run 'show int trunk '.  You should see the VLAN on uplinks necessary - with the exception of the VLAN 1, that will be allowed on all uplinks.

Kind regards

Robert

Tags: Cisco DataCenter

Similar Questions

Maybe you are looking for