cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to see Tape Drives on RHEL6

scratcher
Level 3

Hi,

I have 2 servers (HPUX and Redhat) connected to 2 partitions on a Quantum i2000, the HPUX has 12 tape drives attached and Redhat (6) has 4.

I moved 2 of the tapes drives from Partiton1 (HPUX) to Partition2 (Redhat) which was successful and I can see 6 drives attached to Redhat and 10 to HPUX from the i2000.

My problem is that although I can see the 2 drives from robtest and /usr/openv/volmgr/bin/scan on the Redhat server they are not being discovered by the Redhat server itself. Ive done numerous Redhat rescans (I am a RHEL admin) but am still unable to see the 2 new tape drives.

Im told that I will need to reboot the Redhat box which I find strange as discovering new LUN's is straight forward but apparently discovering tape drives needs a reboot??

Any information or advice would be appreciated...

Except from /usr/openv/volmgr/bin/scan where HU1145KDDJ and HU1149KWK4 are the new drives.

Device Identifier: "QUANTUM 263105164_LL1           "
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 6
Number of Slots  : 228
Number of Media Access Ports: 12
Drive 1 Serial Number      : "HU1225NW3F"
Drive 2 Serial Number      : "HU1225NW3R"
Drive 3 Serial Number      : "HU1145KDDJ"
Drive 4 Serial Number      : "HU1149KWGC"
Drive 5 Serial Number      : "HU1149KWK4"
Drive 6 Serial Number      : "HU1149KWGJ"
Flags : 0x0
Reason: 0x0

But tpconfig -d only shows 4

# tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   ULTRIUM4-SCSIhcar... hcart3 TLD(0)  DRIVE=2
      /dev/nst0                                                        UP
1   ULTRIUM4-SCSIhcar... hcart3 TLD(0)  DRIVE=1
      /dev/nst2                                                        UP
2   ULTRIUM4-SCSIhcar... hcart3 TLD(0)  DRIVE=3
      /dev/nst1                                                        UP
3   ULTRIUM4-SCSIhcar... hcart3 TLD(0)  DRIVE=4
      /dev/nst3                                                        UP

Currently defined robotics are:
  TLD(0)     robotic path = /dev/sg1

EMM Server = xxxxxxx
 

Thanks...
 

5 REPLIES 5

Marianne
Level 6
Partner    VIP    Accredited Certified

tpconfig will only show what has been configured in NBU.

To see devices seen by OS, use
cat /proc/scsi/scsi 
/usr/openv/volmgr/bin/scan -tape 
(the output in your post shows what is seen from the robot itself, i.e. 'scan -changer')

If the OS sees all drives, re-run the Device Config wizard for this media server.

 

scratcher
Level 3

Thanks Marianne...

As I could see the tape drive from robtest and scan I thought everything was ok, after I looked at the switch config the WWN of the tape drive wasn't in the Redhat server zone so ive added the WWN to the zone and everything is good.

Check everything prior to raising an issue on the Symantec forum (!!) but appreciate the quick response..

 

Thanks.. 

Pawan_Nagra_777
Level 3

Hi,

Please run the below OS command for  detect the devices.

echo 1> /sys/class/fc_host/host1/issue_lip

/usr/openv/volmgr/bin/scan -tape 

Thanks,

 

huanglao2002
Level 6
it is best to reboot your server. and make sure you san connect is ok.

Marianne
Level 6
Partner    VIP    Accredited Certified
Robtest and scan -changer shows what the robot sees on the control path. The 2 commands that I've posted in my previous would've checked the data path, i.e OS -> device connectivity.