nv-l
[Top] [All Lists]

RE: [nv-l] snmpd.conf setting to restrict Authentication Failure Traps

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] snmpd.conf setting to restrict Authentication Failure Traps
From: lesdickert@att.net
Date: Wed, 14 Apr 2004 15:20:22 +0000
Delivery-date: Wed, 14 Apr 2004 16:30:30 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
I don't think there is any difference between
f6 and f7 as, they say, the lowest order bit
is not used.

>From snmpd.conf comments:

#    The trap mask is in hexidecimal
#    format.  The bits from left to right stand for coldStart trap, warmStart
#    trap, linkDown trap, linkUp trap, authenticationFailure trap,
#    egpNeighborLoss trap, and enterpriseSpecific trap.  The right most bit
#    does not have any meaning.



Les Dickert
Anthem BC/BS
Richmond, VA




--- Begin Message ---
To: "'nv-l@lists.us.ibm.com'" <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] snmpd.conf setting to restrict Authentication Failure Traps
From: "Bursik, Scott {PBSG}" <Scott.Bursik@pbsg.com>
Date: Wed, 14 Apr 2004 15:01:08 +0000

It appears that a value of f7 would block AuthenticationFailure traps and nothing else. A value of f6 as suggested in the earlier thread would block AuthenticationFailure but would also block Enterprose Specific traps. Does this sound correct? I believe that I am on the right path here.

 

 

Scott Bursik

Enterprise Systems Management

PepsiCo Business Solutions Group

(972) 963-1400

scott.bursik@pbsg.com

 

 


From: Oliver Bruchhaeuser [mailto:oliver.bruchhaeuser@de.ibm.com]
Sent: Wednesday, April 14, 2004 1:03 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] snmpd.conf setting to restrict Authentication Failure Traps

 

 


--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>
  • RE: [nv-l] snmpd.conf setting to restrict Authentication Failure Traps, lesdickert <=

Archive operated by Skills 1st Ltd

See also: The NetView Web