Thank you,

for your expansive explanation. I will check all logs, drives and
microcodes.

kind regards
Michael Garnebode



             Richard Sims
             <rbs AT BU DOT EDU>
             Sent by: "ADSM:                                            To
             Dist Stor                 ADSM-L AT VM.MARIST DOT EDU
             Manager"                                                   cc
             <[email protected]
             .EDU>                                                 Subject
                                       Re: [ADSM-L] Import node failed
                                       with ANR1366W
             15.02.2006 14:07


             Please respond to
             "ADSM: Dist Stor
                 Manager"






On Feb 15, 2006, at 7:33 AM, Michael Garnebode wrote:

> I have seen this description of the problem but the customer says
> he have
> nothing changed.
>
> I can't check this.
>
> any other idea ?

Michael -

A customer who expects systems programmer support must make it
possible for the systems programmer to provide that support. A
minimum requirement is the provision of detailed system configuration
information, including adapter cards in use, drivers in effect, and
firmware & driver levels. When problems occur, you need access to
system problem logs (e.g., AIX Error Log, Windows Event Log). Lacking
basic information, you cannot possibly provide meaningful support for
that customer.

The missing context in this problem may be revealing. We don't know
the reason for the Import Node, but it is often a step in populating
a new TSM server, in transitioning from a different server. If that's
the case, then this would be a new system which had not yet been
fully exercised - and which might be using an incorrect driver or
two. If an Adaptec card is in use, see the List archives for past
issues involving them.

Though no person may have changed things in the operating
environment, conditions can change within the system and cause it to
do unexpected things, as in choose an improper device driver. And
there are situations where "nothing changed" is a bad thing, meaning
that the customer should, over time, have reacted to background error
messages or erratic behavior and upgraded software or firmware to
resolve them.

I know this is largely generic advice, but the situation is vague and
there are no List archive accounts of problems like this; so it's
largely a matter of getting the customer to cooperate if they
seriously seek resolution.

    Richard Sims