SF5.0 whit MP1 I don't see correctly the LUN

[giacomopane]

Hi, I have a problem with the SFHA for solaris10, the relase is 5.0 mp1.
 

The problem I have is as follows:
I zonate LUN to the server correctly, but the Storage Foundation does not see all the LUN, but only one with many paths.
I already run a "vxdctl enable" but the result does not change

a saint can help me

thanks in advance 

Giacomo

[Gaurav_S]

Hello,

can you provide more inputs ..

-- whether OS can see Luns properly in format command ?

usually the device mappings in 5.0MP1 are done in /etc/vx/disk.info file .... we can rename it & restart vxconfigd but would like to check few things before...

When you say, you are seeing multiple paths with one Lun .... can you try running this

# /etc/vx/diag.d/vxdmpinq  /dev/rdsk/<path>     (where path is the full path what you are seeing for that one Lun)

above command will give you a serial number... can you confirm if you are seeing same serial number or different when you try to access the same lun from different paths ?

Gaurav

[giacomopane]

hello

yes the OS show correctly the disk from "format" and the outuput of  vxdmpinq show me the different serial number

Giacomo

[Gaurav_S · Accepted solution]

I would recommend to clear the device tree

Try out moving disk.info file & restarting the vxconfigd daemon.... check out this technote which has section of your interest

http://www.symantec.com/business/support/index?page=content&id=TECH44060

For systems running VERITAS Volume Manager in a non-cluster environment

a. Remove the corrupted /etc/vx/disk.info file:

# rm -f /etc/vx/disk.info  ( I would recommend to move it rather then removing it)

b. Restart vxconfigd:

# /sbin/vxconfigd -k

For systems running VERITAS Volume Manager in a VERITAS Cluster Server environment

a. Freeze all the service groups running on the system that has Volume Manager resources:

    #  hagrp  -freeze  <service_group_name>

b. Remove the corrupted disk.info file:

   #  rm -f  /etc/vx/disk.info

c. Restart vxconfigd:

   #  /sbin/vxconfigd -k

d. Unfreeze the service groups:

   #  hagrp  -unfreeze <service_group_name>

For systems running Cluster Volume Manager

a. Stop the cluster on the local node:

    #  hastop -local

b. Remove the corrupted disk.info file:

   #  rm -f  /etc/vx/disk.info

c. Restart vxconfigd:

   #  /sbin/vxconfigd -k

d. Start the cluster on local node

   #  hastart

Hope this helps...

Gaurav