Hi,

I lanuched an AMI "Observium - Network Management and Monitoring by TurnKey Linux" to monitor couple of Cisco routers I have, unfortunately it keep saying "No reply on community public using v1"

I made sure the router configured properly using snmpwalk tool but the problem persist.

Thanks a lot for your help.

Forum: 
Jeremy Davis's picture

I can however confirm that it 'should' work. I have it running at work and it merrily observes the server, all the PCs and the (cheap consumer grade) modem/router.

So I imagine that it is most likely something specific to your network or hardware. Out of interest I did a quick google and could't find much. Perhas you should double check your config (no doubt they have s wiki or someother docs) and/or post on the Observium mailing list/forums (they should have one or the other, or perhaps both - although if they do, pick just one to post on...).

Eric (tssgery)'s picture

When you say you launched an AMI... Are you running Observium on AWS? Or on the same network as the routers you want to monitor? 

If it's on AWS, you won't be able to monitor routers on your private network as SNMP packets would be blocked somewhere along the way. If you login via sash to the Observium instance, can you ping the routers in question?

The observium is working on Amazon EC2 server readymade package called "Observium - Network Management and Monitoring by TurnKey Linux"

I tried snmpwalk from my personal computer to the Cisco router which is connected to the internet with a public IP without any firewalls and the response was fine and it is reading the snmp on the router.

The host is pingable from the amazon ec2 server

64 bytes from x.x.x.x: icmp_req=1 ttl=232 time=164 ms

I tried snmpwalk from the amazon ec2 obsevium server and the response was "Timeout: No response from x.x.x.x"

I changed the timeout in the snmpwalk to be 1, 30 and 60 sec and still "Timeout: No response from x.x.x.x"

Jeremy Davis's picture

I could be wrong (and no doubt Eric will correct me as he designed the Observium appliance) but I would think that with the appliance running on AWS the only reliable way to monitor your LAN would be to configure a VPN tunnel from your Observium appliance to your LAN.

Unfortunately I can't give you any guidance on how to achieve that as i haven't done it (I understand the theory but never performed it in practice).

Eric (tssgery)'s picture

I suspect you are seeing one of two problems (or possibly both):

  1. SNMP is not listening on the public interface of your router.
  2. SNMP packets are being blocked outbound from Amazon OR inbound from your ISP. I wouldn't be surprised if this were the case.

 

I'm not a VPN expert, but setting up a VPN might work. You'd need the VPN server within your network and the VPN client on the ec2 instance. That said, I don't think that's wise from a security standpoint; if your ec2 instance becomes compromised, your whole network is compromised :(

For network monitoring, you really want the Observium appliance on the same network as is being monitored so I'd run a VM or a low cost server within your network.

nfsravens's picture

It is pretty strange forward to run the Observium from Turnkey.

The only problem to me is that ficking Windows 8.1 and Java gave me a hard time to bring up the Java console and finally solve. Then I add the router IP into /etc/hosts with a host name.

I don't know what Cisco model you are using but I have working with those small business router is pretty easy. Enable Ping from WAN side, enable remote SNMP, add a snmp manager reocrd in SNMP and reference to your AWS instant public IP with 161 for port and community. 

Http to Observium instant, add device, put the router name which created in /etc/hosts, let the snmp version to 2c and input the port and communitry and enter, within 2 seconds. done.

I noticed you said SNMP version 1.0, are you using those RV series router or what model you are using?

sethu's picture

Hi Team,

 

Yes, observium needs dns name to resove the device, while snmp discovery it is checking the dns name not the ip address. We have to add the hostname / ip address in the /etc/hosts file to resolve the ip / name.

 

Regards,

Sethu. B

Abdul's picture

Hi,

Thanks a lot for your comment, the ip is already there and thats why it was able to resolve the hostname the issue here with the SNMP only.

Regards,

feron's picture

hi everyone,

Please how can I install observium on windows and where can I get the version for windows? Thanks

Jeremy Davis's picture

You've come to the right place! :)

We have a "virtual appliance"; basically a virtual machine which includes the required software pre-installed and ready to go. You can install the VM (from ISO, OVA or VMDK) by downloading it; or you can launch in the cloud from your browser.

If you intend to download and run locally, then you will also need some sort of virtual machine hosting software (such as Virtual Box, VMware, Hyper-V or similar) to run it within. Assuming you intend to run this all the time, make sure that you install to a machine that is always on (i.e. a workstation or a laptop are probably not good options, other than just for testing...).

Check out the Observium appliance page.

Add new comment