Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
070315
Engineering Manual
(PASOLINK NEO Version)
NEC Corporation
Copyright © 2007
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.
ROI-S05956
CONTENTS
1 INTRODUCTION…………………………………………………………………………………… 1
2 SYSTEM DESIGN OVERVIEW………………………………………………………………….. 4
2.1 GENERAL DESCRIPTION AND NETWORK DESIGN CONCEPTS ........................................................ 4
2.2 NETWORK ARCHITECTURE ........................................................................................................... 5
2.3 CTRL MODULE FUNCTION ............................................................................................................ 6
2.4 NETCONFIGTOOL V.S. AUTO-DISCOVERY .................................................................................... 7
3 SYSTEM COMPONENTS…………………………………………………………………………. 8
3.1 PNMSI SERVER ............................................................................................................................ 8
3.2 PASOLINK NEO NETWORK ELEMENT ....................................................................................... 8
3.3 PNMTJ MOBILE TERMINAL .......................................................................................................... 8
4 PASOLINK NEO INTERFACE…………………………………………………………………… 9
5 PASOLINK NEO NMS NETWORK DESIGN………………………………………………… 10
5.1 PNMSJ SERVER SIZING ................................................................................................................ 10
5.2 PASOLINK NEO SIZING AND TOPOLOGY ................................................................................... 11
5.3 TYPES OF CONFIGURATION & IP ADDRESSING ............................................................................. 12
5.4 DCN REQUIREMENTS ................................................................................................................... 15
6 INTEROPERABILITY WITH EXISTING PASOLINK EQUIPMENT……………………. 17
6.1 PASOLINK NEO (SERIAL INTERFACE) & PASOLINK (V3/V4)................................................. 17
6.2 PASOLINK (V4/V3) & PASOLINK NEO (SERIAL INTERFACE)................................................. 18
6.3 PASOLINK NEO (LAN INTERFACE) & PASOLINK+/ MX SERIES ............................................. 19
6.4 PASOLINK NEO (SERIAL INTERFACE) & PASOLINK+/ MX...................................................... 20
6.5 PASOLINK+ /MX (LAN INTERFACE) & PASOLINK NEO ......................................................... 21
6.6 PASOLINK+ / MX(SERIAL INTERFACE) & PASOLINK NEO...................................................... 22
7 PNMSJ REDUNDANCY…………………………………………………………………………. 23
7.1 PARALLEL PNMSJ ........................................................................................................................ 23
8 CASE STUDY (SAMPLE NETWORK DESIGN, PLANNING AND IMPLEMENTATION)
…………………………………………………………………………………………………………25
9 NETWORK CONFIGURATION SAMPLE……………………………………………………. 26
9.1 NETWORK CONFIGURATION FOR ONE SUBNET............................................................................. 26
9.2 NETWORK CONFIGURATION WITH TWO BRANCHES ..................................................................... 27
9.3 NETWORK CONFIGURATION WITH MULTI BRANCHES .................................................................. 29
10 CASE STUDY: ADDING NEO TO PASOLINK/PASOLINK+ NETWORK……………. 31
10.1 EXAMPLE: ADD NEW HOP ........................................................................................................... 31
APPENDIX - A: CABLE DIAGRAMS……………………………………………………………….. 33
A.1 PNMT/LCT CABLE ...................................................................................................................... 33
A.2 PNMS CABLE LAN INTERFACE ................................................................................................... 34
A.3 PASOLINK NEO & PASOLINK (V3/V4) .................................................................................. 35
A.4 PASOLINK NEO & PASOLINK................................................................................................. 36
A.5 PASOLINK NEO & PASOLINK................................................................................................. 37
A.6 PASOLINK NEO & PASOLINK+/MX ........................................................................................ 38
A.7 PASOLINK+/MX & PASOLINK NEO ........................................................................................ 39
A.8 PASOLINK NEO & MIU(HOP) OR MIU (LINE CONCENTRATOR)............................................... 40
APPENDIX-B (WINDOWS)…………………………………………………………………………… 43
APPENDIX-C (UNIX)………………………………………………………………………………...... 44
i
ROI-S05956
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.
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
-1-
ROI-S05956
IV. REVISIONS
The functions described in this based is based on the following versions:
-2-
ROI-S05956
V. REFERENCES
It is recommended to read the following references for detailed explanation of other NEC radio
equipment DCN engineering:
-3-
ROI-S05956
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.
-4-
ROI-S05956
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.
-5-
ROI-S05956
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:
-6-
ROI-S05956
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.
-7-
ROI-S05956
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
-8-
ROI-S05956
-9-
ROI-S05956
- 10 -
ROI-S05956
The following network sizing restriction is applied when NEC PASOLINK NEO series supervisory
network hierarchy is configured
** 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:
- 11 -
ROI-S05956
PNMSj
~ ~
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 172.18.14.4
IP 172.18.14.2
N
~ LA ~
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:
- 12 -
ROI-S05956
~ ~
~ ~
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
~ Subnet A ~
Subnetmask
255.255.255.192
Subnet B
~ Subnetmask
~
255.255.255.192
- 13 -
ROI-S05956
- 14 -
ROI-S05956
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.
- 15 -
ROI-S05956
GNE
A
A––384 kbps (minimum bandwidth utilized by the cluster)
- 16 -
ROI-S05956
~ ~
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 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.
- 17 -
ROI-S05956
PNMSj
~ ~
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 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
Subnetmask Subnetmask
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:
- 18 -
ROI-S05956
PNMSj
~ ~
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.
IP172.18.6.2
N IP 172.18.6.66
~ LA ~
IP 172.18.6.1
IP 172.18.6.65
Figure7.3.1a
- 19 -
ROI-S05956
PNMSj
~ ~
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.
PNMSj
IP 172.18.4.66
IP172.18.4.2
~ Async ~
IP 172.18.4.1
IP 172.18.4.65
Figure7.4.1a
- 20 -
ROI-S05956
PNMSj
~ ~
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 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.
Therefore the subnet mask is 255.255.255.192
For reference, recommended IP address, available IP address and subnet mask as follows.
- 21 -
ROI-S05956
PNMSj
~ ~
Figure 7.6.1
PNMSj
IP 172.18.10.66
IP172.18.10.2
~ Async ~
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.
Therefore the subnet mask is 255.255.255.192
- 22 -
ROI-S05956
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).
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.
- 23 -
ROI-S05956
PNM S-1
Alarm or Event Trap
LAN
Custom er IP network
LAN
: ROUTER
PNM S-2
Regional Network Operation Center-2 : PASOLINK NEO
Figure 8.1 Parallel PNMS
- 24 -
ROI-S05956
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.
- 25 -
ROI-S05956
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 -
IP Address 172.18.0.2
Radio/EM1/EM2
Not Subnet Mask 255.255.255.192
No.02 Normal NE
selectable Default Gateway 192.168.0.1
Routing
Static Routing Table -
IP Address 172.18.0.3
Radio/EM1/EM2
Not Subnet Mask 255.255.255.192
No.03 Normal NE
selectable Default Gateway 172.18.0.1
Routing
Static Routing Table -
IP Address 172.18.0.4
Radio/EM1/EM2
Not Subnet Mask 255.255.255.192
No.04 Normal NE
selectable Default Gateway 172.18.0.1
Routing
Static Routing Table -
- 26 -
ROI-S05956
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.
- 27 -
ROI-S05956
- 28 -
ROI-S05956
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.
- 29 -
ROI-S05956
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:
- 30 -
ROI-S05956
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.
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
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
- 31 -
ROI-S05956
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)
- 32 -
ROI-S05956
Station A Station B
NEO NEO
PNMT/LCT
(USB)Port
USB
- 33 -
ROI-S05956
Station A Station B
NEO NEO
ROOT NE
PNMS EM 1
Port(LAN)
Ethernet
HUB LAN
PNMS
- 34 -
ROI-S05956
Figure.3
- 35 -
ROI-S05956
Figure 4
- 36 -
ROI-S05956
Figure 5
- 37 -
ROI-S05956
Figure 6
- 38 -
ROI-S05956
- 39 -
ROI-S05956
Figure 8
- 40 -
ROI-S05956
Figure 9
- 41 -
ROI-S05956
Figure 10
- 42 -
ROI-S05956
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 ® ®
3 party software Acrobat Reader (to read on-line Help manual), Java 2 Runtime Environment. SE
10000
9000 3000
8000
7000
6000
2048
5000
Memory List
4000
3000
1024
2000
1000
500
512
100
50
- 43 -
ROI-S05956
Appendix-C (UNIX)
The minimum hardware and software requirements of PNMSj (UNIX) are shown in the table below.
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
10000
9000 3000
8000
7000
6000
5000
2000
4000
Memory List
3000
2000
1000
500
1000
100
50
- 44 -