nv-l

[nv-l] RE: nv-l-digest V1 #170

2004-05-05 15:23:25
Subject: [nv-l] RE: nv-l-digest V1 #170
From: "Gill, Birinder" <bigill AT mackenziefinancial DOT com>
To: <nv-l AT lists.us.ibm DOT com>
Date: Wed, 5 May 2004 15:10:24 -0400
Thanks for your help. I commented out the stanza containing "deprecated" stuff 
around the problem lines in the MIB and ran it again successfully.

Birinder Gill
Mackenzie Financial

-----Original Message-----
From: owner-nv-l-digest AT lists.us.ibm DOT com
[mailto:owner-nv-l-digest AT lists.us.ibm DOT com]
Sent: Wednesday, May 05, 2004 12:15 PM
To: nv-l-digest AT lists.us.ibm DOT com
Subject: nv-l-digest V1 #170



nv-l-digest           Wednesday, May 5 2004           Volume 01 : Number 170




----------------------------------------------------------------------

Date: Tue, 4 May 2004 11:57:37 -0400
From: James Shanks <jshanks AT us.ibm DOT com>
Subject: Re: [nv-l] Nortel MIB load problem

This is a multipart message in MIME format.
- --=_alternative 0057AC5A85256E8A_=
Content-Type: text/plain; charset="US-ASCII"

My advice would be to open a problem with Support so they can try it.

But the error message would indicate that something in what you have
already loaded is causing a problem with this new MIB.
I say that because of the high line number, 22314.  Since it is unlikely
that this MIB you are loading is that large, then the line number probably
refers to the SNMP V2 MIB database file, /usr/OV/conf/snmpv2mib, to which
we are trying to add this new MIB.  If you examine that file, can you see
what's at or around 22314?  Based on the other error message, I'd be
expecting something with the word "deprecated" in it.

I'm not certain what to tell you to do after that, because I don't have
all the facts, which is why I suggested a call to Support.  Offhand, I
would suggest unloading the MIB which contains the offending line and then
try loading your new Nortel MIBs.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group



"Gill, Birinder" <bigill AT mackenziefinancial DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com
05/04/2004 09:33 AM
Please respond to
nv-l


To
<nv-l AT lists.us.ibm DOT com>
cc

Subject
[nv-l] Nortel MIB load problem







Has anyone successfully loaded the Nortel Passport 8000 series mibs. We
have 8600 and 8100. I am trying to load p80a3230.mib in Netview 7.1.4,
using xnmloadmib2 command on Solaris 2.8.
I am working on a new install.

Here is the Error I am getting:

Error detected while loading MIB File: /usr/OV/snmp_mibs/p80a3220.mib.
Bad format(deprecated): On or around line 22314
Bad Parse of OBJECT-IDENTITY: On or around line 22314
Mib table is bad.

Thanks,
Birinder Gill
Mackenzie Financial Corp.



This e-mail and any attachments may contain confidential information. Any
distributing, copying or reliance upon the contents of this e-mail by
anyone other
than the intended recipient is strictly prohibited. If you have received
this e-mail
accidentally, please delete it and notify the sender. Although this
message has been
screened for viruses, we cannot guarantee that our virus scanner will
detect all
viruses and take no responsibility for any damage or loss that may be
caused by its
contents.



- --=_alternative 0057AC5A85256E8A_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">My advice would be to open a problem
with Support so they can try it.</font>
<br>
<br><font size=2 face="sans-serif">But the error message would indicate
that something in what you have already loaded is causing a problem with
this new MIB.</font>
<br><font size=2 face="sans-serif">I say that because of the high line
number, 22314. &nbsp;Since it is unlikely that this MIB you are loading
is that large, then the line number probably refers to the SNMP V2 MIB
database file, /usr/OV/conf/snmpv2mib, to which we are trying to add this
new MIB. &nbsp;If you examine that file, can you see what's at or around
22314? &nbsp;Based on the other error message, I'd be expecting something
with the word &quot;deprecated&quot; in it.</font>
<br>
<br><font size=2 face="sans-serif">I'm not certain what to tell you to
do after that, because I don't have all the facts, which is why I suggested
a call to Support. &nbsp;Offhand, I would suggest unloading the MIB which
contains the offending line and then try loading your new Nortel MIBs.</font>
<br><font size=2 face="sans-serif"><br>
James Shanks<br>
Level 3 Support &nbsp;for Tivoli NetView for UNIX and Windows<br>
Tivoli Software / IBM Software Group</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Gill, Birinder&quot;
&lt;bigill AT mackenziefinancial DOT com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: owner-nv-l AT lists.us.ibm DOT 
com</font>
<p><font size=1 face="sans-serif">05/04/2004 09:33 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
nv-l</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&lt;nv-l AT lists.us.ibm DOT 
com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">[nv-l] Nortel MIB load 
problem</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt><br>
Has anyone successfully loaded the Nortel Passport 8000 series mibs. We
have 8600 and 8100. I am trying to load p80a3230.mib in Netview 7.1.4,
using xnmloadmib2 command on Solaris 2.8.<br>
I am working on a new install.<br>
<br>
Here is the Error I am getting:<br>
<br>
Error detected while loading MIB File: /usr/OV/snmp_mibs/p80a3220.mib.<br>
Bad format(deprecated): On or around line 22314<br>
Bad Parse of OBJECT-IDENTITY: On or around line 22314<br>
Mib table is bad.<br>
<br>
Thanks,<br>
Birinder Gill<br>
Mackenzie Financial Corp.<br>
<br>
<br>
<br>
This e-mail and any attachments may contain confidential information. Any<br>
distributing, copying or reliance upon the contents of this e-mail by anyone
other<br>
than the intended recipient is strictly prohibited. If you have received
this e-mail<br>
accidentally, please delete it and notify the sender. Although this message
has been<br>
screened for viruses, we cannot guarantee that our virus scanner will detect
all<br>
viruses and take no responsibility for any damage or loss that may be caused
by its<br>
contents.<br>
<br>
</tt></font>
<br>
- --=_alternative 0057AC5A85256E8A_=--

------------------------------

Date: Tue, 4 May 2004 14:32:05 -0400 (EDT)
From: Meyos Yemveng <yemveng AT yahoo DOT ca>
Subject: [nv-l] Discovery

- --0-2025775625-1083695525=:34851
Content-Type: text/plain; charset=us-ascii

Hi Folks,
I would like to clarify some discovery issues
1- I want to limit Netview to only discover what I have in the seed file
Q1: do I need to specify what IP range not to discover again? !102.105.123.*
Q2: What should I Do

Q3- I want to prevent unwanted Nodes to be discovered such as Nodes detected by 
ICMP and SNMP Ping sweeps and SNMP Cold/Warm start Traps ?

Q4- Any other suggestions?



Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"


- ---------------------------------
Post your free ad now! Yahoo! Canada Personals

- --0-2025775625-1083695525=:34851
Content-Type: text/html; charset=us-ascii

<DIV>Hi Folks,</DIV>
<DIV>I&nbsp;would like to clarify some discovery issues</DIV>
<DIV>1- I want to limit Netview to only discover what I have in the seed 
file</DIV>
<DIV>Q1: do I need to specify what IP range not to discover again? 
!102.105.123.*</DIV>
<DIV>Q2: What should I Do</DIV>
<DIV>&nbsp;</DIV>
<DIV>Q3- I want to prevent unwanted Nodes to be discovered such as Nodes 
detected by ICMP and SNMP Ping sweeps and SNMP Cold/Warm start Traps ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Q4- Any other suggestions?</DIV>
<DIV>&nbsp;</DIV><BR><BR>Thank You,<br>Meyos <br>"ALLEZ LES LIONS 
INDOMPTABLES"<p><br><hr size=1>Post your free ad now! <a 
href="http://ca.personals.yahoo.com/";><b>Yahoo! Canada Personals</b></a><br>
- --0-2025775625-1083695525=:34851--

------------------------------

Date: Tue, 4 May 2004 13:45:15 -0500
From: "Alan E. Hennis" <Hennis_Alan_E AT cat DOT com>
Subject: Re: [nv-l] Discovery

Put the following in your seed file to limit discovery to what is in the
seed file.

      @limit_discovery   # Limit discovery to the contents of this seed
file.


Thanks
Alan E. Hennis
Caterpillar Inc.
Systems+Process Division
309.494.3308
hennis_alan_e AT cat DOT com


                                                                                
                                                      
                      Meyos Yemveng                                             
                                                      
                      <yemveng AT yahoo DOT ca                                  
                                                             
                      >                                                         
                                                      
                      Sent by:                                                  
                                                      
                      owner-n[email protected] To: netview Tivoli <nv-l AT 
lists.us.ibm DOT com>                                                    
                      us.ibm.com        cc:                                     
                                                      
                                                                                
                                                      
                                                                                
                                                      
                      05/04/2004 01:32                                          
                                                      
                      PM                  Subject:      [nv-l] Discovery        
                                                      
                      Please respond to                                         
                                                      
                      nv-l                                                      
                                                      
                                                                                
                                                      
                                                                                
                                                      



Caterpillar: Confidential Green                 Retain Until: 06/03/2004
                                                Retention Category:  G90 -
                                                General
                                                Matters/Administration




Hi Folks,
I would like to clarify some discovery issues
1- I want to limit Netview to only discover what I have in the seed file
Q1: do I need to specify what IP range not to discover again? !102.105.123.
*
Q2: What should I Do

Q3- I want to prevent unwanted Nodes to be discovered such as Nodes
detected by ICMP and SNMP Ping sweeps and SNMP Cold/Warm start Traps ?

Q4- Any other suggestions?



Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"



Post your free ad now! Yahoo! Canada Personals

------------------------------

Date: Tue, 04 May 2004 20:18:56 +0100
From: Jane Curry <jane.curry AT skills-1st.co DOT uk>
Subject: Re: [nv-l] Discovery

Please see inserted comments.
Cheers,
Jane

Meyos Yemveng wrote:

> Hi Folks,
> I would like to clarify some discovery issues
> 1- I want to limit Netview to only discover what I have in the seed file
> Q1: do I need to specify what IP range not to discover again?
> !102.105.123.*

You need to turn off automatic discovery if you really want to limit
discovery to what is in the seedfile. If you have a Unix  NetView, you
want Options -> Topology/Status Polling -> and untick the "Discover New
Nodes" box.  When you do this, wildcard entries in your seedfile are
irrelevant - ALL wildcards - includes and excludes.  The only things
NetView will discover will be explicit seedfile entries like 1.2.3.4 or
fred.bloggs.com.  Nothing with * ? or ranges with hyphens, will be
discovered.  This may not be the behaviour you want!

> Q2: What should I Do
> 

If you don't have too many nodes that you want to discover and you are
prepared to hand-maintain your seedfile, then do as above.  If you don't
want to create an explicit entry for each node you want to find then you
need to turn auto-discovery back ON and find a combination of inclusion
and exclusiion wildcard entries for your seedfile that achieves the
desired effect.  Have you looked at the @OID style of seedfile entry to
limit discovery to specific types of SNMP agent?  That can be very
powerful for preventing discovery of nodes.

> Q3- I want to prevent unwanted Nodes to be discovered such as Nodes
> detected by ICMP and SNMP Ping sweeps and SNMP Cold/Warm start Traps ?
> 

Doesn't matter what the polling mechanism is - if the seedfile permits
it - it gets discovered; otherwise it doesn't.

> Q4- Any other suggestions?
> 

You might look at taking the NetView for Unix for Administrators class
(or the Windows version if your NetView is Win based).  We spend the
best part of a day on understanding discovery / seedfiles /
location.conf / etc.

>
>
> Thank You,
> Meyos
> "ALLEZ LES LIONS INDOMPTABLES"
>
>
> ------------------------------------------------------------------------
> Post your free ad now! *Yahoo! Canada Personals*
> <http://ca.personals.yahoo.com/>


- --
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry AT skills-1st.co DOT uk>.  All rights 
reserved.

------------------------------

Date: Wed, 5 May 2004 12:43:31 +0200
From: tilo.strauch AT rzleipzig DOT de
Subject: [nv-l] nvlockd; C5d not running [ =?ISO-8859-1?B?dmlyZW5nZXBy/GZ0XQ==?=

Hi list,

after update NV 7.1.3 to 7.1.4 all works fine. An ovstatus command shows
that nvlockd and C5d are not running. I'd try to added those deamons whith
ovaddobj but nothing helps.


ovstart
 object manager name: nvlockd
 behavior:            OVs_WELL_BEHAVED
 state:               FAILED
 PID:                 17802
 last message:        Initialization failed
 exit status:         -

 object manager name: nvlockd
 behavior:            OVs_WELL_BEHAVED
 state:               DONE
 PID:                 17802
 last message:        Initialization failed
 exit status:         -

 object manager name: C5d
 behavior:            OVs_WELL_BEHAVED
 state:               NOT_RUNNING
 PID:                 22962
 last message:
 exit status:         exit(0)

Regards

Tilo Strauch
- ------------------------------------------------------------------------
Netzwerkmanagement
- ------------------------------------------------------------------------
Deutsche Rentenversicherung
Rechenzentrum Leipzig e.V.
Tel.: +49 0341 9170-220
Fax:  +49 0341 9110-806
- ------------------------------------------------------------------------
mailto:tilo.strauch AT rzleipzig DOT de

------------------------------

Date: Wed, 5 May 2004 05:52:12 -0700 (PDT)
From: Mario Behring <mariobehring AT yahoo DOT com>
Subject: Re: [nv-l] nvlockd; C5d not running [ virengeprüft]

Tilo,

Try loading the daemon through command line without the ovstart (like
./nvlockd) just to see the error messages. May be there is a library
missing or something. In any case, you should have more information to
solve the problem.

HTH

Mario Behring
Tivoli Consultant
IBM Brazil
+55 11 8125-5598
+55 19 2104-3006
mariob AT br.ibm DOT com
mariobehring AT yahoo DOT com


- --- tilo.strauch AT rzleipzig DOT de wrote:
>
>
>
>
> Hi list,
>
> after update NV 7.1.3 to 7.1.4 all works fine. An ovstatus command shows
> that nvlockd and C5d are not running. I'd try to added those deamons
> whith
> ovaddobj but nothing helps.
>
>
> ovstart
>  object manager name: nvlockd
>  behavior:            OVs_WELL_BEHAVED
>  state:               FAILED
>  PID:                 17802
>  last message:        Initialization failed
>  exit status:         -
>
>  object manager name: nvlockd
>  behavior:            OVs_WELL_BEHAVED
>  state:               DONE
>  PID:                 17802
>  last message:        Initialization failed
>  exit status:         -
>
>  object manager name: C5d
>  behavior:            OVs_WELL_BEHAVED
>  state:               NOT_RUNNING
>  PID:                 22962
>  last message:
>  exit status:         exit(0)
>
> Regards
>
> Tilo Strauch
> ------------------------------------------------------------------------
> Netzwerkmanagement
> ------------------------------------------------------------------------
> Deutsche Rentenversicherung
> Rechenzentrum Leipzig e.V.
> Tel.: +49 0341 9170-220
> Fax:  +49 0341 9110-806
> ------------------------------------------------------------------------
> mailto:tilo.strauch AT rzleipzig DOT de
>




        
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 
http://hotjobs.sweepstakes.yahoo.com/careermakeover

------------------------------

Date: Wed, 5 May 2004 15:58:34 +0200 (CEST)
From: Tom Hallberg <gimli AT hhcrew DOT tk>
Subject: Re: [nv-l] Netview icons

Yes that was what I was looking for.. thx.. :)

On Mon, 3 May 2004, Oliver Bruchhaeuser wrote:

> You can change the line in /usr/OV/app-defaults/OVw:
> OVw*marginalStatusColor:                yellow
>
> But is this really what you want to achieve?
>
> Oliver
>
>
>
> gimli AT hhcrew DOT tk
> Sent by: owner-nv-l AT lists.us.ibm DOT com
> 03.05.2004 09:33
> Please respond to
> nv-l
>
>
> To
> nv-l AT lists.us.ibm DOT com
> cc
>
> Subject
> [nv-l] Netview icons
>
>
>
>
>
>
> How do I change the color on the warning events. The default ok color is
> green and if there is something wrong under any site or switch/router and
> so on,it turns to yellow. I want to change the yellow into another color.
>
> Where to look?
>
> I run Netview 7.1.4 on RedHat 7.2.
>
> Thank you
>
>

------------------------------

Date: Wed, 5 May 2004 09:13:01 -0500
From: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
Subject: [nv-l] Netview and AIX v5.2

Netview v7.1.4
Solaris 2.8

I remember seeing something about AIX changing the default SNMP agent
behavior from v1 to v2. We have a box right now, (our first AIX 5 box)
and status polls are failing. My suspicion is that the agent needs to be
configured to use SNMPv1 - I can't remember enough details about what
was reported here to know if I'm on the right track. Anyone recall this
thread?

------------------------------

Date: Wed, 5 May 2004 10:26:43 -0400
From: "Davis, Donald" <donald.davis AT firstcitizens DOT com>
Subject: RE: [nv-l] Netview and AIX v5.2

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- ------_=_NextPart_001_01C432AC.FD103CC0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Scott,
Actually , AIX V5 defaults to SNMPv3. Run this command to reset it back to
SNMPv1.

snmpv3_ssw -1

Don

- -----Original Message-----
From: Barr, Scott [mailto:Scott_Barr AT csgsystems DOT com]
Sent: Wednesday, May 05, 2004 10:13 AM
To: nv-l AT lists.us.ibm DOT com
Subject: [nv-l] Netview and AIX v5.2


Netview v7.1.4
Solaris 2.8

I remember seeing something about AIX changing the default SNMP agent
behavior from v1 to v2. We have a box right now, (our first AIX 5 box) and
status polls are failing. My suspicion is that the agent needs to be
configured to use SNMPv1 - I can't remember enough details about what was
reported here to know if I'm on the right track. Anyone recall this thread?


- ------------------------------------------------------------------------------
This electronic mail and any files transmitted with it are confidential and
are intended solely for the use of individual or entity to whom they are
addressed.  If you are not the intended recipient or the person responsible
for delivering the electronic mail to the intended recipient, be advised that
you have received this electronic mail in error and that any use,
dissemination, forwarding, printing, or copying of this electronic mail is
strictly prohibited.  If you have received this electronic mail in error,
please immediately notify the sender by return mail.
==============================================================================

- ------_=_NextPart_001_01C432AC.FD103CC0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [nv-l] Netview and AIX v5.2</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Scott,</FONT>
<BR><FONT SIZE=3D2>Actually , AIX V5 defaults to SNMPv3. Run this command to =
reset it back to SNMPv1.</FONT>
</P>

<P><FONT SIZE=3D2>snmpv3_ssw -1</FONT>
</P>

<P><FONT SIZE=3D2>Don</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Barr, Scott [<A =
HREF=3D"mailto:Scott_Barr AT csgsystems DOT com">mailto:Scott_Barr AT 
csgsystems DOT com</A=
>]=
 </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, May 05, 2004 10:13 AM</FONT>
<BR><FONT SIZE=3D2>To: nv-l AT lists.us.ibm DOT com</FONT>
<BR><FONT SIZE=3D2>Subject: [nv-l] Netview and AIX v5.2</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Netview v7.1.4</FONT>
<BR><FONT SIZE=3D2>Solaris 2.8</FONT>
</P>

<P><FONT SIZE=3D2>I remember seeing something about AIX changing the default =
SNMP agent behavior from v1 to v2. We have a box right now, (our first AIX 5 =
box) and status polls are failing. My suspicion is that the agent needs to be=
 =
configured to use SNMPv1 - I can't remember enough details about what was =
reported here to know if I'm on the right track. Anyone recall this =
thread=3F</FONT></P>

</BODY>
</HTML>
<P>--------------------------------------------------------------------------=
- ----<br>
This electronic mail and any files transmitted with it are confidential and =
are intended solely for the use of individual or entity to whom they are =
addressed.  If you are not the intended recipient or the person responsible =
=66or delivering the electronic mail to the intended recipient, be advised =
that you have received this electronic mail in error and that any use, =
dissemination, forwarding, printing, or copying of this electronic mail is =
strictly prohibited.  If you have received this electronic mail in error, =
please immediately notify the sender by return mail.<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
</P>
- ------_=_NextPart_001_01C432AC.FD103CC0--

------------------------------

Date: Wed, 05 May 2004 10:30:04 -0400
From: Paul <pstroud AT bellsouth DOT net>
Subject: Re: [nv-l] Netview and AIX v5.2

Scott,
Im sure someone else can give you additional information, but
if you search the archive for "snmpd64" I think you might find
what you are looking for.

Paul


Barr, Scott wrote:

>Netview v7.1.4
>Solaris 2.8
>
>I remember seeing something about AIX changing the default SNMP agent
>behavior from v1 to v2. We have a box right now, (our first AIX 5 box)
>and status polls are failing. My suspicion is that the agent needs to be
>configured to use SNMPv1 - I can't remember enough details about what
>was reported here to know if I'm on the right track. Anyone recall this
>thread?
>
>
> 
>

------------------------------

Date: Wed, 5 May 2004 09:40:39 -0500
From: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
Subject: RE: [nv-l] Netview and AIX v5.2

Thanks folks.

> -----Original Message-----
> From: owner-nv-l AT lists.us.ibm DOT com
> [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Paul
> Sent: Wednesday, May 05, 2004 9:30 AM
> To: nv-l AT lists.us.ibm DOT com
> Subject: Re: [nv-l] Netview and AIX v5.2
>
> Scott,
> Im sure someone else can give you additional information, but
> if you search the archive for "snmpd64" I think you might
> find what you are looking for.
>
> Paul
>
>
> Barr, Scott wrote:
>
> >Netview v7.1.4
> >Solaris 2.8
> >
> >I remember seeing something about AIX changing the default
> SNMP agent
> >behavior from v1 to v2. We have a box right now, (our first
> AIX 5 box)
> >and status polls are failing. My suspicion is that the agent
> needs to
> >be configured to use SNMPv1 - I can't remember enough details about
> >what was reported here to know if I'm on the right track.
> Anyone recall
> >this thread?
> >
> >
> > 
> >
>
>
>

------------------------------

Date: Wed, 5 May 2004 12:14:34 -0400 (EDT)
From: Meyos Yemveng <yemveng AT yahoo DOT ca>
Subject: Re: [nv-l] Discovery

- --0-928095894-1083773674=:40396
Content-Type: text/plain; charset=us-ascii

Thanks Folks,
More QUestions

Q1: Let's say myy seed file have the following two entries:

node1.mydonaine.com #IP=192.168.15.12
!192.168.15* #Do not discover these IP range

Would my node1 be discovered?

Q2: Best practice Advice on Discovery.
- - Should you control your discovery via the seed file content 
(@limit_discovery)?
- - Should you a combination of sedd file entries and IP restrictions while 
allowing auto-discovery?
- - What wold you suggest for a network of Servers and Routers?

Jane Curry <jane.curry AT skills-1st.co DOT uk> wrote:
Please see inserted comments.
Cheers,
Jane

Meyos Yemveng wrote:

> Hi Folks,
> I would like to clarify some discovery issues
> 1- I want to limit Netview to only discover what I have in the seed file
> Q1: do I need to specify what IP range not to discover again?
> !102.105.123.*

You need to turn off automatic discovery if you really want to limit
discovery to what is in the seedfile. If you have a Unix NetView, you
want Options -> Topology/Status Polling -> and untick the "Discover New
Nodes" box. When you do this, wildcard entries in your seedfile are
irrelevant - ALL wildcards - includes and excludes. The only things
NetView will discover will be explicit seedfile entries like 1.2.3.4 or
fred.bloggs.com. Nothing with * ? or ranges with hyphens, will be
discovered. This may not be the behaviour you want!

> Q2: What should I Do
>

If you don't have too many nodes that you want to discover and you are
prepared to hand-maintain your seedfile, then do as above. If you don't
want to create an explicit entry for each node you want to find then you
need to turn auto-discovery back ON and find a combination of inclusion
and exclusiion wildcard entries for your seedfile that achieves the
desired effect. Have you looked at the @OID style of seedfile entry to
limit discovery to specific types of SNMP agent? That can be very
powerful for preventing discovery of nodes.

> Q3- I want to prevent unwanted Nodes to be discovered such as Nodes
> detected by ICMP and SNMP Ping sweeps and SNMP Cold/Warm start Traps ?
>

Doesn't matter what the polling mechanism is - if the seedfile permits
it - it gets discovered; otherwise it doesn't.

> Q4- Any other suggestions?
>

You might look at taking the NetView for Unix for Administrators class
(or the Windows version if your NetView is Win based). We spend the
best part of a day on understanding discovery / seedfiles /
location.conf / etc.

>
>
> Thank You,
> Meyos
> "ALLEZ LES LIONS INDOMPTABLES"
>
>
> ------------------------------------------------------------------------
> Post your free ad now! *Yahoo! Canada Personals*
>


- --
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry . All rights reserved.



Thank You,
Meyos
"ALLEZ LES LIONS INDOMPTABLES"


- ---------------------------------
Post your free ad now! Yahoo! Canada Personals

- --0-928095894-1083773674=:40396
Content-Type: text/html; charset=us-ascii

<DIV>Thanks Folks,</DIV>
<DIV>More QUestions</DIV>
<DIV>&nbsp;</DIV>
<DIV>Q1: Let's say myy seed file have the following two entries:</DIV>
<DIV>&nbsp;</DIV>
<DIV><STRONG>node1.mydonaine.com #IP=192.168.15.12</STRONG></DIV>
<DIV><STRONG>!192.168.15* #Do not discover these IP range</STRONG></DIV>
<DIV>&nbsp;</DIV>
<DIV>Would my node1 be discovered?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Q2: Best practice Advice on Discovery.</DIV>
<DIV>- Should you control your discovery via the seed file content 
(@limit_discovery)?</DIV>
<DIV>- Should you a combination of sedd file entries and IP restrictions while 
allowing auto-discovery?</DIV>
<DIV>- What wold you suggest for a network of Servers and 
Routers?<BR><BR><B><I>Jane Curry &lt;jane.curry AT skills-1st.co DOT 
uk&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; 
BORDER-LEFT: #1010ff 2px solid">Please see inserted 
comments.<BR>Cheers,<BR>Jane<BR><BR>Meyos Yemveng wrote:<BR><BR>&gt; Hi 
Folks,<BR>&gt; I would like to clarify some discovery issues<BR>&gt; 1- I want 
to limit Netview to only discover what I have in the seed file<BR>&gt; Q1: do I 
need to specify what IP range not to discover again? <BR>&gt; 
!102.105.123.*<BR><BR>You need to turn off automatic discovery if you really 
want to limit <BR>discovery to what is in the seedfile. If you have a Unix 
NetView, you <BR>want Options -&gt; Topology/Status Polling -&gt; and untick 
the "Discover New <BR>Nodes" box. When you do this, wildcard entries in your 
seedfile are <BR>irrelevant - ALL wildcards - includes and excludes. The only 
things <BR>NetView will discover will be explicit seedfile entries like 1.2.3.4 
or <BR>fred.bloggs.com. Nothing with * ? or ranges with hyphens, will be 
<BR>discovered. This may not be the be!
 haviour
 you want!<BR><BR>&gt; Q2: What should I Do<BR>&gt; <BR><BR>If you don't have 
too many nodes that you want to discover and you are <BR>prepared to 
hand-maintain your seedfile, then do as above. If you don't <BR>want to create 
an explicit entry for each node you want to find then you <BR>need to turn 
auto-discovery back ON and find a combination of inclusion <BR>and exclusiion 
wildcard entries for your seedfile that achieves the <BR>desired effect. Have 
you looked at the @OID style of seedfile entry to <BR>limit discovery to 
specific types of SNMP agent? That can be very <BR>powerful for preventing 
discovery of nodes.<BR><BR>&gt; Q3- I want to prevent unwanted Nodes to be 
discovered such as Nodes <BR>&gt; detected by ICMP and SNMP Ping sweeps and 
SNMP Cold/Warm start Traps ?<BR>&gt; <BR><BR>Doesn't matter what the polling 
mechanism is - if the seedfile permits <BR>it - it gets discovered; otherwise 
it doesn't.<BR><BR>&gt; Q4- Any other suggestions?<BR>&gt; <BR><BR>You might l!
 ook at
 taking the NetView for Unix for Administrators class <BR>(or the Windows 
version if your NetView is Win based). We spend the <BR>best part of a day on 
understanding discovery / seedfiles / <BR>location.conf / 
etc.<BR><BR>&gt;<BR>&gt;<BR>&gt; Thank You,<BR>&gt; Meyos<BR>&gt; "ALLEZ LES 
LIONS INDOMPTABLES"<BR>&gt;<BR>&gt;<BR>&gt; 
------------------------------------------------------------------------<BR>&gt;
 Post your free ad now! *Yahoo! Canada Personaals* <BR>&gt; <HTTP: 
ca.personals.yahoo.com /><BR><BR><BR>-- <BR>Tivoli Certified Consultant &amp; 
Instructor<BR>Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, 
UK<BR>Tel: +44 (0)1628 782565<BR>Copyright (c) 2004 Jane Curry <JANE.CURRY AT 
SKILLS-1ST.CO DOT UK>. All rights reserved.<BR><BR></BLOCKQUOTE><BR><BR>Thank 
You,<br>Meyos <br>"ALLEZ LES LIONS INDOMPTABLES"<p><br><hr size=1>Post your 
free ad now! <a href="http://ca.personals.yahoo.com/";><b>Yahoo! Canada 
Personals</b></a><br>
- --0-928095894-1083773674=:40396--

------------------------------

End of nv-l-digest V1 #170
**************************




This e-mail and any attachments may contain confidential information. Any
distributing, copying or reliance upon the contents of this e-mail by anyone 
other
than the intended recipient is strictly prohibited. If you have received this 
e-mail
accidentally, please delete it and notify the sender. Although this message has 
been
screened for viruses, we cannot guarantee that our virus scanner will detect all
viruses and take no responsibility for any damage or loss that may be caused by 
its
contents.


<Prev in Thread] Current Thread [Next in Thread>
  • [nv-l] RE: nv-l-digest V1 #170, Gill, Birinder <=