Hi Neil, This sounds like persistent binding is not set on the HBA and causes the OS to keep recognizing it as new and adding it again. I'm not too familiar with how that is setup on Linux, but it should be in your HBA config file.
Good luck! Rusty On Wed, Mar 27, 2013 at 2:07 PM, Neil Conner <n...@mbari.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@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > >
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
