Unsolved
This post is more than 5 years old
29 Posts
0
8640
Monitoring VNX5300 via SNMP
I have a Nagios system that I would like to monitor our two VNX5300's. Using the sparse VNX document on SNMP I have modified the community string of the snmp daemon for using SNMP version 2c. Unfortunately running snmpwalk from my monitoring server resutls in a "Timeout: No Response from x.x.x.x".
Just for kicks I SSH'd back into the Control Station to see if there were any snmp utilities and thankfully the snmpwalk command was available there as well. Running snmpwalk against the localhost yielded the same failing results as above.
I did not see any option for specifying an ip to send traps to, so I do not know if that is an issue? Missing something and would appreciate any help.
Rainer_EMC
8.6K Posts
0
October 14th, 2011 09:00
Which SNMP agent are you querying ?
The SNMP agent on the control station is separate from the SNMP agent on the data mover.
On the CS it’s a simple UCD SNMP agent as with other Linux systems – configured in /etc/snmp
The data mover SNMP config is done with server_snmp or the GUI.
Its documented quite well in the
Configuring Events and Notifications on VNX for File
manual that’s part of your documentation set and also on Powerlink.
Rainer
Devops2
14 Posts
0
March 23rd, 2015 17:00
I have a same issue and I don't think it need CS to get the snmp info.
I think it need get the snmp info from data mover.
Devops2
14 Posts
0
March 23rd, 2015 17:00
I could get the snmp info from 2 storage processors but I can't get info from data mover.
The EMC model is VNX5300
The data mover(server_2) IP is 192.168.10.50
server_snmpd server_2 -info
server_2 :
enabled = Yes
location = system location is not set.
contact = system contact is not set
community = public
server_snmpd server_2 -service -status
server_2 :
SNMP Running
C:\usr\bin>snmpwalk -c public -v 2c 192.168.10.50
Timeout: No Response from 192.168.10.50
AlvaroG
97 Posts
0
March 24th, 2015 07:00
You have to configure it on the datamover.
Look at page 52 of the manual Rainer toll you.
Configure SNMP on Data Movers
The server_snmpd command manipulates SNMP configuration values of the server agent
for the specified Data Mover.
The values you can set or modify are community, syscontact, and location. Using SNMPv3
on VNX and EMC VNX Command Line Interface Reference for File provides more information
about this command.
Action
To assign a new value of private to a server SNMP agent’s community for a Data Mover, type:
$ server_snmpd server_2 -modify -community private
Output
server_2 :
OK
Rainer_EMC
8.6K Posts
0
March 24th, 2015 10:00
Yes – if you configure it correctly it will work
Besides – on the other forum post it looked like 192.168.10.50 was the IP address of the control station.
If you want a SNMP response from the data mover you need to use the correct IP address of the data mover.
Devops2
14 Posts
0
March 24th, 2015 13:00
I think that IP is on the data mover.
Devops2
14 Posts
0
March 24th, 2015 14:00
server_snmpd server_2 -info
server_2 :
enabled = Yes
location = system location is not set.
contact = system contact is not set
community = public
server_snmpd server_2 -service -status
server_2 :
SNMP Running
Rainer_EMC
8.6K Posts
0
March 24th, 2015 14:00
Just post the Output of server_ifconfig server_2 -a
Also - can you Ping that IP from the Host you are running smpwalk from?
Devops2
14 Posts
0
March 24th, 2015 15:00
server_2 :
el30 protocol=IP device=mge0
inet=128.221.252.2 netmask=255.255.255.0 broadcast=128.221.252.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:16:38:e6:14 netname=localhost
el31 protocol=IP device=mge1
inet=128.221.253.2 netmask=255.255.255.0 broadcast=128.221.253.255
UP, Ethernet, mtu=1500, vlan=0, macaddr=0:60:16:38:e6:15 netname=localhost
CIFS_Interface02 protocol=IP device=VNX_ExtremeStack2_LACP
inet=192.168.42.13 netmask=255.255.255.0 broadcast=192.168.42.255
UP, Ethernet, mtu=1500, vlan=42, macaddr=0:60:48:1e:d:da
CIFS_Interface01 protocol=IP device=VNX_ExtremeStack2_LACP
inet=192.168.50.17 netmask=255.255.255.0 broadcast=192.168.50.255
UP, Ethernet, mtu=1500, vlan=50, macaddr=0:60:48:1e:d:da
loop6 protocol=IP6 device=loop
inet=::1 prefix=128
UP, Loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost
loop protocol=IP device=loop
inet=127.0.0.1 netmask=255.0.0.0 broadcast=127.255.255.255
UP, Loopback, mtu=32768, vlan=0, macaddr=0:0:0:0:0:0 netname=localhost
-----------------------
C:\>ping 192.168.10.50
Pinging 192.168.10.50 with 32 bytes of data:
Reply from 192.168.10.50: bytes=32 time<1ms TTL=63
Reply from 192.168.10.50: bytes=32 time<1ms TTL=63
Reply from 192.168.10.50: bytes=32 time<1ms TTL=63
Reply from 192.168.10.50: bytes=32 time<1ms TTL=63
Ping statistics for 192.168.10.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
AlvaroG
97 Posts
0
March 24th, 2015 16:00
You are pinging the Control Station IP.
Your Datamovers IPs are:
192.168.42.13
192.168.50.17
There should you point the snmpwalk.
porterandme
17 Posts
0
March 27th, 2015 05:00
I fully understand the SNMP for the data movers. Is there a way to setup SNMP on the control station and SPs that will allow snmp polling?
porterandme
17 Posts
0
March 27th, 2015 06:00
Makes sense for the cs. Are the sps able to be polled or do they just send traps?
AlvaroG
97 Posts
0
March 27th, 2015 06:00
For the CS you should use Linux commands
Check status
/etc/init.d/snmpd status
Start:
/etc/init.d/snmpd start
Stop:
/etc/init.d/snmpd stop
Usage: /etc/init.d/snmpd {start|stop|status|restart|condrestart|reload}
Also Rainer answer
"the control station SNMP is stock Linux – it wont get you much info – it doesn’t cover the file and block functionality on the DM or SP.
But you need to configure sndmd.conf first"