I want to add a few linux server to our monitoring system (solarwinds).
We have to get this information by snmp.The items we need are:
1-In Byte Transferred on every network interface
2-Out Byte Transferred on every network interface.
3-Memory Usage
4-Memory Free
5-CPU usage
6-Free Disk space on partiotion
7-Uptime
I could not find snmp OID or names for this object to fetch.
I am analyzing memory usage on a Linux system. When I run vmstat -s, I see the following:
waffleman@waffle-iron:~$ vmstat -s 3549184 K total memory 3206708 K used memory 1918012 K active memory 1037320 K inactive memory 342476 K free memory
[Code]...
I know the system has 4096 MB of RAM installed, but why does it show only 3466 MB? Can this be interpreted as total "available" memory? Perhaps the missing 630 MB is being used by the kernel and cannot paged out?
I also tried this on on an Embedded Linux system and saw a similar result. The DRAM chip has 128 MB, but only 124 MB shows up in vmstat.
[root@big-bad-joe /]# more /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 7) ------------------------------------------------------------------
1. Is that WA% only disk I/O or can it include network IO? 2. How do I identify which processes are making up that WA statistic? 3. Why does iostat report 100% utilization when the drive read/write speeds are under 1MB/s?
The reason I'm asking.
My Oracle stats are saying that the drives are running at about 5MB/s right now, the WA is 55%, and the iostat -m -x is reporting the drives running at 100% utilization with a read/write rate under 1MB/s. The read speed of the drive is 98MB/s (tested with hdparm -tT when I installed the drives)
I know I have a few queries using full tables scans which I'm working on but I'd think that 100% utilization should be running at the full 98MB/s.
I want to try to identify which process (most likely and oracle one) is using the 100% utilization/55% WA.
I have been trying to set up SNMP monitoring using Cricket. I believe I have Cricket running fine, however I also believe that I have SNMP set up wrong. When I do an SNMPWALK I get the following:
[Code]....
This tells me I have SNMP running, however I would expect to see a lot more data... Am I correct, should I see more data? I spoke to a friend, and he suggested that I have something not set up correctly in SNMP dealing with the community string...
recently i have installed Squid Server and i want to monitor traffic in my lan with mrtg. so i have installed snmp but when i run "snmp -v 1 -c public localhost" i have got "Timeout: no response from localhost". i have turned off the firewall but i get same error.
I just narrowly passed another exam on UNIX Academy. Their DVDs are incredible. While I made some mistakes here and there.I was really stumbled upon a question that was formulated something like "SNMP for managing Linux machines remotely".I can't remember the exact definition. I'm not sure what it was about.I was under impression that SNMP it is a carrier protocol for commands like "ping" and "traceroute". I was trying to read about it online but it is way too broad and technical, they're loosing me on very first page. I suspect there's some kind of product or technology that uses SNMP in some way to handle Linux, I'm not sure.
I have a log file and there are many different types of exception in this file. These could be looked as follow:
Code:
One can see there two types of exceptions: ORGNoCompetenceException and SocketException.
I will filter out the name/type of exception and the number of each type of exception. At last, this statistic data will write to file and create a Excel table.
I have to get soem statistic about interfaces from /proc/net/dev. but statistic on this file is reset when get reach more than 4G byte.I think linux has limitation on this case.
Iam using snmp to access the remote system data.But according to the requirement iam encoding the snmp request data to OAMPDU packet format and sending to remote system.the remote system receives the OAMPDU packet,decodes it and is sending the snmp packet to snmp agent through UDP socket which is bind to port 161.but iam unable to receive the response from snmp agent.i have created a udp socket which is bind to 161 port to receive the response.
if i use any other free port number other than 161 for receiving snmp agent is not sending the response to that port.can any one please suggest me how to overcome this problem.Can we configure the different ports for tx,rx ?How do we know on which port does snmp sends the response ???
I need to be able to send snmp traps based on certain severity or content of syslog messages. Can this be done from standard linux? Alternatively, are there MIB's out there that support syslog events so I can get the status from snmp?
I am trying to calculate band Width on few interfaces. Every thing works fine, bandWidth goes up when user loged in it goes down the moment working hrs are over. Only problem is once in a while it show negative bandWidth ? I make that script to send information in-case it negative. here are few examples
Code:
from IP XX.X.X.X interface X inCounters new = 1056124169 old = 484753332 outCounters new = 71539457 old = 4205963496 inDelta = 571370837
[code]....
Code:
inPut utilization = (change x 8 X 100) / (change in time X connection speed)
but that would not matter because , problem is caused by lowering count on in and out packets.
I have installed Net-SNMP.It is binded to port udp 161I start it with the command: snmpd -Lo when I do snmpget -v 1 -c public localhost system.sysObjectID.0on the same machine the snmpd is running on- I get a respond SNMPv2-MIB::sysObjectID.0 = OID: ccitt.1when I send same request from another machine (using SNMPc program) - I see no reaction.I used "wireshark" to monitor packets, and I see the requests sent from the other machine. I also see them get to the first machine.
I just installed a fresh copy of RHEL 5.4 64-bit on a new machine, taking default configuration during the setup process. Then I realized we need to install SNMP on it. I found the following packages on the RHEL DVD and tried to install them, using both the Red Hat GUI for package installation and also through the command "rpm -i {package_name.rpm}". But I am getting dependency errors. The dependent components are not found on the DVD even though I have it inserted in the drive. Can someone advise how I can add SNMP to an existing RHEL machine?
I'm configuring a server for Zenoss monitoring over SNMP, but the SNMP process is running on 127.0.0.1:161 instead of 0.0.0.0:161, according to "netstat -an | grep -i udp".
Not sure why this is happening, but Zenoss reports that SNMP is not running due to this. My snmpd.conf file is the same as all of the other servers that are running SNMP, but this is the first Debian server I've tried to add (the other's are CentOS).
I have a favor to ask, I've been having a really hard time trying to understand how snmp traps work, what can they do for you, and why they are useful. I've done some research and I've even set up snmp clients on linux systems, not necessarily the traps. I know they communicate on port 161 and 162 and I also know that you set them up to connect to a community string. Still I cant grasp the concept. If you don't mind can any one break it down for me, in very basic terms.
am not able to install snmp in ubuntu, this is the code i followed from ....., "apt-get update and then apt-get install snmpd. the problem occurs is "could not resolve sg.security.com" and i cant updates using update manager.
I have enabled SNMP monitoring in my debian box (using apt-get install snmp) and configured it to allow my PC to query the server.
I'm able to query the server and get SNMP data but when I get STG to give me a per/second graph of the interface octets, it only updates the data every 12 seconds or so.
Is this a setting in SNMP which could be causing this problem? If so, how can I enable it so that SNMP can give me up to the second octet rates.
2 machines (one of them working as a server to monitor the network with IP 192.168.100.110 and the other one to be monitored with IP address 192.168.100.1):
In the first machine:
snmpwalk -v1 localhost -c public sysName (working fine) snmpwalk -v1 192.168.100.1 -c public sysName (don't works -> Timeout: No Response from 192.168.100.1)
In the monitored machine:
snmpwalk -v1 192.168.100.110 -c public sysName (it works) snmpwalk -v1 localhost -c public sysName (dont works -> Timeout: No Response from localhost)