IManager U2000 IP Network Monitoring and Maintenance Solution
IManager U2000 IP Network Monitoring and Maintenance Solution
Performance management: Plans, monitors, and measures network efficiencies, such as the throughput, usage, and
error rate, to ensure excellent network performance at low costs and meet future requirements of network
performance.
Resource
A resource is a telecommunications resource model, for example, a device, card, port, or link in the performance management domain.
A resource can be a physical or logical entity. Logical resources include physical resources. Resources are configured with certain
indicators for capturing performance data values. The performance monitoring system collects performance data values for the
indicators.
Indicator
Performance indicators are related to resources. Indicators are performance data, such as CPU usage and memory usage, for
monitored resources. The NMS collects performance data for monitored resources and implement calculation. Performance indicator
attributes include the data type, precision value (limited only to the floating point value), and minimum and maximum values.
Indicator group
An indicator group refers to a statistics group, such as a basic indicator group or a subrack feature indicator group. During the
performance statistics process, an indicator group is the collection of statistics indicators. Each indicator group consists of one or
multiple indicators with similar attributes.
Threshold configuration
A threshold is specified for an indicator.
Data monitoring template
A data monitoring template is an indicator collection used to collect resource performance data. Users can configure indicators and
indicator groups.
TCA monitoring template
A TCA monitoring template is a collection of indicators and threshold definitions and applies to resources based on selected conditions,
such as upper threshold monitoring and lower threshold monitoring. Threshold definitions include the high trigger threshold, low
trigger threshold, high clear threshold, low clear threshold, high alarm severity, and low alarm severity.
Scheduled policy
Based on the scheduled policy, users collect performance data within a specified period or based on the repetition cycle.
Monitoring instance
Based on monitoring instances and all performance indicators of a resource, users use monitoring templates and scheduled policies to
collect performance data for devices. One monitoring instance collects performance data of only one resource.
Data query
Users can query performance data of indicators related to a resource.
Data dumping
Users can dump performance data to maintain the database and disk space.
Historical graph: facilitates the analysis of abnormal traffic or data (for example, traffic
at holidays is remarkably heavier than that in normal times and the temperatures of
devices in winter are remarkably lower than those of devices in summer).
TCA: The U2000 supports TCAs. When a data value is greater than the upper
threshold or less than the lower threshold, a TCA is reported to the U2000 promptly to
help O&M personnel identify faults, facilitating quick troubleshooting. In addition, data
that exceeds thresholds is marked red in reports.
Report: The U2000 provides various reports for the O&M engineers. The reports
contain extensive online network data such as the traffic, bandwidth usage, and alarm
distribution, which lays a foundation for network design, network planning, and O&M
assessment.
Northbound interface (NBI): The U2000 masks Huawei NE differences and supports
diversified NBIs, implementing interconnection with the OSS.
Background
Select a data monitoring template and click Apply. Alternatively, right-click the template
and choose Apply to from the shortcut menu to create a monitoring instance that
uses the template.
Procedure
1. Choose Performance > Performance Template Management > Performance
Monitor Template from the main menu. The Performance Monitoring Template
tab is displayed.
2. Select a resource type and click Create. Alternatively, right-click on the result
template and choose Create from the shortcut menu. The Create Monitoring
Template dialog box is displayed.
3. Enter the name of the monitoring template in the Monitor Template Name text box.
The name of a template must meet the following requirements:
Template names must be the same for resources of the same type.
Template names are case insensitive.
A template name is a string of a maximum of 60 characters.
A template name allows Chinese characters, spaces, letters, numbers, and
symbols, such as hyphens (-), underscores (_), full stops (.), and slashes (/).
4. In the Select Indicator area, select or deselect monitoring check boxes and set
indicators and indicator groups requiring performance data collection.
1. Optional: In the Date Range area, select Start Date and End Date and set the start
date and end date for monitoring.
2. Note: The default start date and end date are the current date.
3. Optional: Select Scheduled Policy.
4. Click Test to check whether data can be collected for resources.
5. Click Next to create a monitoring instance.
1. At the top of the progress bar, the status of created instances is displayed, indicating
the instance creation status (succeeded or failed).
2. Click Close.
The left figure shows that the efficiency of manual performance monitoring is low and
it is difficult to find problems.
In the right figure, performance deterioration can be easily identified based on TCAs
on the NMS.
Users can obtain the health status of the entire network quickly.
Procedure
1. Choose Performance > Top N Faulty Resources from the main
menu. The Top N Faulty Resources tab is displayed.
2. Select one or multiple indicators and click Query.
This topic describes the procedure for viewing historical performance data of a resource.
Prerequisites
At least one monitoring instance is available.
Background
For resource types other than the virtual private network (VPN) type, multiple
monitoring instances can be selected simultaneously.
Only instances for data monitoring templates support historical data query.
Procedure
Method 1
1. Choose Performance > Performance Monitoring Management from the main
menu. The Performance Monitoring Management tab is displayed.
2. Select one or multiple monitoring instances, right-click, and choose View Historical
Data from the shortcut menu.
3. Note: Only historical data of multiple instances in the same period can be
simultaneously viewed.
Method 2
1. Choose Performance > Browse Historical Performance Data from the main menu.
2. Set query conditions and click Query.
3. Select resources whose historical performance data is to be viewed and click ↓ to
add the resources to the Selected Resources area. Then click OK.
1. Choose Performance > Browse Top N Performance Data from the main menu.
2. On the Browse Top N Performance Data tab, choose NE > Router/Switch/MA/ME
NE > Router and Switch NE from the navigation tree.
3. Click Select under Selected Resources to select resources to be queried.
4. Select bar chart indicators, line graph indicators, and query periods.
5. Click Query.
Monitoring indicators: Both inbound bandwidth usage and outbound bandwidth usage
are less than 70%.
As shown in the preceding figure on this page, the inbound bandwidth usage is
greater than 70% and keeps increasing, and the inbound rate is also increasing.
Therefore, expansion is required.
Determine whether networks are faulty based on the performance monitoring status
and alarms.