That is how it handles the duplicates - at each poll, it moves it to the
one it is polling, if it is up. What 'up' means depends on whether it is
being pinged, or polled via snmp. If it is up (according to snmp) on
both boxes, you would be better off letting it ping for status, probably.
Then it should help if you take advantage of the 6.0.2 simulated hsrp
support. Put the duplicate addresses in the seedfile with % so it
knows that they are intentional duplicates. If the box that answers
the snmpget of the sysName does not change on the 5-minute
hsrp poll, then it won't be moved. That's how it works in Theory
(that small town in Texas .....)
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Tremblay, David A." <dtremblay@JHANCOCK.COM>@tkg.com on 06/14/2001
11:36:00 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: "Lemire, Mark" <mlemire@JHANCOCK.COM>, "Kenney, John"
<jkenney@JHANCOCK.COM>
Subject: [NV-L] NetView 6.0.2 Behavior question?
After further investigation yesterday, it was discovered that in 2
separate instances we have noticed a behavior that does not happen on our
NV
5.1.1 server that is happening on our NV 6.0.2 server and was wondering if
anyone else has experienced similar behavior with 6.0, 6.0.1 or 6.0.2?
First off, we turned off HSRP on the NV 6.0.2 server where this
occurred and believe that HSRP was not an issue when I wrote about it
yesterday. What we experienced was NV getting confused when it
encountered two servers that had Veritas First Watch product installed on
them. Both servers have 2 cards on them, a HME card and a Quad card in
which 3 of the interfaces are configured. There are duplicate IP addresses
on these cards which are only to be used in a failover situation. Nothing
as changed within in our environment except the addition of the NetView
6.0.2 product on our staging server.
Netview seems to be flipping the interfaces back and forth between
the primary/secondary server and switching their interfaces on the map
every
time the device is polled.
This is causing some confusion for our Operators since in addition
are receiving interface up and down alarms for the "flipping" interfaces.
(No pun intended)
Anyone else seen this or know how to correct this? If not, I will
open a PMR.
Dave
David A. Tremblay John Hancock Financial Services
Lead Systems Analyst Corporate Technology Services
200 Berkeley Street B5-02
Boston, MA 02117
Tel: (617)572-1703
E-Mail: dtremblay@jhancock.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|