Pnms Engineering Manual
Pnms Engineering Manual
Pnms Engineering Manual
030808
P ASOLINK
M ANAGEMENT
S 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.
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
-i-
ROI-S04188
-Abbreviations-
DCN 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).
NEC’s 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
-2-
ROI-S04188
3. SYSTEM COMPONENTS
-3-
ROI-S04188
-4-
ROI-S04188
PNMS-CPM subnetwork
PNMS network
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
-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.
-7-
ROI-S04188
4. PHYSICAL INTERFACE
Summary of physical interface of each equipment is described below.
CPM SCPM
RS-232C RS-232C/V.11
19.2kbps Async. 19.2kbps
RS-485 RPM RS-485
(For Windows NT) Async. or or
or RS232C RS232C
LAN(10Base-T) 9.6kbps 9.6kbps
(NMS port) Async. Async.
PNMS (NMS port) (NMS port)
PNMT
4.1 PNMS
4.2 PNMT
Functional : RS232C
Electrical : V.24
Mechanical : DB 9 PIN
Communication rate : 19.2 kbps (Asynchronous)
-8-
ROI-S04188
4.3 PM Card
4.3.1 LA Port
Functional : RS232C
Electrical : V.24
Mechanical : DB 15 PIN
Communication rate : 19.2 kbps (Asynchronous)
-9-
ROI-S04188
NMS port(LAN)
LA port
NMS port (Serial)
(PASOLINK (V4))
- 10 -
ROI-S04188
RPM
CPM -1
RPM
-2
RPM
SCPM
-3
RPM
-4
Network IP IP IP
RPM
CPM -1
RPM
-2
RPM
SCPM
-3
LAN
RPM
-4
Network IP IP IP
- 11 -
ROI-S04188
PNMS PNMS
for Windows for UNIX
Maximum number of NE per
500/1000 NEs*(1) 1000-10,000NEs*(2)
PNMS
Maximum number of CPM per
32 ea*(3) 320 ea*(4)
PNMS
Maximum number of NEs per
CPM cluster 416NEs*(5)
- 12 -
ROI-S04188
PNMS
SCPM1 SCPM2
SCPM2 SCPM3
: CPM
: SCPM
: RPM
- 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.
RS232C
19.2/9.6kbps, Async
PNMS Remote Site-B
4 5
PNMS
(Windows) 2 3
Remote Site-C
Remote Site-A
6 7
Remote Site-D
1 : CPM
2 : RPM
8
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.
PNMS 192.168.1.254
192.168.1.253
172.20.101.1 172.20.101.4
172.20.101.3 172.20.101.5 172.20.101.7
- 14 -
ROI-S04188
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.
- 15 -
ROI-S04188
LAN(10base-T)
PNMS Remote Site-B
4 5
PNMS 2 3
Remote Site-C
Remote Site-A
6 7
Remote Site-D
1 : CPM
2 : RPM
8
Figure 7.2.2 shows a logical network of Figure7.2.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.
- 16 -
ROI-S04188
- 17 -
ROI-S04188
Remote Site-C
1 13 14
Remote Site-B
11 12
2 23 24
Remote Site-E
21 22
Remote Site-I
3 Remote Site-H 33 34
31 32
1 2 3
CPM CPM CPM
18 13 12 32 33 38
RPM RPM RPM RPM RPM RPM
22 23 28
RPM RPM RPM Subnet-C
- 18 -
ROI-S04188
RS232C or V.11
19.2/9.6kbps, Async
IP or
network 1 LAN(10 base-T)
Remote Site-B
PNMS
4 5
2 3
Remote Site-C
Remote Site-A
6 7
2 : RPM 8
Figure 7.3.1 Typical Network Example (Simple trunk line [Physical Model])
Figure 7.3.2 shows a logical network of Figure7.3.1 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.101.1 172.20.101.4
172.20.101.3 172.20.101.5 172.20.101.7
172.20.101.2 172.20.101.6
1
CPM
Central Site 2 3 4 5 6 7 8
RPM RPM RPM RPM RPM RPM RPM
- 19 -
ROI-S04188
RS232C
19.2/9.6kbps, Async
Remote Site-B
1
PNMS 5 6
(Windows)
Central Site
3 4
Remote Site-E Remote Site-C
Remote Site-A 7
Remote Site-G 10 9 2
8
13 12 11
RS485
Remote Site-D
9.6kbps, Async
Remote Site-F
1 : CPM
14
2 : SCPM
3 : RPM
Figure 7.4.2 shows a logical model of Figure7.4.1 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.
Subnet-C
Figure 7.4.2 Typical Network Example (Multi sub-branches network[Logical Model])
- 20 -
ROI-S04188
- 21 -
ROI-S04188
172.18. 0.66
RPM SCPM F
Router and CPM
171.18.0. 110 172.18.0.65 subnetwork
172.18. 0.67
H 172.18.0. 97
172.18.0.78 172.18.0.34
D C A
RPM RPM SCPM 172.18.2.1
172.18.2.2
172.18. 0. 36
G 172.18.0.83 172.18.0.81 172.18.0.17
Table 7.4.2 shows assigned IP addresses and available IP addresses of each sub network of
this multi sub-branch network.
- 22 -
ROI-S04188
Serial
Interface PNMS (Windows)
CPM
Figure 7.5.1 IP address Scheme for PNMS (Serial interface between PNMS and CPM)
LAN
CPM
Figure7.5.2 IP address Scheme for PNMS (LAN interface between PNMS and CPM)
- 23 -
ROI-S04188
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.
RS-232C
19.2kbps
PASOLINK CLUSTER ASYNC
Existing Network (Dedicated line)
RS-232C/V.11
19.2kbps
ASYNC
RS-232C
19.2kbps LAN
PASOLINK CLUSTER ASYNC
Existing Network (Dedicated line)
R
DSC (19.2kbps, ASYNC)
PNMS
(UNIX or
Windows )
RS-232C/V.11
19.2kbps
ASYNC
- 25 -
ROI-S04188
Figure 9.2 show the PASOLINK supervisory interface with existing network (PSTN or IP
network) between PNMS and CPM.
RS-232C
RS-232C/V.11
9.6kbps
9.6kbps Continuous connection is needed ASYNC
ASYNC
PASOLINK CLUSTER
PSTN
MD MD
PNMS
(Windows )
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER
IP
R R
Network
PNMS
LAN (UNIX or
Windows)
LAN
PASOLINK CLUSTER
R IP R
Network
R :Router MD :Modem
: CPM
Figure 9.2 Interoperability with other network : RPM
Figure 9.3 show the PASOLINK supervisory interface with existing network between
PASOLINKs.
PASOLINK CLUSTER
R
Existing Network (Dedicated line)
19.2/9.6 kbps, ASYNC PNMS
(UNIX or
PASOLINK CLUSTER Windows)
PASOLINK CLUSTER
PSTN
MD MD R
PNMS
(UNIX or
PASOLINK CLUSTER Windows)
- 26 -
ROI-S04188
RS-232C
RS232C, RS-485 RS-232C, RS-485 19.2kbps
9.6kbps 9.6kbps ASYNC
LAN
ASYNC ASYNC
PASOLINK CLUSTER
H H R
Existing Network Y
Y
(Dedicated line) B
B PNMS
19.2/9.6 kbps, Async
(UNIX or
C C Windows)
O O
N N
V V
R :Router
: CPM
: RPM
: Existing Network (Dedicated line)
RS-232C/V.11 RS-232C
19.2kbps 19.2kbps
ASYNC ASYNC
Existing Network (Dedicated line)
PASOLINK CLUSTER 19.2kbps, ASYNC
Multi-serial board
(inserted into PCI SLOT)
PNMS
・・・・
・・・
(Windows)
PASOLINK CLUSTER
- 27 -
ROI-S04188
RS-232C/V.11
19.2kbps
ASYNC RS-232C
Existing Network (Dedicated line) 19.2kbps
PASOLINK CLUSTER 19.2kbps, ASYNC ASYNC
R
PNMS
・・・・
(UNIX or
・・・・
Windows )
PASOLINK CLUSTER
RS-232C
Continuous connection is needed 19.2kbps
ASYNC
PASOLINK CLUSTER
MD MD
Multi-serial board
(inserted into PCI SLOT)
RS-232C
19.2kbps
PSTN
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
RS-232C
Continuous connection is needed 19.2kbps
ASYNC
PASOLINK CLUSTER
MD MD
RS-232C
19.2kbps
PSTN
ASYNC
MD MD
R
MD MD PNMS
(UNIX or
・・・・
・・・・
Windows )
PASOLINK CLUSTER
MD MD
Figure 9.8 Multi-branch network through PSTN with PNMS LAN interface
RS-232C/V.11
19.2kbps
ASYNC
PASOLINK CLUSTER
LAN
R
R
R IP NETWORK
PNMS
・・・・
(UNIX or
Windows )
PASOLINK CLUSTER
- 29 -
ROI-S04188
LAN
PASOLINK CLUSTER
LAN
R
R
R IP NETWORK
PNMS
・・・・ (UNIX or
Windows )
PASOLINK CLUSTER
RS-232C/V.11
19.2kbps
Up to 416 NEs ASYNC
Existing Network (Dedicated line)
RS-232C
19.2kbps
ASYNC
Up to 416 NEs
Up to 416 NEs R
PNMS
(UNIX or
・・・・
・・・・
Windows)
Up to 416 NEs
PASOLINK CLUSTER
: CPM
: SCPM
: RPM
- 30 -
ROI-S04188
PASOLINK CLUSTERs
RS-232C R
19.2kbps
ASYNC
PASOLINK CLUSTERs
Customer
IP Network
R
R
RS-232C PNMS
19.2kbps
PASOLINK CLUSTERs ASYNC
R
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
Existing Network (Dedicated line)
PASOLINK CLUSTER 9.6 kbps, ASYNC SV signal
Concentrated Function
RS-232C
19.2kbps
ASYNC
H
Y
B CPM
Function R
C
O PNMS
N
・・・・
(UNIX or
・・・・
V Windows)
Up to 416 NEs
PASOLINK CLUSTER
: 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
Existing radio line 19.2/9.6kbps
PASOLINK CLUSTER ASYNC
RS-232C/V.11
19.2kbps
ASYNC
RS-232C or RS485 port 5 port or
9.6kbps, ASYNC LAN(10BASE-T)
H
Y
B
MIU R
C
O PNMS
N
・・・・
・・・・
V RS-485
9.6kbps
H ASYNC
Up to 416 NEs Y
B
PASOLINK CLUSTER C
O
N
V : 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
H
Y
RS-232C or RS485 port
B
19.2/9.6kbps C
MIU
R
ASYNC O
N
PASOLINK CLUSTER
V Customer
H
IP Network
Y
B
C
MIU R
O R
N
V PNMS
RS-232C or RS485 port
H
19.2/9.6kbps Y
ASYNC B
PASOLINK CLUSTER
C
MIU R
O
N
V
- 32 -
ROI-S04188
- 33 -
ROI-S04188
PNMS-1
Alarm or Event Trap
LAN
Customer IP network
LAN
PNMS-2 : ROUTER
Regional Network Operation Center-2
: PASOLINK
Figure 10.1Parallel PNMS
- 34 -
ROI-S04188
- 35 -
ROI-S04188
Customer IP Network
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
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
Figure11.1 Network Example
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
Figure11.2 Network Example
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
Figure11.3 Network Example
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
R : Router
: Radio Connection
: Cable Connection
Figure11.4 Network Example
- 38 -
ROI-S04188
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : 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 NE’s 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-5
Subnet-1
Subnet-2
: CPM
Subnet-3
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure 11.6 Network 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
: CPM
Subnet-3
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure 11.7 Network Example
- 40 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure 11.8 Network Example
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.)
- 41 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure 11.9Network Example
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
R : Router
: Radio Connection
: Cable Connection
Figure 11.10 Network Example
- 42 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure11.11 Network Example
- 43 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
Figure11.12 Network 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
R : Router
: Radio Connection
: Cable Connection
Figure11.13 Network Example
- 44 -
ROI-S04188
PNMS Site
: CPM
: RPM
: Radio Connection
: Cable Connection
PNMS Site
: CPM
: SCPM
: RPM
: Radio Connection
: Cable Connection
: PC for Network configuration tool
Figure11.15 Network Example
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
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.
- 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
: PC for Network configuration tool
Figure11.16 Network Example
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
: CPM Subnet-3
: SCPM
: RPM
R : Router
: Radio Connection
: Cable Connection
: PC for Network configuration tool
Figure11.17 Network Example
- 46 -
ROI-S04188
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
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 NE’s 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.)
- 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.)
- 47 -
ROI-S04188
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
Subnet-4
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
- 48 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
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.)
- 49 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
Subnet-4
Subnet-5
Subnet-1
Subnet-6
Subnet-2
Subnet-3
: CPM
: SCPM
: RPM
R : Router
- 50 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
- 51 -
ROI-S04188
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
Subnet-4
Subnet-5
Subnet-1
Subnet-2
R
New Subnet
Subnet-3
: CPM
: SCPM
: RPM
R : Router
- 52 -
ROI-S04188
RS232C, 9.6kbps,
Remote Cluster-A Async Remote Cluster-B
M
M M 1 2 M 3 4
PNMS M
M
Central Site Remote Cluster-C
RS232C
19.2/9.6kbps, M
RS232C, 9.6kbps, M 5 6
Async
Async
Remote Cluster-D
Provide 1:4 Divide/Combine function
M 5 6
: Hybrid Converter
Remote Cluster-E
2 : PASOLINK
M : MODEM / Other Microwave Radio Equipment
M M : Dedicated leased line / Digital Service Channel M 7 8
Figure 12.1 Network example using HYB CONV
- 53 -
ROI-S04188
RS-232 or RS485
9.6kbps
ASYNC
Existing Network (Dedicated line)
PASOLINK CLUSTER 9.6 kbps, ASYNC
RS-232C/V.11
19.2kbps
ASYNC
RS232 port or
(In case of other than RS232C or RS485 port, LAN(10BASE-T)
additional converter is required
in accordance with the physical interface)
H
Y
B
MIU R
C
O PNMS
N
・・・・
(UNIX or
・・・・
V 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 : 9.6 kbps (Asynchronous)
- 54 -
ROI-S04188
- 55 -
ROI-S04188
Station A Station B
PASOLINK PASOLINK
LCT
15pin(M) 9 pin(F)
Paso PC(LCT)
LA
Connector
RS-232C
1 LCT-TXD 1 1 1 CD
2 GND 2 2 2 RD
3 LCT-RXD 3 3 3 TD
4 LCT-RTS 4 4 4 DTR
5 LCT-CTS 5 5 5 GND PC(LCT)
6 6 6 6 DSR
7 7 7 7 RTS
8 GND 8 8 8 CTS
9 9 9 9 RI
10 10
11 PNMT-CTS 11
12 PNMT-RTS 12
13 PNMT-RXD 13
14 GND 14
15 PNMT-TXD 15
Station A Station B
PASOLINK PASOLINK
PNMT
- 56 -
ROI-S04188
15pin(M) 9 pin(F)
Paso PC(PNMT)
LA
Connector
RS-232C
1 LCT-TXD 1
2 GND 2
3 LCT-RXD 3
4 LCT-RTS 4
5 LCT-CTS 5
6 6
7 7
8 GND 8
9 9
10 10
11 PNMT-CTS 11 1 1 CD
12 PNMT-RTS 12 2 2 RD
13 PNMT-RXD 13 3 3 TD
14 GND 14 4 4 DTR
15 PNMT-TXD 15 5 5 GND PC(PNMT)
6 6 DSR
7 7 RTS
8 8 CTS
9 9 RI
Station A Station B
PASOLINK PASOLINK
PNMT or LCT
RS-232C
1 LCT-TXD 1 1 1 CD
2 GND 2 2 2 RD
3 LCT-RXD 3 3 3 TD
4 LCT-RTS 4 4 4 DTR
5 LCT-CTS 5 5 5 GND PC(LCT)
6 6 6 6 DSR
7 7 7 7 RTS
8 GND 8 8 8 CTS
9 9 9 9 RI
10 10
11 PNMT-CTS 11 1 1 CD
12 PNMT-RTS 12 2 2 RD
13 PNMT-RXD 13 3 3 TD
14 GND 14 4 4 DTR
15 PNMT-TXD 15 5 5 GND PC(PNMT)
6 6 DSR
7 7 RTS
8 8 CTS
9 9 RI
- 57 -
ROI-S04188
S tation A Station B
P A S OLIN K P A S O LINK
N MS P ort LA Port
[R S232C ]
Station A Station B
CPM RPM
Router
LAN
PNMS
15pin(M) 9 pin(F)
1 1 CD
2 2 RD
RS-232C
3 3 TD
1 DEBUG-TXD 1
4 4 DTR PC (PNMS)
2 EMS-TXD 2
5 5 GND or
3 EMS-RXD 3
6 6 DSR Router
4 4
7 7 RTS
5 EMS-RTS 5
8 8 CTS
6 EMS-CTS- 6
9 9 RI
7 GND 7
8 8
9 DEBUG-RXD 9
10 NMS-TXD 10
11 NMS-RXD 11
12 12
13 NMS-RTS 13
14 NMS-CTS 14
15 15
- 58 -
ROI-S04188
Station A Station B
CPM RPM
Ethernert HUB
PNMS
CPM
15pin(M) RJ45(Plug)
LAN 10Base-T
1 1 1 1 RD+
2 EMS-T TX+ 2 2 2 RD-
3 EMS-T TX- 3 3 3 TD+
4 4 4 4
5 EMS-T RX+ 5 5 5
6 EMS-T RX- 6 6 6 TD-
7 7 7 7
8 8 8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
- 59 -
ROI-S04188
Station A Station B
CPM RPM
Router
LAN
PNMS Some routers are equipped with Ethernet HUB port.
In this case Figure 12.13 cable is suitable.
CPM
15pin(M) RJ45(Plug)
LAN 10Base-T
1 1 1 1 TD+
2 EMS-T TX+ 2 2 2 TD-
3 EMS-T TX- 3 3 3 RD+
4 4 4 4
5 EMS-T RX+ 5 5 5
6 EMS-T RX- 6 6 6 RD-
7 7 7 7
8 8 8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
- 60 -
ROI-S04188
CPM RPM
RPM RPM
15pin(M) 15pin(M)
RS-232C RS-232C
1 DEBUG-TXD 1 1 1 DEBUG-TXD
2 EMS-TXD 2 2 2 EMS-TXD
3 EMS-RXD 3 3 3 EMS-RXD
4 4 4 4
5 EMS-RTS 5 5 5 EMS-RTS
6 EMS-CTS- 6 6 6 EMS-CTS-
7 GND 7 7 7 GND
8 8 8 8
9 DEBUG-RXD 9 9 9 DEBUG-RXD
10 NMS-TXD 10 10 10 NMS-TXD
11 NMS-RXD 11 11 11 NMS-RXD
12 12 12 12
13 NMS-RTS 13 13 13 NMS-RTS
14 NMS-CTS 14 14 14 NMS-CTS
15 15 15 15
15pin(M) 15pin(M)
RS-485 RS-485
1 1 1 1
2 EMS-TXD+ 2 2 2 EMS-TXD+
3 EMS-TXD- 3 3 3 EMS-TXD-
4 EMS-TXDR 4 4 4 EMS-TXDR
5 EMS-RXD+ 5 5 5 EMS-RXD+
6 EMS-RXD- 6 6 6 EMS-RXD-
7 GND 7 7 7 GND
8 8 8 8
9 9 9 9
10 NMS-TXD+ 10 10 10 NMS-TXD+
11 NMS-TXD- 11 11 11 NMS-TXD-
12 NMS-TXDR 12 12 12 NMS-TXDR
13 NMS-RXD+ 13 13 13 NMS-RXD+
14 NMS-RXD- 14 14 14 NMS-RXD-
15 15 15 15
- 61 -
ROI-S04188
F M
NMS Port NMS Port NMS Port
[RS485] [RS485] [RS485]
F M F M
15pin(F)
RS-485
1 1 1
2 EMS-TXD+ 2 2
3 EMS-TXD- 3 3
4 EMS-TXDR 4 4
5 EMS-RXD+ 5 5
6 EMS-RXD- 6 6
7 GND 7 7
8 8 8
9 9 9
10 NMS-TXD+ 10 10
11 NMS-TXD- 11 11
12 NMS-TXDR 12 12
13 NMS-RXD+ 13 13
14 NMS-RXD- 14 14
15 15 15
Figure12.21 Pin assignment for back to back (point to multi-point) connection (1)
Using with Cascade connection cable
RS-485
1 1 1
1
2 2 2
2 EMS-TXD+
3 3 3
3 EMS-TXD-
4 4 4
4 EMS-TXDR
5 5 5
5 EMS-RXD+
6 6 6
6 EMS-RXD-
7 7 7
7 GND
8 8 8
8
9 9 9
9
10 10 10
10 NMS-TXD+
11 11 11
11 NMS-TXD-
12 12 12
12 NMS-TXDR
13 13 13
13 NMS-RXD+
14 14 14
14 NMS-RXD-
15 15 15
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 1
2 EMS-TXD+ 2
3 EMS-TXD- 3
4 EMS-TXDR 4
5 EMS-RXD+ 5
6 EMS-RXD- 6
7 GND 7
8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
Figure12.23 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
RPM RPM
CPM RPM
NMS Port F M
[RS485] NMS Port [RS485]
[RS232C]
F
F M
(1)
PNMS (Windows NT only) (2)
(3)
(3)Put on the Termination M at the end of connections
15pin(M) 15pin(M)
9 pin(F)
Paso NMS Paso NMS
PC(PNMS) Connector Connector
RS-485
1 CD 1 1 1 1
2 RD 2 2 2 2 EMS-TXD+
3 TD 3 3 3 3 EMS-TXD-
4 DTR 4 4 4 4 EMS-TXDR
5 GND 5 5 5 5 EMS-RXD+
PC
6 DSR 6 6 6 6 EMS-RXD-
(PNMS) 7 RTS 7 7 7 7 GND
8 CTS 8 8 8 8
9 RI 9 9 9 9
10 10 10 NMS-TXD+
11 11 11 NMS-TXD-
12 12 12 NMS-TXDR
13 13 13 NMS-RXD+
14 14 14 NMS-RXD-
15 15 15
- 63 -
ROI-S04188
RS-485
1 1 1
1
2 2 2
2 EMS-TXD+
3 3 3
3 EMS-TXD-
4 4 4
4 EMS-TXDR
5 5 5
5 EMS-RXD+
6 6 6
6 EMS-RXD-
7 7 7
7 GND
8 8 8
8
9 9 9
9
10 10 10
10 NMS-TXD+
11 11 11
11 NMS-TXD-
12 12 12
12 NMS-TXDR
13 13 13
13 NMS-RXD+
14 14 14
14 NMS-RXD-
15 15 15
15
Figure12.26 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
15pin(M)
RS-485
1 1
2 EMS-TXD+ 2
3 EMS-TXD- 3
4 EMS-TXDR 4
5 EMS-RXD+ 5
6 EMS-RXD- 6
7 GND 7
8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
Figure12.27 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
- 64 -
ROI-S04188
RPM RPM
CPM RPM
F M
Ethernet HUB
(1) (2)
(3)
(3)Put on the Termination M at the end of connections
CPM RPM
15pin(F)
RJ45(Plug) 15pin(M)
Paso NMS
Ethernet HUB Paso NMS
Connector
Connector
LAN RS-485
10BASE-T
1 1
1 RD+ 1
2 EMS-T TX+ 2 EMS-TXD+
2 RD- 2
3 EMS-T TX- 3 EMS-TXD-
3 TD+ 3
4 4 EMS-TXDR
4 4
5 EMS-T RX+ 5 EMS-RXD+
5 5
6 EMS-T RX- 6 EMS-RXD-
6 TD- 6
7 7 GND
7 7
8 8
8 8
9 9
10 NMS-TXD+ 10 NMS-TXD+
11 NMS-TXD- 11 NMS-TXD-
12 NMS-TXDR 12 NMS-TXDR
13 NMS-RXD+ 13 NMS-RXD+
14 NMS-RXD- 14 NMS-RXD-
15 15
RS-485
1 1 1
1
2 2 2
2 EMS-TXD+
3 3 3
3 EMS-TXD-
4 4 4
4 EMS-TXDR
5 5 5
5 EMS-RXD+
6 6 6
6 EMS-RXD-
7 7 7
7 GND
8 8 8
8
9 9 9
9
10 10 10
10 NMS-TXD+
11 11 11
11 NMS-TXD-
12 12 12
12 NMS-TXDR
13 13 13
13 NMS-RXD+
14 14 14
14 NMS-RXD-
15 15 15
15
Figure12.30 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
- 65 -
ROI-S04188
15pin(M)
RS-485
1 1
2 EMS-TXD+ 2
3 EMS-TXD- 3
4 EMS-TXDR 4
5 EMS-RXD+ 5
6 EMS-RXD- 6
7 GND 7
8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
Figure12.31 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
12.3.11. PNMS (LAN connection through Router) + back to back (point to multi point)
connection
RPM RPM
CPM RPM
F M
Router
(1)
(2) (3)
(3)Put on the Termination M at the end of connections
Some routers are equipped with Ethernet HUB port.
LAN
In this case Figure 12.28 cable is suitable.
PNMS
This cable is only for use of PASOLINK(V3).
Figure 12.32 Back-to-Back connection with PNMS through Router
CPM RPM
Paso NMS
Router Paso NMS
Connector Connector
LAN RS-485
10BASE-T
1 1 1
1 TD+ 1
2 EMS-T TX+ 2 2 EMS-TXD+
2 TD- 2
3 EMS-T TX- 3 3 EMS-TXD-
3 RD+ 3
4 4 4 EMS-TXDR
4 4
5 EMS-T RX+ 5 5 EMS-RXD+
5 5
6 EMS-T RX- 6 6 EMS-RXD-
6 RD- 6
7 7 7 GND
7 7
8 8 8
8 8
9 9 9
10 NMS-TXD+ 10 10 NMS-TXD+
11 NMS-TXD- 11 11 NMS-TXD-
12 NMS-TXDR 12 12 NMS-TXDR
13 NMS-RXD+ 13 13 NMS-RXD+
14 NMS-RXD- 14 14 NMS-RXD-
15 15 15
- 66 -
ROI-S04188
RS-485
1 1 1
1
2 2 2
2 EMS-TXD+
3 3 3
3 EMS-TXD-
4 4 4
4 EMS-TXDR
5 5 5
5 EMS-RXD+
6 6 6
6 EMS-RXD-
7 7 7
7 GND
8 8 8
8
9 9 9
9
10 10 10
10 NMS-TXD+
11 11 11
11 NMS-TXD-
12 12 12
12 NMS-TXDR
13 13 13
13 NMS-RXD+
14 14 14
14 NMS-RXD-
15 15 15
15
Figure12.34 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
15pin(M)
RS-485
1 1
2 EMS-TXD+ 2
3 EMS-TXD- 3
4 EMS-TXDR 4
5 EMS-RXD+ 5
6 EMS-RXD- 6
7 GND 7
8 8
9 9
10 NMS-TXD+ 10
11 NMS-TXD- 11
12 NMS-TXDR 12
13 NMS-RXD+ 13
14 NMS-RXD- 14
15 15
Figure12.35 Pin assignment for back to back (point to multi-point) connection (3)
(Termination connector)
- 67 -
ROI-S04188
RPM
RPM
NMS Port
HYB CONV
15pin(M) 15 pin(M)
15pin(M) 15 pin(M)
- 68 -
ROI-S04188
RPM RPM
RPM SCPM
F M
NMS Port NMS Port
[RS485] [RS485]
F M F
(2)
(1)
(2)
HYB CONV
15pin(F)
RS-485
1 1 1
1
2 2 2
2 EMS-TXD+
3 3 3
3 EMS-TXD-
4 4 4
4 EMS-TXDR
5 5 5
5 EMS-RXD+
6 6 6
6 EMS-RXD-
7 7 7
7 GND
8 8 8
8
9 9 9
9
10 10 10
10 NMS-TXD+
11 11 11
11 NMS-TXD-
12 12 12
12 NMS-TXDR
13 13 13
13 NMS-RXD+
14 14 14
14 NMS-RXD-
15
15 15 15 Termination is not required
because both TX/RX line are
terminated in HYB CONV.
Figure12.41 Pin assignment for back to back (point to multi-point) connection (2)
(Cascade connection Cable)
- 69 -