polyview user guide n6.8

PolyView N6.8 NMS User Guide

DOC-00008492 (Rev A)

March 2012

Copyright 2012 Ceragon Networks Ltd. All rights reserved. www.ceragon.com

Notice This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.

Registered Trademarks Ceragon Networks is a registered trademark of Ceragon Networks Ltd. FibeAir is a registered trademark of Ceragon Networks Ltd. CeraView is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

Trademarks CeraMap, ConfigAir, PolyView, EncryptAir, and CeraMon are trademarks of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

Statement of Conditions The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

Open Source Statement The Product may use open source software, among them O/S software released under the GPL or GPL alike license ("GPL License"). Inasmuch that such software is being used, it is released under the GPL License, accordingly. Some software might have changed. The complete list of the software being used in this product including their respective license and the aforementioned public available changes is accessible on http://www.gnu.org/licenses/.

Information to User Any changes or modifications of equipment not expressly approved by the manufacturer could void the users authority to operate the equipment and the warranty for such equipment.

Contents

1 PolyView system overview ..................................................................................................1 2 Getting started ......................................................................................................................2

2.1 Logging in to the NMS ........................................................................................... 2 2.2 Launching CeraMap .............................................................................................. 2 2.3 Preparing the network for system management .................................................... 3

3 Designing network topology maps ................................................................................... 36 3.1 Configuring map display settings ......................................................................... 36 3.2 Adding network elements .................................................................................... 38 3.3 Adding symbols to network topology maps .......................................................... 48 3.4 Adding labels to network elements ...................................................................... 50 3.5 Creating groups of network elements .................................................................. 51 3.6 Creating links between map entities .................................................................... 53 3.7 Moving network elements .................................................................................... 55 3.8 Modifying map entities ......................................................................................... 55 3.9 Deleting map entities ........................................................................................... 56 3.10 Backing up network topology data ....................................................................... 56

4 Managing mapped devices ................................................................................................ 58 4.1 Global administration of network elements .......................................................... 58 4.2 Topology tree ....................................................................................................... 58 4.3 Discover node ...................................................................................................... 58 4.4 Poll node .............................................................................................................. 59 4.5 Testing for connectivity to network elements ....................................................... 61 4.6 Finding network elements .................................................................................... 62 4.7 Launching a network elements EMS................................................................... 62 4.8 Working with multi-radio network elements ......................................................... 63

5 Fault management .............................................................................................................. 64 5.1 Configuring alarm settings ................................................................................... 64 5.2 Viewing alarms .................................................................................................... 65 5.3 Managing alarms ................................................................................................. 69 5.4 Configuring alarm triggers ................................................................................... 72 5.5 Trap forwarding.................................................................................................... 86

6 Configuration management ............................................................................................... 91 6.1 Broadcasting network element configurations ..................................................... 91 6.2 Software and configuration archive file locations ............................................... 116 6.3 Backing up and restoring configuration archive files .......................................... 116 6.4 Downloading and installing software versions ................................................... 119

7 Performance management .............................................................................................. 121 7.1 Configuring report settings ................................................................................. 121 7.2 Generating performance reports ........................................................................ 123 7.3 Performance report examples ........................................................................... 125 7.4 Generating inventory reports ............................................................................. 134 7.5 Inventory report examples ................................................................................. 135 7.6 Link utilization report .......................................................................................... 142 7.7 Customizing report data presentation ................................................................ 143

8 End-to-end traffic service management ......................................................................... 149 8.1 Service view ...................................................................................................... 149 8.2 End-to-end Ethernet service management ........................................................ 149

8.3 End-to-end TDM trail management.................................................................... 169 9 Security management ...................................................................................................... 186

9.1 Monitoring and managing user actions .............................................................. 186 10 System administration ..................................................................................................... 189

10.1 Scheduling tasks................................................................................................ 189 10.2 Database management ..................................................................................... 190 10.3 System maintenance ......................................................................................... 192

11 Reference .......................................................................................................................... 202 11.1 CeraMap keyboard shortcuts ............................................................................. 202 11.2 Alarms ............................................................................................................... 202 11.3 Command line interface (CLI) ............................................................................ 211 11.4 CLI report interface ............................................................................................ 212 11.5 PolyView northbound interface .......................................................................... 223 11.6 Server redundancy ............................................................................................ 230 11.7 SNMP MIB support ............................................................................................ 236 11.8 PolyView support for floating IP addresses ....................................................... 239 11.9 Reports .............................................................................................................. 242

NMS User Guide PolyView N6.8 PolyView system overview

Page 1 of 271

1 PolyView system overview

PolyView is a Network Management System (NMS) designed for managing large scale

wireless backhaul networks.

Optimized for centralized operation and maintenance of a complete network, PolyView offers

users a comprehensive set of management functions to simplify network management work.

CeraMap, PolyViews client interface provides centralized, GUI based access to all network

management functionality.

End-to-end traffic service management

PolyView 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

PolyView 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

PolyView simplifies network elements configuration management, with centralized

configuration file backup and rollback. PolyViews 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, CeraMaps 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 Ceragon network

element interfaces and links in the system. Performance reports provide information about

radio, interface, and trail performance.

Network security

PolyView 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.

NMS User Guide PolyView N6.8 Getting started

Page 2 of 271

2 Getting started

2.1 Logging in to the NMS

To start PolyView : Change to the PolyView directory and run pvstart.

2.2 Launching CeraMap

To launch CeraMap:

1. Run pvmap, select Start > Programs > PolyView > CeraMap or double click the

desktop's CeraMap icon.

2. Enter your user name and password, and click OK to login.


Page 3 of 271

2.3 Preparing the network for system management

2.3.1 Server configuration

2.3.1.1 Configuring server memory usage

To configure server memory usage:

1. Open the PolyView server config application.

Select Start > Programs > PolyView > PolyView Server Config or in CeraMap,

select Settings > Server configuration from the CeraMap menu.

2. Select the Advanced tab.


Page 4 of 271

3. Specify the maximum number of network element polling tasks that the server can run

simultaneously.

In the Max concurrent tasks field, specify between 6-100 simultaneous tasks.

4. Specify the maximum amount of memory the application can allocate.

In the Max memory allocation field, specify how many MB of memory to allocate

to the application.

The minimum is 256 MB, the maximum is 8192 MB.

For large scale networks, increase the Max Memory Allocation size to ~1/3 the

total memory in the computer. For example, if the computer is fitted with 2GB

memory, set this value to around 700MB.

5. Specify the minimal amount of free disk space.

In the Threshold of free disk space field, specify the low disk space threshold

below which an alarm will be generated.

6. Specify the system load threshold.

In the Threshold of average CPU load field, allow up to 100 processes to be

waiting for CPU before generating an alarm.

7. Click Apply.

8. Click Close to exit the PolyView server config utility.

2.3.1.2 Configuring the SMTP mail server

To configure the SMTP mail server:





Page 5 of 271

2. Select the General tab.

3. Specify the IP address or hostname of the email server.

In the SMTP (email) server address field, specify the mail servers IP address.

4. Click Apply.


2.3.1.3 Configuring the server time zone

To configure the application time zone:





Page 6 of 271


3. Specify the time zone to be used.

4. In the Application time zone field, specify the servers time zone.

You only need to specify the zone if the application time is not calculated

correctly. If the time zone is already configured correctly, you can leave this field

empty.

The format is GMT+/- with no spaces between the parameters, for

example: GMT+2.

5. Click Apply to save changes.

6. Click Close to exit the PolyView Server config utility.

2.3.1.4 Restoring server configuration defaults

To restore PolyView server defaults:


Run pvconfig, select Start > Programs > PolyView > PolyView Server Config

or in CeraMap, select Settings > Server configuration from the CeraMap menu.

2. Click Restore defaults to reset configuration parameters to their original values.




Page 7 of 271

2.3.2 Proxy configuration

2.3.2.1 Configuring ENM and HTTP proxy settings

To configure the ENM and HTTP proxy settings:





3. Allow the NMS to act as a proxy server when the ENM doesn't have direct access to a

network element.

In the Enable ENM proxy field, select True.

Note that to enable this option, the ENM must be capable of working via a proxy.

4. Allow the NMS to act as a HTTPS proxy server when the web browser doesn't have

direct access to a network element.

In the Enable HTTP(S) proxy field, select True.

Note that you must also configure your web browser to recognize PolyView as a

proxy server.

5. Click Apply.



Page 8 of 271

2.3.2.2 Configuring client browser proxy settings

For each browser that will be used to manage network elements:

1. Open a browser window.

2. Select Internet options from the Tools menu.

3. Select the Connections tab.

4. Click LAN Settings.

5. In the Proxy Server area, select Use a proxy server for your LAN.

6. In the address area, specify the address of the machine on which the web proxy

server is installed.

7. For Port, enter 8080 (or a different port number if configured otherwise in the web

proxy server).

2.3.3 File transfer settings

2.3.3.1 Configuring FTP login information

To configure FTP login information:




2. Select the File Transfer tab.


Page 9 of 271

3. Specify the IP address or hostname of the FTP server.

In the FTP server address field, enter the IP address of the FTP server.

4. Specify the FTP server user name and password.

In the FTP server username field, specify the FTP username to be used for

communication with the PolyView server during automatic upgrade of the

CeraMap client software..

In the FTP server password field, specify the FTP password to be used for

communication with the PolyView server during automatic upgrade of the

CeraMap client software..

NOTE: Make sure that the user name and password match the login information on the FTP server.

5. Click Apply.


2.3.3.2 Configuring the FTP protocol

To configure the FTP protocol





3. Specify the file transfer server protocol.

In the FTP server protocol field, choose FTP or SFTP.


Page 10 of 271

4. Click Apply.


2.3.3.3 Configuring TFTP login information

Login information for the TFTP server must match TFTP login information in PolyView.

To configure TFTP login information:





3. Specify the IP address or hostname of the TFTP server.

In the TFTP server address field, enter the IP address of the FTP server.

4. Click Apply.


2.3.3.4 Configuring the TFTP files location

To configure the FTP protocol





Page 11 of 271


3. Specify the path to network element software files.

In the TFTP files location field specify a relative or absolute path to network

element software files.

The folder name cannot contain spaces.

4. Click Apply.


2.3.3.5 Configuring TFTP retries and timeout

To configure TFTP login retries and timeout:





Page 12 of 271


3. Specify how long to block users after reaching the maximum number of failed login

attempts.

In the TFTP timeout field, specify how many seconds to wait before allowing

blocked users to login again.

4. Specify the maximum number of allowed retries before initiating a TFTP timeout.

In the TFTP retries field, specify between 2-7 allowed login attempts before timing

out the user.

5. Click Apply.


2.3.4 Port settings

2.3.4.1 Configuring the TCP port

To configure the servers TCP port:





Page 13 of 271


3. Define which TCP port the server should use to listen to CeraMap clients.

In the NMS server TCP port number field, specify the TCP port number.

4. Click Apply.


To enable TCP communication in a redundant system:

1. Open the client configuration utility.

Select Start > Programs > PolyView > CeraMap Client Config, or select

Settings > Client configuration from the CeraMap menu.


Page 14 of 271

2. Click the Remote Hosts tab.

3. Specify the TCP listening port of the primary server.

In the Primary NMS server TCP port number field, specify the primary TCP

listening port number. The value of this parameter should match the value

configured for the NMS server TCP port number parameter on the primary server.

4. Specify the TCP listening port of the secondary server port.

In the Secondary NMS server TCP port number field, specify the secondary TCP

listening port number. The value of this parameter should match the value

configured for the NMS server TCP port number parameter on the secondary

server.

5. Click Apply.

6. Click Close to exit the CeraMap Client config utility.

2.3.4.2 Configuring the user actions logger port

To configure the user actions logger port:





Page 15 of 271


3. Specify the port number for logging user actions.

In the User actions logger port number field, specify which port to use for logging

user actions.

4. Click Apply.


2.3.4.3 Configuring the ENM proxy port

To configure the ENM proxy port:





Page 16 of 271


3. Specify which PolyView port to use for receiving proxy requests.

In the ENM proxy port number field, specify the ENM proxy port number.

4. Click Apply.


2.3.4.4 Configuring the HTTP proxy port

To configure the HTTP proxy port:





Page 17 of 271


3. Specify which PolyView port to use for receiving HTTP proxy requests.

In the HTTP proxy port number field, specify the HTTP proxy port number.

4. Click Apply.


2.3.4.5 Configuring the trap listening port

To configure the trap listening port:

1. Open the PolyView trap forwarding utility.

Select Start > Programs > PolyView > Trap forwarding config, or select

Settings > Trap forwarding options from the CeraMap menu.


Page 18 of 271


3. Specify the trap listening port.

In the Trap listening port field, specify which port to use for listening to network

element traps.

The standard port is 162. Change this number if it is already being used by

another SNMP service.


5. Click Close to exit the Trap forwarding config utility.

2.3.4.6 Configuring the management alarms port

To configure the management alarms port:






Page 19 of 271

3. Configure the management alarms port.

In the Management alarms port field, specify which port to use for sending

management alarms to the trap forwarding hosts.



2.3.5 Database configuration

2.3.5.1 Configuring access to the MySQL database

The Server works with the MySQL database, which requires a user name and password. This

procedure enables you to define and modify the user name and password to access the

database.

To specify database login parameters:

1. Open the PolyView server security application.

Select Start > Programs > PolyView > PolyView Security or in CeraMap, select

Settings > Security settings.

2. Click the Database parameters tab.

3. Provide a user name and password for access to the database, and click Apply.

2.3.5.2 User action log settings

To configure the User Actions log:





Page 20 of 271


3. Specify how long to keep user action history records.

In the Keep actions history field, configure the server to store user actions for 5-

365 days.

4. Click Apply.


2.3.5.3 PM history settings

To configure the PM history levels:





Page 21 of 271

2. Select the Polling tab.

3. Specify how long to keep performance monitoring reports data in the database.

In the Keep PM history field, configure the server to keep performance monitoring

data for up to 366 days.

4. Click Apply.


2.3.5.4 Alarms history settings

To configure the alarms history levels:




2. Select the Alarms tab.


Page 22 of 271

3. Specify how long to keep alarm log history data in the database.

In the Keep alarms history field, configure the server to keep alarm log history for

between 5-365 days.

Note that alarms that are open (raised) will be kept until they are closed,

regardless of the value you set for this option.

4. Click Apply.


2.3.6 Defining users and groups

To configure users and groups:




2. Right click the Users item to add a new user. You can also copy or import existing

user definitions.

3. Right click the Groups item to add a new group.

4. Open a group and double click the Features item for that group to grant feature by

feature permissions to the group.

5. Configure user password settings.

6. Configure user access rights by assigning users to a specific group for each allowed

subnet.

7. Save user definitions or update user configurations to the server.

2.3.6.1 Adding users

There are three ways to add users to the system: you can add users individually, copy an

existing user configuration, or import user definitions.

To add a new user:




2. Select Edit > Add user or right click the Users item and choose Add user from the

context menu.

3. Enter the new users name and password in the fields at the top of the window.

4. In the Access by subnet area, assign permissions to the user.

5. Click OK to add the new user.


Page 23 of 271

2.3.6.2 Importing user definitions

To import user definitions:




2. Select File > Import users to import existing user definitions from a file.

2.3.6.3 Copying an existing user

To copy user definitions:




2. Expand the Users list.

3. Right click the user you wish to copy and select Copy User from the context menu.

4. Enter the new users name and password, and click OK.

A new user will be created with the same access rights as the user you chose to copy.

2.3.6.4 Deleting users

To delete a user:




2. Expand the Users list, and right click the name of a user you want to work with.

3. Select Edit > Delete user or right click the user and select Delete user from the

context menu.

Note that you cannot delete the Admin user.

2.3.6.5 Exporting user definitions

You can export your user configuration for EMS applications or for different PolyView session.


Page 24 of 271

To export user definitions:


Select Start > Programs > PolyView > PolyView Security or in CeraMap, select Settings > Security Settings.

2. Select File > Export users to save user definitions to a file.

2.3.6.6 Adding groups

To add a group:




2. Right click the Groups item and choose either Add read-only group or Add read-

write group from the context menu.

3. In the Enter group name window, enter a name for the new group, and click OK to

add the group.

2.3.6.7 Copying groups

To copy group definitions:




2. Open the Groups item and select a group.

3. Select Edit > Copy group or right click the group instead and chose Copy group

from the context menu.

4. Enter the groups name, and click OK.

A new group will be created with the same permissions as the group you chose to copy.

2.3.6.8 Renaming groups

To rename a group:




2. Open the Groups item and select a group.

3. Select Edit > Configure group or right click the group and chose Configure group


4. Rename the group and click OK.

Note that you cannot rename the Admin group.


Page 25 of 271

2.3.6.9 Deleting groups

To delete a group:




2. Open the Group item and select a group.

3. Select Edit > Delete or right click the group and select Delete group from the context

menu.

Note that you cannot delete the Admin group.

2.3.7 Configuring user access

PolyView 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 using a combination of

user access control features, audit logging, and secured interfaces.

PolyView's security configuration utility allows you to create customized views of the network

for each user.

User access rights determine which parts of the network a user can view, and which operations users can perform.

Permissions are defined for each group.

User access is defined by subnet for a specific group.

To configure user access control:

1. Grant or deny access to groups on a feature by feature basis.

.By default, access to all features is specifically denied, unless changed by the

system administrator.

2. Grant users access to specified subnets.

Access to all UNIX shell level commands from the NMS application will be restricted

according to user and group access rights.

2.3.7.1 Configuring user password settings

To configure user password settings:




2. Select File > Setting to open the password settings configuration window.


Page 26 of 271

3. Check the Users can change their own passwords option to enable password

configuration.

If this setting is not enabled, only the server administrator can change user

passwords.

When this setting is enabled, a Change user password option will be added to the

menus.

4. Check the Users must enter passwords on their first login field to force users to

create a new password when logging in for the first time.

Clear the checkbox to disable this feature.

A password cannot be repeated within the past 5 password changes.

5. In the Password expire time field, specify how often users will be required to change

their passwords.

The default password aging interval is 30 days. This can be changed to anywhere

between 20 and 90 days, or may be disabled.

6. In the Minimum password length field, specify the minimum number of characters for

user passwords.

By default, passwords must be at least 8 characters long.

7. Check the Password must contain at least one non alphabetic character to

enforce password complexity.

New passwords will be checked for strength compliance.

8. Click Apply to save your settings.

2.3.7.2 Changing user passwords

If the PolyView administer has allowed users to change their passwords, the system will

prompt users to change expired passwords.

To change a user password:




2. Select File > Change user password.


Page 27 of 271

3. Enter and confirm the new password.

4. Click Apply to change the password.

PolyView will also try to change the password for the user's allowed element

managers. Note that for this to work, the Users can change their passwords

option must also be enabled in the element manager's security application.

2.3.7.3 Assigning access rights to users

User access rights are determined by both group permissions and subnet.

To assign access rights to users, first create groups with the permissions that you wish to

allow. Then allow the user access to subnets, as users for a specific group.

To assign access rights to a user:




2. Create a group with the permissions that you wish to enable.

3. Open the Users item and select a user.

4. Select Edit > Configure user or right click the user and choose Configure user from

the context menu.

5. In the Access by subnet area, select the subnet that you wish to enable for single

sign-on and click Edit to open the User configuration window.


Page 28 of 271

You cannot enter the same subnet twice for the same user.

If none of the subnets you entered match an IP the user tries to connect to, the

user will be denied access to that IP.

If more than one subnet matches an IP the user tries to connect to, the group that

belongs to the subnet that matches the IP the closest will be used for the IP

access. For example, you created the user Joe with the following rights:

172.24.0.0 : Observer, and 172.24.30.0 : Administrator. If Joe requests access to

172.24.30.5, he will be granted Administrator rights for that IP. Even though both

subnets you assigned to Joe match the IP he requested, the subnet 172.24.30.0

is closer to the IP than the other one.

To obtain default Observer rights for IP addresses that do not match any of the

subnets in the list, you need to assign the subnet 0.0.0.0 : Observer to the user,

and the subnet mask must also be 0.0.0.0.

Whenever a user performs an operation that is not applicable to a specific

network element (such as changing the security configuration) access

permissions will be calculated by the "Default Access" line (which contains the

Subnet IP and Mask equal to 0.0.0.0). If a "Default Access" line does not exist for

a user, that user will not be able to access general network features.

6. Assign the user to a group.

7. Click OK to save your settings, and OK again to close the main User configuration

window.

2.3.7.4 Granting permissions to groups

When assigning users to groups, you can use one of PolyView's preconfigured groups, or

define your own group with customized group access rights.

To configure group permissions:




2. Open the Group item, and then open the group that you wish to configure.

3. Select the group's Features item and choose Edit > Configure permissions or

double click the Features item to configure permissions for the group.


Page 29 of 271

4. Check components to enable group access to that feature. Clear any checked

components to disable group access to that feature.

5. Click OK to save your changes and close the Features window.


Page 30 of 271

2.3.7.5 Blocking users after unsuccessful login attempts

You can block users after unsuccessful login attempts to the PolyView and TFTP servers.

Use the PolyView server configuration utility to specify the allowed number of login requests and the timeout period between failed logins.

By default, after 4 failed logins, users will be blocked for 5 minutes.

To specify server retries and timeout:

1. Open the PolyView server configuration utility.

2. Select the Security tab.

3. In the Allowed consecutive failed logins field, specify the number of times a user can

attempt to login before being blocked.

a) After the specified number of login attempts, a management trap will be issued,

and the user will not be able to log in again for the amount of time specified by the

Block user period.

b) Setting this value to 0 will allow an infinite number of login attempts.

4. In the Block user period field, specify the number of minutes to block a user from

logging in after reaching the maximum number of failed login attempts.

Setting this value to 0 will disable this feature.

5. Click Apply to change the settings.

6. Click Close to close the PolyView server configuration utility.


Page 31 of 271

To specify TFTP server retries and timeout:


2. Select the File transfer tab.

3. In the TFTP timeout field, specify how many seconds to wait for the TFTP server

response before considering a TFTP request as timed-out.

4. In the TFTP retries field, specify the maximum number of allowed login attempts

before initiating a TFTP timeout.



2.3.7.6 Enabling single sign-on with network element management clients

Synchronize login information with network element EMS to enable single sign on.

To enable single sign-on:




2. Define a group with the permissions that you wish to enable.



the context menu.

5. In the Access by subnet area, select the subnet that you wish to enable for single

sign-on and click Edit to open the User configuration window.


Page 32 of 271

6. Assign the user to the group that you defined.

7. Enter the user name and password to the web EMS and click OK.

Note that the login information must be the same for both the NMS and the EMS.

2.3.7.7 Enabling remote user authentication

Enable remote authentication or restrict all users to local access via security settings in the

PolyView configuration utility.

PolyView uses the RADIUS server protocol to enable secure, remote authentication.

When Radius authentication is enabled:

If the Radius server is available, users will be authenticated by both the local and Radius servers.

NOTE: Note that users must be added to both servers, and the password must be the same on both servers to allow single sign on.

When Radius authentication is disabled:

Users will be authenticated only by the local server.

To enable remote authentication:




Page 33 of 271

3. In the Radius authentication time field, select Enable.

4. In the Radius server host field, specify the IP address or hostname of the Radius

authentication server.

5. In the Radius server login retry timeout field, specify how many seconds to wait before

allowing users to login after reaching the maximum number of failed login attempts.

6. In the Radius server number of login retries field, specify the maximum number of

allowed login attempts to the Radius server.

7. In the Radius server secret field, specify the shared secret for external authentication.



2.3.7.8 Suspending inactive users

You can protect management channels by configuring the server to suspend inactive users.

To suspend inactive users:



3. In the Inactive client disconnect time field, specify the number of minutes the server

should wait before disconnecting an inactive client.

Setting this value to 0 will allow inactive clients to remain connected indefinitely.

The maximum value is 30,000 minutes.


Page 34 of 271


5. Click Close to exit the PolyView server configuration utility.

2.3.7.9 Enforcing secured client server connections

You can enhance network security by configuring the server to use only secure connections

with clients.

To reject non-secure connections:



3. Set Secured client connection to True.



2.3.7.10 Updating user settings

To update the PolyView after configuration changes:






the context menu.


Page 35 of 271

4. When you are done, select File > Update NMS server. to update the server with your

changes.

Note that changing the settings will not affect operations that were already

defined before a security change was made.

NMS User Guide PolyView N6.8 Designing network topology maps

Page 36 of 271

3 Designing network topology maps

3.1 Configuring map display settings

To specify topology map display settings:




2. Click the General tab.

3. Specify how to display network elements on the topology map.

In the Displayed entity name format field, select the format for the element label:

name only, IP address only, or both name and IP address.

4. Specify whether or not to display link names on the map.

Select Hide Link Name or Show Link Name from the Display link name on map

field drop down list

When hidden, you can view the link names via their tooltips.

5. Specify the default width of lines representing links between network elements in the

topology map.

In the Default link width field, specify between 1-10 pixels as the default width for

map links.

6. Specify the color for the map background.

In the Map background color field, select the color for the map background

through a color choose pallet, specifying HSB values, or specifying RGB values.



Page 37 of 271

3.1.1 Configuring client user interface language

To specify the language used for the application interface:




2. Click the Advanced tab.

3. Select the user interface language for CeraMap.

Select English or German from the Select interface language field drop down list

Note that additional languages require a separate software license.



3.1.2 Configuring the client time zone

To configure the application time zone:




2. Click the Advanced tab.


Page 38 of 271

3. Specify the application time zone.

In the Application time zone field, specify the time zone only if the application time

is not calculated correctly. If the time zone is already configured correctly, you

can leave this field empty.

The format is GMT+/- with no spaces between the parameters, for example: GMT+2.

3.1.3 Restoring client configuration defaults

To restore CeraMap defaults:




2. Click Restore defaults to reset configuration parameters to their original values.



3.2 Adding network elements There are four ways to add network elements to a network topology map: Each method is

appropriate for different stages of network management.

Manually adding network elements You 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.


Page 39 of 271

Using auto discovery Auto discovery finds existing network elements, links, and alarms. As PolyView is

designed to manage large networks, auto discovery is the recommended way to

initialize your network topology map.

Importing map data You can also import saved network topology. Note that importing map data will

overwrite any changes that you made after exporting the map data.

Using the Auto Add Network Element feature Upon receiving the first trap from an element, PolyView adds it to the map. The

element will be added to the root without any link.

NOTE: Note that the element must be configured manually to send traps to PolyView.

3.2.1 Network auto discovery

CeraMap provides auto discovery of network entities, including network elements, subnets,

multi-line, multi radio, and protected links.

Flexible discovery configuration options allow you to poll a specific subnet, range of IP

addresses, or type of protocol.

To start scanning:

1. In the Topology tree, select a group to which all newly discovered elements will be

added.

2. Select File > Network auto discovery.


Page 40 of 271

3. Click Add to open the Scope settings window to define the scope of the discovery.

4. Click Discover to start the discovery process.

3.2.1.1 Scope settings

To configure auto discovery scope settings:

1. Select the type of scope you want: IP range or Subnet.

For IP range:

Specify a range of IP addresses to which the network scan will apply.

For Subnet:

Specify the subnets IP address and mask.

In the SNMP parameters tab:

1. Select which SNMP version to use for the discovery scan.


Page 41 of 271

In the Version field, select V1, V2c, or V3.

2. Specify which ports to scan.

In the Port field, use the up/down buttons to select the port number of the element

you want to include in the scan.

3. Specify the maximum number of login retries.

In the Retries field, specify the number of allowed login retries before timing out

SNMP requests.

4. Specify the length of the timeout after reaching the login retries threshold.

In the Timeout field, specify how many minutes to wait after timing out before

allowing a new SNMP request.

For V1 and V2c:

Specify the login information.

In the Read community field, specify the login password for the Read community.

In the Write community field, specify the login password for the Read community.


Page 42 of 271

For V3:

1. Configure the login information.

In the User name field, specify the SNMPv3 user name.

In the Password field, specify the SNMPv3 password with at least eight

characters.

2. Specify the authentication algorithm.

In the Authentication field, select MD5 or SHA.

Select None to disable SNMP authentication.

3. Specify the security mode.

In the Privacy field, select DES to enable privacy.

Select None to disable SNMP privacy mode.

In the HTTP parameters tab:

Specify the preferred communication protocol: HTTP or HTTPS.


Page 43 of 271

3.2.1.2 The auto discovery process

The Discovery status area shows the progress of the scan.

To view information about errors that may have been detected during the scan, click the Error log tab.

The duration of the discovery process depends on the network size and the connection speed. The time may vary from several minutes to several hours.

Newly discovered elements will be added to the group you selected. If a discovered element already exists in the target group or in one of its sub-groups, the original

element will be retained, and the discovered one will not be added.


Page 44 of 271

During the process, PolyView will also search for connectivity between elements. Links will automatically be generated for any connected entities that PolyView

discovers.

If more than two elements are found to be linked, PolyView will create a sub-group for them, and all the linked elements will be moved to that sub-group.

You can add more than one range or subnet, by clicking the Add button in the Network auto discovery window.

3.2.2 Adding network elements manually

To manually add a network element to a map: Select Edit > Add network element, press Insert, or right click a group icon in the

topology tree or on the map and choose Add network element from the context menu.


Page 45 of 271

In the Add Network Element window:

1. Specify the IP address.

In the IP address field, specify the IP address of the element you want to add.

2. Define a network name for the network element.

Check the User defined name field, and enter a name for the network element.

3. Choose an icon to represent the map element from the Network elements icon

gallery.

The element type is determined from the icon that you choose, after investigating

the element the icon will be according to the correct type of the element.

4. Configure the SNMP and HTTP settings.

5. Click OK to add the new network element to the map. The new element will also

appear in the topology tree on the left.

In the SNMP parameters tab:

1. Select which SNMP version to use for the discovery scan.

In the Version field, select V1, V2c, or V3.

2. Specify which ports to scan.

In the Port field, use the up/down buttons to select the port number of the element

you want to include in the scan.

3. Specify the maximum number of login retries.

In the Retries field, specify the number of allowed login retries before timing out

SNMP requests.

4. Specify the length of the timeout after reaching the login retries threshold.

In the Timeout field, specify how many minutes to wait after timing out before

allowing a new SNMP request.

For V1 and V2c:

Specify the login information.

In the Read community field, specify the login password for the Read community.

In the Write community field, specify the login password for the Read community.


Page 46 of 271

For V3:

1. Configure the login information.

In the User name field, specify the SNMPv3 user name.

In the Password field, specify the SNMPv3 password with at least eight

characters.

2. Specify the authentication algorithm.

In the Authentication field, select MD5 or SHA.

Select None to disable SNMP authentication.

3. Specify the security mode.

In the Privacy field, select DES to enable privacy.

Select None to disable SNMP privacy mode.


Page 47 of 271

In the HTTP parameters tab:

Specify the preferred communication protocol: HTTP or HTTPS.

3.2.3 Importing map data

To import saved network topology data: Select File > Import data.

The data will be imported under the currently selected group.

If you import an entity that already exists - a network element with the same IP, or a group

with the same name, PolyView updates the element attributes from the imported file.

3.2.4 Automatically adding network elements

To automatically add network elements that forward traps to the server:






Page 48 of 271

3. Enable or disable automatically adding a new network element to the map as soon as

it forwards a trap from an unknown IP address.

Select Enable or Disable from the Auto add network element field drop down list.



3.3 Adding symbols to network topology maps Symbols are icons that represent various network devices, but are not treated as network

elements by PolyView.

No polling is performed for symbols.

Links can be defined between symbols and other symbols or network elements.

You can delete and move symbols the same as with other elements in the map.

To add symbols to a network map: Select Edit > Add symbol, press Ctrl + S, or right click the map and choose Add symbol



Page 49 of 271

In the Add Symbol window:

1. In the Name field, specify a name for the symbol in the Name field.

2. Check the Show name on map checkbox if you want the name you specified to

appear on the map under the symbol.

3. Select a symbol from the Select a symbol icon gallery and click OK.

If you want to add a symbol that does not appear in the window, you must copy

the graphic file to the symbol folder in PolyView/image/symbols.

Only GIF and JPG formats are supported.

Symbol files can be grouped in sub-folders in the symbols directory.

Symbol file and sub-folder names cannot include spaces. If you want to include

spaces in symbol file or sub-folder names, use underscores (_). For example, the

file Ethernet_Bridge.gif, will appear as "Ethernet Bridge".

Add symbol files only to PolyView. Media files are automatically copied to all

PolyView clients.


Page 50 of 271

3.4 Adding labels to network elements Labels are customizable text strings of up to 80 characters that you can use to document your

map.

To add labels to a network element: Select Edit > Add Text, press Ctrl + T, or right click the map and choose Add text from

the context menu.

In the Add Text window:

1. In the Text field, enter the text you want to appear in the map. Each element can

include up to 80 symbols.

2. Define the font, color, border, and background options, and click OK.

Note that the Sample area may display only part of the actual text. The level of

opacity is not shown in the sample, and for border size, only the simple border

style will be displayed.


Page 51 of 271

3.5 Creating groups of network elements Network entities will automatically be arranged on the topology tree according to subnet. For

large networks, it is helpful to create additional hierarchy by organizing network entities into

groups.

PolyView operates in a hierarchical manner. Most operations apply to the selected network elements, including all the sub-elements in the selection.

You can establish visual differentiation between groups by establishing logical naming conventions, choosing different icons for each group, and by defining group

backgrounds.

You can create an unlimited number of levels in the map by grouping network elements.

Groups that you add to the map will also be added to the topology panel on the left.

The color of the group element is determined by the alarm severity level of network elements in the group.

To group map elements: Select Edit > Add group, press Ctrl + G, or right click a group icon in the topology panel

or on the map and choose Add group from the context menu.


Page 52 of 271

In the Add Group window:

1. In the Name field, enter a name for the group

Group names can be alphanumeric strings, and may contain spaces.

2. In the Select a group icon area, choose an icon to represent the group.

3. Define the background color for the group.

a) Check the Define background option.


Page 53 of 271

b) Click the Select... button to browse for a background image.

c) Specify the Opacity level of the background image.

4. Click OK to add the new group to the map. The new group will also appear in the

topology list in the left panel.

3.6 Creating links between map entities Links in the map show how elements and groups are connected in the network.

To manually create a link: Select two elements or groups and press Ctrl +L, select Edit > Add link from the menu,

or right click the selection on the map and choose Add link from the context menu.


Page 54 of 271

In the Add Link window:

1. Specify the link end points.

Specify the system ID or IP addresses for the linked elements in the End points

field.

2. Name the link.

Enter a name for the link in the Name field.

Unless you changed the default Display link name on map setting, the link name will be displayed as a tooltip, when you mouseover the link.

3. Define the link width

The default width of map links is determined by the settings you defined in the

Client configuration utility.

The color of the link will be determined by its alarm severity.


Page 55 of 271

4. Specify the type of link connection and click OK.

In the Connections list area, specify the type of link: Radio, Multi radio, Line, Multi

line, Protected, or Generic.

3.7 Moving network elements You can move selected network entities to another group or subnet, by dragging them to a

new location on the map or in the topology tree.

To move network elements to a different group:

1. Select the elements to be moved.

2. Select Edit > Move, or right click the element in the topology panel or on the map and

choose Move from the context menu.

To select multiple elements, press the Ctrl key while you select.

3. Select a new parent group, and click OK.

You can also drag & drop selected elements to a new location.

If the elements you want to move have links between them, the links will be

moved as well.

If the elements have links to other elements that are not to be moved, the links

will be deleted.

3.8 Modifying map entities

To view or modify properties of a map element: Select the element and press Ctrl + Enter, choose Edit > Properties from the menu, or

right click map entities and select Properties from the context menu.

For network elements, you can modify: The system name, location, and contact person.

The user defined name.

The SNMP or HTTP access. Change elements properties


Page 56 of 271

Changing SNMP or HTTP settings will affect only the PolyView database; it doesnt write the change to the element itself.

To change a network elements access settings:

Broadcast the configuration change.

Change elements properties

Perform a Poll node operation to update the elements

properties.

For groups, you can modify: The name, icon or background color.

For links, you can modify: The link name and IP address of the link end points.

Link display parameters such as line width and link type.

For labels, you can modify: The label text, font, color, border, and background options.

For symbols, you can modify: The symbol name and icon.

You can delete any map entity except for the root element or the element that

represents the PolyView server.

3.9 Deleting map entities

To delete map entities:

1. Select the element you wish to delete and select Edit > Delete, or right click the

element and choose Delete from the context menu.

To select multiple elements, press the Ctrl key while you select.

2. Click Yes to confirm.

3.10 Backing up network topology data Map topology can be saved - either to the database or to a file. PolyView stores network

topology data in the NMS database, and raises an event alarm to notify you of changes to the

configuration.

Note that if you use CeraMap to design a network, export the data, running a Discover

operation will overwrite any links that you added to your design.

To export network topology data to an external file:

1. Use the topology tree to select which part of the network data to export.

Select the root to export the entire network. To save topology data for a specific

subnet, select the subnet before performing exporting the data.

2. Select File > Export data to open the Export data window.


Page 57 of 271

3. In the Data types area, clear the checkboxes of any data types you wish to exclude

from the export.

4. In the File area, click the Ellipsis button to specify the output destination path and

filename.

5. Click OK to export the topology data.

NMS User Guide PolyView N6.8 Managing mapped devices

Page 58 of 271

4 Managing mapped devices

4.1 Global administration of network elements

The CeraMap GUI enables centralized administration of all discovered network elements.

View and manage network elements alarms filter network element alarm lists by alarm type, duration, severity, or raise/clear status for any selection of network

elements.

Perform global configuration operations such as configuration broadcasts and software and configuration downloads.

Monitor network element status and performance.

Define customized, feature-based access to network elements.

Manage TDM trails and End-to-End Ethernet services.

4.2 Topology tree CeraMaps topology tree provides a logical view of network topology. NMS users can drill

down to see and open all the subnets in their view of network, and all of the elements in each

subnet.

Selecting a network element in the topology tree highlights the network element on the topology map.

Double clicking a network element in the topology tree opens its EMS.

Double clicking a subnet in the topology tree opens the subnet topology map.

4.3 Discover node When an element is first added to the map, PolyView automatically reads the elements

information. If you change this information, you can perform a Discover node operation to

write the element's most updated properties to the PolyView database.

A Discover node operation removes all existing information, including stored reports, with the

new data.

Discover node operations can be performed only on a single element.

To update a network elements configuration and inventory information:

1. Select the element.

2. Select Tools > Discover node.


Page 59 of 271

3. In the Discover node window, click Apply to rediscover the network element.

Poll node retrieves real time performance data for the network element, such as current

alarms and network element availability.

4.4 Poll node You can poll a selection of sub groups or network elements to retrieve current performance

and inventory status.

PolyView automatically polls all elements every few hours according to user configured polling

intervals.

4.4.1 Retrieving network element inventory information

Executing a Poll node operation overwrites previous element inventory information with

updated element status adds new alarms and performance monitoring information to the

PolyView database.

To force PolyView to retrieve updated information from network elements:

1. Select one or more target elements and select Tools > Poll node.

2. In the Poll Node window, click Apply.

To update the map without polling: Select File > Refresh or click the toolbars Refresh icon.


Page 60 of 271

4.4.2 Configuring polling intervals

To configure polling intervals:





In the Polling tab:

1. Specify how often the server should poll network elements for dynamic inventory data.

In the Dynamic polling interval field, specify the number of hours: minutes

between dynamic data polling.

2. Specify how often the server should poll network elements for performance monitoring

data.

In the Reports polling interval field, specify the number of hours: minutes between

PM data polling.

3. Specify how often the server should backup configuration files from network elements.

In the Config upload interval field, specify the number of hours: minutes between

uploading configuration files.

4. Specify how often the server should poll network elements for current alarm data.

In the Alarms polling interval field, specify the number of hours: minutes between

alarm data polling.

5. Click Apply.



Page 61 of 271

4.5 Testing for connectivity to network elements Ping and trace route are used to test connectivity between the PolyView server and the

network element.

The Ping window lists the attempts made by the server to connect with the element, and other connectivity information, such as the connection speed.

The Trace route window displays the routing connectivity to the element (the path the packet takes on its way to the element).

To start a ping operation: Select an element in CeraMap, and then select Tools > Ping.

To start a trace route operation: Select an element in CeraMap, and then select Tools > Trace route.


Page 62 of 271

4.6 Finding network elements CeraMap's Navigator panel displays a hierarchical view of your network topology. You can

drill down to see all the subnets in your network, and all of the sub-elements of on that subnet.

To find a network element:

1. Select Edit > Find.

2. Enter the search terms in the Text box.

3. Specify the scope of the search and click Find.

4.7 Launching a network elements EMS

The EMS that opens for a unit depends on the type of unit.

IP-10 units open CeraWeb, a browser based EMS.

Older units, such as the x1500 series, open the CeraView desktop SNMP EMS.

3rd party units open their proprietary EMS applications.

CeraMap also provides centralized access to network element EMS clients. When single sign-

on is enabled, you can open the EMS for a selected network element from any network

topology map, any list of alarms, or any type of report.

To launch an element manager from a report: Select a report record, and select Actions > Launch element manager, or right click a

record and select Launch element manager from the context menu.

To launch an element manager from an alarm: Select an alarm from the list, and select Actions > Launch element manager, or right

click an alarm and select Launch element manager from the context menu.


Page 63 of 271

To launch an element manager from a network topology map: Double click a network element to launch its element manager, or right click a network

element and select Open.

Note that double clicking a group opens the group.

4.8 Working with multi-radio network elements

Use discover node to find new (multi radio) network elements and links.

1. Perform Poll node on discovered network elements.

2. Use Ping to verify connectivity.

To add a multi-radio link to two network elements

1. Choose two network elements on a map.

2. Right click and choose Add link to add a link between the selected elements.

To generate an inventory report on network elements with multi-radio links:

1. Select Reports > Inventory reports or click the Inventory reports icon to open the

Inventory reports selection dialog.

2. Select Radio report from the drop down list, and click OK to generate the report.

3. Select Report > Filter > Show/hide columns or click the Filter icon and select

Show/hide columns from the context menu to open the Filter report by columns

value window.

4. Ensure that the Multi RadioAdmin column is set to visible.

Check the Multi RadioAdmin checkbox and click OK.

5. Select Report > Filter > Filter by values or click the Filter icon and select Filter

by values from the context menu to open the Filter report by columns value dialog.

6. Select Multi RadioAdmin from the Field drop down list.

NMS User Guide PolyView N6.8 Fault management

Page 64 of 271

5 Fault management

5.1 Configuring alarm settings

To configure alarm settings:





3. Specify how often the server should poll network elements for current alarm data.

In the Alarms polling interval field, specify how often the server should poll

network elements for current alarm data.

4. Click Apply.

5. Select the Alarms tab.


Page 65 of 271

6. Specify how long to keep alarm log history data in the database.

In the Keep alarms history field, configure the server to keep alarm log history for

between 5-365 days.

Note that alarms that are open (raised) will be kept until they are closed,

regardless of the value you set for this option.

7. Select the format you want for email messages triggered by alarms.

In the Email format field, select HTML or Plain text.

If you select, HTML, you can use HTML tags to control the way the messages appear.

8. Specify the maximum number of alarms to show in the alarm logs window.

In the Max number of initial alarms field, specify between 1000 and 50,000 initial

alarms.

Note that while the window is open, new alarms will be added to the alarms log as they are received.

9. Specify whether to acknowledge or ignore the heartbeat traps received from the

network elements

In the Ignore heartbeat field, select Enable or Disable.

Disable this trap to prevent them from being included with the rest of the forwarded traps.

10. Click Apply.


5.2 Viewing alarms

5.2.1 Viewing current alarms

You can view current alarms or alarm history for the entire network, or for group, subnet, or

selection of network entities.

To view current alarms:

1. Select the target network elements from the network topology map or the Navigator

topology tree.

2. Select Reports > Current alarms, press ALT + A, click the Current alarms icon, or

right click and select Current alarms from the context menu.


Page 66 of 271

5.2.2 Viewing top most alarm severity

Alarm severity status is built into the topology GUI. Map entities are color coded according to

alarm severity, and are displayed using the color of their top-most alarm.

If there is more than one alarm configured for a network entity, the map displays the color of

the most severe alarm.

Severity Color

Critical Red

Major Orange

Minor Light orange

Warning Yellow

Event Blue

Normal Green

Unknown / not responding

Grey

For example, green means that the element is operating with no alarms; while red means that

the element is operating with one or more major alarms.

Icons in the topology tree also reflect alarm status. The color of upper level groups and the

root level will always be the color of the element in the list with the most severe alarm.

If a network element is unreachable, it will appear on the map with a line across it.

5.2.3 Viewing alarm details

The Alarm details window provides comprehensive information about a selected alarm.

To view the details of a particular alarm:

1. Open the Current alarms report.


Page 67 of 271

Select Reports > Current alarms, press ALT + A, click the Current alarms icon,

or right click and select Current alarms from the context menu.

2. Double click an alarm to open its details.

The General tab displays the location, description, severity, and status of the

selected alarm. When available, the General tab will also provide probable

causes and corrective actions to help you clear the alarm.

The User actions history tab displays which actions have been performed on the

selected alarm, and by which user. For example, you can see if an alarm has

been acknowledged or cleared, or if the user added any messages to the alarm.

The Advanced tab provides additional details to help you resolve the alarm, such

as the alarm, trap, and object IDs.


Page 68 of 271

5.2.4 Viewing alarm history

The list of current alarms helps identify which items require immediate action. The alarms log

helps identify recurring events that may require preventative measures.

To view the alarm log:

1. Select the target network elements from the network topology map or the Navigator

topology tree.

2. Select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right click

and select Alarm log from the context menu.

3. Specify the start and end dates of the report, and click OK.

Apply relevant filters to help identify recurring patterns or problematic areas of the network.

By default, the alarm log is a logical view, meaning that Raise and Clear commands generate

a single alarm, and are shown on the same line.


Page 69 of 271

At times, it may be easier to view the Alarm Log in a chronological view, with Raise and Clear

generated alarms on different lines.

To view the alarm log in chronological order:

1. Open the Alarm log window.

Select Reports > Alarm log, press ALT + L , click the Alarm log icon, or right

click and select Alarm log from the context menu.

Specify the start and end dates of the report, and click OK.

2. Select Actions > Filter > Chronological view.

5.3 Managing alarms

5.3.1 Hiding alarms

Use the Hide button below the list of alarms to hide less critical alarms from the list.

To hide selected alarms:




2. Select the alarms that you wish to hide and select Actions > Hide or click the Hide

icon.

5.3.2 Viewing hidden alarms

To view hidden alarms:




2. Select Action > Show hidden to display all alarms that are normally hidden.


Page 70 of 271

5.3.3 Acknowledging alarms

Use the Acknowledge and Note buttons below the list of alarms to acknowledge and add

messages to an alarm.

You can also add notes to alarms that you acknowledge.

To acknowledge an alarm:




2. Select the alarm that you wish to acknowledge.

To perform a multiple acknowledgement, select all the alarms that you wish to

include.

3. Select Actions > Acknowledge, click the Acknowledge icon, or right click

polyview user guide n6.8

Documents