SNMP alarming - No Data

[vaoldschl]

I have tried to set up SNMP from one of my S8500s and one of my S8700s using the web maintenance interface.

I have alternately configured traps and agents trying to get it to work either way. I have set the firewall to allow ports 161 and 162 both directions. My last step was to download SNScan, plug in the telephone server's IP and scan for listening on ports 161 and 162. I'm getting nothing. I've done a netstat -u -l on the server and get
udp 0 0 *:snmp *:*
udp 0 0 *:snmptrap *:*
I'm sorry to admit I don't know what that means but I thought it might mean the service was running and waiting for a connection. I was, however, worried that it didn't say it was in 'Listen' state.

Anybody think of something I might have missed or do I need to pull the network group in to start looking at their stuff? Thanks.

 

[sroush]

You don't need to mess with "IP Addresses for IP access" unless you are going to query (or update) the server.
I assume you just want to receive traps.
I'd guess that you forgot to bring the "Master Agent" down and back up. Go to "Agent Status" on the Web page and cycle the Master Agent down and up. Then it will pick up your changes.
I believe the newer versions (4 and up?) have a "test" capability, but not the older versions. I don't have a system in front of me to test, but netstat may be useful - the CM is also a trap receiver in addition to being a trap sender.
You might also type this at the CM command line:
ps -ef | grep snmp

The trap program will display something like this: "/usr/sbin/snmptrapd"

steve

 

[vaoldschl]

I did bring the Agent up and down prior to making changes. The only reason I added the NMM to the IP address list is because I couldn't get the traps working so was going to try gets instead. I've been using netstat -u -l to try and figure out what was going on from the cli while also using the test from the web interface(my systems are mostly CM 4 but I do have a 3 and a 5) and I never see a connection made. I will try the command you recommend when I get back to the office. Thanks.

 

[AvayaTier3]

Steve asked if you brought the Agent down and up after the changes....

That ps command will only show if snmp process is running.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[vaoldschl]

I'm sorry I was unclear: I brought the agent down, made the changes, then brought the agent up. Then, when it still wasn't working I brought the agent down, waited a couple of minutes and then brought the agent back up again.

 

[vaoldschl]

All right running 'ps -ef | grep snmp' gives me:

/usr/sbin/snmptrapd -f -m etc/opt/ecs/trapmgr and goes on through a laundry list of other stuff and finishes with:

root 20623 4498 Mar16 ? 00:00:00 /usr/sbin/snmptrapd -d

Then a line related to my login and running the ps -ef command.

I'm going to go research to find out what I might be reading but if somebody here could clue me in that would be much appreciated. Mar 16 is when I tried turning this on so I'm deducing that root line is showing me when the changes were made at the web interface level.

As ever, Thanks

 

[vaoldschl]

Okay, latest thing I've found: When I do a netstat for listening ports and ask it to come out in numeric format it shows 161 and 162 listening but local address output is 0.0.0.0. I'm thinking that may be significant.

 

[vaoldschl]

Can anyone who has this working share what the web interface netstat from their system shows for ports 161 and 162? I show the service running and I've verified my configuration for the receiving server but still when I run a query on my network using SNscan for ports 161 and 162 the Communication Manager's IP address never shows up. I'm wondering if the network folks don't have an ACL out there that is blocking that traffic but want to make darned sure my configuration is groovy before I send them looking. Thanks.

 

[vaoldschl]

Found the problem. Researching another issue, actually, and came across an error in the web interface http system log:

failed to open /etc/snmp/snmpd.cnf for reading: 13: Permission denied

Apparently I don't have access. Kind of bites that I can go through all the steps, get it to look like it's working and then get kicked in the a*$ in the background.

 

[sroush]

1. I'd log in with your "best" login and repeat the entire process, just in case it was a transient problem
2. If that does not work, see if you can rename the "conf" file and then create a new one with better permissions:
mv /etc/snmp/snmpd.cnf /etc/snmp/snmpd.cnf.old
cp /etc/snmp/snmpd.cnf.old /etc/snmp/snmpd.cnf
chmod 777 /etc/snmp/snmpd.cnf
3. If that does not work, tell us what the permissions are. Maybe someone can tell you how to fix them.
ls -ld /etc /etc/snmp /etc/snmp/snmpd.cnf
4. If all else fails, call Avaya and tell them to fix the file permissions

steve