cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
777
Views
0
Helpful
1
Replies

UCS ESX5.1 with VNX5300 unable to SAN-boot after installation

nazshuk83
Level 1
Level 1

Hi All,

We have a scenario here, which EMC support claim that they've see this elsewhere.

There is 1 units of CISCO UCS B200 M1 (Palo) with 4 Blades connecting to CISCO Fabric Interconnect 6120XP.

CISCO Fabric Interconnect 612XP has configured with UPLINK to Brocade Switch 5100B.

Meanwhile, VNX5300 is connecting to Brocade Switch 5100B.

Findings:

1. WWN of the Storage and Blades appear on SAN Switches

2. Zoning between 4 Blades and VNX5300 done, initiator of Blades is not appear in UNISPHERE.

3. Have to manually registered initiator for the Blades in the Unisphere

4. Assign LUNS (VNX5300) to the Blades. Blades detected the LUNS.

5. Installed ESX on boot LUNS. But when we wanted to boot up the ESX host, it shows LUN not detected & can’t boot-up the ESX host.

Highlighted issue and concern as below:

1. Why WWN of the Blades not appear on UNISPHERE?

2. Why during ESX boot up, LUN is not detected?

Any suggestion..? Thanks!

Rgds,

Nazri

1 Reply 1

Jeremy Waldrop
Level 4
Level 4

sounds like a zoning issue, WWPNs of vHBAs should show up in the Storage System Connectivity status window in Unisphere. For new hosts in a boot from SAN configuration you have to register them manually because there isn't yet an OS there to auto-register. This can be automated with naviseccli.exe.

Each ESXi host in a boot from SAN configuration will need a unique Storage Group and Boot LUN assigned to the storage group. The boot LUN host ID must match what is configured in UCSM on the boot policy.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: