Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

10 More Discussions You Might Find Interesting

1. AIX

AIX native SNMP producing limited results when walking MIB tree

The company I work for has various AIX servers that I've recently migrated to AIX 7.1 (from 6.1). Some are powerHA clusters some are not. Likewise, the systems engineer that I replaced had net-snmp installed on said clustered systems. Long story short I am re-invoking AIX's native SNMP (v3) for...

2. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

i am working with embedded system -Dell DCS management sub system. my question is as below: currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP...

3. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide.

4. Infrastructure Monitoring

Solaris 10 Snmp command to MiB OID

Hi guys, I am doing follow this guy Tech deposits. : iostat monitoring for zenoss and such I stuck at this step: Add a line into /etc/snmp/snmpd.conf file: pass .1.3.6.1.4.1.2021.255.1 /usr/local/bin/sar_iostat_snmp.sh -m 1 -d dev253 -o .1.3.6.1.4.1.2021.255.1 and test snmp by the...

5. Infrastructure Monitoring

UDP Port 161

hi guys My linux server have SNMP configure port by default is 161 (UDP) now my monitor team - who are using Nagios - say the server are not being monitor so check netstat -lnu and I see all is OK and snmp service is running fine what else should I check about this port 161? to see if it is...

6. Solaris

import UCD-SNMP-MIB into snmpd

I was setting up snmpd on a Solaris 8 server and needed more than the standard mibs, so I installed net-snmp so I could get the UCD-SNMP-MIB. I did not know another way, but I am able to monitor what I need. I would like to know if I could import the UCD-SNMP_MIB into the existing...

7. Solaris

Any Idea about (SNMP) HOST-RESOURCES-MIB

Hello , I am using (Application Manager 7) software for monitoring. I want to add the servers to monitored using SNMP but it shows this error HOST-RESOURCES-MIB is not implemented in the Snmp Agent. your help is highly appreciated ..... :)

8. SCO

Want to set up SNMP with MIB on SCO OS5

Want to setup snmp with mib to track system issues on SCO OS5.0.5. Is there somewhere I can look that will give me insight in how to answer some of the questions the mkdev snmp asks?

9. UNIX for Dummies Questions & Answers

Changing SNMP port number

hi, i am using Sun Solaris 8 (Sparc). Currently there is a SNMP agent running on port 161. How should I change it to port 8001? which file to modify and restart is necessary? pls teach me the information. thanks

10. UNIX for Advanced & Expert Users

Sending SNMP Traps in AIX / Unix

Hi, Just wondering if anyone knows how can I send an SNMP Trap in Unix Environment(AIX) to another machine (NT/Ux) after having activated the SNMP in the AIX. Can this be done by using a single command line or do I have to write a script for it? Thanks in advance for your advices. :)

LEARN ABOUT DEBIAN

torrus_snmpfailures

TORRUS_SNMPFAILURES(8)						      torrus						    TORRUS_SNMPFAILURES(8)

NAME

       snmpfailures - Displays SNMP collector failures.

SYNOPSIS

       torrus snmpfailures --tree=TREENAME [options...]

OPTIONS

       --details
	   In addition to failure counters, list the failed SNMP hosts and the time stamps of failure events.

       --help
	   Displays a help message.

DESCRIPTION

       This utility prints the SNMP collector failure information in JSON format.  Without --details option, it prints only the failure counters.

       Upon collector startup or after the tree re-compilation, the failure counters are reset to zero.

       The output is very convenient for further automatic processing in any scripting language.

       The top level of the output is a JSON object with the following name/value pairs:

       total_unreachable: NUMBER
	   Displays the number SNMP hosts that are currently unreachable.  The number adds up across multiple collector instances for a given
	   tree.  If a host becomes reachable again, the number is decreased.

       total_deleted: NUMBER
	   Displays the number SNMP hosts that are completely removed from SNMP collection for the life cycle of the collector process. This
	   happens when a host is unreachable for too long time and the collector gives up to reach it again.  The number adds up across multiple
	   collector instances for a given tree.

       total_mib_errors: NUMBER
	   Displays the number of MIB errors (noSuchObject, noSuchInstance, and endOfMibView) during the collector life cycle.	The number adds up
	   across multiple collector instances for a given tree.

       detail_unreachable: OBJECT, detail_deleted: OBJECT
	   If the option --details is specified, these objects contain the host names and timestamps of the failures.  The keys are
	   contactenations of SNMP host, UDP port, and SNMP community separated by "|".  The values are objects representing the UNIX timestamp
	   and a human-readable time string.

       detail_mib_errors: OBJECT
	   If the option --details is specified, this object displays the MIB error details: for each SNMP host, it lists the datasource leaves
	   which had these errors and the event timestamps.

EXAMPLES

       The following example illustrates an SNMP host unreachable:

	torrus failures --tree=main --details
	{
	   "detail_deleted" : {},
	   "detail_mib_errors" : {},
	   "detail_unreachable" : {
	      "217.101.101.101|161|public" : {
		 "time" : "Fri Jul 23 14:15:10 2010",
		 "timestamp" : 1279887310
	      }
	   },
	   "total_deleted" : 0,
	   "total_mib_errors" : 0,
	   "total_unreachable" : 1
	}

       The following example illustrates a MIB error:

	torrus failures --tree=main --details
	{
	   "detail_deleted" : {},
	   "detail_mib_errors" : {
	      "217.101.102.102|161|public" : {
		 "count" : 1,
		 "nodes" : {
		    "/Routers/CMTS3/Temperature_Sensors/sensor_01" : {
		       "time" : "Fri Jul 23 15:26:14 2010",
		       "timestamp" : 1279891574
		    }
		 }
	      }
	   },
	   "detail_unreachable" : {},
	   "total_deleted" : 0,
	   "total_mib_errors" : 1,
	   "total_unreachable" : 0
	}

SEE ALSO

       torrus(8),

NOTES

       See more documentation at Torrus home page: http://torrus.org

AUTHOR

       Stanislav Sinyagin <ssinyagin@yahoo.com>

torrus 2.03							    2013-07-26						    TORRUS_SNMPFAILURES(8)

IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

10 More Discussions You Might Find Interesting

1. AIX

AIX native SNMP producing limited results when walking MIB tree

Discussion started by: davix

2. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

Discussion started by: vipul_prajapati

3. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Discussion started by: prabakar4all

4. Infrastructure Monitoring

Solaris 10 Snmp command to MiB OID

Discussion started by: tien86

5. Infrastructure Monitoring

UDP Port 161

Discussion started by: karlochacon

6. Solaris

import UCD-SNMP-MIB into snmpd

Discussion started by: csross

7. Solaris

Any Idea about (SNMP) HOST-RESOURCES-MIB

Discussion started by: adel8483

8. SCO

Want to set up SNMP with MIB on SCO OS5

Discussion started by: herd5cusa

9. UNIX for Dummies Questions & Answers

Changing SNMP port number

Discussion started by: champion

10. UNIX for Advanced & Expert Users

Sending SNMP Traps in AIX / Unix

Discussion started by: goliath

LEARN ABOUT DEBIAN

torrus_snmpfailures