PNMSJ Engineering Manual (NEO) 2 PDF

Submission Prohibited ROI-S06246-051E
NEC Internal Use Only 070213
Engineering Manual
(PASOLINK NEO Version)
ATTENTION! : FOR NEC INTERNAL USE ONLY.

This document is provided for internal use. This can be issued to NEC personnel only.
Please do not provide a copy in any form to the customer.
NEC Corporation
Copyright © 2007
Submission Prohibited
NEC Internal Use Only
Copyright ©2007 by NEC Corporation
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in
any form or by any means, including electronic, mechanical, photographic, or magnetic, without prior written
permission of the publisher.
Microsoft and Windows is either registered trademark of Microsoft Corporation in the United States and other
countries. UNIX is a registered trademark of X/Open Company Ltd.
Printed in Japan.
Submission Prohibited ROI-S06246
CONTENTS
1 INTRODUCTION………………………………………………………………………………………… 1
2 SYSTEM DESIGN OVERVIEW……………………………………………………………………….. 3
2.1 GENERAL DESCRIPTION AND NETWORK DESIGN CONCEPTS…………………………………….. 3
2.2 NETWORK ARCHITECTURE…………………………………………………………………………... 4
2.3 CTRL MODULE FUNCTION…………………………………………………………………………… 5
2.4 NETCONFIGTOOL V.S. AUTO-DISCOVERY.................................................................................7
3 SYSTEM COMPONENTS………………………………………………………………………………. 7
3.1 PNMSI SERVER………………………………………………………………………………………. 7
3.2 PASOLINK NEO NETWORK ELEMENT…………………………………………………………… 7
3.3 PNMTJ MOBILE TERMINAL…………………………………………………………………………. 7
4 PASOLINK NEO INTERFACE………………………………………………………………………… 8
5 PASOLINK NEO NMS NETWORK DESIGN……………………………………………………… 9
5.1 PNMSJ SERVER SIZING……………………………………………………………………………. 9
5.2 PASOLINK NEO SIZING AND TOPOLOGY……………………………………………………….. 10
5.3 TYPES OF CONFIGURATION & IP ADDRESSING…………………………………………………...11
5.4 DCN REQUIREMENTS……………………………………………………………………………… 14
6 INTEROPERABILITY WITH EXISTING PASOLINK EQUIPMENT…………………………. 16
6.1 PASOLINK NEO (SERIAL INTERFACE) & PASOLINK (V3/V4)............................................16
6.2 PASOLINK (V4/V3) & PASOLINK NEO (SERIAL INTERFACE)............................................17
6.3 PASOLINK NEO (LAN INTERFACE) & PASOLINK+/ MX SERIES…………………………… 18
6.4 PASOLINK NEO (SERIAL INTERFACE) & PASOLINK+/ MX................................................ 19
6.5 PASOLINK+ /MX (LAN INTERFACE) & PASOLINK NEO……………………………………..20
6.6 PASOLINK+ / MX(SERIAL INTERFACE) & PASOLINK NEO................................................ 21
7 PNMSJ REDUNDANCY………………………………………………………………………………. 22
7.1 PARALLEL PNMSJ………………………………………………………………………………….. 22
8 CASE STUDY (SAMPLE NETWORK DESIGN, PLANNING AND IMPLEMENTATION).. 24
9 NETWORK CONFIGURATION SAMPLE…………………………………………………………. 25
9.1 NETWORK CONFIGURATION FOR ONE SUBNET………………………………………………….. 25
9.2 NETWORK CONFIGURATION WITH TWO BRANCHES……………………………………………... 26
9.3 NETWORK CONFIGURATION WITH MULTI BRANCHES……………………………………………28
10 CASE STUDY: ADDING NEO TO PASOLINK/PASOLINK+ NETWORK…………………. 30
10.1 EXAMPLE: ADD NEW HOP…………………………………………………………………………. 30
APPENDIX - A: CABLE DIAGRAMS…………………………………………………………………….. 32
A.1 PNMT/LCT CABLE…………………………………………………………………………………. 32
A.2 PNMS CABLE LAN INTERFACE…………………………………………………………………… 33
A.3 PASOLINK NEO & PASOLINK (V3/V4)………………………………………………………..34
A.4 PASOLINK NEO & PASOLINK………………………………………………………………….35
A.5 PASOLINK NEO & PASOLINK………………………………………………………………….36
A.6 PASOLINK NEO & PASOLINK+/MX…………………………………………………………… 37
A.7 PASOLINK+/MX & PASOLINK NEO…………………………………………………………… 38
A.8 PASOLINK NEO & MIU(HOP) OR MIU (LINE CONCENTRATOR)……………………….. 39
A.9 MIU (HOP) & PASOLINK NEO POINT TO MULTIPOINT CONNECTION……………….40
A.10 MIU (HOP) & PASOLINK NEO(POINT TO MULTIPOINT CONTINUE)…………………… 41
APPENDIX-B (WINDOWS)………………………………………………………………………………... 42
APPENDIX-C (UNIX)………………………………………………………………………………………... 43
APPENDIX-D(NOT SUPPORTED FUNCTION)…………………………………………………………44
-i-
1 INTRODUCTION
I. SCOPE and LIMITATION
This document is developed mainly to serve as a guideline to PASOLINK NEO NMS network design
and implementation. It will cover in detail all aspects of the PASOLINK NEO equipment related to
building the NMS network from the ground up. It will cover all aspects of the NMS which includes
system architecture, IP addressing, interconnectivity with other equipments in the network and
cabling requirements for the PASOLINK NEO equipment.
This document will not cover the basics of IP addressing, SNMP and other common protocol and
interfaces mentioned in the manual.
II. INTENDED AUDIENCE

This document is intended for network administrator/engineers, planning and field engineers. It is
recommended that the reader have prior knowledgeable of the common NMS architecture, protocols
and interfaces. This document will not explain in detail about common NMS protocols and interfaces
and assumes that the reader has prior knowledge about those subjects.
III. ACCRONYMS AND DEFINITIONS

The following definitions and acronyms are used in this document:
Ack Acknowledgement
AIS Alarm Indication Signal
APC Automatic phase Control
AUX Auxiliary
ASYNC Asynchronous
BER Bit Error Rate
BSC Base Switching Center
BTS Base Terminal Station
CTRL Control
DCN Digital Communication Network
DEM Demodulator
CONV Converter
CPM Central PM Card
DSC Digital Service Channel
GNE Gateway Network Element
HDLC High Level Data Link Control procedure
HYB Hybrid
IDU Indoor Unit
INTFC Interface
I/O Input/Output
IP Internet Protocol
LAN Local Area Network
LCT Local Craft Terminal
MDP Modulator/Demodulator Equipment
MIB Management Information Base
MIU Management Interface Unit
MSC Mobile Switching Center
MUX Multiplexer
-1-
NE Network Element
NRM Normal Response Mode
ODU Outdoor Unit
OW Order wire
PMC PASOLINK Management Card
PNMS PASOLINK Network Management System
PNMT PASOLINK Network Management Terminal
PPP Point to Point Protocol
PS Power Supply
RPM Remote PM Card
TX Receive
SCPM Sub-Central PM Card
SNMP Simple Network Management protocol
SV Supervisory
TFTP Trivial File Transfer Protocol
TMN Telecommunications Management Network
TX Transmit
SC Service Channel
SV Supervisory
SW Switch
UDP User Datagram Protocol
WS Wayside
IV. REVISIONS
The functions described in this based is based on the following versions:
Refer to Appendix-D regarding for not currently supported function.
SOFTWARE VERSION NUMBER

PNMSj software 1.05.007
PNMTj 1.05.007
NetCfgToolj 1.01.027
NEO CTRL software 1.04.05/2.03(XPIC)
V. REFERENCES
It is recommended to read the following references for detailed explanation of other NEC radio
equipment DCN engineering:
DOCUMENT NUMBER TITLE

ROI-S04188-053E PASOLINK Engineering Manual
ROI-S04406-054E PASOLINK + Engineering Manual
ROI-S05909-055E PNMTj Operation Manual
ROI-S06104-051E PNMSj Operation Manual
ROI-S06070-051E Net ConfigTool java Operation Manual
-2-
2 SYSTEM DESIGN OVERVIEW
2.1 General Description and Network Design Concepts
TCP/IP network is utilized by the PNMSj for communication with the NE and remote clients. PNMSj
to remote client communication relies on IP (LAN or WAN) network to be able to provide remote
operations to users. HTTP and Java RMI allows the users to manage the PASOLINK NEO equipment
from a remote client connected to the PNMSj server. This is illustrated in the figure below.
PNMSj to NE communication is also carried over the IP network. NE(s) are grouped in clusters where
one NE is designated as the Gateway Network Element (GNE). The GNE has a direct connection to
the Data Communication Network (DCN) and provides gateway functions and routing to the other
NE(s) _ in the cluster. The DCN, usually an IP –network, provides the connectivity between the
GNE and the PNMSj. The NE(s) in the cluster then depends on the GNE for communication with the
PNMSj. In the PASOLINK NEO network GNE is also called s “Root-NE”. GNE and/or Root-NE is
used interchangeably throughout this document to mean the same thing.
A typical PNMSj network would be comprised of at least one GNE. Large PNMSj network would
normally be comprised of many clusters and hence many GNE(s).
PNMSj and NE(s) use Simple Network Management Protocol (SNMP v1) for operations and
management. The PNMSj is the SNMP manager and the NE(s) are the SNMP agents. Each of the
NEO NE(s) are equipped with a CTRL module that contains an SNMP agent that allows it to send
alarm and status events to the PNMSj and to interpret and execute control commands.
-3-
2.2 Network Architecture
The PNMSj network architecture is illustrated in Figure 2.2 below.
The Remote Client to PNMSj communication uses HTTP and Java™ RMI over TCP/UDP/IP layers.
Remote clients normally running on Windows® PC utilizes Giga/Fast/Ethernet network interface. The
PNMSj server also support Giga/Fast/Ethernet network interface to provide web-based GUI to the
remote client for the operations and management of the NE(s).
PNMSj to GNE (Root-NE) communication uses SNMPv1 and TFTP over UDP/IP layers. SNMP is
used to send/query/receive information between the manager (PNMSj server) and the agent (GNE).
The PASOLINK NEO GNE is equipped with a LAN-interface (10BaseT) for direct connection to the
DCN.
NE to NE communication is either carried over the radio (384kbps) or through direct LAN-LAN
connection between the NE(s). NE(s) in the cluster relies on the GNE at the root of each cluster to
provide them routing and gateway functions to the PNMSj server.
-4-
2.3 Ctrl Module Function
Each PASOLINK NEO NE is equipped with a CTRL module which is contains all the management
functions of the NE. The CTRL module contains the SNMP agent, MIB and software for handling its
own alarms and collecting statistical data. It is also responsible for routing traffic and providing
gateway functions depending on its position in the cluster.
The hardware of the CTRL module is the same for all NEO NE(s), however, they can be configured to
provide different roles in the cluster. The CTRL module can be configured as:
(1) Root NE (Gateway NE):

This means that this NE has direct access to the DCN and will provide the gateway and routing
functions for the other NE(s) in the cluster. The Root NE will route tandem traffic –intended for other
NE(s) in the cluster. It will also provide remote access to the NE(s) in the cluster via the DCN. This
means that the NE configured as Root NE will provide the connectivity between the NMS and other
NE(s) in the cluster. Aside from this, the Root NE will also have to monitor and handle its own alarms
and monitored items and send SNMP traps to alert the NMS of changes in alarm status. Moreover, it
has to collect its own statistical data such as Link Performance data.
(2) Root NE (Bridge):

Root NE(Bridge) is the gateway functions like Root NE between PNMSj and Branch NEs/Normal
NEs. In network configuration where the subnet is not supposed to be disconnected at the Root
NE.This means that one IP address is assigned to Root NE(Bridge) and subnet is not divided.
(3) Branch NE (Intermediate NE):

This is the NE(s) that is located in between the cluster and has no direct access to the DCN. This NE
will route tandem traffic to other NE(s) on its sub network. Like other NE(s) it will also have to
monitor its own alarm items and status and collect statistical data such as Link Performance data.
(4) Normal NE:

Normal NE is a data acquisition and control unit. It monitors and controls equipment at some remote
location. Its prime task is to monitor its own alarm items and status and collect statistical data such as
Link Performance data
-5-
2.4 NetConfigTool v.s. Auto-Discovery
The PASOLINK NEO NMS network can be created and implemented in 2 possible ways:
1) NetCfgTool – this is a legacy network configuration tool supplied by NEC. Using this tool, the
network designer can create the NMS configuration in the offline tool and then create the
configuration files to each NE and the DAT/NCT file for the PNMSj. The NE configuration files
are then downloaded to the individual NE(s) and the DAT/NCT file is imported in the PNMSj
server. The PNMSj and NE can then establish the communications between them based on the
configuration files and the DAT/NCT file. In case of modifications on the PASOLINK NEO
network such as addition of new NE or removal of existing NE, the network designer has to
modify the existing network using the network configuration tool.
2) Auto-Discovery- the NE NMS configuration is done by entering the IP setting of the NE using the
PNMTj. Then after the IP setting and cabling, the PNMSj can be programmed to search and look
for new NE or new Root-NE(s) automatically. New NE(s) added to existing cluster will be
discovered automatically by the NMS. New Root-NE(s) is discovered by programming the IP
address of the Root-NE to the PNMSj during the Auto-Discovery execution.
NOTE: Auto-Discovery function in the PNMSj is only available for the PASOLINK NEO equipment.
In case earlier generation of equipment is mixed with the PASOLINK NEO in the same cluster,
NetCfgTool should be used.
-6-
3 SYSTEM COMPONENTS
The PASOLINK NEO NMS network is composed of 3 key components to work. These are: (1)
PNMSj server, (2) PASOLINK NEO Network Element, (3) and PNMTj
3.1 PNMSi Server

The PNMSj server is located at the Network Operations Center (NOC). The PNMSj provides fault,
configuration, performance, and security management of the PASOLINK NEO equipment. It also
provides remote client connections using web server service (IIS for Windows® or Apache™ for
Solaris). PNMSj can provide operations and management for up to 10,000 NE(s) and up to 15
concurrent remote client connections.
The PNMSj uses SNMP to control and monitor NE(s) and TFTP to remotely download configuration
files or software update to the NE. PASOLINK NEO NE(s) can be added, removed or modified in
either auto-discovery or NCT mode.
PNMSj can be installed in Windows® 2000 or XP Professional or in Sun Solaris®9.
3.2 PASOLINK NEO Network Element

CTRL module is incorporated in the PASOLINK NEO series. CTRL module is built-in in every
PASOLINK NEO series equipment to monitor alarm and status and to control it from the central site
with the PNMSj. The CTRL module’s primary tasks are to control and acquire data of the PASOLINK
NEO series equipment at remote location and transfer this data back to the central site (NOC).
CTRL module in the IDU has an SNMP agent, which detects alarm and status changes in the
equipment and sends traps to notify network management system.
In addition, the CTRL module has the MIB data and can respond to SNMP “GET commands” from
PNMS / PNMT.
3.3 PNMTj Mobile Terminal

The PASOLINK Network Management Terminal software runs on laptop PC is used to connect to
PASOLINK NEO via the “Pnmt” port for on-site maintenance purposes. By default it can connect to
individual NE and its opposite NE. However, it can also be used to monitors other NE(s) in the
network (cluster). It means that PNMTj user can make connections to remote NE from any node
within a PASOLINK NEO cluster. Moreover, the PNMTj can also be used over IP-network to allow
remote connection to a particular hop in the network.
Note that the PNMTj is an optional component of the PASOLINK equipment.
-7-
4 PASOLINK NEO INTERFACE
-8-
5 PASOLINK NEO NMS NETWORK DESIGN
The NMS network design for the PASOLINK NEO can be summarized into 3 categories: (1) PNMSj
sever sizing, (2) PASOLINK NEO network cluster size and topology, and (3) DCN requirement
between PASOLINK NEO GNE (Root-NE) and PNMSj.
5.1 PNMSj Server Sizing

The recommended PNMSj server hardware specification depends on intended number of managed
NE(s) and the number of remote clients that will be connecting to the server.
For the PNMSj sever: recommended hardware specification
Please see the Appendix-B & Appendix-C
-9-
5.2 PASOLINK NEO Sizing and Topology
Figure 5.2 below illustrates the PASOLINK NEO network topology and sizing.
The following network sizing restriction is applied when NEC PASOLINK NEO series supervisory
network hierarchy is configured
Table 5-1: Recommended PASOLINK Network Sizing

Network Elements allowed
Number of Regions for 1 Central PNMSj server 50
Number of Network Clusters in 1 PNMSj server 500
Number of NE(s) in 1 Network Cluster 500
Number of NE(s) in 1 Subnet** 61 (Maximum)**
Number of NE(s) in Multidrop Connection 32
** Maximum number of NE(s) in one (1) sub-network depends on subnet mask assigned. The
relationship between the subnet mask and number of NE is described in the table below:
Table 5-2: Subnet Assignment

Subnet Mask Subnet Size Available IP addresses Number of NE(s)
255.255.255.252 4 2 1
255.255.255.248 8 6 5
255.255.255.240 16 14 13
255.255.255.224 32 30 29
255.255.255.192 64 62 61
- 10 -
5.3 Types of Configuration & IP Addressing
5.3.1 PASOLINK NEO & PASOLINK NEO (LAN Interface)
PNMSj
~ ~
IP R NEO NEO NEO NEO

Figure 5.2.1/1
Figure 5.2.1/1 shows simple Point to Point connection between PASOLINK NEO where the Gateway
NE or Root NE directly connected to the DCN (IP network) .The NMS port of Root NE is directly
connected to the IP network and must have proper routing established in the DCN to ensure the
connection. The Physical interface between PNMS and Root NE is LAN interface. The NE-NE
connection is either through the NEO SC (radio) or through back-to-back cable (NE to NE port).
NOTE.
•Cross Cable connection is needed for all NE-NE Back to Back connection
•Ethernet HUB is not supported in this time
IP Addressing Summary (LAN Interface)

PNMSj
IP 172.18.14.4
IP 172.18.14.2
N
~ LA ~

Subnet A
Subnetmask
255.255.255.192
IP 172.18.14.3
IP 172.18.14.1
Figure 5.2.1/2
Operator can set subnet mask according to number of NE. The Root NE PNMS port IP address acts as
the gateway to its PASOLINK NEO series cluster. For example, Root NE passes an IP packet from
PNMS thru172.18.14.1 to the destination NE.
For reference, recommended available IP address and subnet mask as follows:
Subnet B Subnetmask: 255.255.255.192

Available IP address: (172.18.14.1 Æ62)
Network IP address: 172.18.14.0
Broadcast IP address: 172.18.14.63
- 11 -
5.3.2 Multi Connections
PNMSj
~ ~
~ ~
B NEO NEO NEO NEO
Figure 5.2.2/1
Figure5.2.3/1 shows multi connection of PASOLINK NEO where Root NE NMS port and PNMS are
located in same subnet mask. The NE(s) are connected back to back by port NE to NE. By making a
new Branch where shows another subnet .The physical interface condition of PASOLINK NEO is
LAN.
NOTE.
•Cross Cable connection is needed for all NE-NE Back to Back connection
•Ethernet HUB is not supported in this time
IP Addressing of PASOLINK NEO

PNMSj
IP 172.18.16.1 IP 172.18.16.2 IP 172.18.16.3 IP 172.18.16.4
~ Subnet A ~
Subnetmask
255.255.255.192
Subnet B
~ Subnetmask
~
255.255.255.192
B NEO NEO NEO NEO
IP 172.18.16.5 IP 172.18.16.65 IP 172.18.16.66

IP 172.18.16.67
IP 172.18.16.68
Figure 5.2.2/2
Operator can set subnet mask according to number of NE.

For reference, recommended available IP address and subnet mask as follows:
- 12 -
5.3.3 Root NE (Bridge) Connection:
Figure 5.3.3/1 shows connection between PASOLINK NEO & Root NE(Bridge) where PNMS is
connected to Root NE(Bridge) via Router.
For reference, recommended IP address, subnetmask as follows:
- 13 -
5.4 DCN Requirements
The DCN between the PNMSj and the NE is also an important aspect that must be given attention
during the design and implementation of the PASOLINK NEO NMS network. A typical DCN
implementation may be a combination of different transport technologies. It can be either a shared
DCN or a dedicated DCN.
Figure 5 below illustrates a typical DCN implementation.
The NE access network for is typically LAN (Ethernet). The PASOLINK NEO GNE (Root-NE) has a
built in 10BaseT LAN-Ethernet NMS port that allows it to directly connect to existing LAN
equipment such as switch or hub. It should be able to handle routing and should allow SNMP and
TFTP traffic. Dial-up and DSC can also be provided, but the bandwidth must be at least 384kbps.
Performance maybe degraded if a smaller pipe is provided.
The DCN backbone is cloud, is normally comprised of one or more DCN technologies. It can be the
customers WAN/MAN or it can also be a dedicated DSC or leased line connecting the NE access
network to the NMS access network. The DCN must be able to provide sufficient bandwidth to
carry the traffic between the NE access network and the NMS access network. It should also be able
to handle routing between the networks.
The NMS access network is typically an LAN. The PNMSj server platform supports Ethernet, Fast
Ethernet or Giga bit Ethernet connections (supported by OS). It has to be able to handle routing and
also should not filter SNMP and TFTP traffic.
The recommended bandwidth between the PNMSj server and the PASOLINK NEO network cluster is
shown in Figure 5.3.2 below.
- 14 -
Figure 5.4.2: BANDWIDTH CONSIDERATIONS
PNMSj NEO NETWORK CLUSTER
GNE
A
A––384 kbps (minimum bandwidth utilized by the cluster)
- 15 -
6 INTEROPERABILITY WITH EXISTING PASOLINK EQUIPMENT
6.1 PASOLINK NEO (Serial Interface) & PASOLINK (V3/V4)
PNMSj
~ ~
IP R NEO B NEO C V4 V4
Figure 7.1.1
Figure 7.1.1.shows connection that PASOLINK NEO and PASOLINK V4 are connected with point to
point connection. PNMSj is connected direct to PASOLINK NEO (Root NE) and PASOLINK V4 line
follows at remote site. The end of PASOLINK NEO line is assigned to Branch and the head NE in
PASOLINK V4 line is assigned to CPM NE.
The SC (Async RS-485) port of PASOLINK NEO is connected to PASOLINK V4 NMS port. * Not
Possible to useRS232C
IP Addressing summary (Serial Interface)

PNMSj
IP 172.18.0.66
IP172.18.0.2
~ Async ~
IP R NEO B NEO C V4 V4
Subnet A Subnet B
Subnetmask Subnetmask
255.255.255.192 255.255.255.240
IP 172.18.0.1
Figure 7.1.1a IP 172.18.0.65
The Root NE IP address acts as the gateway to its network. Figure 7.1.4a shows IP addressing. For
example, Root NE passes an IP packet from PNMS thru 172.18.0.65 to the destination NE.
For reference, recommended available IP address and subnet mask as follows.
- 16 -
6.2 PASOLINK (V4/V3) & PASOLINK NEO (Serial Interface)
PNMSj
~ ~
IP CV4 SV4 B NEO NEO
Figure7.2.1
Figure 7.2.1 show connection that PASOLINK V4 and PASOLINK NEO are connected by point to
point connection. PNMSj is connected direct to PASOLINK V4 (CPM NE) and PASOLINK NEO
line follows at remote site. The end of PASOLINK V4 line is assigned to SCPM and the head NE in
PASOLINK NEO line is assigned to Branch NE. The NMS port of V4 SCPM NE is connected to SC
(Async RS-485) port of PASOLINK NEO Branch NE.
IP Addressing summary (Serial Interface)

PNMSj
IP 172.18.4.17
IP 172.18.4.66
IP172.18.4.18
~ Async ~
IP C V4 S V4 B NEO NEO
Subnet A Subnet B
255.255.255.240 255.255.255.192
IP 172.18.4.1
IP 172.18.4.65
Figure7.2.1a
Subnet B is a sub network under PASOLINK NEO Branch. Therefore the subnet mask is
255.255.255.192.For reference, recommended available IP address and subnet mask as follows:
- 17 -
6.3 PASOLINK NEO (LAN Interface) & PASOLINK+/ Mx Series
PNMSj
~ ~
IP R NEO B NEO BPASO+ PASO+
Figureb7.3.1
Figure 7.3.1shows connection that PASOLINK NEO and PASOLINK+ are connected with point to
point connection. PNMSj is connected direct to PASOLINK NEO (Root NE) and PASOLINK+ line
follows at remote site. The end of PASOLINK NEO line is assigned to Branch and the head NE in
PASOLINK+ line is assigned to Branch NE.
The NE port of PASOLINK NEO is connected to PASOLINK+ LAN (RJ-45) port.

PNMSj
IP172.18.6.2
N IP 172.18.6.66
~ LA ~
IP R NEO B NEO B Paso+ Paso+

Subnet A Subnet B
255.255.255.192 255.255.255.240
IP 172.18.6.1
IP 172.18.6.65
Figure7.3.1a
Operator can set subnet mask according to number of NE.

Here, Subnet A is a sub network under PASOLINK NEO Branch.
Therefore the subnet mask is 255.255.255.192
- 18 -
6.4 PASOLINK NEO (Serial Interface) & PASOLINK+/ Mx
PNMSj
~ ~
IP R NEO B NEO BPASO+ PASO+
Figure7.4.1
Figure 7.4.1.shows connection that PASOLINK NEO and PASOLINK+ are connected by point to
point. PNMSj is connected direct to PASOLINK NEO (Root NE) and PASOLINK+ line follows at
remote site. The end of PASOLINK NEO line is assigned to Branch and the head NE in PASOLINK+
line is assigned to Branch NE.
The SC (Async RS485) port of PASOLINK NEO is connected to PASOLINK+ NE1 (RJ-45) port.
IP Addressing Summary (Serial Interface)
PNMSj
IP 172.18.4.66
IP172.18.4.2
~ Async ~
IP R NEO B NEO B Paso+ Paso+

Subnet A Subnet B
255.255.255.192 255.255.255.240
IP 172.18.4.1
IP 172.18.4.65
Figure7.4.1a
Subnet B is a sub network under PASOLINK NEO Branch.

For reference recommended available IP address and subnet mask as follows.
- 19 -
6.5 PASOLINK+ /Mx (LAN Interface) & PASOLINK NEO
PNMSj
~ ~
IP R PASO+ B PASO+ B NEO NEO
Figure 7.5.1
Figure 7.5.1shows point to point connection of PASOLINK+ and PASOLINK NEO. PNMSj is
connected to PASOLINK+ (Root NE) and PASOLINK NEO line follows at remote site. The interface
between PASOLINK+ and PNMS is LAN. The end of PASOLINK+ line is assigned to Branch NE and
the head NE in PASOLINK NEO line is also assigned to Branch NE. The NE 2port of Pasolink+
Branch is connected with NE Port of NEO Branch NE.
PNMSj
IP 172.18.12.66
IP172.18.12.2
N
LA
~ ~
IP R PASO+ BPASO+ B NEO NEO

Subnet B
Subnet A
Subnetmask
Subnetmask
255.255.255.192
255.255.255.240
IP 172.18.12.1
IP 172.18.12.65
Figure7.5.1a
Operator can set subnet mask according to the number of NE in each sub network.
Here, Subnet B is a sub network under PASOLINK NEO Branch.
For reference, recommended IP address, available IP address and subnet mask as follows.
- 20 -
6.6 PASOLINK+ / Mx(Serial Interface) & PASOLINK NEO
PNMSj
~ ~
IP R PASO+ B PASO+ B NEO NEO
Figure 7.6.1
Figure.7.6.1shows point to point connection of PASOLINK+ and PASOLINK NEO. PNMSj is

connected to PASOLINK+ (Root NE) and PASOLINK NEO line follows at remote site. The interface
between PASOLINK+ and PNMS is Async. The end of PASOLINK+ line is assigned to Branch NE
and the head NE in PASOLINK NEO line is also assigned to Branch NE. The NE2 port of Pasolink+
Branch is connected with SC (IN/OUT) Port of NEO Branch NE.
IP Addressing Summary (Serial Interface)
PNMSj
IP 172.18.10.66
IP172.18.10.2
~ Async ~
IP R PASO+ BPASO+ B NEO NEO

Subnet A Subnet B
255.255.255.240 255.255.255.192
IP 172.18.10.1
IP 172.18.10.65
Figure7.6.1a
Operator can set subnet mask according to the number of NE in each sub network.
Here, Subnet B is a sub network under PASOLINK NEO Branch.
- 21 -
7 PNMSj REDUNDANCY
The PNMSj system offers “parallel” system for redundancy. These are two independent PNMSj
servers in the network than manages the same set of NE(s).
7.1 Parallel PNMSj

Two PNMSj can monitor and control PASOLINK NEO network simultaneously and independently.
These are connected to Root NE through Router, as shown Figure 8.1. This configuration is called
Parallel PNMSj ”Parallel" means that status change (ex. Alarm and event occurrence) of each NE is
recognized in both PNMSj. Even if the one PNMSj is down, the other PNMS can monitor and control
NEs in the network. However, there is case that logging data and performance monitor data are not
synchronized between the PNMSj-1 and PNMSj-2, i.e., such data is not stored into both PNMSjs.
For example, assuming that PNMS-1 is in operation and PNMS-2 is down
a) Logging data
If alarms occur in PASOLINK NEO network, the alarm log is registered in PNMSj-1. However these
logs are not registered in PNMSj-2. After PNMSj-2 is re-started, the logging data is not synchronized
between PNMSj-1 and PNMSj-2. In this case Operator is required to download the logging data from
PNMSj-1and to upload it to PNMSj-2 desired directory and re-start PNMS-2, if the operator wants to
synchronize the logging data of both PNMSj.
b) Performance monitors data

PNMSj collects performance data stored in each NE in the network once a day. (Collecting time can
be set by Operator.) If PNMSj-1 collects performance data of NEs in the network, PNMSj-1 stores
performance data of the day. However, PNMSj-2 does not store the performance data. Therefore, after
PNMSj-2 is re-started, the performance data is not synchronized between PNMSj-1 and PNMSj-2. In
this case Operator is required to download the performance data from PNMSj-1 and upload it to
PNMSj-2 desired directory and re-start PNMSj-2, if Operator wants to synchronize the performance
data of both PNMSjs
- 22 -
c) Network configuration data
In addition, the network configuration data can be created from either Network Configuration tool
(PNMSj) and is not automatically transferred to another PNMSj regardless whether PNMSj is in
operation or down. Therefore, in order to synchronize such data between PNMSjs, whenever such
data is created or changed from one PNMSj, Operator shall remake such data in another PNMSj to be
identical to those in one PNMSj accordingly.
Network Operation Center-1
PNM S-1
Alarm or Event Trap
LAN
Alarm or Event Trap
Custom er IP network
LAN
: ROUTER
PNM S-2
Regional Network Operation Center-2 : PASOLINK NEO
Figure 8.1 Parallel PNMS
- 23 -
8 CASE STUDY
(Sample Network Design, Planning and Implementation)
The Auto Discovery function in PASOLINK NEO series is supported for simplifying network
connection. It allows the PNMSj to identify and register PASOLINK NEO equipment under a specific
Root NE.
To use Auto Discovery you need to do the following:
1) Make sure that in cluster you have only PASOLINK NEO equipments.
2) Existing PASOLINK/PASOLINK+ equipment does not support Auto-discover function and
therefore must use NetCfgTool instead. If a Pasolink NEO is connected downstream to a
PASOLINK/PASOLINK+ GNE (CPM or Root NE), Auto-discovery is not possible.
3) IP network setting (IP Address, subnet mask, default gateway etc.) should be configured to each
NE on-site using PNMTj. (Refer to the Network Settings section for PNMTj operation manual).
4) Run “Find NE” function in the PNMSj. (Refer to PNMSj operation manual). For new clusters, the
IP address of the Root-NE (GNE) must be supplied to the PNMSj to enable it to discover the new
cluster.
Note: To connect PASOLINK NEO with existing equipment need to

create Net Configuration file, refer to section 11
- 24 -
9 NETWORK CONFIGURATION SAMPLE
9.1 Network Configuration for One Subnet
Network Configuration for one subnet
The above figure shows the connection between PASOLINK NEO where head of the PASOLINK
NEO is assigned to Root NE(The nearest NE to PNMS configure as Root NE).The NMS port of Root
NE is connected to PNMS and the NE(s) are connected Back to Back by NE to NE port.
In PASOLINK NEO equipment setting, must need to connect PNMTj to each NE to edit Network
information (i.e. IP address, subnet mask and default Gateway).Here the Root NE and Normal NE(s)
are located in one sub network. The Root NE IP address acts as a Gateway to its network.
To edit the Network information refers to the Table as below:
General (Category)
NE CTRL Branch NE Category Item Name Input data
Type Type
IP Address 172.18.0.1
Radio/EM2
Subnet Mask 255.255.255.192
Not IP Address 192.168.0.10
No.01 Root NE PNMS(EM1)
selectable Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1
Routing
Static Routing Table -
Radio/EM1/EM2
Not Subnet Mask 255.255.255.192
No.02 Normal NE
selectable Default Gateway 192.168.0.1
Routing
Radio/EM1/EM2
No.03 Normal NE
Routing
Radio/EM1/EM2
No.04 Normal NE
Routing
- 25 -
9.2 Network Configuration with Two Branches
Figure shows the connection among PASOLINK NEO where head of the PASOLINK NEO is
assigned to Root NE and connected to PNMS. Here NE (No.2) and NE (No.3) is connected Back to
Back by NE-NE port. Connect the PNMTj to each NE to edit network information.
Here the NE (No.3) assigned as Branch NE. The Root NE IP address (172.18.0.1) acts as Gateway to
the network and passes an IP packet from PNMS to NE (No.03) through routing IP 172.18.0.64 under
one cluster.
- 26 -
For editing the Network information refer to the Table as below:
General (Category)
NE CTRL Branch Category Item Name Input data
Type NE Type
Radio/EM2
Subnet Mask 255.255.255.192
IP Address 192.168.0.10
Not PNMS(EM1)
No.01 Root NE Subnet Mask 255.255.255.0
selectable
Routing IP Address 172.18.0.64
Static Routing
Subnet Mask 255.255.255.192
Table
Radio/EM1/EM2
Subnet Mask 255.255.255.192
Normal Not
No.02 Default Gateway 192.168.0.1
NE selectable
Routing Static Routing
-
Table
Radio
Subnet Mask 255.255.255.192
Branch EM1/EM2
No.03 2 Branches Subnet Mask 255.255.255.192
NE
-
Table
Radio/EM1/EM2
Subnet Mask 255.255.255.192
Normal Not
NE selectable
-
Table
- 27 -
9.3 Network Configuration with Multi Branches
Here Root NE IP address acts as the Gateway to its network. The Root NE IP address (172.18.0.1)
passes an IP packet from PNMS to NE (No.03) through routing IP172.18.0.64 and to NE (No.05)
through routing IP172.18.0.128.
- 28 -
To edit the Network information refers to the Table as below:
General (Category)
NE CTRL Branch NE Category Item Name Input data
Type Type
Radio/EM2
Subnet Mask 255.255.255.192
IP Address 192.168.0.10
PNMS(EM1)
Subnet Mask 255.255.255.0
Not Default Gateway 192.168.0.1
No.01 Root NE IP Address 172.18.0.64
selectable
Subnet Mask 255.255.255.192
Routing Static Routing Default Gateway 172.18.0.3
Table IP Address 172.18.0.128
Subnet Mask 255.255.255.192
Radio/EM1/EM2
Subnet Mask 255.255.255.192
Normal Not
NE selectable
-
Table
Radio
Subnet Mask 255.255.255.192
EM1
Subnet Mask 255.255.255.192
Branch
No.03 3 Branches IP Address 172.18.0.129
NE EM2
Subnet Mask 255.255.255.192
-
Table
Radio/EM1/EM2
Subnet Mask 255.255.255.192
Normal Not
NE selectable
-
Table
NOTE: In IDU front side there is only two ports for NE’s connection. NMS port and NE port (see
PASOLINK NEO Interface chapter 4, page.14).PNMTj manual and Net configuration
Tool shows NMS port as EM1 and NE port as EM2 .To avoid this confusion, please see this table:
IDU PORT NAME REMARKS
NMS Referred to as EMI in PNMTj manual and Net Configuration Tool
NE Referred to as EM2 in PNMTj and Net Configuration Tool
SC(IN/OUT) Referred to use as Async connection
LCT Referred to use for PNMTj connection
- 29 -
10 CASE STUDY:
ADDING NEO TO PASOLINK/PASOLINK+ NETWORK
The following section shows an example on configuration work needed when adding NEO NE to an
existing PASOLINK/PASOLINK+ network. In this case, Auto-Discovery cannot be used, so the
configuration must be done using NetCfgTool.
For detailed cabling schemes please refer to Chapter 7.
10.1 Example: Add New HOP
Subnet-4 New Hop
Subnet-5
Subnet-1
Subnet-2
Subnet-3
: CPM(Root NE)
: SCPM(Branch NE)
: RPM(Normal NE)
R : Router
: Radio Connection
: Cable Connection
Figure 11.1 Network Example
Example: add New Sub network
Subnet-4
Subnet-5
Subnet-1
New Subnet
Subnet-2
Subnet-3
: CPM(Root NE)
: SCPM(Branch NE)
: RPM(Normal NE)
R : Router
: Radio Connection
: Cable Connection
Figure 11.2Network Example
- 30 -
1) Create configuration file for new NEs by “Network Configuration tool”.
2) Export configuration file for each NE (PM card) to desired directory according to “Network
Configuration tool”.
3) Copy the *nct files for each NE from PC (used for Network Configuration Tool) to PNMTj and
download them to new NE using PNMTj and install new NE IDU on site.
Note: For PNMSj(UNIX)--Upload the Netconfig Tool *NCT files to PNMSj

WorkStation (or Server) by FTP from PC (used for Network Configuration tool) and
import it to PNMSj.
4) Download modified configuration file to the existing NE, (Master NE (CPM (Root NE) which
new sub network is belonging and all SCPMs(Branch NE) in the CPM cluster and a NE which
connecting new HOP physically) from PNMSj. (Downloading from PNMTj is also available. In
this case copy the configuration files for each NE from PNMSj PC to PNMTj is required.)
-Master NE (CPM (Root NE) and all SCPM (Branch NE) in the CPM cluster): Modify pp_network
configuration file to recognize new sub network
-Existing NE connecting new subnet physically: Modify pp_network configuration file to recognize
new HOP
-All NEs in new sub network: Modify pp_network configuration file and pp_mib configuration file
5) Update configuration file (Netcfg Tool *nct file) using “Update Network Configuration window”
on PNMSj. Then possible to monitor and control added sub network.(refer to figure 11.3)
- 31 -
Appendix - A: CABLE DIAGRAMS
A.1 PNMT/LCT Cable
Station A Station B
NEO NEO
PNMT/LCT
(USB)Port
USB Cable PNMT/LCT
Figure 12.1 PNMT/ LCT (USB)port connection
USB
- 32 -
A.2 PNMS Cable LAN Interface
Station A Station B
NEO NEO
ROOT NE
PNMS EM 1
Port(LAN)
Ethernet
HUB LAN
PNMS
Figure 12.2PNMS(LAN) port – Ethernet HUB connection
- 33 -
A.3 PASOLINK NEO & PASOLINK (V3/V4)
(Point to Point connection, AsyncRS485 PNMS is on the NEO side)
Figure.3
- 34 -
A.4 PASOLINK NEO & PASOLINK
(Multi-drop connection, AsyncRS485, PNMS is on the Pasolink side)
Figure 4
- 35 -
A.5 PASOLINK NEO & PASOLINK
(Multi-drop connection, Async RS485 PNMS is on the PASOLINK side)
Figure 5
- 36 -
A.6 PASOLINK NEO & PASOLINK+/Mx
(Multi-drop connection, AsyncRS485 PNMS is on the PASOLINK NEO side)
Figure 6
- 37 -
A.7 PASOLINK+/Mx & PASOLINK NEO
(Multi drop connection, Async RS485,PNMS is on the PASOLINK+side)
- 38 -
A.8 PASOLINK NEO & MIU(HOP) or MIU (Line Concentrator)
Figure 8
- 39 -
A.9 MIU (HOP) & PASOLINK NEO Point to Multipoint connection
(PNMS is on the MIU side)
Figure 9
- 40 -
A.10 MIU (HOP) & PASOLINK NEO(Point to Multipoint Continue)
Figure 10
- 41 -
Appendix-B (Windows)
The minimum hardware and software requirements of PNMSj (Windows) are shown in the table
below.
Type of PNMS Stand-alone/Regional/Central
Number of client 0 5 10 15
Manageable NEs 50 1000 4000 8000 1000 6000 1000 6000 1000 6000
- - - - - - - - - -
500 3000 7000 10000 5000 10000 5000 10000 5000 10000
®
CPU Pentium 4 or equivalent
(GHz) 2.2 2.4 2.6 2.8 3.2 3.4 3.4 3.6 3.6 3.6
or or or or or or or or or or
higher higher higher higher higher higher higher higher higher higher
Memory [MB] Refer to Memory List
Hard disk (GB) 40 or more
Removable and optical DVD/CD-ROM drive, FD Drive
media
Display 17-inch LCD (1280 x 1024 or more) color monitor or equivalent
Keyboard Standard English keyboard
Pointing device Mouse
Printer Laser printer (option)
Audio Internal sound system with speaker
Interface 10/100/1000 Base-T LAN x 1 (for PNMS interface), USB x 2 (for keyboard and mouse)
®
Operating system Windows 2000 Professional (English version) or
®
Windows XP Professional (English version)
rd ® ®
3 party software Acrobat Reader (to read on-line Help manual), Java 2 Runtime Environment. SE
Client PC
®
Hardware requirements PC with Pentium 4 CPU 2.8GHz, 1,024 MB RAM, 40 GB HD, FD drive, CD-ROM drive, LAN port,
(minimum) internal sound system with speaker, color monitor (1280 x 1024), keyboard, pointing device
Operating system Windows 2000/XP Professional
rd ® ®
Memory List [MB]

Manageable NEs Memory [MB]
10000
9000 3000
8000
7000
6000
2048
5000
Memory List
4000
3000
1024
2000
1000
500
512
100
50
- 42 -
Appendix-C (UNIX)
The minimum hardware and software requirements of PNMSj (UNIX) are shown in the table below.
Type of PNMS Stand-alone/Regional/Central

Number of client 0 5 10 15
Manageable NEs 50 1000 4000 8000 1000 6000 1000 6000 1000 6000
- - - - - - - - - -
500 3000 7000 10000 5000 10000 5000 10000 5000 10000
CPU ULTRA SPARC III Cu 1.2GHz or Higher(CPU-ULTRA SPARC type only)
(GHz) 1.2 1.2 1.2 1.2 1.2 1.2 1.2 1.2 1.2 1.2
or or or or or or or or or or
higher higher higher higher higher higher higher higher higher higher
Memory (MB) Refer to Memory List
Hard disk (GB) 73 or more
Removable and optical DVD/CD-ROM drive, 4mm DAT Drive, FD Drive
media
Display 17-inch LCD (1280 x 1024 or more) color monitor or equivalent
Keyboard Standard English keyboard
Pointing device Mouse
Printer Laser printer (option)
Audio Internal sound system with speaker
Interface 10/100/1000BaseT LAN x 1 (for PNMS interface), USB x 2 (for keyboard and mouse), SCSI port (option)
Operating system Solaris or other UNIX
rd ® ®
Client PC
®
Hardware requirements PC with Pentium 4 CPU 2.8GHz, 1,024 MB RAM, 40 GB HD, FD drive, CD-ROM drive, LAN port,
(minimum) internal sound system with speaker, color monitor (1280 x 1024), keyboard, pointing device
Operating system Windows 2000/XP Professional
rd ® ®
3 party software Acrobat Reader (to read on-line Help manual), Java Runtime Environment. SE
Memory List [MB]

Manageable NEs Memory [MB]
10000
9000 3000
8000
7000
6000
5000
2000
4000
Memory List
3000
2000
1000
500
1000
100
50
- 43 -
Appendix-D
Currently the following configurations are not supported for PASOLINK NEO.
1. Ring Configuration
2. HUB connection
Connection with HUB

PNMSj
NEO NEO NEO NEO
H
U NEO NEO
B
NEO NEO
NEO NEO
- 44 -
3. Configuration between Pasolink V4 (PMC LAN) & Pasolink NEO
Connection between Pasolink V4 (PMC LAN) & Pasolink NEO
PNMSj
LAN
V4 V4 NEO NEO
Even if LAN PMC is mounted in PasoV4 still have to use the serial port for the BB connection.
Connection pin out also depends on which side the PNMS resides.
For reference, see the PASOLINK NEO Engineering Manual.
4. Configuration between Pasolink NEO & Pasolink V4/V3(PMC LAN)
Connection Between Pasolink NEO & Pasolink V4/V3 (PMC LAN)

PNMSj
LAN
NEO NEO V4 V4
NOTE: Configuration is possible using by Bridge function.
As above configuration if the PNMS on NEO side and V4with LAN card mounted,
Approach should be as follows to make valid configuration.
The NEO NE should be set with Bridge function and use auto discovery to discover the NEO portion
of the network (See Root Bridge setting for NEO).
The PasoV4 portion of the network should be configured using NCT and download the files. Use a
X-cable between EM1/EM2 (NEO) and NMS LAN port (V4) for BB connection (not serial port in
this case).
Refer to the following sample configuration:
- 45 -
A) Example-1
B) Example-2
5. PASOLINK NEO two ways connection
- 46 -

PNMSJ Engineering Manual (NEO) 2 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

PNMSJ Engineering Manual (NEO) 2 PDF

Загружено:

Авторское право:

Доступные форматы

Submission Prohibited ROI-S06246-051E

NEC Internal Use Only 070213

ATTENTION! : FOR NEC INTERNAL USE ONLY.

Copyright ©2007 by NEC Corporation

II. INTENDED AUDIENCE

III. ACCRONYMS AND DEFINITIONS

SOFTWARE VERSION NUMBER

DOCUMENT NUMBER TITLE

(1) Root NE (Gateway NE):

(2) Root NE (Bridge):

(3) Branch NE (Intermediate NE):

(4) Normal NE:

3.1 PNMSi Server

3.2 PASOLINK NEO Network Element

3.3 PNMTj Mobile Terminal

Note that the PNMTj is an optional component of the PASOLINK equipment.

5.1 PNMSj Server Sizing

Table 5-1: Recommended PASOLINK Network Sizing

Table 5-2: Subnet Assignment

IP R NEO NEO NEO NEO

IP Addressing Summary (LAN Interface)

IP R NEO NEO NEO NEO

Subnet B Subnetmask: 255.255.255.192

IP R NEO NEO NEO NEO

B NEO NEO NEO NEO

IP Addressing of PASOLINK NEO

IP R NEO NEO NEO NEO

B NEO NEO NEO NEO

IP 172.18.16.5 IP 172.18.16.65 IP 172.18.16.66

Operator can set subnet mask according to number of NE.

For reference, recommended IP address, subnetmask as follows:

Figure 5.4.2: BANDWIDTH CONSIDERATIONS

PNMSj NEO NETWORK CLUSTER

IP Addressing summary (Serial Interface)

For reference, recommended available IP address and subnet mask as follows.

IP CV4 SV4 B NEO NEO

IP Addressing summary (Serial Interface)

IP R NEO B NEO BPASO+ PASO+

IP Addressing Summary (LAN Interface)

IP R NEO B NEO B Paso+ Paso+

Operator can set subnet mask according to number of NE.

For reference, recommended available IP address and subnet mask as follows.

IP R NEO B NEO BPASO+ PASO+

IP Addressing Summary (Serial Interface)

IP R NEO B NEO B Paso+ Paso+

Subnet B is a sub network under PASOLINK NEO Branch.

IP R PASO+ B PASO+ B NEO NEO

IP Addressing Summary (LAN Interface)

IP R PASO+ BPASO+ B NEO NEO

IP R PASO+ B PASO+ B NEO NEO

Figure.7.6.1shows point to point connection of PASOLINK+ and PASOLINK NEO. PNMSj is

IP Addressing Summary (Serial Interface)

IP R PASO+ BPASO+ B NEO NEO

For reference, recommended available IP address and subnet mask as follows.

7.1 Parallel PNMSj

b) Performance monitors data

Network Operation Center-1

Alarm or Event Trap

Note: To connect PASOLINK NEO with existing equipment need to

Network Configuration for one subnet

10.1 Example: Add New HOP

Subnet-4 New Hop

Example: add New Sub network