My advice is to open your PMR. I thought there was something about
unmanged staus being changed in 6.0.2 but I don't personally work on netmon
or ipmap. I've already published the list of fixed APARs . If you don't
think your problem is resolved by one of them or you don't wnat to wait for
6.0.2, then call Support. That is always my advice.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Peter Anderson" <pETERanderson@westpac.com.au>@tkg.com on 02/07/2001
07:07:39 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "Netview List (E-mail)" <nv-l@tkg.com>
cc:
Subject: [NV-L] NV down traps from unmanaged interfaces
Hi,
I'm using NV 6.0.1 on Solaris 7.
I've got this "problem" which I haven't decided whether to raise a new PMR.
We have a lot of SNMP managed Cisco routers. From time to time, an
interface may be operationally down when a subnet has been decommissioned,
but the Admin status of the router is still up.
To stop NV creating alerts, I have unmanaged the interface.
I've noticed just recently that the unmanaged "status" (I'm using that word
here) is kept in the map, but at what I assume is the next status check
cycle, the status in the object and topology DBs are changed by NV to
Critical/Down. Of course traps are then issued and events start showing
up.
I think this is a bug. I didn't see this as a fix in 6.0.2, but maybe I
missed something (James?).
Here's the one in question:
(nvb)[/usr/OV/log] root# ovobjprint -s
"140phil-u2-lo.rtr.net.westpac.com.au:Ethernet0"
OBJECTID SELECTION NAME
OBJECT: 18390
FIELD ID FIELD NAME FIELD VALUE
10 Selection Name
"140phil-u2-lo.rtr.net.westpac.com.au:Ethernet0"
14 OVW Maps Exists 1
15 OVW Maps Managed 0
72 IP Address "10.215.114.1"
73 IP Subnet Mask "255.255.255.0"
74 IP Status Critical(4)
131 isCard TRUE
132 isInterface TRUE
137 isHSRP FALSE
142 isIP TRUE
165 SNMP ifType Ethernet CSMACD(6)
166 SNMP ifPhysAddr "0x00000C75D9A3"
167 SNMP ifDescr "Ethernet0"
168 SNMP ifSpeed 10000000
209 TopM Network ID 18389
210 TopM Segment ID 18656
211 TopM Node ID 1158
224 XXMAP Protocol List "IP"
225 XXMAP SAPs Used List 0
Note fields 15 and 74.
Here's a bit of an extract from trapd.log (interesting cycle!) ...
981469684 7 Wed Feb 07 01:28:04 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Interface Ethernet0 Unreachable.
981504158 3 Wed Feb 07 11:02:38 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Interface Ethernet0 down.
981504158 3 Wed Feb 07 11:02:38 2001 <none> N Segment
10.215.114.Segment1 Down.
981504158 3 Wed Feb 07 11:02:38 2001 <none> N Network
10.215.114 Down.
981504159 3 Wed Feb 07 11:02:39 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Router marginal.
981519917 7 Wed Feb 07 15:25:17 2001 <none> N Network
10.215.114 is Unreachable, mask(255.255.255.0)
981549785 3 Wed Feb 07 23:43:05 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Router Up.
981549791 7 Wed Feb 07 23:43:11 2001 <none> N Segment
10.215.114.Segment1 Managed.
981549791 7 Wed Feb 07 23:43:11 2001 <none> N Network
10.215.114 Managed.
981550619 7 Wed Feb 07 23:56:59 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Interface Ethernet0 Unreachable.
981557820 3 Thu Feb 08 01:57:00 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Interface Ethernet0 down.
981557820 3 Thu Feb 08 01:57:00 2001 <none> N Segment
10.215.114.Segment1 Down.
981557820 3 Thu Feb 08 01:57:00 2001 <none> N Network
10.215.114 Down.
981557821 3 Thu Feb 08 01:57:01 2001 140phil-u2-lo.rtr.net.westpac.com.au
N Router marginal.
981587381 7 Thu Feb 08 10:09:41 2001 140phil-u2-lo.rtr.net.westpac.com.au
n Demand polling on node 140phil-u2-lo.rtr.net.westpac.com.au.
Searching through NV-L I have found a couple of similar instances and
comments.
In one James Shanks says:
"And "unmanaged" is not a status (normal, marginal, critical) but a kind of
state which tells ipmap to ignore anything
else about this node, segment, interface, and so on."
I'm confused. If unmanaged is not a status, and it's only ipmap that uses
it, why does the notes on netmon say that it won't poll unmanaged devices?
Also, why does the topology and object databases (in other devices) have
"Unmanaged" as a status.
A "good" Example ...
from ovobjprint -s:
OBJECT: 87982
FIELD ID FIELD NAME FIELD VALUE
10 Selection Name "wtc-test2"
11 IP Hostname "wtc-test2"
14 OVW Maps Exists 1
15 OVW Maps Managed 0
74 IP Status Unmanaged(5)
77 isIPRouter FALSE
104 vendor Sun(39)
115 isNode TRUE
117 isComputer TRUE
118 isConnector FALSE
119 isBridge FALSE
120 isRouter FALSE
121 isHub FALSE
125 isWorkstation TRUE
142 isIP TRUE
158 isSNMPSupported TRUE
160 SNMP sysDescr "Sun SNMP Agent,
SUNW,SPARCstation-5"
161 SNMP sysLocation "System
administrators office"
162 SNMP sysContact "System
administrator"
163 SNMP sysObjectID
"1.3.6.1.4.1.42.2.1.1"
164 SNMPAgent Sun Microsystems
SunOS(350)
169 isMLM FALSE
170 isSYSMON FALSE
171 isSIA FALSE
172 isManager FALSE
174 isSLM FALSE
175 isSIAOS2 FALSE
207 TopM Interface Count 2
213 TopM Interface List "le0
Unmanaged 10.208.21.31 255.255.255.0 0x0800207AC890 ethernet csmacd
"
224 XXMAP Protocol List "IP"
962 IPIP Name "wtc-test2"
and from ovtopodump -l:
INTERFACE: le0
INTERFACE ID: 87983
CREATE TIME: Wed 07 Feb 2001 11:42:32 PM E
MODIFIED TIME: Wed 07 Feb 2001 11:42:32 PM E
SYMBOL CHANGE TIME: Wed 07 Feb 2001 11:42:32 PM E
SEGMENT CHANGE TIME: Wed 07 Feb 2001 11:42:32 PM E
STATUS: Unmanaged
IF FLAGS: CONNECTED
IP ADDR: 10.208.21.31
IP MASK: 255.255.255.0
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|