BladeSystem - General
1748089 Members
4933 Online
108758 Solutions
New Discussion юеВ

Re: c-Class VirtualConnect FC *not* using "virtual" WWNs

 
nickkk
New Member

Re: c-Class VirtualConnect FC *not* using "virtual" WWNs

within SANsurfer manager in our box to see what firmware versions we have on our HBAs ... one says firmware version is 4.00.18 and the optionrom firmware version says 4.00.85 ... whats the difference??

See details:


Host Name : mylesx04
HBA Model : QMH2462
HBA Alias :
Port : 1
Port Alias :
Node Name : 20-00-00-E0-8B-91-23-A4
Port Name : 21-00-00-E0-8B-91-23-A4
Port ID : 00-00-00
Serial Number : RFC0633L56131
Driver Version : 7.07.04
FCode Version : 1.26
Firmware Version : 4.00.18
HBA Instance : 3
OS Instance : 3
HBA ID : 3-QMH2462
OptionROM BIOS Version : 1.26
OptionROM FCode Version : 1.17
OptionROM EFI Version : 1.08
OptionROM Firmware Version : 4.00.85
Actual Connection Mode : Unknown
Actual Data Rate : Unknown
PortType (Topology) : Unidentified
Total Number of Devices : 0
HBA Status : Loop down
Annetje
Occasional Advisor

Re: c-Class VirtualConnect FC *not* using "virtual" WWNs

So, the blade server (offline) Firmware CD does not update the Qlogic mezz card? How can you see the Qlogic firmware version?

I am having the same problem. Brocade Director 4800 with BL460c. (FOS FOS 5.2.0a What we see through.

Firmware on blade servers, OA and VC were updated by HP CE yesterday.

nsshow reports are just wack. Some show port 1 WWN from QLogic and port 1 from Virtual Connect + 1.
Paul_637
Regular Advisor

Re: c-Class VirtualConnect FC *not* using "virtual" WWNs

The .18 and .85 versions are fine. It's something like firmware and not-so-firmware (I know that sounds stupid!).

Its kind of like one of them (the .85 I think) is actually a *driver* version rather than firmware.
Annetje
Occasional Advisor

Re: c-Class VirtualConnect FC *not* using "virtual" WWNs

That did it. Forums rock!