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

    Detailed Procedures


    Use autodiscovery to automatically discover your network from an existing router profile, which contains the “seed” routers. A new profile called “’ will be created containing the seed routers and all routers discovered from the seed routers, where “xxx” is the protocol used for the autodiscovery (for example, OSPF, ISIS, or MPLS). Note that from any given router, you will only be able to discover those routers in the same area (OSPF, ISIS, etc.) that have the same login name and password.

    Once the autodiscovery completes, you may want to make manual edits to the router profile to remove unwanted nodes or add some nodes that are not discovered.

    1. If you have not already done so, create a router profile that contains the seed router(s) from which you are going to discover your network, as explained in Setting Up Device Profiles Overview. For example, if you are going to discover the network using OSPF, make sure that your seed routers contain at least one router from each of the OSPF areas to be discovered.
    2. Select Admin > Task Manager from the pull-down menu.
    3. In the Task Manager, create an Autodiscovery task. To do so, click the New Task button. The New Task Wizard window will appear, as shown in Figure 56. Select the Autodiscovery task, specify an optional Task Name or Comment, and click Next.

      Figure 1: Create New Autodiscovery Task

      Create New Autodiscovery Task
    4. In the next screen, select from the Router Profiles drop-down menu the router profile that contains the router(s) from which you are going to discover your network. For each router in the selected profile, the left-hand side table will be populated with the specified IP address and router name for that particular router. (Alternatively, select the “Use Master Profile” checkbox and then select the device(s) from which to discover your network. The Master Profile contains the last used credentials for previously collected devices. This checkbox appears if the Master Profile has been generated from a previous task.)
    5. If you wish to use all the routers in the selected router profile, click on the “Add All >>” button.

      Otherwise, highlight just those routers you wish to use from the table on the left. You can perform multiple selection by using the <SHIFT> and <CTRL> keys. Or, you can select a contiguous set of rows by clicking on one row, and then, while still holding the mouse pressed down, drag it over the desired rows. Click the “Add ->” button to move your selection to the table on the right. You can repeat this process to add other noncontiguous routers from the selected router profile. Or you can select other router profile(s) and add routers from those profile(s) to your current list of routers to be collected.

    6. In the Data Collector Instruction section of the window, specify which protocol to use to access the routers. By default, it will be set to “Use Router Profile Setting” to use the protocol specified in the Access Method field of the router profile. You can also override this by specifying “Telnet Only”, “SSH Only”, “Telnet - or SSH as alternate”, or “SSH - or Telnet as alternate”.
    7. In the Autodiscovery Protocol section of the window, indicate the protocol to use for the collection-- OSPF, ISIS, or MPLS Topology.
    8. At the top of the Task Parameters screen, specify a Collection Directory, where the collection output will be saved. This should be one alphanumeric word. If the directory does not already exist, it is automatically created for you. If it does exist, any pre-existing configuration information will be overwritten by the new collection process.

      Figure 2: Select the Routers for Collection

      Select the Routers for Collection
    9. Click “Next” to proceed to the Schedule Task pane. In this screen, specify the Schedule Type, such as “Immediately”, or at a particular interval.
    10. Click “Finish” to submit the autodiscovery task. You should receive a confirmation message indicating that the task was successfully submitted. Click on OK, and the Task Manager window will appear, displaying the progress of the autodiscovery collection. If you have scheduled the autodiscovery to run at a later time, this will also be visible.

      A new profile called “Autodiscovery.ospf’ will also be created containing all the seed routers and all routers discovered from the seed routers. Additionally, there will be a profile for each seed router showing the discovered routers from that seed router. The router profile will be named according to the router used to discover the network and the method to discover the network. For example, you may get “NWK.ospf” if you were discovering the network from router NWK based on OSPF information. If that filename already exists, it will be overwritten. You will then be asked whether or not you want to reload the file. Click “Yes” to any such windows. Otherwise you will have to close the task manager and reopen it to see the updated router profile(s).

      Figure 3: Autodiscovery Task Results

      Autodiscovery Task Results

      If the task is successful, you should see a list of the seed routers along with the autodiscovery method (OSPF in this example). Following this are rows for the routers discovered (including the one from which they were discovered). The job type is “Config” to indicate that configuration files were collected.

      Note: In the event that the task is completed unsuccessfully, you may get error messages, such as “Detailed Results Not Available.” Lines marked in red also indicate errors. See Reference Overview for an explanation of status messages. See Task Encounters Some Errors for how to resume after you have resolved those issues.

    11. When your task has completed successfully, you can verify this by clicking on the Router Profiles button. As explained earlier, the profiles of the discovered routers will be populated in a router profile, which will be named according to the router used to discover the network and the method to discover the network as shown in Figure 58. For example, you will see a “LDN.ospf” router profile if you were discovering the network from seed router LDN based on OSPF information. This profile will contain just those devices discovered through LDN. For an autodiscovery task, an autoDiscovery.OSPF router profile will also be created containing all discovered routers.
    12. In Figure 4, six additional router profiles were created: one for each of the seed routers, and one for the entire autodiscovery task. Note that aside from LDN.ospf, all the other seed router profiles use the IP address in the profile name. This occurs if a Router Name is not specified in the original profile used to perform the autodiscovery.

      Figure 4: Newly Populated Router Profiles from the Autodiscovery

      Newly Populated Router Profiles
from the Autodiscovery
    13. You can now edit the newly created router profiles. For example, you can delete any undesired router profiles by highlighting them in the list on the left pane and selecting Delete Profile(s) from the right-click popup menu. Be sure to click the Save button to save any changes.

    Some of the IP addresses discovered during the autodiscovery may not be usable by the IP/MPLSView server for the configuration file collection. To clean the router profile to include only the IP addresses accessible to the IP/MPLSView server, one option is to run the Host Discovery task on the newly created autoDiscovery.xxxx profile as described in Cleaning Up an Existing Router Profile.

    Task Encounters Some Errors

    Figure 3 shows some “login failed” errors. For those routers, double check the router login and password information, and make any necessary changes to your router profile. Remember to click the Save button to save changes to your router profile.

    Once you have resolved the issues, you can retry the autodiscovery. You can create a new autodiscovery task, or reuse the original one. In this example, we will do the latter. In the Task Manager window, make sure the original Autodiscovery task is selected in the tasks table, and click Modify Task. Alternatively, right-click on the task in the table, and select Modify from the popup menu, as shown in Figure 5.

    Figure 5: Modifying an Existing Task

    Modifying an Existing Task

    The Autodiscovery task will appear. In the router selection section, you can click the Failed Only button to perform another autodiscovery using only those seed routers which failed the first time. Please read the caveat below for information about using this feature. Also, be sure to mark the Incremental Updating checkbox in the Data Collector Instruction section of the Task parameters pane. Then, click Next and schedule the task to run.

    Note: Incremental discovery is covered in greater detail in Incremental Discovery and Collection on page 88.

    Caveat about using “Failed Only”: A collection may fail for any of several reasons. One reason may be that a device was temporarily offline or that the IP/MPLSView server could not reach it due to underlying network issues. If the collection failed for this reason, then you simply need to click the Failed Only button, and resubmit the task.

    A device collection may also fail because login, password, or similar information were incorrectly specified in the router profile. In this case, you must follow some additional steps to ensure your router profile changes are reflected in the modified task. Most Task Manager tasks use temporary profiles comprised of router entries that can be taken from any number of saved profiles. Therefore, in the current release of IP/MPLSView, any changes such as password or login to a router profile will not be reflected automatically in the failed set that is retrieved from the Failed Only button. In this case, you must manually reselect the failed routers into the Routers to be collected list. That is, you must reselect the newly modified profile(s) from the Profiles dropdown box, select the failed routers from the list on the left, and use the Add button to replace the failed routers that are listed in the Routers to be collected list on the right, as shown in the following figure.

    Figure 6: Performing Autodiscovery With Only the Previously Failed Routers

    Performing Autodiscovery With Only the Previously Failed

    Modified: 2016-11-08