Alain,
Regarding your options :
1) Not supported by the lab - from what I've heard or read -, although this is
generaly working quite good - from the point that both NetView servers are in
the same subnet, that you don't forget to use reset_ci and mapadmin commands
2) I never tried this personnaly, nor read references to that kind of config
anywhere. Anybody tried this ? Although, the question is : the topology DB is in
your RDBMS or exported from server A to the RDBMS, to be used by server B - how
do you maintain adequacy with the object databases on both NetView server. Even
if this could work, I guess it will be more difficult to handle than solution 1.
3) forget it.
Where do you see reporting facilities in TIPN ? The only one I know about are
for generating HTML reports about your Tivoli Managed Nodes, etc
Frederic Mottiat - IBM Global Services (PSS-SMNS)
Tivoli Implementation & Services
Email : frederic_mottiat@be.ibm.com
Tel : 02/225 34 08 Gsm : +32 (0)75 388 773
"MENEZES, ALAIN" <alain.menezes@FORTISBANK.COM> on 06/12/99 16:49:25
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Frederic Mottiat/Belgium/IBM)
Subject: Re: Flat file DB --> RDBMS
This is what we would like to do :
NetView Server A : used with flat files and local (secondary) DNS for
Network management and third-party applications
NetView Server B : used as an interface that enables Tivoli to have a view
on network elements. Server B will have all Tivoli components like TIPN,
TFNC, TMNH, .... + its DB. Now regarding the DB there are several options :
1) Regularly copy database from Server A to Server B
2) export Server A DB to Server B's RDBMS DB (assuming this is possible)
3) Define a NFS read-only exported file system from Server A
(/usr/OV/database) that can be connected to by Server B
What do you think ? Personally I solution 3 sounds interesting but solution
2 offers interesting reporting advantages through RDBMS tools ... (although
TIPN offers reporting facilities too)
> -----Original Message-----
> From: Frederic Mottiat [SMTP:frederic_mottiat@BE.IBM.COM]
> Sent: lundi 6 décembre 1999 16:17
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Re: Flat file DB --> RDBMS
>
> Alain,
>
> seems you are doing a lot of NetView activities, these days :-)
> Which is the DB you want to put in a RDBMS ?
>
> Globally, if we talk about NetView and RDBMS, you can :
> - regularly upload your trapd.log in a RDBMS : usefull if you want to know
> a
> little bit more about your event traffic patterns as you'll be able to
> query
> this RDBMS with SQL (and some NetView commands as well)
> - regularly upload the snmp collected data (from snmpCollect) into a RDBMS
> :
> usefull for queries, again
> - store the topology database in a RDBMS : usefull if you want to compare,
> for
> instance, the "evolution" of your network topology. But I would advise you
> not
> to do this, unless you have a very good reason, because the performance
> are up
> to 20 times slower than when using the flat file topology DB.
>
> In any case, I urge you to read the NetView Database Guide. You might have
> not
> received it in hardcopy with your NetView software, so go to
> www.support.tivoli.com : you can download the guide (PDF) from there
> (you'll
> need a userid and password to access some part of this web site, again
> check
> with your Tivoli team)
>
> Regards,
>
> Frederic
>
> Frederic Mottiat - IBM Global Services (PSS-SMNS)
> Tivoli Implementation & Services
> Email : frederic_mottiat@be.ibm.com
> Tel : 02/225 34 08 Gsm : +32 (0)75 388 773
|