EMAIL SUPPORT

dclessons@dclessons.com

LOCATION

US

LAB UCS End to End LAB With Service Profile & Template

LAB UCS End to End LAB With Service Profile & Template

LAB UCS End to End LAB With Service Profile & Template

Task :

Provision the ESXi host on UCS System via Service Profile to build VMware Infrastructure for VMs.

Topology

Refer below topology to configure UCS System

Refer Below chart to Understand the Topology requirement

Refer below chart for FI IP Information

EMC Port WWPN'S (For SAN Boot Info)

UCS Server UUID, MAC, WWNN, WWPN,

Solution:

Task 1: Do initial setup of UCS Fabric Interconnects

Fabric A:

//you may have to hit return to see the first prompt

Fabric B:

Task 2: Set Up UCS Connections to Chassis and Verify Chassis and Blade Server Discovery

  1. Access the UCS GUI from the remote desktop.
  2. Verify that the discovery policy is “1-link” (this means that servers in a chassis will be discovered after the first link down to that chassis is configured.

Task 3:- Configure the server ports and uplink ports , Set up FC (SAN) Port Channel Configuration on UCS (up to NEXUS)

  1. Identify fabric A built-in ports 7 and 8 as server ports. This will cause discovery of the two chassis and blades within.

  1. Identify fabric B built-in ports 7 and 8 as server ports to the other fex of the same two chassis.
  2. Verify and enable a single port-channel on Fabric A using UCS ports 11 and 12.
  3. Got to FI –A, Select the LAN Uplink Manager | Select Port 11,12 and Configure them as Uplink port.

  1. Select the Port –channel | Select ID 1 | Put the interface in part of port-channel

  1. Select Fabric B | Right Click to select: Create Port-Channel: Select the Port –channel | Select ID 2 | Put the interface 11, 12 in part of port-channel

  1. Verify that the port-channel and all member ports are up on UCS

  1. Return to the 5548’s and verify that the corresponding port channels show that they are Connected.

  1. Enable Uplink trunking on Fabric A and FI-B. Highlight Fabric A and enable FC Uplink Trunking as shown (ignore [ click Yes on] the warning you will get about this feature causing loss of access to higher number VSANs):

Repeat same step for FI-B also.

  1. Create a SAN port channel from FC ports 1 and 2 on fabric A. Under SAN | SAN Cloud: Fabric A: Select Create FC Port-Channel | Select ID 3 for FI-A, 4 for FI-B. Put the interface in part of port-channel

Repeat Same Step for FI-B

Verification:

Bounce the port channel on the corresponding 5548 to make it all work.

The port channel should come up after a few seconds (try the “sh” below a couple of times): On the 5548 side:

Check same for 5548-B.

Task 4:- Set up VLANs and VSANs on both FI’S

  1. Create a ServerData VLAN 199, ESXmgmt VLAN 198, and VMotion VLAN 932.

Go the the LAN tab | Highlight LAN CLOUD | Right-click and choose Create VLANs | Fill in the form like this: (make sure radio button set to Common/Global) | Click OK and confirm

Repeat steps 2-5 two more times for name/vlan combinations ESXmgmt (198) and VMotion (932). Make sure the radio button set to Common/Global.

Verification for VLAN Creation:

Create a VSAN 77 (use FCOE VLAN 77) on UCS Fabric A / Create a VSAN 88 (use FCOE VLAN 88) on UCS Fabric B. Create VSAN 77 (on FCOE VLAN 77) from the SAN tab as shown. Make sure you choose the radio button for Fabric A as shown (not Common/Global)

When your repeat the entire task on Fabric B use VSAN 88 on FCOE VLAN 88)

Task 5: - Cerate the UUID , WWNN, PWWN , MAC , IP address Pools

  1. Create WWNN Pools
  2. Create PWWN Pools
  3. Create Server pools
  4. Create MAC Pools
  5. Create IP Pools

Create UUID Pools

In UCS Manager, on the Servers tab, navigate to Service Profiles |  root as shown and create an organization named Dclessons.

Navigate to: Pools | root | Sub-Organizations | Dclessons| UUID Suffix Pools | Highlight UUID Suffix Pools and right-click to create a pool.

On the popup, create a name dclessons-uuid Select the radio button Prefix: derived and click Next.


Comment

    You are will be the first.

LEAVE A COMMENT

Please login here to comment.