Navigate to Servers -> Service Profiles -> Root.ģ. Boot Policy: Create a Specific Boot PolicyĢ. MAC Address Assignment: 00:25:B5:XX:XX:XXġ3. How would you like to configure LAN connectivity?: Expertġ1. How would you like to configure SAN storage?: No vHBAs.ĩ. Local Storage: Create a Specific Storage PolicyĨ. Right-click on the Service Profiles node and select Create Service Profile (expert).Ĥ. Once the Server Ports have been configured, the Chassis should now show up in the Equipment tab.Ģ. To confirm that the ports have been assigned as Server Ports, navigate to Equipment -> Fabric Interconnects -> Fabric Interconnect A -> Server Ports and review the list of ports displayed.Ĩ. Right-click on the ports used to connect to the chassis and select Configure as Server port.ħ. Navigate to Equipment -> Fabric Interconnects -> Fabric Interconnect A -> Unconfigured Ports.Ħ. Once the cables are plugged, we will need to configure the ports on the Fabric Interconnect as server ports.ĥ. The left Fabric Extender is primary so unless there is another Fabric Interconnect to be used, the right Fabric Extender does not have to be plugged in.Ĥ. Plug in Fabric Extender port 1 to Fabric Interconnect port 1. Connect the twinax cable from the Fabric Extender behind the UCS-5108 Chassis to the UCS-6120XP Fabric Interconnect.Ģ. Configure the northbound switch port as a trunk port.Ĭonnecting UCS-6120XP Fabric Interconnect to the UCS-5108 Chassis:ġ. Connect the physical cables from the Fabric Interconnect to network switch.ġ8. Right-click on the ports used to connect to the chassis and select Configure as Uplink port.ġ6. Navigate to Equipment à Fabric Interconnects -> Fabric Interconnect A -> Unconfigured Ports.ġ5. Once the VLANs have been added in, configure the uplink Ethernet port used for northbound traffic.ġ4. Navigate to the VLANs tab and create the additional required VLANs.ġ3. Under the General tab under the Actions area, click on LAN Uplinks Manager.ġ2. To add VLANs to the Fabric Interconnect, navigate to Equipment -> Fabric Interconnects -> Fabric Interconnect A.ġ1. service console, vmotion, iSCSI, data traffic).ġ0. Configure VLANs that will be used for ESX (i.e. Under the General tab and under the Actions area, you will see which mode is active.ĩ. End-Host Mode is the default setting but if you would like to validate this, navigate to Equipment -> Fabric Interconnects -> Fabric Interconnect A.Ĩ. Under the Global Policies tab, select the proper Chassis Discovery Policy based on the amount of twinax cables that will be used to connect the UCS-6120XP and the UCS Chassis.ħ. On the right side of the GUI, select Policies.ĥ. Navigate to the Equipment tab and select the Equipment node.Ĥ. No to “create a new cluster” to configure standalone.ĩ.
#BACKUP EXEC 16 TMG 2010 SERIES#
Console into Cisco UCS 6100 Series Fabric Interconnect (Baud rate 9600, Data bits 8, Parity None, Stop bits 1).Ħ. Plug in network cable for management interface (Mgmt0 on 6100).Ģ. Setting up management IP on the 6100 via Console:ġ. To reset Cisco UCS 6100 Series Fabric Interconnect, run the following commands: Please also excuse any typos or mistakes below as I had to copy and paste the content from an Outlook email I sent myself, into notepad then back here and some of the text didn't paste properly. I hope these notes help other professionals out there that are just starting out and I will try to find some time to post a thorough "how to" for a fully redundant setup in the future. The complete build document for the UCS components I wrote for an actual project was 40 pages long complete with proper design of UUID, MAC, WWP pools that requires careful thought based on the client's datacenter requirements and rack layout. Please note that this is just a quick and dirty setup of UCS and should by no means be used for production purposes. These are the notes I took during the first time I got to set up a non redundant UCS with 1 fabric interconnect, 1 IOM and 1 chassis.
0 kommentar(er)
