HPE EVA Storage
1848718 Members
6766 Online
104036 Solutions
New Discussion

CVSDM doesn't see VA7110

 
SOLVED
Go to solution
Thayanidhi
Honored Contributor

CVSDM doesn't see VA7110

Hi,
I have installed cvsdm 1.07 and never see the
VA7110. ioscan shows the LUN0. But, armdiscover
armdsp shows no devices. There is no switch.
It's connected directly (PRIVATE_LOOP).
I tried removing/Reinstalling.
insf -e, no luck!!
The array seems to be working and no errors if
I connect to the controller's serial i/f.

From hp-ux cvsdm never worked! When I run
HA_Dial_Start it says started. But there is no
corresponding process running.
armdiscover returns and error. dial is not running!
Any help is appriciated with points.

Regards

TT
Attitude (not aptitude) determines altitude.
8 REPLIES 8
Thayanidhi
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

Output from the system.
armdiscover reports error
armdsp gives no output.
ioscan can see LUN0 on VA.

# ./armdiscover
This could take several minutes ...

Remote discovery failed with status: The Dial daemon is not running. The database content may not be current.

# ./armdsp -i

No devices found.

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type
Description
=================================================================
=========
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE
TEAC DV-28E-B
/dev/cdrom /dev/dsk/c0t0d0 /d
ev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP
36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP
36.4GST336753LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 4 0/2/1/0.8.0.108.0.0.0 sdisk CLAIMED
DEVICE HP A6
189B
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 3 0/5/2/0.8.0.110.0.0.0 sdisk CLAIMED
DEVICE HP A6
189B
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0

=========

Regards

TT
Attitude (not aptitude) determines altitude.
Naveej.K.A
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

Very recently I faced the same problem and It was all working fine with a reboot of the host and the disk array... Hope you have already done that and adding up couple of things.

What does dsp -c show...does it shows everything is fine?? I mean the status as good and the link state as up??

ps -ef |grep cmdvwagt
should show the /usr/sbin/cmdvwagt running.

does the /opt/sanmgr/hostagent/config/commIpAddr.txt has your local hosts IP address??

also /opt/sanmgr/hostagent/config/access.dat should contain your host's IP address...

With best wishes
Naveej
practice makes a man perfect!!!
Thayanidhi
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

cmdvwagt is running!!
commIPaddr and access.dat containing host IP.
Any other clue?
I am using cvsdm 1.07
How to find out VA firmware revision?
dsp -c from array looks normal.

Thanks and Regards

TT
Attitude (not aptitude) determines altitude.
Naveej.K.A
Honored Contributor
Solution

Re: CVSDM doesn't see VA7110

Hi,

dsp -c will give you the product id and the battery charger firmware version.

regds
Naveej
practice makes a man perfect!!!
Thayanidhi
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

I think the problem is diald is not starting.
HA_Dial_Start says daild started.
But armdiscover reports daild not running.
ps does not show diald.
If I try to start daild manually,
Illegal Instruction core dump.
A new core file getting created in
/opt/sanmgr/hostagent/sbin (where daild located)
when ever I run HA_Dial_Start.

Thanks in Advance

T.Thayanidhi
Attitude (not aptitude) determines altitude.
Naveej.K.A
Honored Contributor

Re: CVSDM doesn't see VA7110


Your Patch levels!!

CVSDM requires a minimum QPK of September 2001. as far as i remember

regds
naveej
practice makes a man perfect!!!
Thayanidhi
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

All patches are upto date.
(QPK Dec 2003).

Any other clue?

Thanks and Regards

T.Thayanidhi
Attitude (not aptitude) determines altitude.
Naveej.K.A
Honored Contributor

Re: CVSDM doesn't see VA7110

Hi,

Just another try....
connect using the console cable to the controller. delete the lun0 and recreate them with a different size. (say 10 MB)

do an insf -e on the host...

another try...
remove all the packages associated with SDM, reinstall it again.

with best wishes
Naveej
practice makes a man perfect!!!