Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Fault Management

Launch Event Browser

The Event Browser is used to view events and SNMP traps from devices in the Live network and can be launched from the web using Java Web Start. You may open either the Live or Historical view. For information on how to use the Event Browser, and the differences between the Live and Historical view, see Chapter 13, Fault Management: Events .

Figure 264: Web Event Browser

Web Event Browser

Event Summary Reports

This feature displays a summary of events over a specified period of time. Daily, weekly, and last 30 day summary views are available. Event summary reports by event type or node are also available.


How to Prepare the Data


To see the Event Summary Reports, make sure that the Event Server & SNMP trap server processes are running, by checking /u/wandl/bin/status_mplsview. To receive trap events from network devices, the network devices should be configured to send SNMP traps with the IP/MPLSView application server as one of the target addresses.


Event Dashboard


The Event Dashboard displays the counts for various event categories. Each event category has its own window which can be edited or repositioned in your web browser. Use the Select date range button to query on a specific date, week, or last 30 days.

Figure 265: Event Dashboard

Event Dashboard

By Severity


This report displays the total number of events organized by event severity to device. Use the Select date range button to query on a specific date, week, or last 30 days.

Figure 266: Event Summary by Severity

Event Summary by Severity

By Event Type


This report displays the total number of events organized by event type and severity (INFO, NORMAL, UP, WARNING, MINOR, MAJOR, CRITICAL, and DOWN). Use the Select date range button to query on a specific date, week, or last 30 days.

Figure 267: Event Summary by Event Type

Event Summary by Event Type

By Node


This report displays the total number of events organized by node. Use the Select date range button to query on a specific date, week, or last 30 days.

Figure 268: Event Summary by Node

Event Summary by Node

Event Options

Use the these options to configure your event settings.


Edit Threshold Alarms


Threshold alarms (threshold crossing alerts) can be used to monitor the network against any number of user defined SLAs or other production and performance requirements. To learn how to setup threshold alarms, see Chapter 14, Fault Management:Threshold Crossing Alerts.


Edit Event Severities


This feature allows you to edit the severities associated with each event in the Event Browser. For more information, refer to Edit Event Type Severities.

Link Availability Report

Use this report to view interface Up and Down time information. The Link Availability reports require the routers to be configured to send linkUp and linkDown traps to the application server for processing. The ISIS Link Availability Report requires the routers to be configured to send RPD_ISIS_ADJDOWN and RPD_ISIS_ADJUP for Juniper, and ciiAdjacencyChange for Cisco.

Figure 269: Link Availability Report Options

Link Availability Report Options

Select the desired date range, router, protocol, choose to exclude or include logical interfaces in the reports, then click Generate to build and timestamp the reports. Clicking on the reports will display the reports from the most recent generate build. Click on a specific Show Report to display the following reports:

  • Link Availability displays interfaceA and interfaceZ, Up and Down time information by all links.
  • Physical Link Availability displays interfaceA and interfaceZ, Up and Down time information by physical links.
  • Interface Availability displays interface Up and Down time information by interface name.
  • Unknown Interface Availability displays Unknown time information by interface name. Unknown time is calculated when a router sends two consecutive linkUp or linkDown traps. This may occur if traps are dropped by the router or if network collection is unstable. Example, routerA sends a linkUp trap at 10:00:00 and then sends another linkUp trap at 10:02:00, the Unknown time is calculated as 2 minutes.

Figure 270: Link Availability Report

Link Availability Report

Performance Management

The performance features in the IP/MPLSView Web interface enable you to view various detailed traffic data that the system collects.

To view live traffic data via the IP/MPLSView Web interface, observe the following guidelines:

  • Collect the network data by performing the Scheduling Live Network Collection task with at least the config and interface options selected.
  • Start traffic collection in the Traffic Collection Manager as described in Chapter 11, Performance Management: Traffic Collection .

    You can also adjust the collection time interval to multiples of 300 seconds (5 minutes) in the Traffic Collection Manager.

  • For Group traffic charts, define group names and members.

    For more information on how to create groups, see Group Popup Menus in Chapter 4, The Topology Window .

Live Traffic

Live traffic reports are organized by traffic type.


Network

  • Interface Total: Displays the total interface ingress and egress traffic collected for the entire day.
  • Tunnel Total: Displays the total tunnel traffic collected for the entire day.

Link


  • Link Summary: Displays link traffic between two routers.

Interface


  • Interface Router: Displays total interface ingress and egress traffic on a router at the last collection time interval. Clicking a specific router will display all interfaces on that router. Clicking a specific interface will display historical traffic for that interface.
  • Interface Individual: Displays single interface ingress and egress traffic on a router.
  • Interface Summary: Displays interface ingress and egress traffic on a router.
  • Interface Total Ingress: Displays aggregated interface ingress traffic. Requires running the Traffic Summary Report task in Task Manager.
  • Interface Total Egress: Displays aggregated interface egress traffic. Requires running the Traffic Summary Report task in Task Manager.

Tunnel


  • Tunnel Network Level: Displays tunnel traffic by tunnel name at the last collection time interval. Clicking a specific tunnel will display historical status states and traffic for that tunnel.
  • Tunnel Router: Displays tunnel ingress and egress traffic on a router at the last collection time interval. Clicking a specific router will display all tunnels on that router. Clicking a specific tunnel will display historical status states and traffic for that tunnel.
  • Tunnel Individual: Displays single tunnel traffic on a router.
  • Tunnel Summary: Displays tunnel traffic on a router.
  • Tunnel Total Ingress: Displays aggregated tunnel traffic. Requires running the Traffic Summary Report task in Task Manager.
  • Tunnel Traffic Matrix: Displays the total tunnel traffic originating and terminating at each router.

VPN


  • VPN Summary: Displays VPN ingress and egress traffic on a router.
  • VPN Total Ingress: Displays aggregated VPN ingress traffic. Requires running the Traffic Summary Report task in Task Manager.
  • VPN Total Egress: Displays aggregated VPN egress traffic. Requires running the Traffic Summary Report task in Task Manager.
  • Customer Service: Displays total traffic per Customer Service VPN.

Group


  • Live Chart: Displays interface traffic charts by Report Groups. The Report Group must defined in Admin > Report Groups.
  • Live Report: Displays interface traffic reports by Report Groups. The Report Group must defined in Admin > Report Groups.
  • Single Day: Displays total tunnel traffic between Groups for a single day. The Group is defined in the client.
  • Multiple Days: Displays total tunnel traffic between Groups for multiple days. The Group is defined in the client.
  • Tunnel Traffic Matrix: Displays the total tunnel traffic originating and terminating between Groups. The Group is defined in the client.
  • Status: Displays the data collector’s status, assigned traffic collection groups and routers. Click on the Group ID to display details of the routers and collected tables. The traffic collection group is defined in the client Traffic Collection Manager.

Aggregated Traffic

Aggregated traffic reports are organized by traffic type and aggregated either hourly or daily.


Link


  • Link: Displays link traffic between two routers.

Interface


  • Interface: Displays summary interface traffic at each router.
  • Interface CoS: Displays summary interface CoS traffic at each router.
  • Interface Multicast: Displays summary interface Multicast traffic at each router.
  • Packet Errors: This report provides the number of inbound and outbound packets that could not be transmitted because of errors.
  • Packet Discards: This report provides the number of inbound and outbound packets which were chosen to be discarded even though no errors had been detected. One possible reason for discarding such a packet could be to free up buffer space.

Tunnel


  • Tunnel: Displays summary tunnel traffic at each router.

VPN


  • VPN: This report provides the total in and out traffic per VPN.
  • VPN CoS: This report provides the total in and out CoS traffic per VPN.
  • VPN Multicast: This report provides the total in and out Multicast traffic per VPN.
  • Customer Service: This report provides the total in and out traffic per Customer Service VPN.
  • Customer Service CoS: This report provides the total in and out CoS traffic per Customer Service VPN.
  • Customer Service Multicast: This report provides the total in and out Multicast traffic per Customer Service VPN.

Group


  • Interface Group: This report provides the total in and out traffic for the interfaces in a group. These groups are defined in Admin > Report Groups.
  • Interface Group CoS: This report provides the total in and out CoS traffic for the interfaces in a group. These groups are defined in Admin > Report Groups.
  • Interface Group Multicast: This report provides the total in and out Multicast traffic for the interfaces in a group. These groups are defined in Admin > Report Groups.
  • AS: This report provides the total in and out traffic for the interfaces in an AS.

Traffic Collection Manager

The Traffic Collection Manager enables you to manage data collectors and configure the type of traffic data that IP/MPLSView collects from the devices in your network. By viewing the collected information in various ways in the Traffic Collection Manager, you can monitor your network interface and tunnel traffic.

You can access the Traffic Collection Manager from either the Web interface or Java client interface in IP/MPLSView. The Web version of the Task Manager provides essentially the same features as the Java client version, with only minor variations in the appearance of the GUI.

To access the Traffic Collection Manager from the IP/MPLSView Web interface, select Performance > Traffic Collection Manager from the window’s main menu. The Web version of the Traffic Collection Manager enables you to perform the following tasks:

  • Create, modify, and delete router groups from which data is collected.
  • Assign devices and data collectors to router groups.
  • Select the collection tables that you want to use for data collection.
  • Modify device profile properties for data collection.
  • Manage the collection status.
  • Test network connectivity to one or more devices in a router group.

Note: To configure collection settings for the Master Collection Panel and and the Collection Manager, you must access and use Traffic Collection Manager from the Java client interface. All other tasks are supported in both the Web version and Java version of the Traffic Collection Manager.

In the sample Traffic Collection Manager window in Figure 271, the left pane of the Collection Elements tab shows a router group named Small to which data collector 172.25.152.29_wandl_1 is assigned. The right pane displays the properties for the device named 11_MANCHESTER - 172.16.0.11, which belongs to the Small router group.

Figure 271: Traffic Collection Manager and Router Groups

Traffic Collection Manager
and Router Groups

Figure 272 displays the collection status in the Traffic Collection Manager. After traffic collection has started, you can select the Collection Status tab to view and monitor collection events. The display includes any errors, warnings, and updates that may occur.

Figure 272: Traffic Collection Manager Collection Status

Traffic Collection Manager
Collection Status

Figure 273 displays the profile connectivity test for the seven devices that belong to the MX router group. The connectivity test runs Ping, SNMP, and CLI tests on the devices to verify reachability, SNMP configuration, and CLI login access, respectively. You can run the connectivity test only for devices that belong to a complete router group to which a data collector is assigned.

Figure 273: Traffic Collection Manager Profile Connectivity Test

Traffic Collection
Manager Profile Connectivity Test

Device Performance

This enables web users to view device reports on system uptime, CPU usage, CPU temperature, and memory usage. To prepare this data, schedule the Device SNMP Collection task, as described in Device SNMP Collection.

To display statistics information in the Device Performance report about interface modules (also known as line cards) installed in Juniper Networks devices in your network, select the Collect Line Card Information (Juniper Only) option when you configure the parameters for the Device SNMP Collection task. For example, the Device Performance Report shown in Figure 274 includes various Gigabit Ethernet interface modules installed in a Juniper Networks MX80 3D Universal Edge Router.

Figure 274: Performance Report Displaying Juniper Networks Interface Modules

Performance Report Displaying
Juniper Networks Interface Modules

Figure 275: System Uptime Report

System Uptime Report

Figure 276: CPU Temperature Report

CPU Temperature Report

Figure 277: CPU Usage Report

CPU Usage Report

Figure 278: Memory Usage Report

Memory Usage Report

Network Performance

This enables web users to view network reports on ping, lsp ping, SLA, and link latency. To prepare this data, schedule the Device Ping Collection, LSP Ping Collection, Device SLA Collection, and Link Latency Collection tasks respectively.


Figure 279: Ping Report

Ping Report

Figure 280: LSP Ping Report

LSP Ping Report

Figure 281: SLA Report

SLA Report

Figure 282: Link Latency Report

Link Latency Report

Diagnostics

This enables Web users to run network diagnostic tools such as ping, CLI commands, test connectivity, and traceroute. Adobe Flash needs to be installed to run certain tools.


Diagnostics Manager


The Web version of Diagnostics Manager provides the capability to perform basic and advanced ping commands as well as checking router connectivity.

Figure 283: Diagnostics Manager (Web Version)

Diagnostics Manager (Web Version)

The Web version of Run CLI provides the capability to run multiple CLI commands on a selected device.

Figure 284: Run CLI (Web Version)

Run CLI (Web Version)

Run CLI and Diagnostic

To use the Run CLI and Diagnostic tool in the IP/MPLSView Web interface:

  1. Select Performance > Diagnostics > Run CLI and Diagnostic.
  2. Select the name of the device to test from the Select a device drop-down menu.
  3. From the CLI Commands pane, expand the command category for the command you want to run.
  4. Select the checkbox for the specific CLI command you want to run, and click Collect.
  5. Specify the appropriate parameters for your command, and click Run CLI.

    The Output pane displays the command output for the selected CLI command, as shown in Figure 285.

    Figure 285: Sample Run CLI and Diagnostic Output

    Sample Run CLI and Diagnostic
Output

You can also execute CLI commands and open the Diagnostics Manager from the Actions tab of the Node Info page.

Take any of the following actions:

  • To run a single CLI command, select the command from the Execute CLI Command drop-down menu.
  • To execute multiple CLI commands in a batch, select Execute CLI Commands.
  • To access the Diagnostics Manager, select Open Diagnostic Manager.

For more detailed information about running CLI commands and accessing the Diagnostics Manager from the Node Info page, see Nodes.


Ping Multiple Routers


Use the this function to check the connectivity between multiple routers in the network, measure latency and packet loss. A ping table matrix will be generated, displaying the ping times between all possible pairs of the selected routers. “Ping time” refers to the time it takes for a small packet of data to travel from one device to another and back.

Simply select multiple routers from the list. Then, press Submit and wait until all the results have populated in the table. This may take a few minutes.

Figure 286: Ping Multiple Routers Results

Ping Multiple Routers Results
Ping Multiple Routers Results

Note: The designation “n/a” (not available) may signify that the ping operation timed out. If there are VPNs in your network, it may signify that the two devices are not in the same VPN.

The default color codings and ping thresholds are as follows. These values can be adjusted by the administrator.

Table 45: Default Color Codings

Color

Meaning

Green

Acceptable. The ping operation took less than 150ms.

Yellow

Problematic. The ping operation took between 150ms and 400 ms.

Red

Unacceptable. The ping operation timed out or took longer than 400ms. There may not be any connectivity between the two devices.

Note: Each outcome displayed in the table is actually the result of multiple pings. The Ping Count, or number of pings actually issued between devices, depends upon the diagnostics settings configured by the Web administrator in Admin > Diagnostics Settings. Ping parameter settings are described in Diagnostics Configuration Settings.

In the ping results table, the default view shows the average (avg) ping results, in milliseconds. You can also choose to display the min, max, or loss % of the pings by clicking on the respective word below the table

Table 46: Ping Results

Feature

Description

min/max/avg

Displays the smallest, longest, or average ping time experienced, respectively. (Multiple pings are actually issued.)

loss %

Displays the percentage of pings that are lost or dropped between each device pair.


Ping Router from Router


This function is similar to the Ping Multiple Routers diagnostic described in Ping Multiple Routers. It allows you to check the connectivity between one particular router and several other routers in the network. Select one router from the drop-down box. Then in the second router list, select one or more routers, and press Submit.

Figure 287: Ping Router From Router

Ping Router From Router

Check Router Connectivity


This function allows you to check the connectivity status between the IP/MPLSView server and a particular device in the network. Select the router from the drop-down box, and press Submit. The program will ping the device and simply report whether it is “UP” or “DOWN”.


Traceroute


This function allows you to trace the route that an IP packet follows from one device to another in the Live network. Simply select the source and destination routers from the two selection boxes, and press Submit.

Figure 288: Trace Route Results

Trace Route Results
Trace Route Results

If the trace route times out, the message “No route to host.” will be displayed.

Note: Trace route parameter settings can be changed in Admin > Diagnostic Settings. These parameters are described in Diagnostics Configuration Settings.

Miscellaneous Reports and Charts

This section contains miscellaneous and vendor specific reports and charts related to performance and traffic data.

  • Network Performance Data Report from Task Manager: To view this report, see Network Performance Data Report and further details are described later in this chapter.
  • Aggregated Traffic Reports: To view this report, users should run the Aggregated Traffic Report task from the Task Manager. The resulting report will be saved to /u/wandl/data/task_reportsummary/ and can be viewed from this web menu. You should wait at least one day from the beginning of traffic collection. There is a cron job that runs once daily to perform the aggregation.
  • LDP Traffic Summary Report: To view this report, users should run the LDP Traffic Collection task (for Juniper only) from the Task Manager, and specify the same LDP Traffic Directory here that was used when scheduling the task.
  • LSP Tunnel Traffic Summary Report: To view this report, users should run the LSP Tunnel Traffic Collection task (for Juniper only) from the Task Manager, and specify the same LSP Traffic Directory here that was used when scheduling the task.
  • User Defined Group Traffic Summary Report (Hourly Aggregation): Given the router groups defined through the IP/MPLSView client, this report provides total in and out traffic for the interfaces in a group aggregated by hourly intervals. Click Show to display the Group hierarchy. Click Report to display the report. Only the web Admin can add/remove reports. The default Topology Group is from the file /u/wandl/data/.network/group.x
  • Group / Device / Interface Traffic Summary Reports (Live Traffic): To view this report, users should create Groups from the IP/MPLSView client. This report provides traffic summary report organized by the groupings.

Network Performance Data Chart Report


How to Prepare the Data


A report group is a group containing the router interfaces that will be reported on in the resulting traffic report. From the web, create “report groups” from Admin > Report Groups. Select the created report group to add the desired router interface(s) one by one.

After creating the report group, schedule the Network Performance Data Report task as described in Network Performance Data Report. On the Report Parameters tab, include minimally the format “Data Chart” and a report title. On the Report Attributes tab, specify the report group defined from the web, and select the desired attributes to report on, for example, the Egress utilization. If you have not yet collected one days’ worth of traffic, you will not see data from a query of the last day, for example, ‘Query data over the last 1 Day’. Instead, you can query over the last few hours, for example, ‘Query data over the last 5 Hours’. Alternatively, you can specify a specific date/time range (‘Specify the report query date range’).


Viewing the Reports


Once the report is created, select the title of the report and then select the date/time that it was generated. Reports are provided for CPU, Memory, Ingress and Egress Traffic and Error Count. After selecting the report name, click on the link corresponding to the day that you would like to view.

  • Network_Data_Report: This report will provide CPU and Memory information, one chart per device such as the following.
  • Device: This report will provide CPU and Memory information, one chart per device such as the following.

Network Performance PDF Chart Report


This is similar to the Network Performance Data Chart Report above, except that the chart is provided in PDF format. The difference during setup is that the format “PDF Chart” should be selected as the output from the Report Parameters tab of the Network Performance Data Report task.

Archived Reports

You can use the Archived Reports feature from the IP/MPLSView Web interface to display preprocessed traffic reports that you can view on a daily, weekly, monthly, or yearly basis. Because the reports are generated from preprocessed aggregated traffic data stored in the database on a daily, weekly, monthly, or yearly basis, you can perform report queries more quickly to retrieve the data.

The following archived reports are available:

  • Traffic reports—Archived Interface Traffic, Archived Tunnel Traffic
  • Device performance reports—Archived System Uptime, Archived CPU Temperature, Archived CPU Usage, Archived Memory Usage
  • Network performance reports—Archived Ping, Archived Advanced Ping, Archived LSP Ping, Archived SLA, Archived Link Latency

The daily and weekly reports use hourly aggregated data. The monthly and yearly reports use daily aggregated data. You can specify display options for the average, maximum (max) , 80th, 90th, 95th, and 99th percentiles. IP/MPLSView prepares the data every day at 11:30 AM by running the /u/wandl/bin/genAggTrafDB.sh script.

To generate and display archived reports from the Web interface:

  1. (Optional) Configure the IP/MPLSView server to set the maximum number of days to store performance management data.

    By default, you can store data collected from live traffic, aggregated traffic, and archived traffic for a maximum of 35 days. In most cases, using the default value should be adequate for your data storage needs, However, you can increase or decrease this value according to the available storage space in your network and how long you need to retain the historical data.

    If necessary, you can set a nondefault value for the maximum data storage capacity in either of the following ways:

    • During the IP/MPLSView installation, change the default value (35) for Maximum Traffic Capacity in Days in the installation script.
      Server Configuration Settings:
      (A) Overall Settings
      (B) IP Address
      (C) Memory Settings
      (D) Port Settings (Server to Client)
      (E) Port Settings (Advanced)
      (F) Online Performance Management Settings
      (G) Online Fault Management Settings
      (H) Advanced Configuration
      
      Please select a number to modify.
      [<CR>=accept, q=quit]:F
      
      (F) Online Performance Management Settings
      Aggregation Settings:
         1.) Maximum Traffic Capacity in Days......:35
    • After the IP/MPLSView installation, change the default value by running the /u/wandl/bin/changeconfig.sh script.
  2. Collect the data to be generated for the archived reports by running the appropriate collection task from Task Manager.

    Table 47 lists the collection tasks you need to run to provide data for the associated archived reports. For example, to generate data for the Archived Ping report, you must first schedule the Device Ping Collection task from the Task Manager to run on a recurring basis.

    Table 47: IP/MPLSView Collection Tasks and Associated Archived Reports

    Collection Task

    Associated Archived Reports

    Traffic Collection

    Archived Interface Traffic, Archived Tunnel Traffic

    Device SNMP Collection

    Archived System Uptime, Archived CPU Temperature, Archived CPU Usage, Archived Memory Usage

    Device Ping Collection

    Archived Ping

    Advanced Ping Collection

    Archived Advanced Ping

    LSP Ping Collection

    Archived LSP Ping

    SLA Collection

    Archived SLA

    Link Latency Collection

    Archived Link Latency

  3. Select Performance > Archived Reports from the main menu to access the Archived Reports GUI.

Admin

The Admin menu contains administrative settings for the web, web applications, web user accounts, and monitoring activities on the server. Web settings include session timeout, message of the day, and web policies. Web applications include the diagnostic tools, ping parameters, and trace route parameters. Web user accounts includes user access, groups, and password reset. Server monitoring includes viewing logs, login history, memory, CPU, and IP/MPLSView system processes.

When you select the Admin menu, the Administration window is displayed. Among the suboptions under Application, you can remove stale interfaces, stale tunnels, and stale routers from your topology. For example, Figure 289 illustrates how to use the Adminstration window to remove a stale router.

Figure 289: Administration Window for Removing Stale Routers

Administration Window
for Removing Stale Routers

You can also use the Administration window to duplicate or rename an existing report group.

To duplicate or rename an existing report group:

  1. In the left pane of the Administration window, select Application > Report Groups.
  2. In the Report Groups pane, select the checkbox preceding the group name that you want to duplicate or rename.
  3. Take one of the following actions:

    • To create a duplicate report group, click Duplicate Group and complete the fields in the Duplicate Group dialog box, as shown in Figure 290.

      Figure 290: Administration Window for Creating a Duplicate Report Group

      Administration Window
for Creating a Duplicate Report Group
    • To rename a duplicate report group, click Rename Group and complete the fields in the Rename Group dialog box. (The Duplicate Group dialog box and the Rename Group dialog box have identical fields.)

Modified: 2015-12-29