cancel
Showing results for 
Search instead for 
Did you mean: 

How to realize some concepts about the vmoprcmd output

liuyl
Level 6

1)  What the difference about the DRIVE STATUS between the -dp ds and devmon ds ?
2 ) Does the label "-" mean there is no tape media in the tape drive ?
3)  Does the Ready "No" mean there is no tape media or an unlabeled tape media in the tape drive ?
4)  Why sometime the vmoprcmd -up <drive_num> would failed with "Invalid Drive Number" ?

#
#
# vmoprcmd -h gwzycdb3 -dp ds

DRIVE STATUS

Drv DrivePath Status Label Ready
0 /dev/nst2 UP - No
1 /dev/nst3 UP Yes Yes
2 /dev/nst1 UP Yes Yes
3 /dev/nst0 UP Yes Yes
4 /dev/nst7 UP - No
6 /dev/nst5 UP Yes Yes
7 /dev/nst4 UP Yes Yes
#
#
# vmoprcmd -h gwzycdb3 -up 0
Invalid Drive Number
#
#
#
# vmoprcmd -h gwzycdb3 -dp ds

DRIVE STATUS

Drv DrivePath Status Label Ready
0 /dev/nst2 UP Yes Yes
1 /dev/nst3 UP Yes Yes
2 /dev/nst1 UP - No
3 /dev/nst0 UP Yes Yes
4 /dev/nst7 UP - No
6 /dev/nst5 UP Yes Yes
7 /dev/nst4 UP Yes Yes
#
#
#
# vmoprcmd -devmon ds|grep -Ei "avr|down|pen|rest"|grep gwzycdb3
gwzycdb3 /dev/nst2 DOWN-TLD
#
#
#
# vmoprcmd -h gwzycdb3 -dp ds

DRIVE STATUS

Drv DrivePath Status Label Ready
0 /dev/nst2 UP - No
1 /dev/nst3 UP - No
2 /dev/nst1 UP Yes Yes
3 /dev/nst0 UP Yes Yes
4 /dev/nst7 UP Yes Yes
6 /dev/nst5 UP Yes Yes
7 /dev/nst4 UP Yes Yes
#
#
#
# vmoprcmd -h gwzycdb3 -dp ds

DRIVE STATUS

Drv DrivePath Status Label Ready
0 /dev/nst2 UP - No
1 /dev/nst3 UP - No
2 /dev/nst1 UP Yes Yes
3 /dev/nst0 UP Yes Yes
4 /dev/nst7 UP Yes Yes
6 /dev/nst5 UP Yes Yes
7 /dev/nst4 UP Yes Yes
#
#
#
# vmoprcmd -devmon ds|grep -Ei "avr|down|pen|rest"|grep gwzycdb3
gwzycdb3 /dev/nst2 DOWN-TLD
#
#
#
#
# vmoprcmd -h gwzycdb3 -up 0
#
#
#
# vmoprcmd -devmon ds|grep -Ei "avr|down|pen|rest"|grep gwzycdb3
gwzycdb3 /dev/nst2 DOWN-TLD
#
#
#
# vmoprcmd -devmon ds|grep -Ei "avr|down|pen|rest"|grep gwzycdb3
gwzycdb3 /dev/nst2 DOWN-TLD
#
#
#
# vmoprcmd -h gwzycdb3 -dp ds

DRIVE STATUS

Drv DrivePath Status Label Ready
0 /dev/nst2 UP Yes Yes
1 /dev/nst3 UP Yes Yes
2 /dev/nst1 UP Yes Yes
3 /dev/nst0 UP Yes Yes
4 /dev/nst7 UP Yes Yes
6 /dev/nst5 UP Yes Yes
7 /dev/nst4 UP Yes Yes
#
#
#

4 REPLIES 4

Mike_Gavrilov
Level 6
Partner    VIP    Accredited Certified

@liuyl wrote:

1)  What the difference about the DRIVE STATUS between the -dp ds and devmon ds ?

 

1) They simply have different fields:

[root@media01 ~]# /usr/openv/volmgr/bin/vmoprcmd -devmon ds -h media01

DRIVE STATUS

Drive Name Label Ready RecMID ExtMID Wr.Enbl. Type Host Status DrivePath
=============================================================================
HPE.ULTRIUM8-SCSI.000 No No No hcart2 media1


 

# /usr/openv/volmgr/bin/vmoprcmd -dp ds -h media01

                                  DRIVE STATUS

Drv DrivePath                                             Status  Label  Ready

  5 /dev/tape/by-path/pci-0000:3b:00.0-fc-0x511419b3ec3d1   UP     Yes    Yes

 

2 ) Does the label "-" mean there is no tape media in the tape drive ?

Yes


3)  Does the Ready "No" mean there is no tape media or an unlabeled tape media in the tape drive ?

Yes


4)  Why sometime the vmoprcmd -up <drive_num> would failed with "Invalid Drive Number" ?

It might be because of some inconsistency and require additional troubleshooting. Try to use "vmoprcmd -upbyname " instead

 

 

 

The difference about the  DRIVE  STATUS  I mean  is  that  the  -dp  ds  is  UP ,   versus  the -devmon. ds is  DOWN-TLd  for  the same TD. 

Mike_Gavrilov
Level 6
Partner    VIP    Accredited Certified

These values come from different places.

This is tpconfig value -drstatus UP|DOWN|DISABLED

Sets the initial status of the tape drive to the UP, DOWN, or DISABLED state. Discovered drive paths are enabled (UP) by default. An administrator or operator can disable or configure the drive path up/down. The user can also perform this action with options in the Device Management window.

And it represents physical state of the drive/path

States DOWN-TLD, AVR, SCAN-TLD and so on are logical. For example your tape library robot may become unavailable  and the drives will change state to AVR but all physical paths will remain available and UP. Hope it makes sense.

 

 

 

I would never link the DRIVE STATUS in vmcmd to the corresponding DRSTATUS in tpcmd.
1) tpcmd is to be with the physical hardware interaction
2) vmcmd is to be with the logical database interaction

But it seems that the -dp ds with vmoprcmd does get the DRSTATUS from its tpconfig -l!