INTERMAPPER NOT SHOWING INTERFACE NAME MAC OS
INTERMAPPER NOT SHOWING INTERFACE NAME WINDOWS

It is possible that flow records are arriving, but no template has yet been seen in this case, Intermapper Flows must ignore the records until it receives a template in order to avoid interpreting a record incorrectly. The collector parses the NetFlow v9 datagrams from a particular exporter based on its published template. This format can differ from exporter to exporter, and each exporter publishes a template record approximately every 10 minutes. The NetFlow v9 and IPFIX formats use a template-based system the flow export datagram format is described by a template. 'Template Not Found' (NetFlow v9 and IPFIX only)

If clocks are aligned, the cross-hatch area should occupy a thin strip at the right of the graph. In either case, try moving or extending your time selection back or forward in time until you see a graph showing sessions.Īdjusting one or both system clocks is the preferred method for fixing this problem otherwise, alerts and reports may be also misconfigured. If the cross-hatch area is not showing at all, the client clock is behind (in the past). If the cross-hatch pattern covers the entire graph, the client clock is ahead (in the future compared to the server clock). In either case, the result set might be empty. If Intermapper is running on a machine with a significantly different system clock time than the host running Intermapper Flows Server, a request for recent data can cause the server to try to fetch sessions that it considers to be in the future or far in the past. Significant system time skew between Client and Server If another process or collector is using the same port, change the Listen port in the Flows Settings window and configure the collector to use the same port. On Windows: # netstat -a -o -b will, if run with admin permissions, show which processes have bound to which ports.

INTERMAPPER NOT SHOWING INTERFACE NAME MAC OS

On UNIX hosts (including Mac OS X): # netstat -a -p.

The netstat tool can tell you which process id or executable has the required ports bound. If another flow collector is running on the same system as Intermapper Flows, it will not be able to collect any flow data because it will be unable to bind the required listen ports.

Intermapper Flows is unable to bind the required ports Make sure that traffic on UDP/2055 (NetFlow/IPFIX), UDP/9666 and UDP/9996 (cFlow/jFlow), UDP/6343 (sFlow), and any other ports on which you have configured flow collection can reach the Intermapper Flows Server. Take a look at your firewall configuration to see if you might have this problem.

INTERMAPPER NOT SHOWING INTERFACE NAME WINDOWS

On some versions of Windows, Windows Firewall blocks flow ports by default RedHat Enterprise Linux and CentOS also ship with a firewall configured by default. Most systems have host-based firewalls configured to block inbound traffic on certain ports.

The firewall may be somewhere on the network or on the Flows host itself. Host-based firewalls are often configured to block inbound traffic on certain ports. The firewall may be somewhere on the network or on the flows collector host itself. The most common cause of missing flow traffic is that a firewall is blocking the ports needed to receive flow updates.

Intermapper not showing interface name