Sponsored Content
Operating Systems Linux Red Hat Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161 Post 302543121 by prabakar4all on Friday 29th of July 2011 03:32:19 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. 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

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
BLACKHOLE(4)						   BSD Kernel Interfaces Manual 					      BLACKHOLE(4)

NAME
blackhole -- a sysctl(8) MIB for manipulating behaviour in respect of refused TCP or UDP connection attempts SYNOPSIS
sysctl net.inet.tcp.blackhole[=[0 | 1 | 2]] sysctl net.inet.udp.blackhole[=[0 | 1]] DESCRIPTION
The blackhole sysctl(8) MIB is used to control system behaviour when connection requests are received on TCP or UDP ports where there is no socket listening. Normal behaviour, when a TCP SYN segment is received on a port where there is no socket accepting connections, is for the system to return a RST segment, and drop the connection. The connecting system will see this as a ``Connection refused''. By setting the TCP blackhole MIB to a numeric value of one, the incoming SYN segment is merely dropped, and no RST is sent, making the system appear as a blackhole. By setting the MIB value to two, any segment arriving on a closed port is dropped without returning a RST. This provides some degree of protection against stealth port scans. In the UDP instance, enabling blackhole behaviour turns off the sending of an ICMP port unreachable message in response to a UDP datagram which arrives on a port where there is no socket listening. It must be noted that this behaviour will prevent remote systems from running traceroute(8) to a system. The blackhole behaviour is useful to slow down anyone who is port scanning a system, attempting to detect vulnerable services on a system. It could potentially also slow down someone who is attempting a denial of service attack. WARNING
The TCP and UDP blackhole features should not be regarded as a replacement for firewall solutions. Better security would consist of the blackhole sysctl(8) MIB used in conjunction with one of the available firewall packages. This mechanism is not a substitute for securing a system. It should be used together with other security mechanisms. SEE ALSO
ip(4), tcp(4), udp(4), ipf(8), ipfw(8), pfctl(8), sysctl(8) HISTORY
The TCP and UDP blackhole MIBs first appeared in FreeBSD 4.0. AUTHORS
Geoffrey M. Rehmet BSD
January 1, 2007 BSD
All times are GMT -4. The time now is 05:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy