Last but not least, to further help in any resolution, here is a tcp dump of udp port 161 from the router when I try to model the router through the command line showing that it is receiving packets from zenoss....
/var> tcpdump -s0 -v udp port 161 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 18:16:45.017331 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) monitor.domain.lan.40434 > 10.90.1.252.snmp: UDP, length 36 18:16:45.019733 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) 10.90.1.252.snmp > monitor.domain.lan.40434: UDP, length 36 18:16:48.017404 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) monitor.domain.lan.40434 > 10.90.1.252.snmp: UDP, length 36 18:16:48.019653 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) 10.90.1.252.snmp > monitor.domain.lan.40434: UDP, length 36 18:16:51.017475 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) monitor.domain.lan.40434 > 10.90.1.252.snmp: UDP, length 36 18:16:51.019697 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) 10.90.1.252.snmp > monitor.domain.lan.40434: UDP, length 36 18:16:54.017545 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) monitor.domain.lan.40434 > 10.90.1.252.snmp: UDP, length 36 18:16:54.019734 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 64) 10.90.1.252.snmp > monitor.domain.lan.40434: UDP, length 36 8 packets captured 23 packets received by filter 0 packets dropped by kernel /var> -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25357#25357 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
