Paul Caron caron@sig.com writes:
The problem we are experiencing is that the devices on our filers which represent the SAN attached tape drives (shown by sysconfig -t) get randomly recreated every time the Crossroads reboots.
This was a problem that I encountered early in ONTAP 6.0.x (and 6.1.x to?) although sporadic, often enough to write a perl script to reset the tape aliases a few times a week.
The LUN did not change, but the filers decided to rename the the aliases after the fc-card was reset or unplugged from the Brocade. (The last was a precautionary action to prevent the filer from panic'ing from a SCSI reset when the bridge or library was rebooted)
It appears as though the Crossroads is not presenting the tape drives available on the ATL P7000 in the same order every time it reboots.
Although I am using the STK (Crossroad) 3250, I would believe that the menus/commands are similiar.
Have you set any values in the "Fibre Channel to SCSI mapping"/ "Mapping Table# ?? Does the values change after reboot? What about "Display Attached SCSI Devices", does this change between reboots?
Has anyone else run into this situation? Is there any way of compensating for this on the Netapp filers?
Without the Crossroads not keeping the LUN values stable, you are out of luck. As far as I know there is no way of keeping track of a changing LUN.
BTW, we have received suggestions regarding using the Netapp "storage alias" and "storage unalias" commands. However, since the Galaxy backup software relies on the actual device names (i.e. rst0l, nrst0l, urst0l, etc.) this hasn't helped us so far.
The Filer actually sees the real LUN value, but you may assign an alias, such as st01 st02 ... the device names rst02,nrst02,urst02 etc gives the device functionality.
To sum up: If the Crossroads keep changing the LUN values, I would suggest you bring your vendor to bring this case directly to Crossroads.
>>>>>>>>>>>>>.rune