Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    Chaining VLAN Discovery with Network Config Data Collection

    Once the router profile is created from the autodiscovery or pingsweep step, the login profiles can be used to collect CLI information to build up the network model. If you will be chaining the Network Config Data Collection immediately after the VLAN Discovery task, continue with the following steps. Alternatively, if you wish to manually validate the router profile and then schedule the CLI collection afterwards, skip to Validating the Router Profile and Scheduling CLI Collection on page 101.

    1. From the Task Manager, select New Task, and then select Network Config Data Collection. Enter in a Task Name and then click Next.

      Figure 1: Network Config Data Collection

      Network Config Data Collection
    2. For the Collection Directory, select Browse to select the same output directory used for the VLAN Discovery, for example, /u/wandl/data/collection/vlan1.
    3. For Select the device(s) to be collected, select the checkbox “Use Profile Directly”. Then select the profiles to be collected. Select the router profile output file created from the VLAN Discovery task. Additionally, select the profile containing the login information for any jumpserver that is required to connect to these devices. (This assumes that the agent field was populated in the profile range before running the VLAN Discovery task as described in Setting up the Router Profile.)
    4. Under Data Consolidation, select the VLAN Discovery directory based on the VLAN Discovery output directory, for example, /u/wandl/data/collection/vlan1/bridge

      Figure 2: Network Config Data Collection, Bottom Half

      Network Config Data Collection, Bottom Half
    5. For Data to Be Collected or Processed, select the desired information, for example, Configuration, Interface, Tunnel Path, Transit Tunnel, and Equipment CLI.
    6. For Alternate Login, click the Edit icon to enter in alternate login/password information in case the default one carried over from the profile range specification fails. After adding in the alternate login/passwords, click Save to specify the file in which to save this information. Then select Close.

      Figure 3: Alternate Login Specification

      Alternate Login Specification
    7. Under Collector Settings, change the No. of processes in case you want to collect more devices simultaneously. The No. of retry can also be increased in case you want to retry a device if the device is unreachable at the time of polling.
    8. Click Next.
    9. In the scheduling screen, you can select the Polling Server (Remote Collection Server). This should be the same one used for the VLAN Discovery task.
    10. Next, for the Schedule Type, choose Immediately After and select the preceding task.

      Figure 4: Scheduling Immediately After

      Scheduling Immediately After

    Modified: 2016-11-08