04-02-2024 12:59 PM - edited 04-02-2024 01:01 PM
I have an environment with two FI 6248, two UCS 5108 and two 6510 brocade switches for san. UCSM has 4.0.4m version and FI are in "end host mode".
We have two service profiles in use (PRD_1 & and PRD_2), both created from the same template (PRD_TEMPLATE) and works without any issue. "PRD_TEMPLATE" has 3 VNICs and 2 VHBAs.
All works fine but recently I created a new service profile (PRD_3) from PRD_TEMPLATE, I unbinded this new service profile from the template and I associated it with a UCS Blade (4.0.4n version).
In UCSM I have only one VSAN (default) created. All VHBAs has default VSAN associated, I dont have any SAN Connectivity Policy configured.
The problem is when I try to attach the WWPN to a zone on brocade, this does not see the WWPNs of the VHBAs.On Brocade I issued the commands:
>switchshow
>portshow X
I didn´t find the corresponding WWPNs of the new HBAs.
On FI cli I issued the commands:
#show npv status
#show npv flogi table
But I can't see the corresponding WWPNs.
What could be the problem?
Solved! Go to Solution.
04-03-2024 06:14 AM
This is showing vfc1724 is in VSAN 4094. Assuming vfc1724 is the vHBA in question.
Did you set the VSAN of the vHBA?
Maybe bind the new vHBA to any prior/existing/working vHBA Template which should bring with it the VSAN?
04-03-2024 06:14 AM
This is showing vfc1724 is in VSAN 4094. Assuming vfc1724 is the vHBA in question.
Did you set the VSAN of the vHBA?
Maybe bind the new vHBA to any prior/existing/working vHBA Template which should bring with it the VSAN?
04-08-2024 05:18 PM
Thank you @Steven Tardy. I noted that the vfc 1724 was the vHBA, I restarted the ucs and also I reset the wwpn but nothing happened. I had to create a new service profile and then all worked normally.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide