SAN Manager LM for HP-UX Release Notes
Table Of Contents
- 1 Installation
- 2 Storage Management
- 3 Troubleshooting
- Verifying that the Daemon is Running
- Viewing the LogFile
- An HP-UX Host is Grayed Out in the Administration Application
- No SAN Devices are Available on an HP-UX Host
- An Assigned Device Is Not Accessible to an HP-UX Host
- Error During Mounting: “Not A Block Device”
- An HP-UX Host is not Discovered by a SAN Manager LM Administration Host
- A Device Cannot be Unassigned from an HP-UX Host
- Index
Viewing the LogFile 35
Troubleshooting
Viewing the LogFile
The SAN Manager LM logfile (/tmp/Service.log) is a useful troubleshooting tool. The
following example shows the logfile on a system where the service (daemon) initialized
properly and found the SAN Manager LM database.
When viewing the logfile, note the following:
• If the logfile says Init DB found index 0 id 2009814699, this means that the
HP-UX host found a database on its SAN.
Note In this example, 2009814699 is the ID of the database. This number varies from
SAN to SAN.
• The UID from registry is the unique SAN Manager LM ID of this host. This value is
different for every host on the SAN. The UID value for any host is 0 until the host is
added to the SAN Manager LM database.
• If the daemon status says start event loop listening on 1 addresses, the system
is ready to use SAN Manager LM.
sb-c3po# cat /tmp/Service.log
Sep 26 11:13:59 : TRSANMANService: Initializing
Sep 26 11:13:59 : Searching for db: index 0 id 2009814699 is type 0x3
Sep 26 11:13:59 : Searching for db: index 1 id 1139278638 is type 0x1
Sep 26 11:13:59 : Searching for db: index 2 id 1213150662 is type 0x1
Sep 26 11:13:59 : Searching for db: index 3 id 1783693402 is type 0x0
Sep 26 11:13:59 : SANServiceLogicalStorage::Init DB found index 0 id 2009814699
Sep 26 11:13:59 : TRSANMANService: Init finished
Sep 26 11:13:59 : UID from registry 2009859324
Sep 26 11:13:59 : TRSANMANService: start event loop listening on 1 addresses