topic Re: Command View SDM - install problem in Operating System - HP-UX

Command View SDM - install problem

Matt Powell — Wed, 26 Nov 2003 23:02:59 GMT

Greetings,

I am having difficulty installing CommandViewSDM version 1.07 on an rp5430 running HPUX 11.00 attached to a VA-7100.

Using swinstall the installation completes with this error in the swagent.log "Unable to obtain host IP address for /etc/opt/sanmgr/hostagent/config/
commIpAddr.txt"
and "Failure may have resulted in a partial installation." and "The preinstall" script for "CMDVIEWSVR" failed..."

Does anybody have a clue about this?

I can ping my hostname, I can nslookup my hostname. The "launcher" starts the java GUI but I don't have any devices. I think that is probably because the CMDVIEWSVR component failed the installation.

Here is some output that might be helpful:

swlist
# Initializing...
# Contacting target "phswaint01"...
#
# Target: phswaint01:/
#

#
# Bundle(s):
#

A5230A B.11.00.05 100BT/9000 PCI
A6795A B.11.00.10 PCI Tachyon TL/TS/XL2 Fibre Channel
B5725AA B.4.3.91 HP-UX Installation Utilities (Ignite-UX)
CMDVIEWSDM A.1.07.00 hp StorageWorks Command View SDM
HPUXEng64RT B.11.00.01 English HP-UX 64-bit Runtime Environment
HWE1100 B.11.00.0303.4 Hardware Enablement Patches for HP-UX 11.00, March 2003
Ignite-UX-11-00 B.4.3.91 HP-UX Installation Utilities for Installing 11.00 Systems
OnlineDiag B.11.00.24.11 HPUX 11.0 Support Tools Bundle, Mar 2003
QPK1100 B.11.00.60.4 Quality Pack for HP-UX 11.00, March 2003
UnlimUserLic B.11.00.02 HP-UX Unlimited-User License
XSWGR1100 B.11.00.47.08 General Release Patches, November 1999 (ACE)
perl B.5.6.1.F Perl Programming Language
#
# Product(s) not contained in a Bundle:
#

HPOVLIC 4.31.000 HPOVLIC
HPOVSAMDA 03.10.00.0113 hp OpenView storage area manager HostAgent DIAL
HPOVSAMHA 03.10.00.0113 hp OpenView storage area manager HostAgent Framework
HPOVSAMJR 1.4.1.3 hp OpenView storage area manager embedded JRE
HPOVSAMSG 03.10.00.0113 hp OpenView storage area manager HostAgent SCSI Gateway
SMI-S_VA 1.02.02 hp StorageWorks SMI-S VA
SSLIC 1.0.0.0 HP Storage Software License Manager
#

ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================================
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 4 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 5 0/12/0/0.8.0.108.0.0.0 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
#

# ./fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.2
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Previous Topology = UNINITIALIZED
Link Speed = UNINITIALIZED
Local N_Port_id is = 0x000000
Local Loop_id is = 126
N_Port Node World Wide Name = 0x50060b0000103ca7
N_Port Port World Wide Name = 0x50060b0000103ca6
Driver state = AWAITING_LINK_UP
Hardware Path is = 0/10/0/0
Number of Assisted IOs = 0
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 960
Driver Version = @(#) PATCH_11.00: libtd.a : Jul 15 2002, 11:34:12, PHSS_26798

# ./fcmsutil /dev/td1

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.2
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PRIVATE_LOOP
Link Speed = 1Gb
Local N_Port_id is = 0x000001
Local Loop_id is = 125
N_Port Node World Wide Name = 0x50060b000010c307
N_Port Port World Wide Name = 0x50060b000010c306
Driver state = ONLINE
Hardware Path is = 0/12/0/0
Number of Assisted IOs = 4054
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 960
Driver Version = @(#) PATCH_11.00: libtd.a : Jul 15 2002, 11:34:12, PHSS_26798

(NOTE: I have only (1) one FC adapter connected to the array. )

Thank you for any help.
Matt Powell
Providence Health System

Re: Command View SDM - install problem

Steven E. Protter — Thu, 27 Nov 2003 00:03:03 GMT

swverify \*

This will show any partially installed software.

swconfigure \* will try and configure anything that is installed and not configured.

After that run another swverify \*

Anything that still shows up as a problem will have to be diagnosed(swremove start over).

SEP

Re: Command View SDM - install problem

Matt Powell — Thu, 27 Nov 2003 01:36:16 GMT

Steven,

Thanks - I gave that a try. I probably should have mentioned that I already had done swremove and reinstalled several times to no avail. But anyway, heres what I got after trying your suggestion:

The second swverify complained about 7 corrupted filesets. In the swagent.log I have these 7 errors:

ERROR: Corrupt CMDVIEWSVR.SVRNEWCONFIG,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVRLICENSING,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVREVENTLIB,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVRDEVICES,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVRCONFIG,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVRCOMMANDS,l=/,r=A.1.07.00
ERROR: Corrupt CMDVIEWSVR.SVRCLASSES,l=/,r=A.1.07.00

...which isn't all that surprising given that this is the same software component that fails the swinstall in the first place.

Could I simply have a bad install CD?

The swinstall error is very consistent.

Thanks for your help. - Matt

Re: Command View SDM - install problem

Bernhard Mueller — Fri, 28 Nov 2003 04:52:11 GMT

Matt,

very unlikely that the CD is bad.

So did you also make sure that

nslookup matches nslookup
and nslookup localhost matches 127.0.0.1
and nslooup 127.0.0.1 matches localhost.

If that is all ok, restart swagentd with
swagentd -r

Regards,
Bernhard

Re: Command View SDM - install problem

Matt Powell — Fri, 28 Nov 2003 16:19:03 GMT

Bernhard,

Thank you for your input. I'm still having the same errors in the installation however.

Following are the responses to nslookup that you recommended I confirm. It looks OK to me, but perhaps someone can spot something:

# hostname
phswaint01
#
# date
Fri Nov 28 13:01:01 PST 2003
# hostname
phswaint01
# uname -a
HP-UX unknown B.11.00 U 9000/800 1781967605 unlimited-user license
# nslookup phswaint01
Name Server: rdcdns01.wa.providence.org
Address: 10.230.3.199

Trying DNS
Name: phswaint01.wa.providence.org
Address: 10.230.3.51

# nslookup 10.230.3.51
Name Server: rdcdns01.wa.providence.org
Address: 10.230.3.199

Trying DNS
Name: phswaint01.wa.providence.org
Address: 10.230.3.51

# nslookup localhost
Name Server: rdcdns01.wa.providence.org
Address: 10.230.3.199

Trying DNS
looking up FILES
Name: localhost
Address: 127.0.0.1
Aliases: loopback

# nslookup 127.0.0.1
Name Server: rdcdns01.wa.providence.org
Address: 10.230.3.199

Trying DNS
Name: localhost
Address: 127.0.0.1

# more /etc/hosts
# @(#)hosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $
#
# The form for each entry is:
#
#
# For example:
# 192.1.2.34 hpfcrm loghost
#
# See the hosts(4) manual page for more information.
# Note: The entries cannot be preceded by a space.
# The format described in this file is the correct format.
# The original Berkeley manual page contains an error in
# the format description.
#
127.0.0.1 localhost loopback
10.230.3.51 phswaint01 phswaint01.providence.org phswaint01.wa.providence.or
g

After confirming the nslookup responses, as you suggested, I did this:

1. removed the 9 components with swremove:
CMDVIEWSDM A.1.07.00 hp StorageWorks Command View SDM
HPOVLIC 4.31.000 HPOVLIC
HPOVSAMDA 03.10.00.0113 hp OpenView storage area manager HostAgent DIAL
HPOVSAMHA 03.10.00.0113 hp OpenView storage area manager HostAgent Framework
HPOVSAMJR 1.4.1.3 hp OpenView storage area manager embedded JRE
HPOVSAMSG 03.10.00.0113 hp OpenView storage area manager HostAgent SCSI Gateway
SMI-S_VA 1.02.02 hp StorageWorks SMI-S VA
SSLIC 1.0.0.0 HP Storage Software License Manager

2. I then issued the command '/usr/sbin/swagentd -r' and confirmed by PID that I had successfully launched a new swagent daemon:

# ps -ef | grep agent
root 909 1 0 Nov 25 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 12383 11563 0 12:53:17 pts/ta 0:00 grep agent
root 5856 1 0 Nov 25 ? 0:02 /usr/sbin/swagentd -r
#
#
# /usr/sbin/swagentd -r
#
#
# ps -ef | grep agent
root 12385 1 0 12:53:36 ? 0:00 /usr/sbin/swagentd -r
root 909 1 0 Nov 25 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 12387 11563 0 12:53:39 pts/ta 0:00 grep agent

3. I then reinstalled the software ( from the CD directly ) using swinstall:

"swinstall -s/cdrom/CommandViewSDM/hpux/cvsdm_11_00_v10700.depot"

This install failed again with exactly the same error.

Unfortunatly I'm still stuck. Do you have any more ideas?

Thank you.
Matt Powell

Re: Command View SDM - install problem

Karthik S S — Fri, 28 Nov 2003 16:25:35 GMT

Hi,

uname -a is showing the hostname as unknown and I think there lies the problem

# uname -a
HP-UX unknown B.11.00 U 9000/800 1781967605 unlimited-user license

Set the hostname using,

uname -S hostname.

Also verify the swacl command returns the correct hostname using,

swacl -l host

Regards,
Karthik S S

Re: Command View SDM - install problem

Matt Powell — Fri, 28 Nov 2003 16:53:28 GMT

Karthik S S,

Bingo! That was it. My apologies to all for not including the 'uname -a' output earlier.

Interestingly, when I tried to set uname the first time, I got this:

# uname -S phswaint01
Nodename must be less than9 characters

..OK so I did this:

# uname -S phswint1

and added "phswint1" to /etc/hosts as an alias to "phswaint01" ( just in case. )

I did swremove, re-started swagentd, re-attempted the install and Voila! - no errors.

Thanks a ton.. Good catch.

So what are the ramifications of having the "nodename" set to something different than the "hostname"? Should I go back to the WAN people and have the DNS entries changed to the 8 character "phswint1" instead of the 10 character "phswaint01"?

Does it matter really?

Thank you all.

Matt Powell
Providence Health System

Re: Command View SDM - install problem

Karthik S S — Fri, 28 Nov 2003 17:35:38 GMT

Hi,

That is good !!

As far as you have nodename set to less than 8 characters the length of the hostname really doesn't matter. Refer to the followin threads,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=248155

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=86975

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=12784

-Karthik S S