NWD-113538-03E

P ASOLINK

N
PNMS (Java version)
ETWORK iPASOLINK Series
PNMSjMonitoring

M ANAGEMENT
Procedure Manual

S YSTEM

NEC Corporation
Copyright © 2011
 NWD-113538

Table of Contents

Table of Contents .............................................................................................................................i

1. Preparing PNMSj and NEs in monitoring of iPASOLINK series ............................................... 1

2. SNMP Protocol (and relevant items) ......................................................................................... 2

2.1. Setting up PNMSj ....................................................................................................................... 2

2.2. Setting up NEs............................................................................................................................ 2

3. User Profile (and relevant items) .............................................................................................. 3

3.1. Setting up PNMSj ....................................................................................................................... 3

3.2. Setting up NEs............................................................................................................................ 3

4. FTP Protocol (and relevant items) ............................................................................................ 4

4.1. Setting up PNMSj ....................................................................................................................... 4

4.2. Setting up NEs............................................................................................................................ 4

5. NTP Protocol (and relevant items) ............................................................................................ 6

5.1. Setting up PNMSj Server............................................................................................................. 6

5.1.1. For Windows Server 2008/Windows Server 2008 R2 ...................................................... 6

5.1.2. For Solaris 9 ..................................................................................................................... 7

5.1.3. For Solaris 10 ................................................................................................................... 8

5.2. Setting up NEs............................................................................................................................ 9

6. Severity Colors....................................................................................................................... 12

6.1. Setting up PNMSj ..................................................................................................................... 12

7. HTTP Proxy........................................................................................................................... 13

8. Occupied Protocol Numbers ................................................................................................... 14

APPENDIX A: Setting up Cascade Connection........................................................................ 15

-i-
 NWD-113538

1. Preparing PNMSj and NEs in monitoring of iPASOLINK series

In order to monitor iPASOLINK series, following 6 items need to be setup. In this manual, only the
minimal setups necessary are explained. For more detailed explanation of setup procedures, please
refer to iPASOLINK series LCT manual.
 SNMP protocol (for monitoring/control)
 User profile (for security control)
 FTP protocol (to transfer/download files)
 NTP protocol (to synchronize time)
 Severity color
 HTTP Proxy

-1-
 NWD-113538

2. SNMP Protocol (and relevant items)

To monitor NEs by PNMSj, it is necessary to setup SNMP protocol and certain related items. With
regards to the Community name used to monitor/control NEs by PNMSj, same name must be setup
for all NEs. Without this setup, registration and monitoring of NEs by means of Auto-discovery
cannot be done.

2.1. Setting up PNMSj

To monitor NEs, Community used between PNMSj and NEs needs to be setup. For detailed
explanation of this procedure, please refer to section “3.7.11.1. SNMPv2c Setting” of PNMSj
Operation Manual.
1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
SNMPv2c Setting tab will appear in PNMS Properties window.
2. Select community name to be used by SNMPv2c.
 SNMPv2c Setting - Community (Default: public)
3. Setup IP address for Trap receiver. Select IP address used by PNMSj when connecting with
NEs. If expected IP address is not found in the combo box, please enter manually.
 Trap receiver IP Address Setting - IP Address

2.2. Setting up NEs

Community name setup in PNMSj must also be setup in all NEs. For detailed explanation of setup
procedure, please refer to LCT Manual of iPASOLINK series.
1. Login to LCT as Admin user.
2. From the Menu on left side, select User Account/Security Setting  Security Management
 Service Status Setting.
3. Click No.1 in [SNMP Community] on right side of the window. If No.1 is already used, select
other number for setup.
4. Setup following in SNMP Community (No.1) Window.
 Community Name : <Community name setup in PNMSj>
 Access Level : Admin
 Access Address : <IP address of PNMSj machine>
 Subnet Mask : 255.255.255.255

NOTE
When making arrangements to setup Access
Addresses/Subnet Masks, please proceed by keeping various
situations in mind such as replacing server or monitoring by
multiple numbers of NMS. Above example does not consider
server replacements or multiple NMS usages. If PNMSj
Server address is not clear, set ”0.0.0.0” for [Access Address]
as well as for [Subnet Mask].

5. Click [OK] in SNMP Community (No.1) window to complete the setup. Click OK again when
Complete is displayed by Information dialog (Window will close automatically).
6. Confirm that the setup is reflected in SNMP Community No.1. With above example, following
should be confirmed.
 Community Name : <Community name setup in PNMSj>
 Access Level : Admin
 Access Address : <IP address of PNMSj machine>
 Subnet Mask : 255.255.255.255

-2-
 NWD-113538

3. User Profile (and relevant items)

PNMSj calls for LCT as the summary window of monitoring NE details. In order to login
automatically when every time LCT is called, user name and password for LCT login must be setup
and be kept in PNMSj. Use name and password used to log into LCT must be same for all NEs.

3.1. Setting up PNMSj

To automatically log into LCT, user name and password used between PNMSj and NEs need to be
setup. For detailed explanation of this procedure, please refer to section “LCT Setting” and “LCT
Security Setting” of PNMSj Operation Manual.

[LCT Setting]
1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
LCT setting tab will appear in PNMS Properties window.
2. Setup the following with regards to launching LCT.
 Browser setting :
Specify the browser to be used to launch LCT.
[Recommended Browsers ]
Windows: IE7, IE8
UNIX: Firefox3.0, Firefox3.6

[LCT Security Setting]

1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
LCT Security setting tab will appear in PNMS Properties window.
2. User name and password used to login to LCT are set separately for each PNMS Security level.

LCT Login User Name/Password (Sorted by PNMS Security Level)

PNMS Security LCT Privilege Level LCT Login User Password*
level Name*
Admin Admin Admin 12345678
Remote Config Config 87654321
Local Config Config 87654321
User Operator User 87654321
Monitor Operator User 87654321
*LCT login user names/passwords are the default values of NE.

3.2. Setting up NEs

LCT Login User Names and Passwords setup for PNMSj must also be setup for all NEs. For detailed
explanation of setup procedure, please refer to LCT Manual of iPASOLINK series. This procedure is
not necessary if no changes are made to (default) settings.
1. Login to LCT as Admin user.
2. From the Menu on left side, select User Account / Security Setting  User Account
Management.
3. Add any necessary User Names and Passwords.

-3-
 NWD-113538

4. FTP Protocol (and relevant items)

Certain setups are necessary in order to import PMON, download F/W and for similar other file
transfers. For this procedure, same user name and password will be used by the whole system. Thus,
unified user name/password need to be setup for all NEs.

4.1. Setting up PNMSj

To transfer files, user name and password used between PNMSj and NEs need to be setup. For
detailed explanation of this procedure, please refer to ”LCT Setting” and ”LCT Security Setting”
sections of PNMSj Operation Manual.

[LCT Setting]
1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
LCT setting tab will appear in PNMS Properties window.
2. Setup the following with regards to launching LCT.
 Browser setting :
Specify the browser to be used to launch LCT.
[Recommended Browsers]
Windows: IE7, IE8
UNIX: Firefox3.0, Firefox3.6

[LCT Security Setting]

1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
LCT Security setting tab will appear in PNMS Properties window.
2. User name and password used to login to LCT are set separately for each PNMS Security level.

LCT Login User Name/Password (Sorted by PNMS Security Level)

PNMS Security Privilege Level Login User Name* Password*
level
Admin Admin Admin 12345678
*LCT login user names/passwords are the default values of NE.

4.2. Setting up NEs

FTP Login User Name and Password setup by PNMSj Properties - iPASOLINK- ftp setting must
also be setup for all NEs. This procedure is not necessary if no changes are made to (default) settings.
In addition, FTP Service needs to be started. For detailed explanation of setup procedure, please
refer to LCT Manual of iPASOLINK series.

[User Setup]
1. Login to LCT as Admin user.
2. From the Menu on left side, select User Account/Security Setting  User Account
Management.
3. Add necessary User Names and Passwords.
[Starting up FTP Service]
4. From the Menu on left side, select User Account/Security Setting  Security Management
 Service Status Setting.
5. Click “FTP” in FTP frame.
6. Setup following in FTP Setting window.
 FTP : Service Enable
 TCP Port(Command) : 21
 TCP Port(Data) : 20
 MAX Session : 1
 Auto Stop : Enable
7. Click [OK] in FTP Setting window to complete the setup. Click OK again when Complete is
displayed by Information dialog (Window will close automatically).

-4-
 NWD-113538

8. Confirm that the setup is reflected in FTP. With above example, followings should be
confirmed.
 FTP : Running
 TCP Port(Command) : 21
 TCP Port(Data) : 20
 MAX Session : 1
 Auto Stop : Enable

-5-
 NWD-113538

5. NTP Protocol (and relevant items)

The time set in iPASOLINK equipments are synchronized by NTP; thus, NTP Server is essential in
synchronizing with all NEs. In this section, how to use PNMSj server as NTP server and setups to be done
in order to execute time synchronization of NEs are explained. Following example shows PNMSj acting
as the client to outside NTP server so that it will act as NTP server for iPASOLINK equipments.

5.1. Setting up PNMSj Server

5.1.1. For Windows Server 2008/Windows Server 2008 R2
To carry out time synchronization of NEs, NTP server of the Windows needs to be given proper
privilege. To do so, following setups need to be done.

5.1.1.1. When there is no outside NTP server

1. Click [Start] button and click [run command]. Then, enter “regedit” and click [OK].
2. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\TimeProviders\NtpServer
3. Right click [Enabled] in right side window and then click [Modify].
4. Enter “1” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
5. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
6. Right click [AnnounceFlags] in right side window and then click [Modify].
7. Enter “5” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
8. Right click [LocalClockDispersion] in right side window and then click [Modify].
9. Enter “0” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
10. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
11. Right click [NtpServer] in right side window and then click [Modify].
12. Delete any letters found in [Value data] box of [Edit String] dialog box and click [OK].
13. Terminate registry editor.
14. Enter following command at the command prompt and press Enter key to restart Windows time
service.
net stop w32time && net start w32time

5.1.1.2. When there is outside NTP server available

1. Click [Start] button and click [run command]. Then, enter “regedit” and click [OK].
2. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time
\TimeProviders\NtpServer
3. Right click [Enabled] in right side window and then click [Modify].
4. Enter “1” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
5. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
6. Right click [AnnounceFlags] in right side window and then click [Modify].
7. Enter “5” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
8. Right click [LocalClockDispersion] in right side window and then click [Modify].
9. Enter “0” in [Value data] box of [EDIT DWORD VALUE] dialog box and click [OK].
10. Find following registry key and click.
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
11. Right click [NtpServer] in right side window and then click [Modify].
12. Enter IP address of ntp server in [Value data] box of [Edit String] dialog box and click [OK].
13. Terminate registry editor.
14. Enter following command at the command prompt and press Enter key to restart Windows time
service.
net stop w32time && net start w32time

-6-
 NWD-113538

5.1.2. For Solaris 9

NOTE
Under certain conditions, subject might be allocated under
/etc/init.d .

5.1.2.1. When there is no outside NTP server

1. Login as a root user.
> su -
2. Copy file from the template.
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
3. Edit copied setup file.
# vi /etc/inet/ntp.conf
[Edit No.1] Change any lines starting out with “server”.
(Before)
server 127.127.XType.0 prefer
(After)
server 127.127.1.0 prefer
[Edit No.2] Change any lines starting out with “fudge”.
(Before)
fudge 127.127.XType.0 stratum 0
(After)
fudge 127.127.1.0 stratum 0
[Edit No.3] Comment out any lines starting with “key”.
(Before)
keys /etc/inet/ntp.keys
trustedkey 0
requestkey 0
controlkey 0
(After)
# keys /etc/inet/ntp.keys
# trustedkey 0
# requestkey 0
# controlkey 0
4. Create drift file.
# touch /var/ntp/ntp.drift
5. Launch ntp server.
# /etc/inet/xntpd stop
# /etc/inet/xntpd start

5.1.2.2. When there is outside NTP server available

1. Login as a root user.
> su -
2. Copy file from the template.
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
3. Edit copied setup file.
# vi /etc/inet/ntp.conf

[Edit No.1] Change any lines starting out with “server”.

(Before)
server 127.127.XType.0 prefer
(After)
server <Server address of outside NTP server> prefer
server 127.127.1.0

-7-
 NWD-113538

[Edit No.2] Change any lines starting out with “fudge”.

(Before)
fudge 127.127.XType.0 stratum 0
(After)
fudge 127.127.1.0 stratum 0
[Edit No.3] Comment out any lines starting with “key”.
(Before)
keys /etc/inet/ntp.keys
trustedkey 0
requestkey 0
controlkey 0
(After)
# keys /etc/inet/ntp.keys
# trustedkey 0
# requestkey 0
# controlkey 0
4. Create drift file.
# touch /var/ntp/ntp.drift
5. Launch ntp server.
# /etc/inet/xntpd stop
# /etc/inet/xntpd start

5.1.3. For Solaris 10

5.1.3.1. When there is no outside NTP server
1. Login as a root user.
> su -
2. Copy file from the template.
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
3. Edit copied setup file.
# vi /etc/inet/ntp.conf
[Edit No.1] Change any lines starting out with “server”.
(Before)
server 127.127.XType.0
(After)
server 127.127.1.0 prefer
[Edit No.2] Change any lines starting out with “fudge”.
(Before)
fudge 127.127.XType.0 stratum 0
(After)
fudge 127.127.1.0 stratum 0
[Edit No.3] Comment out any lines starting with “key”.
(Before)
keys /etc/inet/ntp.keys
trustedkey 0
requestkey 0
controlkey 0
(After)
# keys /etc/inet/ntp.keys
# trustedkey 0
# requestkey 0
# controlkey 0
4. Create drift file.
# touch /var/ntp/ntp.drift
5. Launch ntp server.
# svcadm -v enable ntp

-8-
 NWD-113538

5.1.3.2. When there is outside NTP server available

1. Login as a root user.
> su -
2. Copy file from the template.
# cp /etc/inet/ntp.server /etc/inet/ntp.conf
3. Edit copied setup file.
# vi /etc/inet/ntp.conf
[Edit No.1] Change any lines starting out with “server”.
(Before)
server 127.127.XType.0
(After)
server <Server address of outside NTP server> prefer
server 127.127.1.0
[Edit No.2] Change any lines starting out with “fudge”.
(Before)
fudge 127.127.XType.0 stratum 0
(After)
fudge 127.127.1.0 stratum 0
[Edit No.3] Comment out any lines starting with “key”.
(Before)
keys /etc/inet/ntp.keys
trustedkey 0
requestkey 0
controlkey 0
(After)
# keys /etc/inet/ntp.keys
# trustedkey 0
# requestkey 0
# controlkey 0
4. Create drift file.
# touch /var/ntp/ntp.drift
5. Launch ntp server.
# svcadm -v enable ntp

5.2. Setting up NEs

In order to synchronize time by top NE (Root NE), either PNMSj Server or an outside NTP server
must be specified as the NTP server. The top NE of each subnet (Branch NE) must specify top NE
(Root NE/Branch NE) of upper subnet where it belongs as the NTP server. Other NEs than
mentioned above (Normal NEs) must specify top NE (Root NE/Branch NE) of subnet where those
belong as the NTP server. Do not create loop with NTP protocol network (protocol itself does not
detect nor abort loop). For example, specify NTP server as the Default Gateway to avoid loop. For
detailed explanation of setup procedure, please refer to LCT Manual of iPASOLINK series.

[Set current time and time zone]

1. Login to LCT as Admin user.
2. From the Menu on left side, select Equipment Utility  Date/Time Setting.
3. Click Modify button.
4. Check off “Display PC Time” in Date/Time Setting window. If the same Time Zone is not
selected for the PC where LCT is launched and for the machine where PNMSj is active, make
adjustment by selecting appropriate values for Date, Time and Time Zone.
5. Click [OK] in Date/Time Setting window to complete the setup. Click OK again when
Complete is displayed by Information dialog (Window will close automatically).

-9-
 NWD-113538

[Execute the following to specify as the NTP Server.]

6. From the Menu on left side, select User Account/Security Setting  Security Management
 Service Status Setting.
7. Click “NTP” in NTP frame.
8. Setup following in NTP Setting window.
 NTP : Enable
 NTP Server Mode : (For Root NE/Branch NE) Unicast
(Other than above) Disabled
 NTP Client Mode : Unicast
 Stratum : 5

9. Click [OK] in NTP Setting window to complete the setup. Click OK again when Complete is
displayed by Information dialog (Window will close automatically).
10. Confirm that the setup is reflected in NTP. With above example, followings should be
confirmed.
 NTP : Enable
 NTP Server Mode : (For Root NE/Branch NE) Unicast
(Other than above) Disabled
 NTP Client Mode : Unicast
 Stratum : 5
 Multicast Port (Irrelevant)
 Multicast Interval (Irrelevant)

[Execute the following to specify as the NTP Client]

11. Click “No.1” in NTP Server Address frame.
12. Setup following in NTP Server Address Setting window.

IP Address xxx.xxx.xxx.xxx
(For Root NE) Server address of PNMSj
(For Branch NE) IP address of Root NE/Branch
NE of upper subnet which it belongs to
(For Normal NE) IP address of Root NE or
Branch NE of subnet which it belongs to
* However, if iPASOLINK NE is located in the
middle of its previous versions, setups for
iPASOLINK that is closest to PNMSj must be
the same as that of Root NE. Further, setups for
Branch NE and Normal NE which belong to
such network must be done by assuming that
NE, having same setup as Root NE, as the Root
NE.
NTP Version 4
Poll Time 18hour12min16s (65536s)

- 10 -
 NWD-113538

13. Click [OK] in NTP Server Address Setting window to complete the setup. Click OK again
when Complete is displayed by Information dialog (Window will close automatically).
14. Confirm that the setup is reflected in NTP Server Address No.1. With above example,
followings should be confirmed.

IP Address xxx.xxx.xxx.xxx
(For Root NE) Server address of PNMSj
(For Branch NE) IP address of Root NE/Branch
NE of upper subnet which it belongs to
(For Normal NE) IP address of Root NE or
Branch NE of subnet which it belongs to
* However, if iPASOLINK NE is located in the
middle of its previous versions, setups for
iPASOLINK that is closest to PNMSj must be
the same as that of Root NE. Further, setups for
Branch NE and Normal NE which belong to
such network must be done by assuming that
NE, having same setup as Root NE, as the Root
NE.
NTP Version 4
Poll Time 18hour12min16s (65536s)

- 11 -
 NWD-113538

6. Severity Colors
To match Severity Colors with that in LCT, please setup following in PNMSj. With this procedure,
colors in existing NEs will also be changed.

6.1. Setting up PNMSj

For detailed explanation of this procedure, please refer to section “SNMPv2c Setting” of PNMSj
Operation Manual.

1. Click System  Properties  PNMS Properties in menu bar of PNMS main window and
Color tab will appear in PNMS Properties window.
2. Select “Status” in Select Type of Color Settings.
3. By referring to the chart below, select Severity for target Item. Select RGB tab in Change Color
dialog. Enter values for Red/Green/Blue accordingly by RGB chart. Close dialog by pressing OK
button in Change Color dialog.
4. Select “Log” in Select Type of Color Settings.
5. By referring to the chart below, select Severity for target Item. Select RGB tab in Change Color
dialog. Enter values for Red/Green/Blue accordingly by RGB chart. Close dialog by pressing OK
button in Change Color dialog.
6. Click OK button of PNMSj Properties to apply settings.

Severity – Color Chart

Severity PNMSj(Default) PNMSj(Changed) LCT
R: 238 R: 238 R: 255
Critical G: 0 G: 0 G: 0
B: 0 B: 0 B: 0
R: 238 R: 255 R: 255
Major G: 85 G: 154 G: 154
B: 85 B: 0 B: 0
R: 238 R: 255 R: 255
Minor G: 170 G: 255 G: 255
B: 170 B: 0 B: 0
R: 238 R: 99 R: 99
Warning G: 0 G: 255 G: 255
B: 170 B: 255 B: 255
R: 238 R: 255
Indeterminate G: 170 G: 153
B: 0 B: 255
R: 238 R: 238 R: 255
Maintenance G: 238 G: 238 G: 154
B: 85 B: 85 B: 0
R: 102 R: 102 R: 0
Normal G: 255 G: 255 G: 255
B: 0 B: 0 B: 0

- 12 -
 NWD-113538

7. HTTP Proxy
IF the network between PNMSj Client and NE can not be opened at the time when LCT is called,
direct connection between PNMSj Client and NE can be bypassed by setting up HTTP Proxy server
in PNMSj.
For detailed explanation of setup procedure, please refer to “Setting up Web Proxy” section of
Server Setting Manual.

- 13 -
 NWD-113538

8. Occupied Protocol Numbers

Necessary port numbers to monitor iPASOLINK equipments are listed below.
Direction of Communication Protocol Receiving Port
Client  PNMSj Server RMI 1099 (Initial connection port)
1024-65535 (Connection port)
Client  PNMSj Server HTTP 80
Client  PNMSj Server HTTP Proxy 8080
PNMSj  Equipment SNMP 161
PNMSj  Equipment FTP 21
PNMSj  Equipment FTP-DATA 20
PNMSj  Equipment HTTP 80
Equipment  PNMSj SNMP TRAP 162
Equipment  PNMSj NTP 123

- 14 -
 NWD-113538

APPENDIX A: Setting up Cascade Connection

In order for PNMSj to correctly display cascade connected NE, a single, uniquely Own Cascade ID
must be set within a cascade group.
Primary IP Address setup for each NE in a cascade group must have the same subnet address.

For detailed setup method, please refer to LCT Manual of iPASOLINK.

1. Login to LCT.
2. From the Menu on left side, select Equipment Setup  Network Management Configuration
 Equipment Cascade Setting.
3. In order for IP address to be matched with Own Cascade ID, click Setup button and setup
following in Equipment Cascade Setting window.

 Number of Cascaded NEs: Number of NE to be connected by cascade connection

 Own Cascade ID: One’s very own Cascade ID
 Cascade ID / IP Address: IP address matched with Own Cascade ID of other NE
that exists within a cascade group

- 15 -