UCS C Series SAN Boot

gofianto.phin · ‎07-11-2013

Hi All,

How to configure SAN Boot on the UCS C Series platform ?

On B Series, we can configure the boot order from vHBA, but on the UCS C Series I found nothing.

The C Series SAN boot had being enabled and also the boot target was configured on the vHBA properties, but the C Series can't boot from SAN

Attached are the detailed of the configuration on C Series

Please help, if you have C Series boot from SAN succesfully

Thanks,

Gofi

padramas · ‎07-12-2013

Hello,

Does it flogi into upstream switch ?

Can you please share more information about upstream switch FCoE configuration ?

Padma

gofianto.phin · ‎07-14-2013

Hi Padma,

Yes, that will be the flogi into the upstream switch.

Below are the configurations of Nexus 5K, while I used 2 N5k as the upstream FCoE switch

N5K1# sh run int vfc113

!Command: show running-config interface vfc113

!Time: Wed Jun 17 03:21:56 2009

version 5.2(1)N1(5)

interface vfc113

bind interface Ethernet113/1/1

switchport trunk allowed vsan 10

no shutdown

N5K1# sh run int eth113/1/1

!Command: show running-config interface Ethernet113/1/1

!Time: Wed Jun 17 03:22:05 2009

version 5.2(1)N1(5)

interface Ethernet113/1/1

switchport mode trunk

switchport trunk allowed vlan 10,120,125,130,135,200-201

N5K1# sh run | sec fex

feature fex

fex 113

pinning max-links 1

description "FEX0113"

fcoe

fex 123

pinning max-links 1

description "FEX0123"

N5K1# sh feature | i fcoe

fcoe 1 enabled

fcoe-npv 1 disabled

***************************************************************************************************************

N5K2# sh run int vfc123

!Command: show running-config interface vfc123

!Time: Wed Jun 17 03:24:12 2009

version 5.2(1)N1(5)

interface vfc123

bind interface Ethernet123/1/1

switchport trunk allowed vsan 20

no shutdown

N5K2# sh run int eth123/1/1

!Command: show running-config interface Ethernet123/1/1

!Time: Wed Jun 17 03:24:29 2009

version 5.2(1)N1(5)

interface Ethernet123/1/1

switchport mode trunk

switchport trunk allowed vlan 20,120,125,130,135,200-201

N5K2# sh run | sec fex

feature fex

fex 113

pinning max-links 1

description "FEX0113"

fex 123

pinning max-links 1

description "FEX0123"

fcoe

N5K2# sh feature | i fcoe

fcoe 1 enabled

fcoe-npv 1 disabled

The CNA server connected to FEX Nexus 2K, while the Nexus uplinks are controlled by 2 Nexus 5Ks (vPC on the N5K)

Any suggestions ?

Thanks,

Gofi

padramas · ‎07-15-2013

Hello Gofi,

What happens when you try to boot ?

Have you mapped FCoE vlan to VSAN on N5K ( output of " show vlan fcoe ") ?

In screen shot, I notice that you have configured vlan 10 as native on vHBA. Please configure vlan 10 as native vlan on these ethernet ports.

Then verify if CNA can flogi into N5K or not.

Padma

gofianto.phin · ‎07-15-2013

Hi Padma,

I have configured the native vlan on both interface ethernet of N5K, but still no flogi found on the N5K.

N5K1(config-if)# sh run int eth113/1/1

!Command: show running-config interface Ethernet113/1/1

!Time: Thu Jun 18 03:07:34 2009

version 5.2(1)N1(5)

interface Ethernet113/1/1

switchport mode trunk

switchport trunk native vlan 10

switchport trunk allowed vlan 10,120,125,130,135,200-201

N5K2(config-if)# sh run int eth123/1/1

!Command: show running-config interface Ethernet123/1/1

!Time: Thu Jun 18 03:07:41 2009

version 5.2(1)N1(5)

interface Ethernet123/1/1

switchport mode trunk

switchport trunk native vlan 20

switchport trunk allowed vlan 20,120,125,130,135,200-201

I recheck the vlan to vsan mapping and it was configured correctly on both N5K.

N5K1(config-if)# sh vlan fcoe

Original VLAN ID Translated VSAN ID Association State

---------------- ------------------ -----------------

10 10 Operational

N5K2(config-if)# sh vlan fcoe

Original VLAN ID Translated VSAN ID Association State

---------------- ------------------ -----------------

10 10 Operational

20 20 Operational

Because no flogi found on the upstream switch, so the server can't boot the ESX.

Any other suggestions ?

Thanks,

Gofi

gofianto.phin · ‎07-26-2013

Hi Padma,

After a week of troublehooting, finally I found the issue. I just do CLEAR BIOS CMOS over CIMC of C Series. And then the vfc appear on the N5K, boot correctly through the SAN.

It seems that the C Series has cache of booting order save in the CMOS.

Thanks,

Gofi

padramas · ‎07-26-2013

Hello Gofi,

Thanks for sharing the solution.

Padma

sbhadrav@cisco.com · ‎03-19-2018

UCS Rack Server CNA <-- FCoE--> N5K <--FcoE--> SAN Array ( Target )

This is not a multihop topology as it does not have VE <--> VE connection ( or ISLs connecting different Domain IDs )

On the vHBA, you need to enable " FC SAN Boot " option to boot from FCoE target.

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/gui/config/guide/1.4.1/b_Cisco_UCS_C-Series_GUI_Configuration_Guide_141_chapter_01001.html

Before you start, checklist ( recommended config ) from top of my mind are

UCS

- Update firmware for all components using latest Host Upgrade Utility ( HUU )

- Use Cisco OEM ESXi image ( inbuilt drivers )

Nexus 5K

- Enable lldp,fcoe,npiv feature

- Verify the QoS configuration for FCoE