Hi George,
The udev config files used by Lin_tape allow for tieing specific device names
to attributes of the tape drives like their serial number, or perhaps LUN
number.
I was a bit surprised to see that all EMC EDL devices assigned to a given path
are presented all on the same WWNN, differi
Thx for the clarification, been a while (we use AIX so the ODM takes
care of it all). To the point earlier FC devices changing order can be
remediated fairly easy.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Strand, Neil B.
Sent: Tuesday, Oc
The zoning process simply associates a server HBA port on the server
with the HBA port on the disk device.
Persistent binding is a function of the OS and HBA drivers on the
server. Within the server configuration, the HBA must be told that a
device with a particular ID (i.e. /dev/rmt1) is always
George,
Thanks for responding with your expertise and obvious hard work on
addressing these short-comings.
Yes, I would be interesting in seeing what you have written. You can
contact me - off-list..
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Offi
This may be a dumb response but this behavior is similar in Windows and
or Solaris, I thought if the person that zoned the device enabled
persistent binding these devices would not re-order on but as it scans
the FC.
Did I completely miss it?
-Original Message-
From: ADSM: Dist Stor M
Well, I've gotten a little further along. The drives and paths have been added
to TSM and TSM is reporting all the information correctly (SN, Support RW
types, WWN's, etc.). Still haven't tried opening the drives and
reading/writing tapes (next step). The init script I use to load lin_tape is
Sergio,
Thanks for the experience/guidance/details. Looks like we may be heading
in this direction, although we aren't sure why.
To update our situation.
After doing some digging and pure-luck, I discovered one of the fibre
connections had gone "amber". Not sure why since when we cabled th
Thanks for the info and examples.
However, I am at a loss to understand why I need this, now. Especially
when 2-identical (well, I guess something is different ;--) servers are
acting differently. I have never had to do this with *ANY* other of my
now 7-servers. Unless hardware changed, a reboo
I'm doing this work right now for a big project here. My first endeavor into
Linux.
The lin_tape drivers for 6.2 will require a .rules file in /etc/udev/rules.d
(or wherever your udev stuff lives) mainly because of the instance owner/group
requirements to run 6.2 dsmserv processes. Unless y
Zoltan,
Look at how udev config and rules are configured. It may be that the
PowerPath installation affected the configuration.
Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic
There is a "by-id" section in the IBM Tape device driver installation and user
guide (for LTO). Looks like it hooks into the RHEL udev stuff.
I would personally try to find the same guide for TS1120 and send you a link,
but I'm fighting an EDL problem at the moment.
Thanks,
[RC]
On Sep 22, 2
11 matches
Mail list logo
