is anybody using the net-snmp package in his production environment for a long time now (at least several months) for sending traps and processing them etc.?
Any notes on stability and usability?
Any description on your environment about amount of traffic ie. number of traps/per time that have to be handled etc. would be very helpful, thanks!
Last edited by zaxxon; 10-10-2012 at 12:50 PM..
Reason: spelling & phrasing
1)We have 2 node cluster RAC on AIX:
->test1
->test3
2) After rebooting server both the node sequentailly, we are getting below error from errpt command :
# errpt |more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
FE2DEE00 0901223914 P S SYSXAIXIF DUPLICATE IP ADDRESS... (2 Replies)
Hi All,
I have an issue with net-snmp communication from a monitoring server to HP UX server.
Following are the details
HP - UX server : 172.16.184.34
Monitoring Server : 172.16.5.57
(Solarwinds Application)I'm running HP-UX's snmp on udp port 161 and net-snmp on udp 1161.
... (0 Replies)
Hi
Is there any default/open source snmp application to
send traps
monitor some processes in Solaris
has MIB package available
that can be used in production environment
I am using
SunOS Server1 5.10 Generic_142910-17 i86pc i386 i86pc
If it has a GUI its a plus :) (1 Reply)
cups-snmp(8) Apple Inc. cups-snmp(8)NAME
snmp - cups snmp backend
SYNOPSIS
/usr/lib/cups/backend/snmp ip-address-or-hostname
lpinfo -v --include-schemes snmp
DESCRIPTION
The CUPS SNMP backend provides legacy discovery and identification of network printers using SNMPv1. When used for discovery through the
scheduler, the backend will list all printers that respond to a broadcast SNMPv1 query with the "public" community name. Additional queries
are then sent to printers that respond in order to determine the correct device URI, make and model, and other information needed for
printing.
In the first form, the SNMP backend is run directly by the user to look up the device URI and other information when you have an IP address
or hostname. This can be used for programs that need to configure print queues where the user has supplied an address but nothing else.
In the second form, the SNMP backend is run indirectly using the lpinfo(8) command. The output provides all printers detected via SNMP on
the configured broadcast addresses. Note: no broadcast addresses are configured by default.
MIBS
The CUPS SNMP backend uses the information from the Host, Printer, and Port Monitor MIBs along with some vendor private MIBs and intelli-
gent port probes to determine the correct device URI and make and model for each printer.
CONFIGURATION
The SNMP backend reads the /etc/cups/snmp.conf configuration file, if present, to set the default broadcast address, community name, and
logging level. The configuration file is documented in cups-snmp.conf(5). The DebugLevel value can be overridden using the CUPS_DEBUG_LEVEL
environment variable and the MaxRunTime value can be overridden using the CUPS_MAX_RUN_TIME environment variable.
SEE ALSO backend(7), cups-snmp.conf(5), cupsd(8), cupsd.conf(5), filter(7), lpinfo(8),
http://localhost:631/help
COPYRIGHT
Copyright 2007-2013 by Apple Inc.
23 April 2012 CUPS cups-snmp(8)
