NFS configuration for remote servers

If you have deployed Packet Sensor, Flow Sensor or Wanguard Filter on a different server than the Console, you must configure NFS (Network File System) to export the Flow Collector and Packet Trace data to the Console server. Without it, the user interface cannot access the packet traces and flows saved on remote servers.

Three things that commonly trip people up:

• TCP and UDP ports 2049 (NFS) and 111 (RPC) must be open in the remote server’s firewall.
• Configure the remote server with the same time zone as the Console server.
• If you plan to remove an NFS-linked directory from the Console server, unmount it first with umount -l -f /opt/andrisoft/...

To troubleshoot NFS-related issues, use the following commands:

• showmount -e — shows the shares available on the local machine;
• showmount -e [server IP or hostname] — lists the shares available on a remote server;
• showmount -d — lists all the subdirectories;
• exportfs -v — displays the shares and their options on a server;
• exportfs -a — exports all shares listed in /etc/exports, or the given name;
• exportfs -u — unexports all shares listed in /etc/exports, or the given name;
• exportfs -r — refreshes the server’s list after modifying /etc/exports.