cant add hba in virtual connect using bl490g6

[phillbl1]

Hi,
we have the following setup

c7000 blade enclosure with virtual connect. 6 bl490 servers configured and running.

These are in bays 1,2,3,9,10,11

all flex 10 with qlogic qmh2562 8gb fc hba installed

All setup to boot from eva 4400. all work without any issues.

we have added the following
2 bl490 with flex 10 & qlogic qmh2562 8gb fc hba installedto eva as ports, presented staorage to hosts

The cards was installed in mezanine slot 2 in the blades

blades in slots 4 & 12 in the chasis

when i try to add a profile the following message appears:
At least one fibre channel hba port is not connected to a vc-fc switch. The mezzanine card maybe installed in the wrong location. Are you sure you to continue. I click yes and continue

when i check the fabrics in virtual connect they look ok and they are listed but they say "not logged in"

Any help on the above is much appreciated.

When i try to add the a profile it works apart from the fibre connections dont work

Thanks

[Shayne Heidemann]

Hi.

I assume that you have VC Fibre interconnects in slots 3 and 4.

Are you using OM3 cables, or OM2?

[Markus M.]

Hi,

I suppose Shayne is on the right way.
If VC-FC Interconnect is on bay 3 and 4 you have to remount the fc mezz to Mezz Port 1.

Compare the mezz card location of the "old" blades with the location of the new ones.

kind regards
Markus

[phillbl1]

thanks for that. worked it out yesterday! cards now in slot 1.

one of the blades is fine but when i look at the interconnect module in virtual connect one of the blades has NOT-LOGGED-IN next to it. Any ideas what this means. I have checked the blade and all lights appear green and no errors.

Thanks

[The Brit]

Be sure that the SAN Switch Ports have NPIV enabled.

Dave.

[phillbl1]

six existing servers connect through using the interconnect bays with the fibre already plugged into the port. would all the other servers not work if this was the case?

[Antonio Milanese]

Hi,

>connect one of the blades has NOT-LOGGED-IN next to it

try this:

1) unassign VC server profile of guilty blade
2) reboot the balde and enter Qlogic menu (alt-q) and reset to default the raw config
3) reassingn server profile
boot with smartstart or try a LUN scan from Qlogic menu to "force" a fc login

it has worked for me a couple of times when some hba nvram got nuts after a FW upgrade

Cheers,

Antonio

[phillbl1]

hi, thanks, that worked great