I'm with Allen. In 10 years of TSM work with both SCSI and FC Libraries and drives, I've never had to restart TSM on AIX to add drives and paths one by one.
I also don't mess with TSM Devices since TSM 4.2 on AIX either. I just run cfgmgr, then define the drives and paths. I have used an Exabyte Library (well, that's using the term "used" loosely, it stunk), and several 3584's. Something isn't getting adjusted right in the TSM database, or it's having a hard time picking up the device serial number and/or WWN (at least that's what I would suspect). See Ya' Howard Coles Jr. John 3:16! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen S. Rout Sent: Thursday, January 19, 2012 8:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Re: Drive and Path Definition On 01/18/2012 06:28 PM, David Bronder wrote: > Richard Rhodes wrote: >> >>> In the past we've never had to restart TSM to add a new drive. As >>> long as the drive was discovered and available at the AIX layer, we >>> could define the new drive. Has this changed with v6.2.x? > > Seriously? Is this behavior due to changes in TSM 6.x, or has it > always been this way for SCSI-style (smcX) libraries? > > I've never had this issue with my 3494 library and any TSM version > from ADSM 2.1 through TSM 5.5. > "Me too"; 3494 and 3584 both, I've not needed to restart TSM to begin accessing new devices. - Allen S. Rout DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail.