Pnms Engineering Manual PDF

ROI-S04188-053E
030808
P
N
M
S
ASOLINK
ETWORK
Engineering Manual
(PASOLINK Version)
ANAGEMENT
YSTEM
NEC Corporation
Copyright 2003
ROI-S04188
Restricted Right Legends. All rights are reserved. No part of this document may be copied, reproduced,
or translated to another language without the prior written consent of NEC Corporation. The information
contained in this material is subject to change without notice.
Copyright Notices. Copyright 2003 NEC Corporation, all right reserved.
Reproduction, adaptation, or translation of this material without prior written permission is prohibited,
expected as allowed under the copyright laws.
ROI-S04188
CONTENTS
1. INTRODUCTION .......................................................................................................................1
2. SYSTEM OVERVIEW ...............................................................................................................2
3. SYSTEM COMPONENTS .........................................................................................................3
3.1 PNMS-CENTRAL SITE COMPUTER SYSTEM .............................................................................3
3.2 PNMT - PASOLINK NETWORK MANAGEMENT TERMINAL ........................................................3
3.3 PMC- PASOLINK MANAGEMENT CARD ..................................................................................3
4. PHYSICAL INTERFACE ............................................................................................................8
4.1 PNMS ..................................................................................................................................8
4.2 PNMT...................................................................................................................................8
4.3 PM CARD ..............................................................................................................................9
5. PNMS COMMUNICATION INTERAFCE.................................................................................11
6. NETWORK SIZING RULE .....................................................................................................12
7. PNMS IP ADDRESSING .........................................................................................................14
7.1 SIMPLE TRUNK LINE NETWORK (SERIAL INTERFACE) ..............................................................14
7.2 SIMPLE TRUNK LINE NETWORK (LAN INTERFACE)..................................................................16
7.3 SIMPLE TRUNK LINE NETWORK (THROUGH IP NETWORK) ........................................................19
7.4 MULTI SUB-BRANCH NETWORK .............................................................................................20
7.5 PNMS IP ADDRESSING SUMMARY .......................................................................................23
7.6 IP ADDRESS REQUIREMENT FOR CUSTOMER .........................................................................23
8. INTEROPERABILITY WITH OTHER NETWORK....................................................................24
8.1 CONNECTION AVAILABILITY ...................................................................................................24
9.TYPICAL CONFIGURATION ....................................................................................................25
9.1 POINT TO POINT CONNECTION ...............................................................................................25
9.2 POINT TO MULTI-POINT CONNECTION ....................................................................................27
9.3 MULTI-CLUSTER NETWORK (1) -DEDICATED LEASED LINE (SERIAL INTERFACE)-......................27
9.4 MULTI-CLUSTER NETWORK (2) DEDICATED LEASED LINE (LAN INTERFACE)- .......................28
9.5 MULTI-CLUSTER NETWORK (3) PSTN (SERIAL INTERFACE)-.................................................28
9.6 MULTI-CLUSTER NETWORK (4) PSTN (LAN INTERFACE)- ....................................................29
9.7 MULTI-CLUSTER NETWORK (5) IP NETWORK (LAN INTERFACE)- .........................................29
9.8 CPM REDUCTION SOLUTION .................................................................................................30
10. PNMS CONFIGURATION .....................................................................................................33
10.1 COLD STAND-BY PNMS PRINCIPLE .....................................................................................33
10.2. BACK UP PNMS DATA (UNIX VERSION ONLY) ....................................................................33
10.3 PARALLEL PNMS ...............................................................................................................33
10.4 HIERARCHICAL PNMS CONFIGURATION ...............................................................................35
11. NETWORK CONFIGURATION WORK..................................................................................37
11.1 PNMS FOR WINDOWS ........................................................................................................37
11.2 PNMS FOR UNIX ...............................................................................................................45
12. RELATED EQUIPMENT FOR PNMS ..................................................................................53
12.1 HYB CONVERTER ...............................................................................................................53
12.2. MANAGEMENT INTERFACE UNIT (MIU) ................................................................................54
12.3 PNMS CABLE...................................................................................................................55
-i-
ROI-S04188
-AbbreviationsDCN
Digital Communication Network
DEM
Demodulator
CONV
Converter
CPM
Central PM Card
DSC
Digital Service Channel
HDLC
High Level Data Link Control
HYB
Hybrid
IDU
Indoor Unit
INTFC
Interface
I/O
Input/Output
IP
Internet Protocol
LAN
Local Area Network
LCT
Local Craft Terminal
MIB
Management Information Base
MIU
Management Interface Unit
MSC
Mobile Switching Center
MUX
Multiplexer
NE
Network Element
NRM
Normal Response Mode
ODU
Outdoor Unit
PMC
PASOLINK Management Card
PNMS
PASOLINK Network Management System
PNMT
PASOLINK Network Management Terminal
PPP
Point to Point Protocol
PS
Power Supply
PSTN
Public Switched Telephone Network
RPM
Remote PM Card
TX
Receive
SCPM
Sub-Central PM Card
SNMP
Simple Network Management Protocol
SV
Supervisory
TFTP
Trivial File Transfer Protocol
TX
Transmit
SC
Service Channel
SV
Supervisory
SW
Switch
UDP
User Datagram Protocol
- ii -
ROI-S04188
1. INTRODUCTION
This document is developed as a guideline to help to ensure a high degree of accuracy,
completeness and uniformity in the system design of a PNMS (PASOLINK Network
Management System).
NECs PASOLINK system can be remotely monitored and controlled by the optional PNMT
(PASOLINK Network Management Terminal) and the PNMS*.
In order to use these systems, each IDU needs to be equipped with the optional PMC
(PASOLINK Management Card). The PNMT software is installed in the Windows
98/NT/2000/XP based portable PC and connected to SV (marked as LA) port at 19.2kbps
asynchronous mode. PNMT can login to a PMC and monitor and control any PASOLINK
remotely in the network. Therefore the PNMT is used mainly for maintenance purpose. For
continuous network monitoring, PNMS is required. All PASOLINKs under the PNMS are
always accessible.
To facilitate the system design, this guide describes the PNMS and its components, with
emphasis on the capability of each component and the connections that makes the
communication of network management system possible. It is also includes the procedure for
PASOLINK network system design, the architecture, the interpretation of a radio network to
the system, determination of the communication paths, and consideration of system
expansion. In addition, this guide gives some examples of System design, the drawings for
cabling of components and the PMC (PASOLINK Management Card) naming and
addressing scheme are the topics of relating to the detailed PNMS system configuration.
*PNMS and PNMT is not mandatory requirement s for the operation of PASOLINK network.
-1-
ROI-S04188
2. SYSTEM OVERVIEW
NEC designed PASOLINK Network Management System (PNMS), which enables remote
monitoring and control of a radio network. The NEC PNMS is a sophisticated supervisory tool
for transmission equipment and allows operator to perform remote system monitor alarms,
control NE configuration parameters and display event logging and performance data in
either UNIX or Microsoft Windows platform.
Figure 2.1 shows a typical PNMS application. The system consists of a central computer
(PNMS Computer) and a number of remote data processing nodes called PM card. It
supervises and controls PASOLINK transmission equipments.
In the following sections the functions and the usage of each component are described in
more detail.
Concept of NM
N M S for PASO LINK
O peration Center
D igital Service C hannel, 9.6kbps
ID U
PM
C AR D
R S-232C/V.11, 19.2kbps
or
L AN(10Base-T)
RS-232C,19.2kbps
PNM S
PNM T
Figure 2-1 Typical PNMS Application
-2-
ROI-S04188
3. SYSTEM COMPONENTS
3.1 PNMS-Central Site Computer System
The Central Site Computer is the central operator interface and database, from which system
operators manage the PASOLINK network. It receives data from the network via PM Card,
stores it, and displays it to the operator in a variety of formats. It accepts command request
from the operators and sends them to the on-site equipment for execution. Two types of
PNMS can be proposed in accordance with Customers Network size. One is PNMS on
Windows NT/2000/XP (supporting up to 500/1,000NEs) and the other is PNMS on UNIX OS
(supporting up to 10,000NEs).
3.2 PNMT - PASOLINK Network Management Terminal

The PNMT (PASOLINK Network Management Terminal) is a portable computer fitted with
NEC's PMNT software, which is used, as an on-site maintenance tool by technicians. It
connects directly to the LA port of PASOLINK to upgrade the configuration and software. It is
also used to provide local/remote data display and control capabilities similar to those of
PNMS.
The PNMT function can also be run on the PNMS to provide configuration and application
software upgrade for PM Card from a central point.
The PNMT runs in the Windows 95/98/NT/2000/XP environment and makes extensive use of
the user friendly Windows Graphical User Interface (GUI). It cannot only interrogate
individual PMCs but also monitors the network (subnetwork). It means that the PNMT user
can make connections to remote PMC from any node within a PASOLINK subnetwork. A
PASOLINK subnetwork is defined as a collection of PMC nodes headed by Central PM
CARD. Sub PM Card and Remote PM Card nodes are other node types, which can be part of
a PASOLINK subnetwork. This PASOLINK subnetwork is called PASOLINK CPM Cluster in
later section. Note that the PNMT is an optional component of the PNMS system.
3.3 PMC- PASOLINK Management Card

PM Cards are located at each site in the monitored network to collect alarm and status
information from PASOLINK and to control that equipment in response to commands from
the central site operator. The PMC primary tasks are to control and acquire data from
PASOLINK at remote location and transfer this data back to the central site. The PM card is
designed as plug-in modules.
3.3.1 SNMP Agent Function
- PM Cards is functioned as a SNMP agent, which detects alarm and status changes in
monitored equipment, and sends of change notifications to PNMS
- PM Card retains the MIB data and transmit a response to SNMP GET commands from
PNMS and PNMT.
- Execution of SNMP SET message commands received from PNMS/PNMT and transmit
a control command to the alarm control portion (ALM CONT) in the IDU.
-3-
ROI-S04188
3.3.2 Collecting Performance Monitor Data

- Performance measurement is equivalent to ITU-T G.826 standard.*
* The measurement is by the total value of performance monitoring data of RF portion, not the
performance monitoring data of every 2MB traffic as stated in ITU-T G.826.
- The following performance parameters are measured.
- Erred Second Ratio (ESR)
- Severely Erred Second Ratio (SESR)
- Unavailable Seconds Ratio (UASR)
- Background Block Error Ratio (BBER)
- Stored period in PM Card
There are two types of performance data files, one is every 15 minutes data file and the other
is every day data file.
PASOLINK :
per 15 minutes data :

per day data :
7 days
7 days
- Performance Monitor file format

Performance monitor file is Binary format in PM Card (This file is stored in PNMS/PNMT as
ASCII format.). It can be converted to the desirable format by the customer.
3.3.3 Collecting Event Log Data
- Hold event log of changed MIB data. The following events are logged.
- Status change
- Alarm occurrence
- Alarm recovery
- Control initiation
- Parameter change
- Up to 300 event logs are stored.
(The old event logs will be erased as the new event is logged.)
- Event log file format
Events log file is ASCII format. It can be converted to the desirable format by the customer.
-4-
ROI-S04188
3.3.4 Configuration File

- Hold information of PASOLINK logical network. There are three kinds of file as follows.
(1) ME Configuration file : Common file
- Setting Auxiliary input and output
- Threshold value of Performance Monitor data
(2) System Configuration file : As per PM card
- NE name and PM Card type
- IP address of each port of PM card, Communication speed
- Opposite IP address
(3) Network Configuration file : As per PM card
- Sub network name
- IP address and PM Card type in the Sub network
3.3.5 PMC Operating Modes
Depending on the size, a network can normally be divided into a number of sub-networks. To
distribute the traffic load we normally define one of the PMC as master and the rest as slaves
through discrete design. As introduced in above, we also call a master a Central PMC (CPM),
a sub-master a Sub-Central PMC (SCPM) and similarly, a slave a Remote PMC (RPM) as
described in Figure 3.1.
PNMS-CPM subnetwork
CPM
SCPM
CPM
CPM
SCPM
SCPM
RPM
RPM
SCPM
SCPM
RPM
RPM
RPM
RPM
RPM
SCPM
RPM
SCPM
RPM
RPM
CPM cluster
Subnetwork
PNMS network
Figure 3.1 PNMS NETWORK IMAGE
The Roles of CPM, SCPM and RPM and their rule are explained, 1. Basic function of PMC, 2.
Sizing rule of PMC, 3. Adoption Criteria of SCPM, and 4. Positioning of SCPM
-5-
ROI-S04188
1. Basic function of PMC

The PM Cards (PMC) operational mode is based on Master/Slave polling concept. The
network consists of a Central site PM Card (CPM), a possibly Sub-central site PMC (SCPM)
and a Remote Site PMC (RPM) installed with an individual software functioning as CPM,
SCPM and RPM.
Even though there is no difference in the hardware design, the PMC will be playing different
roles according to the installed software in a network management system as follows;
(1) Master mode (CPM, the head of CPM Cluster):
Master function of SCPMs/RPMs under it
Gateway function between PNMS and SCPMs/RPMs and routing the messages from
PNMS to SCPMs/RPMs and back.
The CPM is a data acquisition and control unit, which processes and then transfers all
the physical information of equipment. which is directly connected to the CPM. In
addition, CPM is connected to PNMS via a dedicated serial communications link or
LAN interface, and passes messages received from SCPM/RPMs to the PNMS for
display.
(2) Sub-Master mode (Sub-Central PMC, SCPM): the head of Subnetwork
Master function of RPMs under it
Gateway function between CPM and RPM and routing the messages from CPM to
RPM and back.
SCPM is a data acquisition and control unit which processes and then transfers all
the physical information of equipment which is directly connected to the SCPM. This
function is the same as that of RPM.(Slave Mode).
(3) Slave Mode (RPM):

RPM is a data acquisition and control unit. It monitors and controls equipment at some
remote location. Its prime task is to monitor and control and transfer data back to the
central site.
2. Sizing Rule of PMC
The sizing restriction of PMC is specified as follows:
(1) CPM-RPM Configuration:
In the case of CPM-RPM configuration, one CPM can handle up to13 RPM(s). To
increase the number of RPM to more than 14, another CPM is required.
One PNMS can handle up to 32 CPMs. (The detailed network sizing rule is described in
SECTION 6.)
Therefore in case of regional PNMS-CPM-RPM configuration, one PNMS can handle
max. 416 RPM(s) (32CPMsX13RPMs=416).
(2) CPM-SCPM-RPM Configuration:
In case more than 416 RPM(s) are required to be handled by one PNMS, SCPM is used.
One SCPM can handle up to 13RPM (S)
One CPM can handle up to 31 or 30 SCPM(s). (Refer section 6)
-6-
ROI-S04188
Therefore, if SCPM is used, the number of RPM which can be handled by one PNMS is
increased more than 416 RPMs.
As a rule of thumb, SCPM is used in order to increase the network size that can be
supervised by PNMS.
By using the SCPM, one CPM associated with 31 SCPMs can handle up to 416 NEs
(SCPMs and RPMs). This can result in a network configuration with the optimal number of
CPM(s) within one PNMS coverage.
(3) Adoption Criteria SCPM
As basic rule, if the number of RPM becomes 10, a SCPM is assigned on the head of the
group of RPM(s) then connected to CPM. As mentioned before, additional 3 RPM(S) may
be connected in the maximum case . However this possibility is reserved for future
expansion. (Of course, if no future expansion is sure, up to 13 RPM(S) may be connected
from initial stage.)
(4) Rule of SCPM
SCPM is considered as a kind of RPM with enhanced function such as Sub-master
in order to expand the network size. Therefore, depends on the network configuration,
there is a case that RPM may be applicable and there is a case that SCPM should be
applied. In other word, SCPM NE is NE which may be selected as RPM or SCPM
depends on the actual network configuration.
3.3.6 CPM/SCPM/RPM Role Change Function

When the PM card founds an interruption of polling signal from the upper PM card, this PM
card can function as CPM. Several PM cards do the role change. The PM card cease role
change when receiving a polling signal from its upper PM card. During role change, an alarm
is indicated but role change status cannot be viewed on the PNMS.
Example 1
If there is a link fault between RPM3 and 4, RPM4 will role change to CPM.
Example 2
If there is an equipment fault in RPM4, RPM5 will role change to CPM.
CPM1
RPM2
RPM3
RPM4
-7-
RPM5
RPM6
RPM7
ROI-S04188
4. PHYSICAL INTERFACE
Summary of physical interface of each equipment is described below.
DSC (9.6kbps) internal connection
10 Base-T
For upper management system
CPM
RS-232C
RS-232C/V.11
19.2kbps Async. 19.2kbps
(For Windows NT) Async.
or
LAN(10Base-T)
(NMS port)
RS-485
or
RS232C
9.6kbps
Async.
(NMS port)
PNMS
10Base T
(For Windows NT and Unix)
RS-232C (LA port)
SCPM
RPM
RS-232C (LA port)
RS-232C(COM port)
PNMT
Figure 4-1 Available Physical Interface
4.1 PNMS
4.1.1 Serial Interface
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 9 PIN
Communication rate
: 19.2 kbps (Asynchronous)
4.1.2 LAN Interface

Interface
: Ethernet (100/10 BaseT)
Connector type
: RJ-45
4.2 PNMT
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 9 PIN
Communication rate
-8-
RS-485
or
RS232C
9.6kbps
Async.
(NMS port)
ROI-S04188
4.3 PM Card
4.3.1 LA Port
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 15 PIN
Communication rate
4.3.2 NMS Port

4.3.2.1 PASOLINK (V3)
Functional
for PNMS connection
: RS232C/RS422/LAN(10Base-T)
for Back to Back connection : RS232C/RS485

Electrical
: V.24/V.11(for RS232C/RS422/RS485)
Mechanical
:DB 15 PIN
Communication rate
for PNMS connection
: 19.2 kbps (Asynchronous) (for RS232C/RS422)
for Back to Back connection : 9.6kbps (Asynchronous)

4.3.2.1 PASOLINK (V4)
Functional
for PNMS connection
: RS232C/RS422/LAN(10Base-T)
for Back to Back connection : RS232C/RS485
Electrical
: V.24/V.11(for RS232C/RS422/RS485)
Mechanical
: DB 15 PIN
RJ-45 (for PNMS(LAN) connection)
Communication rate
for PNMS connection
: 9.2 kbps (Asynchronous) (for RS232C/RS422)
for Back to Back connection : 9.6kbps (Asynchronous)
-9-
ROI-S04188
NMS port
LA port
(PASOLINK (V3))
NMS port(LAN)
NMS port (Serial)
(PASOLINK (V4))
- 10 -
LA port
ROI-S04188
5. PNMS COMMUNICATION INTERAFCE

The interface condition between PNMS and NEs (CPM,SCPM,RPM) is summarized in Figure
5.1 (Serial interface) and Figure5.2 (LAN interface). The physical interface at PNMS
Hardware is RS232C or 10baseT interface. The physical interface at CPM for PNMS
connection is Serial (RS-232C/V.11,19.2kbps, Async.) or LAN(10 Base-T). The choice of the
physical (Serial or LAN) interface at CPM should be done by the hardware replacement of PM
Card. The choice of the serial interface (RS232C or V.11) should be done by the PNMS
software.
The physical interface at CPM, SCPM and RPM for back to back connection is RS-232C or
RS-485 (9.6kbps, Async.). The choice of the physical interface (RS232C or RS485) at
CPM,SCPM and RPM should be done by the PNMS software.
Serial Interface between PNMS (Windows) and CPM
RPM
-1
CPM
RPM
-2
SCPM
RPM
-3
RPM
-4
PNMS-CPM
CPM-SCPM
SCPM-RPM
AP
SNMP/TFTP
SNMP/TFTP
SNMP/TFTP
Transport
UDP
UDP
UDP
Network
IP
IP
IP
Data Link
PPP
HDLC/NRM
HDLC/NRM
Physical*
RS-232C
19.2kbps Async.
RS-232C/485
9.6kbps Async.
RS-232C/485
9.6kbps Async.
*The converter will

be required for
other interfaces.
Figure5-1 PNMS Communication Architecture (Serial Interface)
LAN Interface between PNMS (Windows and UNIX) and CPM
CPM
RPM
-1
RPM
-2
SCPM
RPM
-3
LAN
RPM
-4
PNMS-CPM
CPM-SCPM
SCPM-RPM
AP
SNMP/TFTP
SNMP/TFTP
SNMP/TFTP
Transport
UDP
UDP
UDP
Network
IP
IP
IP
Data Link
Ethernet
HDLC/NRM
HDLC/NRM
Physical*
10baseT
RS-232C/485
9.6kbps Async.
RS-232C/485
9.6kbps Async.
Figure 5-2 PNMS Communication Architecture
- 11 -
ROI-S04188
6. NETWORK SIZING RULE

The following network sizing restriction is applied when NEC PASOLINK supervisory network
hierarchy is configured.
PNMS
for Windows
Maximum number of NE per
PNMS
Maximum number of CPM per
PNMS
PNMS
for UNIX
500/1000 NEs*(1) 1000-10,000NEs*(2)

32 ea*(3)
Maximum number of NEs per

CPM cluster
Maximum number of
subnetwork per CPM cluster
320 ea*(4)
416NEs*(5)
32 subnetwork *(6)
Maximum number of NEs per

subnetwork
Maximum number of
branch(multi-drop) per site
13,5,1*(7)
13*(8)
Table 6-1: Network Sizing Rule (Theoretical, Number of NE)
(1) Maximum number of NEs(500 or 1,000) is depends on PC Hardware specification.

(2) Software type for1,000/2,000/3,000/4,000/5,000/6,000/7,000/8,000/9,000/10,000 NEs
are available.
(3) Through LAN interface
(4) PNMS for UNIX has region level window(up to 10 regions can be supported per PNMS.
1 region includes up to 32CPMs. Therefore up to 320(10 regions X 32CPMs) CPMs can
be included per PNMS.
(5) This number is calculated by following formula.
Maximum number of NEs per CPM cluster
= [Maximum Number of subnetwork per CPM cluster] X [Maximum number of NE per
subnetwork ]
(6) This value has relation with maximum number of SCPM because the head NE of each
subnetwork is SCPM.
Maximum number of SCPMs : 31 (Single Master, Refer Figure 6.1)
30 (Dual Master, Refer Figure 6.2)
- 12 -
ROI-S04188
PNMS
SCPM1
Subnet1
SCPM N-1
SCPM2
Subnet2
Subnet3
SCPM N
SCPM31
Subnet N
Subnet N+1
Subnet32
Maximum number of subnetwork are 32 under a CPM.

Therefore maximum number of SCPM is 31.
: CPM
: SCPM
: RPM
Figure 6.1(Single Master)
PNMS
Dual Master
SCPM2
Subnet2
SCPM3
Subnet1
Subnet 3
Back to back connection

SCPM N-1
SCPM N
Subnet N+1
Subnet4
Radio Section
SCPM N+1 SCPM30
Subnet N+2
Subnet32
: CPM
: SCPM
: RPM
Maximum number of subnetwork are 32. In case of dual CPM configuration,

maximum number of SCPM is 30.
Figure 6.2 CPM (Dual Master)
(7) Maximum number of NE(SCPM and RPM)s in one subnetwork is depends on

subnetmask of its subnetmask setting by Operator. The relation between the
subnetmask and number of NE is described below.
Subnetmask
255.255.255.252
Assigned IP address
4
Available IP address
2
Number of NE
255.255.255.248
255.255.255.240
16
14
13
(8) This is applied for star configuration.
- 13 -
ROI-S04188
7. PNMS IP ADDRESSING
PNMS identifies each NE with IP address (IP v4). IP addressing scheme and requirement is
described with typical network.
7.1 Simple Trunk Line Network (Serial Interface)

To explain IP addressing of PNMS, Typical network example (simple Trunk line) is shown
(Figure 7.1.1). Serial interface is assumed for the interface between PNMS (Windows) and
CPM in this figure.
RS232C
19.2/9.6kbps, Async
PNMS
Remote Site-B
1
4
PNMS
(Windows)
Remote Site-C
Remote Site-A
Remote Site-D
: CPM
: RPM
Figure7.1.1 Typical Network Example (Simple trunk line [Physical Model])
Figure 7.1.2 shows a logical network of Figure7.1.1 and IP address assignment example. To
demonstrate connection of each NE with PNMS, 2 sub-networks, PNMS and CPM
sub-network (A) and PASOLINK CPM cluster network (B) are defined.
Subnet-A (PNMS-CPM Subnetwork)

PNMS
192.168.1.254
192.168.1.253
172.20.101.1
1
CPM
Central Site
172.20.101.4
172.20.101.7
172.20.101.3
172.20.101.5
172.20.101.8
172.20.101.6
172.20.101.2
2
RPM
3
4
5
6
7
RPM RPM RPM RPM RPM
8
RPM
Subnet-B (PASOLINK CPM cluster)
Figure7.1.2 Typical Network Example (Simple trunk line [Logical Model])
- 14 -
ROI-S04188
7.1.1 IP Addressing Scheme for PNMS-CPM Subnetwork

CPM NMS port and PC PNMS serial port must be located in the same sub network as shown
Figure7.1.2. In this figure, the CPM is connected to PNMS through RS-232C interface and
PPP encapsulation. The CPM NMS port IP address acts as the gateway to its PASOLINK
cluster. For example, CPM passes an IP packet from PNMS with 172.20.101.3 to the
destination NE.
For this PNMS and CPM sub-network (A), PNMS uses a subnet mask of 255.255.255.252.
(fixed). One PNMSCPM sub network includes 4 IP addresses accordingly. However 2 IP
addresses are not available because one is assigned for network address, the other is
reserved for broadcast address.
7.1.2 IP Addressing Scheme for PASOLINK CPM Cluster
This section shows the IP addressing scheme in PASOLINK CPM cluster (B). PNMS uses a
Subnet mask of 255.255.255.240 for this sub-network in this case. Therefore one
sub-network in CPM cluster has 16 IP addresses. However available IP addresses for
Remote PM Card (RPM) are 13 as shown in section 6 Network sizing rule. It is because one
is assigned for network address, the other is reserved for broadcast address, in addition one
IP address is assigned for CPM.
In addition, Operator can set subnetmask in accordance with the number of NE in each
sub-network in case the number of NE in a subnetwork is small. The relation between the
subnetmask and the number of NE in the subnetwork is described below.
Subnetmask
Available
IP address
2
Number of NE
255.255.255.252
Assigned
IP address
4
255.255.255.248
255.255.255.240
16
14
13
Table 7.1.1 Relation between the subnetmask and number of NE
For reference assigned IP address and available IP address of each sub-network are shown
in following table.
Subnet-A (Subnetm ask : 255.255.255.252(Fixed))

192.168.1. 252 255
(Assigned IP Address(Fixed))
(Available IP Address(Fixed))
192.168.1. 253 254
Subnet-B(Num ber of NEs : 7NEs ->Subnetm ask : 255.255.255.240
(Assigned IP Address)
172.20.101. 0 15
172.20.101. 1 14
(Available IP Address)
Table7.1.2 Exam ple for IP address planing in each Subnet
- 15 -
ROI-S04188
7.2 Simple Trunk Line Network (LAN Interface)

To explain IP addressing of PNMS, Typical network example (simple Trunk line) is shown
(Figure 7.2.1). Serial interface is assumed for the interface between PNMS and CPM in this
figure.
LAN(10base-T)
PNMS
Remote Site-B
1
4
2
PNMS
Remote Site-C
Remote Site-A
Remote Site-D
: CPM
: RPM
Figure7.2.1 Typical Network Example (Simple trunk line [Physical Model])
sub-network (A) and PASOLINK CPM cluster network (B) are defined.
Subnet-A (PNMS-CPM Subnetwork)

PNMS
172.20.100.1
172.20.100.2
172.20.101.1
1
CPM
Central Site
172.20.101.4
172.20.101.7
172.20.101.5
172.20.101.3
172.20.101.6
172.20.101.8
172.20.101.2
2
RPM
3
4
5
6
7
RPM RPM RPM RPM RPM
8
RPM
- 16 -
ROI-S04188

CPM NMS port and PC PNMS LAN port must be located in the same sub network as shown
Figure7.2.2. In this figure, the CPM is connected to PNMS through LAN(10 Base-T) interface.
The CPM NMS port IP address acts as the gateway to its PASOLINK cluster. For example,
CPM passes an IP packet from PNMS with 172.20.101.3 to the destination NE.
For this PNMS and CPM sub-network (A), Operator can set subnetmask in accordance with
the number of NE in this subnetwork. In case of network example described in Figure 7.4,
PNMS uses a subnet mask of 255.255.255.252 because this subnetwork has one CPM
(Refer to Table7.1.1)
Refer to section 7.1.2.
in following table.
Subnet-A (Num ber of NEs : 1NEs ->Subnetwask : 255.255.255.252

172.20.100. 0 3
172.20.100. 1 2
Subnet-B (Num ber of NEs : 7NEs -> Subnetm ask : 255.255.255.240
172.20.101. 0 15
172.20.101. 1 14
Table7.2.1 Exam ple for IP address planing in each Subnet
7.2.3 Plural CPM Configuration

Figure 7.2.3 shows plural CPM configuration. Figure 7.2.4 is logical Model of this
configuration. In this case, Subnetmask of PNMS-CPM subnetwrok is assigned to
255.255.255.248 as shown Table 7.2.2.
- 17 -
ROI-S04188
Remote Site-C
13
Remote Site-B
11
14
12
Remote Site-F
PNMS
23
Remote Site-E
21
24
22
Remote Site-I
Remote Site-H
31
33
34
32
Figure7.2.3 Typical Network Example

(Simple trunk line with plural CPM [Physical Model])
Subnet-A (PNMS-CPM subnetwork)
PNMS
1
CPM
18
RPM
13
RPM
2
CPM
3
CPM
12
RPM
32
33
RPM RPM
22
23
RPM RPM
38
RPM
Subnet-D
28
RPM
Subnet-C
Figure7.2.4 Typical Network Example (Multi-branch network [Logical Model])
Subnet-A (Number of NEs : 3 NEs -> Subnetmask : 255.255.255.248)

172.20.100. 0 7
172.20.100. 1 6
Subnet-B (Number of NEs : 10 NEs -> Subnetmask : 255.255.255.240)
172.20.101. 015
172.20.101. 114
Subnet-C (Number of NEs : 10NEs -> Subnetmask : 255.25.255.240)
172.20.102. 0 15
172.20.102. 1 14
Subnet-D (Number of NEs : 10NEs -> Subnetmask : 255.255.255.240)
172.20.103. 015
172.20.103.1 14
Table7.2.2 Example for IP address planing in each Subnet
- 18 -
ROI-S04188
7.3 Simple Trunk Line Network (through IP network)

Figure7.3 .1shows typical network example (simple Trunk line) with LAN interface through IP
network between PNMS and CPM.
IP
network
RS232C or V.11
19.2/9.6kbps, Async
or
LAN(10 base-T)
PNMS
Remote Site-B
4
2
3
Remote Site-C
Remote Site-A
6
: Router
: CPM
: RPM
Remote Site-D
Figure 7.3.1 Typical Network Example (Simple trunk line [Physical Model])
demonstrate connection of each NE with PNMS, 2 sub-networks, Router and CPM
sub-network and PASOLINK CPM cluster network are defined.
PNMS
Subnet-A (Router-CPM Subnetwork)

IP
network
172.20.100.1
172.20.100.2
172.20.101.8
172.20.101.1
1
CPM
Central Site
172.20.101.4
172.20.101.7
172.20.101.3
172.20.101.5
172.20.101.6
172.20.101.2
2
RPM
3
4
5
6
7
RPM RPM RPM RPM RPM
8
RPM

- 19 -
ROI-S04188
7.3.1 IP Addressing Scheme for Router-CPM Subnetwork

CPM NMS port and the Router Serial or LAN port must be located in the same sub network as
shown Figure 7.3.2. In this figure, the CPM is connected to the router and must be added to
the IP routing table of the subnetwork in the CPM Cluster into the router and acts as the
gateway to the PASOLINK CPM cluster. For example, an IP packet with 172.20.101.3 is sent
to the IP network, the router passes this to the CPM NMS port and then the CPM passes it to
the destination NE, which is the recipient of the packet as shown in Figure 7.3.2.
For this Router and CPM sub-network, PNMS uses a subnet mask of 255.255.255.252
(fixed) for serial interface. For LAN interface Operator can set subnetmask in accordance
with the number of NE in this network.
7.4 Multi Sub-Branch Network

Figure7.4.1 shows typical network example (Multi sub-branch network). In this figure serial
interface between PNMS and CPM is assumed.
RS232C
19.2/9.6kbps, Async
1
PNMS
(Windows)
Remote Site-B
Central Site
4
Remote Site-E
Remote Site-C
Remote Site-A
Remote Site-G
7
10
13
12
11
Remote Site-D
1
2
: CPM
: RPM
Remote Site-F
8
RS485
9.6kbps, Async
14
: SCPM
Figure 7.4.1 Typical Network Example (Multi sub-branches network[Physical Model])
Figure 7.4.2 shows a logical model of Figure7.4.1 and IP address assignment example. To
sub-network (A) and PASOLINK CPM cluster network (B and C) are defined.
PNM S
Subnet-B
172.20.100.1
(PASOLINK CPM cluster)

172.20.101.7
172.20.101.4
172. 20.101.8
172.20.101.3
172.20.101.5
172.20.100.2
172.20.101.1
1
CPM
Central Site
172.20.101.2
172. 20.101.6
172.20.101.9
3
4
5
6
7
8
2
14
RPM RPM RPM RPM RPM RPM SCPM RPM
172.120.101. 21 172.20.101. 20 172.20.101.17
172.20.101. 19
172.20.101. 22
172.20.101.18
Subnet-A
(Router-CPM Subnetwork)
13
12
11
10
9
RPM RPM RPM RPM RPM
Subnet-C
Figure 7.4.2 Typical Network Example (Multi sub-branches network[Logical Model])
- 20 -
ROI-S04188

PNMS uses a Subnet mask of 255.255.255.240 for subnet-B. Therefore one sub-network in
CPM cluster has 16 IP addresses. Each sub network can accommodate 16 IP addresses.
Available IP addresses for Remote PM Card (RPM) are 13. Subnet-B is assigned from
172.20.101.0 to 172.20.101.15. (16 IP Addresses) However 172.20.101.0 and
172.20.101.15 is not available because 172.20.101.0. is sub network address and
172.20.101.15 is reserved for broadcast address. In addition one IP address is assigned on
Central PM Card. Therefore 13 IP addresses (for 13 RPMs) are available in Subnet-B (same
as for all other sub network).
In addition IP address for next sub-network (Subnet-C) shall be assigned from
172.20.101.16. (172.20.101.17 to172.20.101.30 is available), even if Subnet-B has less than
13 NEs (for example only one NE), Subnet-C is started to assign from 172.20.101.17. As
explained section 7.1.2, operator can set subnetmask for each subnetwork. For example,
255.255.255.248 can be assigned for Subnet-C in case there is no additional NE in
Subnert-C in the future.
One CPM cluster can include maximum 32 sub-networks as explained in Section 6.
Therefore one CPM cluster can accommodate maximum 512 IP addresses(16 IP address x
32 sub-networks) . This maximum 512 consecutive IP addresses are reserved in PNMS. Two
(2) class C sub-networks (for example, 172.20.101.** and 172.20.102.**) are required to
assure the 512 IP Addresses.
in Table 7.4.1
Subnet-A : 172.20.100. 0 3
172.20.100. 1 2
Subnet-B : 172.20.101. 0 15
: 172.20.101. 1 14
Subnet-C : 172.20.101.16 31
172.20.101. 17 30
Table 7.4.1 Exam ple for IP address planing in each Subnet
- 21 -
ROI-S04188
7.4.3 Example of IP Addressing for Multi Sub-Branch Network

Figure7.4.3 show the example of IP address assignment for CPM cluster with 8
sub-network. (In this example, all subnetmask is assigned to 255.255.255.240.)
172.18. 0.66
RPM
SCPM
171.18.0. 110
172.18.0. 97
172.18. 0.67
Router and CPM

subnetwork
172.18.0.65
172.18.0.78
172.18.0.34
RPM
RPM
SCPM
172.18.2.1
172.18.2.2
172.18. 0. 36
172.18.0.83
RPM
172.18.0.17
172.18.0.81
RPM
SCPM RPM
CPM
172.18.0. 35
172.18.0. 94
PNMS
172.18.0.18
172.18.0. 37
172.18.0.82
172.18.0.33
RPM
172.18. 0.1
SCPM
172.18.0.126
RPM SCPM
172.18. 0. 113
172.18.0.62
172.18. 0.51
RPM
172.18.0. 50
172.18.0. 49
RPM RPM
SCPM
172.18.0.2
Figure 7.4.3 Network Example (IP address Scheme)
Table 7.4.2 shows assigned IP addresses and available IP addresses of each sub network of
this multi sub-branch network.
Subnet-A : 172.18.2. 1
(Router Serial IP Address)
: 172.18.2. 2
(CPM NMS port IP Address)
Subnet-B : 172.18.0. 015
: 172.18.0. 1 14
Subnet-C : 172.18.0. 1631
: 172.18.0. 17 30
Subnet-D : 172.18.0. 3247
: 172.18.0. 33 46
Subnet-E : 172.18.0. 4863
: 172.18.0. 4962
Subnet-F : 172.18.0. 6479
: 172. 18.0. 6578
Subnet-G : 172.18.0.8095
: 172.18.0.8194
Subnet-H : 172.18.0.96111
: 172.18.0.97110
Subnet-I : 172.18.0.112127
: 172.18.0.113126
Table 7.4.2 : Example for IP address planning in each Subnet
- 22 -
ROI-S04188
7.5 PNMS IP Addressing Summary

Figure 7.5.1 (Serial Interface) and Figure 7.5.2 (LAN interface) describe the summary of
PNMS IP addressing scheme.
Serial
Interface
PNMS (Windows)
Subnet Mask is 255.255.255.252
(11111111.11111111.11111111.11111100)
Assigned address is 4.
All 1s and 0s are reserved.
Therefore 2 address are available.
CPM
Subnet Mask is selectable by Operator.

SCPM
SCPM
SCPM
RPM
RPM
RPM
255.255.255.252
(11111111.11111111.11111111.11111100)
255.255.255.248
(11111111.11111111.11111111.11111000)
255.255.255.240
(11111111.11111111.11111111.11110000)
Figure 7.5.1 IP address Scheme for PNMS (Serial interface between PNMS and CPM)
LAN
Subnet Mask is selectable by Operator

according to the number of CPM.
CPM
Subnet Mask is selectable by Operator.

SCPM
SCPM
SCPM
RPM
RPM
RPM
255.255.255.252
(11111111.11111111.11111111.11111100)
255.255.255.248
(11111111.11111111.11111111.11111000)
255.255.255.240
(11111111.11111111.11111111.11110000)
Figure7.5.2 IP address Scheme for PNMS (LAN interface between PNMS and CPM)
7.6 IP Address Requirement for Customer

During the Network Design phase, following IP address must be required in order for each
NEs to connect to the PNMS.
1) PNMS(Router)CPM sub-network
IP address for Router Serial port or PNMS (PC or WS) port
IP address for CPM NMS
2) PASOLINK CPM cluster network
CPM cluster sub-network Address for each NE
(Two class C sub networks are required for maximum 512 IP addresses)
- 23 -
ROI-S04188
8. INTEROPERABILITY WITH OTHER NETWORK

If the network is composed of only PASOLINK, the integration of PNMS will be simple.
However in case of the existing customers transmission network, interconnectivities and
interoperability among different manufacturers will have to be confirmed. The purpose of this
section is to allow the PASOLINK supervisory network to managed each heterogeneously
located PASOLINK hop through customers existing transmission network and IP network.
For example, the interconnected equipments could be:
Other transport equipments from manufacturers
Routers such as Cisco
8.1 Connection Availability

Following table is the connection availability between PASOLINK and Other equipment
(other manufacture equipment and NEC equipment other than PASOLINK) of RS485
interface.
Table 8.1 Connection Availability
Point to point Connection
PASOLINK
(RS485)
Proposed
Solution
Point to multi-point
(daisy chain) connection
Other
equipment
(RS485)
Other
equipment
(RS422)
Other
equipment
(RS485)
Other
equipment
(RS422)
PASOLINK
RS485
Not Available
(Note 1)
(Note 2)
Not Available
(Note 1)
Not Available
Available
Convert RS422
by using HYB CONV
Convert RS422
by using HYB CONV
Note.1) Because the method of connecting data signal lines in plural connections in point to
multi-point line is not determined, it is not possible to connect equipment from different
manufacturers unless connection test between PASOLINK and other equipment is
required.
Note.2) Terminal impedance of other manufacture equipment is not clear. Therefore output logical
condition of other manufacture equipment is not clear in high impedance condition. In this
case it is impossible to connect each other. (Connection test is required between
PASOLINK and other equipment.)
- 24 -
ROI-S04188
9. TYPICAL CONFIGURATION
The PNMS supports a variety of radio topologies. That is, there are many ways in which the
connections can be made between PNMS, CPM, SCPM and RPM. The system design is to
analyse the network and customer requirement, to decide the PASOLINK network
configuration, to estimate the cost and provide customer with some optimised solutions.
Based on the radio network information a PASOLINK network management system can be
formed by following steps specified below:
Select PNMS Architecture and decide on the number of PNMS hardware.
Decide that the PASOLINK network configuration based on given radio topology.
Divide the monitored network into sub-networks, which is geographically and
functionally manageable for monitoring and controlling in accordance with section
6.Network Sizing rule.
Decide on the PMC operation modes (such as CPM, SCPM, and RPM) and the
PMC
Determine the data communication path.
9.1 Point to Point Connection

Figure 9.1 shows the PASOLINK supervisory interface with existing network (dedicated line
such as DSC) between PNMS and CPM.
PASOLINK CLUSTER
RS-232C
19.2kbps
ASYNC
Existing Network (Dedicated line)

DSC 19.2kbps, ASYNC
PNMS
(Windows )
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER

DSC 19.2kbps, ASYNC
RS-232C
19.2kbps
ASYNC
LAN
R
PNMS
(UNIX or
Windows )
RS-232C/V.11
19.2kbps
ASYNC
Figure 9.1 Interoperability with other manufacture equipment
- 25 -
ROI-S04188
Figure 9.2 show the PASOLINK supervisory interface with existing network (PSTN or IP
network) between PNMS and CPM.
RS-232C/V.11
9.6kbps
ASYNC
RS-232C
9.6kbps
ASYNC
Continuous connection is needed
PASOLINK CLUSTER
PSTN
MD
MD
PNMS
(Windows )
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER
IP
Network
R
PNMS
(UNIX or
Windows)
LAN
LAN
PASOLINK CLUSTER
IP
Network
:Modem
:Router MD
: CPM
Figure 9.2 Interoperability with other network
: RPM
Figure 9.3 show the PASOLINK supervisory interface with existing network between
PASOLINKs.
RS-232C, RS-485
9.6kbps
ASYNC
RS-232C or RS-485
9.6kbps
ASYNC
RS-232C
19.2kbps
ASYNC
LAN
PASOLINK CLUSTER
R
19.2/9.6 kbps, ASYNC
PNMS
(UNIX or
Windows)
PASOLINK CLUSTER
RS-232C or RS-485
9.6kbps
ASYNC
RS-232C
19.2kbps
ASYNC
LAN
PASOLINK CLUSTER
PSTN
MD
RS-232C or RS-485
9.6kbps
ASYNC
MD
R
PNMS
(UNIX or
Windows)
PASOLINK CLUSTER
Figure 9.3 Interoperability with other network (point to point connection)
- 26 -
ROI-S04188
9.2 Point to Multi-Point Connection

Figure 9.4 show the PASOLINK supervisory interface with existing network between
PASOLINKs (point to multi-point connection). Because of the reason described section 8.1,
HYB converter (Refer to section 12.1) is required to combine and divide the supervision
signal.
RS-232C, RS-485
9.6kbps
ASYNC
RS232C, RS-485
9.6kbps
ASYNC
RS-232C
19.2kbps
ASYNC
LAN
PASOLINK CLUSTER
H
Y
B
Existing Network
(Dedicated line)
19.2/9.6 kbps, Async
H
Y
B
PNMS
(UNIX or
Windows)
C
O
N
V
C
O
N
V
:Router
: CPM
: RPM
: Existing Network (Dedicated line)
Figure 9.4 Interoperability with other network
9.3 Multi-Cluster Network (1) - Dedicated Leased Line (Serial Interface) Figure 9.5 shows a multi-cluster network, monitored and controlled by PNMS through serial
interface and dedicated line such as DSC. Multiple connections on central computer are
realized by RS232C extension port installed in the PC. 19.2kbps (RS232C interface) are
required for dedicated leased line or Digital Service Channel.
RS-232C/V.11
19.2kbps
ASYNC
RS-232C
19.2kbps
ASYNC
PASOLINK CLUSTER
19.2kbps, ASYNC
Multi-serial board
(inserted into PCI SLOT)
PNMS
(Windows)
PASOLINK CLUSTER
Figure 9.5 Multi-branch network through Digital Service Channel

with PNMS Serial interface
- 27 -
ROI-S04188
9.4 Multi-Cluster Network (2) - Dedicated Leased Line (LAN Interface) Figure 9.6 shows a multi-cluster network, monitored and controlled by PNMS through LAN
interface and dedicated line such as DSC. 19.2kbps (RS232C interface) are required for
Router port.
RS-232C/V.11
19.2kbps
ASYNC
RS-232C
19.2kbps
ASYNC

PASOLINK CLUSTER
19.2kbps, ASYNC
PNMS
(UNIX or
Windows )
PASOLINK CLUSTER
Figure 9.6 Multi-branch network through Digital Service Channel

with PNMS Serial interface
9.5 Multi-Cluster Network (3) - PSTN (Serial Interface) Figure9.7 shows a multi-cluster network, monitored and controlled by PNMS through serial
interface and PSTN. RS232C interface (19.2kbps) are required for Modem.
RS-232C
19.2kbps
ASYNC
PASOLINK CLUSTER
MD
MD
Multi-serial board
(inserted into PCI SLOT)
PSTN
RS-232C
19.2kbps
ASYNC
MD
MD
MD
MD
PNMS
(Windows)
PASOLINK CLUSTER
MD
MD
Figure 9.7 Multi-branch network through PSTN with PNMS Serial interface
- 28 -
ROI-S04188
9.6 Multi-Cluster Network (4) - PSTN (LAN Interface) Figure 9.8 shows a multi-cluster network, monitored and controlled by PNMS through LAN
interface and PSTN. RS232C interface (19.2kbps) are required for Modem.
RS-232C
19.2kbps
ASYNC

PASOLINK CLUSTER
MD
MD
PSTN
RS-232C
19.2kbps
ASYNC
MD
MD
R
MD
PNMS
(UNIX or
Windows )
MD
PASOLINK CLUSTER
MD
MD
Figure 9.8 Multi-branch network through PSTN with PNMS LAN interface
9.7 Multi-Cluster Network (5) - IP Network (LAN Interface) Figure 9.9 and Figure 9.10 shows a multi-cluster network, monitored and controlled by
PNMS through LAN interface and IP network. Figure 9.9 shows serial interface is assumed
between Router port and CPM. Figure 9.10 shows LAN interface is assumed between Router
and CPM.
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER
LAN
R
R
IP NETWORK
PNMS
(UNIX or
Windows )
PASOLINK CLUSTER
Figure 9.9 Multi-branch network through IP network
- 29 -
ROI-S04188
LAN
PASOLINK CLUSTER
LAN
R
R
IP NETWORK
PNMS
(UNIX or
Windows )
PASOLINK CLUSTER
Figure 9.10 Multi-branch network through IP network
9.8 CPM Reduction Solution

In accordance with customers network such that many CPM clusters scattered in all over the
region, plural CPMs are required to be monitored and controlled by PNMS as shown in
Figure9.11 and Figure 9.12. In such cases the number of the required Router serial ports
increases according to the number of CPMs. To reduce CPMs and reduce the number of
Routers serial ports, following solution is proposed.
Up to 416 NEs
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER

19.2kbps, ASYNC
RS-232C
19.2kbps
ASYNC
Up to 416 NEs
Up to 416 NEs
Up to 416 NEs
PASOLINK CLUSTER
PNMS
(UNIX or
Windows)
: CPM
: SCPM
: RPM
Figure 9.11 Multi cluster network through Digital Service Channel
- 30 -
ROI-S04188
PASOLINK CLUSTERs
RS-232C
19.2kbps
ASYNC
PASOLINK CLUSTERs
Customer
IP Network
RS-232C
19.2kbps
ASYNC
PASOLINK CLUSTERs
PNMS
: CPM
Figure 9.12 Basic connection through existing radio line and IP network
(point to multi-point)
The concept for reducing CPM is shown Figure 9.13. The CPM function is located at PNMS
site. The SV signal from PASOLINK clusters scattered all over the region are concentrated
(combined) by mediation device called HYB CONV (Hybrid Converter) at PNMS site. Then
the concentrated signal is connected to CPM function. (The detailed function of HYB CONV
is described in Section 12.1.)
RS-232C or RS485
9.6kbps
ASYNC
PASOLINK CLUSTER
9.6 kbps, ASYNC
SV signal
Concentrated Function
RS-232C
19.2kbps
ASYNC
H
Y
B
PASOLINK CLUSTER
Up to 416 NEs
CPM
Function
C
O
N
V
PNMS
(UNIX or
Windows)
: CPM
: SCPM
: RPM
This CPM function is realized by usage of mediation device, called MIU (Management
Interface Unit), locating at PNMS site as shown Figure 9.14 and Figure 9.15.(The detailed
function of MIU is described in Section 12.2.)
By using HYB CONV and MIU, the SV signal from many PASOLINK cluster is combined into
one signal and send to a serial port of Router.
- 31 -
ROI-S04188
RS-232C
19.2/9.6kbps
ASYNC
Existing radio line

PASOLINK CLUSTER
5 port
RS-232C or RS485 port

9.6kbps, ASYNC
H
Y
B
MIU
C
O
N
V
Up to 416 NEs
RS-232C/V.11
19.2kbps
ASYNC
or
LAN(10BASE-T)
PNMS
RS-485
9.6kbps
ASYNC
H
Y
B
C
O
N
V
PASOLINK CLUSTER
: CPM
: SCPM
Up to 13 SCPM
5 port
: RPM
Figure 9.14 CPM reduction solution-1
for basic connection through existing radio line (point to multi-point)
PASOLINK CLUSTER

: CPM

19.2/9.6kbps
ASYNC
PASOLINK CLUSTER
PASOLINK CLUSTER

19.2/9.6kbps
ASYNC
H
Y
B
C
O
N
V
MIU
H
Y
B
C
O
N
V
MIU
H
Y
B
C
O
N
V
MIU
: SCPM
: RPM
R
Customer
IP Network
R
PNMS
Figure 9.15 CPM reduction solution-2

for basic connection through existing radio line and IP network (point to multi-point)
- 32 -
ROI-S04188
10. PNMS CONFIGURATION

Basically cold stand-by configuration is proposed for PNMS redundancy. In addition Parallel
PNMS can be proposed.
10.1 Cold Stand-by PNMS Principle

Basically cold stand-by PNMS is pre- installed PNMS software. However network
configuration file, event log data and performance monitor data is not included in cold
stand-by PNMS. Cold stand-by PNMS should be assigned the same IP addresses as on-line
PNMS and not connected with PNMS network.
Therefore in case that on-line PNMS is down, one of following two procedures could be
taken.
(1) Remake the network configuration file in the cold stand-by PNMS same as that of on- line
PNMS to monitor and control the same network. (Event log and Performance monitor
data of on-line PNMS can not be retrieved in cold stand-by PNMS.
(2) Operator takes a back up data of network configuration file to cold stand-by PNMS disk
when network configuration is changed. In addition (if desired), Operator is
recommended to perform regular back up of event log data and performance monitor
data to cold stand-by disk daily, for instance.
When on-line PNMS is down, Operator should connect the stand-by PNMS with PNMS
network. (The data between the timing of last back up and timing of on-line PNMS clash
cannot be retrieved.)
10.2. Back Up PNMS Data (UNIX version only)

PNMS (UNIX) provides GUI-based backup tool for making backups of the following PNMS
data to another disk. There are two types of PNMS backups method, scheduled backup
(every day or every week) and Manual backup (unscheduled).
-Network configuration data
-User security data
-Performance monitor data
-Logging data
10.3 Parallel PNMS

Two PNMS can monitor and control PASOLINK network simultaneously and independently.
These are connected to CPM through Router, as shown Figure 10.1. This configuration is
called Parallel PNMS. Parallel" means that status change (ex. Alarm and event occurrence)
of each NE is recognized in both PNMS. Even if the one PNMS is down, the other PNMS can
monitor and control NEs in the network. However, there is case that logging data and
performance monitor data are not synchronized between the PNMS-1 and PNMS-2, i.e.,
such data is not stored into both PNMSs.
- 33 -
ROI-S04188
For example, assuming that PNMS-1 is in operation and PNMS-2 is down:

a) Logging data
If alarms occur in PASOLINK network, the alarm log is registered in PNMS-1. However these
logs are not registered in PNMS-2. After PNMS-2 is re-started, the logging data is not
synchronized between PNMS-1 and PNMS-2. In this case Operator is required to download
the logging data from PNMS-1and to upload it to PNMS-2 desired directory and re-start
PNMS-2, if Operator want to synchronize the logging data of both PNMS.
b) Performance monitor data
PNMS collects performance data stored in each PM Cards in the network once a day.
(Collecting time can be set by Operator.) If PNMS-1 collects performance data of NEs in the
network, PNMS-1 stores performance data of the day. However PNMS-2 does not store the
performance data. Therefore, after PNMS-2 is re-started, the performance data is not
synchronized between PNMS-1 and PNMS-2. In this case Operator is required to download
the performance data from PNMS-1 and upload it to PNMS-2 desired directory and re-start
PNMS-2, if Operator want to synchronize the performance data of both PNMSs.
c) Network configuration data
In addition, the network configuration data can be created from either Network Configuration
tool (PNMS) and is not automatically transferred to another PNMS regardless whether PNMS
is in operation or down. Therefore, in order to synchronize such data between PNMSs,
whenever such data is created or changed from one PNMS, Operator shall remake such data
in another PNMS to be identical to those in one PNMS accordingly.
Network Operation Center-1
PNMS-1
Alarm or Event Trap
LAN
Alarm or Event Trap
Customer IP network
LAN
PNMS-2
: ROUTER
Regional Network Operation Center-2

Figure 10.1Parallel PNMS
- 34 -
: PASOLINK
ROI-S04188
10.4 Hierarchical PNMS configuration

Central and Regional PNMS can be configured as shown in the Figure 10.2. Regional PNMS
monitors and controls PASOLINKs in its region. Central PNMS monitors and controls all
PASOLINKs in all regions (up to 10 regions).
Regional PNMS supports up to 500/1,000 NEs (PNMS for Windows) or 1,000 NEs (PNMS for
UNIX). Central PNMS supports up to 2,000 NEs (PNMS for Windows) or 10,000 NEs (PNMS
for UNIX).
Each NE is monitored and controlled by both Central and Regional PNMS. It means that even
if Central PNMS is down, each Regional PNMS can monitor and control NEs in its region.
In a similar way, if a regional PNMS is down, the Central PNMS can monitor and control NEs
under the region where the Regional PNMS is down.
Central and Regional PNMS work independently. In case one of them is down following
situation occurs for logging data and performance monitor data.
For example, assuming that Central PNMS is in operation and a Regional PNMS is down:
a) Logging data
If alarms occur in the PASOLINK network, the alarm logs are registered in only Central
PNMS. However these logs are not registered in Regional PNMS. Even if Regional PNMS is
re-started, the logging data is not recorded in the Regional PNMS.
b) Performance monitor data
PNMS collects performance data stored in each NE in the network once a day. Operator can
set time to collect and what NEs to collect. In case Central PNMS collects performance data
of NEs in the network when regional PNMS is down, only Central PNMS stores performance
data of the day and Regional PNMS does not store them. Even if Regional PNMS is
re-started, the performance data is not stored in the Regional PNMS.
Network configuration work

The network configuration file for Regional PNMS and each NE is created by Network
Configuration tool in Regional PNMS site and imported to Regional PNMS by Update
network configuration window. Operator should send network configuration file for each
Regional PNMS to Central PNMS (for example by E-mail). In Central PNMS, Operator
imports each regional PNMS configuration file to Central PNMS by Update network
configuration window in order to monitor and control all regions.
If network configuration is modified in a region, Operator modifies network configuration file in
each Regional PNMS site and import it to Regional PNMS by Update network configuration
window. The modified network configuration file is sent to Central PNMS, for example by
E-mail, and imported to it by Update network configuration window.
- 35 -
ROI-S04188
Network Operation Center

Central PNMS
Regional PNMS
Regional PNMS
Regional Operation Center-4
Customer IP Network
Figure 10.2 Central/Regional PNMS Configuration
Note) Following function is not supported for Central PNMS. These functions are done by
Regional PNMS.
1.
Link performance history (collection of link performance monitor data stored in each NE
per day) function to avoid traffic congestion
2.
Automatically Set date and time function
3.
Dialup connection function (only for PNMS for Windows, This function is not used
because IP connection is used.)
4.
Upper SNMP interface function (only for PNMS for Windows)
- 36 -
ROI-S04188
11. NETWORK CONFIGURATION WORK

11.1 PNMS for Windows
11.1.1 Install PNMS
1. Install PASOLINK hardware.
If the PASOLINK system exists with configuration file, skip Step 2 through Step 6.
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
Figure11.1 Network Example
2. Decide each PM Card mode (for example Figure 11.2).
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
3. Create configuration file on PNMS for each PM Card and PNMS by Network
Configuration tool.
4. Export configuration file of each PM Card and PNMS to the directory set up in the
Network Configuration tool.
- 37 -
ROI-S04188
5. Copy the configuration files of each PM Card from PNMS PC to PNMT and download
them to each PM Card on site using PNMT.
6. Import configuration file for PNMS using Update Network Configuration window
function on PNMS.
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
7. Connect PNMS to CPM and confirm the connection. After that it is possible to monitor
and control each NE.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
Figure11.4Network Example
- 38 -
ROI-S04188
11.1.2 Modify Network Configuration

11.1.2.1 Example 1 : Add New HOP in Subnet-4
1. Plan to add new HOP in Subnet-4.
Subnet-4
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
Figure 11.5 Network Example
2. Decide the new PM Card mode(CPM, SCPM or RPM) (for example Figure 11.7).
3. Create configuration file for new PM card and PNMS by Network Configuration tool.
4. Export configuration file of each PM Card and PNMS to the directory set up in Network
Configuration tool.
5. Copy the configuration files of new PM Card from PNMS PC to PNMT and download
them to new PM Card by PNMT and install new NE(ODU and IDU) on site.
6. Download the modified configuration files to the existing PM Cards, Master PM Cards
(SCPM of new NEs subnetwork and CPM which such SCPM is belonging) and a PM
Card which is connecting new HOP physically) from PNMS. Refer to Figure 11.6.
(Downloading from PNMT is also available. In this case copy the configuration files for
each NE from PNMS PC to PNMT is required.)
- Master PM Card (Sub-CPM in Subnet-4): Modify Network Configuration file to
recognize the added new HOP. (System Configuration file is not necessary to be
modified.)
- Existing PM card connecting with new HOP physically : Modify System
Configuration file to recognize connecting with new HOP. (Although Network
Configuration file is also necessary to be modified, the network configuration file is
automatically modified and downloaded from Master PM CARD (CPM or SCPM) to
the RPM under it.)
-Other PM Cards in this CPM cluster: Although Network Configuration file is
necessary to be modified, the network configuration file is automatically modified
and downloaded from Master PM CARD (CPM or SCPM) to each PM Cards under it.
(System Configuration file is not necessary to be modified.)
- 39 -
ROI-S04188
Subnet-4
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
Figure 11.6Network Example
7. Update Network configuration file for PNMS using Update Network Configuration
window function PNMS. After that it is possible to monitor and control added NE.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
- 40 -
ROI-S04188
11.1.2.2 Example 2 : Add New Subnetwork

1. Plan to add new subnetwork.
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
2. Decide the new PM Card mode (CPM, SCPM or RPM) (for example Figure 11.10).
3. Create configuration file for new subnetwork and PNMS by Network Configuration tool.
4.
Export configuration file of each PM Card and PNMS to the directory set up in the to
5. Copy the configuration files of new PM Card from PNMS PC to PNMT and download the
configuration file for new PM Card by PNMT and install new NE (ODU and IDU) on site.
6. Download the modified configuration file, to the existing PM Card (Master PM Card
(CPM which new subnetwork is belonging and all SCPMs in the CPM cluster.) and a
PM Card which connecting with new HOP physically from PNMS. Refer to Figure 11.9.
- Master PM CARD (CPM and all SCPMs in the CPM cluster): Modify Network
Configuration file to recognized the added new subnetwork. (System Configuration
file is not necessary to be modified.)
- Existing PM Card connecting with new subnet physically: Modify System
Configuration file to be recognized connecting new HOP. (Although Network
the RPM under it.)
- Other PM Card in this CPM Cluster: Although Network Configuration file is
and downloaded from Master PM CARD (CPM or SCPM) to the PM Card under it.
- 41 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
7. Update Network configuration file for PNMS by Update Network Configuration window
function on PNMS. After that it is possible to monitor and control added subnetwork.
Subnet-4
Subnet-5
Subnet-1
Subnet-6
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
- 42 -
ROI-S04188
11.1.2.3 Example 3 : Modify Sub-Network Configuration

1. It is planed to be divided Subnet-2 into two subnetworks to consider future expansion.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
2. Decide each PM Card mode according to new network configuration as shown

Figure11.13.
3. Create configuration file for PM Cards in modified subnetwork and for PNMS by
4. Export configuration file for each PM Card and for PNMS to the director set up in the
5. Download modified configuration file to associated all NEs in new subnetwork and the
Master NE (CPM which new subnetwork is belonging and all SCPMs in the CPM
cluster.) from PNMS. Refer to Figure 11.12. (Downloading from PNMT is also available.
In this case copy the configuration files for each NE from PNMS PC to PNMT is
required.)
- Master PM CARD (CPM) and all SCPM in the CPM cluster : Modify Network
Configuration file to be recognized to modification of sub-network configuration
- All NEs in new subnetwork : Modify network configuration file and system
configuration file
and downloaded from Master PM CARD (CPM or SCPM) to the PM Card under it.
- 43 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
6. Update Network configuration file for PNMS by Update Network Configuration window
function on PNMS. After that it is possible to monitor and control modified sub network.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
- 44 -
ROI-S04188
11.2 PNMS for UNIX

11.2.1 Install PNMS
1. Install PASOLINK hardware.
If the PASOLINK system exists with configuration file, skip Step 2 through Step 6.
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
: PC for Network configuration tool
2. Decide each PM Card mode (for example Figure 11.15).
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
3. Create configuration file for each PM Card and for PNMS by Network Configuration
tool on PC.
4. Export configuration file of each PM Card and for PNMS to the directory set up in the
5. Copy the configuration files of each PM Card form PC (Network Configuration tool) to
PNMT and download them to each PM Card on site using PNMT.
- 45 -
ROI-S04188
6. Upload the configuration file from PC (Network Configuration tool) to PNMS Work
Station by FTP and import it into PNMS.
Upload
Map file
: CPM
: RPM
: Radio Connection
: Cable Connection
7. Connect PNMS to CPM and confirm the connection. After that it is possible to monitor
and control each NE.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
- 46 -
ROI-S04188
11.2.2 Modify Network Configuration

11.2.2.1 Example 1 : Add New HOP in Subnet-4
1. Plan to add new HOP in Subnet-4.
Subnet-4
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
3. Create configuration file for new PM card and PNMS by Network Configuration tool.
5. Upload the configuration file of each PM Card and PNMS from PC (Network
configuration tool) to PNMS Work Station by FTP and import it into PNMS.
6. Copy the configuration files of new PM Card from PC (Network Configuration tool) to
PNMT and download them to new PM Card by PNMT and install new NE (ODU and
IDU) on site.
7. Download the modified configuration files to the existing PM Cards, Master PM Cards
(SCPM of new NEs subnetwork and CPM which such SCPM is belonging.) and a PM
Card, which is connecting new HOP physically from PNMS. Refer to Figure 11.19.
- Master PM Card (Sub-CPM in Subnet-4): Modify Network Configuration file to
recognize the added new HOP (System Configuration file is not necessary to be
modified.
- Existing PM card connecting with new HOP physically : Modify System
Configuration file to recognize connecting with new HOP (Although Network
the RPM under it.)
- Other PM Cards in this CPM cluster: Although Network Configuration file is
and downloaded from Master PM CARD (CPM or SCPM) to each PM Cards under it.
- 47 -
ROI-S04188
Subnet-4
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
8. After that it is possible to monitor and control added NE.

Subnet-4
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
- 48 -
ROI-S04188
11.2.2.2 Example 2 : Add New Subnetwork

1. Plan to add new subnetwork
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
3. Create configuration file for new subnetwork and PNMS by Network Configuration
tool.
5. Upload the configuration file of each PM Card and PNMS from PC (Network
Configuration tool) to PNMS Work Station by FTP and import it into PNMS.
6. Copy the configuration files of new PM Card from PC (Network Configuration tool) to
PNMT and download the configuration file for new PM Card by PNMT and install new
NE (ODU and IDU)I on site.
7. Download the modified configuration file, to the existing PM Card (Master PM Card
(CPM which new subnetwork is belonging and all SCPMs in the CPM cluster.) and a
PM Card which connecting with new HOP physically from PNMS Refer to Figure 11.22.
-Master PM CARD (CPM and all SCPMs in the CPM cluster): Modify Network
Configuration file to recognized the added new subnetwork. (System Configuration
file is not necessary to be modified.)
- Existing PM Card connecting with new subnet physically: Modify System
Configuration file to be recognized connecting new HOP (Although Network
the RPM under it.)
and downloaded from Master PM CARD(CPM or SCPM) to the PM Card under it.)
- 49 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
8. After that it is possible to monitor and control added subnetwork.

Subnet-4
Subnet-5
Subnet-1
Subnet-6
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
- 50 -
ROI-S04188
11.2.2.3 Example 3 : Modify Sub-Network Configuration

1. It is planed to be divided Subnet-2 into two subnetworks to consider future expansion.
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
2. Decide each PM Card mode according to new network configuration as shown

Figure11.26.
3. Create configuration file for PM Cards in modified subnetwork and for PNMS by
4. Export configuration file for each PM Card and PNMS to the directory set up in the
5. Upload the configuration file for each PM Card and PNMS from PC(Network
Configuration tool) to PNMS Work Station by FTP and import it into PNMS.
6. Download modified configuration file to associated all NEs in new subnetwork and the
Master NE (CPM which new subnetwork is belonging and all SCPMs in the CPM
cluster) from PNMS. Refer to Figure 11.25. (Downloading from PNMT is also available.
In this case copy the configuration files for each NE from PNMS PC to PNMT is
required.)
- Master PM CARD (CPM) and all SCPM in the CPM cluster : Modify Network
Configuration file to be recognized to modification of sub-network configuration
- All NEs in new subnetwork : Modify network configuration file and system
configuration file
and downloaded from Master PM CARD(CPM or SCPM) to the PM Card under it.
- 51 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
7. After that it is possible to monitor and control modified sub network.

Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
- 52 -
ROI-S04188
12. RELATED EQUIPMENT FOR PNMS

12.1 HYB Converter
The Hybrid converter is designed to convert serial interface, RS232C, RS422 and RS485 and
to combine/divide communication signal simultaneously all in one unit. It is used for
transmitting SV signal of PNMS through third party equipment.
It is especially useful for PASOLINK multi-cluster network monitored and controlled by PNMS
through third party equipment to convert interface and to combine or divide supervisory
signal.
Followings are the features of HYB Converter:
Easy setting Interface, function and transmission speed.
-> Selection of interface (RS232C/RS422/RS485), function (interface conversion or
Combine/Divide) and transmission speed (9.6kbps/19.2kbps) is executed by front switch
Interface Conversion function
-> For each port, three physical interfaces may be selected: RS232C, RS422 and RS485.
Following conversions are available.
(1) RS232C form/to RS422
(2) RS232C from/to RS485
(3) RS422 from/to RS485
Combine/Divide function
-> Provide 7 communication ports, up to 1:6 (Maximum) combine/divide function is
available
Flexible function Setting
-> In accordance with network configuration, flexible function setting is available at port level.
(1) Interface conversion function only
(2) Combine/Divide function only
(3) Both Conversion and Combine/Divide function
Figure 12.1 shows a example of using HYB converter in PNMS network.
RS232C, 9.6kbps,
Async
Remote Cluster-A
Remote Cluster-B
M
M
PNMS
Central Site
RS232C
19.2/9.6kbps,
Async
M
RS232C, 9.6kbps,
Async
Remote Cluster-C
6
Remote Cluster-D
Provide 1:4 Divide/Combine function
: Hybrid Converter
2 : PASOLINK
M : MODEM / Other Microwave Radio Equipment
M M : Dedicated leased line / Digital Service Channel
Remote Cluster-E
Figure 12.1 Network example using HYB CONV
- 53 -
ROI-S04188
12.2 Management Interface Unit (MIU)

12.2.1 Main Feature
MIU provides CPM function and together with HYB Converter it works to concentrate
Supervisory signal from each PASOLINK (PM Card), which is scattered in different places as
shown Figure 12.2. The detail is also described in section 9.8.
RS-232 or RS485
9.6kbps
ASYNC
9.6 kbps, ASYNC
PASOLINK CLUSTER
RS232 port
(In case of other than RS232C or RS485 port,
additional converter is required
in accordance with the physical interface)
RS-232C/V.11
19.2kbps
ASYNC
or
LAN(10BASE-T)
H
Y
B
MIU
C
O
N
V
R
PNMS
(UNIX or
Windows NT)
RS-485
9.6kbps
ASYNC
PASOLINK CLUSTER
12.2.2 Interface:
(1) For PNMS: PNMS port
Physical interface
RS232C (V.24) or RS422 (V.11) or LAN(10Base-T)
Connector
:
:
DB 15pin (for RS23C/RS422)

RJ-45 (for LAN(10Base-T))
Communication rate
19.2 kbps (PPP, Asynchronous)

(for RS23C/RS422)
(2) For PNMT : PNMT port

Physical interface
: RS232C (V.24)
Connector
: DB 15pin
Communication rate
: 19.2 kbps (PPP, Asynchronous)
(3) For Back to Back : EXP port

Physical interface
: RS485 (V.11)
Connector
: RJ 45
Communication rate
- 54 -
ROI-S04188
12.3 PNMS CABLE

Following table shows cables for PNMS connection. In accordance with customers network
configuration, the selection of suitable cable is required.
Cable Name
Table 13.1 Cable List

How to use
Pin Assignment
LCT
Figure 12.4
Figure 12.5
PNMT
Figure 12.6
Figure 12.7
PNMT+LCT
Figure 12.8
Figure 12.9
PNMS (serial connection)
Figure 12.10,12.11
Figure 12.12
PNMS (LAN connection through Ethernet HUB)*1 Figure 12.13
Figure 12.14
PNMS (LAN connection through Router)*1
Figure 12.15
Figure 12.16
-RS232C
Figure 12.17
Figure 12.18
-RS485
Figure 12.17
Figure 12.19
(1) Cascade connection Cable
Figure 12.20
Figure 12.21
Figure 12.20
Figure 12.22
(3) Terminal connector
Figure 12.20
Figure 12.23
Figure 12.24
Figure 12.25
Figure 12.24
Figure 12.26
Figure 12.24
Figure 12.27
Figure 12.28
Figure 12.29
Figure 12.28
Figure 12.30
Figure 12.28
Figure 12.31
Figure 12.32
Figure 12.33
Figure 12.32
Figure 12.34
Figure 12.32
Figure 12.35
-RS232C
Figure 12.36
Figure 12.37
-RS422
Figure 12.36
Figure 12.38
Figure 12.39
Figure 12.40
Figure 12.39
Figure 12.41
Back to Back (Point to point)
Back to Back (Point to multi-point)
PNMS (Serial connection)

+ Back to Back (Point to multi-point)
PNMS (LAN connection through Ethernet HUB)*1

+Back to Back (Point to multi-point)
PNMS (LAN connection through Router)*1

+Back to Back (Point to multi-point)
HYB CONV-PASOLINK (point to point)
HYB CONV-PASOLINK (point to multi-point)
*1 : This cable is applied only for PASOLINK(V3).
- 55 -
ROI-S04188
12.3.1 LCT Cable
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
LCT
Figure 12.4 LA port - LCT (PC) connection
15pin(M)
9 pin(F)
Paso
LA
Connector
PC(LCT)
RS-232C
1
LCT-TXD
GND
LCT-RXD
TD
LCT-RTS
DTR
LCT-CTS
GND
DSR
6
7
CD
RD
RTS
CTS
RI
10
10
GND
11
PNMT-CTS
11
12
PNMT-RTS
12
13
PNMT-RXD
13
14
GND
14
15
PNMT-TXD
15
PC(LCT)
Figure12.5 Pin assignment for LA port - LCT(PC) connection
12.3.2 PNMT Cable
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
PNMT
Figure 12.6 LA port - PNMT (PC) connection
- 56 -
ROI-S04188
RS-232C
LCT-TXD
GND
LCT-RXD
LCT-RTS
LCT-CTS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
15pin(M)
9 pin(F)
Paso
LA
Connector
PC(PNMT)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
GND
PNMT-CTS
PNMT-RTS
PNMT-RXD
GND
PNMT-TXD
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
CD
RD
TD
DTR
GND
DSR
RTS
CTS
RI
PC(PNMT)
Figure 12.7 Pin assignment for LA port PNMT (PC) connection
12.3.3 PNMT + LCT Cable
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
PNMT
or
LCT
Figure 12.8 LA port - PNMT/LCT (PC) connection
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
RS-232C
LCT-TXD
GND
LCT-RXD
LCT-RTS
LCT-CTS
GND
PNMT-CTS
PNMT-RTS
PNMT-RXD
GND
PNMT-TXD
15pin(M)
9 pin(F)
Paso
LA
Connector
PC(PNMT)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
9 pin(F)
PC(LCT)
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
CD
RD
TD
DTR
GND
DSR
RTS
CTS
RI
PC(LCT)
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
CD
RD
TD
DTR
GND
DSR
RTS
CTS
RI
PC(PNMT)
Figure 12.9 Pin assignment for LA port PNMT/LCT (PC) connection
- 57 -
ROI-S04188
12.3.4 PNMS Cable (Serial connection)
Station B
S tation A
P A S OLIN K
N MS P ort
[R S232C ]
P A S O LINK
LA Port
PN M S (W indows v ersion only)
Figure 12.10 N M S port - PN M S connection
Station B
Station A
CPM
NMS Port
[RS232C]
RPM
LA Port
Router
LAN
PNMS
In case of connection to Router, physical interface
shall be adjusted by suitable adaptor(s)
Figure 12.11 NMS port - Router connection
RS-232C
1 DEBUG-TXD
2
EMS-TXD
3
EMS-RXD
4
5
EMS-RTS
6
EMS-CTS7
GND
8
9 DEBUG-RXD
10
NMS-TXD
11
NMS-RXD
12
13
NMS-RTS
14
NMS-CTS
15
15pin(M)
9 pin(F)
Paso NMS
Connector
PC(PNMS)
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
CD
RD
TD
DTR
GND
DSR
RTS
CTS
RI
PC (PNMS)
or
Router
Figure12.12 Pin assignment for NMS port PNMS/Router connection
- 58 -
ROI-S04188
12.3.5. PNMS Cable (LAN connection through Ethernet HUB)
Station A
Station B
CPM
NMS Port
[LAN]
RPM
LA Port
Ethernert HUB
PNMS
Figure. 12.13 NMS port - Ethernet HUB connection

This cable is only for use of PASOLINK(V3).
CPM
15pin(M)
RJ45(Plug)
Paso NMS
Connector
HUB
LAN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-T TX+
EMS-T TXEMS-T RX+
EMS-T RX-
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
10Base-T
RD+
RDTD
TD-
Figure.12.14 Pin assignment for NMS port Ethernet HUB connection

- 59 -
ROI-S04188
12.3.6. PNMS Cable (LAN connection through Router)
Station A
Station B
CPM
NMS Port
[LAN]
RPM
LA Port
Router
LAN
PNMS
Some routers are equipped with Ethernet HUB port.

In this case Figure 12.13 cable is suitable.
Figure. 12.15 NMS port - Router connection

CPM
15pin(M)
RJ45(Plug)
Paso NMS
Connector
Router
LAN
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-T TX+
EMS-T TXEMS-T RX+
EMS-T RX-
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
10Base-T
TD+
TDRD
RD-
Figure.12.16 Pin assignment for NMS port Router connection

- 60 -
ROI-S04188
12.3.7 Back to Back Cable (Point to Point)
RPM
CPM
RPM
RPM
NMS Port
NMS Port
Figure 12.17 Back-to-Back (point to point) connection
15pin(M)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
RS-232C
DEBUG-TXD
EMS-TXD
EMS-RXD
15pin(M)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-RTS
EMS-CTSGND
DEBUG-RXD
NMS-TXD
NMS-RXD
NMS-RTS
NMS-CTS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
RS-232C
DEBUG-TXD
EMS-TXD
EMS-RXD
EMS-RTS
EMS-CTSGND
DEBUG-RXD
NMS-TXD
NMS-RXD
NMS-RTS
NMS-CTS
Figure12.18 Pin assignment for back to back

(point to point, RS232C) connection
15pin(M)
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure12.19 Pin assignment for back to back

(point to point, RS485) connection
- 61 -
ROI-S04188
12.3.8 Back to Back Cable (Point to Multi-point)
CPM
SCPM
F
NMS Port
[RS485]
RPM
RPM
RPM
SCPM
NMS Port
[RS485]
F
(1)
NMS Port
[RS485]
(2)
(2)
(3)Put on the Termination M at the end of connections
15pin(F)
15pin(M)
Figure 12.20 Back to Back Cable (point to Multi-point) connection
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Figure12.21 Pin assignment for back to back (point to multi-point) connection (1)
Using with Cascade connection cable
0.5 to 15m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
0.3m
15pin(M)
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Figure 12.22 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
- 62 -
ROI-S04188
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
(Termination connector)
12.3.9 PNMS (Serial connection) + Back to Back (Point to Multi-Point) Connection
RPM
RPM
CPM
NMS Port
[RS232C]
RPM
[RS485]
F M
NMS Port [RS485]
(1)
PNMS (Windows NT only)
(2)
(3)
Figure 12.24 Back-to-Back connection with PNMS
9 pin(F)
PC(PNMS)
15pin(M)
15pin(M)
Paso NMS
Connector
Paso NMS
Connector
RS-485
PC
(PNMS)
1
2
3
4
5
6
7
8
9
CD
RD
TD
DTR
GND
DSR
RTS
CTS
RI
1
2
3
4
5
6
7
8
9
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure12.25 Pin assignment for back to back (point to multi-point)

with PNMS connection (1)
using with Cascade connection cable
- 63 -
ROI-S04188
0.5 to 15m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
15pin(M)
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
0.3m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
- 64 -
ROI-S04188
12.3.10. PNMS (LAN connection through Ethernet HUB) + back to back

(point to multi point) connection
RPM
RPM
CPM
RPM
NMS Port
[LAN]
[RS485]
NMS Port [RS485]
Ethernet HUB
(1)
(2)
(3)

PNMS
Figure 12.28 Back-to-Back connection with PNMS through Ethernet HUB

CPM
RJ45(Plug)
Paso NMS
Connector
Paso NMS
Connector
Ethernet HUB
1
2
3
4
5
6
7
8
RPM
15pin(F)
15pin(M)
LAN
10BASE-T
RD+
RDTD
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
TD-
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-T TX+
EMS-T TXEMS-T RX+
EMS-T RX-
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure 12.29 Pin assignment for back to back (point to multi-point)

with PNMS connection through Ethernet HUB (1)
0.5 to 15m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
0.3m
15pin(M)
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
- 65 -
ROI-S04188
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
12.3.11. PNMS (LAN connection through Router) + back to back (point to multi point)
connection
RPM
RPM
CPM
RPM
NMS Port
[LAN]
[RS485]
NMS Port [RS485]
Router
LAN
PNMS
(1)
(2)
(3)

Some routers are equipped with Ethernet HUB port.
In this case Figure 12.28 cable is suitable.
Figure 12.32 Back-to-Back connection with PNMS through Router
CPM
Router
1
2
3
4
5
6
7
8
10BASE-T
TD+
TDRD
RD-
RPM
15pin(M)
15pin(F)
Paso NMS
Connector
Paso NMS
Connector
RJ45(Plug)
LAN
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-T TX+
EMS-T TXEMS-T RX+
EMS-T RX-
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure 12.33 Pin assignment for back to back (point to multi-point)

with PNMS connection through Router (1)
- 66 -
ROI-S04188
0.5 to 15m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
15pin(M)
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
0.3m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
- 67 -
ROI-S04188
12.3.12 HYB CONV PASOLINK Cable (Point to Point)
RPM
NEC Radio Network
RPM
NMS Port
HYB CONV
Figure 12.36 NMS port - HYB Converter (point to point) connection
15pin(M)
15 pin(M)
HYB
Connector
Paso NMS
Connector
HYB CONV
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NMS RXD
NMS -TXD
NMS RTS
NMS -CTS
NMS DTR
GRD
NMS-DCD
NMS-RXD+
NMS-RXDNMS-TXD+
NMS-TXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
RS-232C
1 DEBUG-TXD
2
EMS-TXD
3
EMS-RXD
4
5
EMS-RTS
6
EMS-CTS7
GND
8
9 DEBUG-RXD
10
NMS-TXD
11
NMS-RXD
12
13
NMS-RTS
14
NMS-CTS
15
Figure 12.37 Pin assignment for NMS port - HYB Converter

(point to point, RS232C) connection
15pin(M)
15 pin(M)
HYB
Connector
Paso NMS
Connector
HYB CONV
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NMS RXD
NMS -TXD
NMS RTS
NMS -CTS
NMS DTR
GRD
NMS-DCD
NMS-RXD+
NMS-RXDNMS-TXD+
NMS-TXD-
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure 12.38 Pin assignment for NMS port RS422 connection
- 68 -
ROI-S04188
12.3.13 HYB CONV PASOLINK Cable (Point to Multi-point)
RPM
RPM
RPM
SCPM
NMS Port
[RS485]
NMS Port
[RS485]
(2)
(1)
(2)
HYB CONV
15pin(F)
15pin(M)
Figure 12.39 NMS port - HYB Converter (point to multi-point) connection
HYB
Connector
Paso NMS
Connector
HYB CONV
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NMS- RXD
NMS -TXD
NMS RTS
NMS -CTS
LOOP
GRD
LOOP
NMS-RXD+
NMS-RXDNMS-TXD+
NMS-TXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
Figure12.40 Pin assignment for NMS port HYB Converter

(point to multi-point) connection(1)
Using with Cascade connection cable
0.5 to 15m
15pin(M)
RS-485
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
15pin(M)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0.3m
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Termination is not required

because both TX/RX line are
terminated in HYB CONV.
- 69 -

Pnms Engineering Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pnms Engineering Manual PDF

Uploaded by

Copyright:

Available Formats

ROI-S04188-053E

Digital Communication Network

Digital Service Channel

High Level Data Link Control

Local Area Network

Local Craft Terminal

Management Information Base

Management Interface Unit

Mobile Switching Center

Normal Response Mode

PASOLINK Management Card

PASOLINK Network Management System

PASOLINK Network Management Terminal

Point to Point Protocol

Public Switched Telephone Network

Simple Network Management Protocol

Trivial File Transfer Protocol

User Datagram Protocol

D igital Service C hannel, 9.6kbps

Figure 2-1 Typical PNMS Application

3.2 PNMT - PASOLINK Network Management Terminal

3.3 PMC- PASOLINK Management Card

3.3.2 Collecting Performance Monitor Data

per 15 minutes data :

- Performance Monitor file format

3.3.4 Configuration File

Figure 3.1 PNMS NETWORK IMAGE

1. Basic function of PMC

Master function of SCPMs/RPMs under it

(2) Sub-Master mode (Sub-Central PMC, SCPM): the head of Subnetwork

Master function of RPMs under it

(3) Slave Mode (RPM):

3.3.6 CPM/SCPM/RPM Role Change Function

DSC (9.6kbps) internal connection

RS-232C (LA port)

RS-232C (LA port)

Figure 4-1 Available Physical Interface

: 19.2 kbps (Asynchronous)

4.1.2 LAN Interface

: Ethernet (100/10 BaseT)

: 19.2 kbps (Asynchronous)

: 19.2 kbps (Asynchronous)

4.3.2 NMS Port

for Back to Back connection : RS232C/RS485

: 19.2 kbps (Asynchronous) (for RS232C/RS422)

for Back to Back connection : 9.6kbps (Asynchronous)

5. PNMS COMMUNICATION INTERAFCE

*The converter will

Figure5-1 PNMS Communication Architecture (Serial Interface)

LAN Interface between PNMS (Windows and UNIX) and CPM

Figure 5-2 PNMS Communication Architecture

6. NETWORK SIZING RULE

500/1000 NEs*(1) 1000-10,000NEs*(2)

Maximum number of NEs per

Maximum number of NEs per

Table 6-1: Network Sizing Rule (Theoretical, Number of NE)

(1) Maximum number of NEs(500 or 1,000) is depends on PC Hardware specification.

Maximum number of subnetwork are 32 under a CPM.

Figure 6.1(Single Master)

Back to back connection

Maximum number of subnetwork are 32. In case of dual CPM configuration,

Figure 6.2 CPM (Dual Master)

(7) Maximum number of NE(SCPM and RPM)s in one subnetwork is depends on

500/1000 NEs(1) 1000-10,000NEs(2)