Sponsored Content
Special Forums IP Networking Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161 Post 302543122 by prabakar4all on Friday 29th of July 2011 03:37:16 PM
Old 07-29-2011
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.
 

10 More Discussions You Might Find Interesting

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

2. 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 (8 Replies)
Discussion started by: champion
8 Replies

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

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

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

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

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

8. 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

9. 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

10. 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... (1 Reply)
Discussion started by: davix
1 Replies
UDP(4)							   BSD Kernel Interfaces Manual 						    UDP(4)

NAME
udp -- Internet User Datagram Protocol SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> int socket(AF_INET, SOCK_DGRAM, 0); DESCRIPTION
UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family. UDP sockets are connectionless, and are normally used with the sendto(2) and recvfrom(2) calls, though the connect(2) call may also be used to fix the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used). UDP address formats are identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet address format. Note that the UDP port space is separate from the TCP port space (i.e., a UDP port may not be ``connected'' to a TCP port). In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved ``broadcast address''; this address is network interface dependent. Options at the IP transport level may be used with UDP; see ip(4). MIB VARIABLES
The udp protocol implements a number of variables in the net.inet branch of the sysctl(3) MIB. UDPCTL_CHECKSUM (udp.checksum) Enable udp checksums (enabled by default). UDPCTL_MAXDGRAM (udp.maxdgram) Maximum outgoing UDP datagram size UDPCTL_RECVSPACE (udp.recvspace) Maximum space for incoming UDP datagrams udp.log_in_vain For all udp datagrams, to ports on which there is no socket listening, log the connection attempt (disabled by default). udp.blackhole When a datagram is received on a port where there is no socket listening, do not return an ICMP port unreachable message. (Disabled by default. See blackhole(4).) ERRORS
A socket operation may fail with one of the following errors returned: [EISCONN] when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the desti- nation address specified and the socket is already connected; [ENOTCONN] when trying to send a datagram, but no destination address is specified, and the socket has not been connected; [ENOBUFS] when the system runs out of memory for an internal data structure; [EADDRINUSE] when an attempt is made to create a socket with a port which has already been allocated; [EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists. SEE ALSO
getsockopt(2), recv(2), send(2), socket(2), blackhole(4), inet(4), intro(4), ip(4) HISTORY
The udp protocol appeared in 4.2BSD. BSD
June 5, 1993 BSD
All times are GMT -4. The time now is 11:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy