Thanks for the confirmation. In our other frame with drives, there is an
Ethernet cable going to a switch besides the TS3000 console. It has a 172
address (we don't use it), so it must be the call home/maintenance
connection.
FWIW, on Linux systems, the drives used for the control paths appear v
Yes and No
It is used to access the Specialist web interface.
The IP info is set from the front console.
We don't do this, but I believe you also use the ethernet interface to have the
3584 access a Master Console for dial home. See the topic "Remote Support
through a Master Console" in the 35
Am I correct that the IP connection in the L23 frame is used purely for
the Tape Library Specialist web interface, not like the 3494 where its IP
connection was also used for management interface with the TSM servers?
My network folks want to change/move the address.
--
*Zoltan Forray*
TSM Softwa
Thanks Skylar,
The is no NFS mount on this server and is does not use and external directory
for identification & authentification either.
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
- Mail original -
De: "Skylar Thompson"
À: ADSM-L@VM.MARIST.EDU
Envoyé: Jeudi 15 Mai 2014
A couple things I can think of:
* Do you have any stale NFS mounts on your TSM server? Even if the FILE
volumes are not on NFS, I've seen slow access on any file if there's a
hung mount.
* Do you use a central directory server (NIS, LDAP, etc.) for this system?
If directory lookups are slow,
Thanks for all the advice, I am talking about WAN traffic.
Thomas Taylor
System Administrator
Jos. A. Bank Clothiers
Cell (443)-974-5768
From:
Bent Christensen
To:
ADSM-L@VM.MARIST.EDU,
Date:
05/15/2014 08:54 AM
Subject:
Re: [ADSM-L] Bandwidth
Sent by:
"ADSM: Dist Stor Manager"
Hi T
Hi all,
I've recently done some upgrades to a customer's TSM server and I'm now
experiencing some strange behabiour with long delay for mount of FILE storage
pools volumes.
Delay is 1 minute or more, and it seems it does not depend on usage (mount for
client sessions or server processes).
Do
Hi David,
Upgrade (rpm -U) is working begining with client 6.3. I guess it has been
changed to enable/facilitate autodeployment.
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
- Mail original -
De: "David E. Ehresman"
À: ADSM-L@VM.MARIST.EDU
Envoyé: Jeudi 15 Mai 2014 15:04:31
For Linux clients, I've always had to remove (rpm -e) and install (rpm ivh or
rpm -Uvh) the client rpms. If upgrade now works without a remove first, I'd
love to know at what client level that started.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU]
Hi Thomas,
Just to be sure, are you talking about LAN or WAN backup traffic? Is your
bottleneck in the TSM-client-to-switch connection or the switch-to-tsm-server
connection?
If TSM is saturating your WAN lines, looking into dedup and compression is the
best you can do. If your problem is with
Thomas,
To get some immediate consider using the "randomize" setting on the TSM server
combined with an extended backup window and limiting the number of machines
that can backup concurrently with the "maxschedsessions" setting.
This will allow you to have some control over how many clients back
11 matches
Mail list logo
