New answers tagged snmp
Problem was on other host side, by default, the SNMP client configuration gives basic information. You must edit /etc/snmp/snmpd.conf and be sure of: rocommunity public default That's it, I got plenty of data now! I have written a small tutorial: https://medium.com/@thomasdecaux/monitor-your-ec2-servers-with-observium-8851d2441aa1
Seems like a NAT traversing issue. Your VMs are in different subnets, so they are communicating through the router. You should take tcpdump and diagnose whether VMs are seeing each other requests/replies.
After a lot of back and forth, it turns out that you must create the community with permission "ALL". A bit questionable with regards to security, however.
OIDs set in the config file become read-only so this is why iso.184.108.40.206.220.127.116.11 is writable only if sysName is not set in config. To have meaningful MIBs, able to write to them and produce effect, one must load them or extend the agent himself.
I've done some of this. The OID you want is called the Q-Bridge-II MIB, at 18.104.22.168.22.214.171.124.126.96.36.199.2 -- it returns a list of MAC addresses associated with the logical port those MAC addresses are listed on. Now you want to beware because there are a couple of wrinkles: firstly the MAC addresses are encoded as row specifications in the OIDs, the VALUES ...
show interfaces extensive will give you just about everything. Show vlan also is valid and helpful.
Top 50 recent answers are included