I've seen our RHEL5 server running Qlogic HBAs lose information about our 
Quantum i6000 tape library which is Fibre Channel.

Typically it appears the device simply is lost and a full reboot of the media 
server would resolve it but of course you can't always reboot the media server.

Since we have redundant HBAs in our media server (for disks - tapes can't be 
redundant on our library) I simply reset the HBAs one at a time and that seems 
to resolve it.

I've used the script from Qlogic to do the reset:  
/root/qlogic/ql-dynamic-tgt-lun-disc-2.5/ql-dynamic-tgt-lun-disc.sh.   You can 
download the RPM for that from their site.

The script tells you not to have an I/O going but again so long as the disks 
you're using are on redundant paths (i.e. using Linux multipath or EMC 
PowerPath or some other multipathing) it actually resets the cards one at a 
time so doesn't impact I/O to disks (except a momentary performance drop).

We have our master on RHEL6 and I've not seen this behavior there very often 
but then again I'm more likely to boot the master since it ONLY does NetBackup 
as opposed to the media server which runs major DBs.





-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Neil 
Conner
Sent: Wednesday, March 27, 2013 3:12 PM
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: Re: [Veritas-bu] Fiber channel robot device numbers auto-incrementing

Forgot to mention:  The media server is an HP Proliant DL380p Gen8 with an HP 
QLogic Fibre Channel HBA.


On Mar 27, 2013, at 12:07 PM, Neil Conner <neil AT mbari DOT org> wrote:

> Environment:
> NetBackup 7.1.0.4
> RHEL6 master and media server
> Overland Storage FC Neo 8000e tape library (tld)
> LTO5 tape drives
>
> Our new tape library has frozen a couple of times and needed to be rebooted.  
> When it comes back online, the media server assigns the robot a new device 
> name which means NetBackup can't talk to it any more and all the tape drives 
> are down'd until the robot is reconfigured with the new device name. Major 
> PTA.
>
> output from scan:
> Device Name  : "/dev/sg6"
> Passthru Name: "/dev/sg6"
> Volume Header: ""
> Port: -1; Bus: -1; Target: -1; LUN: -1
> Inquiry    : "OVERLANDNEO Series      0701"
> Vendor ID  : "OVERLAND"
> Product ID : "NEO Series      "
> Product Rev: "0701"
> WWN          : ""
> WWN Id Type  : 0
> Device Identifier: "OVERLANDNEO Series"
> Device Type    : SDT_CHANGER
> NetBackup Robot Type: 8
>
> Prior to yesterday's reboot, the Device Name and Passthru Name were both 
> "/dev/sg5", and prior to that they were both "/dev/sg4", etc.
>
> Does anyone know how to keep the device name fixed in RHEL6?
>
> Thanks,
> Neil
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu




Athena(r), Created for the Cause(tm)
Making a Difference in the Fight Against Breast Cancer

---------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
information and is for the sole use of the intended recipient(s). If you are 
not the intended recipient, any disclosure, copying, distribution, or use of 
the contents of this information is prohibited and may be unlawful. If you have 
received this electronic transmission in error, please reply immediately to the 
sender that you have received the message in error, and delete it. Thank you.
----------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu