ADSM-L

Re: General *SM database/ IP address question

2000-12-18 18:13:37
Subject: Re: General *SM database/ IP address question
From: "Williams, Tim" <Tim.Williams AT FRITOLAY DOT COM>
Date: Mon, 18 Dec 2000 17:13:30 -0600
        I don't think that it really 'stores' that information, per se.
        IT, is however logged in the activity log....
        q actlog.....search=....etc....  (help q actlog)
        hope this helps...




        David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
        12/18/2000 02:24 PM
        Please respond to "ADSM: Dist Stor Manager"
<ADSM-L AT VM.MARIST DOT EDU>@SMTP@Exchange
        To:     ADSM-L AT VM.MARIST DOT EDU@SMTP@Exchange
        cc:

        Subject:        General *SM database/ IP address question

        When you register a node name and the node first contacts the *SM
Server, the server stores the IP address of the client.  Where is this IP
address stored on the server?


        David B. Longo
        Systems Administrator
        Health First, Inc. I/T
        3300 Fiske Blvd.
        Rockledge, FL 32955-4305
        PH      321.434.5536
        Pager  321.634.8230
        Fax:    321.434.5525
        david.longo AT health-first DOT org



        >>> tangeric AT HK1.IBM DOT COM 12/18/00 10:44AM >>>
        Hi All,

        I am upgrading HP-UX11.0  ADSM client from v3.1 to v3.7.2 &
connectAgent
        v2.1.7 to TDP Oracle v2.1.10. (AIX ADSM Server v3.1.2.57)

        After upgrade, dsmc can be invoked and backup/restore is working,
however
        the following message is displayed in dsmerror.log once dsmc is
invoked.

        12/18/00   23:19:00 shl_load() of
        /opt/tivoli/tsm/client/ba/bin/plugins/libPiIMG.sl failed, errno: 215

        IBM support suggests the uninstall of old ADSM client is not clean,
so I
        swremove the 3.7.2 client & TDP Oracle; also manually remove the
/usr/adsm
        & /usr/adsmagent old directories and swinstall TSM 3.7.2 client and
TDP
        Oracle again.

        But there is still the same error message in dsmerror.log when
invoking
        dsmc. Anyone encounters this before? Thanks in advance.


        Regards,
        Eric Tang