Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Getting Started Essentials


The following describes the typical high-level procedures for getting started with the Network Management module.

  1. Log into IP/MPLSView. When starting up IP/MPLSView, you will be prompted with the welcome screen. Select Manage & Monitor. If this window does not appear, you can also choose File > Open Live Network from the main menu bar.

  2. Set up Router Profiles. The next step is to set up router profiles which contain login and password information, allowing you to connect to the devices in your network. You can (a) build a router profile from scratch through the graphical interface, (b) import the information from a text file using the Import Wizard, or (c) populate a router profile automatically using the Autodiscovery or Host Discovery tasks in the Task Manager. These are described further in Setting Up Device Profiles Overview. Many users choose to perform an Autodiscovery task in the Task Manager to identify the routers that exist in a given network and to automatically populate a router profile, as described in Network Discovery Overview. The first step is to select one or more seed routers (for example, one per area), and specify them in a router profile. The Autodiscovery task will poll the seed routers’ specified router database (for example, OSPF, ISIS or MPLS database), constructing a list of IP addresses, or routers, that are then polled for their configuration files. Performing an autodiscovery will also automatically populate your router profile with the newly discovered devices. The collected data is automatically parsed by IP/MPLSView, allowing the network topology to be displayed in the Topology Map at this time.

  3. Start the Live Topology Collection. The Scheduling Live Network Collection task in the Task Manager, as described in Live Network Collection Overview is required if you wish to see near real-time updates of the network status on the Topology Map. Because router configuration files are modified over time, this task is usually scheduled periodically in order to synchronize with the real network. In addition to configuration data, the Live Network Collection also collects interface/tunnel data. Once this task is scheduled, live network data can also be viewed from the Web Interface, as described in the IP/MPLSView Web-Based Management and Monitoring Guide.

  4. Start the Traffic Collection. In order to see the utilization results reflected in near-real time on the topology map, in addition to performing the Scheduling Live Network Collection task, you can also perform a Traffic Collection to collect the traffic data on each tunnel/interface, as described in Performance Management: Traffic Collection Overview. This feature is accessed via Performance > Traffic Collection Manager, but requires that you start one or more data collectors first.

  5. The Task Manager (Task Manager Overview ) can also be used to run a one-time or periodic User CLI Collection task that collects the same network router data (such as configuration files, tunnel or interface data) or the output of other “show” commands, but saves it into any user-specified directory. This is described in Collecting Supplementary Device Data Overview.

  6. The Hardware Inventory can be used to keep track of shelf/card/port usage. For more details, refer to the Hardware Inventory Overview or the IP/MPLSView Java-based Graphical User Interface Reference “Hardware Model” chapter.

  7. You can switch to Offline mode in order to perform a variety of offline planning, analysis, design, and failure simulation. For more information, refer to the Performing Further Analysis Offline Overview and refer to the Router Feature Guide for IP/MPLSView for offline features.