HPE BladeSystem Virtual Connect
Showing results for 
Search instead for 
Do you mean 

BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Highlighted
Advisor

BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Trying to install a BL460c Gen8 with a new 2 x v2 E5-2670 CPU and 256GB memory into a c7000 with FlexFabric.  The OA is 4.01 and VC is 4.1.

 

We apply the Server Profile with Ethernet and FC.   When we install HP branded vSphere 5.5 on the host is does not detect the HBA part of the CNA. 

 

Any thoughts?

 

Thanks,

-MattGG

14 REPLIES
Regular Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Hi Matt

 

Had the same problem with Proliant BL660c gen 8, we tried almost everything we could think off, no success. Elevated the call to Level 2 engineering and they were taking very long to resolve. So we decided to apply some classical troubleshooting methods and low and behold stumbled on the solution quite by accident. For some reason even though firmware drivers etc were off the latest HP build of ESXI 5.5 Sept 2013 could not get the server WWPN to login to fabric.

 

Basically we knew that we should find hba/fcoe info in /proc/scsi- but it had only an sa entry for the internal smart array controller so we knew something was wrong on the blade side of things. I then ran the following command from an ssh session: esxcfg-fcoe -d vmnic2 and do the ame fo vmnic3. If you go back to /proc you will see that there is an entry for the FCOE hba including it's WWN etc. From here everything should just work as normal.

 

Hope this helps you solve your issue?

 

Regards

 

Kumi Chetty ( HP South Africa)

Occasional Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Hi Kumi Chetty,

 

I would like to extend my gratitude to you for your information on this, I have the same issue with 18 x blade servers and HP support have been very below par to say the least!!!

 

Now I would like to know why that fixes it and why this is not already known by L2 HP support.

 

A massive thank you again to you, legend!

:)

 

Spoiler
 

 

Respected Contributor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

To vent I had the same problem with 5.1.  Support was utterly useless.  I found the link to the fix on VMware's site and the rep ignored me when I said we should try it.  This was after a week and a half of back and forth.  I finally just did it and it resolved the issue.

 

I still can't believe that it isn't documented somewhere within HP.  They should have been able to provide me a fix right away for this issue.  

 

To say I was dissappointed in support is an understatement.

Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

[ Edited ]

Command “esxcfg-fcoe -d vmnic2 “ is a ESX console command, used to create fabric login in ESX OS. If there are any hardware or blade issue fabric login creation would fail.

 

Steps to configure FCoE,

 

  1. Change the default  Nic Personality from ISCSI to FCoE in RBSU.
  2. If there a VC setup, Create the SAN Fabrics FCoE_A and FCoE_B configure appropriate uplink ports, refer 36 Page VC cook book if need more help.

   http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c02616817-5.pdf

 

3. In order to configure FCoE on VMware ESX5.X either use Esx console or VI Client  GUI, for more help refer below link shared for Intel Chip adapters.

 

http://www.intel.in/content/dam/www/public/us/en/documents/guides/ethernet-x520-configuring-fcoe-vmware-esxi-5-guide.pdf

 

thanks

Javeed

Respected Contributor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Hi Kumi Chetty,

 

you saved my Day!

 

esxcfg-fcoe -d vmnic0

 

Was the solution for us too.

 

We have BL560c Gen8 with v2 CPU and 534FLB & ESX 5.5.

 

Thank you.

Occasional Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

I've been struggling with the same issue for almost a week now. BL460c Gen8 (745915-S01) with a 534FLB and a 554M. The 554M showed up, no problem. Finally ran across this article from VMware: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034702. Now I can see my 534FLB...
Occasional Collector

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

I have Same Problem, Please run below command and activate HBA on ESXi host,

 

1-       Login to ESXi CLI.

2-       Determine which interfaces are FCoE capable
      
# esxcli fcoe nic list.

3- Activate FCoE:
# esxcli fcoe nic discover –n vmnicX (vmnicX is VMNIC Number)

4- Verify the interface is activated by one of the steps below:

      # esxcli fcoe adapter list

      # esxcfg-scsidevs –a

Note:
If it is not activate, please reinstall the driver.


Command Scritp

esxcli fcoe nic list
esxcli fcoe nic discover -n vmnic4  (vmnicX is VMNIC Number)
esxcli fcoe nic discover -n vmnic5  (vmnicX is VMNIC Number)
esxcli fcoe adapter list
esxcfg-scsidevs -a

 

Thanks

Shriniwas

Occasional Contributor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

I got to say: thank you for sharing, it worked for me too !!
HPE Pro

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

[ Edited ]

 

Got the FCoE ports working but now it seems the enet ports are also still visible.. Anyone got a solution to fix this as I am stumped here.. Probably missing some dumb something but stil..

 

I work for HP

A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details

Hit that Thumbs Up button if you find this helpful.
Occasional Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Worked for me also ....Thanks!!!!!!!!!!

Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

[ Edited ]

Kumi Chetty,

 

Thanks a milion times for your post!

Occasional Visitor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Kumi,

 

Thanks for the suggestion!

 

Solved the issue real quick and effective.

 

 

Regards,

 

Bram

Technical Consultant @ HP The Netherlands

Advisor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

I was having this problem too and thanks to this I was able to fix it.

Now I have a couple of questions in a Boot from SAN scenario

  1. How can I make this work in a boot from SAN scenario ? I mean, how can I force FCoE hba scanning before setup scans the media ? Can I escape to a shell ALT-something before setup scans the media or do I have to customize the ISO with scripts ?
  2. If I were able to make the setup "see" the LUN in the SAN media, it will work after the reboot ?

 

Thanks.

 

 

Regular Advisor

Re: BL460c Gen with V2 Intel CPUs can't see 534FLB's HBA?

Thanks. i am not sure how it was not mentioned in the document. the issue was resolved by as belwo.

 

login as: root
Using keyboard-interactive authentication.
Password:
The time and date of this login have been sent to the system logs.

VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
~ # cat /proc/scsi/bnx2fc/5
cat: can't open '/proc/scsi/bnx2fc/5': No such file or directory
~ # esxcfg-fcoe -l
~ # esxcfg-fcoe -d vmnic2
~ # esxcfg-fcoe -d vmnic3
~ # esxcfg-fcoe -l
HBA Name: vmhba32
Source MAC: 36:17:ab:50:00:16
FCF MAC: 44:1e:a1:78:f3:74
VNPort MAC: 0e:fc:01:01:02:02
Underlying PNIC: vmnic2
Priority Class: 3
VLAN ID: 1001

HBA Name: vmhba33
Source MAC: 36:17:ab:50:00:17
FCF MAC: 00:00:00:00:00:00
VNPort MAC: 00:00:00:00:00:00
Underlying PNIC: vmnic3
Priority Class: 3
VLAN ID: 0

~ # cat /proc/scsi/bnx2fc/5
Broadcom Offload FCoE:bnx2fc v1.78.76.v55.1 over vmnic2
HBA:0x410aae04a0b0 for netdev:vmnic2
Adapter state: UP, READY, FFA
Registered with cnic
Flags:0x0
init_done: FW_INIT_DONE, CTLR_INIT_DONE, CREATE_DONE,
Vlan Disabled
Vlan Filter Stats: invalid grp: 0, invalid vlan: 0
IO CMPL - ABORT RACE: 0, 0
next_conn_id:0x0
num_offload_sess:0
cna_init_queue:0
cna_clean_queue:0
fip(0x410aae04a578) lp(0x410a58f3c810) information
State: FIP_ST_ENABLED
lld selected mode: FIP_ST_AUTO
fcf_count:1 sol_time:554809 sel_time:558008 port_ka_time:564210
ctlr_ka_time:559211 user_mfs:0 flogi_oxid:0xffff flogi_count:0
reset_req:0 map_dest:0 spma:0 send_ctlr_ka:0 send_port_ka:0
dest_addr:44:1e:a1:78:f3:74
ctl_src_addr:36:17:ab:50:00:16
vlan_id:1001
lport(0x410a58f3c810) information
link_up:1 qfull:0 boot_time:0x87738 retry_count:0
State: LPORT_ST_READY
WWNN[10003a0544700009] WWPN[10003a0544700008] SParam:0x22 e_d_tov:2000 r_a_tov:10000
sg_supp: Disabled
seq_offload: Disabled
crc_offload: Disabled
lro_enabled: Disabled
does_npiv: No
npiv_enabled: Enabled
mfs:2048 max_retry_count:3 max_rport_retry_count:255
link_supported_speed: 1GB, 10GB,
link_speed: 10GB
lro_xid:0 lso_max:0
Offloaded ports:
cvl_workaround: 0
cvl_workaround alloc: 0
cvl_workaround alloc_err: 0

~ # cat /proc/scsi/bnx2fc/6
Broadcom Offload FCoE:bnx2fc v1.78.76.v55.1 over vmnic3
HBA:0x410aae04b0c0 for netdev:vmnic3
Adapter state: UP, READY, FFA
Registered with cnic
Flags:0x0
init_done: FW_INIT_DONE, CTLR_INIT_DONE, CREATE_DONE,
Vlan Disabled
Vlan Filter Stats: invalid grp: 0, invalid vlan: 0
IO CMPL - ABORT RACE: 0, 0
next_conn_id:0x2
num_offload_sess:2
cna_init_queue:0
cna_clean_queue:0
fip(0x410aae04b588) lp(0x410a58f3d840) information
State: FIP_ST_ENABLED
lld selected mode: FIP_ST_AUTO
fcf_count:1 sol_time:555385 sel_time:558805 port_ka_time:564800
ctlr_ka_time:559801 user_mfs:0 flogi_oxid:0xffff flogi_count:0
reset_req:0 map_dest:0 spma:0 send_ctlr_ka:0 send_port_ka:0
dest_addr:44:1e:a1:78:f3:8c
ctl_src_addr:36:17:ab:50:00:17
vlan_id:1001
lport(0x410a58f3d840) information
link_up:1 qfull:0 boot_time:0x87979 retry_count:0
State: LPORT_ST_READY
WWNN[10003a054470000b] WWPN[10003a054470000a] SParam:0x22 e_d_tov:2000 r_a_tov:10000
sg_supp: Disabled
seq_offload: Disabled
crc_offload: Disabled
lro_enabled: Disabled
does_npiv: No
npiv_enabled: Enabled
mfs:2048 max_retry_count:3 max_rport_retry_count:255
link_supported_speed: 1GB, 10GB,
link_speed: 10GB
lro_xid:0 lso_max:0
Offloaded ports:
rport:0x410a48203760 cid:0
rport:0x410a48204e90 cid:1
cvl_workaround: 0
cvl_workaround alloc: 0
cvl_workaround alloc_err: 0