NetMaster SAT Rev - D

Site Acceptance Test (SAT)
Rev Date Rev. Document ID

2011-04-05 D NETMASTER\COMMON\00026
Prepared by Approved by
PFD PFD
NetMaster Standard Site Acceptance Test
Procedures and Test Result Records
Table of Contents
1. INTRODUCTION .............................................................................................................3
2. GENERAL INFORMATION..............................................................................................3
2.1 System configurations......................................................................................................3
2.2 Related documents ..........................................................................................................4
2.3 Test preparations.............................................................................................................4
2.4 Description of System in Test ..........................................................................................5
3. INDIVIDUAL TESTS ........................................................................................................6
3.1 Configuration Management..............................................................................................6
3.1.1 Discovering and managing elements ...............................................................................6
3.1.2 Unmanaging elements .....................................................................................................6
3.1.3 NE Configuration .............................................................................................................7
3.1.4 HW and SW Inventory .....................................................................................................7
3.1.5 CPE specific views for PtMP systems ..............................................................................7
3.1.6 SW Download Jobs (Evolution/InterLink/CityLink/NL-29x/WiLink elements) ....................7
3.1.7 SW Activation/Reset (Evolution/InterLink/CityLink/NL-29x elements)...............................8
3.1.8 NE Configuration File Management (Evolution elements) ................................................8
3.1.9 Help System ....................................................................................................................9
3.2 Fault Management .........................................................................................................10
3.2.1 Active Alarms.................................................................................................................10
3.2.2 Historical Alarms............................................................................................................11
3.2.3 Alarm Templates............................................................................................................11
3.3 Performance Management.............................................................................................12
3.3.1 Enable Performance Measurements Collection .............................................................12
3.3.2 Current Performance .....................................................................................................12
3.3.3 Historical Performance...................................................................................................12
3.3.4 Threshold Crossing Alarms (TCA) .................................................................................13
3.4 Security Management ....................................................................................................14
3.4.1 Group and User Management........................................................................................14
3.4.2 User Audit Data Logging ................................................................................................14
3.4.3 User Audit Filtering ........................................................................................................15
3.5 Optional Features ..........................................................................................................16
3.5.1 Administrative Domains with Geographical Maps...........................................................16
3.5.2 Report Generator ...........................................................................................................17
3.5.3 SNMP Northbound Interface ..........................................................................................17
3.5.4 Hot Standby Redundancy Tests, 2+2 HA system...........................................................18
3.5.4.1 Hot Standby Redundancy, 2+2 HA system: Installation and Normal Operation..............19
3.5.4.2 HA Restore, 2+2 HA system - no existing restore backup file ........................................25
3.5.4.3 HA Export, 2+2 HA system - Number of export files to keep ..........................................27
3.5.4.4 HA Export Restore, 2+2 HA system - Number of HA restore files to keep......................31
3.5.4.5 Schedule export and restore, 2+2 HA system ................................................................34
3.5.4.6 Oracle error on primary DB Server, 2+2 HA system.......................................................37
3.5.5 Hot Standby Redundancy Tests, 2+2 HA system, Reversed Operation .........................38
3.5.5.1 Hot Standby Redundancy (reversed operation) , 2+2 HA system ..................................40
3.5.5.2 HA Restore, 2+2 HA system - no existing restore backup (reversed operation) .............43
3.5.5.3 Schedule export and restore (reversed operation) , 2+2 HA system ..............................45
Nera Networks AS
Page 1(83)
Document ID Rev. Rev Date
NETMASTER\COMMON\00026 D 2011-04-05
3.5.5.4 Oracle error on primary DB Server (reversed operation) , 2+2 HA system .....................48
3.5.6 Hot Standby Redundancy Tests, 1+1 HA system...........................................................50
3.5.6.1 Hot Standby Redundancy, 1+1 HA system: Installation and Normal Operation..............51
3.5.6.2 HA Restore, 1+1 HA system - no existing restore backup file ........................................57
3.5.6.3 HA Export, 1+1 HA system - Number of export files to keep ..........................................59
3.5.6.4 HA Export Restore, 1+1 HA system - Number of HA restore files to keep......................63
3.5.6.5 Schedule export and restore, 1+1 HA system ................................................................66
3.5.6.6 Oracle error on primary Server, 1+1 HA system.............................................................69
3.5.7 Hot Standby Redundancy Tests, 1+1 HA system, Reversed Operation .........................70
3.5.7.1 Hot Standby Redundancy (reversed operation) , 1+1 HA system...................................72
3.5.7.2 HA Restore, 1+1 HA system - no existing restore backup (reversed operation) .............75
3.5.7.3 Schedule export and restore (reversed operation) , 1+1 HA system ..............................77
3.5.7.4 Oracle error on primary DB Server (reversed operation) , 1+1 HA system .....................80
3.5.8 NetMaster System Manager - Backup and Restore .......................................................82
CONCLUDING REMARKS............................................................................................................83
4. SIGNATURES ...............................................................................................................83
Nera Networks AS
Page 2(83)
1. INTRODUCTION
This document describes the Site Acceptance Test for the Nera NetMaster management system.
2. GENERAL INFORMATION
2.1 System configurations

A co-located server/client configuration is shown in Figure 1. This is suitable for small networks.
Co-located
Server
+ Network
Client Elements
LAN/WAN
Network
Elements
Figure 1. A NetMaster configuration with co-located servers and client.

In Figure 2, a NetMaster configuration with separate servers and clients is shown. This is suitable for
medium-sized networks.
A SAT for a NetMaster configuration according to Figure 1 or Figure 2 is performed as one test for a single
installation.
Clients
Application
Server
LAN/WAN
Database
Server
Network Network
Elements Elements
Figure 2. A NetMaster configuration with separate servers and clients.

Figure 3 shows a configuration suitable for the largest networks. In addition to the server and client split, a
redundant standby system with database replication is also configured.
A SAT for a NetMaster configuration according to Figure 3 is performed as two separate tests, one for each
installation in Primary/Main and Standby site.
Nera Networks AS
Page 3(83)
Main system Standby system

App. Server DB Server DB Server App. Server
Clients LAN
Clients
WAN
Network Network
Network Network
Elements Elements
Elements Elements Network Network
Elements Elements
Figure 3. A redundant NetMaster system.
2.2 Related documents

Relevant documents for the SAT are:
• NetMaster Technical Description
• NetMaster Installation Guide
• NetMaster User Manual
• NetMaster System Manager User Manual
2.3 Test preparations

Prior to test executions, the NetMaster system must be properly installed and running. This implies correct
installation of
• NetMaster server
• Database (co-located with NetMaster server or on separate computer)
• One or more NetMaster clients (co-located with NetMaster server or on separate computer)
• External Configuration Tools for NE specific element configuration
For details on the installation, refer to NetMaster Installation Guide and NetMaster System Manager User
Manual.
The NetMaster system must be connected to a radio network with operational elements, and the settings for
NE specific external configuration tools must be configured in both System Settings and Local Settings under
the NetMaster Preferences View.
Nera Networks AS
Page 4(83)
2.4 Description of System in Test
Date of Test
Place of Test
Customer
(Tick one)
Single site
Site Description Primary site of redundant system
Standby site of redundant system
Primary + Standby site of redundant system
NetMaster Version (Primary):
License number (Primary):
Operating System, Version & Patch level:
NetMaster Server
CPU:
RAM:
HDD:
(Tick one) (Tick one)
Oracle Standard Edition One Separate database server
Oracle Standard Edition Co-located database server
Oracle Enterprise Edition
Database Server PostgreSQL
CPU:
RAM:
HDD:
(Tick one)
Client Separate client
Co-located client
CPU:
RAM:
HDD:
(Tick all that apply)
Evolution NL29x/24x/18x-A FlexLink SmartNode
InterLink/CityLink CityLink FE WiLink I SmartMetro
Managed NE Types NetLink/N2N CompactLink WiLink XL Eltek SmartPack
BG-Mux
Other:
Nera Networks AS
Page 5(83)
3. INDIVIDUAL TESTS
3.1 Configuration Management
3.1.1 Discovering and managing elements

Step Description Expected result Status Comments
Discover some elements. Use 5-10 Discovered elements are Pass
1 elements of different kinds if possible. shown in the Unmanaged Fail
Elements view. N/A
Drag some unmanaged elements into The elements appear in
Pass
the geographical or logical tree. the tree, and are removed
2 Fail
from the Unmanaged
N/A
Elements view
In the Unmanaged Elements View, The Managed Elements Pass
4 select a number of elements dialog is displayed Fail
Invoke Manage Element(s) action N/A
Select the destination model The selected elements Pass
5 (geographical or logical) in the dialog appear in the tree view of Fail
and press OK. the corresponding model N/A
3.1.2 Unmanaging elements

Ensure that an element A is managed Element model presence
in geographical model only. verified OK. Pass
1 Ensure that two elements B and C are Fail
managed in both geographical and N/A
logical models.
Select element A in the geographical The element is removed
model. Invoke the Delete action. from the geographical Pass
2 A Confirm Delete dialog appears. model, and appears in Fail
Select Yes. the Unmanaged N/A
Elements view.
Select element B in the geographical The element is removed
model. Invoke the Delete action. from the geographical
A Confirm Delete dialog appears. model, but is still present Pass
3 Do not select Remove from all models. in the logical model. The Fail
Select Yes. element does not appear N/A
in the Unmanaged
Elements view.
Select element B in the logical model The element is removed
Invoke the Delete action. from the logical model, Pass
4 A Confirm Delete dialog appears. and appears in the Fail
Select Yes. Unmanaged Elements N/A
view.
Nera Networks AS
Page 6(83)

Select element C in the logical model. Element C is removed
Invoke the Delete action. from both geographical
Pass
A Confirm Delete dialog appears. and logical models, and
5 Fail
Select Remove from all models. appears in the
N/A
Select Yes. Unmanaged Elements
view.
3.1.3 NE Configuration
Select an element in the geographical There is an external
Pass
tree, right click and select configuration tool
1 Fail
Configuration -> External Tools. Do available for every NE
N/A
this for every different NE type. type.
For every different NE type, start the The external
Pass
external configuration tool. configuration tool opens,
2 Fail
or optionally prompts for
N/A
username and password.
If requested, enter username and The external
Pass
password to open the external tool. configuration tool opens
3 Fail
with the selected element
N/A
in scope.
3.1.4 HW and SW Inventory

Right click on an element in the tree A view opens with a Pass
1 view and select Configuration -> software inventory list for Fail
Software Inventory. the selected element. N/A
Right click on an element in the tree A view opens with a Pass
2 view and select Configuration -> hardware inventory list for Fail
Hardware Inventory. the selected element. N/A
3.1.5 CPE specific views for PtMP systems

Right click on a PtMP element and The CPE Inventory view Pass
1 select Configuration -> CPE is opened. Fail
Inventory. N/A
Right click on a PtMP element and The CPE Radio Statistics Pass
2 select Performance -> CPE Radio view is opened. Fail
Statistics. N/A
3.1.6 SW Download Jobs (Evolution/InterLink/CityLink/NL-29x/WiLink elements)

Start the wizard for SW download The SW Download wizard
Pass
jobs, from main menu View -> starts.
1 Fail
Configuration or element/domain
N/A
popup Configuration menu.
Nera Networks AS
Page 7(83)

Create a download job and include A download job is created
Pass
some elements. Define SW package and shown in the
2 Fail
files to download and then save the Software Download Jobs
N/A
job. view.
Start the download job. SW is downloaded to the Pass
3 elements included in the Fail
job. Progress is shown. N/A
3.1.7 SW Activation/Reset (Evolution/InterLink/CityLink/NL-29x elements)

Note: SU board dependence for NL-29x equipment, only applicable for newer SU board 2KZ198B
Right click on an element and select A view opens with a list of Pass
1 Configuration -> Software Inventory. software for the selection. Fail
N/A
Check that an IDLE SW package is IDLE SW package is Pass
2 available in the element. available. Fail
N/A
Select the IDLE SW package and IDLE SW package is Pass
3 invoke the Activate action. activated. Fail
N/A
Select the ACTIVE SW package and ACTIVE SW package is Pass
4 invoke the Reset action. reset. Fail
N/A
3.1.8 NE Configuration File Management (Evolution elements)

Right-click on an Evolution element The Configuration File
Pass
and invoke the Configuration -> Management view opens
1 Fail
Configuration File Management with the selected element
N/A
action. shown.
Invoke the Backup Configuration A dialog window opens,
Pass
action from the menu bar icon or by prompting for a
2 Fail
right-clicking on the element. description of the planned
N/A
backup job.
Type in a description of the backup A backup job is created,
job and click OK. Open the job details started and finished for
Pass
by clicking on the +-sign next to the the selected element. Job
3 Fail
element name. status enters RUNNING
N/A
and DONE states for the
selected element.
Invoke the Configuration File The Configuration File
Pass
Management action from main menu Management view opens
4 Fail
View -> Configuration. with all valid network
N/A
elements listed.
Select multiple elements from the list A dialog window opens,
and invoke the Backup Configuration prompting for a Pass
5 action from the menu bar icon or by description of the planned Fail
right-clicking on one of the selected backup job. N/A
elements.
Nera Networks AS
Page 8(83)

Type in a description of the backup A backup job is created
job and click OK. Open the job details and started in RUNNING
by clicking on the +-sign next to the state for the first element
element names. in the list; other elements
are in PENDING state. Pass
6 When one element Fail
backup is finished, this N/A
element enters DONE
state and the next
element in the list enters
RUNNING state.
Before the running backup job is The running element
finished, invoke the Cancel Backup backup and all pending
menu icon. element backups enter
Pass
state CANCELLING and
7 Fail
then CANCELLED.
N/A
Already finished element
backups are preserved in
the DONE state.
From a backup job that is DONE, The backup file is saved
Pass
invoke the Save As action to save the to the local file system,
8 Fail
newly acquired backup file to the local and can be seen from a
N/A
OS file system. file explorer window.
From the external configuration tool, The recently uploaded
upload a configuration file backup backup file is added to
from a network element to the local the list of available
file system. From the Configuration configuration files in the Pass
9 File Management view, select the Configuration File Fail
actual network element and invoke Management view, with N/A
the Add file action. Select the recently status ADDED.
uploaded backup file, type in a
description and press OK.
From the Configuration File The selected
Management view, select a network configuration file is
element with an available restored to the selected Pass
10 configuration file. Select the network element and the Fail
configuration file and invoke the element is reset. N/A
Restore Configuration action. Press
Yes to confirm configuration restore.
3.1.9 Help System

Right click the Help choice from the The general Help system Pass
1 NetMaster main window menu. opens. Fail
N/A
Right click on an element or a domain Context sensitive Help Pass
2 and select the Help choice. function opens. Fail
N/A
Nera Networks AS
Page 9(83)
3.2 Fault Management
3.2.1 Active Alarms

Open Active Alarms view for an Active Alarms view Pass
1 element. opens. Fail
N/A
Generate an alarm on the element. Alarm is shown in Active
Pass
Alarms view and element
2 Fail
colour is updated
N/A
according to new alarm.
Verify that the colour of the highest The colour of the highest
Pass
severity on the various resources are severity is mapped to the
3 Fail
mapped to corresponding element in element.
N/A
tree view and map view
Acknowledge all active alarms on an Fill colour of element is
Pass
element. cleared and severity
4 Fail
colour is shown only on
N/A
the element outline.
Set audible alarms from Preferences Audible alarm is
-> Local settings -> Fault -> Sounds. generated. Pass
5 Generate an alarm on an element, Fail
with higher severity than any existing N/A
alarm on the element
From Active Alarms view, on the top All columns appear in
Pass
right dropdown menu, select view.
6 Fail
Customize Columns and enable all
N/A
columns in view
Sort the alarms by Raised time by Alarms are sorted by Pass
7 clicking on the column header. raised time. Fail
N/A
Sort the alarms by Severity. Alarms are sorted by Pass
8 severity. Fail
N/A
Open the Preferences view from the New severity colour
Window menu, change the colour should be reflected in
Pass
associated with a severity class that GUI (Map/tree views,
9 Fail
corresponds to one of the active Active alarms, Alarm
N/A
alarms in the network. (System Summary).
settings or Local settings).
Check total alarm count in Alarm The total alarm counts of Pass
10 Summary view and Active Alarms the two views are Fail
view. identical. N/A
For each alarm severity, check total For each alarm severity,
Pass
alarm count of that severity in Alarm the number of alarms is
11 Fail
Summary view and Active Alarms identical in both views.
N/A
view.
Nera Networks AS
Page 10(83)
3.2.2 Historical Alarms

Open Historical Alarms view for an The Customize Columns
Pass
element, and then on the top right dialog appears.
1 Fail
dropdown menu, select Customize
N/A
Columns.
Enable all columns in view. All columns appear in Pass
2 view. Fail
N/A
Sort the alarms by Raised Time by Alarms are sorted by Pass
3 clicking on the column header. raised time. Fail
N/A
Sort the alarms by Severity. Alarms are sorted by Pass
4 severity Fail
N/A
In the view, invoke the Export to File A File Save dialog pops Pass
5 action. up. Fail
N/A
In the File Save dialog, select the .xls, The file can be opened
Pass
.csv or .xml file format and save to file. and the dataset of the
6 Fail
Open the saved file with a view is present and
N/A
corresponding application. readable in the file.
Open View -> Other -> Filter Manager A new Historical Alarms
and create a new blank Historical filter is created.
Alarms filter. Under the Raised Time Pass
7 (NE), select Last Day, then press Fail
Apply and save the filter. Right-click N/A
on the new filter and select Include in
Favourites (for the current user).
In the Historical Alarms view open the Only historical alarms Pass
8 newly created filter. with raised time within Fail
last day are shown. N/A
3.2.3 Alarm Templates

Open from main menu View -> Fault A new alarm template is
-> Alarm Templates and create a new created.
alarm template for an existing network Pass
1 element type. Change the severity of Fail
an alarm that can be manually created N/A
on the element, and save the
template.
From a managed element of the same The template is assigned
type as the newly created template, to the chosen element. Pass
2 assign the template from the element Fail
popup-menu, Fault -> Alarm N/A
Templates Assignment.
Generate an alarm of the type that Alarm presented in
Pass
has been changed in the template. NetMaster is according to
3 Fail
the redefined severity
N/A
from the template.
Nera Networks AS
Page 11(83)
3.3 Performance Management
3.3.1 Enable Performance Measurements Collection

Select a managed element and invoke Performance Collection Pass
1 the Enable Performance Collection dialog is opened. Fail
action. N/A
Select Granularity 15 min for some Granularity 15 min for Pass
2 parameters, select OK to start parameters is selected. Fail
measurements collection. N/A
3.3.2 Current Performance

Select a managed element with Current Performance
Pass
running measurements (or a domain dialog is opened.
1 Fail
containing such elements). Invoke the
N/A
Current Performance action.
Select a combination of Layer Current Performance is
Rate/Parameter and Granularity for a shown in tabular view for
Pass
running measurement type. chosen element(s).
2 Fail
Status and time of
N/A
measurements are
correct.
3.3.3 Historical Performance

Select one or more managed The Historical Pass
1 element(s). Invoke the Historical Performance dialog is Fail
Performance action. opened. N/A
Select Historical Table display with Data selection is
Custom duration and specify start and performed. Pass
2 stop time. Fail
Select 15 min granularity and one or N/A
more Layer Rate/Parameter.
Select OK in the dialog. If more than A tabular view is opened Pass
3 one view will be opened, a warning for each granularity. Fail
message will be displayed N/A
Select one or more managed The Historical Pass
4 element(s). Invoke the Historical Performance dialog is Fail
Performance action. opened. N/A
Select Time Series Graph display with Data selection is
Custom duration and specify start and performed. Pass
5 stop time. Select 15 min granularity Fail
and one or more Layer N/A
Rate/Parameter
Nera Networks AS
Page 12(83)

Select OK in the dialog. If more than A separate graph view is Pass
6 one view will be opened, a warning opened for each Fail
message will be displayed granularity and resource. N/A
3.3.4 Threshold Crossing Alarms (TCA)

Open TCA Templates View and A new TCA template is
create a new TCA template for an created.
existing network element type with Pass
1 running measurements. Set a Fail
trigger/clear pair of points that will be N/A
triggered during the next 15 min
period.
From one or more managed The template is assigned
element(s) of the same type as the to the chosen element(s).
Pass
newly created template, assign the
2 Fail
template from the element popup-
N/A
menu Performance -> TCA Templates
Assignment.
Wait for the next 15 min performance Alarms are raised in Pass
3 measurements to arrive in NetMaster. NetMaster according to Fail
TCA template setting. N/A
Nera Networks AS
Page 13(83)
3.4 Security Management
3.4.1 Group and User Management

Open User Management perspective Perspective is opened.
Normally the Group
Administration and User Pass
1 Administration views will Fail
be open – if not they can N/A
be opened from the view
menu.
Create a new user group and assign A new user group is
Pass
Action Permissions to Topology and created.
2 Fail
Resource Permissions to one
N/A
particular domain only and then save.
Create a new user, assigned to the A new user is created. Pass
3 newly created group and then save. Fail
N/A
Log off and log on again with The NetMaster client
Pass
credentials of the newly created user. starts with the assigned
4 Fail
Action Permissions and
N/A
Resource Permissions.
3.4.2 User Audit Data Logging

From NetMaster client logon dialog, Login/logout successful. Pass
1 log on and off with different valid Fail
users. N/A
Try to log on with an invalid username Login not successful. Pass
2 or password. Fail
N/A
Change the password of a user from Password changed Pass
3 the Preference pages successfully. Fail
N/A
From NetMaster client, logon with User Audit view opens. Pass
4 user root. Operations in step 1, 2 Fail
Open the User Audit View and 3 are reported. N/A
Create, Update and Delete user(s) Operations are reported Pass
5 Refresh the User Audit view in User Audit view Fail
N/A
Change Resource Permissions for a Operations are reported Pass
5 user group. in User Audit View Fail
Refresh the User Audit view N/A
Change Action Permissions for a user Operations are reported Pass
6 group in User Audit View Fail
Refresh the User Audit view N/A
Change group membership for a user. Operations are reported Pass
7 Refresh the User Audit view in User Audit View Fail
N/A
Nera Networks AS
Page 14(83)
3.4.3 User Audit Filtering

Open View -> Other -> Filter Manager A new User Audit filter is
and create a new blank User Audit created.
filter. Under the user-account node,
Pass
enter the name of a user (other than
1 Fail
root) and save the filter.
N/A
Right-click on the new filter and select
Include in Favourites (for the current
user).
In the user audit log, open the Only entries regarding the Pass
2 favourite filter. user included in the newly Fail
created filter are shown. N/A
Nera Networks AS
Page 15(83)
3.5 Optional Features
3.5.1 Administrative Domains with Geographical Maps

Discover some elements. Use 5-10 Discovered elements are
Pass
elements of different kinds if possible. shown in the Unmanaged
1 Fail
(Or use elements already available in Elements view.
N/A
the Unmanaged Elements view).
Drag some unmanaged elements into The elements appear in
a domain in the geographical or logical the domain's map, and Pass
2 map. are removed from the Fail
Unmanaged Elements N/A
view.
In the Unmanaged Elements view, The Managed Elements Pass
3 select a number of elements dialog is displayed. Fail
Invoke Manage Element(s) action. N/A
Select the destination domain in the The selected elements Pass
4 dialog and press OK. appears in the domain, Fail
both in tree and map view N/A
Select a domain In the geographical The map view is Pass
5 tree view and invoke the Geographic displayed, showing the Fail
Map action. contents of the domain. N/A
In an open map view with (at least) a When the view opens
domain and an element, invoke the again, the positions of the
Pass
Select tool (arrow icon) and place the map items are according
6 Fail
objects as desired. to the saved state.
N/A
Press the view's save button, then
close the view and open it again.
In an open map view with (at least) a Elements are distributed Pass
7 domain and an element, invoke the side by side in a grid. Fail
Grid Layout action. N/A
In an open map view with (at least) a Elements are distributed Pass
8 domain and an element, invoke the randomly. Fail
Random Layout action. N/A
From the map view's pull-down menu, The Background Image
Pass
select the Background Image action. dialog is displayed, with
9 Fail
background settings for
N/A
the current map view.
Select the Use background image tick The selected background
Pass
box and select a background image image is displayed in the
10 Fail
from the Browse button. Select OK to map view.
N/A
close the Background Image dialog
Open a map view with a background The background image is
image and invoke the Background no longer displayed in the
Pass
Image action. In the Background map view.
11 Fail
Image dialog, deselect the Use
N/A
background image tick box and select
OK.
Nera Networks AS
Page 16(83)

Open a map view with an The domain is highlighted
administrative domain and invoke the and all points in the Pass
12 Edit Domain Outline action (hexagonal outline polygon are Fail
toolbar button). displayed. N/A
Select an administrative domain.
Select one of the points and drag it to The shape of the
Pass
a new position. administrative domain
13 Fail
Click outside the polygon. changes according to the
N/A
moved point.
Add a new point by holding CTRL The shape of the domain Pass
14 down while clicking near the border is changed according to Fail
inside the polygon. the added point. N/A
Remove a point by holding CTRL The shape of the domain Pass
15 down while clicking on the point. is changed according to Fail
the removed point. N/A
3.5.2 Report Generator

Select Reports -> Inventory Report Inventory Report is Pass
1 from the popup menu of a network shown for the chosen Fail
element. element. N/A
Click on the printer icon in the upper Inventory Report can be Pass
2 left part of the Inventory Report view exported to PDF file or Fail
MS Office document. N/A
Select Reports -> Inventory Report Inventory Report is
Pass
from the popup menu of a domain or shown for the
3 Fail
from the main menu View -> Reports corresponding elements.
N/A
-> Inventory Reports (whole network)
Invoke other report types from All different reports can
Pass
element popup menus or main menu. be started and results can
4 Fail
be exported to PDF files
N/A
or MS Office documents.
3.5.3 SNMP Northbound Interface

Note: For this test, an additional computer (external manager) with a MIB browser must be available (for
instance MG-Soft).

Ensure NetMaster SNMP Agent is The agent icon, with a Pass
1 running. green square, should be Fail
present in system tray. N/A
Open MIB in MIB browser and MIB browser connects to Pass
2 connect to the NetMaster SNMP the agent. Fail
agent. N/A
Open in the MIB tree: Table view in browser
iso.org.dod.internet.mgmt.private.ente shows all active alarms Pass
3 rprises.nera.neraProducts.nmsProduc present in the system. Fail
ts.netMaster.netMasterAlarms.netmas N/A
terAlarmTable.
Nera Networks AS
Page 17(83)

Open in the MIB tree: Notifications (traps) are
iso.org.dod.internet.mgmt.private.ente re-sent for all active Pass
4 rprises.nera.neraProducts.nmsProduc alarms in the system. Fail
ts.netMaster.netMasterAlarms.netmas N/A
terSyncAlarms and send 162
Acknowledge an active alarm in External manager Pass
5 NetMaster. receives notification that Fail
alarm is acknowledged. N/A
Toggle on and off an alarm on a Alarms are received by Pass
6 managed element. the external manager. Fail
N/A
Open in the MIB tree: Table view in browser
Pass
iso.org.dod.internet.mgmt.mib- shows a list of all
7 Fail
2.entityMIB.entityMIBObjects.entityPh managed elements in the
N/A
ysical.entPhysicalTable. system.
3.5.4 Hot Standby Redundancy Tests, 2+2 HA system
Prerequisites:
- NetMaster and its corresponding database is installed on both primary/main/Site A and
standby/backup/Site B servers, with equal schema/user name
- Identify the (planned or already installed) server names, roles and other data in the table below
Initial role: “Primary NetMaster Server”

Computer name:
IP Address:
NMS-Server-A
NetMaster Version / Build:
License number:
Initial role: “Primary Database Server”
Computer name:
IP Address:
DB-Server-A
NetMaster DB Schema Name
Database Type / Version:
Initial role: “Standby NetMaster Server”
Computer name:
IP Address:
NMS-Server-B
NetMaster Version / Build:
License number:
Initial role: “Standby Database Server”
Computer name:
IP Address:
DB-Server-B
NetMaster DB Schema Name
Nera Networks AS
Page 18(83)
3.5.4.1 Hot Standby Redundancy, 2+2 HA system: Installation and Normal Operation
Step 1 - The purpose of this test is to All system data in the
Pass
Preparations configure and verify that the table in section 3.5.4
Fail
script based HA solution above is available N/A
performs the expected actions
Step 2 - Follow the NetMaster A 2+2 system is
Pass
Install Installation Guide and install a configured.
Fail
servers 2+2 system using 4 different N/A
computers.
Step 3 - Import a valid license to the NetMaster running on Pass
Import NetMaster servers and start the both "NMS-Server-A" Fail
license servers and "NMS-Server-B" N/A
Step 4 - On both NetMaster servers verify OK
Verify task that installer generates a tasks
Pass
catalogue catalogue with
Fail
netmaster_environment.cmd N/A
This contains the correct
parameters.
Step 5 - Follow the NetMaster On both database servers
Maintenance Maintenance guide and complete (DB-Server-A and DB-
configuration the NetMaster database Server-B)
environment preparations.
(Standard preparations) on both - Task folder copied to Pass
database servers (DB-Server-A the database server, Fail
and DB-Server-B) C:\Netmaster\Tasks N/A
- The
NetMaster_enivironment.
cmd file is edited.
Step 6 - DB- Perform a database export on Backup file created (See
export both database servers ("DB- NetMaster_Environment.
Server-A" and DB-Server-B") to cmd for path and
verify that the export script is filename)
Pass
functional
Fail
The backup file is greater N/A
Execute the script than zero KB
"run_netmaster_database_export.
cmd" located in the task folder
on the database server
Step 7 - If any NetMaster script files are No scheduled tasks are
Remove old scheduled on the database configured on the Pass
scheduled servers remove the scheduled database servers (DB- Fail
tasks tasks. Server-A and DB-Server- N/A
B)
Nera Networks AS
Page 19(83)

Step 8 - On the standby database server Backup folder on DB-
Share folder (DB-Server-B): Share the folder: Server-B shared
Pass
I .\tasks\backup\
Fail
N/A
Give full rights to modify the
content by everyone.
Step 9 On the primary database server Backup folder on DB-
Share folder (DB-Server-A): Share the folder: Server-A shared
Pass
II .\tasks\backup\ .
Fail
N/A
Step 10 - Copy the CONTENT of the The content of the
Copy new folder ha_tasks in to the existing ha_tasks folder is applied
script files tasks folders on BOTH database to the task folder on both Pass
servers DB-Server-A and DB- Fail
Server-B N/A
In any message about existing
files, overwrite the files
Step 11 - On the primary database server ha_netmaster_environme
Edit (DB-Server-A): Open the file nts configured
environment \tasks\ha_netmaster_environment
file I .cmd in notepad.
Assign the necessary values to

the parameters described below:
-
RESTORE_DATABASE_SERV
ER_UNC_SHARE=<The path to Pass
shared folder on the database Fail
server to receive backups after N/A
export (during normal operation),
e.g. \\mystandbyserver\backup\>
-
NETMASTER_SERVER_ADD
RESS=<The IP address of the
NetMaster server which should
be started and stopped during
restore.>
Step 12 - On the primary database server "ha_run_netmaster-
Add DB-Server-A: database_export.cmd"
scheduled Add the file scheduled on the primary Pass
task "ha_run_netmaster_database_exp database server Fail
ort.cmd" to scheduled tasks in N/A
windows. Schedule it to run
every day at e.g. 1.00 am.
Nera Networks AS
Page 20(83)

Step 13 - On the standby database server ha_netmaster_environme
Edit (DB-Server-B): nts configured on the
environment standby database server
file II Open the file
\tasks\ha_netmaster_environment
.cmd in notepad.
-
Pass
ER_UNC_SHARE=<The path to
Fail
shared folder on the database N/A
server to receive backups after
export (during “reversed”
operation), e.g.
\\myprimaryserver\backup\>
-
restore.>
Step 14 - On the standby database server "ha_run_netmaster-
Add (DB-Server-B): database_restore.cmd"
scheduled Add the file: scheduled on the standby Pass
task \tasks\ha_run_netmaster_databas database server Fail
e_restore.cmd to scheduled tasks N/A
in windows. Schedule it to run
Step 15 - On the primary NetMaster server Elements discovered and
Log on (NMS-Server-A) log on to set to managed state
NetMaster NetMaster client.
Pass
Make notes of how many
Fail
Discover and manage some elements are discovered N/A
elements. and how many elements
that are set to managed
state.
Step 16 - HA On the primary database server Export started
Pass
DB Export DB-Server-A execute the script
Fail
"ha_run_netmaster_database_exp N/A
ort.cmd"
Nera Networks AS
Page 21(83)

Step 17 - When the export is finished Export finished ok,
Verify DB verify that the export file is backup file created on the
Export created on the primary database primary database server
server (DB-Server-A)
Filename:
0_netmaster_database.backup
Folder: ..\tasks\backup (DB-
Pass
Server-A)
Fail
N/A
Make a note of the starting time
of this operation for later
reference.
Make a note of the resulting

backup file size (before and after
compression, if applicable) for
later reference.
Step 18 - Verify that the backup file copied Backup file copied to the
Verify Copy to the standby database server standby database server
of backup (DB-Server-B) and that the (DB-Server-B), file size
file and backup file is renamed. same as on the primary
correct task database server (ref. step
scheduling Filename: 17)
Rnetmaster_database.backup
Folder: ..\tasks\backup (DB- The filename is renamed
Server-B) to
Rnetmaster_database.bac
Check file size of the backup file kup
that arrived on DB-Server-B
Pass
(before and after unzipping, if Old restore backup files
Fail
applicable) are renamed and prefixed N/A
with
Calculate the duration from start X_Rnetmaster.backup (X
of export (in step 17 above) until = number of the old
completed file transfer. restored backup set)
The duration of the file

export and transfer is well
within the time margins
between the scheduled
export set in step 12, and
the start of import set in
step 14.
Nera Networks AS
Page 22(83)

Step 19 - Open the client on the standby NetMaster is running on
Check for NetMaster server (NMS-Server- the standby NetMaster
changes B) and verify that NetMaster is server (NMS-Server-B). Pass
running. Fail
No discovered or N/A
Verify that there are still no managed elements are
discovered or managed elements stored in the database.
Step 20 - On the standby database server The restore process of the
Restore DB (DB-Server-B) execute the script database on the standby Pass
HA_run_netmaster_database_res database server starts Fail
tore (located in the local "..\task" N/A
folder)
Step 21 - Verify that the standby Server icon indicates that
NetMaster NetMaster server (NMS-Server- NetMaster server is not
stopped B) has stopped (server monitor running on the standby
icon) NetMaster server (NMS-
Server-B) Pass
Fail
If clients are connected to N/A
this NetMaster server an
error message connecting
to server should be
displayed.
Step 22 - Verify that the NetMaster server NetMaster server on the
Primary on the primary NetMaster server primary NetMaster server
NetMaster (NMS-Server-A) is running is still running
Pass
running
Fail
Check the state of the server N/A
monitor icon or connect a client
to the NetMaster server on NMS-
Server-A
Step 23 - When the restore process is The log lists a summary
Check log finished, open and check the HA- of the restore process.
file restore log on the standby Verify that elements
database server (DB-Server-B) discovered and managed
in Step 14 are reflected in
log file is located in the count of rows in the
Pass
(..\tasks\log\HA_restore.log) MED_DISCOVERED_E
Fail
LEMENTS and in the N/A
Verify that the filename of the STATE_MANAGED_EL
HA backup file is renamed to EMENTS tables
0_Rnetmaster_database.backup
(.\tasks\backup folder on the DB- The backup file on the
Server-B) standby database server is
renamed
Nera Networks AS
Page 23(83)

Step 24 - On the standby NetMaster server NetMaster running on
NetMaster (NMS-Server-B) right click on NMS-Server-B
started the server monitor icon and open
Pass
the server log.
Fail
N/A
Refresh/reopen the server log
and verify that the server has
started
Step 25 - On the standby NetMaster server NetMaster on the standby
Log on to use the client and connect to server are updated with
standby NetMaster on the standby changes
NetMaster NetMaster server (NMS-Server-
server B)
Pass
Fail
Verify that the restore process N/A
has updated the standby database
(DB-Server-B), elements
discovered and set to managed
state are present on the standby
solution
Log on (NMS-Server-A) log on to set to managed state
Primary NetMaster.
Pass
NetMaster Make notes of how many
Fail
server Discover and manage some more elements are discovered N/A
elements. (create a new domain and how many elements
for the managed elements) that are set to managed
state.
Pass
Export DB-Server-A execute the script
Fail
ort.cmd"
Step 28 - HA On the standby database server The restore process of the
Restore (DB-Server-B) execute the script database on the standby Pass
folder)
Nera Networks AS
Page 24(83)

Step 29 - On the standby NetMaster server NetMaster is running on
Standby db (NMS-Server-B), wait until the standby NetMaster
updated NetMaster is started server.
The standby database are
Connect to NetMaster on NMS- updated,
Server-B - new domain created
- new discovered Pass
Verify that the restore process elements Fail
has updated the standby database - new managed elements N/A
(DB-Server-B), added to the newly
created domain
NetMaster on the standby

server are updated with
changes
3.5.4.2 HA Restore, 2+2 HA system - no existing restore backup file

Preparations verify that the restore table in section 3.5.4
Pass
procedure in the new script above is available
Fail
based HA solution does not N/A
perform any action if no HA
restore backup file is available
Step 2 - Precondition: The script based High
Precondition Before running this test, you Availability system is "up
must have installed and and running" with NMS-
configured the script based Server-A as primary Pass
HA solution on a 2+2 system server, and NMS-Server- Fail
using 4 different computers. B and DB-Server-B N/A
NMS-Server-A and DB- running as a backup
Server-A running as primary server.
servers.
Step 3 - On the standby database No backup files named
Verify no server, verify that no new HA Rnetmaster_database.bac
new restore backup files are available for kup are available on the
file on server restoring standby database server
(DB-Server-B)
Open the ..\task\backup folder Pass
on DB-Server-B look for If old HA backup files Fail
backup files named exist on the server they N/A
Rnetmaster_database.backup should be named
X_Rnetmaster_database.b
ackup (X is the number of
old restored backup e.g.
0, 1 or 2.....)
Nera Networks AS
Page 25(83)

Restore (DB-Server-B) execute the database on the standby
Pass
script database server starts
Fail
HA_run_netmaster_database_r N/A
estore (located in the local
"..\task" folder)
Step 5 - Verify that the restore process Backup process aborted
Restore on the standby database is
finished aborted due to missing backup NetMaster is not affected
file (check the HA restore log on the standby NetMaster
on the DB-Server-B) server (NMS-Server-B)
HA Restore log located on the
standby database server, DB- HA Restore log state that
Server-B should indicate that the backup is aborted due
Pass
the backup is aborted due to to missing backup file
Fail
missing backup file) N/A
Verify that the running

standby NetMaster server
NMS-Server-B is not stopped
and restarted during the restore
process ( monitor the
NetMaster server icon and
server log on NMS-Server-B)
Nera Networks AS
Page 26(83)
3.5.4.3 HA Export, 2+2 HA system - Number of export files to keep

Preparations verify that if the HA Export table in section 3.5.4
task is performed several times above is available Pass
before the restore is executed Fail
the Restore backup set is N/A
replaced and updated on the
standby server
configured the script based Server-A as primary Pass
using 4 different computers. B and DB-Server-B N/A
NMS-Server-A and DB- running as a backup
Server-A running as primary server.
servers.
Step 3 Edit the environment file on Netmaster_environment.c
both database server md edited on both db
(Netmaster_environment.cmd) servers (DB-Server-A
and DB-Server-B) Pass
Change the value for the Fail
Database Export and backup N/A
parameter SET
DB_EXPORTS_TO_KEEP to
3
Step 4 On the primary database No old
server open the backup folder X_netmaster_database.ba
Pass
(..\tasks\backup). If old backup ckup files exists in the
Fail
files exist delete them. backup folder on the N/A
primary database server
DB-Server-A
Step 5 - HA On the primary database Export started
DB Export server DB-Server-A execute Pass
the script Fail
"ha_run_netmaster_database_e N/A
xport.cmd"
Export created on the primary primary database server
database server (DB-Server-A) Pass
Fail
Filename: Timestamp of the file is N/A
0_netmaster_database.backup the time when the export
Folder: ..\tasks\backup (DB- was performed on DB-
Server-A) Server-A
Nera Networks AS
Page 27(83)

Step 7 - Verify that the backup file Backup file copied to the
Verify Copy copied to the standby database standby database server
of backup server (DB-Server-B) and that (DB-Server-B)
file the backup file is renamed.
The filename is renamed
Filename: to
Rnetmaster_database.backup Rnetmaster_database.bac
Folder: ..\tasks\backup (DB- kup
Server-B)
Timestamp of the file is Pass
the time when the export Fail
was performed on DB- N/A
Server-A (Step 5)
Note! If old restored

backup files exists they
are prefixed with
X_Rnetmaster.backup (X
= number of the old
restored backup set)
Step 8 - HA On the primary database Export started
DB Export server DB-Server-A execute Pass
the script Fail
xport.cmd"
Export created on the primary primary database server
database server (DB-Server-A)
Filename: Timestamp of the file is

Folder: ..\tasks\backup (DB- was performed on DB- Pass
Server-A) Server-A Fail
N/A
Timestamp of the file is the The old backup file from
time when the export was step 5 is renamed
performed on DB-Server-A
The old backup file created in

step 5 is now renamed to
Nera Networks AS
Page 28(83)

Step 10 - On the standby database server Backup file copied to the
Verify Copy DB-Server-B: verify that there standby database server
of backup is only one backup file named and replaces the old HA
file Rnetmaster_database.backup backup file(DB-Server-B)
The timestamp and the file The filename is renamed

size of the to
file is the same as the exported kup
backup file in step 8 (the new
0_netmaster_database.backup The file size and Pass
file the DB-Server-A) timestamp of the file is Fail
the time when the export N/A
was performed in step 8
on DB-Server-A

are prefixed with
= number of the old
Step 11 On the primary database Three HA database
server DB-Server-A execute exports run on the Pass
the script primary database server Fail
"ha_run_netmaster_database_e (DB-Server-A) N/A
xport.cmd" three more times
Nera Networks AS
Page 29(83)

Step 12 - The HA Export is now Only three backup files
Maximum performed 5 times on the are stored in the backup
export primary database server (DB- folder on the primary
number Server-A). database server (DB-
Server-A)
The number of Database
Exports to keep is set to 3
Verify that the backup folder

on the primary database server Pass
only contains three backup Fail
files (...\tasks\backup) N/A
0_Netmaster_database.backup
The backup file

should have the newest time
stamp
Step 13 - On the standby database server Backup file copied to the
Verify Copy DB-Server-B: verify that there standby database server
of backup is only one backup file named and replaces the old HA
file Rnetmaster_database.backup backup file(DB-Server-B)

size of the to
file is the same as the latest kup
exported backup file in step 11
(the new The file size and Pass
0_netmaster_database.backup timestamp of the file is Fail
file the DB-Server-A) the time when the export N/A
on DB-Server-A

are prefixed with
= number of the old
Nera Networks AS
Page 30(83)
3.5.4.4 HA Export Restore, 2+2 HA system - Number of HA restore files to keep

Preparations verify that if the HA Restore task table in section 3.5.4
Pass
is performed several times the above is available
Fail
correct amount of restore backup N/A
files are kept on the standby
server
Precondition Before running this test, you Availability system is
must have installed and "up and running" with
Pass
configured the script based HA NMS-Server-A as
Fail
solution on a 2+2 system using 4 primary server, and N/A
different computers. NMS- NMS-Server-B and
Server-A and DB-Server-A DB-Server-B running
running as primary servers. as a backup server.
Step 3 Edit the environment file on both Netmaster_environmen
database server t.cmd edited on both db
(Netmaster_environment.cmd) servers (DB-Server-A
Pass
and DB-Server-B)
Fail
Change the value for the N/A
Database Export and backup
parameter SET
DB_EXPORTS_TO_KEEP to 3
Step 4 On the both the primary database No old backup files
server and the standby server exists in the backup
open the backup folder folder on both servers
(..\tasks\backup). If old backup (DB-Server-A and DB-
files exist delete them. Server-B) Pass
Fail
Both N/A
"X_Rnetmaster_database.backup
" and
"X_netmaster_database.backup"
files
Nera Networks AS
Page 31(83)

Step 5 - HA 1. On the primary database 1. Export completed,
DB Export / server DB-Server-A: backup file
HA Restore - Execute the script (Rnetmaster_database.
"ha_run_netmaster_database_exp backup) copied to the
ort.cmd" standby database
server (DB-Server-B) Pass
When the export is finished Fail
2. Restore completed N/A
2. Move to the standby database successfully
server DB-Server-B:
- Execute the script
"ha_run_netmaster_datbase_rest
ore"
Step 6 - Re-run step 5 four times The HA Export and
Pass
Rerun HA Restore is executed
Fail
Export/Rest five times N/A
ore
Maximum performed 5 times on the primary are stored in the
export database server (DB-Server-A). backup folder on the
number primary database
The number of Database Exports server (DB-Server-A)
to keep is set to 3
Verify that the backup folder on

the primary database server only
Pass
contains three backup files
Fail
(...\tasks\backup) N/A
The backup file

stamp
Nera Networks AS
Page 32(83)

Step 8 - The HA Restore is now Only three restore
Maximum performed 5 times on the standby backup files are stored
Restore database server (DB-Server-B). in the backup folder on
number the primary database
The number of Database server (DB-Server-A)
Export/Restore files to keep is set
to 3

the standby database server only Pass
contains three archived restore Fail
backup files (...\tasks\backup) N/A
The restore file

stamp
Nera Networks AS
Page 33(83)
3.5.4.5 Schedule export and restore, 2+2 HA system

Preparations verify that if the HA table in section 3.5.4 Pass
Export/Restore task is above is available Fail
performed correctly using N/A
scheduled tasks
configured the script based Server-A and DB-Server- Pass
HA solution on a 2+2 system A as primary server, and Fail
using 4 different computers. NMS-Server-B and DB- N/A
NMS-Server-A and DB- Server-B running as a
Server-A running as primary backup server.
servers.
Step 3 - 1. On the both the primary 1. No old backup files
Remove old database server and the exist in the backup folder
files standby server open the on both servers (DB-
backup folder Server-A and DB-Server-
(..\tasks\backup). B)
If old backup files exist delete 2. No old log files exist in

them. Both the log folder on both
"X_Rnetmaster_database.back servers (DB-Server-A
up" and and DB-Server-B)
"X_netmaster_database.backu Pass
p" files Fail
N/A
2. On the both the primary
database server and the
standby server open the log
folder (..\tasks\log).
If old log files exist delete

them. Both
"HA_Netmaster_database_exp
ort.log" and
“HA_netmaster_restore.log"
Nera Networks AS
Page 34(83)

Step 4 - 1. On the primary database Five "Export tasks"
Schedule server DB-Server-A: scheduled during the
HA DB - Schedule the script night
Export "ha_run_netmaster_database_e
xport.cmd" five times
(spread the scheduled tasks Pass

during the night. e.g. Export 1 Fail
- 01:00 AM, Export 2 - 02:00 N/A
AM ......)
NOTE! Make sure that the

export on DB-Server-A is
finished before the next export
task is scheduled to start.
Step 5 - 1. On the standby database Five "Restore tasks"
Schedule server DB-Server-B: scheduled during the
Restore "ha_run_netmaster_database_r
estore.cmd" five times
(spread the scheduled tasks

during the night. e.g. Export 1
- 01:30 AM, Export 2 - 02:30 Pass
AM ......) Fail
N/A
restore on DB-Server-B is
finished and NetMaster on
NMS-Server-B is properly
started before the next export
task on DB-Server-A is
scheduled to start (Export in
step 4).
Step 6 - Wait until the last scheduled All scheduled tasks are
Pass
Wait task is completed (Restore executed
Fail
number 5 on the Standby N/A
database server (DB-Server-B)
Step 7 - Verify that NetMaster is It is possible to connect a
Pass
Verify running on both NetMaster client to each NetMaster
Fail
NetMaster servers (NMS-Server-A and server and monitor the N/A
running NMS-Server-B) network
Nera Networks AS
Page 35(83)

Step 8 - On the Primary database All exports completed
Verify Export server (DB-Server-A) open the successfully.
log HA_Netmaster_database_expo
rt.log filer Number of alarms in
(C:\Netmaster\tasks\log) STATE_ALARMS table
are noted
Pass
Verify that all the scheduled
Fail
exports are completed N/A
successfully.
Take notes of the number of

alarms in the
STATE_ALARMS table from
the last export
Step 9 - On the Standby database All restores completed
Verify server (DB-Server-B) open the successfully.
Restore log HA_Netmaster_restore.log
filer (C:\Netmaster\tasks\log) Number of
imported/restored alarms
Verify that all the scheduled in STATE_ALARMS
Pass
restores are completed table is the same as the
Fail
successfully. number of exported N/A
alarms from step 8.
On the last restore compare the
number of imported rows to
the table STATE_ALARMS
with the number of exported
rows in step 8.
Nera Networks AS
Page 36(83)
3.5.4.6 Oracle error on primary DB Server, 2+2 HA system

Preparations verify that the HA Export does table in section 3.5.4
Pass
not copy a restore/backup file above is available
Fail
to the standby database server N/A
if a error situation occurs on
the primary database server
configured the script based Server-A and DB-Server- Pass
HA solution on a 2+2 system A as primary server, and Fail
using 4 different computers. NMS-Server-B and DB- N/A
NMS-Server-A and DB- Server-B running as a
Server-A running as primary backup server.
servers.
Step 3 - On the standby database server No restore backup file
Remove (DB-Server-B) open the exist in the backup folder
restore file backup folder on the standby database
(..\tasks\backup). If an old server (DB-Server-B) Pass
restore backup file exists Fail
delete it. N/A
File name:
"Rnetmaster_database.backup"
Step 4 - Create an error-situation on - Oracle listener stopped
Generate System A by stopping the
error- Oracle listener on DB-server -
situation A logon_database_as_NMS
script reports connection
(e.g. stop the service, error:
Pass
OracleOraDB10g_home1TNS ERROR:
Fail
Listener) ORA-12541: TNS:no N/A
listener
Use the
"logon_database_as_NMS.cm
d" script in the task folder on
DB-Server-A to verify oracle
error
Step 5 - HA On the primary database Export started and
DB Export server DB-Server-A execute aborted due to connection Pass
the script problems Fail
xport.cmd"
Nera Networks AS
Page 37(83)

Step 6 - Open the HA export log file 1. Log contains
Verify HA on the primary database information about aborted
Export log server, DB-Server-A export. Example of error
message:
(..\tasks\log\HA_netmaster_ek
sport)
Start: Export NetMaster
1. Verify that the log indicates database schema
that the export is aborted NetMaster NMSDB
Export: Release
10.2.0.1.0 - Production
on Wed Sep 16 13:06:40
2009
Copyright (c) 1982, 2005,
Oracle. All rights Pass
reserved. Fail
EXP-00056: ORACLE N/A
error 12541 encountered
ORA-12541: TNS:no
listener
EXP-00000: Export
terminated
unsuccessfully
.
Failed to export because
of database connection
problems. Verify that the
database is up and
running
and retry the procedure.
.
Step 7 - Verify that no new The Backup/restore file is
Restore file backup/restore file is copied to not copied to the standby
not copied the standby database server database server (DB-
(DB-Server-B) Server-B) Pass
Fail
Filename: N/A
Server-B)
3.5.5 Hot Standby Redundancy Tests, 2+2 HA system, Reversed Operation
Prerequisites:
- System was originally set up according to section 3.5.4.
- No system settings are changed for this test – just the perceived role of the two systems.
Nera Networks AS
Page 38(83)
Reversed role: “Standby NetMaster Server”

NMS-Server-A Computer name:
IP Address:
Reversed role: “Standby Database Server”
DB-Server-A Computer name:
IP Address:
Reversed role: “Primary NetMaster Server”
NMS-Server-B Computer name:
IP Address:
Reversed role: “Primary Database Server”
DB-Server-B Computer name:
IP Address:
Nera Networks AS
Page 39(83)
3.5.5.1 Hot Standby Redundancy (reversed operation) , 2+2 HA system

script based HA solution above is available Pass
performs the expected actions Fail
after a switch-over from initial N/A
primary server to the initial
standby server.
Step 15 - On the currently primary Elements discovered and
Log on NetMaster server (NMS-Server- set to managed state
NetMaster B) log on to NetMaster client.
Pass
Fail
state.
Pass
DB Export DB-Server-B execute the script
Fail
ort.cmd"
Export created on the current primary primary database server
database server (DB-Server-B)
Filename:
Pass
Server-B)
Fail
N/A
reference.

later reference.
Nera Networks AS
Page 40(83)

Step 18 - Verify that the backup file was Backup file copied to the
Verify Copy copied to the currently standby standby database server
of backup database server (DB-Server-A) (DB-Server-A), file size
file and and that the backup file is same as on the primary
correct task renamed. database server (ref. step
scheduling 17)
Filename:
Rnetmaster_database.backup The filename is renamed
Folder: ..\tasks\backup (DB- to
Server-A) Rnetmaster_database.bac
kup
Check file size of the backup file Pass
that arrived on DB-Server-A Old restore backup files Fail
(before and after unzipping, if are renamed and prefixed N/A
applicable) with
Calculate the duration from start = number of the old
of export (in step 17 above) until restored backup set)
completed file transfer.
export, and the start of
import.
Check for NetMaster server (NMS-Server- the standby NetMaster
changes A) and verify that NetMaster is server (NMS-Server-A). Pass
running. Fail
No discovered or N/A
Verify that there are still no managed elements are
discovered or managed elements stored in the database.
Restore DB (DB-Server-A) execute the script database on the standby Pass
folder)
NetMaster NetMaster server (NMS-Server- NetMaster server is not
stopped A) has stopped (server monitor running on the standby
icon) NetMaster server (NMS-
Server-A) Pass
Fail
to server should be
displayed.
Nera Networks AS
Page 41(83)

NetMaster (NMS-Server-B) is running is still running
Pass
running
Fail
to the NetMaster server on NMS-
Server-B
Check log finished open and check the HA- of the restore process.
file restore log on the standby Verify that elements
database server (DB-Server-A) discovered and managed
Pass
Fail
(.\tasks\backup folder on the DB- The backup file on the
Server-A) standby database server is
renamed
Step 24 - On the standby NetMaster server NetMaster running on
NetMaster (NMS-Server-A) right click on NMS-Server-A
started the server monitor icon and open
Pass
the server log.
Fail
N/A
Refresh/reopen the server log
started
Step 25 - On the standby NetMaster server NetMaster on the standby
Log on to use the client and connect to server are updated with
standby NetMaster on the standby changes
NetMaster NetMaster server (NMS-Server-
server A)
Pass
Fail
Verify that the restore process N/A
has updated the standby database
(DB-Server-A), elements
discovered and set to managed
state are present on the standby
solution
Nera Networks AS
Page 42(83)

Log on (NMS-Server-B) log on to set to managed state
Primary NetMaster.
Pass
NetMaster Make notes of how many
Fail
server Discover and manage some more elements are discovered N/A
elements. (create a new domain and how many elements
for the managed elements) that are set to managed
state.
Pass
Export DB-Server-B execute the script
Fail
ort.cmd"
Step 28 - HA On the standby database server The restore process of the
Restore (DB-Server-A) execute the script database on the standby Pass
folder)
Standby db (NMS-Server-A), wait until the standby NetMaster
updated NetMaster is started server.
Connect to NetMaster on NMS- updated,
Server-A - new domain created
- new discovered Pass
Verify that the restore process elements Fail
has updated the standby database - new managed elements N/A
(DB-Server-A), added to the newly
created domain

changes
3.5.5.2 HA Restore, 2+2 HA system - no existing restore backup (reversed operation)

Pass
Fail
Nera Networks AS
Page 43(83)

configured the script based Server-B as primary Pass
using 4 different computers. A and DB-Server-A N/A
NMS-Server-B and DB- running as a backup
Server-B running as primary server.
servers.
Step 3 - On the standby database No backup files named
Verify no server, verify that no new HA Rnetmaster_database.bac
new restore backup files are available for kup are available on the
file on server restoring standby database server
(DB-Server-A)
Open the ..\task\backup folder Pass
on DB-Server-A look for If old HA backup files Fail
backup files named exist on the server they N/A
0, 1 or 2.....)
Restore (DB-Server-A) execute the database on the standby
Pass
script database server starts
Fail
HA_run_netmaster_database_r N/A
estore (located in the local
"..\task" folder)
on the DB-Server-A) server (NMS-Server-A)
standby database server, DB- HA Restore log state that
Server-A should indicate that the backup is aborted due
Pass
the backup is aborted due to to missing backup file
Fail
missing backup file) N/A

NMS-Server-A is not stopped
and restarted during the restore
server log on NMS-Server-A)
Nera Networks AS
Page 44(83)
3.5.5.3 Schedule export and restore (reversed operation) , 2+2 HA system

scheduled tasks
configured the script based Server-B and DB-Server- Pass
HA solution on a 2+2 system B as primary server, and Fail
using 4 different computers. NMS-Server-A and DB- N/A
NMS-Server-B and DB- Server-A running as a
Server-B running as primary backup server.
servers.
Remove old database server and the exist in the backup folder
files standby server open the on both servers (DB-
backup folder Server-A and DB-Server-
(..\tasks\backup). B)

"X_Rnetmaster_database.back servers (DB-Server-A
up" and and DB-Server-B)
"X_netmaster_database.backu Pass
p" files Fail
N/A
database server and the
standby server open the log
folder (..\tasks\log).

them. Both
ort.log" and
HA_netmaster_restore.log"
Nera Networks AS
Page 45(83)

Step 4 - 1. On the primary database Five "Export tasks"
Schedule server DB-Server-B: scheduled during the

- 01:00 AM, Export 2 - 02:00 N/A
AM ......)

export on DB-Server-B is
finished before the next export
task is scheduled to start.
Step 5 - 1. On the standby database Five "Restore tasks"
Schedule server DB-Server-A: scheduled during the

- 01:30 AM, Export 2 - 02:30 Pass
AM ......) Fail
N/A
restore on DB-Server-A is
finished and NetMaster on
NMS-Server-A is properly
started before the next export
task on DB-Server-B is
step 4).
Pass
Fail
database server (DB-Server-A)
Pass
Fail
NetMaster servers (NMS-Server-A and server and monitor the N/A
running NMS-Server-B) network
Nera Networks AS
Page 46(83)

Step 8 - On the Primary database All exports completed
Verify Export server (DB-Server-B) open the successfully.
are noted
Pass
Fail
successfully.

alarms in the
the last export
Step 9 - On the Standby database All restores completed
Verify server (DB-Server-A) open the successfully.
Pass
Fail
alarms from step 8.
rows in step 8.
Nera Networks AS
Page 47(83)
3.5.5.4 Oracle error on primary DB Server (reversed operation) , 2+2 HA system

Pass
Fail
to the standby database server N/A
if a error situation occurs on
the primary database server
configured the script based Server-B and DB-Server- Pass
HA solution on a 2+2 system B as primary server, and Fail
using 4 different computers. NMS-Server-A and DB- N/A
NMS-Server-B and DB- Server-A running as a
Server-B running as primary backup server.
servers.
Step 3 - On the standby database server No restore backup file
Remove (DB-Server-A) open the exist in the backup folder
restore file backup folder on the standby database
(..\tasks\backup). If an old server (DB-Server-A) Pass
restore backup file exists Fail
delete it. N/A
File name:
Generate System B by stopping the
error- Oracle listener on DB-server B -
situation logon_database_as_NMS
(e.g. stop the service, script reports connection
OracleOraDB10g_home1TNS error: Pass
Listener) ERROR: Fail
ORA-12541: TNS:no N/A
Use the listener
DB-Server-B to verify oracle
error
Step 5 - HA On the primary database Export started and
DB Export server DB-Server-B execute aborted due to connection Pass
the script problems Fail
xport.cmd"
Nera Networks AS
Page 48(83)

Verify HA on the primary database information about aborted
Export log server, DB-Server-B export. Example of error
message:
sport)
Export: Release
on Wed Sep 16 13:06:40
2009
reserved. Fail
ORA-12541: TNS:no
listener
EXP-00000: Export
terminated
unsuccessfully
.
database is up and
running
.
not copied the standby database server database server (DB-
(DB-Server-A) Server-A) Pass
Fail
Filename: N/A
Server-A)
Nera Networks AS
Page 49(83)
3.5.6 Hot Standby Redundancy Tests, 1+1 HA system
Prerequisites:
- NetMaster and its corresponding database is installed on both primary/main/Site A and
standby/backup/Site B server, with equal schema/user name
- Identify the (planned or already installed) server names, roles and other data in the table below
Initial role: “Primary Server”

Computer name:
IP Address:
NMS and NetMaster Version / Build:
DB installed on
License number:
Server-A
NetMaster DB Schema Name:
Initial role: “Standby Server”
Computer name:
IP Address:
NMS and NetMaster Version / Build:
DB installed on
License number:
Server-B
NetMaster DB Schema Name:
Nera Networks AS
Page 50(83)
3.5.6.1 Hot Standby Redundancy, 1+1 HA system: Installation and Normal Operation
Pass
Fail
script based HA solution above is available N/A
performs the expected actions
Step 2 - Follow the NetMaster A 1+1 system is
Install Installation Guide and install a configured. (NetMaster
Pass
servers 1+1 system using 2 different server and database
Fail
computers. server on the same N/A
computer)
Step 3 - Import a valid license to the NetMaster running on Pass

Import NetMaster servers and start the both "Server-A" and Fail
license servers "Server-B" N/A
Step 4 - On both NetMaster servers verify OK
Verify task that installer generates a tasks
Pass
catalogue catalogue with
Fail
netmaster_environment.cmd N/A
This contains the correct
parameters.
Step 5 - Follow the NetMaster On both servers (Server-
Maintenance Maintenance guide and complete A and Server-B)
configuration the NetMaster database
environment preparations. - Task folder copied to Pass
(Standard preparations) on both the, C:\Netmaster\Tasks Fail
servers (Server-A and Server-B) N/A
- The
NetMaster_enivironment.
cmd file is edited.
Step 6 - DB- Perform a database export on Backup file created (See
export both servers ("Server-A" and NetMaster_Environment.
Server-B") to verify that the cmd for path and
export script is functional filename) Pass
Fail
Execute the script The backup file is greater N/A
"run_netmaster_database_export. than zero KB
cmd" located in the task folder
on the server
Step 7 - If any NetMaster script files are No scheduled tasks are
Pass
Remove old scheduled on the servers remove configured on the servers
Fail
scheduled the scheduled tasks. (Server-A and Server-B) N/A
tasks
Step 8 - On the standby server (Server- Backup folder on Server-
Share folder B): Share the folder: B shared
Pass
I .\tasks\backup\
Fail
N/A
Nera Networks AS
Page 51(83)

Step 9 On the primary server (Server- Backup folder on Server-
Share folder A): Share the folder: A shared
Pass
II .\tasks\backup\ .
Fail
N/A
Step 10 - Copy the CONTENT of the The content of the
Copy new folder ha_tasks in to the existing ha_tasks folder is applied
Pass
script files tasks folders on BOTH servers to the task folder on both
Fail
Server-A and Server-B N/A
In any message about existing
files, overwrite the files
Step 11 - On the primary server (Server- ha_netmaster_environme
Edit A): Open the file nts configured
environment \tasks\ha_netmaster_environment
file I .cmd in notepad.

-
ER_UNC_SHARE=<The path to Pass
shared folder on the server to Fail
receive backups after export N/A
(during normal operation), e.g.
\\mystandbyserver\backup\>
-
restore.>
Step 12 - On the primary server Server-A: "ha_run_netmaster-
Add Add the file database_export.cmd"
Pass
scheduled "ha_run_netmaster_database_exp scheduled on the primary
Fail
task ort.cmd" to scheduled tasks in server N/A
windows. Schedule it to run
Nera Networks AS
Page 52(83)

Step 13 - On the standby server (Server- ha_netmaster_environme
Edit B): nts configured on the
environment standby server
file II Open the file
\tasks\ha_netmaster_environment
.cmd in notepad.
-
Pass
ER_UNC_SHARE=<The path to
Fail
shared folder on the server to N/A
receive backups after export
(during “reversed” operation),
e.g.
\\myprimaryserver\backup\>
-
restore.>
Step 14 - On the standby server (Server- "ha_run_netmaster-
Add B): database_restore.cmd"
scheduled Add the file: scheduled on the standby Pass
task \tasks\ha_run_netmaster_databas server Fail
e_restore.cmd to scheduled tasks N/A
in windows. Schedule it to run
Step 15 - On the primary server (Server-A) Elements discovered and
Log on log on to NetMaster client. set to managed state
NetMaster
Pass
Discover and manage some Make notes of how many
Fail
elements. elements are discovered N/A
and how many elements
state.
Step 16 - HA On the primary server Server-A Export started
Pass
DB Export execute the script
Fail
ort.cmd"
Nera Networks AS
Page 53(83)

Export created on the primary server primary server (Server-A)
Filename:
Folder: ..\tasks\backup (Server-
A) Pass
Fail
Make a note of the starting time N/A
reference.

later reference.
Step 18 - Verify that the backup file copied Backup file copied to the
Verify Copy to the standby server (Server-B) standby server (Server-
of backup and that the backup file is B), file size same as on
file and renamed. the primary server (ref.
correct task step 17)
scheduling Filename:
Folder: ..\tasks\backup (Server- to
B) Rnetmaster_database.bac
kup
Check file size of the backup file
that arrived on Server-B (before Old restore backup files Pass
and after unzipping, if are renamed and prefixed Fail
applicable) with N/A
export set in step 12, and
the start of import set in
step 14.
Check for server (Server-B) and verify that the standby server
changes NetMaster is running. (Server-B). Pass
Fail
Verify that there are still no No discovered or N/A
discovered or managed elements managed elements are
stored in the database.
Nera Networks AS
Page 54(83)

Step 20 - On the standby server (Server-B) The restore process of the
Restore DB execute the script database on the standby Pass
HA_run_netmaster_database_res server starts Fail
folder)
NetMaster NetMaster server (Server-B) has NetMaster server is not
stopped stopped (server monitor icon) running on the standby
NetMaster server (Server-
B) Pass
Fail
to server should be
displayed.
NetMaster (Server-A) is running is still running
Pass
running
Fail
to the NetMaster server on
Server-A
Check log finished, open and check the HA- of the restore process.
file restore log on the standby server Verify that elements
(Server-B) discovered and managed
Pass
Fail
(.\tasks\backup folder on the The backup file on the
Server-B) standby database server is
renamed
Step 24 - On the standby server (Server-B) NetMaster running on
NetMaster right click on the server monitor NMS-Server-B
started icon and open the server log. Pass
Fail
Refresh/reopen the server log N/A
started
Nera Networks AS
Page 55(83)

Step 25 - On the standby server use the NetMaster on the standby
Log on to client and connect to NetMaster server are updated with
standby on the standby server (Server-B) changes
NetMaster Pass
server Verify that the restore process Fail
has updated the standby database N/A
(Server-B), elements discovered
and set to managed state are
present on the standby solution
Step 26 - On the primary server (Server-A) Elements discovered and
Log on log on to NetMaster. set to managed state
Primary
Pass
NetMaster Discover and manage some more Make notes of how many
Fail
server elements. (create a new domain elements are discovered N/A
for the managed elements) and how many elements
state.
Step 27 - HA On the primary server Server-A Export started
Pass
Export execute the script
Fail
ort.cmd"
Step 28 - HA On the standby server (Server-B) The restore process of the
Restore execute the script database on the standby Pass
folder)
Standby db (Server-B), wait until NetMaster the standby NetMaster
updated is started server.
Connect to NetMaster on Server- updated,
B - new domain created
- new discovered
Verify that the restore process elements
has updated the standby database - new managed elements
(Server-B), added to the newly
Pass
created domain
Fail
N/A
changes
Nera Networks AS
Page 56(83)
3.5.6.2 HA Restore, 1+1 HA system - no existing restore backup file

Pass
Fail
must have installed and and running" with Server-
Pass
configured the script based A as primary server, and
Fail
HA solution on a 1+1 system Server-B as a backup N/A
using 2 different computers. server.
Server-A running as primary
server
Step 3 - On the standby server, verify No backup files named
Verify no that no new HA backup files Rnetmaster_database.bac
new restore are available for restoring kup are available on the
file on server standby database server
Open the ..\task\backup folder (Server-B)
on Server-B look for backup Pass
files named If old HA backup files Fail
Rnetmaster_database.backup exist on the server they N/A
should be named
0, 1 or 2.....)
Step 4 - On the standby server (Server- The restore process of the
Restore B) execute the script database on the standby Pass
HA_run_netmaster_database_r server starts Fail
estore (located in the local N/A
"..\task" folder)
Nera Networks AS
Page 57(83)

on the Server-B) server (Server-B)
standby server, Server-B HA Restore log state that
should indicate that the backup the backup is aborted due
Pass
is aborted due to missing to missing backup file
Fail
backup file) N/A

Server-B is not stopped and
restarted during the restore
server log on Server-B)
Nera Networks AS
Page 58(83)
3.5.6.3 HA Export, 1+1 HA system - Number of export files to keep

Preparations verify that if the HA Export table in section 3.5.6
task is performed several times above is available Pass
before the restore is executed Fail
the Restore backup set is N/A
replaced and updated on the
standby server
Pass
Fail
HA solution on a 1+1 system Server-B running as a N/A
using 2 different computers. backup server.
server.
Step 3 Edit the environment file on Netmaster_environment.c
both servers md edited on both servers
(Netmaster_environment.cmd) (Server-A and Server-B)
Pass
Change the value for the Fail
Database Export and backup N/A
parameter SET
DB_EXPORTS_TO_KEEP to
3
Step 4 On the primary server open the No old
backup folder X_netmaster_database.ba Pass
(..\tasks\backup). If old backup
ckup files exists in the Fail
files exist delete them. backup folder on the N/A
primary server Server-A
Step 5 - HA On the primary server Server- Export started
Pass
DB Export A execute the script
Fail
xport.cmd"
Pass
Fail
Filename: Timestamp of the file is N/A
Folder: ..\tasks\backup was performed on Server-
(Server-A) A
Nera Networks AS
Page 59(83)

Step 7 - Verify that the backup file Backup file copied to the
Verify Copy copied to the standby server standby server (Server-B)
of backup (Server-B) and that the backup
file file is renamed. The filename is renamed
to
Filename: Rnetmaster_database.bac
Rnetmaster_database.backup kup
Folder: ..\tasks\backup
(Server-B) Timestamp of the file is
Pass
the time when the export
Fail
was performed on Server- N/A
A (Step 5)

are prefixed with
= number of the old
Step 8 - HA On the primary server Server- Export started
Pass
DB Export A execute the script
Fail
xport.cmd"
Filename: Timestamp of the file is

Folder: ..\tasks\backup was performed on Server-
Pass
(Server-A) A
Fail
N/A
Timestamp of the file is the The old backup file from
time when the export was step 5 is renamed
performed on Server-A
The old backup file created in

step 5 is now renamed to
Nera Networks AS
Page 60(83)

Step 10 - On the standby server Server- Backup file copied to the
Verify Copy B: verify that there is only one standby server and
of backup backup file named replaces the old HA
file Rnetmaster_database.backup backup file(Server-B)

size of the to
file is the same as the exported kup
backup file in step 8 (the new
0_netmaster_database.backup The file size and Pass
file the Server-A) timestamp of the file is Fail
the time when the export N/A
on Server-A

are prefixed with
= number of the old
Step 11 On the primary server Server- Three HA database
Pass
A execute the script exports run on the
Fail
"ha_run_netmaster_database_e primary server (Server-A) N/A
xport.cmd" three more times
Maximum performed 5 times on the are stored in the backup
export primary server (Server-A). folder on the primary
number server (Server-A)
The number of Database
Exports to keep is set to 3
Verify that the backup folder

on the primary server only
Pass
contains three backup files
Fail
The backup file

stamp
Nera Networks AS
Page 61(83)

Step 13 - On the standby server Server- Backup file copied to the
Verify Copy B: verify that there is only one standby server and
of backup backup file named replaces the old HA
file Rnetmaster_database.backup backup file(Server-B)

size of the to
file is the same as the latest kup
exported backup file in step 11
(the new The file size and Pass
0_netmaster_database.backup timestamp of the file is Fail
file the Server-A) the time when the export N/A
on Server-A

are prefixed with
= number of the old
Nera Networks AS
Page 62(83)
3.5.6.4 HA Export Restore, 1+1 HA system - Number of HA restore files to keep

Preparations verify that if the HA Restore task table in section 3.5.6
Pass
is performed several times the above is available
Fail
correct amount of restore backup N/A
files are kept on the standby
server
Precondition Before running this test, you Availability system is
must have installed and "up and running" with Pass
configured the script based HA Server-A as primary Fail
solution on a 1+1 system using 2 server, and Server-B N/A
different computers. Server-A running as a backup
running as primary server. server.
Step 3 Edit the environment file on both Netmaster_environmen
servers t.cmd edited on both
(Netmaster_environment.cmd) servers (Server-A and
Pass
Server-B)
Fail
Change the value for the N/A
Database Export and backup
parameter SET
DB_EXPORTS_TO_KEEP to 3
Step 4 On the both the primary server No old backup files
and the standby server open the exists in the backup
backup folder (..\tasks\backup). folder on both servers
If old backup files exist delete (Server-A and Server-
them. B) Pass
Fail
Both N/A
"X_Rnetmaster_database.backup
" and
"X_netmaster_database.backup"
files
Nera Networks AS
Page 63(83)

Step 5 - HA 1. On the primary server Server- 1. Export completed,
DB Export / A: backup file
HA Restore - Execute the script (Rnetmaster_database.
"ha_run_netmaster_database_exp backup) copied to the
ort.cmd" standby server (Server-
B) Pass
When the export is finished Fail
2. Restore completed N/A
2. Move to the standby server successfully
Server-B:
- Execute the script
"ha_run_netmaster_datbase_rest
ore"
Step 6 - Re-run step 5 four times The HA Export and
Pass
Rerun HA Restore is executed
Fail
Export/Rest five times N/A
ore
Maximum performed 5 times on the primary are stored in the
export server (Server-A). backup folder on the
number primary server (Server-
The number of Database Exports A)
to keep is set to 3

the primary server only contains
Pass
three backup files
Fail
The backup file

stamp
Nera Networks AS
Page 64(83)

Step 8 - The HA Restore is now Only three restore
Maximum performed 5 times on the standby backup files are stored
Restore server (Server-B). in the backup folder on
number the standby database
The number of Database server (Server-B)
Export/Restore files to keep is set
to 3

the standby server only contains Pass
three archived restore backup Fail
files (...\tasks\backup) N/A
The restore file

stamp
Nera Networks AS
Page 65(83)
3.5.6.5 Schedule export and restore, 1+1 HA system

scheduled tasks
Pass
Fail
servers.
Remove old server and the standby server exist in the backup folder
files open the backup folder on both servers (Server-A
(..\tasks\backup). and Server-B)

"X_Rnetmaster_database.back servers (Server-A and
up" and Server-B)
"X_netmaster_database.backu
Pass
p" files
Fail
N/A
server and the standby server
open the log folder
(..\tasks\log).

them. Both
ort.log" and
“HA_netmaster_restore.log"
Nera Networks AS
Page 66(83)

Step 4 - 1. On the primary server Five "Export tasks"
Schedule Server-A: scheduled during the

- 01:00 AM, Export 2 - 02:00 N/A
AM ......)

export on Server-A is finished
before the next export task is
scheduled to start.
Step 5 - 1. On the standby server Five "Restore tasks"
Schedule Server-B: scheduled during the

Pass
- 01:30 AM, Export 2 - 02:30
Fail
AM ......) N/A

restore on Server-B is finished
and NetMaster on Server-B is
properly started before the
next export task on Server-A is
step 4).
Pass
Fail
database server (Server-B)
Pass
Fail
NetMaster servers (Server-A and Server- server and monitor the N/A
running B) network
Nera Networks AS
Page 67(83)

Step 8 - On the Primary server (Server- All exports completed
Verify Export A) open the successfully.
are noted
Pass
Fail
successfully.

alarms in the
the last export
Step 9 - On the Standby server (Server- All restores completed
Verify B) open the successfully.
Pass
Fail
alarms from step 8.
rows in step 8.
Nera Networks AS
Page 68(83)
3.5.6.6 Oracle error on primary Server, 1+1 HA system

Pass
Fail
to the standby server if a error N/A
situation occurs on the primary
database server
Pass
Fail
server.
Step 3 - On the standby server (Server- No restore backup file
Remove B) open the backup folder exist in the backup folder
restore file (..\tasks\backup). If an old on the standby server
Pass
restore backup file exists (Server-B)
Fail
delete it. N/A
File name:
Generate System A by stopping the
error- Oracle listener on server A -
Pass
OracleOraDB10g_home1TNS error:
Fail
Listener) ERROR: N/A
ORA-12541: TNS:no
Use the listener
Server-A to verify oracle error
Step 5 - HA On the primary server Server- Export started and
Pass
DB Export A execute the script aborted due to connection
Fail
"ha_run_netmaster_database_e problems N/A
xport.cmd"
Nera Networks AS
Page 69(83)

Verify HA on the primary server, Server- information about aborted
Export log A export. Example of error
message:
sport)
Export: Release
on Wed Sep 16 13:06:40
2009
reserved. Fail
ORA-12541: TNS:no
listener
EXP-00000: Export
terminated
unsuccessfully
.
database is up and
running
.
not copied the standby server (Server-B) server (Server-B)
Pass
Fail
Filename: N/A
(Server-B)
3.5.7 Hot Standby Redundancy Tests, 1+1 HA system, Reversed Operation
Prerequisites:
- System was originally set up according to section 3.5.6
- No system settings are changed for this test – just the perceived role of the two systems.
Nera Networks AS
Page 70(83)
Reversed role: “Standby Server”

NMS-Server-A and
Computer name:
DB-Server-A
IP Address:
Reversed role: “Primary Server”
NMS-Server-B and
Computer name:
DB-Server-B
IP Address:
Nera Networks AS
Page 71(83)
3.5.7.1 Hot Standby Redundancy (reversed operation) , 1+1 HA system

script based HA solution above is available Pass
performs the expected actions Fail
after a switch-over from initial N/A
primary server to the initial
standby server.
Step 15 - On the currently primary Elements discovered and
Log on NetMaster server (Server-B) log set to managed state
NetMaster on to NetMaster client.
Pass
Fail
state.
Step 16 - HA On the primary server Server-B Export started
Pass
DB Export execute the script
Fail
ort.cmd"
Export created on the current primary primary server (Server-B)
database server
Filename:
Folder: ..\tasks\backup (Server-
Pass
B)
Fail
N/A
reference.

later reference.
Nera Networks AS
Page 72(83)

Step 18 - Verify that the backup file was Backup file copied to the
Verify Copy copied to the currently standby standby server (Server-
of backup server (Server-A) and that the A), file size same as on
file and backup file is renamed. the primary database
correct task server (ref. step 17)
scheduling Filename:
Folder: ..\tasks\backup (Server- to
A) Rnetmaster_database.bac
kup
Check file size of the backup file
Pass
that arrived on Server-A (before Old restore backup files
Fail
and after unzipping, if are renamed and prefixed N/A
applicable) with
export, and the start of
import.
Check for NetMaster server (Server-A) and the standby NetMaster
changes verify that NetMaster is running. server (Server-A). Pass
Fail
Verify that there are still no No discovered or N/A
discovered or managed elements managed elements are
stored in the database.
Step 20 - On the standby server (Server-A) The restore process of the
Restore DB execute the script database on the standby Pass
folder)
NetMaster NetMaster server (Server-A) has NetMaster server is not
stopped stopped (server monitor icon) running on the standby
NetMaster server (Server-
A) Pass
Fail
to server should be
displayed.
Nera Networks AS
Page 73(83)

Primary on the primary NetMaster server primary server is still
NetMaster (Server-B) is running running
Pass
running
Fail
to the NetMaster server on
Server-B
Check log finished open and check the HA- of the restore process.
file restore log on the standby server Verify that elements
(Server-A) discovered and managed
Pass
Fail
(.\tasks\backup folder on the The backup file on the
Server-A) standby database server is
renamed
Step 24 - On the standby server (Server-A) NetMaster running on
NetMaster right click on the server monitor Server-A
started icon and open the server log. Pass
Fail
Refresh/reopen the server log N/A
started
Step 25 - On the standby server use the NetMaster on the standby
Log on to client and connect to NetMaster server (Server-A) are
standby on the standby server (Server-A) updated with changes
NetMaster Pass
server Verify that the restore process Fail
has updated the standby database N/A
(Server-A), elements discovered
and set to managed state are
present on the standby solution
Step 26 - On the primary server (Server-B) Elements discovered and
Log on log on to NetMaster. set to managed state
Primary
Pass
NetMaster Discover and manage some more Make notes of how many
Fail
server elements. (create a new domain elements are discovered N/A
for the managed elements) and how many elements
state.
Nera Networks AS
Page 74(83)

Step 27 - HA On the primary server Server-B Export started
Pass
Export execute the script
Fail
ort.cmd"
Step 28 - HA On the standby server (Server-A) The restore process of the
Restore execute the script database on the standby Pass
folder)
Step 29 - On the standby server (Server- NetMaster is running on
Standby db A), wait until NetMaster is the standby server.
updated started The standby database are
updated,
Connect to NetMaster on Server- - new domain created
A - new discovered
Pass
elements
Fail
Verify that the restore process - new managed elements N/A
has updated the standby database added to the newly
(Server-A), created domain

changes
3.5.7.2 HA Restore, 1+1 HA system - no existing restore backup (reversed operation)

Pass
Fail
Pass
configured the script based B as primary server, and
Fail
HA solution on a 1+1 system Server-A running as a N/A
Server-B running as primary
server.
Nera Networks AS
Page 75(83)

Step 3 - On the standby server, verify No backup files named
Verify no that no new HA backup files Rnetmaster_database.bac
new restore are available for restoring kup are available on the
file on server standby server (Server-A)
Open the ..\task\backup folder
Pass
on Server-A look for backup If old HA backup files
Fail
files named exist on the server they N/A
0, 1 or 2.....)
Step 4 - On the standby server (Server- The restore process of the
Restore A) execute the script database on the standby Pass
HA_run_netmaster_database_r server starts Fail
estore (located in the local N/A
"..\task" folder)
Restore on the standby server is
on the Server-A) server (Server-A)
standby server, Server-A HA Restore log state that
should indicate that the backup the backup is aborted due
Pass
is aborted due to missing to missing backup file
Fail
backup file) N/A

Server-A is not stopped and
restarted during the restore
server log on Server-A)
Nera Networks AS
Page 76(83)
3.5.7.3 Schedule export and restore (reversed operation) , 1+1 HA system

scheduled tasks
Pass
Fail
HA solution on a 1+1 system Server-A running as a N/A
servers.
Remove old server and the standby server exist in the backup folder
files open the backup folder on both servers (Server-A
(..\tasks\backup). and Server-B)

"X_Rnetmaster_database.back servers (Server-A and
up" and Server-B)
"X_netmaster_database.backu
Pass
p" files
Fail
N/A
server and the standby server
open the log folder
(..\tasks\log).

them. Both
ort.log" and
HA_netmaster_restore.log"
Nera Networks AS
Page 77(83)

Step 4 - 1. On the primary server Five "Export tasks"
Schedule Server-B: scheduled during the

- 01:00 AM, Export 2 - 02:00 N/A
AM ......)

export on Server-B is finished
before the next export task is
scheduled to start.
Step 5 - 1. On the standby server Five "Restore tasks"
Schedule Server-A: scheduled during the

Pass
- 01:30 AM, Export 2 - 02:30
Fail
AM ......) N/A

restore on Server-A is finished
and NetMaster on Server-A is
properly started before the
next export task on Server-B is
step 4).
Pass
Fail
server (Server-A)
Pass
Fail
NetMaster servers (Server-A and Server- server and monitor the N/A
running B) network
Nera Networks AS
Page 78(83)

Step 8 - On the Primary server (Server- All exports completed
Verify Export B) open the successfully.
are noted
Pass
Fail
successfully.

alarms in the
the last export
Step 9 - On the Standby server (Server- All restores completed
Verify A) open the successfully.
Pass
Fail
alarms from step 8.
rows in step 8.
Nera Networks AS
Page 79(83)
3.5.7.4 Oracle error on primary DB Server (reversed operation) , 1+1 HA system

Pass
Fail
to the standby server if a error N/A
situation occurs on the primary
server
Pass
Fail
HA solution on a 1+1 system Server-A as a backup N/A
using 2 different computers. server.
server.
Step 3 - On the standby server (Server- No restore backup file
Remove A) open the backup folder exist in the backup folder
restore file (..\tasks\backup). If an old on the standby server
Pass
restore backup file exists (Server-A)
Fail
delete it. N/A
File name:
Generate System B by stopping the
error- Oracle listener on Server B -
Pass
OracleOraDB10g_home1TNS error:
Fail
Listener) ERROR: N/A
ORA-12541: TNS:no
Use the listener
Server-B to verify oracle error
Step 5 - HA On the primary server Server- Export started and
Pass
DB Export B execute the script aborted due to connection
Fail
"ha_run_netmaster_database_e problems N/A
xport.cmd"
Nera Networks AS
Page 80(83)

Verify HA on the primary server, Server- information about aborted
Export log B export. Example of error
message:
sport)
Export: Release
on Wed Sep 16 13:06:40
2009
reserved. Fail
ORA-12541: TNS:no
listener
EXP-00000: Export
terminated
unsuccessfully
.
database is up and
running
.
not copied the standby server (Server-A) server (Server-A)
Pass
Fail
Filename: N/A
(Server-A)
Nera Networks AS
Page 81(83)
3.5.8 NetMaster System Manager - Backup and Restore

Step 1 - Launch NetMaster System NetMaster System Pass
Preparations Manager on the NetMaster Manager is launched Fail
server N/A
Step 2 - Perform a database backup A backup of the current
Backup using NetMaster System NetMaster database
Manager finishes with out any
error messages
Pass
If 2+0 Server
Fail
configuration N/A
The backup file is
automaticaly copied to
the NetMaster server
without any error
messages
Step 2 – Use System Manager and open The log shall contain a
Verify the "Task log" view new log entry showing Pass
Backup that a "Backup Fail
Database" has been N/A
executed
Step 3 - Perform a database restore The restore to the
Restore using NetMaster System active NetMaster
Manager on the NetMaster schema (user)
server completes successfully
1. During the restore select the Pass

NetMaster schema/user used Fail
in previous step (during N/A
backup)
2. Select the backupfile

prepared in step 2
Step 4 – Use System Manager and open The log shall contain a
Verify the "Task log" view new log entry showing Pass
Restore that a "Restore Fail
user/schema" has been N/A
executed
Step 5 – Use System Manager and NetMaster server starts
Pass
Start invoke the Start Server action successfully after the
Fail
NetMaster DB restore N/A
Server
Nera Networks AS
Page 82(83)
CONCLUDING REMARKS
Concluding Remarks
4. SIGNATURES
Location: Date:
Customer representatives Nera Representatives
Name: Name:
Sign:_____________________________________ Sign:_____________________________________
Name: Name:
Sign:_____________________________________ Sign:_____________________________________
Name: Name:
Sign:_____________________________________ Sign:_____________________________________
Nera Networks AS
Page 83(83)

NetMaster SAT Rev - D

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NetMaster SAT Rev - D

Încărcat de

Drepturi de autor:

Formate disponibile

Site Acceptance Test (SAT)

Rev Date Rev. Document ID

2.1 System configurations

Figure 1. A NetMaster configuration with co-located servers and client.

Figure 2. A NetMaster configuration with separate servers and clients.

Main system Standby system

Figure 3. A redundant NetMaster system.

2.2 Related documents

2.3 Test preparations

2.4 Description of System in Test

3.1 Configuration Management

3.1.1 Discovering and managing elements

3.1.2 Unmanaging elements

Step Description Expected result Status Comments

3.1.4 HW and SW Inventory

3.1.5 CPE specific views for PtMP systems

3.1.6 SW Download Jobs (Evolution/InterLink/CityLink/NL-29x/WiLink elements)

Step Description Expected result Status Comments

3.1.7 SW Activation/Reset (Evolution/InterLink/CityLink/NL-29x elements)

3.1.8 NE Configuration File Management (Evolution elements)

Step Description Expected result Status Comments

3.1.9 Help System

3.2 Fault Management

3.2.1 Active Alarms

3.2.2 Historical Alarms

3.2.3 Alarm Templates

3.3 Performance Management

3.3.1 Enable Performance Measurements Collection

3.3.2 Current Performance

Step Description Expected result Status Comments

3.3.3 Historical Performance

Step Description Expected result Status Comments

3.3.4 Threshold Crossing Alarms (TCA)

3.4 Security Management

3.4.1 Group and User Management

3.4.2 User Audit Data Logging

3.4.3 User Audit Filtering

3.5 Optional Features

3.5.1 Administrative Domains with Geographical Maps

Step Description Expected result Status Comments

3.5.2 Report Generator

3.5.3 SNMP Northbound Interface

Step Description Expected result Status Comments

Step Description Expected result Status Comments

3.5.4 Hot Standby Redundancy Tests, 2+2 HA system

Initial role: “Primary NetMaster Server”

Step Description Expected result Status Comments

Assign the necessary values to

Step Description Expected result Status Comments

Step Description Expected result Status Comments

Make a note of the resulting

The duration of the file

Step Description Expected result Status Comments

Step Description Expected result Status Comments

Step Description Expected result Status Comments

NetMaster on the standby

3.5.4.2 HA Restore, 2+2 HA system - no existing restore backup file

Step Description Expected result Status Comments

Verify that the running

3.5.4.3 HA Export, 2+2 HA system - Number of export files to keep

Step Description Expected result Status Comments

Note! If old restored

Filename: Timestamp of the file is