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
|