nv-l
[Top] [All Lists]

RE: [nv-l] ovsnmp.conf

To: <nv-l@lists.tivoli.com>
Subject: RE: [nv-l] ovsnmp.conf
From: "Barr, Scott" <Scott_Barr@csgsystems.com>
Date: Tue, 1 Oct 2002 07:46:19 -0500
My psychiatrist says I can't learn any more new programming languages

Sorry, a quick little script is not something I can write, they are a struggle 
for me. Fortunately, Paul is slightly MORE depraved. Thanks muchly Paul.

> -----Original Message-----
> From: Paul Stroud [mailto:pstroud@bellsouth.net]
> Sent: Monday, September 30, 2002 5:39 PM
> To: Barr, Scott; nv-l@lists.tivoli.com
> Subject: Re: [nv-l] ovsnmp.conf
> 
> 
> All,
> Heres a quick ugly hack to do just that.  Copy the ovsnmp.conf file
> from one machine to the other(just not into the /usr/OV/conf dir as
> xnmsnmpconf will overwrite that file as you add new nodes). Anyhow,
> it will complain about the nodes it cannot and will not add them, but
> it should add everything else, including wildcards and ranges.
> 
> #!/usr/bin/perl
> 
> # passed the full path to the ovsnmp.conf(ie /tmp/ovsnmp.conf) it will
> # parse the file and build the new entries.
> 
> # check for command line arg and die if none
> if (!$ARGV[0]) {
>    print "Usage: $0 /path/to/ovsnmp.conf\n";
>    exit;
>    }
> # open the file
> open (SNMPDATA, $ARGV[0]) || die "Unable to open $ARGV[0]!\n";
> while(<SNMPDATA>) {
>    chomp;
>    # don't try to add the default or comments
>    if ($_ !~ /^\*\.\*\.\*\.\*/ && $_ !~ /^#.*/) {
>        `/usr/OV/bin/xnmsnmpconf -create $_`;
>       }
>    }
> # close the file
> close(SNMPDATA);
> 
> Paul
> 
> 
> On Monday 30 September 2002 17:07, Barr, Scott wrote:
> > Hello forum.....
> >
> > I am trying to find a way to keep ovsnmp.conf sync'd 
> between two similar,
> > but not identical systems. (one is v7.1.1 and the other is 
> 7.1.2) The
> > discovery on the two boxes uses the same seed files 
> however, there are a
> > few nodes not reachable from one of the boxes. When I used 
> the xnmsnmpconf
> > -export <filename> and then move <filename> to the other 
> server and do
> > xnmsnmpconf -import <filename> it dies with a node not in discovery.
> > (invalid destination in hosts database)
> >
> > At issue here is this: We use the alternate community names 
> table. As a
> > result, when we do discovery, we pound on the unix servers 
> with several
> > different community names (results are the mib2 sub agent 
> on the solaris
> > box dies as documented on several occasions here) In addition, the
> > community strings used in communityNames.conf get placed into the
> > /var/adm/messages log on each of the Sun boxes, thus giving 
> our sysAdmins
> > in clear text ALL of the community strings we are using. 
> So, I manually
> > updated ovsnmp.conf using xnmsnmpconf but I am trying to 
> avoid having to
> > manually add 225 servers to the other two NetView servers I 
> have running
> > and I am looking for a way to keep them in sync.
> >
> > I am tempted to whack /usr/OV/conf/ovsnmp.conf_db and copy 
> it from the
> > other system, but I know Leslie will scold me if I do.
> >
> >
> >
> > Scott Barr
> > Network Systems Engineer
> > CSG Systems
> > Phone: 402-431-7939
> > Fax: 402-431-7413
> > Email:  <mailto:Scott_Barr@csgsystems.com> Scott_Barr@csgsystems.com
> 

<Prev in Thread] Current Thread [Next in Thread>
  • RE: [nv-l] ovsnmp.conf, Barr, Scott <=

Archive operated by Skills 1st Ltd

See also: The NetView Web