Sponsored Content
Full Discussion: Snmp
Top Forums UNIX for Advanced & Expert Users Snmp Post 33527 by RTM on Wednesday 8th of January 2003 11:03:35 AM
Old 01-08-2003
Also read your man page for snmpd (if available). From the man page for HP-UX:
Quote:
The Master SNMP Agent (/usr/sbin/snmpdm) and the collection of
subAgents (/usr/sbin/mib2agt, /usr/sbin/hp_unixagt, ...) that would
attach to the Master Agent collectively form a single SNMP Agent. The
SNMP Agent accepts SNMP Get, GetNext and Set requests from an SNMP
Manager which cause it to read or write the Management Information
Base (MIB). The MIB objects are instrumented by the subAgents.

The Master Agent can bind to three kinds of subAgents, namely,

+ Loosely coupled subAgents or separate process subAgents which
open IPC communication channels to communicate with the Master
Agent,

+ Shared library subAgents which are dynamically linkable
libraries,

+ Remotely coupled subagents which could run on a different
processor or operating system and communicate with the Master
Agent using TCP.
And from Solaris:
Quote:
The Master SNMP Agent (snmpdm) and the collection of
subAgents (/usr/lib/libSa...sl and /usr/sbin/*agt) that have
attached to the Master Agent collectively form a single SNMP
Agent. The SNMP Agent accepts SNMP Get, GetNext and Set
requests from an SNMP Manager which cause it to read or
write the Management Information Base (MIB). The MIB
objects are instrumented by the subAgents. The Master Agent
can bind to separate process subAgents and to shared library
subAgents. The subagt_ld command is used to bind a shared
library subAgent to the Master Agent process long after the
Master Agent begins running. The subagt_unld is used to
remove or unload a shared library subAgent from the Master
Agent process.
Also noted that both of these show port 161 is the default port and only one snmpd can run on one port - I would believe you could then start another snmpd on another port, such as the one you mentioned.

So, even if you have only one snmpdm (Master SNMP agent) running, it should coordinate all the sub-agents that have been installed on the system. If the MIBs are installed correctly, it would have no problem 'knowing' about all the different hardware.

If you haven't gotten all the answers to your questions or have more, please post back (and include what OS you are using as that will help in getting more specific answers).
 

7 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

snmp

hello, I am looking for Overall CPU usage info in net-snmp 5.1.2 on solaris 5.8. I didn't see hrProcessorLoad info from host-resource-mib. Is there any other MIB I could look into? Thanks (0 Replies)
Discussion started by: lamou23
0 Replies

2. Infrastructure Monitoring

SNMP - what am I seeing?

Hey everyone! First, thank you in advance for any help you can provide. I'm a fairly experienced linux user, and just getting my feet wet in solaris for a project here at the office. I am trying to use snmpget on a linux box to get information from a Solaris 10 system. The solaris 10 system has... (5 Replies)
Discussion started by: msarro
5 Replies

3. IP Networking

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. (0 Replies)
Discussion started by: prabakar4all
0 Replies

4. 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. (1 Reply)
Discussion started by: prabakar4all
1 Replies

5. IP Networking

SNMP Problem - SNMP not getting to the agent.

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

6. Infrastructure Monitoring

SNMP traps to SNMP server

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

7. 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... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
cmsnmpd(1m)															       cmsnmpd(1m)

NAME
cmsnmpd - SNMP subAgent that services the High Availability cluster MIB objects SYNOPSIS
cmsnmpd DESCRIPTION
cmsnmpd is a subAgent that together with the SNMP Master Agent (snmpdm), form the SNMP Agent for a particular system. The cmsnmpd provides the instrumentation for the High Availability cluster MIB objects. The cmsnmpd is a separate process, yet registers with the SNMP Master Agent, and the two share a procedural interface. Traps The cmsnmpd sends asynchronous event notifications called "traps". By default, SNMP traps are not sent to any destination. To configure the agent to send traps to one or more specific destinations, add the trap destinations to /etc/SnmpAgent.d/snmpd.conf. The SNMP Master Agent and the cmsnmpd collaborate to send High Availability cluster-related traps and information. For example, a trap is sent when the cluster configuration changes, or when a Highly Available package has failed. A complete list of all the cluster-related traps can be found on systems with OpenView installed. On an OpenView management station, the trap descriptions can be found in /etc/opt/OV/share/conf/$LANG/trapd.conf. Supported MIB Objects The Management Information Base (MIB) is a conceptual database of values on the agent system. The cmsnmpd implements the hp-cluster and hp-sgcluster MIB objects. Included in these MIBs are descriptions of the cluster configuration, as well as the current status of each cluster component. A complete list of all the High Availability MIB objects can be found on systems with OpenView installed. On an Open- View management station, the MIB object descriptors can be found in /etc/opt/OV/share/conf/snmpmib. cmsnmpd Startup Startup is controlled by the setting of the AUTOSTART_CMSNMPD variable in the /etc/rc.config.d/cmsnmpagt file. If AUTOSTART_CMSNMPD is set to 1, the cmsnmpd is started automatically each time the system boots. The variable should be set to 1 if you will be using ClusterView to monitor your Highly Available clusters through OpenView. If AUTOSTART_CMSNMPD is set to 0, the cmsnmpd is not started automatically when the system boots. If configured for autostart, the cmsnmpd should startup automatically, after the SNMP Master Agent starts, each time the system reboots, or any time the system transitions from run level 1 to run level 2. When the system enters run level 2, the system will execute /sbin/init.d/SnmpMaster which will start the Master Agent. Similarly, /sbin/init.d/cmsnmpagt will start the cmsnmpd immediately after the Master Agent is started. Prior to executing these startup scripts the system will examine all scripts in /etc/rc.config.d for environment variables which could potentially influence the startup of the Master Agent and the cmsnmpd. See the specific startup script or configuration file for details on supported environment variables. The user should never modify scripts in /sbin/init.d. Instead, the startup behavior should be con- trolled by adjusting values in the configuration script /etc/rc.config.d/cmsnmpd. There are two ways to start the SNMP Master Agent and the cmsnmpd manually. The first way is to execute snmpdm and then start cmsnmpd by invoking the cmsnmpd executable (/usr/lbin/cmsnmpd). The second and simplest way to start the SNMP Agent manually is to execute the snmpd startup script which will invoke the Master Agent and all subAgents who have been installed and designed to operate in this paradigm. The snmpd startup script is layered upon the V.4 startup paradigm and so makes use of the component startup scripts in /sbin/init.d and configuration scripts in /etc/rc.config.d. When snmpd is invoked it passes all its command line arguments to snmpdm and then executes each script found in /sbin/SnmpAgtStart.d. DEPENDENCIES
None. AUTHOR
cmsnmpd was developed by Hewlett-Packard. FILES
/usr/lbin/cmsnmpd /sbin/init.d/cmsnmpagt /etc/rc.config.d/cmsnmpagt /var/adm/SGsnmpsuba.log SEE ALSO
snmpd(1m), snmpd.conf(4). Requires Optional Serviceguard Software cmsnmpd(1m)
All times are GMT -4. The time now is 07:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy