HighCapRadioNMS Technical Description - N7.0.0.1.0

Copyright 2013. All rights reserved.
HighCapNMS
N7.0
Technical Description
Rev A.01
May 2013

HighCapNMS
N7.0 Technical Description

HighCapRadio Proprietary and Confidential Page 2 of 88
Table of Contents
1. HighCapNMS system overview ....................................................................... 5
1.1 HighCapNMS features overview .................................................................................... 6
1.1.1 Automatic discovery of network topology ....................................................................... 6
1.1.2 Global fault management ............................................................................................... 7
1.1.3 Network element configuration management ................................................................ 8
1.1.4 Network performance management ............................................................................... 9
1.1.5 End-to-End Ethernet services management ................................................................ 10
1.1.6 End-to-End TDM trail management ............................................................................. 11
1.1.7 Network security management .................................................................................... 12
1.1.8 System administration .................................................................................................. 13
2. System architecture ....................................................................................... 14
2.1 HighCapNMS server components ............................................................................... 14
2.1.1 MySQL database ......................................................................................................... 14
2.1.2 FTP/ TFTP server ........................................................................................................ 14
2.1.3 XML & HTTP proxy ...................................................................................................... 14
2.1.4 Server redundancy ....................................................................................................... 14
2.2 HighCapNMS Client GUI.............................................................................................. 14
2.2.1 Network topology maps................................................................................................ 15
2.2.2 Navigator panel topology tree ...................................................................................... 15
2.3 Management interfaces................................................................................................ 15
2.3.1 Northbound interfaces .................................................................................................. 15
2.3.2 CLI report interface ...................................................................................................... 16
2.3.3 SNMP southbound interface ........................................................................................ 16
3. HighCapNMS features .................................................................................... 17
3.1 GUI based network management ................................................................................ 17
3.1.1 Adding network elements to a network topology map ................................................. 17
3.1.2 Network auto discovery ................................................................................................ 17
3.1.3 Network rediscovery ..................................................................................................... 18
3.1.4 Grouping and linking network elements ....................................................................... 18
3.1.5 Network hierarchy and the Navigator topology tree ..................................................... 18
3.2 Fault and alarms management .................................................................................... 19
3.2.1 Network entity alarms ................................................................................................... 19
3.2.2 HighCapNMSs alarms interface .................................................................................. 19
3.2.3 Viewing top most alarm severity .................................................................................. 19
3.2.4 Viewing alarm history ................................................................................................... 19
3.2.5 Network management alarms ...................................................................................... 20
3.2.6 Alarm triggers ............................................................................................................... 20
3.3 Configuration management .......................................................................................... 20
3.3.1 Network element configuration backup & restore ........................................................ 20
3.3.2 Mass configuration broadcast ...................................................................................... 20
3.3.3 Mass software downloads ............................................................................................ 21
3.3.4 NMS client auto upgrade.............................................................................................. 21
3.4 Traffic services management ....................................................................................... 21
3.4.1 End-to-end Ethernet services management ................................................................ 21
3.4.1.1 GUI based service management ................................................................. 21
HighCapNMS

3.4.1.2 Wizard based provisioning .......................................................................... 22
3.4.1.3 xSTP status maps ........................................................................................ 22
3.4.1.4 Excluding Ethernet services from NMS management ................................. 22
3.4.2 End-to-end TDM trail management .............................................................................. 22
3.4.2.1 GUI based TDM trail management .............................................................. 22
3.4.2.2 Automatic provisioning of TDM trails ........................................................... 23
3.5 Connectivity Fault Management (CFM) ....................................................................... 23
3.6 Performance management .......................................................................................... 23
3.6.1 Inventory management ................................................................................................ 24
3.6.2 Performance monitoring ............................................................................................... 24
3.7 Security ........................................................................................................................ 24
3.7.1 User access control ...................................................................................................... 24
3.7.1.1 Personalize view per user ........................................................................... 24
3.7.1.2 Domain based group permissions and subnet based access rights ........... 25
3.7.1.3 Password security configuration .................................................................. 25
3.7.1.4 Single sign-on to EMS web clients .............................................................. 25
3.7.1.5 RADIUS remote user authentication ........................................................... 25
3.7.2 Audit logging ................................................................................................................ 26
3.7.2.1 Monitoring and managing connected NMS users ....................................... 26
3.7.2.2 User action log ............................................................................................. 26
3.8 System administration .................................................................................................. 26
3.8.1 Task scheduler ............................................................................................................. 26
3.8.2 Database management ................................................................................................ 27
3.8.3 Server redundancy and synchronization ...................................................................... 27
3.9 HighCapNMSs server redundancy .............................................................................. 27
3.9.1 HighCapNMSs redundant server configuration .......................................................... 27
3.9.2 The role of the secondary server ................................................................................. 28
3.9.3 Activation operations for a standby server ................................................................... 29
3.10 HighCapNMS northbound interface ............................................................................. 30
3.10.1 HighCapNMS northbound integration .......................................................................... 30
3.10.2 Northbound trap forwarding ......................................................................................... 30
3.10.3 Configuring northbound trap forwarding ...................................................................... 30
3.10.3.1 Enabling HighCapNMS for northbound trap forwarding .............................. 31
3.10.4 Scheduling reports for the northbound NMS................................................................ 31
3.10.5 Scheduling reports for the northbound NMS................................................................ 32
3.10.6 Northbound trap synchronization ................................................................................. 32
3.10.7 Northbound alarm synchronization .............................................................................. 32
3.10.8 Enabling network elements for northbound trap forwarding ........................................ 33
3.10.9 Northbound heartbeat trap mechanism ....................................................................... 35
3.11 Network management alarms ...................................................................................... 35
3.11.1.1 Management raise alarms ........................................................................... 36
3.11.1.2 Management clear alarms ........................................................................... 37
3.11.2 Ethernet service related alarms ................................................................................... 38
3.11.2.1 Service related network element alarms ..................................................... 38
3.11.2.2 Ethernet service related management alarms ............................................. 39
3.11.3 Trail alarms .................................................................................................................. 39
3.11.4 Configuring sound alarms ............................................................................................ 43
3.12 Command line interface (CLI) ...................................................................................... 44
3.12.1 CLI scheduling instructions .......................................................................................... 44
HighCapNMS

3.13 SNMP MIB support ...................................................................................................... 44
3.13.1 NMS current alarm table (nmsCurrentAlarmTable) ..................................................... 45
3.13.1.1 NMS current alarm table columns ............................................................... 45
3.13.1.2 IDU/ IDU-G current alarm mapping to the NMS current alarms .................. 46
3.13.2 NMS traps .................................................................................................................... 47
3.14 HighCapNMS predefined report types ......................................................................... 48
3.14.1 Performance monitoring reports .................................................................................. 48
3.14.1.1 Radio performance ...................................................................................... 48
3.14.1.2 Radio Ethernet performance ....................................................................... 51
3.14.1.3 Inventory reports .......................................................................................... 57
3.14.1.4 Logs ............................................................................................................. 72
3.14.1.5 Service lists .................................................................................................. 75
4. HighCapNMS Network Support ..................................................................... 78
4.1 Supported Network Elements ...................................................................................... 78
4.1.1 Evolution XPAND IP+ .................................................................................................. 78
4.1.2 AGG-Node-N ................................................................................................................ 78
4.1.3 AODC-C ....................................................................................................................... 78
4.1.4 HighCapRadio Multi-Rate family .................................................................................. 78
4.1.5 HighCapRadio 2000/4800 family ................................................................................. 79
4.1.6 3rd party supported elements ...................................................................................... 79
4.2 Supported protocols ..................................................................................................... 79
5. HighCapNMS license information ................................................................. 80
5.1 Introduction .................................................................................................................. 80
5.2 License requirements ................................................................................................... 80
5.3 License components .................................................................................................... 81
5.3.1 Redundancy server support ......................................................................................... 81
5.3.2 TDM trail license requirements .................................................................................... 81
5.3.3 Ethernet services license requirements ....................................................................... 81
5.4 Licensing MySQL ......................................................................................................... 82
5.5 Temporary demo license.............................................................................................. 82
5.6 Obtaining a permanent license .................................................................................... 82
5.7 License configuration recommendations ..................................................................... 83
5.8 License configuration examples ................................................................................... 83
5.9 HighCapNMS license request form .............................................................................. 84
6. Hardware capacity recommendations .......................................................... 86
6.1 Unix server capacity examples .................................................................................... 86
6.2 Windows server capacity recommendations................................................................ 87
Windows server capacity recommendations .......................................................................... 87
7. Compatibility matrix ....................................................................................... 88

HighCapNMS

1. HighCapNMS system overview
HighCapNMS is a Network Management System (NMS) designed for managing
large scale wireless backhaul networks.
Optimized for centralized operation and maintenance of a complete network,
HighCapNMS offers users a comprehensive set of management functions to
simplify network management work.
HighCapNMSs client interface provides centralized, GUI based access to all
network management functionality.
End-to-end traffic service management
HighCapNMS includes a service management GUI for provisioning,
configuration, monitoring, and management of Ethernet services and TDM
trails. Service view provides Wizard based provisioning, service topology
maps, and GUI driven configuration of service paths.
Fault management
HighCapNMS enables global management of network entity alarms with
comprehensive alarm reporting. The alarms interface provides details of each
alarm, including the alarm type and severity, raise and clear time, probable
causes and corrective actions.
Additionally, all map entities, including network elements, links, TDM trails,
and Ethernet services, are color coded, with the color indicating the status of
the most severe current alarm.
Configuration management
HighCapNMS simplifies network elements configuration management, with
centralized configuration file backup and rollback. HighCapNMSs
configuration broadcast and software download utilities help the NMS user to
manage groups of network elements.
Performance management
Scheduled polling allows users to monitor network activity in real time and to
keep historical performance monitoring information for future usage. For a
more in-depth understanding of network performance, HighCapNMS Clients
reporting interface is designed to help users identify activity patterns and
anticipate problems before they occur.
Inventory and performance reports can be generated for the entire network,
or for a selected subnet, group, trail, or service. Inventory reports provide
information about HighCapRadio network element interfaces and links in the
system. Performance reports provide information about radio, interface, and
trail performance.
Network security
HighCapNMS is a secure system that enables administrators to control who
uses the system, and which parts of the system can be accessed. Security is
maintained by a combination of user access control features, audit logging,
and secured interfaces.
HighCapNMS

Permissions are assigned to groups on a feature-by-feature basis. User access
rights determine which parts of the network a user can view, and which
operations users can perform for each subnet.
1.1 HighCapNMS features overview
1.1.1 Automatic discovery of network topology

Auto discovery of network entities, including network elements, subnets,
multi-line, multi radio, and protected links.
Flexible discovery scope configuration options.
Multi link map discovery and display.
Pre-scheduled network discovery at daily, weekly, and/or monthly
intervals.
HighCapNMS

1.1.2 Global fault management

Comprehensive alarm interface, including dedicated management, trail,
and service alarms.
Alarm details include probable causes and suggestions for corrective
actions.
Graphic representation of alarm severity levels.
Alarm history and user action logs show performed on alarms.
Configurable alarm filtering.
Alarm synchronization toward southbound and northbound interfaces.
Alarm history including raise/clear time and actions performed on an
alarm.
HighCapNMS

1.1.3 Network element configuration management

Global network element administration
Single sign-on with network element managers via HighCapNMS Client
topology maps, service maps, reports, or alarms.
Network elements configuration file backup & rollback
Mass configuration broadcasts
Batch software downloads
HighCapNMS

1.1.4 Network performance management

Generate reports performance and inventory reports for the entire
network or selected groups, subnets or specific network elements.
Sophisticated report filtering for customized views of network status and
performance data
Scheduled report generation via HighCapNMSs command line report
interface.
HighCapNMS

1.1.5 End-to-End Ethernet services management

GUI based Ethernet service management,
Automatic, wizard based provisioning of Ethernet services.
Ethernet service topology maps.
Automatic discovery of all Ethernet service paths.
Multiple property based views.
View current Ethernet service related alarms.
xSTP status map.
Ability to exclude specified Ethernet services from NMS management
based on EVC ID or VLAN ID.
HighCapNMS

1.1.6 End-to-End TDM trail management
GUI based TDM trail management.
Automated, wizard based TDM trail provisioning.
TDM trail topology maps.
Automatic discovery of primary and secondary TDM trails between two
end points.
TDM trail performance monitoring and reporting.
Manage trail protection, including ABR protection, protected SNCP links,
and dual ended protection.
HighCapNMS

1.1.7 Network security management

Feature based permissions.
Subnet based access.
Password encryption and rules enforcing.
Passwords retry ceilings and timeout blocking.
Single sign on with network element managers.
Configure customizable network access.
External user authentication.
Secure authentication and security protocols for all management
interfaces.
HighCapNMS

1.1.8 System administration

Comprehensive server configuration options, including redundancy and
synchronization.
GUI or command line scheduling of recurring tasks.
Database backup, repair, & restore.
HighCapNMS

2. System architecture
2.1 HighCapNMS server components
The HighCapNMS NMS system includes:
HighCapNMS framework - the foundation on which all HighCapNMS
applications and services run
The HighCapNMS server
HighCapNMS database - a centralized internal MySQL database
HighCapNMS Client application - HighCapRadios NMS GUI
2.1.1 MySQL database
HighCapNMS N7.0 works with embedded MySQL Enterprise Server 5.1. The
database is provided as part of the basic HighCapNMS installation. The MySQL
license must be purchased as part of the purchase order of the HighCapNMS
system from HighCapRadio.
2.1.2 FTP/ TFTP server
HighCapNMS uses an external FTP server to backup network element
configuration files and to manage software uploads and downloads. NMS users
can use the FTP server to download configuration files from the network
elements, or to upload software updates.
For Windows servers, HighCapNMS expects to find the FileZilla FTP client
installed in its default location (C:\ProgramFiles\FileZilla Server\)
For UNIX servers, HighCapNMS uses the Solaris FTP client, and doesnt
require FileZilla.
2.1.3 XML & HTTP proxy
HighCapNMS has an embedded XML & HTTP proxy that enables connection
between network elements and the HighCapNMS Client when direct
connection between is unavailable.
2.1.4 Server redundancy
HighCapNMS has built-in support for redundancy configuration. With two
HighCapNMS servers, one is configured as the primary server, with the
secondary server configured for standby mode.
2.2 HighCapNMS Client GUI
HighCapNMSs network management GUI, HighCapNMS Client, enables fast
and easy design of multi-layered network element maps, and helps manage
the network from the initial deployment stage through ongoing maintenance
and configuration procedures.
HighCapNMS

With full support for todays mixed network topologies, HighCapNMSs
network management GUI enables maximum flexibility in network operation,
planning and design.
2.2.1 Network topology maps
The topology map shows both physical and logical links between network
entities. When there are multiple physical links between two network-
elements, HighCapNMS Client treats them all as separate links. Logical links
can be configured for Ethernet traffic.
Actions are performed on the current selection. For most operations,
actions will be applied to all the sub-elements that are included in the
selection.
The main window presents a map of the network topology, with a topology
tree in the Navigator panel on the left.
Alarm severity of map entities is represented by color.
Mouse over a network element to display its tooltip, with information
about the network element: its user defined name, its system name, IP, and
alarm severity.
Double clicking an icon opens the Element Manager of a single network
element.
Double clicking a group of network elements opens a map of the group.
2.2.2 Navigator panel topology tree
HighCapNMS Clients topology tree provides a logical view of network
topology. NMS users can drill down to see all the subnets in their view of
network, and all of the elements in each subnet.
2.3 Management interfaces
HighCapNMS supports three different management interfaces for network
management access:
Northbound interface (SNMP, NetAct ESYMAC)
Reports interface CLI reports interface
Southbound interface (SNMP, XML over HTTP)
2.3.1 Northbound interfaces
SNMP Interface toward OSS / Other NMS platforms
HighCapNMSs SNMP agent provides a system-wide active alarm table, which
the northbound OSSs can poll when needed.
HighCapNMS can be configured to forward network elements server
management traps to a predefined server IP address (OSS server).
Northbound alarm synchronization towards a higher level NMS / OSS is
available. An external OSS can poll the alarms counter and the current alarm
table through SNMP.
HighCapNMS

NetAct ESYMAC
HighCapNMS supports the NSN open OAM interface for integration with OSS
level network management systems. Via this interface, faults, topology, and
performance data can be sent to the northbound OSS.
2.3.2 CLI report interface
HighCapNMS allows system administrators to perform many server related
tasks via the command line.
The CLI interface can be used to generate performance monitoring and
inventory data reports for higher level OSS usage. The CLI also allows access
to the HighCapNMS system for specific tasks, such as starting or stopping the
server, exporting and importing data, or scheduling recurring reports.
2.3.3 SNMP southbound interface
HighCapNMSs NMS supports monitoring and configuring of network elements
via the SNMP interface. In addition to logging alarms which have been
received through SNMP traps, HighCapNMS includes an alarm synchronization
mechanism that automatically creates and generates traps for alarms that
were sent by the network element but didn't reach the HighCapNMS server.
HighCapNMS

3. HighCapNMS features
3.1 GUI based network management
HighCapNMSs client interface provides centralized, GUI based access to all
network management functionality.
View and manage network entity alarms.
Current alarm status is built into the topology GUI. All map entities are
color coded according to alarm severity. If there is more than one alarm
configured for a network entity, the map entity will display the color of the
most severe alarm.
Perform global configuration operations such as configuration broadcasts
and software downloads.
Monitor network element status and performance.
Define customized, feature based access to network elements.
Manage network traffic services.
Open network element EMS from HighCapNMS Client topology maps,
alarm lists, or reports to configure parameters for a selected network
element.
3.1.1 Adding network elements to a network topology map
There are three ways to add network elements to a network topology map:
Each method is appropriate for different stages of network management.
Using auto discovery
Auto discovery finds existing network elements, links, and alarms. As
HighCapNMS is designed to manage large networks, auto discovery is the
recommended way to initialize network topology maps.
Manually adding network elements
NMS users can manually add network elements to a group or subnet. This
is useful for adding specific units to a discovered topology, and for
designing changes to network topology.
Importing map data
NMS users can also import saved network topology. Note that importing
map data will overwrite any changes that were made after exporting the
map data.
3.1.2 Network auto discovery
The HighCapNMS Client provides auto discovery of network entities, including
network elements, subnets, multi-line, multi radio, and protected links. Auto
discovery can be performed on a timer, enabling users to schedule network
discovery for specific times on a regular daily, weekly, and/or monthly basis.
Users can define the range of the discovery scope according to IP range or
subnet, or a combination of both. HighCapNMS Client allows users to choose
HighCapNMS

between different protocols and authentication methods for each type of
discovery scope.
The auto discovery utility is able to identify any network entity with an IP
address, including third party elements and elements with floating IP
addresses.
3.1.3 Network rediscovery
When an element is first added to the map, HighCapNMS automatically reads
the elements static information.
There are a number of rediscovery options that will update the network
topology map with current data. Each discovery feature has a distinct purpose.
Users can perform a Discover node operation to re-discover the element's
properties. Discover node replaces existing information, including stored
reports, with the new data.
Users can perform a Poll node operation for a selection of discovered
network elements to retrieve current performance and availability status.
Users can also Refresh topology maps to display the most current data
from the server.
3.1.4 Grouping and linking network elements
Users can create an unlimited number of levels in the map by grouping
network elements. Groups that are added to the map will also be added to the
topology panel on the left.
Users can differentiate between groups by establishing logical naming
conventions, choosing the appropriate icon to represent each group, and by
defining group backgrounds.
Links in the map show how elements and groups are connected in the
network. Multiple link configurations, such as multi-radio links, aggregated
links, and 2+2 configurations, are represented by corresponding link types.
During the Auto discovery process, HighCapNMS also searches for
connectivity between elements. When connections are found, HighCapNMS
automatically identifies the type of link and adds links the connected elements
on the topology map.
If more than two elements are found to be linked, HighCapNMS automatically
creates a sub-group, and moves the linked elements to that sub-group.
If a user moves linked network elements or groups, the links between them
will be moved as well. If the elements have links to other elements that are not
to be moved, the links will be deleted instead.
3.1.5 Network hierarchy and the Navigator topology tree
HighCapNMS Client's Navigator panel displays a hierarchical view of network
topology. Network entities are automatically arranged on the topology tree
according to subnet. Users can drill down to see all the subnets in the network,
and all of the sub-elements of on that subnet.
HighCapNMS

HighCapNMS operates in a hierarchical manner. Most operations apply to the
selected network elements, including all the sub-elements in the selection.
HighCapNMS supports up to seven levels of hierarchy.
3.2 Fault and alarms management
HighCapNMS enables global management of network entity alarms with
comprehensive alarm reporting.
3.2.1 Network entity alarms
Network operators can view current or historical alarms for a group, subnet,
network element, or for the entire network.
In terms of functionality, the alarm lists are similar to the network element
EMS reports. Users can view, filter, print, and save the current alarms, alarm
triggers, and the alarm history logs.
3.2.2 HighCapNMSs alarms interface
The alarms interface provides details of each alarm, including the alarm type
and severity, raise and clear time, probable causes, and corrective actions.
After viewing an alarms details, an NMS user may:
Acknowledge the alarm, or to perform a collective acknowledgement for a
selection of alarms.
Add a note to the alarm, without acknowledging the alarm.
Reset an acknowledged alarm to unacknowledged.
Set the alarm to hidden so that it will no longer appear in the alarm lists.
Users will be prompted to add a note about the hidden alarm.
Show hidden alarms, or remove hidden status from an alarm.
The acknowledge state of an alarm, alarm descriptions, and alarm messages
can all be used to help find the alarm when viewing the alarm or user actions
logs.
3.2.3 Viewing top most alarm severity
Additionally, all map entities, including network elements, links, trails, and
services, are color coded, with the color indicating the status of the top most
current alarm.
3.2.4 Viewing alarm history
The list of current alarms helps users to identify which items require
immediate action, for example, recurring events that may require preventative
measures.
Network administrators can specify how long to keep alarm log information,
with the exception of raised alarms which are kept in the alarm history log
until they are cleared.
HighCapNMS

3.2.5 Network management alarms
Management alarms keep users informed about the state of their networks.
For example, network management alarms will forward a trap if the NMS
loses connectivity with a network element, if the network is unable to switch
to a standby server, if the server is running low on disk space, or if a license is
about to expire.
3.2.6 Alarm triggers
Alarm triggers and trap generation complement scheduled polling intervals,
providing real time alerts about loss of radio frames, surpassing capacity
thresholds and network element level issues that affect network services.
Trigger configuration allows users to define activation conditions and
activation operations for raising alarms.
Activation conditions can be based on alarm severity, alarm type, alarm
description, or acknowledged status.
For example, users can enable a Severity trigger by selecting one or
more alarm severities or activate a trigger when specific characters are
detected in the alarm text.
Activation operations include displaying messages, sound alarms, sending
email, forwarding traps, and customized executables.
3.3 Configuration management
HighCapNMS simplifies management of network elements by enabling global
administration of network element configuration.
HighCapNMS simplifies network elements configuration management, with
centralized configuration file backup and rollback. HighCapNMSs broadcast
configuration and software download utilities help the NMS user to manage
groups of network elements.
3.3.1 Network element configuration backup & restore
HighCapNMS reads network element configuration data during its user
defined polling intervals. Network element configuration data is stored in
configuration files on the NMS database.
Network administrators can use these files to restore network elements to the
latest functioned configuration.
3.3.2 Mass configuration broadcast
HighCapNMSs broadcast configuration and software download utilities help
the NMS user to manage groups of network elements.
HighCapNMSs broadcast configuration utility allows users to set attributes or
modify configuration parameters for selections of network elements
according to type of element, subnet, or other common feature.
HighCapNMS

3.3.3 Mass software downloads
HighCapNMSs smart software download utility allows users to perform
simultaneous upgrades of multiple units. As with mass configuration
broadcast, if a selection includes sub-elements, the download will apply to all
the sub-elements as well.
HighCapNMS uses a customized version of its software download utility to
provide automatic client upgrades.
3.3.4 NMS client auto upgrade
When upgrading from N6.7 or higher, HighCapNMSs smart upgrade utility
will find all HighCapNMS Clients on the network, and will perform automatic
upgrades from the previous two releases, for clients running versions N6.7
and higher.
3.4 Traffic services management
HighCapNMS includes a service management GUI for provisioning,
configuration, monitoring and management of Ethernet service and TDM
trails. Service view provides Wizard based provisioning, service topology
maps, and GUI driven configuration of service paths and trails.
3.4.1 End-to-end Ethernet services management
Note that the IP tables for target service access points must be pre-configured
through the network element web EMS or CLI.
Ethernet level connectivity must be preconfigured manually; otherwise
HighCapNMS will not recognize the Ethernet ports neighbors. Additionally,
ports must be enabled and configured for all the network elements for the
target service.
HighCapNMSs end to end Ethernet service management is available for:
XPAND IP R1 release I6.3.2 and above
IDU-G and IDU-E release I6.7 and above
3.4.1.1 GUI based service management
The Ethernet services GUI simplifies configuration and management of
Ethernet service paths.
Service view provides GUI based access to all service attributes:
Provision and configure new Ethernet services.
Edit service access points and service network point parameters.
Repair services whose operational status is unknown, broken, or partially
configured.
Update service status.
Poll a service to update the service topology map with the current status
and alarms.
View and manage service related alarms for network elements along the
service path.
HighCapNMS

View real time operational status of xSTP rings.
Remove services.
3.4.1.2 Wizard based provisioning
Wizard based provisioning wizard automates configuration of Ethernet
service paths.
The Ethernet services wizard automates provisioning of E-LINE and E-LAN
services. HighCapNMSs auto discovery searches for paths between two or
more selected service access point.
3.4.1.3 xSTP status maps
STP ensures a loop-free topology for any bridged LAN. Spanning Tree allows a
network design to include spare (redundant) links for automatic backup
paths, needed for cases in which an active link fails. The backup paths can be
included with no danger of bridge loops, or the need for manual
enabling/disabling of the backup links. Bridge loops must be avoided since
they result in network flooding.
Users can choose between the Fast Ring RSTP and the standard RSTP
protocols as defined in IEEE 802.1D.
RSTP and Ring RSTP algorithms are designed to create loop-free topologies in
any network design, which makes it sub-optimal to ring topologies.
3.4.1.4 Excluding Ethernet services from NMS management
HighCapNMS enables users to configure and maintain a list of services that
will not be managed inHighCapNMS. This enables users to prevent services
that do not need to be managed in HighCapNMS from taking up network
resources. For example, the network may include management services that
traverse a large number of network elements, some of which are not managed
byHighCapNMS. By adding these services to the Unmanaged EVCs list, users
can conserve network resources and simplify management of the services that
do need to be managed in HighCapNMS.
Users can add an Ethernet service to the Unmanaged EVCs list based on the
services VLAN ID or EVC ID.
3.4.2 End-to-end TDM trail management
HighCapNMSs end-to-end trail management allows comprehensive trail
definitions and configuration of trail properties and status information such as
alarms, operational status and performance monitoring.
3.4.2.1 GUI based TDM trail management
The TDM trail GUI simplifies configuration and management of TDM trails,
providing access to all trail parameters:
Add trail protection to an unprotected trail.
Manage trail protection by specifying which will be the primary trail and
which will be the secondary trail.
HighCapNMS

Generate trail performance reports from the HighCapNMS Client GUI, or
schedule recurring reports using HighCapNMSs command line report
interface.
View trail related alarms.
Poll trails to update the trail map with current availability and alarm
status data.
3.4.2.2 Automatic provisioning of TDM trails
Wizard based provisioning wizard automates configuration of TDM trails.
HighCapNMSs auto discovery searches for the most efficient trail between
two selected end points.
HighCapNMS calculates the trail path using information from the network
elements. Links between network elements along the target trail must be
discovered and TDM enabled for the system to automatically provision a TDM
trail.
3.5 Connectivity Fault Management (CFM)
HighCapNMS supports CFM for IDU-G and IDU-E network elements that meet
the following requirements:
Network element must be running software version I6.9 or higher.
Network element must be configured to Metro Switch or Managed Switch
switching mode.
You can use HighCapNMS to configure Maintenance Associations (MAs) on
Ethernet services. HighCapNMS calculates the service points (SPs) on the
service that belong to network elements that are supported for CFM and meet
the other criteria membership in the MA, and creates the MA, creating the
necessary Maintenance End Points (MEPs) and Maintenance Intermediate
Points (MIPs) on the network elements.
MAs perform continuity checks at defined intervals by sending Continuity
Check Messages (CCMs). CCMs are heartbeat messages exchanged periodically
between all the MEPs in an Ethernet service. Each MEP sends out multicast
CCMs and receives CCMs from all the other MEPs in the service, known as peer
MEPs. This enables each MEP to discover its peer MEPs, and to verify
connectivity among them. MIPs also receive CCMs, which they use to build a
MAC learning database that is used when responding to a linktrace.
You can perform a loopback from any MEP on a defined MA. Loopbacks verify
connectivity between a MEP and all the other MEPs and MIPs on the MA.
3.6 Performance management
Scheduled polling allows users to store historical data and to monitor network
level activity in near real time.
HighCapNMS Client reporting interface is designed to help users identify
activity patterns and anticipate problems before they occur. Report specific
filters allow for customized report generation.
HighCapNMS

Inventory and performance reports can be generated for the entire network,
or for a selected subnet, group, trail, or service.
In addition to the built-in reports, the Service view reporting interface
displays Ethernet service and TDM trail status information.
3.6.1 Inventory management
HighCapNMS retrieves inventory information from all managed network
elements. Inventory data is available to users via 14 built-in predefined
reports.
Inventory reports provide information about HighCapRadio interfaces and
links in the system.
3.6.2 Performance monitoring
Comprehensive PMs for network entities are available via the built in
Performance reports.
Performance reports provide information about radio, interface, and trail
performance.
3.7 Security
HighCapNMS is a secure system that enables administrators to control who
uses the system, and which parts of the system can be accessed.
Security is maintained by a combination of user access control features, audit
logging, and secured interfaces.
Permissions are assigned to groups on a feature by feature basis. User access
rights determine which parts of the network a user can view, and which
operations users can perform for each subnet.
3.7.1 User access control
User access configuration determines which parts of the network a user can
view, and which operations users can perform for each subnet.
In effect, user access rights create a personalized view of the network for each
user.
3.7.1.1 Personalize view per user
Network topology and service maps are saved in the database per user.
When network operators open their clients, they see only the map for the
network where theyve been granted access.
Discovery and configuration scope, alarm lists, traffic service management,
and reports are all limited to the IP range and subnets where users have
access rights.
For example, the list of current alarms that a network operator sees is actually
only a subset of the list of alarms that will be displayed to an Admin-Security
user who has access rights to the entire network.
HighCapNMS

3.7.1.2 Domain based group permissions and subnet based access rights
The set of operations that network operator may perform within their allowed
subnets is further limited by the permissions that are defined for each group.
Users are assigned to one group per subnet; however, they may be assigned to
a different group with different permissions for each subnet.
Permissions are configured on a feature by feature basis for each group.
3.7.1.3 Password security configuration
Administrators can enforce password security by enabling minimum
password length, password complexity, and password aging.
By default, passwords must be at least eight characters long and must include
a mix of alphanumeric characters and case.
The default interval for password expiry is one month. New passwords cannot
repeat any of the previous five passwords.
Password compliance is enforced. HighCapNMS will not accept a user
password that does not meet all the configured restrictions.
Password rule settings can be modified by an Admin network administrator.
Passwords information is encrypted on the database.
3.7.1.4 Single sign-on to EMS web clients
HighCapNMS supports single sign-on with IDUWeb EMS.
User name and password for single sign-on are assigned to groups.
Login information to EMS users is assigned to groups that define which
operations users will be able to perform on managed network elements.
For single sign-on with network elements, users must be granted access rights
to the subnet where the network element is located, as a user of a group with
silent login privileges.
3.7.1.5 RADIUS remote user authentication
The RADIUS protocol provides centralized user management services.
HighCapNMS can be configured to function as a RADIUS client for user
authentication.
When RADIUS is enabled, a user attempting to log into the system is not
authenticated locally but rather, his or her credentials are sent to a centralized
standard RADIUS server which indicates to HighCapNMS whether the user is
known, and which privilege is to be given to the user.
RADIUS login works as follows:
If the Radius server is available, users will be authenticated by the RADIUS
server.
If the RADIUS server is not available, the user will be authenticated locally.
If the RADIUS server rejects the user, no further authentication will be
performed locally, and the user will not be able to log in.
HighCapNMS

For the user with the user name admin, HighCapNMS enables you to
configure whether this user is authenticated locally or by RADIUS. If you
choose to authenticate the admin user locally, the admin user will always
be authenticated locally and not by RADIUS, even when the RADIUS server
is available.
In order to support privilege levels that are specific for HighCapNMS and for
HighCapRadio network elements, the vendor-specific field must be used.
HighCapRadios IANA number for this field is 2281.
The following RADIUS servers are supported:
FreeRADIUS
RADIUS on Windows Server (IAS)
Windows Server 2008
Windows Server 2003
Cisco ACS
3.7.2 Audit logging
3.7.2.1 Monitoring and managing connected NMS users
Admin users can view actions performed by connected users.
The connected users report displays the user name, the IP address of network
element on which an action is being performed, and the protocol used to
connect to the network element.
The network administrator can send messages or disconnect connected users.
3.7.2.2 User action log
HighCapNMS records all user actions performed over the past day. The log
records details about each operation performed by every system user.
The User action log displays the username, location, and details about the
operation that was performed.
When Web EMS is connected to the network elements via HighCapNMS, Web
EMS operations will be included in the user action log.
3.8 System administration
3.8.1 Task scheduler
HighCapNMSs task scheduler allows network administrators to set up
recurring tasks such as database checks and automatic database backup.
While HighCapNMSs command line interface only allows specific,
HighCapNMS supported executables, HighCapNMS Clients task schedule
allows users to set up customized executables as recurring tasks.
HighCapRadio recommends adding database and configuration backup as
daily tasks. Database backup and repair can also be performed using
HighCapNMSs command line interface.
HighCapNMS

3.8.2 Database management
HighCapNMS stores performance monitoring data, network element
inventory, alarm and user action history, map topology, user definitions, and
configuration backups for all network entities.
The system is preconfigured with recommended but customizable - log
limits.
Polling data, alarm history and user action logs are stored for a user-
specified period of time in the server database.
Configuration backup saves the four most recent snapshots.
Network map topology, alarm triggers, and scheduled tasks are saved per
user.
3.8.3 Server redundancy and synchronization
HighCapNMS has built-in support for server redundancy.
When redundancy is enabled, network operators can configure redundancy
thresholds and synchronization options.
By default, data is synchronized from the primary to the secondary server. The
administrator can also set the synchronization for both ways, or disable it
altogether.
3.9 HighCapNMSs server redundancy
3.9.1 HighCapNMSs redundant server configuration
HighCapNMS has built-in support for redundancy configuration. This
configuration includes two HighCapNMS servers: a primary server, which is
generally active, and a secondary server, which is generally located at
a geographically remote site and is in standby mode.
HighCapNMS

HighCapNMS redundancy schema

Redundancy requires that databases in both servers remain synchronized:
topology changes, including adding and deleting network elements, must be
synchronized across both databases.
By default, data is synchronized from the primary to the secondary server. The
administrator can also set the synchronization for both ways, or disable it
altogether.
In a redundant server configuration, data that is imperative for the well
functioning of the servers, such as topology and security information, is
usually synchronized from the primary to the secondary server.
Administrators can also set synchronization to work in both directions, or
disable it altogether.
Topology data, trigger definitions, and security settings are included in the
synchronization.
Configuration settings may differ between servers and are not included in
the synchronization process.
3.9.2 The role of the secondary server
While a secondary server is on standby, its server duties are usually limited to
polling network elements. By default, a secondary server will poll only for
alarms, but network administrators can configure the secondary to poll also
for inventory information and PMs.
Administrators who are concerned about the toll of two servers polling the
network can also configure the secondary server to not do any polling at all.
HighCapNMS

When a secondary server becomes active, it immediately takes over all the
defined tasks of the main server. It immediately begins polling the network,
activating triggers, and forwarding traps.
A secondary server takes over automatically when:
It loses connection with the main server.
The main server loses connection to HighCapNMS clients.
The network administrator forces the secondary server to be active mode.
A secondary server resumes standby mode when:
When the main server is active.
3.9.3 Activation operations for a standby server
If the main server is down, the standby server can be configured to
automatically take over.
The standby server becomes active when the main server crosses user
specified thresholds, or if it loses connectivity with the main server. When the
main server starts again after a failure, the secondary server returns to
standby mode.
Lost connectivity between the two servers could mean that the main server is
unavailable, but it could also create a situation where both will become active.
If the synchronization mode is both ways, when connectivity is restored, the
main server will get the current topology map from the standby server. When
the synchronization mode is from main to standby, no synchronization action
will be performed when the main server becomes active again.
In all cases, switching to the standby server raises an alarm, and gives users
the option to switch back to the primary server.
If no connection is detected between the main and standby servers for
more than the user defined loss of connectivity threshold:
It will raise the alarm No Connection with Standby Server
In Auto mode, the secondary (standby) server becomes active, and will:
Start sending traps and triggers.
Start accepting client connections.
Raise the management alarm No Connection with Main Server.
Start polling network elements.
When the connection is resumed and is stable:
The main server clears the No Connection with Standby Server alarm.
If in Auto mode, the secondary (standby) server will go to standby mode,
and will:
Clear the management alarm No Connection with Main Server
Notify about new client connections, and send the message Main
server (IP) is active to connected clients.
Stop sending traps and triggers.
Resume limited polling (by default, in standby mode, the secondary
server polls only alarms).
HighCapNMS

When a security file is updated, the standby server reloads the file, and
immediately begins to use it.
Network elements should be configured to send traps to both servers.
3.10 HighCapNMS northbound interface
HighCapNMS's flexible architecture allows it to be used either as a stand-alone
network management system or as a supporting component for an OSS with
an existing NMS.
3.10.1 HighCapNMS northbound integration
HighCapNMS supports all OSS for basic northbound communication, providing
a deeper level of integration with the NSN open OAM. Via this interface,
besides faults performance data is also sent to the northbound NSN Netact
OSS.
HighCapNMSs trap forwarding utility allows integration with OSS network
systems. HighCapNMS can forward SNMP traps that arrive from the devices to
one or more OSS network management systems.
HighCapNMS also includes an SNMP agent that provides a system-wide active
alarm table, which the northbound OSS can poll when needed.
3.10.2 Northbound trap forwarding
HighCapNMS can forward network element traps and events that arrive from
network devices to one or more OSS network management systems. In
addition, HighCapNMS also forwards management alarms, such as security,
license, and redundancy.
Trap forwarding is a two-step process: network elements send traps to the
trap forwarding utility. The trap forwarding utility forwards these traps to
HighCapNMS, encapsulates it, and sends it to the northbound traps
destination.
In the Internet protocol header, the sender IP of the forward trap will be the
HighCapNMS IP.
In the SNMP trap header, the agent address (agent-addr) will contain the
element IP address.
HighCapNMS forwards the same the SNMP version that it receives from the
elements: V1, V2c, V3.
3.10.3 Configuring northbound trap forwarding
Set trap forwarding parameters specific to the OSS network management
application.
To configure northbound trap forwarding settings:
1 Select Start > Programs > HighCapNMS > Trap forwarding config, or
select Settings > Trap forwarding options from the HighCapNMS Client
menu to open the HighCapNMS trap forwarding utility.
2 Select the NetAct Specific tab.
HighCapNMS


3 SNMP agent address Specify the IP address.
4 SNMP agent port number Specify the agent port.
5 NMS server ID Define a unique ID for the OSS NMS server.
Note: In the NMS server ID field, you may want to change the
value When multiple NMS servers are connected to the
same NSN server, make sure that each NMS server has a
unique ID.
6 Click Apply to save changes.
7 Click Close to exit the Trap forwarding config utility.
3.10.3.1 Enabling HighCapNMS for northbound trap forwarding
Northbound trap forwarding is configuring using HighCapNMSs trap
forwarding configuration utility.
To enable northbound forwarding, in the Trap Forwarding utility:
1 Set the Trap Forwarding mode to Regular.
2 Specify the host addresses of the target destinations.
3 Specify the listening port number for incoming traps.
To avoid multiple traps being sent to the northbound OSS, network elements
should only send traps to the HighCapNMS traps receiver.
Note that you can customize elements traps by setting the severity level for
sending traps and enabling or disabling heartbeat traps. You can also modify
the polling interval that HighCapNMS uses to poll network elements.
3.10.4 Scheduling reports for the northbound NMS
Report Information: Using the HighCapNMS CLI interface, you can generate
different reports, such as Current alarms, Alarm log, Performance
management, Inventory, and User actions. The reports can be forwarded to
the northbound OSS automatically and periodically (in accordance with user
preference) in plain text or CSV format.
HighCapNMS

3.10.5 Scheduling reports for the northbound NMS
Using the HighCapNMS CLI interface, you can generate different reports, such
as Current alarms, Alarm log, Performance management, Inventory, and User
actions.
The reports can either collected or forwarded to the northbound OSS
automatically and periodically (in accordance with user preference), in plain
text or CSV format.
3.10.6 Northbound trap synchronization
When a trap detected from the network element was not received,
HighCapNMS will generate the trap for the network element and send it to the
northbound OSS.
When a trap detected from the network element was not received,
HighCapNMS will generate the trap for the network element and send it to the
northbound OSS. HighCapNMS will raise node down trap (nmsNodeDown
Alarm ID 63, trap ID 401) for the unreachable element. Upon resuming
connection, HighCapNMS will send a node up trap. (nmsNodeUp Alarm ID 63,
trap ID 501).
To enable alarm synchronization:
1 Enable trap forwarding of the nmsAlarmLastChange event.
Note: The nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1) is a
counter that advances every change of the current alarm
table and compares it with the OSS alarms/traps counter.
2 Allow the OSS NMS access to the HighCapNMS alarm table.
Note: If the value is not the same, the OSS must poll the current
HighCapNMS alarm table, nmsCurrentAlarmTable (which
contains all IDU, x1500, HighCapNMS, and 3rd party current
alarms). This will synchronize all alarms in the current
alarm table.
3.10.7 Northbound alarm synchronization
For northbound interfaces, HighCapNMS provides an alarm synchronization
mechanism.
HighCapNMSs SNMP agent provides a system-wide active alarm table, which
the northbound OSSs can poll when needed. An external OSS can poll the
alarms counter and the current alarm table through SNMP.
To enable alarm synchronization, allow the OSS NMS access to the
HighCapNMS alarm table and enable trap forwarding of the
nmsAlarmLastChange event. The nmsAlarmLastChange
(1.3.6.1.4.1.2281.2.2.15.1.1) is a counter that advances every change of the
current alarm table and compares it with the OSS alarms/traps counter.
If the value is not the same, the OSS must poll the current HighCapNMS alarm
table, nmsCurrentAlarmTable (which contains all IDU, x1500, HighCapNMS,
and 3rd party current alarms). This will synchronize all alarms in the current
alarm table.
HighCapNMS

3.10.8 Enabling network elements for northbound trap forwarding
HighCapRadio MIB objects to configure traps of network element of IDU
series.
genEquipTrapCfgMgrAdmin
Enables/ disables a specific manager. When disabled - will not send traps to
this trap manager.
genEquipTrapCfgMgrIP
Configures the managers IP address.
genEquipTrapCfgMgrPort
Configures the port that sends the trap for each manager.
genEquipTrapCfgMgrName
Configures the name of the manager that receives the traps.
genEquipTrapCfgMgrCommunity
Configures the trap manager community.
genEquipTrapCfgMgrSeverityFilter
Bit mask value for masking traps according to its severity.
genEquipTrapCfgMgrStatusChangeFilter
Enables or disables filtering alarms according to a change in the trap severity
filter.
genEquipTrapCfgMgrCLLI
Configures the Common Language Location Identifier (CLLI), a user input that
will be sent in a field in the trap varbind
genEquipTrapCfgMgrHeartbeatPeriod
Configures the minute interval between each heartbeat.

HighCapRadio MIB objects to configure traps of network element of 1500
series
gnAgnMgrId
This value indicates an index of a specific manager.

gnAgnMgrIP
This value indicates the managers IP address.
An IP address of all zeroes (0.0.0.0) will remove the entry.

gnAgnMgrAlarmGroupMask
bit mask .1 is 'send a trap' 0 is doesnt send any traps'.
The list of alarms from MSB to LSB is:
bit 1 = Power supply alarm
bit 2 = Cable alarm
bit 3 = Temperature alarm
bit 4 = External alarm
HighCapNMS

bit 5 = Radio alarm
bit 6 = Modem alarm
bit 7 = Line alarm
bit 8 = SDH alarm
bit 9 = BER alarm
bit 10 = System fault alarm
bit 11 = Maintenance alarm
If this field is 0, only standard traps will be sent to the manager

gnAgnMgrSeverityFilter
This is a bit mask value for masking traps according to their severity.
There is a bit for each severity. If the relevant bit is on (1), then the Agent will
send traps with this severity
The list of bits from LSB to MSB:
bit 1 (LSB) = Event.
bit 2 = Warning.
bit 3 = Minor.
bit 4 = Major.
bit 5 (MSB) = Critical.

gnAgnMgrTrapPort
The port for sending the trap for each manager (possible values: 70-65535)

gnGenCfgCLLI
Common Language Location Identifier (maximum length 30 characters).
This string is added as a field in the trap.

gnGenCfgHeartbeatPeriod
Configure the element to send heartbeat trap. The value is in minutes.
Setting the value to 0 disables this feature.

gnGenCfgTrapOption
This item defines various trap options. It is a bitmask: i.e., you can set multiple
options, by doing bitwise OR between their values.
Possible values are:
Standard traps include serial number.
If selected, the unit serial number is added only to the standard traps
such as "Link Down"
Not supported for the 1500P family.
HighCapNMS

Use different trap ID for each alarm type.
This option normally should be set, otherwise, the traps are grouped
together, and sent with trap ID 1 to 8.
Send 'Cleared' traps with zero severity.
Otherwise they will be sent with the same severity as the "Raised" trap.
gnGenAddAlarmExtToTraps
If this entry enabled, extended information is added to each HighCapRadio
trap. Those additional parameters are added after the last parameter of the
trap, as defined in the MIB.
Note that HighCapNMS requires this option to be enabled.
3.10.9 Northbound heartbeat trap mechanism
HighCapNMS can be configured to forward heartbeat traps from network
elements to a northbound OSS.
When both IDU and HighCapNMS are configured to send heartbeat
traps to northbound.
1 IDU sends heartbeat traps with ID (specific trap) 1003 to HighCapNMS.
2 HighCapNMS receives the traps encapsulates it and sends it as is to
northbound.
3 Northbound receives heartbeat traps from HighCapNMS with agent
address of IDU and with ID 1003.
4 HighCapNMS sends heartbeat traps with ID (specific trap) 49 to
northbound.
5 Northbound receives heartbeat traps from HighCapNMS with ID 49.
Since HighCapNMS forwards traps to northbound without analyzing the trap
type, alarms will not be raised for missing or resumed heartbeats.
HighCapNMS is notified about unreachable network elements only if the
network element is still down during the next polling cycle.
The way to stop heartbeat trap forwarding is to either disable trap forwarding
from HighCapNMS or to disable forwarding of heartbeat traps from the
network elements.
3.11 Network management alarms
HighCapNMS generates several management alarms. Most of the alarms (in
the current alarms and alarm log) can be viewed by selecting the icon
representing the HighCapNMS server in HighCapNMS Client. The server icon
changes color in accordance with the top-most current management alarm
severity.
The only exception is the nmsNodeDown (unreachable element) and
nmsNodeUp (element is reachable) alarms, which are generated by the
HighCapNMS server according to the connectivity to the network element.
These alarms are raised on behalf of the network element itself (as if it was
sent by the element).
Note that all management alarms are forwarded to northbound systems (if
HighCapNMS is configured to forward alarms to the northbound OSS).
HighCapNMS

3.11.1.1 Management raise alarms
Alarm name Description ID Severity
nmsNodeDown Sent when the NMS loses
connection with a network element.
401 Node
down
nmsSecurityFailure Sent if a user fails three sequential
login attempts to the NMS system.
402 Event
nmsPrimaryServerConfigMismatch Sent when a secondary standby
server tries to connect to stand-alone
server.
403 Major
nmsSecondaryServerNotConnected Sent by a primary server when it
loses connection to the secondary
standby server.
404 Major
nmsLicenseExpiresInLessThanTwoWeeks Sent by a main server when license
file expires in less than two weeks.
405 Warning
nmsLicenseExpired Sent by a main server when the
license file has expired.
406 Major
nmsNetworkElementNumExceedsLimit Sent by a main server when the
number of network elements
exceeds the license limit.
407 Major
nmsFailedLoadingLicenseFile Sent by a main server when it fails to
load a license file.
408 Major
nmsTftpServerAlreadyRunning Sent when TFTP port is bound by
another process.
409 Major
userDisconnected Sent when a user is disconnected by
another user.
410 Event
nmsPrimaryServerVerMismatch Sent when a secondary standby
server tries to connect to a main
server with a different NMS version.
411 Major
nmsEsymacNotConnected Sent when the server cannot
communicate with ESYMAC
services.
412 Major
nmsPrimaryServerNotConnected Sent by a secondary standby server
when it loses connection to the
primary server.
413 Major
nmsEnabledFeatureSetNotLicensed Sent when an enabled feature set is
not licensed.
414 Major
nmsFreeDiskSpaceTooLow Sent when the free disk space on the
main disk is below the configured
threshold.
415 Major
nmsCpuLoadTooHigh Sent when average system load is
above the configured threshold.
416 Major
HighCapNMS

Alarm name Description ID Severity
nmsProtectionSwitchOccurred Sent when a protection switch occurs
between the main slots in a network
element
417 Major
nmsPrimaryAndSecondaryServersAreActive Sent by a primary server (Main) and
by the secondary server (Standby)
when both servers are in active
mode in case the percentage of
unreachable NE in the main server
crossed the configured threshold.
The trap description includes the
following format: 'Percentage of
unreachable elements in main server
is over threshold Raised'.
418 Major
nmsFloatingIpAdded Sent when a floating IP is added to a
network element.
The trap description includes the
main (non floating) IP of the network
element in the following format:
'Alarm from IP <IP>: Floating IP
added'.
419 Minor
nmsConfigurationChange Management trap: NMS
configuration change event:
For each configuration change, The
description of the event shall be the
same description that being logged in
the Users Action Log concatenated
with the three fields
- Application
- User name
- Connected From
- Description + Details (in { })
421 Warning
3.11.1.2 Management clear alarms
Alarm name Description ID
nmsNodeUp Sent when the NMS resumes connection with
a previously disconnected network element.
501
nmsPrimaryServerConfigOK Sent when a secondary standby server
connects to a main server
503
nmsSecondaryServerConnected Sent by a primary server when it reconnects
to the secondary standby server
504
nmsLicenseExpiresInMoreThanTwoWeeks Sent by a main server when license file
expires in more than two weeks.
505
nmsLicenseDoesNotExpire Sent by a main server when license file does
not expire.
506
HighCapNMS

nmsNetworkElementNumWithinLimit Sent by a main server when the number of
network elements is back within the license
limit.
507
nmsSuccededLoadingLicenseFile Sent by a main server after successfully
loading the license file.
508
nmsTftpServerStartRunning Sent when the TFTP server successfully
binds the TFTP port.
509
nmsPrimaryServerVerMismatchOK Sent when a secondary standby server
connects to a main server.
511
nmsEsymacConnected Sent when server can communicate with
ESYMAC services.
512
nmsPrimaryServerConnected Sent by a secondary standby server when it
reconnects to the primary server.
513
nmsLicenseConfigurationMismatchRemoved Sent when a license configuration mismatch
is resolved.
514
nmsFreeDiskSpaceOK Clears the free disk space alert. It is sent
when the free disk space of the main disk is
back above the configured threshold.
515
nmsCpuLoadOK Clears the high CPU load alert. It is sent
when the average system load is back to
below the configured threshold.
516
nmsPrimaryAndSecondaryServersAreNotActive Sent by a primary server (Main) and by the
secondary server (Standby) when both
servers are no longer both in active mode.
518
nmsFloatingIpCleared Clears the alert that was sent when a floating
IP was added to a network element.
519
3.11.2 Ethernet service related alarms
3.11.2.1 Service related network element alarms
Alarm description Alarm ID
Mute 410
FE Loss of carrier on port #n (n = 3,4,5,6,7) 401
Ethernet gigabit loss of carrier (port 1 or 2) 403
SFP is not inserted (port1 or 2) 404
SFP malfunction (port 1 or 2) 405
GBE TX mute override 406
Loss of frame on radio 603
IF loopback 1601
HighCapNMS

Alarm description Alarm ID
RF loopback 1722
ODU TX mute 1735
3.11.2.2 Ethernet service related management alarms
nmsNodeDown Sent when the NMS loses connection with a network element. 401
nmsNodeUp Sent when the NMS resumes connection with a previously
disconnected network element.
501
3.11.3 Trail alarms
Name ID Description Severity Origin Probable Cause Corrective Action
lvds-backplane-
error-main
728 Errors in TDM
backplane
channel for
slot # %1.
Major IDU Extension or main
unit equipment
failure.
Backplane failure.
Reinsert unit.
Power-cycle unit.
Replace unit.
Check backplane.
lvds-backplane-
error-extn
729 Errors in TDM
backplane
channel in
connection with
main.
Major IDU Extension or main
unit equipment
failure.
Backplane failure.
Reinsert unit.
Power-cycle unit.
Replace unit.
Check backplane.
lvds-db-error 730 Errors in TDM
channel in
connection with
T-card.
Major IDU IDU HW failure.
T-card HW failure.
Reinsert unit.
Power-cycle unit.
Replace T-card.
Replace IDU.
eeprom-
access-failure
2201 Error in TDM
drawer type
detection
Major IDU Inserted drawer
not supported.
Hardware error.
Make sure drawer is
properly inserted.
Power cycle the
system.
Replace drawer
bp-lof-alarm 2301 TDM backplane
LOF for slot
#%1.
Critical IDU Extension or main
unit equipment
failure.
Backplane failure.
Reinsert unit.
Power-cycle unit.
Check backplane.
idu-presence-
not-detected
2304 IDU #%1
presence not
detected.
Minor IDU IDU with TDM trails
mapped to it was
extracted from
shelf.
Insert IDU in shelf.
Delete relevant TDM
trails
HighCapNMS

extension-bp-
lof
2402 TDM backplane
LOF in
connection with
main.
Critical IDU Extension or main
unit equipment
failure.
Backplane failure.
Re-insert unit.
Power-cycle unit.
Check backplane
failure-in-one-
or-more-tdm-
trails
2403 Failure in one
or more TDM
trails.
Warning IDU Network TDM trail
configuration error.
Signal failure in
TDM trail - this
may be due to
equipment failure
or AIS at the line
input.
Excessive BER in
TDM trail.
Signal degrade in
TDM trail.
Check TDM trails
status.
invalid-trail-
status-change
2406 Invalid trail
status change
%1 in trail %2.
Major IDU Trail end-point
failure detected for
one or more trails.
Trail end-point
failure cleared for
one or more trails.
Perform reset in
end-point IDU if
exists.
Replace end-point
IDU.
trail-excessive-
BER-change
2407 Trail excessive
BER status
change %1 in
trail %2.
Major IDU Trail excessive
BER detected for
one or more trails.
Trail excessive
BER cleared for
one or more trails.
Check links and
equipment alarms
along the TDM trail.
trail-id-
mismatch
2408 Trail ID
mismatch in at
least one trail.
Warning IDU Trail ID spelling
difference between
trail ends.
Network TDM trail
configuration error.
Errors in incoming
signal.
Check trail ID at
both ends of the
trail.
Check network trail
configuration.
Check trail
performance (BER)
along the trail path
and fix errored links
if needed.
trail-id-
mismatch-
change
2409 Trail ID
mismatch
status change
%1 in trail %2.
Warning IDU Trail ID mismatch
detected for one or
more trails.
Trail ID mismatch
cleared for one or
more trails.
Check trail ID at
both ends of the
trail.
Check network trail
configuration.
HighCapNMS

trail-protected-
forced-active
2410 Trail ID: %1,
path: %2 forced
active.
Warning IDU User command
force active.
Set force active to
"none" for this trail.
trail-protected-
switch
2411 Trail protection
switch
performed in
trail %1 due to
%2.
Warning IDU Signal failure along
the active trail's
path.
User issued force
active command to
stand-by path.
NA
trail-signal-
degrade-
change
2412 Trail signal
degrade status
change %1 in
trail %2.
Minor IDU Trail signal
degrade detected
for one or more
trails.
Trail signal
degrade cleared
for one or more
trails.
Check links and
equipment alarms
along the TDM trail.
trails-mapped-
to-inexistent-
interfaces
2413 Trails mapped
to inexistent
interfaces in
IDU #%1.
Warning IDU One or more
components were
extracted from the
system since trails
were defined.
Radio scripts have
been replaced by
narrower scripts
since trails were
defined.
Replace missing
components (IDUs,
T-cards).
Make sure radio
scripts support
required number of
E1/DS1 trails
through radio.
Delete relevant
trails.
trail-signal-
failure-change
2414 Trail signal
failure status
change %1 in
trail %2.
Warning IDU (1) Fade in a link
along the trail.
(2) Equipment
failure in a network
element along the
trail.
(3) Trail not
properly
provisioned along
the path.
Check links,
equipment alarms
and trail
configuration along
the TDM trail.
illegal-trail-
configuration
2415 Conflicting trails
are configured
in protected
IDUs %1 and
%2.
Warning IDU Protection was
enabled in pair of
IDUs between
which trails were
previously
configured.
Erase relevant trails.
Disable protection in
pair.
HighCapNMS

stm1-sync-
clock-signal-
failure
2613 STM-1 clock
source signal
failure.
Major IDU Clock source
configured from
wrong VC.
Radio LOF or
equipment failure
along the path of
the
synchronization
trail.
LOS or AIS at the
synchronization
source interface in
the far end of the
trail.
Make sure the
configured VC is the
end-point of the
synchronization trail.
Check status of
synchronization trail.
Check status of
clock source
interface.

HighCapNMS

3.11.4 Configuring sound alarms
It is possible to configure a sound that will be played when triggered by an
alarm. The sound will be played continuously until the user acknowledges the
alarm.
In the HighCapNMS installation directory, an application called playsound
enables you to configure the sound to be played.
You can run playsound in a command window, using the format:
playsound <sound file name> <message to the user> <severity>
where:
<sound file name> is the name of the file that contains the sound. The value
can be a specific path, or a path relative to the HighCapNMS installation folder.
Several sound files were included with the HighCapNMS installation in the
sound directory in the installation folder.
<message to the user> is a text message that will be displayed for the user in a
window that opens.
<severity> is used to organize the playing of sounds, according to their
severity. If a sound with severity X is triggered by an alarm, and another sound
is triggered by an alarm with severity Y, if Y's severity is greater than that of X
(for example, Y is Major and X is Warning), Y will be played instead of the X. If
Y is not greater than X, X will be played.
PlaySound example
An example of the usage of the playsound application would be to define
different sounds for Major alarms and Critical alarms:
1 Create a trigger.
2 For Severity in the Activate conditions area, select Major.
3 In the Activation operation field, select Run Executable.
Path: playsound
Parameters: sound/bark.au %SEVERITY: %DESCR %#SEVERITY
Execute On: Connected clients
4 Create an additional trigger.
5 For Severity in the Activate conditions area, select Critical.
6 In the Activation operation area, select Run Executable
Path: playsound
Parameters: sound/bong.au %SEVERITY: %DESCR %#SEVERITY
Execute On: Connected clients
HighCapNMS

3.12 Command line interface (CLI)
The CLI executable is a part of the HighCapNMS installation (both client and
server) and therefore the CLI can be activated from any machine on which
HighCapNMS client or server is installed.
There are two common working modes.
CLI runs locally on the server.
The report file is saved in the server machine under a known FTP
directory. Assuming the FTP server is enabled on the HighCapNMS
server machine, a remote machine should fetch the file using an
FTP/SFTP client.
Advantage: The file can be copied via a known protocol (FTP/SFTP)
which is sometimes the only option when dealing with firewalls.
CLI runs on a remote machine
CLI runs as a remote client towards the server. The report is saved on
the remote machine and there is no need for FTP.
Advantages: No need for FTP, the client application copies the file.
3.12.1 CLI scheduling instructions
For Windows, create a batch file containing the desired CLI command.
Schedule it via the Windows scheduler.
For Solaris, create a shell script containing the desired CLI command.
Schedule it via the UNIX crontab application.
3.13 SNMP MIB support
HighCapRadio NMS-MIB functionalities
HighCapNMS supports HighCapRadios proprietary NMS-MIB.
The main functionality of the MIB for HighCapNMS is the current alarm
table.
HighCapNMS MIB uses the current alarm as defined in the HighCapRadio
MIB.
The current alarm table includes:
NMS server alarms
All network element alarms, including alarms for the IDU and the x1500.
In addition to the current alarms there are two scalars:
nmsAlarmLastChange (1.3.6.1.4.1.2281.2.2.15.1.1 ) a counter that
advance every change of the current alarm table.
nmsMostSevereAlarm (1.3.6.1.4.1.2281.2.2.15.1.3( - the most severe alarm
within the current alarm table.
Note the following:
Only SNMP V.1 is supported.
The default Server SNMP port number is 1610 (configurable).
HighCapNMS

The community string for Read only is public.
There are no write permissions for the MIB.
3.13.1 NMS current alarm table (nmsCurrentAlarmTable)
3.13.1.1 NMS current alarm table columns
nmsCurrentAlarmCounter - A running counter of open alarm, the counter
is incremented on every new RAISED trap. It is cleared after reset.
nmsIpAddress The IP address of the NE that the alarm is raised upon. It
could be the NMS servers IP for NMS alarms, or a NE IP for any NE alarm.
nmsCurrentAlarmSeverity The severity of the alarm. The following
severities can be for the alarms
event (1)
warning (3)
minor (7)
major (15)
critical (31)
node down (63) - this is for unreachable NEs raised by the NMS server
only.
nmsCurrentAlarmId - Alarm Identifier (contains alarm type and interface).
Same AlarmId for raise and clear alarms.
nmsCurrentAlarmIfIndex- Interface Index where the alarm occurred,
alarms that are not associated with specific interface will have the
following value (for example, for the x1500):
For IDC related alarms the value is: 65001
For drawer1 related alarms the value is: 65003
For drawer2 related alarms the value is: 65004
If Alarm's origin is bigger than 256, it will be 65000 + the origin
nmsCurrentAlarmOrigin- The origin drawer of the alarm (if applicable,
otherwise it will be idc(2)) other possible values are based on
gnAgnCurrentAlarmOrigin:
Interfaces(1), idc(2), drawer1(3), drawer2(4), unknown(5),
tIdc1(257), tIdc2(258), tIdc3(259), tIdc4(260), tIdc5(261), tIdc6(262),
tIdc7(263), tIdc8(264), tIdc9(265), tDrawer1(513), tDrawer2(514),
tDrawer3(515), tDrawer4(516), tDrawer5(517), tDrawer6(518),
tDrawer15(527), tXC1(769), tXC2(770), tXC3(771), tXC4(772),
tXC5(773), tXC6(774)
nmsCurrentAlarmUnit- The unit of the alarm, possible values are:
idc(2), odu(3), mux(4), modem(5), drawer(6), unknown(7), xc(9)
ODU (101)
nmsCurrentAlarmTrapID- The trap ID of the RAISED trap that was sent
when this alarm was raised.
HighCapNMS

nmsCurrentAlarmTimeT Timestamp of this alarm, this number is the
seconds from midnight 1.1.1970
nmsCurrentAlarmText- The alarm display text (same as the text in the sent
trap).
3.13.1.2 IDU/ IDU-G current alarm mapping to the NMS current alarms
Var-bind mapping IDU to NMS current alarms
IDU trap
Var-
Bind/Current
Alarm Column
IDU Var-Bind NMS Var-Bind Comments
Trap var-bind &
current alarm
column
genEquipCurrentAlarmCounter nmsCurrentAlarmCounter No mapping.
The NMS counter is
different from the
NE counter.
Trap var-bind &
current alarm
column
genEquipCurrentAlarmRaisedTimeT nmsCurrentAlarmTimeT Mapping 1:1
Trap var-bind &
current alarm
column
genEquipCurrentAlarmId nmsCurrentAlarmId Mapping 1:1
Trap var-bind &
current alarm
column
genEquipCurrentAlarmInstance NA No mapping
Trap var-bind &
current alarm
column
genEquipCurrentAlarmSeverity nmsCurrentAlarmSeverity Mapping 1:1
Trap var-bind &
current alarm
column
genEquipCurrentAlarmIfIndex nmsCurrentAlarmIfIndex Mapping 1:1
Trap var-bind &
current alarm
column
genEquipCurrentAlarmModule nmsCurrentAlarmUnit Mapping
IDU : 101
ODU : 3 (odu)
Trap var-bind &
current alarm
column
genEquipCurrentAlarmDesc nmsCurrentAlarmText Mapping 1:1
Trap var-bind only genEquipMostSevereAlarm NA No mapping
Trap var-bind only genEquipNetworkAgentIp nmsIpAddress Mapping 1:1
Trap var-bind &
current alarm
column
genEquipCurrentAlarmState NA No mapping (no
need, as only the
raised traps will be
in the table)
Trap var-bind only genEquipTrapCfgMgrCLLI NA No mapping
HighCapNMS

IDU trap
Var-
Bind/Current
Alarm Column
IDU Var-Bind NMS Var-Bind Comments
Trap id NA nmsCurrentAlarmTrapID The trap ID of the
alarm (SNMP v.1)
Current alarm
column only
genEquipCurrentAlarmName
(the parameter and entity in the CLI)
for example 'radio/framer/radio-lof')
NA No mapping
Trap var-bind &
current alarm
column
genEquipCurrentAlarmSlotId nmsCurrentAlarmSlotId 1000 SA IDU
1001 IDU-G slot 1
1002 IDU-G slot 2
1003 IDU-G slot 3
1004 IDU-G slot 4
1005 IDU-G slot 5
1006 IDU-G slot 6
Current alarm
column only
genEquipCurrentAlarmProbableCau
se
nmsCurrentAlarmProbableCaus
e
Alarm Probable
Cause
Current alarm
column only
genEquipCurrentAlarmCorrectiveAct
ions
nmsCurrentAlarmCorrectiveActio
ns
Alarm Corrective
Actions
3.13.2 NMS traps
The list of NMS traps are defined in HighCapRadio NMS MIB, and in the alarm
chapter.
NMS traps are sent with the following var-binds
gnGenCfgTrapSeverity: Severity of the trap (nmsCurrentAlarmSeverity)
gnGenCfgAlarmText: Alarm text (nmsCurrentAlarmText)
gnGenCfgCLLI: Fixed empty string will be sent ("") - not supported
gnAgnCurrentAlarmOrigin: 400 (fixed number) will be sent - not supported
gnAgnCurrentAlarmUnit: 400 (fixed number) will be sent - not supported
gnAgnCurrentAlarmTimeT: Timestamp of this alarm, nmsCurrentAlarmTimeT will be
sent.
gnAgnCurrentAlarmID: For event - 0 (integer), for alarm it will be equal to the trap ID
of the raise alarm (400+).Trap-ids starting from 500 are
always clearing raise alarms starting in 400. There is a
difference of 100 between raise and clear alarms, for
example, Trap 401 is a raise alarm, while 501 is the clear
alarm for it.
HighCapNMS

3.14 HighCapNMS predefined report types
3.14.1 Performance monitoring reports
3.14.1.1 Radio performance
Radio channels

HighCapNMS

Radio MRMC performance

Radio MSE performance

HighCapNMS

Radio RSL performance

Radio TSL performance

HighCapNMS

Radio XPI performance

3.14.1.2 Radio Ethernet performance
The Radio Ethernet performance report displays Ethernet service
performance parameters.
Frame error rate

HighCapNMS

Frame Error Rate (%) is the number of received error frames measured
by the radio Ethernet port, relative to all frames received by the radio
Ethernet port.
Integrity indicates whether the values received at that time and date are
reliable.
An x in the column indicates that the values are not reliable due to a
possible power surge or power failure that occurred at that time.
Throughput

The Throughput parameters displays radio Ethernet throughput statistics
(excluding TDM traffic), measured on the radio port.
Peak Throughput (bps) is the maximum throughput measured during
the last interval.
Average Throughput (bps) is the average throughput measured during
the last interval.
Throughput Exceed (Seconds) is the number of seconds the throughput
exceeded the threshold (configured in the field below the table) during the
last interval.
reliable.
HighCapNMS

Capacity

The Capacity parameters displays statistics of the Ethernet capacity (including
Ethernet data and overhead bytes) measured on the radio port.
Peak Capacity (bps) is the maximum capacity measured during the last
interval.
Average Capacity (bps) is the average capacity measured during the last
interval.
Capacity Exceed (Seconds) is the number of seconds the throughput
exceeded the threshold (configured in the field below the table) during the
last interval.
reliable.
HighCapNMS

Utilization

The Utilization parameters display statistics of Ethernet utilization (%)
measured on the radio port.
Ethernet utilization is a measurement of actual Ethernet throughput, relative
to the potential Ethernet throughput of the radio (excluding TDM channels).
The Utilization threshold percentage is the utilization threshold percentage
which was specified in the radio unit. Ethernet utilization during the last
interval is displayed as one of five bins: 0-20%, 20-40%, 40-60%, 60-80%, 80-
100%.
Range of Peak Utilization (%) is the maximum utilization measured
during the last interval.
Range of Average Utilization (%) is the average utilization measured
during the last interval.
Utilization Exceed (Seconds) is the number of seconds the value
exceeded the threshold during the last interval.
reliable.

HighCapNMS

Interface performance reports
The Interface performance report shows performance measurements for line
(E1 / DS1/ STM-1 / OC-3) interfaces.

Date records the time that the data was polled.
UAS is the Unavailable Seconds value of the current interval. The value can
be between 0 and 900 seconds (15 minutes).
ES is the number of seconds during which errors occurred.
SES is the number of severely errored seconds. . Sever errors lasting
longer than 10 seconds are recorded as Unavailable Seconds (UAS).
BBE is the number of background block errors.
The Integrity column indicates whether the values received at that time
and date are reliable.
HighCapNMS

TDM trail performance report
The TDM trail performance reports shows Bit Error Rate (BER)
measurements for a trail. If TDM trail path protection is enabled, the system
performs measurement on both the primary and secondary paths.

Date records the time that the data was polled.
UAS is the Unavailable Seconds value of the current interval. The value can
be between 0 and 900 seconds (15 minutes).
ES is the number of seconds during which errors occurred.
SES is the number of severely errored seconds. . Sever errors lasting
longer than 10 seconds are recorded as Unavailable Seconds (UAS).
BBE is the number of background block errors.
Number of switches indicates the number of protected switches.
Active path count indicates the number of active paths.
The Integrity column indicates whether the values received at that time
and date are reliable.
HighCapNMS

3.14.1.3 Inventory reports
In-band reports
In-band management uses the network management software to send
management packets through the same network it is managing.

IP address - displays the IP address of the network element.
The IP address of the shelf is the address of the main unit in it. For 1+1
units, the shelf will have two IP addresses (the addresses of each of the
main units) and it should be managed via the active unit. However, if a
floating IP address is used, the shelf should be managed via the floating
IP address.
Slot number indicates the slot number of the interface.
IDUs in such a shelf get each a slot ID indicating their position: slot 1
is the lowest IDU and 6 is the highest
Name indicates the slots system name.
In-band status indicates the management type, either In-band or Out-of-
band.
Element type indicates the type of network element.
Channel indicates user channel availability.
TTL displays the Reply TTL hop number
Subnet address displays the IP address of the subnet.
Subnet mask Displays the subnet mask string describing the network
and host addresses.
Network ID shows the TCP/IP address used to identify the subnet.
HighCapNMS

Interface reports
The Interface report presents data polled from network interfaces.

IP address.
Slot displays the number of enabled interfaces out of the total number of
interfaces.
Interfaces indicates the names of available interfaces.
Wayside interface reports if the connector type is RJ-45.
Wayside admin indicates whether the wayside channel is enabled or
disabled.
HighCapNMS

Available interfaces report
The Available interfaces report presents the location and availability of
network element radio interfaces.

IP address.
Product type indicates the network element type.
Is radio interface available indicates whether or not radio interface is
available. A radio interface is considered disabled if
The Radio Admin state is set to Disable
A reset was performed, and the operational state is Down.
The local-remote status is unavailable for the interface.
A radio interface is considered enabled if
The RadioAdmin state was set to Disable, but no reset was performed.
Is non-radio interface available indicates availability of non-radio
interface.
HighCapNMS

Interface availability reports

IP address.
Slot label Displays the name of the slot unit across the radio link.
Radio Displays the number of enabled radio interfaces out of the total
number available.
E1/DS1 Displays the number of enabled E1 and DS1 interfaces out of the
total number available.
STM-1 / OC-3 Displays the number of enabled STM-1 and OC-3
interfaces out of the total number available.
Optical GE Indicates the number of enabled optical GE interfaces out of
the total number available.
Electrical GE Indicates the number of enabled electrical GE interfaces
out of the total number available.
Combo GE Indicates the number of enabled combo GE interfaces out of
FE Indicates the number of enabled FE ports out of the total number
available.
PWE3 GE Indicates the number of enabled PWE3 GE ports out of the
total number available.
Clock interface Indicates the number of enabled clock interfaces out of
UC Indicates the number of enabled UC interfaces out of the total number
available.
HighCapNMS

EoW Indicates the number of Engineering Order Wire (EoW) interfaces
out of the total number available.
WS Indicates the number of enabled wayside Ethernet interfaces out of
Licensing reports
The Licensing report provides data about which licenses are enabled for each
network element.

IP address.
License type indicates the license type.
License code displays license validity code.
Demo admin indicates if the demo license is enabled or disabled.
License per usage indicates the capacity of the license feature.
Demo timer indicates the remaining validity period of the license for
trial or demo licenses.
Feature indicates which feature set is enabled by the license.
License indicates the license status.
Usage configuration indicates if the feature is allowed or not allowed
for the given license.
License model indicates the license model for allowed features.
HighCapNMS

Link reports
The Link report provides data about links, such as transmit and receive
frequencies and slot number locations.

IP address.
Transmit frequency indicates the transmit frequency for that end of the
link.
Receive frequency indicates the receive frequency for that end of the
link.
ATPC indicates whether the link is using Ad hoc TCP.
Link reports are unavailable for disabled radio interfaces.
HighCapNMS

Neighbors reports
The Neighbors report provides data about the IP addresses of the units on a
link.

IP address.
Interface indicates the interface type and the port number.
Neighbor IP address indicates the IP address of the neighboring
interface.
Neighbor name indicates the system name for the neighboring interface
slot.
Neighbor interface indicates the interface type and the port number for
the neighboring interface.
Neighbor slot number indicates the slot number of the neighboring
interface, or the two slot numbers for a protected unit.
Config manually indicates whether the link can be configured manually.
This option is currently unavailable for Ethernet link types.
Neighbor reports are unavailable for disabled radio interfaces.
Network element reports
The Network element report provides status information and data about
indoor units.
HighCapNMS

IP address.
Status indicates the availability of the network element: reachable,
unreachable, or uninvestigated.
Last reachable indicates the last reachable date and time of the network
element.
Applicable only for network elements with a status state of Reachable
or Unreachable.
Name indicates the network elements User defined name.
System name indicates the system name of the network element.
System contact indicates the network user responsible for the network
element.
System location indicates the physical location of the network element.
Product type indicates the type of network element.
Network element visibility reports
The Network element visibility report provides detailed information about the
current availability and status of indoor units.

IP address.
Slot Number If the NE is an IDU R1, or an NE that is not part of the IDU
series, the slot number will be N/A.
Slot Label The user-configured slot label. If no slot label has been
configured, this field is empty.
HighCapNMS

Slot Status Indicates the availability of the network element in the slot:
reachable, unreachable, or uninvestigated.
Product type indicates the type of network element.
System name indicates the system name of the network element.
System location indicates the physical location of the network element.
Protection reports
The Protection report provides data about protected configurations in the
network.
Note that for protected IDU-G series network elements HighCapNMS presents
alarms and report data for the IP address of the active slot. Only protected
slots are included in the protection reports.

IP address.
IP displays either:
The IP address of the network elements Slot 1, which acts as the
primary IP address for a protected unit.
The floating IP address for the network element, if it is using floating IP
instead of a permanent IP address.
Mate IP displays the IP address of the secondary slot.
HighCapNMS

For slots enabled with 2+2, protection, the slot number will be the slot
of the primary slot (Slot 1, 3, or 5).
Type indicates the type of protection: 1+1 HSB, 2+2 HSB, or 2+0 HSB
(Multi radio with line protection).
Mode indicates the admin state of the protection, either Active or Standby.
Radio reports
Radio reports display inventory information of outdoor units.

HighCapNMS

IP address.
ODU type displays the product type of the ODU.
Modem type indicates the type of modem in use.
Transmit frequency (MHz) indicates the transmit frequency measured
during the interval.
Receive frequency (MHz) indicates the receive frequency measured
during the interval.
Min transmit frequency (MHz) indicates the minimum received level
measured during the interval.
Max transmit frequency (MHz) indicates the maximum received level
measured during the interval.
Channel spacing (MHz) indicates the allocated bandwidth for the RF
channel
Transmit level indicates the average transmit level for the measured
interval.
ATPC indicates the Automatic Transmit Power Control status (enabled or
disabled).
ATPC reference level indicates the Received Signal Level value.
Link ID displays the link ID.
Admin state reports whether the radio interface is Enabled or Disabled.
Operational status indicates whether the radio is operational.
MultiRadio admin indicates the status of the multiradio unit (enabled
or disabled).
Serial number reports
The Serial numbers report shows the serial number for each network element.
HighCapNMS


IP address.
Slot indicates the name of the slot across the unit.
Type indicates the unit type: IDU or RFU.
Serial# indicates the device ID.
Part# indicates the part number of the interface.
HighCapNMS

Slot population reports
The Slot population report shows the IP address of each slot's IDU and its
availability.

IP address.
Slot 1-6 indicates the availability status for each slot in the shelf.
HighCapNMS

Versions reports
The Versions report provides data about which software and firmware
versions are installed on network elements.
Double-clicking a line in a versions report opens a page with additional
information about the version type.

IP address.
Slot indicates the name of the main slot.
Type indicates the product type.
Version indicates the installed software version on the unit.
Post reset version indicates the updated version after a software
upgrade.
HighCapNMS

xSTP reports
The xSTP report provides data about active and inactive xSTP paths.

IP address.
Admin state indicates if the port is Enabled or Disabled.
Bridge ID indicates the MAC address of the bridge in the active IDU.
Is edge indicates whether the port is a service access point on the ring,
or is functioning as one of the ring edges.
Operational state indicates if the ports operational status is active (UP)
or inactive (DOWN).
Port number indicates which port has been enabled for RSTP traffic.
Bridge priority indicates the specific (ACM?) priority for this interface.
Designated path cost indicates the path cost for this port. The lower the
value the more likely that port is used.
Role indicates the role of the bridge: Root or Designated.
Root ID - The MAC address of the root bridge.
Root Path Cost - The cost of the path from the active IDU to the root
bridge.
State indicates whether the port state is Disable, Forwarding, Learning,
or Blocking.
HighCapNMS

xSTP protocol indicates which STP protocol is in use: standard RSTP or
Ring RSTP. If RSTP has been configured but disabled, the xSTP protocol
status will be Disabled.
3.14.1.4 Logs
Alarm log

IP indicates the IP address of the unit where the alarm was raised
Slot number indicates the slot number where the alarm was raised.
Name indicates the system name of the unit where the alarm was raised.
Severity indicates the severity of the alarm.
Ack indicates whether the alarm has been acknowledged: True or False.
Time indicates the raise time of the alarm.
Status indicates the status of the alarm: Raised or Cleared.
Module indicates the type of interface where the alarm was raised.
Description provides a one sentence summary of the alarm. Details
about each alarm, including its probable causes and suggested corrected
actions, are available in a separate window.
Alarm severity
Alarm severity is classified into seven categories.
Alarm severity is represented in the client GUI by colors that correspond
to the alarm severity classes. The color of a map entity indicates its most
severe alarm:
Severity Clear Event Warning Minor Major Critical Node down
Weight 0 1 3 7 15 31 63
Color Green Blue Yellow Orange Dark orange Red Grey
HighCapNMS

User actions log

Action time indicates the date and time of the logged user action.
Application indicates the application where the action was performed.
User name indicates the username of the user who performed the
action.
Connected from indicates the IP address of the user who performed the
action.
Description describes the feature set of the logged action, using the
system command name to describe which action was performed. For
example, Topology, add network element. When available, the log will
add details about the action. Using Add network element as an example,
logged details could include the type of network element that was added
and its IP address.
List of optional user actions for the users actions log report
Operation area Details
Alarms Acknowledge
Alarms Delete alarm from current alarm
Alarms Delete alarm from current alarm
Alarms Delete Alarms
Alarms Hide
Alarms Note
Alarms Show
Configuration Broadcast Run
Configuration Download Run
Connected Users Disconnect User
HighCapNMS

Connected Users Display Message
Discover Node Run
Dynamic Security Configuration
Edit EVC Configuration
Import Data Run
Login Login HighCapNMS Client
Network Auto Discovery Discover
Topology Remove NE
Run Scheduled Task Run
Software Download Data
Software Download Delete
Software Download Scheduled
Software Download Status
Topology Add Group Element
Topology Add Link
Topology Add Network Element
Topology Add Symbol
Topology Add Text
Topology Configure Group
Topology Configure Link
Topology Configure Network Element
Topology Configure Symbol
Topology Configure Text
Topology Delete Link
Topology Delete Topology Element
Topology Move Element
Topology Relocate Topology Element
Trail Advanced Trail Configuration
Trail Create Trail
Trail Delete Trail
Trail East West Validation
Trail Edit Trail
Trail Fix Trail
HighCapNMS

Trail LoopBack
Trail Switch Trail Active Path
Triggers Configuration
Logout Logout HighCapNMS Client
3.14.1.5 Service lists
Trail lists
Trail ID and Trail description are trail identifiers.
Most severe alarm indicates the severity level of the most severe alarm
on the trail.
Admin state indicates whether the selected trail is Operational or
Reserved.
Operational state indicates whether the trails operational status is
Operational or Reserved.
ACM priority indicates High or Low priority for which trails will be
dropped first from radio links when bandwidth is reduced.
Type indicates the type of trail protection. Protected trails allow traffic
from two different paths, with different methods of allocating bandwidth.
Dual ended protected trails have three end points, with outgoing traffic is
split between two alternative endpoints.
Unprotected indicates a point-to-point trail.
Protected 1+1 indicates permanent use of bandwidth for both paths.
In a protected 1+1 configuration, instead of a single IP address for both
units, the node has two IP addresses, those of each of the main units.
The IP address of the active main unit is used to manage the node.
Protected ABR indicates protection with dynamic allocation of
bandwidth.
Protected ABR is a unique network level method of dynamic
capacity allocation for TDM and Ethernet flows. By using the
bidirectional capabilities of the ring, TDM-based information is
transmitted in one direction and unused protection capacity is
allocated for Ethernet traffic, making better use of bandwidth and
effectively doubling the capacity of wireless rings.
Protected 1+1 DE indicates dual ended protection with permanent
allocation of bandwidth.
Protected ABR DE indicates dual ended protection with dynamic
allocation of bandwidth.
End point parameters
HighCapNMS

IP address.
EVC lists
EVC ID and EVC description display are service identifiers.
Transport VLAN type indicates whether the transport VLAN is configured
with C-VLAN or S-VLAN.
EVC type: E-LINE or E-LAN
E-LINE indicates a service with only two Service Access Points (SAPs).
E-LAN indicates a service with more than two SAPs.
Admin state indicates whether the service is Enabled or Disabled.
Operational state can be:
Unknown The operational state will be changed to Unknown if any of
the network elements along the service become unreachable by the
NMS.
Up The service operational state will be Up if there is a connection
between the SAP, all service ports are Enabled (admin state) and UP
(operational state), and the VLAN is configured correctly for all the
ports along the service.
Up unprotected When there is more than one path available between
two SAPs and the service is configured on an RSTP ring, the
Operational state of the service will be Unknown when there is only
one path available for the service.
Down If the operational state of any of the service ports is Down and
causes a lack of connection between two or more SAPs, the operational
state of the service will also be down.
Partially down In an E-LAN service, if there is no connection between
a pair of 2 SAPs, but some of the SAPs are still connected, the
operational state of the service will be Partially down.
Broken service If the NMS finds the same service ID in two subnets
that are not connected, the operational state of the service will be
Broken service.
Partially configured A service can be set to only Partially configured if
the Service succeeded, but with specific fail points.
SAP parameters
HighCapNMS

main units) and should be managed via the active unit. However, if a
IP address.
VLAN encapsulation type can be C-VID or Untagged for Managed
switches, and All-to-one or S-VID for Metro switches.
Filtering the Ethernet Service (EVC) and TDM Trail lists
Users can filter the lists of Ethernet services and TDM trails according to any
of the EVC or trail properties. Filters can be used to identify list entries that
either match, or do not match, the filter criteria.
Users can configure which columns are displayed in these lists. By default, all
columns appear except the Description column. The list can be filtered
according to the Description, as well as any of the other columns, even if the
Description column is not displayed.
HighCapNMS

4. HighCapNMS Network Support
4.1 Supported Network Elements
4.1.1 Evolution XPAND IP+
Series
HW
version
Marketing version Software version
NMS support
level
Min Max Min Max
XPAND IP+ R1 I6.0 I6.3.2 1.4.5.2*
2.7.12

2.9.26

XPAND IP+ R2 I6.5ca1 I7.0 3.0.97*
6.6.0.0.1.40
7.0.0.0.0.15
XPAND IP+ R3 I6.7 I7.0 6.7.0.0.0.93 7.0.0.0.0.15
4.1.2 AGG-Node-N
Marketing
version
Software version Remarks
7.0 7.0.0.0.0.76
4.1.3 AODC-C
Marketing
version
Software version Remarks
7.0 7.0.0.0.0

4.1.4 HighCapRadio Multi-Rate family
Product
Marketing
version
Software version
1500
1528
1500A I5.28
1500AL I-528f
1528A
1500P (I5, S5,
G5)
4.95 4.95s19
HighCapNMS

Product
Marketing
version
Software version
1500P (I5, S5,
S5 Quad G5)
5.10 5.10n1
1500R S6.0 SFD_6.00c3.sfd
1500R S6.5 SFD_6.50e2.sfd
1500R S6.6 SFD_6.60c3.sfd
1500R Quad S6.6 SFD_6.60c3.sfd
3200T T5.0 SFD_5.00a71a
640P
4.1.5 HighCapRadio 2000/4800 family
Product
Marketing
version
Software version
FA2000 2.5 2.5.00_b2650
FA4800 1.9.35 1.9.35_b1845
4.1.6 3rd party supported elements
Manufacturer Product Software version
ECI BG-20B V12.0.45
Telco T-Marc 3208SH 2.4.R3.1.1

4.2 Supported protocols
SNMP V1 / V2C / V3
CLI / SSH-2
HTTP / HTTPS
FTP / SFTP
HighCapNMS

5. HighCapNMS license information
5.1 Introduction
Licensed based scalability allows you to add features and capacity as needed.
When the user installs the HighCapNMS server for the first time, it is installed
with a demo license that will enable 30 days of work with all features
enabled, and no limitation on the number of managed NEs.
To manage more than 20 NEs, an additional license should be purchased from
HighCapRadio.
HighCapNMS software is available on a CD that will be delivered to the client,
or downloaded via HighCapRadio's customer support FTP.
A network element is counted according to the number of IDUs.
For example:
IDU-G with 6 slots is counted as 6 in the license.
3200T is counted as one IDU in the license.
5.2 License requirements
Description Model #
Quantity per
server
Quantity for redundant servers
solution
HighCapNMS Software
+ License for 20 network
elements
HighCapNMS NMS 1 2
License for 21-100
network elements, per
NE
PV_21-100_NE 80 160
License for 101-500
network elements: per
NE
PV_101-500_NE 30 60
License for redundant
HighCapNMS support
PV_Redundant_Support 1 2
TDM trails PV_TDM_Provisioning 1 2
Ethernet services PV_Ethernet_Provisioning 1 2
mySQL Enterprise
Server 5.1
MySQL-License-PV 1 2
HighCapNMS

5.3 License components
HighCapNMS uses a capacity based licensing system.
The built-in license can manage up to 20 elements. Additional licenses can be
purchased to align with the size and needs of network. Customers should
purchase the HighCapNMS software and the appropriate license based on the
number of managed network elements (number of IDUs).
The following license components are limited, based on the purchase order.
Feature Description
Managed network element limit Limits the number of managed elements (number IDUs). There is
no limit on the number of groups or symbols the user can add.
Feature set and enabled features Limits the features enabled by HighCapNMS. Two feature sets
are currently defined (default is Pro):
Pro All features are enabled, except the following which require a
specific license.
Enabled features Specific proposal for the following features that require a specific
license:
NSN NetAct interface
Redundant server support
End to end TDM trails provisioning
Ethernet services
Expiry date No expiry (permanent license), or expiry date of license (for
trials/demos)
5.3.1 Redundancy server support
Redundancy servers requires the same license including Redundancy in both
primary and secondary server.
5.3.2 TDM trail license requirements
The TDM service requires an additional license. When the license isnt
detected, users will not be able to create new TDM trails, view or edit TDM
trail lists, modify trail properties, or access TDM trail performance reports. In
addition, in the absence of a valid TDM trail license, trail alarms will not be
raised.
5.3.3 Ethernet services license requirements
Ethernet services require an additional license. When the license is not
detected, users will not be able to create new EVC, view or edit EVC, modify
EVC properties, or access EVCs. The Ethernet services license also includes the
ability to work with CFM.
HighCapNMS

5.4 Licensing MySQL
MySQL is provided as part of the HighCapNMS installation package, but comes
with its own license, which must be purchased separately.
HighCapRadio HighCapNMS SW uses internal MySQL SW database. The
following Item should be purchased on every new server HW.
Marketing model Item description Part number
MYSQL-LICENSE MySQL software License for Windows/Unix
platform.
SL-0003-X
You must update your HighCapNMS dealer or distributer with details
of every upgraded server:
Customer details: Final customer, integrator, country, and region.
Server details: operating system and serial number.
License details: Host ID and maximum network elements included in the
license.
General details: Installed by, installation date, and any additional notes.
5.5 Temporary demo license
When the user installs the HighCapNMS server for the first time, it is installed
with a demo license that will enable 30 days of work with all features
enabled, and no limitation on the number of managed NEs.
HighCapNMS will provide 14 days of notification before the license expires.
The notification will appear upon each login to remind the customer to contact
HighCapRadio to obtain a permanent license.
If a permanent license was not obtained within 30 days, the demo license will
expire and the user will no longer be able to log in. An error message will
advise the customer to contact HighCapRadio to obtain a permanent license.
The demo license will be activated once per station. Uninstalling and
reinstalling the HighCapNMS software will not grant a new demo license.
5.6 Obtaining a permanent license
To obtain a permanent HighCapNMS license:
1 Install HighCapNMS and restart the machine.
2 Start HighCapNMS Client and select Help > About.
3 Write down the Host ID number.
4 Contact HighCapRadio Networks customer support to report the Host ID
number and request your license file.
5 Activate the new license
Copy the license file that you receive from customer support to the
HighCapNMS/config directory
- Windows: \HighCapNMS\config
- Solaris: /opt/HighCapNMS/config
6 Restart the server.
7 Start HighCapNMS Client.
HighCapNMS

8 Select Help > About to confirm the updated license information.
A permanent HighCapNMS license will be issued when the relevant order is
processed by HighCapRadio, after HighCapNMS is installed on the customer
station.
Once an order is placed and processed, the customer must send the
"HighCapNMS License Request Form" to HighCapRadio Customer Support,
with all the relevant information.
HighCapRadio Customer Support will verify that the necessary information
was provided, and that the order was properly made. The license will then be
generated and emailed to the customer, together with license installation
instructions.
An invoice will be issued when the license is generated.
5.7 License configuration recommendations
HighCapNMS software can be purchased from HighCapRadio. The basic
software item consists a built-in license for 20 network elements (NEs),
meaning it can manage up to 20 managed elements.
To manage more than 20 NEs, additional licenses should be purchased from
HighCapRadio.
Customers should purchase the HighCapNMS software and the appropriate
license based on the number of managed network elements (the number of
IDUs).
It is possible (and preferable) to order from HighCapRadio the NMS servers
including the HighCapNMS/HCR NMS SW installation as a package.
Description Model # Part #
HighCapNMS Software (Win/Unix+ License for 20 NEs HighCapNMS NMS SP-0028-x*
License for 21-100 NEs: per NE PV_21-100_NE SR-0038-0
License for 1001 or more NEs: per NE PV_>1000_NE SR-0041-0
SP-0028-x- whereby "x" represents the latest released version of HighCapNMS
5.8 License configuration examples
Management of 130 NEs
Description Model # Quantity
HighCapNMS Software + License for 20
NEs
HighCapNMS NMS 1
License for 21-100 NEs: per NE PV_21-100_NE 80
HighCapNMS

Upgrade of existing license from 60 NEs to 130 NEs
Description Model # Quantity
Management of 130 NEs, redundant servers configuration
Description Model #
Quantity per
server
Quantity for
redundant
servers solution
HighCapNMS
Software + License for
20 NEs
HighCapNMS NMS 1 2
License for 21-100
NEs: per NE
PV_21-100_NE 80 160
License for 101-500
NEs: per NE
PV_101-500_NE 30 60
License for redundant
HighCapNMS support
PV_Redundant_Support 1 2
5.9 HighCapNMS license request form
Please fill in this form and email it to support@HighCapRadio.com.
Field
Company Name
HighCapRadio Order #
Host ID
User Name
(full name of primary customer contact)

Email Address
(email address of the primary contact to
which the license file will be sent)

Managed NEs Limit
(according to the order placed)

Feature Set - Pro
Enabled Features
(according to the order placed)
- NSN NetAct interface
- Redundancy server
- HighCapNMS software, upgrade only
- End to End TDM trail provisioning
Expiration Date
(relevant for demo/trials only)
- Permanent license (no expiry)
- Expiration date:
HighCapNMS

Field
Remarks
(additional information or special
request)

* Managed NEs limit means the total number of IDUs in the system.
For example an IDU-G Node with 6 IDUs is counted as 6 managed elements,
while 3200T is counted as one IDU.
HighCapNMS

6. Hardware capacity recommendations
Number of managed
network elements
Number of parallel
connected clients
Server (Processor) Memory Hard drive
Up to 5,000 network
elements
Up to 10 NMS Clients Oracle T3 (SPARC) /
Dell PowerEdge T110 II
(Win2008 Server)
8G 300 GB
Up to 7,000 network
elements
Up to 20 NMS Clients Oracle T3 (SPARC) 16G 600 GB
Up to 7,000 network
elements
Up to 40 NMS Clients Oracle T3 (SPARC) 32G 600 GB

6.1 Unix server capacity examples
UNIX servers are supplied with HighCapNMS NMS already installed.
HighCapNMS supports Solaris 10 operation system for Oracle T3 servers.
HighCapRadio doesnt support UNIX servers that were not purchased through
HighCapRadio and were not installed by HighCapRadio.
All NMS software licenses and MySQL database software should be purchased
separately.
Oracle server hardware is delivered with one year basic warranty.
HP server hardware is delivered with three years basic warranty.
Annual warranty extensions are available.
Number of
managed
network
elements
Number of
parallel
connected
clients
Server Memory Hard drive Marketing Model
Up to 5,000
network
elements
Up to 10 NMS
clients
Oracle T3 8G 300 GB HighCap-SW&HW,Med,Solaris
Up to 7,000
network
elements
Up to 20 NMS
clients
Oracle T3 16G 600 GB HighCap-SW&HW,High,Solaris
Up to 7,000
network
elements
Up to 40 NMS
clients
Oracle T3 32G 600 GB HighCap-SW&HW,UltraHigh,Solaris

HighCapNMS

UNIX Server, Network Elements <5,000, up to 10 clients
Marketing model Item description
HighCap-SW&HW,Med,Solaris
Oracle T3-1 HW, Solaris OS with basic HighCap Radio SW license (20
NEs).
Supported configuration - up to 5K NEs and up to 10 clients

UNIX Server, Network Elements <7,000, up to 20 clients
HighCap-SW&HW,High,Solaris
NEs).

UNIX server, network elements <7,000, up to 40 clients
HighCap-SW&HW,UltraHigh,Solaris
NEs).

6.2 Windows server capacity recommendations
Windows server capacity recommendations
Unlike UNIX servers, Windows PCs can be purchased separately from the with
HighCapNMS software. Installation can be done by the customer.
All NMS software licenses and MySQL database software should be purchased
separately.
Windows Server, Network Elements <5,000, up to 10 clients
PV-Win-HW-Medium
Dell T110 II HW, Windows 2008 server OS
Windows PC, Network Elements <600, up to 3 clients
HighCapNMS can be installed on any up to date Windows PC with minimum
requirements of 2GB memory. Maximum of 2-3 parallel NMS clients usage is
recommended with this basic configuration.
HighCapNMS

7. Compatibility matrix

IDU Version HighCapNMS Version
2.35w 6.01e N6.1g N6.5r N6.6.0.0.1 N6.6.0.0.2 N6.6.0.1.2 N6.6.1.5.1 N6.7.0.2.0 N6.8.0.1.0 N6.9.0.1.1 N7.0.0.1.0
Evolution
METRO
10B00 N N N N N N N N N Y Y Y
Evolution
XPAND
10B00 N N N N N N N N N Y Y Y
Evolution
XPAND IP
R4B00 N N N N N N N N N Y Y Y
R6A00 N N N N N N N N N N N Y
AGG-NODE-N
1RU
7.0.0.0.0.76 N N N N N N N N N N N Y
AGG-NODE-N
1RU
T7.2.0.0.0.30 N N N N N N N N N N N Y
AGG-NODE-N
2RU
7.0.0.0.0.76 N N N N N N N N N N N Y
AGG-NODE-N
2RU
T7.2.0.0.0.30 N N N N N N N N N N N Y
AODC-C 7.0.0.0.0 N N N N N N N N N N N Y

HighCapRadioNMS Technical Description - N7.0.0.1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HighCapRadioNMS Technical Description - N7.0.0.1.0

Uploaded by

Copyright:

Available Formats

Copyright 2013. All rights reserved.

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description

N7.0 Technical Description