ADSM-L

Re: [ADSM-L] Looking for SAN/tape experts assistance

2010-09-23 09:28:26
Subject: Re: [ADSM-L] Looking for SAN/tape experts assistance
From: "Strand, Neil B." <NBStrand AT LEGGMASON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 23 Sep 2010 09:27:25 -0400
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.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Wednesday, September 22, 2010 2:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Looking for SAN/tape experts assistance

I have mentioned in previous posts that we are putting up 2-new RH Linux
based TSM server . These are the first of my existing 5-Linux servers to
use EMC SAN storage.

With every new adventure, we get new problems.  This one is driving
everyone crazy and hope someone out there can point us in the right
direction.

We have seen posts in ADSM-L that sorta talk about it, but nothing that
explains what is going on with us or how to resolve it.

Both new servers have been configured identically when it comes to the
OS
(RedHat Linux 5.5  kernel 2.6.18-194.11.3.el5) software and other
hardware
supporting software (EMC Powerpath and IBM lin_tape drivers - 1.41.1 for
the TS1120/1130 drives)

The problem is this.

Every time we reboot one of the new servers,  the values in
/proc/scsi/IBMtape is different in the assignment of /dev numbers to the
drives.  It seems to find the tape drives in a different order each
time.
None of my 5-production nor the other new TSM server have this problem
(I
have rebooted the 2nd new server 4-times and the /dev/IBMtape? values
stay
the same).

When looking through the "fixlist" for lin_tape (usually
engineering-speak), we saw this interesting entry at the 1.37 level:

Removed persistent naming script in favor of new method


Questions come to mind about things like "what naming
script"......."what
new method" ....   "could this possibly be related to what we are
experiencing"?

We have spent all day trying to figure this wrinkle out.  Any
suggestions
are greatly appreciated.
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

<Prev in Thread] Current Thread [Next in Thread>