Name resolution is not the issue here, so it is not necessary
(or even advisable) to resolve them all in DNS. Netview
made them into one node because you put the entries in
DNS. It would have done the same whether they were HSRP
or not, just based on name resolution. It will make a router out
of three non-snmp PCs if you resolve them all to the same name.
It probably made separate nodes of them initially because
they were resolved differently and/or because it did not have
proper snmp access to them.
The way I usually go about this, with good results, is:
1) Resolve the loopback or some other stable, unique address
2) Put that address or name in the seedfile
3) Verify SNMP access to the device
4) Put the HSRP addresses, all of them, in the seedfile with %
5) Delete and discover the nodes involved.
6) If the hsrp interfaces don't show up on their own, ping them, or
add them to the seedfile lower down to get netmon to ping them.
When verifying snmp access to the node, here are some tips:
- xnmsnmpconf -resolve <Selection Name> will show you the
community string and ip address Netview assumes for a node.
- xnmsnmpconf -clearC is often necessary to get netmon to reconsider.
- Demandpoll will try all alternates and then update the snmp database
but not always.
- Monitor...MIB Variable..System Info must be able to resolve the
Selection Name to an address before it will work, and then uses the
community that is in effect in the SNMP database, so it is an excellent
test of consistency. If it does not work, then your work is not done.
- If you have address ranges in the snmp database, and the node you
are working on conflicts with that, demandpoll will work, trying
alternates, but it will NOT necessarily add a specific entry to the snmp
database (so the test above will fail). You may need to add the override
entry manually.
- Nodes set up for snmp status polling, either explicitly or by default,
are not going to work with HSRP, because snmp status polling only
works with the interface table, and HSRP interfaces are not in the
interface table.
- HSRP processing requires snmp access to all of the virtual addresses.
This is because the hsrp polling does a get of the sysname through that
address to see which box it is on at the moment. Note also that the
sysnames must be unique, and it would be good if they did not have
blanks, etc in them.
Behavior in these areas changes a little bit with every maintenance
release as things get tightened up. So stay current.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Westphal,
Raymond" To:
"'John.Boswell@us.ngrid.com'" <John.Boswell@us.ngrid.com>, "NV List
<RWestphal@erac.c (E-mail)"
<nv-l@lists.tivoli.com>
om> cc:
Subject: RE: [nv-l] How to
handle HSRP addresses in DNS.
11/06/2002 12:56
PM
Yes. They are all in the netmon.seed file.
Thanks John.
-----Original Message-----
From: John.Boswell@us.ngrid.com [mailto:John.Boswell@us.ngrid.com]
Sent: Wednesday, November 06, 2002 10:23 AM
To: Westphal, Raymond
Subject: Re: [nv-l] How to handle HSRP addresses in DNS.
Have you added all your hsrp ip's to your Monitor special devices\Monitor
HSRP Interfaces under the netmon seed editor???..Unfortunately you have to
manually add each ip address individually....but it will clear up those
type of issues......
From: "Westphal, Raymond" <RWestphal@erac.com> on 11/06/2002 09:43 AM
To: "NV List (E-mail)" <nv-l@lists.tivoli.com>
cc:
Subject: [nv-l] How to handle HSRP addresses in DNS.
Hello Everyone.
NV 7.1.3 on AIX 4.3.3 ML10.
When I run my weekly database cleanup job, ovtopofix routinely complains of
a router that needs to be deleted. I think I may have discovered the reason
for the problem this morning. NV had 8 router objects on the map for this
single router. In all but one of the objects, the Selection Name of the
router was one of the HSRP virtual IP addresses.
As an experiment, I added all the HSRP IP addresses to the /etc/hosts file
with the same name, such as bldgx-router-hsrp. I then demand polled each of
the 8 objects. All of the duplicate objects were deleted and the single
router with the correct Selection Name remained.
I know it is recommended that each interface be in the DNS. The question is
this how to handle the dozen(s) of HSRP virtual IP addresses on all my
routers?
Thanks,
Ray Westphal
Enterprise Rent-A-Car
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|