--
You received this message because you are subscribed to a topic in the Google Groups "sFlow-RT" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sflow-rt/QuxzzYXKUxk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sflow-rt+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sflow-rt/dc34e5e4-5a6b-4e25-9237-01dea968c722n%40googlegroups.com.
Looking at the original sFlowTrend screenshot, the agent in question has an sFlow agent address of 10.192.101.10 and you have configured an SNMP IP address of 10.192.1.101.The details for your device show 10.192.1.115 and am sFlow datagram source address of 10.192.72.156. So the addresses that you are showing for the device do not match those shown in sFlowTrend.Is this the correct device?The sFlow datagram source address for the device is not necessarily the same as the sFlow agent address. The sFlow agent address is a field inside the sFlow datagram and must uniquely identify the switch. If this address is not reachable from sFlowTrend, you can configure sFlowTrend, to use an IP address that is reachable and responds to SNMP (SNMP IP address). See https://inmon.com/products/sFlowTrend/help/html/configuration.agents.htmlIn addition, The screenshot for sFlowTrend reports an SNMP error of “Timed out”. The troubleshooting in the help https://inmon.com/products/sFlowTrend/help/html/troubleshooting.html#troubleshooting.troubleshooting.no-snmp indicates that this could be because the SNMP settings are incorrect or there are firewalls in the network or on the host blocking SNMP. Are the SNMP v3 settings you have configured correct and is the host you are running sFlowTrend on blocking any traffic?
On 22 Jan 2021, at 07:08, Vlad Kratsberg <vkrat...@gmail.com> wrote:
Yes, I specifically configured sFlow Agent on network device with a reachable ip.
You received this message because you are subscribed to the Google Groups "sFlow-RT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sflow-rt+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sflow-rt/CAA9sD4uE8ytF47npgjkDx4QNSW7%2BTEU%3DBGBi9cbWj4SpBDOYjw%40mail.gmail.com.
On Jan 22, 2021, at 9:09 AM, Vlad Kratsberg <vkrat...@gmail.com> wrote:
Hello Sonia,10.192.101.10/10.192.1.101 is a different device. I understand what you are saying and wouldn't even reach out if I saw get-request coming from sFlow-RT or sFlowTrend. I am doing a port mirror and tcpdump matching the source-ip of the collectors, however I don't see any snmp packet sent from either sFlow-RT nor sFlowTrend. Below are new sFlowTrend screenshots.
<Screen Shot 2021-01-22 at 8.56.49 AM.png>
It sounds as if you are looking at the device end to see if any SNMP from sFlowTrend is received. Have you checked on the sFlowTrend system that SNMP is sent (using tcpdump or Wireshark for example)?The SNMP error “Timed out” shown in sFlowTrend is normally a result of incorrect SNMP settings or a host (or network firewall). Since you are not seeing anything on the device end, have you also checked to see whether there is a route from the sFlowTrend system to the device for SNMP?
On 22 Jan 2021, at 07:08, Vlad Kratsberg <vkrat...@gmail.com> wrote:
Yes, I specifically configured sFlow Agent on network device with a reachable ip.
You received this message because you are subscribed to the Google Groups "sFlow-RT" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sflow-rt+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sflow-rt/CAA9sD4uE8ytF47npgjkDx4QNSW7%2BTEU%3DBGBi9cbWj4SpBDOYjw%40mail.gmail.com.
On 22 Jan 2021, at 14:27, Vlad Kratsberg <vkrat...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/sflow-rt/95d4c44e-c826-4e50-9ef8-f9d3a3b7b3can%40googlegroups.com.