Secure Path for Linux only seeing one controller

[Keri MacNeil]

We have an EVA5000 SAN, and I have just connected my first Linux Server (Red Hat AS 2.1) to it using Secure Path 3.0C. The server has many HPUX and Windows servers that are already connected to it.

I'm used to seeing 4 paths on HPUX to each LUN, since we have 2 HBAs connected to 2 controllers.

When I run spmgr display on the Linux server, it only reports 2 paths, and both are through a single controller, one is listed as active and the other as available. I would expect the other two paths through the other controller as standby.

I have confirmed that zoning is OK (even turned zoning off during troubleshooting).

The LUN is configured as "No preference". If I force the path to the other controller, the mounted filesystem becomes dual failed. However, when I reboot in this state, the system will come up connected to the other controller.

Load Balancing, Auto Restore, and Path Verify are on in spmgr. I have tried turning these settings off, with no difference.

Obviously I would like to have all paths available in case failover is needed. Any clues?

[Steven Clementi]

Michael:

Some additional things to check would be...

1. Make sure your host definition in Command View has the WWID's for BOTH HBA's in the server configured.

2. Make sure your HBA's are logging into the SAN Switch Properly. Both should auto negotiate at 2G/F-Port. Check the links i the back of the cards too. Usually green/amber means it's linked vs. only amber, not connected. (most of the time).

3. You should never turn zoning off in a production environment, unless you absolutely know that there might be problems afterwards.


Steven

[Nguyen Anh Tien]

1. Check all required Patches on Redhat AS 2.1 server for Securepath.
2. Each LUN should be configured for each controller.
MiChael, you should consider required Patches. Last time i worked on EVA3K and lacked 1 patches. My server (HP-UX 11i) was hang wherever it boot. After patched. It is OK.
regard.
Tienna

[Keri MacNeil]

I think I found the problem. On the EVA, I had identified the OS as "Unknown" since "Linux" wasn't a choice for OS. After talking to someone at HP about an unrelated issue, I found out that you should choose "Solaris" as the OS when connecting a Linux server to the EVA. Once I did that, and rebooted, all paths were visable.