Hardware independent feature (supported in 61 FI)Ī more detailed description can be found in following whitepaper.ĭeploy Layer 2 Disjoint Networks Upstream in End Host ModeĪs per default behavior, UCS will allow all vlans on all uplink ports.Native support in End-Host mode allows simplification of configuration (i.e no need for Switch mode).By default, version 1.4 behavior is preserved (i.e all VLANs present in all uplinks) Feature introduced in UCS version 2.x.This can also be same physical upstream switch but different vlans allowed on different switch ports. Once all the vNICs have the VLAN available to them, exit UCS Manager.įrom UCS End Host Mode perspective, a disjoint L2 (layer 2) is a network design in which UCS connects to different upstream switches (via single port or port-channel) and these upstream switches carry different non-overlapping vlans. Repeat this process for each vNIC that is not bound to a template. K) In the window that opens select the new VLAN. For vNICs bound to templates, this link will be greyed out. J) If the VLAN is not listed then select the vNIC and in the main panel click the Modify VLANs link. If the vNIC is bound to one of the templates modified earlier then the VLAN will be listed under the vNIC.
I) Expand each service profile in turn so that the vNIC for the Chassis/Blade is visible. H) Switch to the servers tab in the Navigation Pane and expand the Service Profiles and the root node, the service profiles for each Chassis/Blade should be visible.
G) In the window that opens add the new VLAN. Expand the vNIC Templates branch of the navigation pane (LAN -> Policies -> root -> vNIC Templates) and select the template which should have the VLAN available.į) On the General tab for each Template click Modify VLANs. Enter the VLAN ID(s), then press the Check Overlap button to ensure there is no conflict with existing configuration and if unique, press OK.ĭ) Check that the newly created VLAN appears in the list of configured VLANs in the navigation pane.Į) If the platform is using vNIC templates then the next step is to add the created VLAN to the required templates. For most situations the Common/Global radio button should be selected to ensure the same configuration is applied to both Fabrics. Right click on the VLANs branch and select Create VLAN(s).Ĭ) Provide a meaningful name for the VLAN, this name can not be changed once saved. In the Navigation pane on the left of the application, select the LAN tab.ī) Expand the navigation tree so that the VLANs branch is visible. The same applies in the VMWare environment.įollow the steps to configure VLAN on UCS:Ī) Open UCS manager. Note that the name of a VLAN is known only within the UCS environment, and outside of the UCS the VLAN is represented by the unique ID.ĭepending on how the UCS infrastructure is configured, VLAN availability for physical hosts may have to be configured on either a port group or individual host basis. You can also create more than one named VLANs with the same VLAN ID.
CONFIGURE IATKOS L2 FOR VMWARE UPDATE
The name that you assign to a VLAN ID adds a layer of abstraction that allows you to globally update all servers associated with service profiles that use the named VLAN.
The VLAN ID is a number that represents that particular VLAN. In UCS each VLAN is identified by a unique ID. This document shows steps required to add VLANs to both UCS and VMware.