Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Remote Collection Server Overview

    The remote collection server is a distributed CLI/SNMP poller that can be used for VLAN autodiscovery, CLI collection, and device and network performance data collection. When a task is run from the Task Manager on the central parsing server, the task can be dispatched to the remote collection server. The final results are transferred back to the central application server.

    Note: This feature requires a license. Contact Juniper Support or your sales representative for more information.

    The remote collection server can be used to reach the network you are monitoring with IP/MPLSView when it cannot be accessed directly by the application server. This situation might arise when the application server on your internal network is separated by a firewall from the network being monitored. Figure 1 illustrates this scenario.

    Figure 1: Sample Environment Using a Remote Collection Server

    Sample
Environment Using a Remote Collection Server

    Note: There are certain discovery tasks that cannot be run on the remote collection server. Therefore, one router (shown in Figure 1 as the seed router) on the network to be monitored, must be reachable from the application server over the following ports: TCP port 22 (ssh), UDP port 161 (SNMP Get), UDP port 162 (SNMP Trap), and ICMP type 0 and 8 (ping).

    Note: The remote collection server is not the same as the agent configured in the device profile window. The Agent(s) field in the device profile is used to identify an intermediate host that the application server can log in to, and from there log in to the network device to perform CLI operations.

    Modified: 2016-11-08