Ch.01 System Overview and Architecture.pptx

System Overview and Architecture

1

Proprietary and Confidential

NetMaster Concept

• Based on the NGOSS principles,

• Based on Java technology

• Flexible SW components

• Platform independent

• Scalable HW platform

• Client-server architecture

• Management of the complete growing and evolving Ceragon product portfolio.

2


NetMaster Concept

• Full set of FCAPS functionalities

• End-to-end Services provisioning - Long Haul and Short Haul platforms

• Ethernet and TDM EtE services - maintenance and Provisioning

• Open SNMP adapter – managing any 3rd party SNMP based network element

• Complete redundancy & backup functionality

• Strong secured solution, flexible User access control

• Future-proof complete solution to support migration to all-IP

3


• Evolution Series• InterLink Family• Eltek Smartpack• BG20/BG30• CityLink Family• WiLink I / XL• FlexLink• CompactLink• NetLink & N2N• SmartNode/Metro/Connect• NL29x, NL24x & NL18x-A• FA 70F/T / 1500R• FA IP-10 C/E/G/Q

EltekCityLink

InterLink

Evolution Series

SmartNode

Evolution Long Haul Split

Evolution Long Haul

Supported Network Elements

FA 70

4

http://www.eltekenergy.com/wip4/detail_product.epl?cat=9816


Available features in NetMaster

Faults• Traps & Polling (user set)• Multiple views - Summary bar, Unique “Time Slider” histogram• NetMaster Northbound SNMP Agent for Higher layer management integrations• Reports – network view and alarm statistics

Configuration• End to End Services management• Bulk settings of common network parameters (as Trap Subscriber, Real Time clock)• Network elements Config files backup/restore • Network elements SW download• Launch of EMS GUI

Performance• Template based collection – flexible per usage needs• Graphing of collected data• Reports

Security• User/group privilege management• Audit logging/browsing

5


NetMaster license information- After installing NetMaster,a temporary

license is used to read the activation key from the server. Permanente license is issued after activation key from NetMaster server is sent to office. A valid licence must be imported within 30 days.

- NetMaster software key license is handled by Customer support directly.

6


Importing NetMaster license

- Importing NetMaster license is normally done by using the web based ”System Manager Software Tool”.

- During the installation the ”NetMaster initial setup wizard” will ask for the temporary license.

- During NetMaster Upgrade process a new licence file will be imported.

7


Flexible SW Components – Scalable HW Platform

Three Main Software Components:

• Application Server

• Clients (GUI)

• Database Server (Commercial)

One installation CD. Specific software components to be Installed, are selected when running setup: Server, Client, System Manager or Northbound interface.

8



Software Selection During the Installation:

Custom Installation.

• Client• Server• System Manager• Northbound SNMP Agent

9


Data Base


Two Software tools:

• System Manager: Runs as a service in both, App. Server and DB Server.

• Northbound SNMP Agent: Runs as a service in App. Server

System Manager

System Manager

Northbound Interface

App. Server

DB Server

NetMaster Installer

Commercial Database Installer

10


Clients

Client

Client – Server PlatformNetworks with more than 200 NEs:

Application Server, DB Server and Client should be in different Hardware.

In the case of very big networks, normally with more than 1000 NEs, it is recommended to have redundancy in the application server and DB server.

11


Client and server are connected by the TCP/IP network. Communication between client and server (Protocol) are based on Java Remote Method Invocation (Java RMI).

A periodical DB back up must be schedule in the Database Server. Back up files must be sent to a different Hard Drive.

Client – Server PlatformNetworks with more than 200 NEs:

12


Client – Server PlatformNetworks with less than 200 NEs:

Co-Located System.

•Application Server, Data Base Server may be in the same Hardware.

•Clients may also be in the same hardware and/or separated PCs.

13


Application Server

• Runs continuously in the background as a service.

• Manage the interaction of all NetMaster system components.

• Provides communication with all network elements (SNMP,).

• Designed based on JAVA/J2EE technology, hence suitable for porting to other Operating systems.

• There are not user interface for the server. All configuration will be done from clients.

Operating systems:

Windows XP SP3 / 2008 Server R2 / 7 SP1

14


Less than 200 NEs. Application Server, DB Server and Client might be in the same Hardware. (Co-Located system)

Between 200 and 1000 NEs. Application Server,• DB Server and Client should be in different • Hardware.

More than 1000 NEs. Application Server, DB Server and Client should be in different Hardware and it is recommended to have redundancy.

Application Server. Hardware Recomendations

#Radio Channels

#NE CPU RAM Disk) OS NIC Database) #15 min performance)

1-500 1 – 200 2.4 GHz 4 core

16 GB 150 GB

Win 2008 R2 SE x64

Ethernet100 Mbit/s

PostgreSQL 50

#Radio Channels


500-2500 200 – 1000 2.4 GHz

4 core

16 GB 300 GB

Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 250.

#Radio Channels


2500-5000

1000 – 2000

2.4 GHz

8 core

32 GB 300 GB

Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 500

15


Clients (GUI)

• End-user application.• Handles all user access to

NetMaster.• Rich Client• With License, up to 20 clients

can be logged on to the server simultaneously.

• Can be run in standard PCs.

Operating system:Windows XP SP3 / 2008 Server R2 / 7 SP1

16


Clients. The Graphical User Interface

• The GUI is built on “Rich client” platform• Perspectives• Geographical Tree & Maps• Logical Tree & Maps• Automatic Network Discovery• Data from multiple network elements can • be displayed simultaneously• System status are indicated using colours• Report Generator• Alarms on Topological Links

17


•Client/Server bandwidth recommendations are given for management of the complete network, with all network elements included.

•Restricting user access to administrative domains with a limited number of elements will reduce the amount of bandwidth required.

•1098: Java RMI Activation Port. •1099: Java RMI Registry Port.•4444: JBoss RMI Object Port. •8089: Apache Tomcat servlet container port, which is used by the Report Framework.

TCP ports used in Server/Client connection

Clients (GUI). Hardware Recomendations

MS Windows Client Configuration Recommendations#NE CPU RAM Disk space NIC Client/Server

bandwidth)

1 – 200 2.4 GHzDual core

4 GB 50 GB Ethernet100 Mbit/s

1-5 Mbit/s

200 – 1000 2.4 GHz

Dual core

4 GB 50 GB Ethernet

100 Mbit/s

10-50 Mbit/s

1000 2.4 GHzQuad core

8 GB 50 GB Ethernet100 Mbit/s

100 Mbit/s

18


Launching the client

•Default User name: root•Default password: pw

• Server: Server IP address in the network.

19


Launching the SystemManager Tool

•Default User name: root•Default password: pw

System Manager tool is running as a local service in both, NetMaster App. Server and DB Server computers, however is launched only on the NetMaster App. Server.

20


Database Server

• Application server has contact with NEs. Information and status from the network are store in the data base.

• The database server stores all data used by the NetMaster system.

• Two supported Data Base products in NetMaster.

Oracle: A commercial, proprietary database SW vendor.

PostgreSQL: A freeware, open-source database SW project.

21


Database

• Oracle 10g / 11g R2

• PostgreSQL versions 9.1

Database Server Recommendations#Radio

Channels

#NE CPU RAM Disk OS NIC Database #15 min performance)

1-500 1 – 200 2.4 GHz

4 core

16 GB 150 GB Win 2008 R2 SE x64

Ethernet

100 Mbit/s

PostgreSQL 50

500-2500

200 – 1000

2.4 GHz

4 core

16 GB 300 GB Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 250.

2500-5000

1000 – 2000

2.4 GHz

4 core

16 GB 300 GB(SSD)

Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 500

5000-10000

2000 – 5000

2.4 GHz

8 core

32 GB 600 GB RAID(SSD)

Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 1000

10000-25000

5000 – 10000

2.9 GHz

16 core

64 GB 600 GB RAID(SSD)

Win 2008 R2 SE x64

Ethernet

1 Gbit/s

PostgreSQL 2500

22


Database Server Connection ports

•1521: Oracle Database Listener. •2030: Oracle Services for Microsoft Transaction Server.•8081: HTTP Listener.

•5432: PostgreSQL 9.1

TCP ports used in Server/DB connection

23


DCN

Data Communication Network• Enable data communications

between NetMaster application Server and Networks Elements.

• Management communication between NetMaster and a network element is based on one of the following communication ports:

• SNMP over UDP/IP• HTTP over TCP/IP• Q1 over TCP/IP• Q1 over serial RS-232

24


DCN. IP Router. SU ver. D

DCC channels inRadio Link Overheador STM-1/OC-3 Line

25


DCN

• SU communication data channel change according to the radio family:

- Evolution Series: 256 kbps- InterLink/CityLink/NL29x: DCCr, 192 kbps- Mux: SmartNode/BG: DCCm, 576 kbps- Traditional PDH radios: 64 kbps

• NEs are represented in the DCN as routers (Internal in the SU/control unit)

• For elements using Q1, each NEs connected to the DCN will work as a Q1 gateway for the chain of elements connected behind them.

• Big Networks may also need to use external routers to build DCN backbone.

26


DCN

• A common approach is to use the 2 Mbps wayside channel in the network to build the DCN backbone.

• To avoid big delays in the polling time for NEs it is recommended to use 20 as a maximum network depth.

• Networks segments are normally build with no more that 30 NEs.

• A backbone segment of 2 Mbps is suitable for connecting up to 500 NEs.

• Dynamic Routing protocols are available in the different radio families.

- OSPF- RIP v2- Q1 dynamic routing protocol

27


DCN – IP 10

All units must be members of the same subnet / LAN unless Router is used

MNG data consumes BW of the total Radio link

Every Link (two ends) is associated with unique Link ID an VLAN ID

MNG BW can be configured via GUI: 64Kbps to 2048Kbps (recommended)

Remote units are managed via Radio Link

28


NetMaster redundancy with failover capabilities

• NetMaster can be configured for redundancy with failover capabilities, using a database replication scheme between main and standby NMS sites. This can be applied to both pure in-house HW redundancy as well as geographical system redundancy for disaster recovery.

29


Database replication scheme.

• Oracle 10g / 11g and Postgres 9.1: Both, main and standby app. servers are running in parallel, polling all elements. A set of scripts are available to make automatic replication of the entire database at regular basis, normally every night, so configuration changes are synchronized between databases.

30


NetMaster Database Online Backup

• 1+1 High Availability Configuration

31




32




33



• 2+2 High Availability Configuration with examples for the Points of Failure (POF)

34


Northbound Interface to Higher-order OSS

• The NetMaster SNMP Agent is an optional feature which requires a separate license.

• The agent provides topological information according to the standardized ENTITY-MIB (RFC 2737), and alarm state of the various network elements through proprietary tables and variables given in the proprietary NETMASTER-MIB.

• State changes are communicated to managers by means of SNMP traps.

• The SNMP Agent is a specialized client.

• For northbound integration from NetMaster to Nokia NetAct, a separate Nokia NetAct Bridge application has been provided.

• Inventory Management Reporting. (Licensed) Current HW and SW configuration. It updates, insertion/deletion of NE modules or the discovery of new NEs through the interface.

35


PM Feature

System design: NMS Server+ Optional Features

• Minimum system:NetMaster NMS Server

• Basic FCPS functionality

• Enhancements:Optional features

• Selectable (and priced) one by one

Secu

rity

Feat

ure

NetMasterNMS server

Basic FCPS management

Hierarchicaldomains

with maps

FM Feature

Report generator

Redundancy and

failover

Unix platform

North

boun

d SN

MP

conn

ectio

n

CM F

eatu

re

FM Feature

PM Feature

Secu

rity

Feat

ure

FMdomain

PM

domain

User

/Sec

urity

do

mai

n

GUIdomain

Platform

domain

CMdo

mai

n

System design

36

Thank You

Ch.01 System Overview and Architecture.pptx

Documents

Transcript of Ch.01 System Overview and Architecture.pptx