I don't let SNMP through my firewall. Period. When I have need monitor in another location that I don't have a private line to, I'll put another monitor in there and have it communicate back here over VPN.
Kristopher Dick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mauibay Sent: Thursday, 29 March 2007 10:58 To: [email protected] Subject: [zenoss-users] Re: snmp on a non-standard port? After more testing, I find that if I add a device listening on the default snmp port (161) and then change the port on the device and in zProperties it works after doing a "Collect Configuration." So, it seems that Zenoss _will_ talk to devices on alternate snmp ports, if they already exist. If I try to add a device using any snmp port other than 161, it fails with the "No snmp found on IP" error. It's quite cumbersome to change the snmp port for each device just to add it for monitoring by Zenoss, then change it back. And seriously, is this so unusual? Nobody else runs into this issue? Everybody is really leaving their snmp listeners on the standard port for every script kiddie's bot network to scan? Nobody is using port forwarding to query multiple devices behind a firewall? ------------------------ unset -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=4960#4960 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
