Professional Documents
Culture Documents
NEC Corporation
Copyright 2015
CONTENTS
I.
INTRODUCTION .................................................................................................................... 1
II.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
-i-
I. INTRODUCTION
This document descibes the proposed test procedures for Pasolink Network Management System java
version (PNMSj). The procedures introduced in this document aims to verify that the PNMSj is
operating according to the specifications.
The details of the procedures used in this document are found on the documents mentioned below and
are supplied by NEC, before proceding with the system test.
It is therefore recommended that the said documents are readily available to the engineers and
technicians carrying out the tests.
We believe that the participants are familiar with the NetCfgTool, PNMTj and PNMSj operations in
general. Some detailed steps are ommited in the test procedure.
The IP addresses mentioned in the document is only as an example, during the tests the customer can
use any IP address scheme they prefer.
Rev. 1.07.010.001
PNMTj
Rev. 1.20.018.003
PNMSj
Rev. 1.20.018.003
-1-
Note: Some test procedures are targeted to test several functions under the same category.
The following steps will be carried out to eveluate the objectives mention under
Purpose.
1. Objective: This section describes all of the objectives for the test and any areas of specific
interest.
2. Prerequisite: This section refers to the physical description of the test facility. Describe the test
setup layout, connections and the necessary pre-prerequisite.
3. Procedure: This is the first key technical section. It provides sufficient information to carry out
the test to obtain the results stipulated under Purpose.
4. Success Criteria: This is the second major technical section of the process, It description the
excepted result from the test which will have a direct influence on the next step, Test Result and
validation
5. Test Result and Validation: Final stage of the test which evaluates the test results obtained.
-2-
1. Security Management
1. Objective
This test is intended to test the Security Management Function on PNMSj software and targeted to test
the following functions.
1. Add Group / Change Group Privilege / Add User
2. Modify Group (Change PNMT Security Level / NE)
3. Block / Unblock Function/
4. Confirm that all the activates are listed in the event Log.
1-2
2. Prerequisite
At least one Hop should be connected to the PNMSj.
3. Procedure
1. Add Group / Change Group Privilege / Add User
(1)
-3-
(2)
(3)
(4)
Confirm that Security menu in the System Security dropdown menu that User Account
Setting function is not selectable (grayed-out)
(5)
Open one of the connected NE Link Summary and confirm that PNMT Admin privileges are
available.
NOTE: Step 5 is only applicable with PASOLINK NEO and 5000S NEs.
2. Modify Group Privileges (Change PNMT Security level to Monitor and select only NE001)
(1) Logout and Login as Admin, modify Group Properties (Test), As shown below.
(2) Login as User and confirm that only No.001 is visible. Other NE(s) are grayed-out.
(3) Open No.001 link summary and confirm that only monitoring is allowed.
3. Block / Unblock Function
(1) Logout and try to Login as User with an invalid password.
(2) Repeat 2 more times to login with an invalid password and confirm that the account gets blocked.
(3) Login as Admin and unblock the User account.
-4-
(4) Login as User with the correct password and confirm that the account is not blocked.
(5) Delete User and then the Test Group.
(6) Try to Login using the deleted User Name and Password
(7) Confirm that Login is not allowed.
-5-
4. Success criteria
The user belonging to the modified group must have the same privilege as the modified group.
The modified user now must have the privilege of the new group specified during the modification
procedure. Three attempt of invalid login using wrong password should block the account. The
administrator should be able to unblock the blocked accounts. All the activities performed during this
test should appear in the Event Log.
Test Validation
Comment
OK
NOK
ND
NO
YES
Note:- Please refer the corresponding PNMTj operation manual for different user level privileges.
(Monitor, User, Local, Remote and Admin)
-6-
2. Prerequisite
At least one Hop should be connected to the PNMSj. It should be tested on console. (not available in
Remote Clients)
3. Procedure
(1) Select No Sound from the PNMS Properties Alarm Buzzer menu.
(2) Create an alarm in the radio equipment and confirm that there is no audible alarm and the Buzzer
Icon stay inactive.
(3)
4. Success criteria
Selection of No Sound from the Alarm Buzzer menu should not generate any audible alarm.
Selection of a Wave File from the Alarm Buzzer menu should play the selected file and allow buzzer
stop function.
Test Validation
Comment
OK
NOK
ND
NO
-7-
YES
2. Prerequisite
At least one Hop should be connected to the PNMSj and a PNMT connected to one of them.
3. Procedure
(1) Connect the PNMT to the Root NE.
(2) Select Date/Time set menu from the PNMT
PCM folder.
(3) Change the PNMT PC time by 1 Hour with
respect to the PNMS PC time.
(4) Set this time to the connected IDU.
(5) Set the IDU to maintenance using PNMT,
observe the PNMS event log and note down
the time of the event (MAINT ON).
(6) In Propoertiex PNMSj Properties menu
select Auto Set Date/Time and check the box
Enable set PMC Date/Time automatically and set the user defined start time to few minutes
after the current time.
(7) Wait until the user defined start time is past and then release the MAINT ON condition using the
PNMT.
(8) Observe the PNMS event log and note down the time of the event (MAINT OFF).
-8-
4. Success criteria
The event MAINT ON should indicate the time set by the PNMT. The MAINT OFF command was
initiated after PNMSJ Date/Time synchronization so this event should be listed in the event log with
the PNMSj time setting.
Test Validation
Comment
OK
NOK
ND
NO
-9-
YES
2. Prerequisite
At least one hop should be connected to the PNMSj and the network elements should contain
performance history data. The NEs should be continuously running for at least 24 hours generating
some errors. (48 hours recommended)
3. Procedure
(1) In the Properties Element Properties Link Performance History menu, set the Collect time
to few minutes after the current PNMSj PC time.
(2) Wait until the time set in step (1) is past and observe the collection of Pmon data.
(3) Check C:/PNMSj/Pmon directory and confirm that the Pmon data has been collected as
specified in step (1).
4. Success criteria
The performance history data should be collected once pay day as specified in the menu and stored in
the PNMSj directory.
- 10 -
Test Validation
Comment
OK
NOK
ND
NO
- 11 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj. The procedure below is written assuming that the
PNMSj PC date is 2006/05/10. Need more than 48 hours to complete the test successfully.
3. Procedure
(1)
(2)
(3)
(4)
Launch PNMSj program and open Properties PNMS Properties and select Event Log from
the menu list.
(5)
(6)
Open C:\PNMSj\log\log folder and confirm that one file is already created with the file name as
YYYYMMDD_1.
(7)
(8)
Confirm that the events generated in step (7) are listed in the 20060510_1 file.
(9)
After 24 hours confirm that another file with file name YYYYMMDD_1 is created in the folder
C:\PNMSj\log\log.
- 12 -
4. Success criteria
The event data should be stored in the C:\PNMSj\log\log folder as specified in step (5). The folder
should contain the event data for the latest two days.
Test Validation
Comment
OK
NOK
ND
NO
- 13 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj.
3. Procedure
1 .Disconnection Type severity setting
(1) From Properties PNMS Properties then select Color from the list. Select Type to Log.
(2) Confirm the color used for Status (By default White color is used)
(3) From Properties Element Properties Severity Setting. Select Disconnect Type to Status.
- 14 -
(8) Open Properties PNMS Properties and select Color from the list and confirm the color
assigned for Warning. (By default Purple color is used)
(9) Power OFF No.002.
(10) Confirm that the event No.002 disconnect appear in the Event Log with Purple color.
2. Item severity setting
(1) Decide on an alarm to generate (INPUT LOSS CH01 Major)
(2) Open Properties PNMS Properties Color menus and confirm the assigned Color related to
the target alarm in (1) alarm. Then go to the Properties Element Properties Severity Setting
and confirm that the target alarm in (1) has the correct severity (Major).
(3) Generate the alarm and confirm that said alarm is listed in the event log with the assigned color.
(4) Normalize the alarm
(5) Change Severity and/or color.
(6) Generate the same alarm again and confirm that the alarm is listed in the event log according to
the changes made in step (5).
4. Success criteria
The NE disconnection type severity should be able to select between Status and Alarm. Selection of
alarm should allow selecting different levels of severity. Should allow customizing the severity of the
items listed in the PNMS Properties Severity menu.
- 15 -
Test Validation
Comment
OK
NOK
ND
NO
- 16 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj. A Major alarm is selected for this test.
Default color for Major Alarm
Status Red
Log Red
3. Procedure
(1) Generate a Major alarm in the radio equipment and confirm that the corresponding icons become
Red and the alarm is listed in the event log in Red color.
(2) Release the alarm generated in step (1).
(3) From Properties PNMS Properties Color menu Select Type to Status.
(4) Change item Major to Yellow color.
(5)
4. Success criteria
NE Icon in the PNMSj windows (Network Map, Main window, etc.) should change color according to
the changes made to the color menu. The Event Log and PNMSj windows should change color
according to the changes made in step (4)./(6).
Test Validation
Comment
OK
NOK
ND
NO
- 17 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj.
3. Procedure
(1) Generate few alarms in the radio equipment.
(2) Open folder C:\PNMSj\log\log and confirm that the alarms generated in step (1) are saved as a
text file.
(3) From Properties PNMS Properties Backup menu Select Enable backup automatically.
(4) Select a time near to the current time and a directory to save the backup files.
(5) Click OK button and wait until the set time is past then make sure that three folders (config, log,
pmon) are created in the backup folder.
(6) Open the/Backup/log/log folder and confirm that the alarms generated in step (1) are backed
up to this file.
4. Success criteria
Make sure that the backup folder is created in the directory as specified in step (4), and it contain three
folders (config, log, pmon)
- 18 -
Test Validation
Comment
OK
NOK
ND
NO
YES
2. Prerequisite
The data generated in Test-8 (alarms) will be used.
3. Procedure
(1) Open Event log history and confirm that the alarms
generated in Test-8 are still listed.
4. Success Criteria
Verify that the Backup data is created in the specified directory. Verify that the PNMSj is running with
Backup data. (Alarms restored)
- 19 -
Test Results
Test Validation
Comment
OK
NOK
ND
NO
YES
2. Prerequisite
No prerequisite necessary.
3. Procedure
(1)
Login as Admin.
(2)
(3)
(4)
Logout and try to login with the old password and confirm that the old password is no longer
valid.
(5)
Try to login with the new password and confirm its validity.
(6)
Add a user.
(7)
(8)
4. Success Criteria
Administrator and the Users Passwords can be changed.
Test Validation
Comment
OK
NOK
ND
NO
- 20 -
YES
2. Prerequisite
1. PNMSj Server Setting
a. IIS Setting
b. Edit PNMSj.jnlp file
2. Remote Client Setting
a. IJava Runtime Installation
b. Java Plug-in Setting
c. Java Policy Setting
Please refer the related manuals for the above setting.
A test setup as shown below or similar should be used.
Normal NE
Root NE
NE1
172.18.0.1
172.18.0.2
NE2
NMS
Remote Client
10.27.86.218
Server
10.27.86.254
IP : 10.27.86.18
GW : 10.27.86.254
3. Procedure
(1) Launch PNMSj in the Server PC with Admin privileges.
(2) Using PNMS Properties Security menu add a user (demo).
(3) Remote login using the client PC with the User Name / password created in step (2).
(4) From System dropdown menu open Client List.
- 21 -
(5) Confirm the window is populated with two entries (Server / Client) giving login details as shown
below.
4. Success Criteria
The Client List should list down all the users currently logged in to the system.
The list should also gives the IP address of the PC the remote user is using as well as the access type
(Server / Client)
Test Validation
Comment
OK
NOK
ND
NO
- 22 -
YES
Note: - After selecting the filter open the corresponding window to verify its proper operation.
2. Prerequisite
No prerequisite necessary.
3. Procedure
(1) From Filter drop down menu select Filter Setting.
(2) Confirm Active Alarm folder is selected.
(3) Click add and input filter name (Active Alarm Filer).
(4) Using the filter setting window do the selections as shown in the window below.
(please see next page)
(5) Repeat the process and create three more filters for the remaining three folders (Event Log /
Network Element List) with same selections.
a) Event log Filter
b) Network Element List Filter
- 23 -
4. Success Criteria
The four filters created should appear in the Filter Selection menu.
- 24 -
Test Validation
Comment
OK
NOK
ND
NO
- 25 -
YES
2. Prerequisite
At lest one hop (No.001 No.002) with no Major alarms should be connected to the PNMSj. Before
launching PNMSj delete the Text files in the following two folders.
C:\PNMSj\log\log
C:\PNMSj\log\alarm
3. Procedure
(1) From the filter selection menu select Non Filter.
(2) Generate a Major alarm in No.001.
(3) Generate a Major alarm in No.002.
(4) Generate Minor alarms in No.001 and No.002.
(5) Confirm that all alarms are listed in the active alarm window.
(6) From the filter selection menu select Event Log Filter.
(7) Confirm that only NE001 Major Alarm is listed in the Event Log.
- 26 -
(8) From the filter selection menu select Active Alarm Filter and confirm that Event log window
gets populated again as it was in step (5).
(9) Open Active Alarm window and confirm that the filter is been applied and shows only the
No.001 Major Alarm.
(10) From the filter selection menu select Network Element List Filter.
(11) Open System Network Element List window and confirm that the filter is been applied and
show only the filtered criteria.
4. Success Criteria
The above test procedure is written targeting NE001 Major Alarm; the four windows should
successfully filter out the NE001 Major alarm with the selection of the appropriate filter.
Test Validation
Comment
OK
NOK
ND
NO
- 27 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj. Active Alarm window is used
3. Procedure
(1)
(2)
(3)
(4)
Click icon
(5)
Right click on one Major alarm and add a comment. (Team A).
(6)
(7)
Select active Alarm folder, click Add and input filter name (Team A).
(8)
Using filter setting window do the selections as shown in the window below.
- 28 -
(9)
(10) Open active alarm window and confirm only the alarm with comment Team A is listed.
(11) Select Non Filter and open active alarm window.
(12) Click on Acknowledge box and confirm it is possible to Un-Acknowledge.
(13) Open Event History window Click on each column to short according to Ack, Date/Time,
Network Element, Item or Severity.
(14) Check items under related column are shorted by an action.
- 29 -
4. Success Criteria
When the Acknowledge box is clicked the alarm check mark is shown and event log shows the alarm
acknowledge. (Note: If the acknowledge alarm button in the Active Alarm tool bar is used. All the
alarms are acknowledged; hence all alarm logs are shown with check marks). Clicking on an alarm
item already acknowledged will Un-Acknowledges the alarm the check mark will be removed in the
acknowledge box. Verify that Comment can be used for filtering. Verify that ascending/descending can
be done by click operation.
Test Validation
Comment
OK
NOK
ND
NO
YES
2. Prerequisite
PNMSj should contain NE001 Performance History data.
3. Procedure
(1) From Filter drop down menu select Search.
- 30 -
(3) From search result click the respective icon to view Chart and report.
Note: Chart and reports can also be created by right clicking on NE icon as shown in the next page.
4. Success Criteria
PNMSj display performance data (following parameter) with report and chart format.
- Out of Frame Second Ratio (OFS) - SDH
-Erred Second Ratio (ES)
-Severely Erred Second Ratio (SES)
-Unavailable Second Ratio (UAS)
-Background Block Error Ratio (BBE)
Test Validation
Comment
OK
NOK
ND
NO
- 31 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj.
3. Procedure
(1) Activate Edit mode by clicking on the Edit icon
4. Success Criteria
PNMS should not receive any status changes or alarms from the network elements set as Unmanaged.
Test Validation
Comment
OK
NOK
ND
NO
- 32 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj.
3. Procedure
(1)
Generate a Major alarm in NE 001 and confirm that the alarm severity is shown in all windows
as shown below.
(2)
(3)
4. Success Criteria
NE Icons in the PNMSj windows (Group View, Connection View, List, etc.) should change color
according to status created in the NE showing the color of the highest severity. The Colors shown
should be in accordance with color settings in The PNMS Properties Color menu.
- 33 -
Test Validation
Comment
OK
NOK
ND
NO
- 34 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj.
3. Procedure
(1) Confirm that no alarms are present in the radio equipment and the Total Alarm Summary
window appears as shown below.
(2) Generate few alarms in NE001 and NE002 ( MAJ and MIN )
(Check PNMS Properties Severity menu to find out the current setting)
(3) Open Active Alarm window and acknowledge some of the alarms using the check box.
(4) Compare the Total Alarm Summary window with the Alarm Information window and the
Active Alarm window.
- 35 -
4. Success Criteria
The Total Alarm Summary window should show the total number of alarms belong to each category
(CRI, MAJ, MIN, etc.). The number on the Left Hand Side should indicate the total number of not
acknowledged alarms and the number on the Right Hand Side should indicate the total number of
active alarms. (Total NAck / Total)
Test Validation
Comment
OK
NOK
ND
NO
- 36 -
YES
2. Prerequisite
At least one hop should be connected to the PNMSj. NetCfgTool.nct or NetCfg2Pnms.dat file is
necessary. The example shown below is using Pasolink V4 equipment. A test setup as shown below or
similar should be used.
Normal NE
Root NE
NE1
172.18.0.2
172.18.0.1
NE2
NMS
Server
10.27.86.254
IP : 10.27.86.18
GW : 10.27.86.254
PNMTj
3. Procedure
(1) Create a network using NetCfgTool.
(2) Right click on Root NE and select properties.
(3) Open PNMS folder.
(4) Select LAN for PNMS Connection.
- 37 -
(11) Use NetCfgTool.nct file created in step (6) in the wizard to update PNMSj.
(12) End of the wizard the network should get connected to the PNMSj.
(13) Click on the NE icon and open the Link Summary window.
(14) Select No.001 to Maintenance using the Link Summary window and confirm the connectivity.
4. Success Criteria
End of the PNMSj update wizard the network elements will appear in blue color and then should
change according to the NE status, this confirms the connectivity.
Test Validation
Comment
OK
NOK
ND
NO
- 38 -
YES
2. Prerequisite
One hop NEO equipment is necessary.
In order to demonstrate Auto-Discovery function it is necessary to connect the PNMTj to the
individual NE and setup the required network information according to the test setup shown
below.
Normal NE
Root NE
NE001
172.18.0.2
172.18.0.1
NMS
Server
10.27.86.254
IP : 10.27.86.18
GW : 10.27.86.254
PNMTj
- 39 -
NE002
3. Procedure
(1) Make IP configuration of the PNMSj Server as shown in the test setup.
(2) Set-up the IP addresses on each NEO NE according to the test setup.
(Use Equipment Network Setting window in the PNMTj to set the NEs)
Configure the Equipment network settings (i.e. IP addresses, subnet masks, Default gateway and
Routing) using the tags in the left-hand field of the Equipment Network Settings window.
(3) Radio/EM2 setting for the test set up announced above is shown below. (Root NE)
- 40 -
(6) Click Execute and complete the network setting for Root NE.
(7) PNMS/EM2/EM1 setting for the Normal NE is shown below.
- 41 -
(9) Click Execute and complete the network setting for Normal NE. Launch PNMSj.
(10) From main window dropdown menu select NetworkSetting Connection Management
Network, this will start find NE wizard as shown below.
Click Add button and input Root NE IP address (ex 172.20.0.1) when prompted.
- 42 -
(11) The NEs will be deteected and added to the PNMSj after completing the procedure in the wizard.
4. Success Criteria
After setting the necessary network parameters to the NEs using the PNMTj, The PNMSj should
discover the network automatically just by inputting the root NE IP Address in the wizard.
Test Validation
Comment
OK
NOK
ND
NO
- 43 -
YES
2. Prerequisite
One hop iPASOLINK equipment is necessary.
In order to demonstrate Auto-Discovery function it is necessary to connect the PNMTj to the
individual NE and setup the required network information according to the test setup shown
below.
Normal NE
Root NE
NE001
172.18.0.2
172.18.0.1
NE002
NMS
Server
10.27.86.254
IP : 10.27.86.18
GW : 10.27.86.254
PNMTj
3. Procedure
(1)
(2) Set-up the IP addresses on each iPASOLIK NE according to the test setup.
(Use Web-LCT to set the NEs)
Go to Equipment Setup Network Management Configuration General Setting
(Detail) .Click the Setup button to configure the IP address based on the network connection you
have on the test bench.
- 44 -
(3) In the test bench shown the NMS port is on a separate subnet as the MODEM/NE1 port. So in
that case the following click on Setup button on the top of the LCT menu (Root NE) and click
on the NMS hyperlink.
- 45 -
- 46 -
- 47 -
(6) Click OK button until you complete the network setting for Root NE.
(7) Next you must register the Community Name and SNMP setting for the NE. Go to User
Account/Security Setting Security Management Service Status Setting menu as shown in
the next figure. Click on the 1 hyperlink in the SNMP Community field.
- 48 -
- 49 -
(8) Enter the Community Name (same as the community name set in PNMSj), Access user to
Admin, Access control Enable, Source IP address 0.0.0.0, and Source Mask 0.0.0.0.
SNMP` setting in the PNMSj is located in System Properties PNMS Properties
iPASOLINK SNMP as shown below.
(9) Logout from the Root-NE and connect the WebLCT to the opposite NE
(10) The opposite NE is Normal so the NMS/NE1/MODEM are on the same Bridge 1. Do the
Web LCT setup again this time with only Bridge 1 settng.
(11) Set the Community name and SNMP setting as in steps (7) to (8).
(12) Click OK button and complete the network setting for Normal NE. Logout from LCT and launch
PNMSj.
(13) From main window dropdown menu select NetworkSetting Connection Management
Network, this will start find NE wizard as shown below.
Click Add button and input Root NE IP address (ex 172.20.0.1) when prompted.
- 50 -
(14) The NEs will be deteected and added to the PNMSj after completing the procedure in the wizard.
- 51 -
4. Success Criteria
After setting the necessary network parameters to the NEs using the PNMTj, The PNMSj should
discover the network automatically just by inputting the root NE IP Address in the wizard.
Test Validation
Comment
OK
NOK
ND
NO
- 52 -
YES
2. Prerequisite
At least 1 hop of radio connected to the PNMSj.
3. Procedure
(1)
Open the Network Element List window by selection System Network Element List
menu from the main window.
(3) Check and compare that the information shown (NE name, Equipment Type, IP addres,
Connection status, Severity, etc. ) is correct.
4. Success Criteria
The Network Element List window is displayed and shows the correct information of the NE(s).
Test Validation
Comment
OK
NOK
ND
NO
- 53 -
YES
2. Prerequisite
At least 1 hop of radio connected to the PNMSj. Generating PMON errors can be complicated and may
require additional test equipment to generate errors. This test is to simply shown that PNMSj can show
the Threshold crossing alarm so it is up to the customer to if they require to setup a complex test bench
to generate PMON errors. For this test only UAS (Unavailable Seconds) will be considered since it is
easy to generate. It is not he scope of this document to intruct how to generate PMON errors.
3. Procedure
(1)
For PASOLINK NEO and 5000S, open the Link Summary or PNMTj and set the PMON
Threshold on the Root-NE.
Click the Threshold button in the Summary Link
Performance Monitor window and the threshold setting window will appear as shown below.
- 54 -
For the iPASOLINK open the LCT and set the PMON threshold as shown below:
(2)
(3) Wait and observe until the UAS threshold is crossed and check the the appropriate alarm is
displayed in the PNMSj.
- 55 -
4. Success Criteria
The UAS threshold alarm crossing is displayed in the PNMSj active alarm and event log window.
Test Validation
Comment
OK
NOK
ND
NO
- 56 -
YES