Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
As a start check http://forums.cacti.net/viewtopic.php?t ... ight=as400.
I don't know very much about AS/400. But if it has an SNMP implementation you need a tool to see what OIDs your AS/400 offers and an AS/400 MIB file that explains the returned values.
I would suggest that you
* check if AS/400 offers SNMP
* if yes, get the MIB for AS/400 from http://www.mibdepot.com
* get the tool GETIF from http://www.wtcs.org/snmp4tpc/getif.htm
* Move the AS/400 MIB to the GETIF directory (see the GETIF readme) and then GETIF can tell you the meaning of the AS/400 OIDs.
# nmap xx.xxx.xxx.xxx -p 161 -sU
Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2004-12-30 16:07 CET
Interesting ports on xx.xxx.xxx.xxx:
PORT STATE SERVICE
161/udp open snmp
Nmap run completed -- 1 IP address (1 host up) scanned in 0.924 seconds
$ snmpwalk -v 1 -c public xx.xxx.xxx.xxx sysdescr
Timeout: No Response from 10.150.113.253
We've looked at IBM's redbook "An Introduction to AS/400 SNMP Support", but everything seems to be well configured.
Getting no reply from SNMP could have the following reasons (in my experience):
* SNMP isn't running at all -> check if there is a SNMP daemon running
* SNMP uses a different port -> check the SNMP config file
* SNMP isn't configured for the specified community -> check the SNMP config file for the community string.
* SNMP doesn't allow your computer to query -> check the SNMP config file for the hostnames/IP addresses allowed to query the SNMP daemon
As I know nothing about AS/400 this can only give you a starting point.
Maybe you can post the SNMP config file so we all can have a look at it.
fmangeant wrote:I'm trying to graph an AS/400 server, but it doesn't work. The SNMP agent seems to be running :
...
Do you know what could be wrong ?
I realize this is a very old message, but we're revisiting getting some decent metrics off our iSeries/AS400 machines. And immediately we ran into the same problem: SNMP running, but no response from an snmpwalk.
Turns out, the OS/400 implementation of SNMP, as with many things in its TCP stack, is slightly off. Our firewalls were blocking the snmp-replies. Basically, with most devices you send an SNMP-read to port 161 with a source of some random high port, and it will reply with source port 161. The iSeries, however, chooses a random source port to reply with. Fortunately, our firewall had an option for snmp for "Accept replies from any port." This solved the problem.
I'm putting together some graphs... If I find anything useful with the default snmp agent I'll be sure to post them.