Hi Fred,
both client and server sits on AIX 5.2.
fred johanson <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
01/11/2006 11:54 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] ANR1639I
I view the message primarily as a warning to search the activity log to
ensure that nothing funny is going on with that node.
David
>>> [EMAIL PROTECTED] 01/12/06 6:58 AM >>>
Hi David,
Well ... that's what puzzling me actually we didn't change the IP
address
The IP address associated with
Hi David,
Well ... that's what puzzling me actually we didn't change the IP
address
The IP address associated with the node changed. To say it a different
way, the node connected from a different IP address than the one TSM had
stored for it.
We didn;t change any IP related to the node. I've
>>1. Could anyone enligthen me the attributes of some of the nodes that
were
changed automatically without human intervention?<<
The IP address associated with the node changed. To say it a different
way, the node connected from a different IP address than the one TSM had
stored for it. In the exa
Is this box a laptop? Wireless?
At 01:02 PM 1/11/2006 +0800, you wrote:
Hi all,
1. Could anyone enligthen me the attributes of some of the nodes that were
changed automatically without human intervention?
2. Checked from the TSM messages information that this message will not
bring any harm bu
Hi,
I see this in a number of scenarios
- questions to ask are: are there multiple interfaces in this machine/these
machines? Have there been any network routing changes which might coincide
with these? It is part of a cluster?
Take a look a the following to see if
they match:
http://www-1.ibm.
Is the machine part of a cluster ?
This can happen when the cluster fails over and the cluster node
connects to the TSM server with a new active node and hence a new IP
address and GUID.
I have also seen this with multi-honed machines. Ie more than one NIC.
Sometimes, if the routing has changed an
