Leslie, not sure if you directed that at me or the original poster. I have
talked to support about it, but I don't have the issue regularly, just once
in a while when I am usually doing install type work so its not a huge
problem for me.
-----Original Message-----
From: Leslie Clark [mailto:lclark@us.ibm.com]
Sent: Wednesday, November 14, 2001 10:52 PM
To: IBM NetView Discussion
Subject: RE: [NV-L] Cisco Content Switches.
Can I ask if this is something you reported to the Support center? In
my experience, at current code levels, Netview has gotten good at
merging nodes that it found one way and then another way. It complains
of duplicates, deletes the one you just tried to add, but there is another
one in the map somewhere already, maybe named for another
address than the one you meant to discover it by. In that case I either
delete that one as well and force discovery by the address I want (the
one which resolves), or add name resolution for the address it found
it by. If it has interface hints on hand, and I put one of those addresses
in the seedfile, it generally completes the node quickly and merges
the addresses.
In the case of things with virtual addresses, it is important to discover
them by a 'real' address. Try putting the ethernet interface or the
loopback interface or some such in the seedfile. A lot of these
mysterious deletions have turned out to be caused by the node
having been discovered by an address that is not in the address
table on the device.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Barr, Scott"
<Scott_Barr@csgsy To: "'IBM NetView
Discussion'"
stems.com> <nv-l@tkg.com>
Sent by: cc:
owner-nv-l@tkg.co Subject: RE: [NV-L] Cisco
Content
m Switches.
11/13/01 01:51 PM
Please respond to
IBM NetView
Discussion
use ovobjprint -s | grep <devicename> and you will see interfaces in the
database that belong to the box you deleted from the map. Netview deletes
the node as soon as it rediscovers because the database has those
interfaces
already. I consider this a bug personally. The only recourse I know of is
to
use the <unsupported> ovwdbdmap -d <objectnumber> command. Good luck. I
have
a router in this condition right now too. I tried ovtopofix -A and
ovmapcount -a as my usual attempts to fix it after deleting the interfaces.
No change.
-----Original Message-----
From: Westphal, Raymond [mailto:RWestphal@erac.com]
Sent: Tuesday, November 13, 2001 12:47 PM
To: NV List (E-mail)
Subject: [NV-L] Cisco Content Switches.
Hello Everyone.
NetView for UNIX 6.0.2 w/ IY22983 netmon fix on AIX 4.3.3 w/ ML 9.
NetView is having some trouble dealing with the Cisco Content Switch
(Arrowpoint apCS50). Both TAC and local Cisco people have told us that VIPs
do not reliably respond to ICMP polling. So I unmanaged the VIP interface
objects on each CCS.
I then decided to use SNMP status polling for the CCS. I added the $node
entry to the netmon.seed file. I removed them from the map (a big mistake).
NetView rediscovered them but deleted them as soon as I demand polled one
or
the other switch. NetView complained of a duplicate address.
Can anyone out there share their technique for managing these things?
Thanks in advance!
Ray Westphal
Enterprise Rent-A-Car
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|