Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

N

NeilHopwood

46 Posts

1459

July 5th, 2010 02:00

Mixed HBA host discovery problem

I have a Solaris 10 host with Emulex HBAs connected to Sym and Qlogic connected to RAMSAN. Although the host is discovered in Control Center it does not have the Emulex HBAs associated with it, though the Qlogic are listed.

The missing HBA show up in the unknown HBA tab, if I manually associate them after the next discovery cycle the Emulex cards reappear in the unknown section and loose their association with the host.

Has anyone seen this before? Is it a Control Center issue or a host issue?

Thanks

ConorLawlor

2 Intern

 • 

233 Posts

July 5th, 2010 06:00

Hi Neil,

What errors messages are being generated in the Solaris Host agent logs " %ECC_INSTALL_ROOT%/exec/MSR610/MSR.log etc.." at the time of the HBa discovery?

If Solution Enabler is installed on this host run syminq hba -fibre on the host and confirm if it returns HBa information.

otherwise

if Solution Enabler is not installed on the host. Please download the inq.sol64 utility for Solaris from the following ftp site: ftp://ftp.emc.com/pub/elab/inquiry/v6.5.2.0  Copy it to /usr/ecc/exec/MSR610 on the problem host.

Run the following commands and provide the outputs.


# cat /etc/hba.conf > hba_conf.out
# ./inq.sol64 -hba > inq_hba.out
# export SDEBUG=ALL
# ./inq.sol64 -hba > inq_hba_debug.out

This will help to pinpoint if the issue is related to the Solaris Host agent or a problem with the SNIA libraries on the host.

Use the following points to confirm proper configuration of the Solaris host.

  • Ensure that an EMC supported version of the Fibre Channel HBA driver is installed.

  • Ensure that the application support libraries (SNIA) have been installed.  For many vendors, the libraries are shipped with the driver, however, they may need to be installed separately.  Check the driver installation manual and release notes for information on installing the libraries.  If SNIA libraries are not available for the HBA, then ControlCenter will not be able to import its World Wide Names.

  • If a supported driver and its support libraries have been installed, check the contents of the file /etc/hba.conf.  This file is used by Solutions Enabler and ControlCenter Host Agent to identify the location of the SNIA-compliant libraries.  The file is created automatically by the HBA driver installation utility, and should appear something like this:

If the hba.conf file does not exist or is empty, re-installing the application libraries will resolve the issue.  If you are sure that the SNIA-compliant libraries are present, use the above example to populate the file based on the type of HBA installed in the host.  Ensure that the paths on each line point to a file that exists.

Once the modifications have been performed, restart the Solaris Host Agent and the missing information will be populated into the ControlCenter Console.

Conor Lawlor

Was this post helpful?

View All

No Events found!

Top