cancel
Showing results for 
Search instead for 
Did you mean: 

HP ULTRIUM5-SCSI DRIVE IN "DOWN-TLD" STATUS ON NETBACKUP

Dany54000
Level 4

Hi all

I am experiencing a DRIVE's issue with netbackup since I've changed the SFP component.

I have a backup server (Hp ProLiant DL360p Gen8) with "PCIe 3.0 Low Profile x8" card.

The backup server is linked to a Symantec tape library via a ICSI cable + SFP component.

Last week all the "PCIe 3.0 Low Profile x8" LED were flashing, no backups performed and got the following error message:

RD-BMO-BCK01 login: NOHZ: local_Softirq_pending 100
  rport-2:0-0: blocked FC remote port time out: removing target and saving binding

After investigation, I had to replace the SFP component and restart both servers. Now no LEDs are OK but I am still not able to perform backup.

When checking at the "DRIVE MONITOR" menu, I can see that my drive is in DOWN-TLD status. When right-click I can see severals options such as "Up Drive".

Despite of this the "DEVICE/DRIVE" menu report that the drive is enabled.

All my tapes are in ACTIVE mode.

Since I've rebooted I lost the Netbackup's client conenction on my workstation.

Can someone help me to troubleshoot ?

In advance, I thank you for your help.
Damien

1 ACCEPTED SOLUTION

Accepted Solutions

jim_dalton
Level 6

Confused...you have one robot and one drive yet tpconfig says you have two robots and two drives one pair of which is a bit duff. I'd delete the stunits, all drives, all robots, start from scrach, ensure theres one and only one of each at the OS (assuming thats the real number you have) and then and only then recreate netbackup devices, stunits.jim

View solution in original post

11 REPLIES 11

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

Windows, Linux, UNix Media Server?

If I understand correctly, you did not try "Up Drive" yet?. Try it and check if it goes to TLD (UP) state. Drives does not go to UP state automatically once thinks are ok.

If not, check OS debug logs whats the problem - in this cases problem is usually on OS or HW level, probably related to SFP change.

Michla

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
You forgot to mention the OS on your backup server. NBU needs the OS to see and access devices. 1st step to troubleshoot is to check and verify OS connectivity. If we know which OS we can provide better assistance.

Will_Restore
Level 6

rport-2:0-0: blocked FC remote port time out: removing target and saving binding

Certainly looks like Linux message above. 

Run 'scan' command to confirm you can see drive and changer.

If that's good then try Device Configuration Wizard to confirm it also sees the devices.

 

Dany54000
Level 4

Hi all

Thank you for your replies!!

michal1967 and Marianne : The OS is a "Red Hat Enterprise Linux 6"

michal1967: I did an "Up Drive" and the control's status pass from DOWN-TLD to TLD.

Will Restore: can you tell me how to run a 'scan' command and how to launch the "Device Configuration Wizard" because I'm not familiar with Netbackup

In advance, I thank you for your replies.

Damien

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

 I did an "Up Drive" and the control's status pass from DOWN-TLD to TLD.

Does the drive stay UP (TLD) when you start a backup?

To ensure all devices are seen at OS-level, run:
cat /proc/scsi/scsi

scan command is in /usr/openv/volmgr/bin.

Please copy the text output of scan as well as 'tpconfig -l' (in same folder) and post here.

This output will tell us if it is necessary to re-run the Device Config Wizard.
(Will give details if needed.)

 

jim_dalton
Level 6

Did it ever work? If so , apart from described, any other change? Any other devices on the same server...any other port you can zone in the drive and verifty temporarily? (Unclear if its direct attached or not). The long and short as detailed by others is: no point in thinking about netbackup until the OS can use all drives successfully...and for this just use Os cmdline and tar, writing and reading to all drives in turn.Isnt there some OS level cmd needed to make it generate a device tree for what it could believe to be a new drive?Jim

Dany54000
Level 4

Hello Marianne and Jim

I am really sorry for the late reply.

I've succesffully restarted the Netbackup client on my workstation by resolving a network issue on my Backup server.

In fact, I've a BOND interface which include ETH0 and ETH1 which are on two different Vlans.

So I've done some network configuration changes and I have to see if the backups will run.

I'll wait until monday before providing you the two commands.

Damien

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I doubt that the network and drive issues are related.

Dany54000
Level 4

Hello Marianne

 

Please find below the results that you requested (sorry for the presentation, I copied them, get them unorganized and try to organize them by myself).

 

cat /proc/scsi/scsi command result:

Attached devices:

Host: scsi
3 Channel: 03 Id: 00 Lun: 00
 
Vendor: HP       
Model: P420i            
Rev: 5.22
 
Type:   RAID                             ANSI  
SCSI revision: 05

Host: scsi3
Channel: 00 Id: 00 Lun: 00
 
Vendor: HP       
Model: LOGICAL VOLUME   Rev: 5.22
 
Type:   Direct-Access                    ANSI  
SCSI revision: 05

Host: scsi2
Channel: 00 Id: 00 Lun: 00
 
Vendor: HP       
Model: Ultrium 5-SCSI   
Rev: Y65W
 
Type:   Sequential-Access                ANSI  
SCSI revision: 06

Host: scsi2
Channel: 00 Id: 00 Lun: 01
 
Vendor: HP       
Model: 1x8 G2 AUTOLDR   Rev: 4.10
 
Type:   Medium Changer                   ANSI  
SCSI revision: 05

 

scan command result

************************************************************
*********************** SDT_TAPE    
************************
*********************** SDT_CHANGER
************************
************************************************************

------------------------------------------------------------

Device Name  : "/dev/sg1"
Passthru Name: "/dev/sg1"

Volume Header: ""

Port: -1;
Bus: -1;
Target: -1;
LUN: -1

Inquiry    : "HP 1x8 G2 AUTOLDR  4.10"

Vendor ID  : "HP      "

Product ID : "1x8 G2 AUTOLDR  "

Product Rev: "4.10"

Serial Number: "MXA338Z00S"
WWN: ""
WWN
Id Type: 0

Device Identifier: "HP 1x8 G2 AUTOLDR  MXA338Z00S"

Device Type: SDT_CHANGER

NetBackup Robot Type: 8

Removable : Yes

Device Supports: SCSI-5

Number of Drives : 1

Number of Slots  : 8

Number of Media Access Ports: 0

Drive 1 Serial Number      : "HU1334Y14K"

Flags : 0x0
Reason: 0x0

------------------------------------------------------------

Device Name  : "/dev/nst0"

Passthru Name: "/dev/sg0"

Volume Header: ""

Port: -1;
Bus: -1;
Target: -1;
LUN: -1

Inquiry    : "HP      Ultrium 5-SCSI  Y65W"

Vendor ID  : "HP      "

Product ID : "Ultrium 5-SCSI  "

Product Rev: "Y65W"

Serial Number: "HU1334Y14K"
WWN: ""
WWN
Id Type  : 0

Device Identifier: ""

Device Type    : SDT_TAPE

NetBackup Drive Type: 10

Removable      : Yes

Device Supports: SCSI-6

Flags : 0x0
Reason: 0x0

 

tpconfig -l command result:

Device Robot Drive       
Robot                    
Drive                 
Device                           
Second
Type     
Num Index  
Type DrNum
Status  
Comment    
Name                  
Path                             
Device
Path

robot 0  - TLD    -  -  -  -   MISSING_PATH:MXA338Z00P
  drive -    0 hcart2    1      UP  -  HP.ULTRIUM5-SCSI.000  MISSING_PATH:2:0:0:0:HU1334Y15E
robot 1  - TLD    -  -  - -    /dev/sg1
          drive -    1 hcart2    1      UP  -  HP.ULTRIUM5-SCSI.001  /dev/nst0 

 

 

 

jim_dalton
Level 6

Confused...you have one robot and one drive yet tpconfig says you have two robots and two drives one pair of which is a bit duff. I'd delete the stunits, all drives, all robots, start from scrach, ensure theres one and only one of each at the OS (assuming thats the real number you have) and then and only then recreate netbackup devices, stunits.jim

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
I agree. Those MISSING_PATH entries looks like device path entries have changed at OS level. Lack of persistent binding between hba and OS? Best to delete all devices in NBU and re-add.