I wonder if anybody may be able to enlighten me on a problem we
encountered this weekend with ADSM running on an SP2.

In our environment, ADSM 2.1.0.8 is running on a single node of
our SP2. The ADSM node is configured with a direct route to the
rest of our network (via an ATM card). All other nodes in the SP2
have their routes directed through a single network access node.
All traffic going to, or coming from outside of the SP2,
therefore, is directed through this network node *except* for the
ADSM node.

Sunday afternoon our network node crashed, which should prevent
incoming and outgoing traffic to all SP2 nodes except the ADSM
node. The ADSM logs, however, indicate that all scheduled backups
were missed last night. In addition, all communication with the
ADSM server via 'dsmadmc' was impossible. This was true even when
running 'dsmadmc' on the ADSM node of the SP2.

Can anyone explain why the failure of what should be an unrelated
machine within an SP2 complex can affect the operation of ADSM
within the SP2. [Also, note that the ADSM server running on the
SP2 node is *not* backing up any nodes of the SP2, only hosts
running outside of the SP2 complex.]

I'd appreciate hearing any thoughts on this situation. We
originally believed that we had configured this system so that
there are no network dependencies between the ADSM server and the
network access node. As this appears not to be the case, we're
interested in determining where the dependency is. As I recall a
while back someone mentioned that ADSM maintains client IP
addresses within its database. Perhaps this was our point of
failure.

Thanks. -- Tom

"If I could dot the 'i' in a Michigan     Thomas A. La Porte
 game and the good lord came to take me   Archivist, Feature Animation
 the next day ... at least I could        DreamWorks SKG
 die happy." - Beano Cook, ESPN           <tlaporte AT anim.dreamworks DOT com>