RE: monitor "looking" at objects which are not supposed to be monitored

Richard Gipps <[email protected]> Wed, 27 May 2009 09:01:19 +0800

Newsgroups	gmane.network.net-snmp.user
Message-ID	<[email protected]>

Dave,
     See my responses below...

>>      I am using monitor to "keep an eye on" some parameters in a mib. I have
>> found that objects which are not being monitored are still being accessed by
>> snmpd (as if a get command was issued).

> What objects are being accessed?

The object being accessed (1.3.6.1.4.1.33302.10.4.15) is from one of our enterprise MIBs. I have attached the MIB for reference.

>>                                               I commented out all the monitor
>> lines (in snmpd.conf)and the problem persisted. Next I commented out the
>> notificationEvent lines (in snmpd.conf) and that seemed to fix the problem.

> What are the contents of the snmpd.conf file?

I have attached the snmpd.conf file. If you have a look in the snmpd.conf file you will see two lines commented out:

#notificationEvent NotifyDownstreamNetworkId 1.3.6.1.4.1.33302.10.10.24 -m
# monitor -S -r 5 -e NotifyDownstreamNetworkId "Downstream network ID changed." != 1.3.6.1.4.1.33302.10.4.15

Even though they are commented out the 1.3.6.1.4.1.33302.10.4.15 object is still being accessed.


>> There are no notificationEvents linked to the particular object I am having
>> the problem with.

> Which is....

1.3.6.1.4.1.33302.10.4.15

Richard.

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

JR900.mib (application/octet-stream, 19.3 KB) - not displayed

snmpd.conf (application/octet-stream, 7.2 KB)

###########################################################################
#
# snmpd.conf
#
#   - created by the snmpconf configuration program
#
###########################################################################
# SECTION: Access Control Setup
#
#   This section defines who is allowed to talk to your running
#   snmp agent.

# rocommunity: a SNMPv1/SNMPv2c read-only access community name
#   arguments:  community [default|hostname|network/bits] [oid]
rocommunity  public  

# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
#   arguments:  community [default|hostname|network/bits] [oid]
rwcommunity  private

# trapcommunity: Defines the default community string to be used when sending traps.
# Note that this directive must be used prior to any community-based trap destination
# directives that need to use it.
trapcommunity trap

###########################################################################
# SECTION: System Information Setup
#
#   This section defines some of the information reported in
#   the "system" mib group in the mibII tree.

# sysObjectID: Trio's authoritative identification of the network management
#    subsystem contained in the J-Series.  This value is allocated within
#    the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and
#    unambiguous means for determining `what kind of box' is being managed.
sysObjectID 1.3.6.1.4.1.33302.1

# sysServices: The value which indicates the set of services that the J-Series
#    primarily offers. The value is a sum.  This sum initially takes the value
#    zero, Then, for each layer, L, in the range 1 through 7, that this node
#    performs transactions for, 2 raised to (L - 1) is added to the sum.  For
#    example, a node which performs primarily routing functions would have a
#    value of 4 (2^(3-1)).  In contrast, a node which is a host offering
#    application services would have a value of 72 (2^(4-1) + 2^(7-1)).  Note
#    that in the context of the Internet suite of protocols, values should be
#    calculated accordingly:
#
#                          layer  functionality
#                              1  physical (e.g., repeaters)
#                              2  datalink/subnetwork (e.g., bridges)
#                              3  internet (e.g., IP gateways)
#                              4  end-to-end  (e.g., IP hosts)
#                              7  applications (e.g., mail relays)
#
#    For systems including OSI protocols, layers 5 and 6 may also be counted.
#    Since the J-Series currently only performs bridging the value is 2 (2^(2-1))
sysServices 2

# sysDescr: A description of the system (most manufacturers state the model
#    number and firmware version in this field.
sysDescr "J Series JRxxx-aabbb-cde Ethernet Data Radio, Firmware version D3.0.0 Rev 983"

# Set up a user for SNMP V3. Current we are not supporting SNMP V3 but when an internal 
# query is performed using the monitor function it is an SNMP V3 query.
createUser user SHA password
rwuser user
iquerySecName user

# Notifications
notificationEvent NotifyFatalError     1.3.6.1.4.1.33302.10.10.1 -m
notificationEvent NotifyPllLocked      1.3.6.1.4.1.33302.10.10.2 -m
notificationEvent NotifyOldProtocol    1.3.6.1.4.1.33302.10.10.3 -m
notificationEvent NotifyConfigRecord   1.3.6.1.4.1.33302.10.10.4 -m
notificationEvent NotifyVswr           1.3.6.1.4.1.33302.10.10.5 -m
notificationEvent NotifyTemperature    1.3.6.1.4.1.33302.10.10.6 -m
notificationEvent NotifySupplyVoltage  1.3.6.1.4.1.33302.10.10.7 -m
notificationEvent NotifyAnt1RssiLow 1.3.6.1.4.1.33302.10.10.8 -m
#notificationEvent NotifyAnt2RssiLow 1.3.6.1.4.1.33302.10.10.9 -i 1.3.6.1.4.1.33302.10.2.13.0
#RSSI ANT1 Delta
#RSSI ANT2 Delta
notificationEvent NotifyAnt1Power 1.3.6.1.4.1.33302.10.10.12 -m
notificationEvent NotifyAnt2Power 1.3.6.1.4.1.33302.10.10.13 -m
notificationEvent NotifySync 1.3.6.1.4.1.33302.10.10.14 -m
notificationEvent NotifyAccessPoint 1.3.6.1.4.1.33302.10.10.15 -m
# notificationEvent NotifyAccessPoint 1.3.6.1.4.1.33302.10.10.16 -m IP address changed
notificationEvent NotifyConsoleLogin 1.3.6.1.4.1.33302.10.10.17 -m
notificationEvent NotifyTelnet1Login 1.3.6.1.4.1.33302.10.10.18 -m
notificationEvent NotifyTelnet2Login 1.3.6.1.4.1.33302.10.10.19 -m
notificationEvent NotifyTelnet3Login 1.3.6.1.4.1.33302.10.10.20 -m
notificationEvent NotifyHttpLogin 1.3.6.1.4.1.33302.10.10.21 -m
notificationEvent NotifyEncryption 1.3.6.1.4.1.33302.10.10.22 -m
notificationEvent NotifyIpAddress 1.3.6.1.4.1.33302.10.10.23 -m
#notificationEvent NotifyDownstreamNetworkId 1.3.6.1.4.1.33302.10.10.24 -m

# Items to monitor
monitor -S -r 5 -e NotifyFatalError "Fatal error" != 1.3.6.1.4.1.33302.10.6.1 
monitor -S -r 5 -e NotifyPllLocked "PLL lock status changed." != 1.3.6.1.4.1.33302.10.6.2 
monitor -S -r 5 -e NotifyOldProtocol "Received packet with deprecated format." 1.3.6.1.4.1.33302.10.6.3 == 1
monitor -S -r 5 -e NotifyConfigRecord "Configuration Record not present." 1.3.6.1.4.1.33302.10.6.4 == 2
monitor -S -r 5 -e NotifyVswr "High VSWR present." != 1.3.6.1.4.1.33302.10.6.5
monitor -S -r 5 -e NotifyTemperature "Traversing temperature limits." != 1.3.6.1.4.1.33302.10.6.7
monitor -S -r 5 -e NotifySupplyVoltage "Traversing supply voltage limits." != 1.3.6.1.4.1.33302.10.6.6
monitor -S -r 1 -e NotifyAnt1RssiLow "Traversing ANT1 lower RSSI limit." 1.3.6.1.4.1.33302.10.2.12 -80 -60
#monitor -S -r 5 -e NotifyAnt2RssiLow "Traversing ANT2 lower RSSI limit." 1.3.6.1.4.1.33302.10.2.13 x y
#RSSI ANT1 Delta
#RSSI ANT2 Delta
monitor -S -r 5 -e NotifyAnt1Power "Traversing ANT1 lower power limit." 1.3.6.1.4.1.33302.10.2.6 27 28
monitor -S -r 5 -e NotifyAnt1Power "Traversing ANT1 upper power limit." 1.3.6.1.4.1.33302.10.2.6 32 33
monitor -S -r 5 -e NotifySync "Changing synchronisation status." != 1.3.6.1.4.1.33302.10.2.18
monitor -S -r 5 -e NotifyAccessPoint "Changing Access Point." != 1.3.6.1.4.1.33302.10.2.24
#VSWR change
monitor -S -r 5 -e NotifyConsoleLogin "Console login changed state." != 1.3.6.1.4.1.33302.10.4.2
monitor -S -r 5 -e NotifyTelnet1Login "Telnet1 login changed state." != 1.3.6.1.4.1.33302.10.4.4
monitor -S -r 5 -e NotifyTelnet2Login "Telnet2 login changed state." != 1.3.6.1.4.1.33302.10.4.6
monitor -S -r 5 -e NotifyTelnet3Login "Telnet3 login changed state." != 1.3.6.1.4.1.33302.10.4.8
monitor -S -r 5 -e NotifyHttpLogin "HTTP login changed state." != 1.3.6.1.4.1.33302.10.4.10
monitor -S -r 5 -e NotifyEncryption "Encryption enabled/disabled." != 1.3.6.1.4.1.33302.10.4.14
monitor -S -r 5 -e NotifyIpAddress "IP address of radio changed-1." != 1.3.6.1.4.1.33302.10.10.100.1
monitor -S -r 5 -e NotifyIpAddress "IP address of radio changed-2." != 1.3.6.1.4.1.33302.10.10.100.2
# monitor -S -r 5 -e NotifyDownstreamNetworkId "Downstream network ID changed." != 1.3.6.1.4.1.33302.10.4.15

# trapsink: Define the address of a notification receiver where SNMP V1 traps are sent.
trapsink 192.168.0.133

# authtrapenable: Determines whether to generate authentication failure traps (enabled(1))
# or not (disabled(2) - the default). Ordinarily the corresponding MIB object
# (snmpEnableAuthenTraps.0) is read-write, but specifying this directive makes this object
# read-only, and attempts to set the value via SET requests will result in a notWritable
# error response.
authtrapenable 1