Home.... | log in.... | Pub my question! | Sign-up....

Java-index >> Storage Forums >> Storage General Discussion

Disk array 3510 not visible on V240 server : Solaris 9

Hi All,

This is very urgent issue, where we are not able to see Disk array from the server, Please help. We are using Sun StorEdge 3510 FC disk array along with Sun netra V240 server. We have installed Solaris 9 OS on V240 server and installed the Recommended patch cluster available from the Sun's Patch site.

Somehow, the StorEdge 3510 is not visible on the server. We have configured the logical partitions on 3510 diskarray and done LUN mapping. We have connected fiber cable between server and disk array. Are there any other patches that i need to install ? Any ideas would be greatly appreciated.

Thanks

Karthik

[658 byte] By [] at [2007-11-25 23:02:47]

«« Sata Controller
»» T3/T3+ or T3a/T3b

# 1

Did you do a reconfiguration boot after installing the patches HBA driver?

Can you drop the server to the obp and run the following commands:

ok setenv auto-boot? false

ok reset-all

After reset:

ok probe-scsi-all

If you can see the array from the obp then you are most likely experiencing a software issue. Please tell me what HBA you are using.

at 2007-7-5 17:54:45 >

top of Java-index,Storage Forums,Storage General Discussion...

# 2

To get a better idea of your configuration, please send the answers to the following:1) version of StorEdge SAN Foundation Kit you are using2) type of HBA cards3) how are you connected to the 3510 (e.g. what ports are you using)-Jojo Jaballas

at 2007-7-5 17:54:45 >

# 3

Jojo, SFK may not be applicable here since they mention that the array is directly attached to the server. I also get the feeling that the system may have been patched but the HBA driver has not been installed, hence the suggestion to go to obp to see if the LUN is visable that way. I have come accross this issue with a Sun customer that was attaching to an EMC Clariion with a Emulex HBA, early Solaris 9 does not support the lpfc driver and initially they were unable to see the LUN when Solaris was loaded.

<b>EDIT</b> I've updated this post, the cards on my customers server were in fact an Emulex OEM card and not a Sun Emulex card.

at 2007-7-5 17:54:45 >

# 4

Hi m-lennon,

hmmm, I don't mean to disagree with you 'cause being a senior member you've obviously been around. BUT, the Sun StorEdge 3510 Release notes (ref <a href="http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-6597-13.pdf " target="_blank"> http://www.sun.com/products-n-solutions/hardware/docs/pdf/81 7-6597-13.pdf</a>) & Sun's Best Practices (ref <a href="http://www.sun.com/products-n-solutions/hardware/docs/pdf/816-7325-16.pdf " target="_blank"> http://www.sun.com/products-n-solutions/hardware/docs/pdf/81 6-7325-16.pdf</a>) clearly states that the SAN Foundation Kit is required for Solaris 8 & 9 (regardless of whether in DAS or SAN configuration). And all of the client installs that I've worked on have included the SAN Foundation Kit and never have we had an issue with getting the OS to see the luns from the 3510 array. Then again, all the HBA cards (e.g. 375-3102 or 375-3108) we've used meets the requirement for the 3510 array. The 3510 is actually pretty easy to work with once you've gotten comfortable with how to configure it. We've pretty much streamlined our 3510 config down to the following process:

1) build OS on server and install latest recommended patch clusters

2) Install latest SAN Foundation Kit (e.g. v 4.4)

3) console into array and configure for network access

4) from host, telnet into array and configure all configuration parameters (e.g. Caching Parameters, Host-side SCSI Parameters, Disk Array Parameters)

5) Configure logical drives & map luns to appropriate channels

6) Verify HBA cards have link to the ports on the array/switches (e.g. 'luxadm -e port' should show have connected status)

7) Check HBA controller status (e.g. 'cfgadm -al' if controller is still in "uncofigured" status, then configure it with 'cfgadm -c configure controller_number'

8) Verify luns visibiliy through format

9) Install SUNWsscs & configure the service agent

-Jojo Jaballas

at 2007-7-5 17:54:45 >

# 5

I understand what you are saying, I didn't read the best pratice guide before posting. So SFK is applicable! Now we've got to hear from Karthik to see if they've tried any suggestions. BTW no need to worry about the disagreement, but I have a tendancy to use the obp first, it reduces OS troubleshooting time for me.

at 2007-7-5 17:54:45 >

# 6

Hi All,

I am having similar problems. My scenario.

Sun Fire V240 (Solaris 9 latest Recommended Patch Cluster) with 3510FC (Firmware 4.15G, Bootrecord 1.31H) and 2GB single connection Fibre HBA. This card is Emulex/Sun OEMed, Sun FRU PN 375-3304-1 Rev 52. Marketing part number SG-XPCI1FC-EM2. This is Sun OEMed Emulex LP10000. Firmware is 5.01a8.

V240 Server has System PROM revisions:

OBP 4.22.19 2006/09/06 23:44 Sun Fire V210/V240,Netra 210/240 OBDIAG 4.22.19 2006/09/06 23:57

The basic problem is the server doesn't see the HBA from OS and hence doesn't see the 3510FC.

From OpenBoot prompt I can see card and 3510FC. I do

show-devs

Lots of stuff deleted....

Emulex card is shown below

/pci@1e,600000/SUNW,emlxs@3/fp@0,0

/pci@1e,600000/SUNW,emlxs@3/fp@0,0/disk

I can see the 3510FC from OpenBoot.

{1} ok apply show-children /pci@1e,600000/SUNW,emlxs@3

Device ALPA a7 WWPN 216000c0ff8a77f0

LUN 0DiskSUNStorEdge 3510415G

Should I be able to see my Logical Drives that I set-up from OpenBoot?

For example

select /pci@1e,600000/SUNW,emlxs@3

show-children I only see 3510FC again.

When I boot into OS I get the messages

Apr 17 14:24:39 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:24:40 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:24:40 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

Apr 17 14:25:14 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:25:14 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:25:14 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

Apr 17 14:25:48 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:25:48 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:25:48 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

Apr 17 14:26:22 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:26:22 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:26:22 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

Apr 17 14:26:56 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:26:56 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:26:56 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

Apr 17 14:27:30 dubsdbs10_new emlxs: [ID 349649 kern.notice] [6.0262]emlxs1: ERROR: 201: Adapter initialization failed. (Unable to configure port. Mailbox cmd=88 status=fffe hbainit=0)

Apr 17 14:27:30 dubsdbs10_new emlxs: [ID 349649 kern.notice] [5.0517]emlxs1: ERROR: 201: Adapter initialization failed. (status=5)

Apr 17 14:27:30 dubsdbs10_new emlxs: [ID 349649 kern.notice] [B.11DA]emlxs1: ERROR: 101: Driver attach failed. (Unable to initialize adapter.)

I have configured the 3510FC as follows:

Lun 0 Logical Drive 0 Partition 0 are configured as RAID 5 drive with just first 3 actual drives. This is just for a test.

They are on Channel 0 ID 40 Primary Controller. I setup a filter so that the Fibre Card WWN could see LUN 0. I have configured my LUN as per page chapter 5 - "First-Time Configuration FC or SATA Arrays", page 79 of Sun StorEdge 3000 Family RAID Firmware 4.15 Users Guide.

It is worth noting that the LEDs on the HBA behave as follows

LEDS :

When booted to OpenBoot prompt Green is constantly on. Amber is "fast blink". Looking in the page 8 of "Sun StorEdge Enterprise 2GB FC Single and Dual Port Host Bus Adapter Install Guide" manual this seems to mean "Normal Operating System 2GhZ link rate". This is good!!!

However when I boot into the OS it changes to Green On, Amber Off which is "Failure While Functioning".

I have Sun SAN Software (SFS) 4.4.12 installed on OS. This includes the following

SUNWcfclSUNWcfplxSUNWemlxux SUNWfcsmSUNWjfcaux SUNWqlcx

SUNWcfclrSUNWemlxsSUNWfchbaSUNWfcsmxSUNWjfcaxSUNWsan

SUNWcfclxSUNWemlxsx SUNWfchbrSUNWjfcaSUNWmdiu

SUNWcfplSUNWemlxuSUNWfchbxSUNWjfcauSUNWqlc

I installed it using the install_it script. This installs the patches etc.

It is worth noting that SFS upgraded the cards firmware the fist time it was installed see below.

Apr 17 10:44:53 dubsdbs10_new emlxs: [ID 349649 kern.info] [6.021C]emlxs1: NOTICE: 200: Adapter initialization. (Firmware update needed. Updating... (id=17 fw=16))

Apr 17 10:44:53 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.09D5]emlxs1: NOTICE:1520: Firmware download. (AWC file: KERN: old=1.30a5 new=1.40a3 )

Apr 17 10:44:56 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.09DF]emlxs1: NOTICE:1520: Firmware download. (DWC file: TEST: new=1.01a0 )

Apr 17 10:44:56 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.09E2]emlxs1: NOTICE:1520: Firmware download. (DWC file: STUB: old=1.90a4 new=1.91x15 )

Apr 17 10:44:56 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.09E6]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI1: old=1.90a4 new=1.91x15 )

Apr 17 10:44:56 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.09EA]emlxs1: NOTICE:1520: Firmware download. (DWC file: SLI2: old=1.90a4 new=1.91x15 )

Apr 17 10:45:02 dubsdbs10_new emlxs: [ID 349649 kern.info] [3.018A]emlxs1: NOTICE:1521: Firmware download complete. (Status good.)

Does anyone have any idea where I could start with this problem?

Best Regards and thanks in advance.

Kevin Smith.

Message was edited by:

K_Smith

K_Smith at 2007-7-5 17:54:45 >

# 7

Hi All,

Replying to my own message with update just in case other people experience this problem.

The problem was solved by removing the PCI Riser Card in V240 and plugging the HBA into bottom direct motherboard slot on V240.

This worked!!!!

Got new riser card today from Sun and put it in. Emulex cards now work in Riser Card PCI slots to!

Conclusion PCI Riser card was the problem.

Best Regards,

Kevin.

K_Smith at 2007-7-5 17:54:45 >

Storage General Discussion

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

Disk array 3510 not visible on V240 server : Solaris 9

Storage Forums New Topic

Storage Forums Hot Topic

Storage Forums

All Classified