Documente Academic
Documente Profesional
Documente Cultură
021212
P
N
M
S
ASOLINK
ETWORK
Engineering Manual
(PASOLINK Version)
ANAGEMENT
YSTEM
NEC Corporation
Copyright 2002
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.
NEC Corporation
Tokyo, JAPAN
Copyright Notices. Copyright 2002 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..................................................................................................................................9
4.3 PM CARD .............................................................................................................................9
5. PNMS COMMUNICATION INTERAFCE......................................................................... 10
6. NETWORK SIZING RULE ............................................................................................... 11
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 MULTI SUB-BRANCH NETWORK .........................................................................................19
7.4 PNMS IP ADDRESSING SUMMARY ....................................................................................22
7.5 IP ADDRESS REQUIREMENT FOR CUSTOMER......................................................................23
7.6 MAXIMUM NUMBER OF IP ADDRESS...................................................................................24
8. INTEROPERABILITY WITH OTHER NETWORK ......................................................... 25
8.1 CONNECTION AVAILABILITY ...............................................................................................25
8.2 POINT TO POINT CONNECTION ...........................................................................................26
8.3 POINT TO MULTI-POINT CONNECTION ...............................................................................27
9. TYPICAL CONFIGURATION............................................................................................ 28
9.1 MULTI-CLUSTER NETWORK (1) -DEDICATED LEASED LINE (SERIAL INTERFACE)- ............28
9.2 MULTI-CLUSTER NETWORK (2) DEDICATED LEASED LINE (LAN INTERFACE)- ..............29
9.3 MULTI-CLUSTER NETWORK (3) PSTN (SERIAL INTERFACE)- ..........................................29
9.4 MULTI-CLUSTER NETWORK (4) PSTN (LAN INTERFACE)- ..............................................30
9.5 MULTI-CLUSTER NETWORK (5) IP NETWORK (LAN INTERFACE)- ..................................30
9.6 CPM REDUCTION SOLUTION ..............................................................................................31
10. PNMS RELIABILITY ....................................................................................................... 34
10.1 COLD STAND-BY PNMS PRINCIPLE ..................................................................................34
10.2. BACK UP PNMS DATA (UNIX VERSION ONLY) ...............................................................34
10.3 PARALLEL PNMS .............................................................................................................34
11. NETWORK CONFIGURATION WORK ........................................................................... 36
11.1 PNMS FOR WINDOWS.......................................................................................................36
11.2 PNMS FOR UNIX .............................................................................................................44
12. RELATED EQUIPMENT FOR PNMS ............................................................................ 52
12.1 HYB CONVERTER .............................................................................................................52
12.2. MANAGEMENT INTERFACE UNIT (MIU) ..........................................................................53
12.3 PNMS CABLE .................................................................................................................54
-i-
ROI-S04188
-AbbreviationsDCN
DEM
Demodulator
CONV
Converter
CPM
Central PM Card
DSC
HDLC
HYB
Hybrid
IDU
Indoor Unit
INTFC
Interface
I/O
Input/Output
IP
Internet Protocol
LAN
LCT
MIB
MIU
MSC
MUX
Multiplexer
NE
Network Element
NRM
ODU
Outdoor Unit
PMC
PNMS
PNMT
PPP
PS
Power Supply
PSTN
RPM
Remote PM Card
TX
Receive
SCPM
Sub-Central PM Card
SNMP
SV
Supervisory
TFTP
TX
Transmit
SC
Service Channel
SV
Supervisory
SW
Switch
UDP
- 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
95/98/NT/2000 based portable PC and connected to SV (marked as LA) port at 9.6/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.
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.
C oncept of NM
N M S for PASO LIN K
O peration C enter
ID U
PM
C ARD
RS-232C, 19.2kbps
RS-232C,19.2kbps
PNM S
PNM T
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 (supporting up to 500NEs) and the other is PNMS on UNIX OS
(supporting up to 1,000NEs).
ROI-S04188
4 days
7 days
PASOLINK :
7 days
7 days
ROI-S04188
ROI-S04188
(2) Sub-Master mode (Sub-Central PMC, SCPM): The SCPM has two operating functions:
Master and gateway function which performs the same activity as a CPM acting as a
gateway between CPM and RPM and routing the messages from CPM to RPM and
back.
Terminal unit function that acts as a stand-alone 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 stand-alone 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) (32CPMX13RPM=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)
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.
ROI-S04188
CPM1
RPM2
RPM3
RPM4
RPM5
RPM6
RPM7
ROI-S04188
4. PHYSICAL INTERFACE
Summary of physical interface of each equipment is described below.
10 Base-T
For upper management system
RS-232C
9.6/19.2kbps
Async.
(For Windows NT)
RS-232C/V.11
9.6/19.2kbps
Async.
or
LAN(10Base-T)
(NMS port)
RS-485
or
RS232C
9.6kbps
Async.
(NMS port)
PNMS
10Base T
(For Windows NT and Unix)
SCPM
RPM
CPM
RS-485
or
RS232C
9.6kbps
Async.
(NMS port)
RS-232C(COM port)
PNMT
4.1 PNMS
4.1.1 Serial Interface
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 9 PIN
Communication rate
Connector type
: RJ-45
ROI-S04188
4.2 PNMT
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 9 PIN
Communication rate
4.3 PM Card
4.3.1 LA Port
Functional
: RS232C
Electrical
: V.24
Mechanical
: DB 15 PIN
Communication rate
: RS232C/RS422/LAN(10Base-T)
: V.24/V.11(for RS232C/RS422/RS485)
Mechanical
: DB 15 PIN
Communication rate
for PNMS connection
NMS port
LA port
ROI-S04188
RPM
-1
CPM
-2
SCPM
RPM
-3
-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.
IP
Network
RPM
-1
CPM
-2
SCPM
RPM
-3
-4
PNMS-ROUTER
ROUTER-CPM
CPM-SCPM
SCPM-RPM
AP
SNMP/TFTP
SNMP/TFTP
SNMP/TFTP
SNMP/TFTP
Transport
UDP
UDP
UDP
UDP
Network
IP
IP
IP
IP
Data Link
Ethernet
PPP
HDLC/NRM
HDLC/NRM
Physical*
10baseT
RS-232C
19.2kbps Async.
RS-232C/485
9.6kbps Async.
RS-232C/485
9.6kbps Async.
ROI-S04188
PNMS(UNIX)
(10,000NE type)
PNMS (UNIX)
(1,000NE type)
PNMS (NT)
CPM
(1) Maximum number of CPMs for Central type PNMS is recommended to be less than
100 due to PNMS hardware performance limitation even if theoretical value is 192 as
indicated in the Table 6.1
ROI-S04188
PNMS
SCPM1
Subnet1
SCPM N-1
SCPM2
Subnet2
Subnet3
SCPM N
SCPM31
Subnet N
Subnet N+1
Subnet32
: CPM
: SCPM
: RPM
Figure 6.1
(3) In case that the two(2) physical Subnets connection is required to CPM as shown
below, the CPM is regarded as Dual master mode.
PNMS
Dual Master
SCPM2
Subnet2
SCPM3
Subnet1
Subnet 3
SCPM N
Subnet N+1
Subnet4
Radio Section
SCPM N+1 SCPM30
Subnet N+2
Subnet32
: CPM
: SCPM
: RPM
ROI-S04188
(4) The diagram below demonstrate this restriction on the CPM layer.
PNMS
: CPM
: SCPM
: RPM
Figure 6.3
(5) Maximum number of NEs is set to 10,000, assuming there are 10 regional PNMS (10
Regional PNMS x 1000NEs).
(6) SCPM is within the sub network of the master SCPM. For example in Figure 6.1,
SCPM2 is within the SCPM1 sub network. SCPM1 is the master SCPM of SCPM2.
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.
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
Figure 7.2 shows a logical network of Figure7.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.
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
ROI-S04188
Subnet-A : 172.20.100. 0 3
172.20.100. 1 2
(Assigned IP Address)
(Available IP Address)
Subnet-B : 172.20.101. 0 15
: 172.20.101. 1 14
(Assigned IP Address)
(Available IP Address)
ROI-S04188
R
PNMS
IP R
Network
1
Remote Site-B
4
2
3
Remote Site-C
Remote Site-A
6
R
: Router
: CPM
: RPM
Remote Site-D
Figure 7.4 shows a logical network of Figure7.3 and IP address assignment example. To
demonstrate connection of each NE with PNMS, 2 sub-networks, Router and CPM
sub-network and PASOLINK CPM cluster network are defined.
PNMS
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.5
172.20.101.3
172.20.101.6
172.20.101.2
2
RPM
3
4
5
6
7
RPM RPM RPM RPM RPM
8
RPM
ROI-S04188
Subnet-B
IP
Network
Subnet-C
R
1
CPM
18
RPM
13
RPM
2
CPM
3
CPM
12
RPM
32
33
RPM RPM
22
23
RPM RPM
38
RPM
Subnet-F
28
RPM
Subnet-E
ROI-S04188
Subnet-A : 172.20.100. 0 3
172.20.100. 1 2
(Assigned IP Address)
(Available IP Address)
Subnet-B : 172.20.101. 0 15
: 172.20.101. 1 14
(Assigned IP Address)
(Available IP Address)
Table7.2 Exam ple for IP address planing in each Subnet for Figure 7.4
Subnet-A : 172.20.100. 0
172.20.100. 1
3
2
Subnet-B : 172.20.100. 4
: 172.20.100. 5
7
6
(Assigned IP Address)
(Available IP Address)
Subnet-C : 172.20.100. 8
: 172.20.100. 12
11
13
(Assigned IP Address)
(Available IP Address)
Subnet-D : 172.20.101. 0
: 172.20.101. 1
15
14
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
Subnet-E : 172.20.101. 16
: 172.20.101. 17
31
30
(Assigned IP Address)
(Available IP Address)
Subnet-F : 172.20.101. 32
: 172. 20.101.33
47
46
(Assigned IP Address)
(Available IP Address)
Table7.3 Exam ple for IP address planing in each Subnet for Figure 7.5
ROI-S04188
RS232C
19.2/9.6kbps, Async
1
PNMS
(W indow s)
Central Site
4
Rem ote Site-E
7
10
13
12
11
Rem ote Site-D
: CPM
2
3
: SCPM
8
RS485
9.6kbps, Async
14
: RPM
Figure 7.7 shows a logical network of Figure7.6 and IP address assignment example. To
demonstrate connection of each NE with PNMS, 3 sub-networks, PNMS and CPM
sub-network (A) and PASOLINK CPM cluster network (B and C) are defined.
PNM S
Subnet-B
172.20.100.1
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
ROI-S04188
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
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
ROI-S04188
RPM
SCPM
171.18.0. 110
172.18.0. 97
172.18. 0.67
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
R
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
RPM RPM
172.18.0. 49
SCPM
172.18.0.2
Table 7.5 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. 0 15
(Assigned IP Address)
: 172.18.0. 1 14
(Available IP Address)
Subnet-C : 172.18.0. 16 31
(Assigned IP Address)
: 172.18.0. 17 30
(Available IP Address)
Subnet-D : 172.18.0. 32
: 172.18.0. 33
Subnet-E : 172.18.0. 48
: 172.18.0. 49
47
46
63
62
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
Subnet-F : 172.18.0. 64 79
: 172. 18.0. 65 78
(Assigned IP Address)
(Available IP Address)
Subnet-G : 172.18.0.80 95
: 172.18.0.81 94
Subnet-H : 172.18.0.96 111
: 172.18.0.97 110
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
(Assigned IP Address)
(Available IP Address)
ROI-S04188
PNMS (Windows)
Subnet Mask is 255.255.255.252
(11111111.11111111.11111111.11111100)
Number of assigned address is 4.
All 1s and 0s are reserved.
Therefore 2 address are available.
CPM
Subnet Mask is 255.255.255.240
(11111111.11111111.11111111.11110000)
SCPM
RPM
SCPM
SCPM
RPM
RPM
Figure 7.9 IP address Scheme for PNMS (Serial interface between PNMS and CPM)
R
IP
Network
CPM
Subnet Mask is 255.255.255.240
(11111111.11111111.11111111.11110000)
SCPM
RPM
SCPM
SCPM
RPM
RPM
Figure7.10 IP address Scheme for PNMS (LAN interface between PNMS and CPM)
ROI-S04188
(Two class C sub networks are required for maximum 512 IP addresses)
3) Others
ROI-S04188
PNMS (UNIX)
(10,000NE Type)
PNMS (UNIX)
(1,000NE Type)
PNMS (Windows)
(Serial Interface)
CPM
SCPM
Layer
PNMS (Windows)
(LAN interface)
*7)
ROI-S04188
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
Convert RS422
by using HYB CONV
by using HYB CONV
Table 8.1 Connection availability
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.)
ROI-S04188
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
PNMS
(Windows )
RS232C port
(In case of other than RS232C port,
RS-232C
19.2/9.6kbps additional converter is required
ASYNC
in accordance with the existing
physical interface
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
LAN
PNMS
(UNIX or
Windows )
RS-232C
19.2/9.6kbps
ASYNC
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the existing
physical interface
RS-232C
9.6kbps
ASYNC
PASOLINK CLUSTER
PSTN
MD
MD
PNMS
(Windows )
RS-232C
9.6kbps
ASYNC
LAN
PASOLINK CLUSTER
IP
Network
R
PNMS
(UNIX or
Windows)
RS-232C
19.2/9.6kbps
ASYNC
ROI-S04188
Figure 8.3 show the PASOLINK supervisory interface with existing network between
PASOLINKs.
RS-232Cor RS-485
19.2/9.6kbps
ASYNC
RS232Cport
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
RS-232C, RS-485
19.2/9.6kbps
ASYNC
RS-232C
19.2/9.6kbps
ASYNC
LAN
PASOLINK CLUSTER
R
Existing Network (Dedicated line)
19.2/9.6 kbps, ASYNC
PNMS
(UNIX or
Windows)
PASOLINK CLUSTER
RS-232Cor RS-485
19.2/9.6kbps
ASYNC
RS-232C, RS-485
19.2/9.6kbps
ASYNC
RS-232C
19.2/9.6kbps
ASYNC
PASOLINK CLUSTER
PSTN
MD
MD
LAN
PNMS
(UNIX or
Windows)
PASOLINK CLUSTER
RS232C, RS-485
19.2/9.6kbps
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
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 Multi-Cluster Network (1) -Dedicated Leased Line (Serial Interface)Figure 9.1 shows a multi-cluster network, monitored and controlled by PNMS through serial
(RS232C) interface and dedicated line such as DSC. Multiple connections on central
computer are realized by RS232C extension port installed in the PC. 19.2kbps or 9.6kbps
(RS232C interface) are required for dedicated leased line or Digital Service Channel.
RS-232C
19.2/9.6kbps
ASYNC
RS-232C
19.2/9.6kbps
ASYNC
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the existing
physical interface
PNMS
(Windows)
PASOLINK CLUSTER
ROI-S04188
9.2 Multi-Cluster Network (2) Dedicated Leased Line (LAN Interface)Figure 9.2 shows a multi-cluster network, monitored and controlled by PNMS through LAN
interface and dedicated line such as DSC. 19.2kbps or 9.6kbps (RS232C interface) are
required for Router port of dedicated line or Digital Service Channel .
RS-232C
19.2/9.6kbps
ASYNC
RS-232C
19.2/9.6kbps
ASYNC
RS232Cport
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
PNMS
(UNIX or
Windows )
PASOLINK CLUSTER
9.3 Multi-Cluster Network (3) PSTN (Serial Interface)Figure9.3 shows a multi-cluster network, monitored and controlled by PNMS through serial
interface and PSTN. RS232C interface (9.6/19.2kbps) are required for Modem.
RS-232C
9.6kbps
ASYNC
PASOLINK CLUSTER
MD
MD
Extension port (board
inserted into PCI SLOT)
PSTN
RS-232C
9.6kbps
ASYNC
MD
MD
MD
MD
PNMS
(Windows)
PASOLINK CLUSTER
MD
MD
Figure 9.3 Multi-branch network through PSTN with PNMS Serial interface
ROI-S04188
9.4 Multi-Cluster Network (4) PSTN (LAN Interface)Figure 9.4 shows a multi-cluster network, monitored and controlled by PNMS through LAN
interface and PSTN. RS232C interface (9.6/19.2kbps) are required for Modem.
RS-232C
9.6kbps
ASYNC
MD
MD
PSTN
RS-232C
9.6kbps
ASYNC
MD
MD
R
MD
PNMS
(UNIX or
Windows )
MD
PASOLINK CLUSTER
MD
MD
Figure 9.4 Multi-branch network through PSTN with PNMS LAN interface
9.5 Multi-Cluster Network (5) IP Network (LAN Interface)Figure 9.5 shows a multi-cluster network, monitored and controlled by PNMS through LAN
interface and IP network.
RS-232C
19.2/9.6kbps
ASYNC
PASOLINK CLUSTER
LAN
R
R
IP NETWORK
PNMS
(UNIX or
Windows )
PASOLINK CLUSTER
ROI-S04188
Up to 416 NEs
RS-232C
19.2/9.6kbps
ASYNC
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
Up to 416 NEs
Up to 416 NEs
Up to 416 NEs
PNMS
(UNIX or
Windows)
PASOLINK CLUSTER
: CPM
: SCPM
: RPM
RS-232C or RS485
9.6kbps
ASYNC
Existing Network (Dedicated line)
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
H
Y
B
PASOLINK CLUSTER
Up to 416 NEs
CPM
Function
C
O
N
V
PNMS
(UNIX or
Windows)
: CPM
: SCPM
: RPM
ROI-S04188
9.6.1 Solution 1
This solution is applied for the case of PASOLINK HOP locating at PNMS site as shown in
Figure 9.8.
RS-232C or RS485 port
9.6kbps
ASYNC
Existing Network (Dedicated line)
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
Up to 416NEs
C
O
N
V
PASOLINK CLUSTER
PNMS
(UNIX or
Windows)
: CPM
: SCPM
: RPM
9.6.2 Solution 2
This solution is applied for the usage of mediation device (CPM function) locating at PNMS
site. This mediation device is called MIU (Management Interface Unit). (Refer to Section
12.2.)
RS-232Cor RS485
9.6kbps
ASYNC
Existing Network (Dedicated line)
PASOLINK CLUSTER
RS-232C
19.2/9.6kbps
ASYNC
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
H
Y
B
PASOLINK CLUSTER
Up to 416 NEs
MIU
C
O
N
V
PNMS
(UNIX or
Windows)
RS-485
9.6kbps
ASYNC
: CPM
: SCPM
: RPM
ROI-S04188
9.6.3 Solution 3
This solution is applied to support plural MIUs at PNMS site. Plural MIUs requires plural
serial ports of Router. This solution reduces the number of the router port.
A multiplexing function is introduced between MIU and Router at PNMS site to reduce the
number of router serial ports as shown Figure 9.10. Multiplexing function is router, which has
plural serial interface.
PASOLINK CLUSTER
Up to 416 NEs
RS232C port
(In case of other than RS232C port,
additional converter is required
in accordance with the physical interface
PASOLINK CLUSTER
Up to 416 NEs
PASOLINK CLUSTER
RS-485
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
RS-232C
19.2/9.6kbps
ASYNC
MUX
Function
R
PNMS
Up to 416 NEs
: SCPM
: RPM
Figure 9.10 Network Architecture
ROI-S04188
ROI-S04188
PNMS-1
PNMS-2
LAN
R
Alarm or Event trap
R : Router
ROI-S04188
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
ROI-S04188
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.
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
ROI-S04188
New Hop
Subnet-5
Subnet-1
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.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.)
ROI-S04188
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
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
ROI-S04188
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
Network Configuration tool.
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.
(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 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
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 Card 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 the PM Card under it.
(System Configuration file is not necessary to be modified.)
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
ROI-S04188
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
Figure11.11Network Example
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: Radio Connection
: Cable Connection
Figure11.12Network Example
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
Figure11.13Network Example
ROI-S04188
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
: PC for Network configuration tool
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
: PC for Network configuration tool
3. Create configuration file for each PM Card and for PNMS by Network Configuration
tool on PC.
ROI-S04188
4. Export configuration file of each PM Card and for PNMS to the directory set up in the
Network Configuration tool.
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.
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
: PC for Network configuration tool
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
: PC for Network configuration tool
Figure11.17Network Example
ROI-S04188
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
2. Decide the new PM Card mode (CPM, SCPM or RPM) (for example Figure 11.20).
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 the
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.
(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.)
ROI-S04188
and downloaded from Master PM CARD (CPM or SCPM) to each PM Cards under
it. (System Configuration file is not necessary to be modified.)
Subnet-4
New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
ROI-S04188
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
2. Decide the new PM Card mode (CPM, SCPM or RPM) (for example Figure 11.23).
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
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.
(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 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
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 Card 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 the PM Card under it.)
(System Configuration file is not necessary to be modified.)
PNMS Engineering manual
- 48 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
Subnet-5
Subnet-1
Subnet-6
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
ROI-S04188
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
Figure11.24Network Example
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
Figure11.25Network Example
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
: Router
: PC for Network configuration tool
Figure11.26Network Example
ROI-S04188
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
: Hybrid Converter
2 : PASOLINK
M : MODEM / Other Microwave Radio Equipment
M M : Dedicated leased line / Digital Service Channel
Remote Cluster-E
ROI-S04188
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.6.
RS-232 or RS485
9.6kbps
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
19.2kbps
ASYNC
H
Y
B
MIU
C
O
N
V
PNMS
(UNIX or
Windows NT)
RS-485
9.6kbps
ASYNC
PASOLINK CLUSTER
12.2.2 Interface:
(1) For PNMS: PNMS port
Physical interface
Connector
: DB 15pin
Communication rate
: RS232C (V.24)
Connector
: DB 15pin
Communication rate
: RS485 (V.11)
Connector
: RJ 45
Communication rate
ROI-S04188
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
Figure 12.13
Figure 12.14
-RS485
Figure 12.13
Figure 12.15
Figure 12.16
Figure 12.17
Figure 12.16
Figure 12.18
Figure 12.16
Figure 12.19
Figure 12.20
Figure 12.21
Figure 12.20
Figure 12.22
Figure 12.20
Figure 12.23
-RS232C
Figure 12.24
Figure 12.25
-RS422
Figure 12.24
Figure 12.26
Figure 12.27
Figure 12.28
Figure 12.27
Figure 12.29
ROI-S04188
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
LCT
15pin(M)
9 pin(F)
Paso
LA
Connector
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-C TS
PNMT-R TS
PNMT-RXD
GND
PNMT-TXD
PC(LCT)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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)
ROI-S04188
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
PNMT
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
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)
ROI-S04188
Station B
Station A
PASOLINK
NMS Port
PASOLINK
LA Port
PNMT
or
LCT
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)
ROI-S04188
Station B
Station A
P ASO LIN K
NM S Port
[RS232C]
P A SO LINK
LA Port
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)
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
ROI-S04188
RPM
CPM
RPM
RPM
NMS Port
NMS Port
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
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-
ROI-S04188
CPM
SCPM
F
NMS Port
[RS485]
(1)
RPM
RPM
RPM
SCPM
NMS Port
[RS485]
NMS Port
[RS485]
(2)
(2)
15pin(F)
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-
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Figure12.17 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.18 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
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-
Figure13.19 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
RPM
RPM
RPM
CPM
NMS Port
[RS232C]
[RS485]
F M
(1)
PNMS (Windows NT only)
(2)
(3)
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-
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
Figure12.22 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
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
Figure12.23 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
RPM
RPM
NMS Port
HYB CONV
ROI-S04188
15pin(M)
15 pin(M)
Paso NMS
Connector
HYB
Connector
HYB CONV
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
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
DEBUG-TXD
EMS-TXD
EMS-RXD
EMS-RTS
EMS-CTSGND
DEBUG-RXD
NMS-TXD
NMS-RXD
NMS-RTS
NMS-CTS
15pin(M)
15 pin(M)
Paso NMS
Connector
HYB
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
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
EMS-TXD+
EMS-TXDEMS-TXDR
EMS-RXD+
EMS-RXDGND
NMS-TXD+
NMS-TXDNMS-TXDR
NMS-RXD+
NMS-RXD-
(1)
RPM
RPM
RPM
SCPM
NMS Port
[RS485]
NMS Port
[RS485]
(2)
(2)
HYB CONV
15pin(F)
15pin(M)
ROI-S04188
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-
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-
15pin(M)
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
0.3m
15pin(F)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Figure12.29 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)