This is a multipart message in MIME format.

We have a similar problem after update from NetView 6.0 to NetView 6.0.1 
on AIX 4.3.3. The differenz in configuration is: Now we use the 
RFI-Feature.
If I set several Interfaces from Router to unmanaged, then I get the 
following result:

1. Event Interface SerX/X unmanaged
2. The IP Status in DB is unmanaged
3.  After short time (Polling Intervall ?) I get event Interface SerX/X 
down.
4. The IP Status in DB is Critical.


Thanks for any help

Uwe

 




"Smith, Kristi" <kristi_smith AT mentorg DOT com>
Gesendet von: owner-nv-l AT tkg DOT com
20.12.2000 22:16
Bitte antworten an IBM NetView Discussion

 
        An:     "'IBM NetView Discussion'" <nv-l AT tkg DOT com>
        Kopie:  (Blindkopie: Uwe Richter/Synthesis)
        Thema:  RE: [NV-L] Interfaces not being unmanaged when the node is 
unmana ged


I am seeing this behavior on my NetView server as well so I would be 
interested in any workarounds or configuration tips.   I am running v. 
6.0.1 on Solaris 2.7.
 
Thanks,
Kristi Smith
Mentor Graphics Corporation
(503) 685-1971
kristi_smith AT mentor DOT com 
-----Original Message-----
From: Graeme Nelson [mailto:Graeme.Nelson AT macquarie.com DOT au]
Sent: Tuesday, December 19, 2000 7:16 PM
To: 'nv-l AT tkg DOT com'
Subject: [NV-L] Interfaces not being unmanaged when the node is unmanaged

Hi Netviewers, 
This is more a nuisance than a problem. We've found that when a PC is 
discovered immediately unmanaged except the interface remains managed.
Our Global Default is to NOT Discover Node(s) Managed. 
Here's an example from trapd.log: 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node 
Added. 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N 
Interface Intel Added 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N System 
Name Changed 
977116499  3  Mon Dec 18 16:14:59 2000 AA039207                  N Node 
Up. 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N 
Forwarding Status Changed -- Now a Host 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node 
flags changed to 
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node 
unmanaged. 
...... 
977272321  3  Wed Dec 20 11:32:01 2000 AA039207                  N 
Interface Intel down. 
Our PC's are a mix of NT and Win2000 some support SNMP some don't. This 
affects both NV 5.1.1 and 6.0.1 on Solaris 2.6. 
The impact is the maps are always yellow and once you drill down your 
looking not for a red icon but a red link from the icon to the network.
Is there some setting that we've missed or changed that's causing this 
problem. 
Thanks 
Graeme Nelson 
Macquarie Bank 
Sydney, Australia 

Hi Netviewers,
This is more a nuisance than a problem. We've found that when a PC is discovered immediately unmanaged except the interface remains managed.

Our Global Default is to NOT Discover Node(s) Managed.

Here's an example from trapd.log:
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node Added.
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Interface Intel Added
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N System Name Changed
977116499  3  Mon Dec 18 16:14:59 2000 AA039207                  N Node Up.
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Forwarding Status Changed -- Now a Host
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node flags changed to
977116499  7  Mon Dec 18 16:14:59 2000 AA039207                  N Node unmanaged.
......
977272321  3  Wed Dec 20 11:32:01 2000 AA039207                  N Interface Intel down.

Our PC's are a mix of NT and Win2000 some support SNMP some don't. This affects both NV 5.1.1 and 6.0.1 on Solaris 2.6.

The impact is the maps are always yellow and once you drill down your looking not for a red icon but a red link from the icon to the network.

Is there some setting that we've missed or changed that's causing this problem.

Thanks

Graeme Nelson
Macquarie Bank
Sydney, Australia