PNMS Engineering ROI-S04188-052E (Ver.4).pdf

8/10/2019 PNMS Engineering ROI-S04188-052E (Ver.4).pdf

1/68

ROI-S04188-052E021212

P ASOLINK

N ETWORK

MANAGEMENT

S YSTEM

Engineering Manua(PASOLINK Version)

NEC CorporationCopyright 2002


2/68

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 NECCorporation. The information contained in this material is subject to change without notice.

NEC CorporationTokyo, JAPAN

Copyright Notices. Copyright 2002 NEC Corporation, all right reserved.

Reproduction, adaptation, or translation of this material without prior written permission isprohibited, expected as allowed under the copyright laws.


3/68

ROI-S04188

PNMS Engineering manual- i -

CONTENTS

1 INTRODUCTION 1

2 SYSTEM OVERVIEW 2

3 SYSTEM COMPONENTS 3

3.1 PNMS-CENTRAL SITE COMPUTER SYSTEM ..........................................................................3

3.2 PNMT - PASOLI NK NETWORK MANAGEMENTTERMINAL .................................................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 SIMPLETRUNK L INE NETWORK (SERIAL INTERFACE) .......................................................14

7.2 SIMPLETRUNK L INE NETWORK (LAN INTERFACE)............................................................16

7.3 MULTI SUB-BRANCH NETWORK .........................................................................................19

7.4 PNMS IP ADDRESSING SUMMARY ....................................................................................22

7.5 IP ADDRESS REQUIREMENT F OR CUSTOMER......................................................................23

7.6 MAXIMUM NUMBER OF IP ADDRESS...................................................................................24

8 INTEROPERABILI TY 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 TYPI CAL CONFI GURATION 28

9.1 MULTI-CLUSTER NETWORK (1) -DEDICATED LEASED L INE (SERIAL INTERFACE)- ............28

9.2 MULTI-CLUSTER NETWORK (2) DEDICATED LEASED L INE (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 RELIABILI TY 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 (MI U) ..........................................................................5312.3 PNMS CABL E .................................................................................................................54


4/68


5/68

ROI-S04188

PNMS Engineering manual- 1 -

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 NetworkManagement 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 Windows95/98/NT/2000 based portable PC and connected to SV (marked as LA) port at 9.6/19.2kbpsasynchronous mode. PNMT can login to a PMC and monitor and control any PASOLINKremotely in the network. Therefore the PNMT is used mainly for maintenance purpose. Forcontinuous network monitoring, PNMS is required. All PASOLINKs under the PNMS arealways 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 thecommunication of network management system possible. It is also includes the procedure forPASOLINK network system design, the architecture, the interpretation of a radio network tothe system, determination of the communication paths, and consideration of systemexpansion. In addition, this guide gives some examples of System design, the drawings forcabling of components and the PMC (PASOLINK Management Card) naming andaddressing 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.


6/68

ROI-S04188


2. SYSTEM OVERVIEW

NEC designed PASOLINK Network Management System (PNMS) which enablesremote monitoring and control of a radio network. The NEC PNMS is a sophisticatedsupervisory tool for transmission equipment and allows operator to perform remotesystem monitor alarms, control NE configuration parameters and display event loggingand 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. Itsupervises and controls PASOLINK transmission equipments.

In the following sections the functions and the usage of each component are described inmore detail.

PNMSPNMT

ID U

RS-232C, 19.2kbps

RS-232C,19.2kbps

Digital Service Channel, 9.6kbps

PM

CARD

Operation Center

Concept of NMS for PASOLINKConcept of NMS for PASOLINK

Figure 2-1 Typical PNMS Application


7/68

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 requestfrom the operators and sends them to the on-site equipment for execution. Two types ofPNMS can be proposed in accordance with Customers Network size. One is PNMS onWindows NT/2000 (supporting up to 500NEs) and the other is PNMS on UNIX OS(supporting up to 1,000NEs).

3.2 PNMT - PASOLINK Network Management Terminal

The PNMT (PASOLINK Network Management Terminal) is a portable computer fitted withNEC's PMNT software, which is used, as an on-site maintenance tool by technicians. Itconnects 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 ofPNMS.

The PNMT function can also be run on the PNMS to provide configuration and applicationsoftware upgrade for PM Card from a central point.

The PNMT runs in the Windows 95/98/NT/2000 environment and makes extensive use of theuser friendly Windows Graphical User Interface (GUI). It cannot only interrogate individualPMCs but also monitors the network (subnetwork). It means that the PNMT user can makeconnections to remote PMC from any node within a PASOLINK subnetwork. A PASOLINKsubnetwork is defined as a collection of PMC nodes headed by Central PM CARD. Sub PMCard 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 statusinformation from PASOLINK and to control that equipment in response to commands fromthe central site operator. The PMC primary tasks are to control and acquire data fromPASOLINK at remote location and transfer this data back to the central site. The PM card isdesigned as plug-in modules.

3.3.1 SNMP Agent Function

- PM Cards is functioned as a SNMP agent, which detects alarm and status changes inmonitored equipment, and sends of change notifications to PNMS

- PM Card retains the MIB data and transmit a response to SNMP GET commands fromPNMS and PNMT.

- Execution of SNMP SET message commands received from PNMS/PNMT and transmita control command to the alarm control portion (ALM CONT) in the IDU.


8/68

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 theperformance 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)- Out of Frame Seconds (OFS) only for PASOLINK-S

Stored period in PM Card

There are two types of performance data files, one is every 15 minutes data file and the otheris every day data file.

PASOLINK-S : per 15 minutes data : 4 daysper day data : 7 days

PASOLINK : per 15 minutes data : 7 daysper day data : 7 days

- Performance Monitor file format

Performance monitor file is Binary format in PM Card (This file is stored in PNMS/PNMT asASCII 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.


9/68

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. Todistribute the traffic load we normally define one of the PMC as master and the rest as slavesthrough 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).

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

1. Basic function of PMC

The PM Cards (PMC) operational mode is based on Master/Slave polling concept. Thenetwork 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 differentroles according to the installed software in a network management system as follows;

(1) Master mode (CPM):

To get information from the remote sites and to generate reports to the Central Computer(PNMS). The CPM may act as a terminal unit; which processes and then transfers all thephysical information of equipment, which is directly connected to the CPM. In addition,CPM is connected to PNMS via a dedicated serial communications link, and passesmessages received from RPMCs to the PNMS for display.


10/68

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 agateway between CPM and RPM and routing the messages from CPM to RPM andback.

Terminal unit function that acts as a stand-alone data acquisition and control unitwhich processes and then transfers all the physical information of equipment which isdirectly connected to the SCPM. This function is the same as that of RPM (SlaveMode).

(3) Slave Mode (RPM):

RPM is a stand-alone data acquisition and control unit. It monitors and controlsequipment at some remote location. Its prime task is to monitor and control and transferdata 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). Toincrease the number of RPM to more than 14, another CPM is required.

OnePNMS can handle up to 32 CPMs. (The detailed network sizing rule is described inSECTION 6.)

Therefore in case of regional PNMS-CPM-RPM configuration, one PNMS can handlemax. 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 isincreased more than 416 RPMs.

As a rule of thumb, SCPM is used in order to increase the network size that can besupervised 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 ofCPM(s) within one PNMS coverage.


11/68

ROI-S04188


(3) Adoption Criteria SCPM

As basic rule, if the number of RPM becomes 10, a SCPM is assigned on the head of thegroup of RPM(s) then connected to CPM. As mentioned before, additional 3 RPM(S) maybe connected in the maximum case . However this possibility is reserved for futureexpansion. (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-masterin 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 beapplied. In other word, SCPM NE is NE which may be selected as RPM or SCPMdepends 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 rolechange when receiving a polling signal from its upper PM card. During role change, an alarmis 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 RPM5 RPM6 RPM7


12/68

ROI-S04188


4. PHYSICAL INTERFACE

Summary of physical interface of each equipment is described below.

Figure 4-1 Available Physical Interface

PNMS

CPM

PNMT

SCPM

RPMRS-232C9.6/19.2kbps

Async.

(For Windows NT)

10Base T

(For Windows NT and Unix)

RS-232C/V.11

9.6/19.2kbps

Async.

or

LAN(10Base-T)

(NMS port)

RS-485

or

RS232C

9.6kbps

Async.

(NMS port)

RS-232C(COM port)

RS-232C (LA port) RS-232C (LA port)

DSC (9.6kbps) internal connection10 Base-T

For upper management system

RS-485

or

RS232C

9.6kbps

Async.

(NMS port)

4.1 PNMS

4.1.1 Serial InterfaceFunctional : RS232C

Electrical : V.24

Mechanical : DB 9 PIN

Communication rate : 9.6/19.2 kbps (Asynchronous)

4.1.2 LAN Interface

Interface : Ethernet (100/10 BaseT)

Connector type : RJ-45


13/68

ROI-S04188


4.2 PNMT

Functional : RS232C

Electrical : V.24

Mechanical : DB 9 PINCommunication rate : 9.6/19.2 kbps (Asynchronous)

4.3 PM Card

4.3.1 LA Port

Functional : RS232C

Electrical : V.24


Communication rate : 9.6/19.2 kbps (Asynchronous)

4.3.2 NMS Port

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)


Communication rate

for PNMS connection : 9.6/19.2 kbps (Asynchronous) (for RS232C/RS422)

for Back to Back connection : 9.6kbps (Asynchronous)

LA portNMS port


14/68

ROI-S04188


5. PNMS COMMUNICATION INTERAFCE

The interface condition between PNMS and NEs (CPM,SCPM,RPM) is summarized in Figure5.1 (Serial interface) and Figure5.2 (LAN interface). The physical interface at PNMSHardware is RS232C or 10baseT interface. The physical interface at CPM for PNMSconnection is RS-232C (9.6/19.2kbps, Async.). The physical interface at CPM, SCPM and

RPM for back to back connection is RS-232C or RS-485 (9.6kbps, Async.). And the choice ofthe physical interface at CPM,SCPM and RPM should be done by the PNMS software.

Serial Interface between PNMS (Windows) and CPM

Figure5-1 PNMS Communication Architecture (Serial Interface)

RPM

-1

SCPM

-2

SNMP/TFTPSNMP/TFTPSNMP/TFTPAP

RS-232C/485

9.6kbps Async.

RS-232C/485

9.6kbps Async.

RS-232C

19.2kbps Async.

Physical*

HDLC/NRMHDLC/NRMPPPData Link

IPIPIPNetwork

UDPUDPUDPTransport

SCPM-RPMCPM-SCPMPNMS-CPM

CPM

RPM

-3

-4

*The converter will

be required for

other interfaces.

LAN Interface between PNMS (Windows and UNIX) and CPM

Figure 5-2 PNMS Communication Architecture

RPM

-1

SCPM

-2

SNMP/TFTPSNMP/TFTPSNMP/TFTPSNMP/TFTPAP

RS-232C/485

9.6kbps Async.

RS-232C/485

9.6kbps Async.

RS-232C

19.2kbps Async.

10baseTPhysical*

HDLC/NRMHDLC/NRMPPPEthernetData Link

IPIPIPIPNetwork

UDPUDPUDPUDPTransport

SCPM-RPMCPM-SCPMROUTER-CPMPNMS-ROUTER

CPM

RPM

-3

-4

RR IPNetwork

*The converter will

be required forother interfaces.


15/68

ROI-S04188


6. NETWORK SIZING RULE

The following network sizing restriction is applied when NEC PASOLINK supervisory networkhierarchy is configured.

Restriction in this layer Restriction of Number of NE in thislayer

PNMS(UNIX)(10,000NE type)

Maximum number of CPMs =192(1)

Maximum number of NE (CPM +SCPM + RPM) s = 10,000(5)

PNMS (UNIX)(1,000NE type)

Maximum number of CPMs = 32 Maximum number of NE (CPM +SCPM + RPM) s = 1,000

Maximum number of CPMs = 16(Serial Interface)

PNMS (NT)

Maximum number of CPMs = 32(LAN Interface)

Maximum number of NE (CPM +SCPM + RPM) s = 500

CPM Maximum number of SCPMs =

31(2)

Maximum number of SCPMs(when CPM is in Dual Master

mode) = 30(3)

Maximum number of directlyconnected SCPMs with one CPM

= 13(4)

Maximum number of NE (SCPM +

RPM) = 416

SCPM Maximum number of (SCPM(5)

+

RPM)s = 13

Maximum number of NE (SCPM +

RPM)s = 13(6)

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

(1) Maximum number of CPMs for Central type PNMS is recommended to be less than100 due to PNMS hardware performance limitation even if theoretical value is 192 asindicated in the Table 6.1


16/68

ROI-S04188


(2) The diagram below demonstrates the restriction per CPM

(3) In case that the two(2) physical Subnets connection is required to CPM as shownbelow, the CPM is regarded as Dual master mode.

PNMS

Subnet1

SCPM1 SCPM2

Subnet2 Subnet3

Subnet32

SCPM31

Subnet N

SCPM N-1

Subnet N+1

SCPM N

Figure 6.1

Maximum number of subnet is 32 under a CPM.

Therefore maximum number of SCPM is 31.

: RPM

: CPM

: SCPM

PNMS

SCPM3

Subnet4

Subnet32

SCPM30

Subnet N+1

SCPM N-1

Subnet N+2

SCPM N

Subnet 3

Figure 6.2 CPM (Dual Master mode)

Maximum number of subnet is 32. In case of dual CPM configuration,

maximum number of SCPM is 30.

Dual Master

SCPM2

Subnet2 Subnet1

SCPM N+1

Radio SectionBack to back connection

: RPM

: CPM

: SCPM


17/68

ROI-S04188


(4) The diagram below demonstrate this restriction on the CPM layer.

(5) Maximum number of NEs is set to 10,000, assuming there are 10 regional PNMS (10Regional 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.

PNMS

Figure 6.3

Maximum number of SCPM per CPM

: 31 or 30(Dual Master)

Maximum number of directly connected

SCPM with CPM is13.

(CPM and SCPM issame subnetwork)

: RPM

: CPM

: SCPM


18/68

ROI-S04188


7. PNMS IP ADDRESSING

PNMS identifies each NE with IP address (IP v4). IP addressing scheme and requirement isdescribed 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). Serial interface is assumed for the interface between PNMS (Windows) andCPM in this figure.

PNMS(Windows)

PNMS

1

3

Remote Site-A

4 5

Remote Site-B

6 7

Remote Site-C

8

Remote Site-D

2

: RPM

RS232C

19.2/9.6kbps, Async

2

Figure7.1 Typical Network Example (Simple trunk line [Physical Model])

1 : CPM

Figure 7.2 shows a logical network of Figure7.1 and IP address assignment example. Todemonstrate connection of each NE with PNMS, 2 sub-networks, PNMS and CPMsub-network (A) and PASOLINK CPM cluster network (B) are defined.

1

CPM

2

RPM

4

RPM

5

RPM

6

RPM

7

RPM

8

RPM

3

RPM

PNMS

Central Site

172.20.100.1

172.20.100.2

172.20.101.2

172.20.101.3

172.20.101.6

172.20.101.4172.20.101.5 172.20.101.7

172.20.101.8

172.20.101.1

Subnet-B (PASOLINK CPM cluster)

Subnet-A (PNMS-CPM Subnetwork)

Figure7.2 Typical Network Example (Simple trunk line [Logical Model])


19/68

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 shownFigure7.2. In this figure, the CPM is connected to PNMS through RS-232C interface and PPPencapsulation. 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 IPaddresses are not available because one is assigned for network address, the other isreserved 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 aSubnet mask of 255.255.255.240. (fixed) for this sub-network. Therefore one sub-network inCPM 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 fornetwork address, the other is reserved for broadcast address, in addition one IP address is

assigned for CPM.

For reference assigned IP address and available IP address of each sub-network are shownin following table.

Subnet-B : 172.20.101. 0 15 (Assigned IP Address): 172.20.101. 1 14 (Available IP Address)

Table7.1 Example for IP address planing in each Subnet

Subnet-A : 172.20.100. 0 3 (Assigned IP Address)

172.20.100. 1 2 (Available IP Address)


20/68

ROI-S04188


7.2 Simple Trunk Line network (LAN Interface)

Figure7.3 shows typical network example (simple Trunk line) with LAN interface through IPnetwork between PNMS and CPM.

PNMS

1

3

Remote Site-A

4 5

Remote Site-B

6 7

Remote Site-C

8

Remote Site-D

2

: RPM

RS232C

19.2/9.6kbps, Async

2

1 : CPM

R : Router

Figure7.3 Typical Network Example (Simple trunk line [Physical Model])

IP

Network

R R

Figure 7.4 shows a logical network of Figure7.3 and IP address assignment example. Todemonstrate connection of each NE with PNMS, 2 sub-networks, Router and CPMsub-network and PASOLINK CPM cluster network are defined.

1

CPM

2RPM

4RPM

5RPM

6RPM

7RPM

8RPM

3RPM

PNMS

Central Site

172.20.100.1

172.20.100.2

172.20.101.2

172.20.101.3

172.20.101.6

172.20.101.4

172.20.101.5 172.20.101.7

172.20.101.8

172.20.101.1

Subnet-B (PASOLINK CPM cluster)

R

Subnet-A (Router-CPM Subnetwork)

RIP

Network

Figure7.4 Typical Network Example (Simple trunk line [Logical Model])


21/68

ROI-S04188


7.2.1 IP Addressing Scheme for Router-CPM Subnetwork

CPM NMS port and the Router Serial port must be located in the same sub network as shownFigure 7.4. In this figure, the CPM is connected to the router (R) and must be added to the IProute of the said router. The interface is RS-232C and PPP encapsulation. The CPM NMSport IP address is added to the IP route table of 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 IPnetwork, the router passes this to the CPM NMS port and then the CPM passes it to thedestination NE, which is the recipient of the packet as shown in Figure 7.4.

For this Router and CPM sub-network, PNMS uses a subnet mask of 255.255.255.252(fixed). One RouterCPM sub network includes 4 IP addresses accordingly. However only 2IP addresses are not available because one is assigned for network address, the other isreserved for broadcast address.

. To allocate plural CPMs and Router ports in the future in this sub-network for networkexpansion as shown Figure 7.5, the Class C sub-network (for example 172.20.100.**) isrecommended.

1

CPM

12

RPM

PNMS

Subnet-D (PASOLINK CPM cluster)

RIP

Network

Figure7.5 Typical Network Example (Multi-branch network [Logical Model])

R

13

RPM

18

RPM

3

CPM

32

RPM

38

RPM

33

RPM

22

RPM

28

RPM

23

RPM

2

CPM

Subnet-A (Router-CPM subnetwork) Subnet-B

Subnet-C

Subnet-E

Subnet-F


22/68

ROI-S04188


7.2.2 IP Addressing Scheme for PASOLINK CPM Cluster

Refer to section 7.1.2.

For reference assigned IP address and available IP address of each sub-network are shownin Table 7.2 for Figure 7.4 and Table 7.3 for Figure 7.5

Subnet-B : 172.20.101. 0 15 (Assigned IP Address)

: 172.20.101. 1 14 (Available IP Address)

Table7.2 Example for IP address planing in each Subnet for Figure 7.4





Table7.3 Example for IP address planing in each Subnet for Figure 7.5



Subnet-C : 172.20.100. 8 11 (Assigned IP Address)

: 172.20.100. 1213 (Available IP Address)

Subnet-D : 172.20.101. 015 (Assigned IP Address)


Subnet-E : 172.20.101. 1631 (Assigned IP Address)


Subnet-F : 172.20.101. 3247 (Assigned IP Address)

@@@@@ : 172. 20.101.3346 (Available IP Address)


23/68

ROI-S04188


7.3 Multi Sub-Branch Network

Figure7.6 shows typical network example (Multi sub-branch network). In this figure serialinterface between PNMS and Router is assumed.

Central Site

PNMS

(Windows)

1

4

Remote Site-A

5 6

Remote Site-B

Remote Site-C

14

Remote Site-D

3

10 9

12 1113

Remote Site-E

Remote Site-F

Remote Site-G

7

82

RS232C

19.2/9.6kbps, Async

RS485

9.6kbps, Async

Figure 7.6 Typical Network Example (Multi sub-branches network[Physical Model])

: RPM3

1 : CPM

2 : SCPM

Figure 7.7 shows a logical network of Figure7.6 and IP address assignment example. Todemonstrate connection of each NE with PNMS, 3 sub-networks, PNMS and CPMsub-network (A) and PASOLINK CPM cluster network (B and C) are defined.

1

CPM

2

SCPM

4

RPM

5

RPM

6

RPM

7

RPM

8

RPM

3

RPM

PNMS

Central Site 14

RPM

11

RPM

10

RPM

9

RP M

12

RPM

13

RPM

172.20.100.1

172.20.100.2

172.20.101.2

172.20.101.3

172. 20.101.6

172.20.101.4

172.20.101.5

172.20.101.7

172. 20.101.8

172.20.101.9

Subnet-B(PASOLINK CPM cluster)

Subnet-C

172.20.101.17

172.20.101.18172.20.101. 19172.20.101. 20172.120.101. 21

172.20.101. 22

Subnet-A(Router-CPM Subnetwork)

172.20.101.1

Figure 7.7 Typical Network Example (Multi sub-branches network[Logical Model])

7.3.1 IP Addressing Scheme for PNMS-CPM Subnetwork

Refer to section 7.1.1.


24/68

ROI-S04188


7.3.2 IP Addressing Scheme for PASOLINK CPM Cluster

PNMS uses a Subnet mask of 255.255.255.240. (fixed) for this sub-network. Therefore onesub-network in CPM cluster has 16 IP addresses. Depending on the size, a network cannormally be divided into a number of sub-networks to distribute the traffic load. Each subnetwork can accommodate 16 IP addresses. Available IP addresses for Remote PM Card

(RPM) are 13.

In Figure7.6, 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 subnetwork address and 172.20.101.15 is reserved for broadcast address. In addition one IPaddress is assigned on Central PM Card. Therefore 13 IP addresses (for 13 RPMs) areavailable in Subnet-B (same as for all other sub network).

In addition IP address for next sub-network (Subnet-C) shall be assigned from172.20.101.16. (172.20.101.17 to172.20.101.30 is available), even if Subnet-B has less than13 NEs (for example only one NE), Subnet-C is started to assign from 172.20.101.17.

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 x32 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 toassure the 512 IP Addresses.

For reference assigned IP address and available IP address of each sub-network are shownin Table 7.4.



Subnet-C : 172.20.101.16 31 (Assigned IP Address)


Table 7.4 Exam ple for IP address planing in each Subnet




25/68

ROI-S04188


7.3.3 Example of IP Addressing for Multi Sub-Branch Network

Figure7.8 show the example of IP address assignment for CPM cluster with 8 sub-network

RPM SCPM

CPMSCPMRPMRPMRPM

RPM SCPMRPM

RPM SCPM172.18. 0.1

RPM SCPMRPMRPM

RPM SCPM

172.18.0.18

172.18.0.2

172.18.0.33

172.18.0.34

172.18.0.65

172.18. 0. 36

172.18.0. 35

172.18.0.78

172.18. 0.66

172.18.0. 49172.18.0. 50172.18. 0.51172.18.0.62

172.18.0.81172.18.0.83

172.18.0. 94

172.18.0.82

172.18.0.97

172.18. 0. 113

171.18.0. 110

172.18.0.126

B

CD

E

F

G

H

172.18.0. 37

172.18. 0.67

PNMS

Figure 7.8 Network Example (IP address Scheme)

172.18.2.2

172.18.2.1

172.18.0.17

A

I

Router and CPM

subnetwork

R

Table 7.5 shows assigned IP addresses and available IP addresses of each sub network ofthis multi sub-branch network.

Subnet-C : 172.18.0. 1631 (Assigned IP Address)


Subnet-D : 172.18.0. 3247 (Assigned IP Address)


Subnet-E : 172.18.0. 4863 (Assigned IP Address)


Subnet-F : 172.18.0. 6479 (Assigned IP Address)

@@@@@ : 172. 18.0. 65

78 (Available IP Address)Subnet-G : 172.18.0.8095 (Assigned IP Address)

: 172.18.0.8194 (Available IP Address)

Subnet-H : 172.18.0.96111 (Assigned IP Address)


Table 7.5 : Example for IP address planning in each Subnet

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 (Assigned IP Address)


Subnet-I : 172.18.0.112127 (Assigned IP Address)



26/68

ROI-S04188


7.4 PNMS IP Addressing Summary

Figure 7.9 (Serial Interface) and Figure 7.10 (LAN interface) describe the summary of PNMSIP addressing scheme

Figure 7.9 IP address Scheme for PNMS (Serial interface between PNMS and CPM)

Subnet Mask is 255.255.255.240

(11111111.11111111.11111111.11110000)

Number of assigned address is 16.

All 1s and 0s are reserved.

Therefore 14 address are available

for each network.The last 8 bit is also used as a HDLC

address for polling.

The CPM and SCPM works as a router to

routing the packets among the networks.


(11111111.11111111.11111111.11111100)



Therefore 2 address are available.

CPM

SCPM

SCPMSCPM

RPMRPM

RPM

PNMS (Windows)

R


(11111111.11111111.11111111.11110000)



Therefore 14 address are available

for each network.

The last 8 bit is also used as a HDLC

address for polling.

The CPM and SCPM works as a router to

routing the packets among the networks.


(11111111.11111111.11111111.11111100)



Therefore 2 address are available.

CPM

SCPM

SCPMSCPM

RPMRPM

RPM

R

IP

Network

Figure7.10 IP address Scheme for PNMS (LAN interface between PNMS and CPM)


27/68

ROI-S04188


7.5 IP Address Requirement for Customer

During the Network Design phase, following IP address must be required in order for eachNEs to connect to the PNMS.

1) RouterCPM sub-network

IP address for Router Serial port

IP address for CPM NMS port (Provision of one class C sub-network isrecommended for multiple Routers in future for expansion)

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)

3) Others

IP address for the PNMS


28/68

ROI-S04188


7.6 Maximum Number of IP Address

When the PASOLINK network is configured according to the sizing rule, the theoreticalnumber of IP address is calculated as shown in following Table 7.6.

Layer

Theoretical absolute maximumnumber of IP address for NECPASOLINK CPM cluster subnetwork

Theoretical absolute maximum numberof IP address for Router-CPM subnetwork

PNMS (UNIX)(10,000NE Type)

98,304(This type PNMS has up to192 CPMs and each CPM can haveup to 32 subnets and each subnethas a maximum of 16 addresses;therefore total = 192 x (32 subnets x16)) =98,304).

384 (Maximum number of CPMs is 192,two IP addresses are required (RouterSerial IP address and CPM PNMS portIP address).

PNMS (UNIX)

(1,000NE Type)PNMS (Windows)(LAN interface)

16,384 (This type PNMS has up to

32 CPMs and each CPM can haveup to 32 subnet and each subnet hasa maximum of 16 addresses;therefore total = 32 x (32 subnets x16)) = 16,384).

64 (Maximum number of CPMs is 32,

two IP addresses are required (RouterSerial IP address and CPM PNMS portIP address).

PNMS (Windows)(Serial Interface)

8,192 (1 PNMS has up to 16 CPMsand each CPM can have up to 32subnet and each subnet has amaximum of 16 addresses;therefore total = 16 x (32 subnets x16)) = 16,384).

32 (Maximum number of CPMs is 16,two IP addresses are required (RouterSerial IP address and CPM PNMS portIP address).

CPM 512 (1 CPM can have up to 32subnet and each subnet has amaximum of 16 addresses thereforetotal = 32 subnets x 16 = 512).

2 (Router Serial IP address and CPMPNMS port IP address)

SCPM 16 (13 address for the SCPM/RPM*7)

, one for the SCPM*8)

, one forbroadcast address, one for thenetwork address.

-

Table7.6 : Network Sizing Rule (Theoretical, Number of IP address)

Note:The above numbers are theoretical maximum. The practical numbers required are

determined by network capacity and performance requirements by the Customer. For examplethe number of CPMs per PNMS can be optimised to three (3) to cover the maximum 1000 NEsinstead of the above theoretical maximum 32 CPMs by introducing effective mediation devicessuch as MIU (Refer to Section 12.2)


29/68

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 andinteroperability among different manufacturers will have to be confirmed. The purpose of thissection 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 RS485interface.

Point to point Connection Point to multi-point(daisy chain) connection

Otherequipment(RS485)




PASOLINKRS485

PASOLINK(RS485)

Not Available(Note 1)

(Note 2) Not Available(Note 1)

Not Available Available

ProposedSolution

Convert RS422by using HYB CONV

Convert RS422by using HYB CONV

-

Table 8.1 Connection availability

Note.1) Because the method of connecting data signal lines in plural connections in point tomulti-point line is not determined, it is not possible to connect equipment fromdifferent manufacturers unless connection test between PASOLINK and otherequipment is required.

Note.2) Terminal impedance of other manufacture equipment is not clear. Therefore outputlogical condition of other manufacture equipment is not clear in high impedancecondition. In this case it is impossible to connect each other. (Connection test isrequired between PASOLINKand other equipment.)


30/68

ROI-S04188


8.2 Point to Point Connection

Figure 8.1 shows the PASOLINK supervisory interface with existing network (dedicated linesuch as DSC) between PNMS and CPM.

PASOLINK CLUSTER

DSC i 19.2/9.6kbps, ASYNCj

Figure 8.1 Interoperability with other manufacture equipment

PNMS

(Windows )

Existing Network (Dedicated line)

RS232C port

(In case of other than RS232C port,

additional converter is required

in accordance with the existing

physical interface

RS-232C19.2/9.6kbps

ASYNC

RS-232C

19.2/9.6kbpsASYNC

DSC i 19.2/9.6 kbps, ASYNCj

LAN

RS-232C

19.2/9.6kbps

ASYNC


RS232C port




physical interface

PNMS

(UNIX or

Windows )

PASOLINK CLUSTER

R

RS-232C

19.2/9.6kbps

ASYNC

Figure 8.2 show the PASOLINK supervisory interface with existing network (PSTN or IPnetwork) between PNMS and CPM.

MD MD

IP

Network

Figure 8.2 Interoperability with other network

LAN

RS-232C

9.6kbps

ASYNC

RS-232C

9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PSTN

Continuous connection is needed

PNMS

(UNIX or

Windows)

PNMS

(Windows )

PASOLINK CLUSTER

RR

PASOLINK CLUSTER


31/68

ROI-S04188


Figure 8.3 show the PASOLINK supervisory interface with existing network betweenPASOLINKs.

Figure 8.3 Interoperability with other network (point to point connection)

LAN

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


19.2/9.6 kbps, ASYNC PNMS

(UNIX or

Windows)

LANRS-232Cor RS-485

19.2/9.6kbps

ASYNC

RS-232C, RS-48519.2/9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PNMS

(UNIX or

Windows)

MD MD

PSTN


R

R

RS232Cport


additional converter is requiredin accordance with the physical interface

PASOLINK CLUSTER

PASOLINK CLUSTER

8.3 Point to Multi-Point Connection

Figure 8.4 show the PASOLINK supervisory interface with existing network betweenPASOLINKs (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 supervisionsignal.

Figure 8.4 Interoperability with other network

LANRS232C, RS-485

19.2/9.6kbps

ASYNC

RS-232C, RS-48519.2/9.6kbps

ASYNC

RS-232C19.2/9.6kbps

ASYNC

Existing Network

(Dedicated line)

19.2/9.6 kbps, ASYNC

RS232 or RS422 or RS485 port

(In case of other than RS232C or RS485 or RS485 port,

additional converter is requiredin accordance with the existing physical interface

PNMS

(UNIX orWindows)

H

Y

B

C

O

N

V

H

Y

B

C

O

N

V

R

R :Router

: Existing Network (Dedicated line): RPM

: CPM

PASOLINK CLUSTER


32/68

ROI-S04188


9. TYPICAL CONFIGURATION

The PNMS supports a variety of radio topologies. That is, there are many ways in which theconnections can be made between PNMS, CPM, SCPM and RPM. The system design is toanalyse the network and customer requirement, to decide the PASOLINK networkconfiguration, to estimate the cost and provide customer with some optimised solutions.

Based on the radio network information a PASOLINK network management system can beformed 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 andfunctionally manageable for monitoring and controlling in accordance with section6.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 centralcomputer 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.

EEE

Figure 9.1 Multi-branch network through Digital Service Channel

with PNMS Serial interface

PNMS

(Windows)

Extension port (board

inserted into PCI SLOT)

EEEE

RS-232C

19.2/9.6kbps

ASYNCRS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER



RS232C port




physical interface

PASOLINK CLUSTER


33/68

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 LANinterface and dedicated line such as DSC. 19.2kbps or 9.6kbps (RS232C interface) arerequired for Router port of dedicated line or Digital Service Channel .

EEEE

EEEE

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS

(UNIX or

Windows )



RS232Cport



in accordance with the physical interface

Figure 9.2Multi-branch network through Digital Service Channel

with PNMS Serial interface

RS-232C

19.2/9.6kbps

ASYNC

9.3 Multi-Cluster Network (3) PSTN (Serial Interface)-

Figure9.3 shows a multi-cluster network, monitored and controlled by PNMS through serialinterface and PSTN. RS232C interface (9.6/19.2kbps) are required for Modem.

PNMS(Windows)

MD

MD

MD

MD

MD

MD

MD

MD

EEEE

RS-232C9.6kbps

ASYNC

RS-232C

9.6kbps

ASYNC

Extension port (board

inserted into PCI SLOT)

EEEE

PASOLINK CLUSTER

PSTN


Figure 9.3 Multi-branch network through PSTN with PNMS Serial interface

PASOLINK CLUSTER


34/68

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 LANinterface and PSTN. RS232C interface (9.6/19.2kbps) are required for Modem.

MD

MD

MD

MD

MD

MD

MD

MD

E

EEE

RS-232C9.6kbps

ASYNC

RS-232C

9.6kbps

ASYNC

E

EEE

PASOLINK CLUSTER

PSTN


Figure 9.4 Multi-branch network through PSTN with PNMS LAN interface

R

PASOLINK CLUSTER

PNMS

(UNIX or

Windows )

9.5 Multi-Cluster Network (5) IP Network (LAN Interface)-

Figure 9.5 shows a multi-cluster network, monitored and controlled by PNMS through LANinterface and IP network.

IP NETWORK

LAN

RS-232C

19.2/9.6kbps

ASYNC

EEEE

PASOLINK CLUSTER

PASOLINK CLUSTER

Figure 9.5 Multi-branch network through IP network

R

R

R

R

R

PNMS

(UNIX or

Windows )


35/68

ROI-S04188


9.6 CPM Reduction Solution

In accordance with customers network such that many CPM clusters scattered in all over theregion, plural CPMs are required to be monitored and controlled by PNMS as shown inFigure9.6. In such cases the number of the required Router serial port increases inaccordance with the number of CPMs. If the number of NEs within a PASOLINK cluster

managed by a CPM is smaller than 416, it is possible to combine such PASOLINK clusters tooptimise the configuration. To reduce CPMs, 3 solutions are proposed as described infollowing section.

The concept for reducing CPM is shown Figure 9.7. The CPM function is located at PNMSsite. In case that each PASOLINK cluster scattered all over the region and these are neededto be connected through customers DSC, HYB CONV can concentrate this connection atPNMS site. Then single combined signal is connected to CPM.

EEEE

EEEE

RS-232C

19.2/9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS

(UNIX or

Windows)



RS232C port




Figure 9.6 Multi cluster network through Digital Service Channel

: RPM

: CPM

: SCPM

Up to 416 NEs

Up to 416 NEs

Up to 416 NEs

Up to 416 NEs

EEEE

EEEE

RS-232C or RS485

9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS

(UNIX or

Windows)


9.6 kbps, ASYNC

RS232C port


additional converter is requiredin accordance with the physical interface


CPM

Function

H

Y

B

C

O

N

V

: RPM

: CPM

: SCPM

Up to 416 NEs


36/68

ROI-S04188


9.6.1 Solution 1

This solution is applied for the case of PASOLINK HOP locating at PNMS site as shown inFigure 9.8.

EE

EE

EEEE

RS-232C or RS485 port

9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS

(UNIX or

Windows)


9.6 kbps, ASYNC

RS232C port (In case of other than RS232C

port,additional converter is required



H

Y

B

C

O

NV

: RPM

: CPM

: SCPM

Up to 416NEs

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 Section12.2.)

EEEE

EEEE

RS-232Cor RS485

9.6kbps

ASYNC

RS-232C

19.2/9.6kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS

(UNIX or

Windows)


9.6 kbps, ASYNC

RS232C port





H

Y

B

C

O

N

V

MIU

Up to 416 NEs

: RPM

: CPM

: SCPM

RS-485

9.6kbps

ASYNC


37/68

ROI-S04188


9.6.3 Solution 3

This solution is applied to support plural MIUs at PNMS site. Plural MIUs requires pluralserial 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 hasplural serial interface.

R

Figure 9.10 Network Architecture

PASOLINK CLUSTER

PNMS

H

Y

B

C

O

N

V

MUX

Function

PASOLINK CLUSTER

H

Y

B

C

O

N

V

PASOLINK CLUSTER

H

Y

B

C

O

N

V

MIU

MIU

MIU

RS-232C

19.2/9.6kbps

ASYNC

: Existing Network (Dedicated line)

Up to 416 NEs

Up to 416 NEs

Up to 416 NEs: RPM

: CPM

: SCPM

RS232C port

(In case of other than RS232C port,additional converter is required



9.6kbps

ASYNC


9.6kbps

ASYNC

RS-485

9.6kbpsASYNC


38/68


39/68

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 theselogs 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 downloadthe logging data from PNMS-1and to upload it to PNMS-2 desired directory and re-startPNMS-2, if Operator want to synchronize the logging data of both PNMS.

b) Performance monitor data

PNMS collects performance data stored in all PM Cards in the network once a day.(Collecting time can be set by Operator.) If PNMS-1 collects performance data of all NEs inthe network, PNMS-1 stores performance data of the day. However PNMS-2 does not storethe performance data. Therefore, after PNMS-2 is re-started, the performance data is notsynchronized between PNMS-1 and PNMS-2. In this case Operator is required to downloadthe 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 Configurationtool (PNMS) and is not automatically transferred to another PNMS regardless whether PNMSis 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 datain another PNMS to be identical to those in one PNMS accordingly.

PNMS-1 PNMS-2

R

Figure 10.1Parallel PNMS

LAN

Alarm or Event trap Alarm or Event trap

R : Router


40/68


41/68

ROI-S04188


3. Create configuration file on PNMS for each PM Card and PNMS by NetworkConfiguration tool.

4. Export configuration file of each PM Card and PNMS to the directory set up in theNetwork 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 windowfunction on PNMS.

Figure11.3 Network Example

: RPM

: CPM

: Radio Connection

: Cable Connection

PNMS Site

7. Connect PNMS to CPM and confirm the connection. After that it is possible tomonitor and control each NE.

Figure11.4@Network Example

: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

: Radio Connection

: Cable Connection


42/68

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.

Figure 11.5 Network Example

: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Hop

: 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 NetworkConfiguration tool.

5. Copy the configuration files of new PM Card from PNMS PC to PNMT and downloadthem 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 PMCard 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 foreach 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 bemodified.)

- Existing PM card connecting with new HOP physically : Modify SystemConfiguration file to recognize connecting with new HOP. (Although NetworkConfiguration file is also necessary to be modified, the network configuration file isautomatically modified and downloaded from Master PM CARD (CPM or SCPM) tothe RPM under it.)


43/68

ROI-S04188


-Other PM Cards in this CPM cluster: Although Network Configuration file isnecessary to be modified, the network configuration file is automatically modifiedand downloaded from Master PM CARD (CPM or SCPM) to each PM Cards underit. (System Configuration file is not necessary to be modified.)

Figure 11.6@Network Example

R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Hop

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection

7. Update Network configuration file for PNMS using Update Network Configurationwindow function PNMS. After that it is possible to monitor and control added NE.

Figure 11.7@Network Example

R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection


44/68


45/68

ROI-S04188


Figure 11.9Network Example

R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

NewSubnet

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection

7. Update Network configuration file for PNMS by Update Network Configuration windowfunction on PNMS. After that it is possible to monitor and control added subnetwork.


R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

Subnet-6

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection


46/68

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.


R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection

2. Decide each PM Card mode according to new network configuration as shownFigure11.13.

3. Create configuration file for PM Cards in modified subnetwork and for PNMS by

Network Configuration tool.4. Export configuration file for each PM Card and for PNMS to the director set up in the

Network Configuration tool.

5. Download modified configuration file to associated all NEs in new subnetwork and theMaster NE (CPM which new subnetwork is belonging and all SCPMs in the CPMcluster.) 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 isrequired.)

- Master PM CARD (CPM) and all SCPM in the CPM cluster : Modify NetworkConfiguration file to be recognized to modification of sub-network configuration

- All NEs in new subnetwork : Modify network configuration file and system

configuration file

- Other PM Card in this CPM Cluster: Although Network Configuration file isnecessary to be modified, the network configuration file is automatically modifiedand downloaded from Master PM CARD (CPM or SCPM) to the PM Card under it.(System Configuration file is not necessary to be modified.)


47/68

ROI-S04188



R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection

6. Update Network configuration file for PNMS by Update Network Configuration windowfunction on PNMS. After that it is possible to monitor and control modified sub network.


R

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet

: RPM

: CPM

: SCPM

R : Router

: Radio Connection

: Cable Connection


48/68

ROI-S04188


11.2 PNMS for UNIX

11.2.1 Install PNMS

1. Install PASOLINK hardware.

I f the PASOLINK system exists w ith conf igu rat ion f i le, skip Step 2 throug h Step 6.


: RPM

: CPM

: Radio Connection

: Cable Connection

PNMS Site

: PC for Network configuration tool

2. Decide each PM Card mode (for example Figure 11.15).


: RPM

: CPM

: Radio Connection

: Cable Connection

: SCPM

PNMS Site


3. Create configuration file for each PM Card and for PNMS by Network Configuration

tool on PC.


49/68

ROI-S04188


4. Export configuration file of each PM Card and for PNMS to the directory set up in theNetwork Configuration tool.

5. Copy the configuration files of each PM Card form PC (Network Configuration tool) toPNMT 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.


: RPM

: CPM

: Radio Connection

: Cable Connection

UploadMap file


7. Connect PNMS to CPM and confirm the connection. After that it is possible to monitor

and control each NE.


: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5


: Radio Connection

: Cable Connection


50/68

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.


: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Hop


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 theNetwork Configuration tool.

5. Upload the configuration file of each PM Card and PNMS from PC (Networkconfiguration 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) toPNMT and download them to new PM Card by PNMT and install new NE (ODU andIDU) 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 PMCard 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 foreach NE from PNMS PC to PNMT is required.)

- Master PM Card (Sub-CPM in Subnet-4): Modify Network Configuration file torecognize the added new HOP (System Configuration file is not necessary to bemodified.

- Existing PM card connecting with new HOP physically : Modify SystemConfiguration file to recognize connecting with new HOP (Although NetworkConfiguration file is also necessary to be modified, the network configuration file isautomatically modified and downloaded from Master PM CARD (CPM or SCPM) tothe RPM under it.)

- Other PM Cards in this CPM cluster: Although Network Configuration file isnecessary to be modified, the network configuration file is automatically modified


51/68


52/68


53/68

ROI-S04188



: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

NewSubnet


8. After that it is possible to monitor and control added subnetwork.


: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

Subnet-6



54/68

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.


: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet


2. Decide each PM Card mode according to new network configuration as shownFigure11.26.

3. Create configuration file for PM Cards in modified subnetwork and for PNMS byNetwork Configuration tool.

4. Export configuration file for each PM Card and PNMS to the directory set up in theNetwork Configuration tool.

5. Upload the configuration file for each PM Card and PNMS from PC(NetworkConfiguration 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 theMaster NE (CPM which new subnetwork is belonging and all SCPMs in the CPMcluster) 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 isrequired.)

- Master PM CARD (CPM) and all SCPM in the CPM cluster : Modify NetworkConfiguration file to be recognized to modification of sub-network configuration

- All NEs in new subnetwork : Modify network configuration file and systemconfiguration file

- Other PM Card in this CPM Cluster: Although Network Configuration file isnecessary to be modified, the network configuration file is automatically modifiedand downloaded from Master PM CARD(CPM or SCPM) to the PM Card under it.(System Configuration file is not necessary to be modified.)


55/68

ROI-S04188



: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet


7. After that it is possible to monitor and control modified sub network.


: RPM

: CPM

: SCPM

R

R : Router

Subnet-1

Subnet-2

Subnet-3

Subnet-4

Subnet-5

New Subnet



56/68

ROI-S04188


12. RELATED EQUIPMENT FOR PNMS

12.1 HYB Converter

The Hybrid converter is designed to convert serial interface, RS232C, RS422 and RS485 andto 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 PNMSthrough third party equipment to convert interface and to combine or divide supervisorysignal.

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 communicationports, up to 1:6 (Maximum) combine/divide function isavailable

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.

Central Site

PNMS

Remote Cluster-A

3 41 2

Remote Cluster-B

7 8

Remote Cluster-E

5 6

Remote Cluster-C

MM

M

MM

M

M M

M : MODEM / Other Microwave Radio Equipment

2 : PASOLINK

M M : Dedicated leased line / Digital Service Channel

RS232C

19.2/9.6kbps,

Async

RS232C,9.6kbps,

Async

Provide 1:4 Divide/Combine function

: Hybrid Converter

5 6

Remote Cluster-D

M

M

RS232C,9.6kbps,

Async

Figure 12.1 Network example using HYB CONV


57/68

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 concentrateSupervisory signal from each PASOLINK (PM Card), which is scattered in differentplaces as shown Figure 12.2. The detail is also described in section 9.6.

EEEE

EEEE

RS-232 or RS485

9.6kbps

ASYNC

RS-232C

19.2kbps

ASYNC

PASOLINK CLUSTER

PASOLINK CLUSTER

R

PNMS(UNIX or

Windows NT)


9.6 kbps, ASYNC

RS232 port

(In case of other than RS232C or RS485 port,




H

Y

B

C

O

N

V

MIU

RS-4859.6kbps

ASYNC

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

Communication rate : 19.2 kbps (PPP, Asynchronous)

(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)


58/68

ROI-S04188


12.3 PNMS CABLE

Following table shows cables for PNMS connection. In accordance with customers networkconfiguration, the selection of suitable cable is required.

Cable Name How to use Pin AssignmentLCT Figure 12.4 Figure 12.5

PNMT Figure 12.6 Figure 12.7

PNMT+LCT Figure 12.8 Figure 12.9

PNMS Figure 12.10,12.11 Figure 12.12

Back to Back (Point to point)

-RS232C Figure 12.13 Figure 12.14

-RS485 Figure 12.13 Figure 12.15

Back to Back (Point to multi-point)

(1) Cascade connection Cable Figure 12.16 Figure 12.17(2) Cascade connection Cable Figure 12.16 Figure 12.18

(3) Terminal connector Figure 12.16 Figure 12.19

PNMS+Back to Back (Point to multi-point)

(1) Cascade connection Cable Figure 12.20 Figure 12.21


(3) Terminal connector Figure 12.20 Figure 12.23

HYB CONV-PASOLINK (point to point)

-RS232C Figure 12.24 Figure 12.25

-RS422 Figure 12.24 Figure 12.26HYB CONV-PASOLINK (point to multi-point)



Table 13.1 Cable List


59/68

ROI-S04188


12.3.1 LCT Cable

PASOLINK

Figure 12.4 LA port - LCT(PC) connection

LA PortNMS Port

Station A Station B

LCT

PASOLINK

Figure12.5 Pin assignment for LA port - LCT(PC) connection

15pin(M)

1

23

45

6

7

89

10

11

1213

14

15

1

23

45

6

7

89

Paso

LAConnector

CD

RDTD

DTRGND

DSR

RTS

CTSRI

PC(LCT)

LCT-TXD

GNDLCT-RXD

LCT-RTSLCT-CTS

GND

PNMT-CTS

PNMT-RTSPNMT-RXD

GND

PNMT-TXD

RS-232C1

23

45

6

7

89

10

11

1213

14

15

1

23

45

6

7

89

9 pin(F)

PC(LCT)


60/68

ROI-S04188


12.3.2 PNMT Cable

PASOLINK

Figure 12.6 LA port - PNMT(PC) connection

LA PortNMS Port

Station A Station B

PNMT

PASOLINK

15pin(M) 9 pin(F)

PC(PNMT)Paso

LA

Connector

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

LCT-TXD

GND

LCT-RXD

LCT-RTS

LCT-CTS

GND

PNMT-CTS

PNMT-RTS

PNMT-RXD

GND

PNMT-TXD

RS-232C

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(PNMT)

1

2

3

4

5

6

7

8

9

Figure 12.7 Pin assignment for LA port PNMT (PC) connection


61/68

ROI-S04188


12.3.3 PNMT + LCT Cable

PASOLINK

Figure 12.8 LA port - PNMT/LCT(PC) connection

LA PortNMS Port

Station A Station B

PNMT LCTor

PASOLINK

15pin(M) 9 pin(F)

1

2

3

4

5

6

7

89

10

11

12

13

14

15

1

2

3

4

5

6

7

89

PC(PNMT)Paso

LA

Connector

CD

RD

TD

DTR

GND

DSR

RTS

CTSRI

PC(LCT)

LCT-TXD

GND

LCT-RXD

LCT-RTS

LCT-CTS

GND

PNMT-CTS

PNMT-RTS

PNMT-RXD

GND

PNMT-TXD

RS-232C

1

2

3

4

5

6

7

89

10

11

12

13

14

15

1

2

3

4

5

6

7

89

1

2

3

4

5

6

7

8

9

CD

RD

TD

DTR

GND

DSR

RTS

CTS

RI

PC(PNMT)

1

2

3

4

5

6

7

8

9

9 pin(F)

PC(LCT)

Figure 12.9 Pin assignment for LA port PNMT/LCT (PC) connection


62/68

ROI-S04188


12.3.4 PNMS Cable

PASOLINK PASOLINK

Figure 12.10 NMS port PNMS connection

LA PortNMS Port

[RS232C]

Station A Station B

PNMS (Windows NT only)

CPM RPM

Figure 12.11 NMS port - Router connection

LA PortNMS Port

[RS232C]

Station A Station B

PNMS

In case of connection to Router, physical interface

shall be adjusted by suitable adaptor(s)

RouterLAN

15pin(M)

1

234

5

67

8

91011

12

1314

15

1

23

45

67

8

9

PC(PNMS)Paso NMSConnector

CD

RDTD

DTRGND

DSRRTS

CTS

RI

PC (PNMS)

orRouter

DEBUG-TXD

EMS-TXDEMS-RXD

EMS-RTS

EMS-CTS-GND

DEBUG-RXDNMS-TXDNMS-RXD

NMS-RTSNMS-CTS

RS-232C

1

234

5

67

8

91011

12

1314

15

1

23

45

67

8

9

9 pin(F)

Figure12.12 Pin assignment for NMS port PNMS/Router connection


63/68

ROI-S04188


12.3.5 Back to Back Cable (Point to Point)

CPM

RPM

RPM

Figure 12.13 Back-to-Back (point to point) connection

NMS Port NMS Port

RPM

15pin(M) 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

DEBUG-TXD

EMS-TXD

EMS-RXD

EMS-RTS

EMS-CTS-

GND

DEBUG-RXD

NMS-TXD

NMS-RXD

NMS-RTS

NMS-CTS

RS-232C

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

DEBUG-TXD

EMS-TXD

EMS-RXD

EMS-RTS

EMS-CTS-

GND

DEBUG-RXD

NMS-TXD

NMS-RXD

NMS-RTS

NMS-CTS

RS-232C

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Figure12.14 Pin assignment for back to back

(point to point, RS232C) connection

15pin(M) 15p in(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

EMS-TXD+

EMS-TXD-

EMS-TXDR

EMS-RXD+

EMS-RXD-

GND

NMS-TXD+

NMS-TXD-

NMS-TXDR

NMS-RXD+

NMS-RXD-

RS-485

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

EMS-TXD+

EMS-TXD-

EMS-TXDR

EMS-RXD+

EMS-RXD-

GND

NMS-TXD+

NMS-TXD-

NMS-TXDR

NMS-RXD+

NMS-RXD-

RS-485

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Figure12.15 Pin assignment for back to back

(point to point, RS485) connection


64/68

ROI-S04188


12.3.6 Back to Back Cable (Point to Multi-point)

CPM

RPM

RPM

Figure 12.16 Back to Back Cable (point to Multi-point) connection

NMS Port

[RS485]

NMS Port

[RS485]

SCPM

F M

F M

SCPM

RPM

NMS Port

[RS485]

F M

(3)Put on the Termination M at the end of connections

(1) (2) (2)

15pin(M)

15pin(F)

1

2

3

4

5

6

78

9

10

11

12

13

14

15

1

2

3

4

5

6

78

9

10

11

12

13

14

15

EMS-TXD+

EMS-TXD-

EMS-TXDR

EMS-RXD+

EMS-RXD-

GND

NMS-TXD+

NMS-T

Documents

PNMS Engineering ROI-S04188-052E (Ver.4).pdf