7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
2. Infrastructure Monitoring
Dear Champs,
I am new to unix, and need to configure linux server to send below traps to a SNMP server.
Monitoring TRAP Disk Space Low
Monitoring TRAP Memory Low
Monitoring TRAP CPU high
Monitoring TRAP Admin login/Logoff
Please help me how to send this information to my SNMP server... (2 Replies)
Discussion started by: stavar
2 Replies
3. IP Networking
I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem.
Description:
There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent.
I see where the... (0 Replies)
Discussion started by: broberts
0 Replies
4. Red Hat
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. (1 Reply)
Discussion started by: prabakar4all
1 Replies
5. IP Networking
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. (0 Replies)
Discussion started by: prabakar4all
0 Replies
6. AIX
Can someone help setting up snmpv3? (1 Reply)
Discussion started by: dunman22
1 Replies
7. UNIX for Advanced & Expert Users
Hi I have doubt/confusion on the SNMP Agents.
We know that these days use of SNMP is growing more.
Most of the venders who manufacture computer based accessories provide SNMP support with thier Unique MIB
for Managing/Monitoring their Hardware.
So, through the use of Management software,... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies
LEARN ABOUT DEBIAN
snmp::info::layer3::netsnmp
Info::Layer3::NetSNMP(3pm) User Contributed Perl Documentation Info::Layer3::NetSNMP(3pm)
NAME
SNMP::Info::Layer3::NetSNMP - SNMP Interface to L3 Net-SNMP Devices
AUTHORS
Bradley Baetz and Bill Fenner
SYNOPSIS
# Let SNMP::Info determine the correct subclass for you.
my $netsnmp = new SNMP::Info(
AutoSpecify => 1,
Debug => 1,
DestHost => 'myrouter',
Community => 'public',
Version => 2
)
or die "Can't connect to DestHost.
";
my $class = $netsnmp->class();
print "SNMP::Info determined this device to fall under subclass : $class
";
DESCRIPTION
Subclass for Generic Net-SNMP devices
Inherited Classes
SNMP::Info::Layer3
Required MIBs
UCD-SNMP-MIB
NET-SNMP-TC
HOST-RESOURCES-MIB
Inherited Classes' MIBs
See SNMP::Info::Layer3 for its own MIB requirements.
GLOBALS
These are methods that return scalar value from SNMP
$netsnmp->vendor()
Returns 'Net-SNMP'.
$netsnmp->os()
Returns the OS extracted from "sysDescr".
$netsnmp->os_ver()
Returns the software version extracted from "sysDescr", along with the Net-SNMP version.
$netsnmp->uptime()
Returns the system uptime instead of the agent uptime. NOTE: discontinuity timers and other Time Stamp based objects are based on
agent uptime, so use orig_uptime().
$netsnmp->serial()
Returns ''.
Globals imported from SNMP::Info::Layer3
See documentation in SNMP::Info::Layer3 for details.
TABLE ENTRIES
These are methods that return tables of information in the form of a reference to a hash.
Overrides
$netsnmp->i_ignore()
Returns reference to hash. Increments value of IID if port is to be ignored.
Ignores loopback
Table Methods imported from SNMP::Info::Layer3
See documentation in SNMP::Info::Layer3 for details.
NOTES
In order to cause SNMP::Info to classify your device into this class, it may be necessary to put a configuration line into your snmpd.conf
similar to
sysobjectid .1.3.6.1.4.1.8072.3.2.N
where N is the object ID for your OS from the "NET-SNMP-TC" MIB (or 255 if not listed). Some Net-SNMP installations default to an
incorrect return value for "system.sysObjectId".
In order to recognize a Net-SNMP device as Layer3, it may be necessary to put a configuration line similar to
sysservices 76
in your snmpd.conf.
perl v5.12.4 2011-09-28 Info::Layer3::NetSNMP(3pm)