klittlejohn1
asked on
IBM HS22 Not Seeing Fibre Devices
Hi all,
I currently have a HS22 blade with Server 2008 r2 installed. We have a H series bladecenter. We have an IBM ds4700 SAN. Qlogic qmi2572 expansion card with qlogic pass through module connectd to a cisco fiber switch. I am not booting to san and have bios disabled for HBAs. I have updated firmware on blade and installed qlogic drivers. When i open up Sansurfer manager and click to configure the ports, i get "must have fibre devices to configure". I have entered the WWNs for the HBAs and have the LUN setup using IBM system storage manager. I cannot get this server 2008 blade to see the storage. Zones are configured on the fibre switch and have the correct WWNs. Help is needed! Thanks in advance.
I currently have a HS22 blade with Server 2008 r2 installed. We have a H series bladecenter. We have an IBM ds4700 SAN. Qlogic qmi2572 expansion card with qlogic pass through module connectd to a cisco fiber switch. I am not booting to san and have bios disabled for HBAs. I have updated firmware on blade and installed qlogic drivers. When i open up Sansurfer manager and click to configure the ports, i get "must have fibre devices to configure". I have entered the WWNs for the HBAs and have the LUN setup using IBM system storage manager. I cannot get this server 2008 blade to see the storage. Zones are configured on the fibre switch and have the correct WWNs. Help is needed! Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you configure the BIOS then you can access it and make sure the PC sees everything. In grand scheme of things the additional overhead in statistically insignificant.
ASKER
A couple of questions I have are:
1. I have the option to configure boot settings going through Setup hitting F1 and navigating to the adapters and setting options there. should i go through settings there or wait until I see ctl-Q and enter in settings that way?
2. Would I go to selective boot option and enter WWN with lun # there?
thanks
1. I have the option to configure boot settings going through Setup hitting F1 and navigating to the adapters and setting options there. should i go through settings there or wait until I see ctl-Q and enter in settings that way?
2. Would I go to selective boot option and enter WWN with lun # there?
thanks
ASKER
Issue resolved. Servers are able to see the storage. thanks for the help dlethe!
A couple of questions I have are:
1. I have the option to configure boot settings going through Setup hitting F1 and navigating to the adapters and setting options there. should i go through settings there or wait until I see ctl-Q and enter in settings that way?
Unless you are booting from the SAN, don't change anything. It is just nice if the BIOS is on so you can make sure the PC sees everything on a POST. You can also set some tunable parameters like queue depth, which may be very beneficial to you.
2. Would I go to selective boot option and enter WWN with lun # there?
See above, but the WWN is going to be the WWN of a switch port, or a LUN, so even if you wanted to boot off any particular LUN, don't make the mistake of configuring it to always boot off port#3 on a certain switch. (Unless that is what you want to do). The correct answer is that you need to know what WWN you are actually looking at. (Go to the switch)
Curios .. what was the actual problem?
1. I have the option to configure boot settings going through Setup hitting F1 and navigating to the adapters and setting options there. should i go through settings there or wait until I see ctl-Q and enter in settings that way?
Unless you are booting from the SAN, don't change anything. It is just nice if the BIOS is on so you can make sure the PC sees everything on a POST. You can also set some tunable parameters like queue depth, which may be very beneficial to you.
2. Would I go to selective boot option and enter WWN with lun # there?
See above, but the WWN is going to be the WWN of a switch port, or a LUN, so even if you wanted to boot off any particular LUN, don't make the mistake of configuring it to always boot off port#3 on a certain switch. (Unless that is what you want to do). The correct answer is that you need to know what WWN you are actually looking at. (Go to the switch)
Curios .. what was the actual problem?
ASKER
Sorry for the delay. I ended going into the bios like you suggested and putting in SAN controller WWNs for controller A and B. Looking at the SAN, it had the preferred path using controller B for the LUN access. I did a fiber scan on server's HBAs and all good. I booted server and storage was presented in disk management.
ASKER