scan command produces an error

[UNIX_Cliff]

I have two Solaris 10 servers which I've installed NBU 6.5 Media Server onto, before I add them to our master server I was checking visability of the attached devices (SAN Tape Library), One of them returned what I expected but one returned the following error "Unable to intialize the device mappings table, status = 1" and doesn't show the Netbackup drive type field ? Example below :

Can anyone provide any assistance ? 

 [/usr/openv/netbackup/bin]# scan -tape
************************************************************
*********************** SDT_TAPE    ************************
************************************************************
Unable to intialize the device mappings table, status = 1
------------------------------------------------------------
Device Name  : "/dev/rmt/1cbn"
Passthru Name: "/dev/sg/c0tw100000e00223a5a3l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 3-SCSI  G25W"
Vendor ID  : "HP      "
Product ID : "Ultrium 3-SCSI  "
Product Rev: "G25W"
Serial Number: "HU106443KU"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: Not Found(6)
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c0tw100000e00223a5a3l2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 3-SCSI  G54W"
Vendor ID  : "HP      "
Product ID : "Ultrium 3-SCSI  "
Product Rev: "G54W"
Serial Number: "HU10550703"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: Not Found(6)
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/2cbn"
Passthru Name: "/dev/sg/c0tw100000e00223e414l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 3-SCSI  G63W"
Vendor ID  : "HP      "
Product ID : "Ultrium 3-SCSI  "
Product Rev: "G63W"
Serial Number: "HU10746NBG"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: Not Found(6)
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/rmt/3cbn"
Passthru Name: "/dev/sg/c0tw100000e00223e414l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "HP      Ultrium 3-SCSI  G63W"
Vendor ID  : "HP      "
Product ID : "Ultrium 3-SCSI  "
Product Rev: "G63W"
Serial Number: "HU1074641G"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_TAPE
NetBackup Drive Type: Not Found(6)
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0

[Patrick_Whelan_]

Since you have the luxury of Solaris, what does sgscan show?

[UNIX_Cliff]

Hi, sgscan shows the devices correctly from both servers :

Server A

/dev/sg/c0tw100000e00223a5a3l0: Changer: "HP      MSL6000 Series"
/dev/sg/c0tw100000e00223a5a3l1: Tape (/dev/rmt/1): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223a5a3l2: Tape (/dev/rmt/0): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223a5a3l3: Array-controller: "HP      NS E1200-320"
/dev/sg/c0tw100000e00223e414l0: Tape (/dev/rmt/2): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223e414l1: Tape (/dev/rmt/3): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223e414l2: Array-controller: "HP      NS E1200-320"

ServerB

/dev/sg/c0tw100000e00223a5a3l0: Changer: "HP      MSL6000 Series"
/dev/sg/c0tw100000e00223a5a3l1: Tape (/dev/rmt/1): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223a5a3l2: Tape (/dev/rmt/0): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223a5a3l3: Array-controller: "HP      NS E1200-320"
/dev/sg/c0tw100000e00223e414l0: Tape (/dev/rmt/2): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223e414l1: Tape (/dev/rmt/3): "HP      Ultrium 3-SCSI"
/dev/sg/c0tw100000e00223e414l2: Array-controller: "HP      NS E1200-320"
 

[tjhebert]

We are using Solaris for our master and most media servers as well... Did you set the library and the drives up for use in Netbackup yet using tpconfig?  What is the output for tpconfig -dl?

[MonkFish]

This is UNIX Cliff under a different name (For some reason it says I'm banned from the forum using my old account??) Anyhow we have resolved the issue, or more to the point it went away once we'd sucessfully added the media servers to our master/emm db. Strange as I thought the scan command didn't interogate the emm, I thought onlt tpconfig did that. Thanks for all the questions though.............

[rdhnt]

I Have the same problem, while runing scan I got  NetBackup Drive Type Not Found (6). 
I have update the driver, change tape backup drive, but nothing help.

[Mike_Gavrilov]

Unable to intialize the device mappings table, status = 1   --- I faced this such problem then I have a network problem between media and master (that's why you don't have a device mappings table). Check connection between this servers and restart netbackup.

[Mouse]

update the device mappings file

http://seer.entsupport.symantec.com/downloads/export.asp?ddProduct=NBUESVR&file=Mappings_6_328212.zi...

These instructions assume that NetBackup is installed in the default location of C:\Program Files\VERITAS\.  If NetBackup is installed in a different location, substitute that path for C:\Program Files\VERITAS\ in the instructions below:
 

1. Download and extract the new mappings file to a temporary folder.  This will create two files in the temporary location
 

Readme.txt (this file)
 

external_types.txt
 

2. Copy the external_types.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\.
 

3. Bring up a command window with Start -> Run -> Type "cmd". Enter the following commands in that command window.
 

4. Update the NetBackup Enterprise Media Manager database with the new device mappings version. This only needs to be done once and must be run from the Master Server or the EMM Server.  Use the command format below that corresponds to the installed version of NetBackup:
 

NetBackup 6.5:  C:\Program Files\VERITAS\Volmgr\bin\tpext -loadEMM
 

NetBackup 6.0:  C:\Program Files\VERITAS\Volmgr\bin\tpext
 

5. For Media Servers running 6.0_MP4 and earlier, manually update each Media Server with the new device mappings.  (On Media Servers running 6.5 or 6.0_MP5 and later, this command is not needed since ltid will update the device mappings when it starts.)  This command must be run on each 6.0_MP4 and earlier Media Server that has devices attached:
 

C:\Program Files\VERITAS\Volmgr\bin\tpext -get_dev_mappings
 

6. Restart Device Manager (ltid) on each Media Server.  
 

7. Verify that the version that is now stored in the Enterprise Media Manager database is the same as what is in the file stored on the Media Server:
 

C:\Program Files\VERITAS\Volmgr\bin\tpext -get_dev_mappings_ver


http://seer.entsupport.symantec.com/docs/328212.htm

 

[Ramanc]

If the above did not work, try to rebuild the followings

/usr/openv/volmgr/bin/tpext -get_dev_mappings

Rename the following files:

mv /kernel/drv/sg.conf to /kernel/drv/sg.conf.old
mv /usr/openv/volmgr/bin/driver/st.conf  /usr/openv/volmgr/bin/driver/st.conf.old
mv /usr/openv/volmgr/bin/driver/sg.conf   /usr/openv/volmgr/bin/driver/sg.conf.old
mv /usr/openv/volmgr/bin/driver/sg.links   /usr/openv/volmgr/bin/driver/sg.links.old

2. Run the following commands:
cd /usr/openv/volmgr/bin/driver
/usr/openv/volmgr/bin/sg.build all -mt 0 -ml 16

make sure the 16 value varies as per your system config.

./sg.install
../sgscan conf -v

/usr/openv/volmgr/bin/tpext -get_dev_mappings