UNSOLVED

SKT2

updated

18 years ago

S

SKT2

2 Intern

1340 Posts

0

933

March 12th, 2008 13:00

DVS_READY and DVS_UNOPENED

Could some one explain DVS_READY and DVS_UNOPENED?

root [/root] /opt/fc/bin/fcmsutil /dev/td0 get remote all

Target N_Port_id is = 0x615e13
Target state = DVS_READY
Target Port World Wide Name = 0x5006016030603525
Target Node World Wide Name = 0x50060160b0603525

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x616213
Target state = DVS_UNOPENED
Target Port World Wide Name = 0x5006016830603525
Target Node World Wide Name = 0x50060160b0603525

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------

:root [/root] /opt/fc/bin/fcmsutil /dev/td1 get remote all

Target N_Port_id is = 0x625e13
Target state = DVS_UNOPENED
Target Port World Wide Name = 0x5006016130603525
Target Node World Wide Name = 0x50060160b0603525

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------


Target N_Port_id is = 0x626213
Target state = DVS_READY
Target Port World Wide Name = 0x5006016930603525
Target Node World Wide Name = 0x50060160b0603525

Common Service parameters (all values shown in hex):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Version_Hi: 20 Version_Low: 9
BB_Credit: 8 Ciro: 1
Alt_BBcred: 0 Rxsz: 800
Conseq: ff RO_Bitmap: fe
Resolution: 0 EDTOV(ms): 7d0

Vendor version (in hex) 0 0 0 0
-------------------------------------------------------------
  • xe2sdc

    6 Operator

    2831 Posts

    421

    0

    Posted March 13th, 2008 07:00

    Santhosh it looks like this is something you can ask to your HP sales rep ;-)

    docs.hp.com/en/A6826-96009/ch01s08.html

    Unfortunatly I can't read the page, but it looks like a promising result. :D
  • SKT2

    2 Intern

    1340 Posts

    421

    0

    Posted March 13th, 2008 07:00

    that is about just interpretting the LUN h/w path.
  • xe2sdc

    6 Operator

    2831 Posts

    421

    0

    Posted March 13th, 2008 08:00

    I think that you have to ask HP .. since you pasted the output of an hpux command .. and only HP can explain you what the hell it is saying :D

    However let's see if someone can find better answers to your thread.
  • brutus333

    3 Posts

    421

    1

    Posted March 21st, 2008 04:00

    From my experience the DVS_READY means that the storage device allow initiator logins on the port; DVS_UNOPENED may appear in cases where the WWN of the hba is not registered on a Clariion Array or when a DMX storage port (VCM Enabled) is accesible but no device was masked for that particular port or even in cases where a storage port was moved in SAN from one port-id to another so the host does not authenticate it anymore.
    Generally, it means that something is happening with that device but this may only be interpreted on an active device: if the host does not try to acces luns on that specific storage it may be possible that the state of the device to be unopened.
    I guess that this state means that the host did not tried to open (login in fabric terms) the devi ce in the last period of time (AFAIK the hp-ux logins to the device each time it opens it) or tried and failed.
    Hope that this helps.
    Virgil
  • SKT2

    2 Intern

    1340 Posts

    421

    0

    Posted October 4th, 2009 04:00

    FC cable issue