Forum Discussion

Tatarenko_Maksy's avatar
12 years ago

Drive replace in SL500

Hello,

We replace one drive in SL500

“HU10720K7Y” – new drive.

##################################################

SL500 info

                     Device Id  : 0,1,1,9

                     Drive Type : HpUltrium3

                     Serial Number : HU11014G6C

                     World Wide Name Node : 50:01:04:f0:00:95:9b:b2

                     Port A World Wide Name : 50:01:04:f0:00:95:9b:b3    

                     Port B World Wide Name : 50:01:04:f0:00:95:9b:b4

                    

               Device Id  : 0,1,2,9

                     Drive Type : HpUltrium3

                     Serial Number : HU10729PTG

                     World Wide Name Node : 50:01:04:f0:00:95:9b:b5

                     Port A World Wide Name : 50:01:04:f0:00:95:9b:b6                  

                     Port B World Wide Name : 50:01:04:f0:00:95:9b:b7                    

             

               Device Id  : 0,2,1,9

                     Drive Type : HpUltrium3

                     Serial Number : HU10720K7Y

                     World Wide Name Node : 50:01:04:f0:00:95:9b:b8

                     Port A World Wide Name : 50:01:04:f0:00:95:9b:b9                  

                     Port B World Wide Name : 50:01:04:f0:00:95:9b:ba                    

 

               Device Id  : 0,2,2,9

                     Drive Type : HpUltrium3

                     Serial Number : HU10637425

                     World Wide Name Node : 50:01:04:f0:00:95:9b:bb

                     Port A World Wide Name : 50:01:04:f0:00:95:9b:bc                  

                     Port B World Wide Name : 50:01:04:f0:00:95:9b:bd                  

##################################################

 

After drive replace we can see all drives in Solaris from both host (xgrant1, xgrant3).

 

xgrant1 - Media Server

xgrant3 - Master Server

 

##################################################

xgrant1 can see Drive from NetBackup (scan):

Serial Number: "HU11014G6C"

Serial Number: "HU10729PTG"

Serial Number: HU10637425

 

xgrant1 can't see Drive from NetBackup (scan):

Serial Number: HU10720K7Y

##################################################

xgrant3 can see Drive from NetBackup (scan):

Serial Number: "HU11014G6C"

Serial Number: "HU10729PTG"

Serial Number: "HU10720K7Y"

Serial Number: "HU10637425"

##################################################

xgrant1 can see Drive from NetBackup (sgcan):

/dev/sg/c0tw500104f000959ba9l0: Changer: "STK     SL500"

/dev/sg/c0tw500104f000959bb3l0: Tape (/dev/rmt/6): "HP      Ultrium 3-SCSI"

/dev/sg/c0tw500104f000959bb6l0: Tape (/dev/rmt/7): "HP      Ultrium 3-SCSI"

/dev/sg/c0tw500104f000959bbcl0: Tape (/dev/rmt/0): "HP      Ultrium 3-SCSI"

##################################################             

xgrant3 can see Drive from NetBackup (sgcan):

/dev/sg/c2tw500104f000959ba9l0: Changer: "STK     SL500"

/dev/sg/c2tw500104f000959bb9l0: Tape (/dev/rmt/2): "HP      Ultrium 3-SCSI"

/dev/sg/c2tw500104f000959bbcl0: Tape (/dev/rmt/3): "HP      Ultrium 3-SCSI"

##################################################

We already restart MediaManager #stopltid/ltid.

root@xgrant1 # /usr/openv/volmgr/bin/tpautoconf -t
TPAC60 HP      Ultrium 3-SCSI  R210 7c7u0Ncm01 -1 -1 -1 -1 /dev/rmt/11cbn - -
TPAC60 HP      Ultrium 3-SCSI  R210 7c7u0Ncm02 -1 -1 -1 -1 /dev/rmt/10cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU11014G6C -1 -1 -1 -1 /dev/rmt/6cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU10729PTG -1 -1 -1 -1 /dev/rmt/7cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU10637425 -1 -1 -1 -1 /dev/rmt/0cbn - -

root@xgrant3 # /usr/openv/volmgr/bin/tpautoconf -t
TPAC60 HP      Ultrium 3-SCSI  M6BS HU11014G6C -1 -1 -1 -1 /dev/rmt/0cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU10729PTG -1 -1 -1 -1 /dev/rmt/1cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU10720K7Y -1 -1 -1 -1 /dev/rmt/2cbn - -
TPAC60 HP      Ultrium 3-SCSI  M6BS HU10637425 -1 -1 -1 -1 /dev/rmt/3cbn - -

 

How can we see new drive HU10720K7Y  from host xgrant1 in NetBackup after drive replacing?

All was Ok before replacing drive.

 

 

 

  • If the fibre / scsi bus has reset then a re-boot may resolve it for you to re-establish the connection.

    Otherwise, as Marianne says, check zoning (especially if wwn based)

7 Replies

  • You need to confirm that OS can see replaced drive.

    Was zoning changed/updated?

    Did you run 'devfsadm' on xgrant1?

    Can you see device entry in /dev/rmt for the WWN?

  • If the fibre / scsi bus has reset then a re-boot may resolve it for you to re-establish the connection.

    Otherwise, as Marianne says, check zoning (especially if wwn based)

  • OS can see all drives on both hosts. Cfgadm show all drives.

    Zoning has no change.

    Already use devfsadm and reboot library and hosts.

    xgrant1#  ls -la /dev/rmt
    lrwxrwxrwx   1 root     root          68 Jul 11  2007 4 -> ../../devices/pci@8,600000/SUNW,qlc@2/fp@0,0/st@w500104f000959bb3,0:
    ...
    lrwxrwxrwx   1 root     root          68 Jul 11  2007 5 -> ../../devices/pci@8,600000/SUNW,qlc@2/fp@0,0/st@w500104f000959bb6,0:
    ...
    lrwxrwxrwx   1 root     root          70 Aug 10 15:52 49 -> ../../devices/pci@8,600000/SUNW,qlc@2,1/fp@0,0/st@w500104f000959bb9,0:
    ...
    lrwxrwxrwx   1 root     root          70 Jul 25 12:34 0 -> ../../devices/pci@8,600000/SUNW,qlc@1,1/fp@0,0/st@w500104f000959bbc,0:
     

     

    But NetBackup can't see drive HU10720K7Y (www: 50:01:04:f0:00:95:9b:b9) on  Media Server (xgrant1).

  • If you have already run the wizard and this drive is now in NetBackup can you open up the drive properties (under the devices section of the admin console) and then select xgrant1 and browse to the drive to add it in that way - I doubt it but worth a shot!

    Strange that the O/S sees it but not NetBackup - as if something is blocking it (a NetBackup configuration preventing that path being used twice

    Are you sure that the old drive has been thoroughly deleted from the NetBackup configuration?

     

  • If cfgadm sees the drives but /usr/openv/volmgr/bin/scan does not, then simply rebuild the sgdriver, this is the most common cause.

    Run, on the media srever.

    cd /usr/openv/volmgr/bin/driver

     

    cp sg.links sg.links.safe
    cp sg.conf sg.conf.safe
    ../sg.build all
    modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}'))
    mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old
    /usr/openv/volmgr/bin/driver/sg.install
     
    Thinking this through It would make sense, the WWN of the drive has probably changed, so therefore the sg conf doesn't know about it.
     
    Martin
  • Thanks for recommendations.

    Strange but after Solaris reconfiguration reboot (boot -r) we can see new drive HU10720K7Y (www: 50:01:04:f0:00:95:9b:b9) in NetBackup.

    root@xgrant1 # /opt/openv/volmgr/bin/sgscan
    /dev/sg/c0tw500104f000959ba9l0: Changer: "STK     SL500"
    /dev/sg/c0tw500104f000959bb3l0: Tape (/dev/rmt/6): "HP      Ultrium 3-SCSI"
    /dev/sg/c0tw500104f000959bb6l0: Tape (/dev/rmt/7): "HP      Ultrium 3-SCSI"
    /dev/sg/c0tw500104f000959bb9l0: Tape (/dev/rmt/50): "HP      Ultrium 3-SCSI"
    /dev/sg/c0tw500104f000959bbcl0: Tape (/dev/rmt/0): "HP      Ultrium 3-SCSI"
     

  • Okay - reconfiguration boot is hardly ever necessary on Solaris. 
    The reboot would've performed the following tasks:
    1) perform same actions as devfsadm 
    2) reload sg drivers as per Martin's suggestion.

    Seeing that reboot fixed the problem for you, please mark Mark's post as Solution....