Troubleshooting

Support

Technical support is available, provided maintenance is active.

Frequently Asked Questions

Q) I’ve configured my router to send flows to the replicator, but the replicator says it hasn’t heard traffic from this device.

A) There may be a firewall or other network intrusion system preventing traffic from reaching the Flow Replicator. You can verify if the Flow Replicator is seeing traffic from that device by using the snoop <ip_of_network_device> command.

Q) Is there a way to get a list of exporters that are not in any profiles but still sending packets to the replicator?

A) Use the exporter noprofiles command:

REPLICATOR> exporters noprofile

+--------------------------------------------------------------------------+
| 10.1.73.1         Wed Jul 16 11:06:37 2014         1 packet(s)
| 10.1.29.60        Wed Jul 16 11:06:38 2014         2 packet(s)
| 10.202.0.103      Wed Jul 16 11:06:39 2014         5 packet(s)
| 10.200.10.1       Wed Jul 16 11:06:39 2014        32 packet(s)
| 172.20.124.41     Wed Jul 16 11:06:33 2014         1 packet(s)
+--------------------------------------------------------------------------+
Done in 0.035998 secs

Q) I want to send syslog notifications and IPFIX metrics generated by the replicator to multiple collectors but the setting seems to only support 1 collector. How do I configure it for multiple collectors?

A) This is possible by configuring the setting to send the notifications and/or IPFIX metrics back to the Flow Replicator. Then, create a profile to send the data on to one or more collectors. However, since one setting is for syslogs and the other setting is for IPFIX, two different profiles are required. Assuming the Flow Replicator’s IP is 10.1.4.66, below is an example of what both profiles would look like.

+--------------------------------+-----------------------------------------+
| replicator_notifications       | IN PORT 514 -> OUT PORT 514
+--------------------------------+-----------------------------------------+

 Policies                   Exporters     ->    Collectors
 (include) 0.0.0.0/0        10.1.4.66           10.1.10.1
                                                10.1.4.19
                                                10.1.4.20
                                                10.1.4.222
                                                10.1.4.93
                                                10.1.4.94

+--------------------------------+-----------------------------------------+

+--------------------------------+-----------------------------------------+
| replicator_metrics             | IN PORT 2003 -> OUT PORT 2056
+--------------------------------+-----------------------------------------+

 Policies                   Exporters     ->    Collectors
 (include) 0.0.0.0/0        10.1.4.66           10.1.10.1
                                                10.1.4.19
                                                10.1.4.20
                                                10.1.4.222
                                                10.1.4.93
                                                10.1.4.94

+--------------------------------+-----------------------------------------+

Q) Can a profile have the same listening and sending port?

A) Yes. However, the Flow Replicator will perform additional checking when adding collectors and exporters to verify a loop isn’t introduced.

Q) What does it mean when I’m trying to add an exporter or collector and the Flow Replicator won’t add it because it would create a loop?

A) A loop is when flows from a device are exported from and sent back to itself repeatedly. This requires that a device is both an exporter and collector. If the profile is configured with the same listening and sending ports, the packets will be sent back and forth continuously.

Q) How do I change the root password on the Flow Replicator?

A) Log into the Flow Replicator as the root user and issue the passwd command.

Q) How do I change the hostname and IP Address of the Flow Replicator?

A) There are two options to change the hostname and IP Address. First, log in as root and run the /home/replicator/conf/sethostname.sh command. Or, login as replicator and issue the system change command.