Raisecom GPON Solution Training - Chapter 4 NView_V2.pptx

Content Overview
Session 1 Session 2
Day 1
 OVERVIEW
o Introduction.
o NVIEW Structure
 SYSTEM DEPLOYMENT
o Deployment Topology
o License File
o Installation / Upgrade Procedure
 NVIEW OPERATION
o NVIEW Dashboard
o General review
o Topology
o GPON Configurations
 Service Configurations
Day 2
 NVIEW OPERATION
o NVIEW Data Center
 Configuration Nodes Backup
 Sw Backup/Upgrade
 Practice
o NVIEW Services Testing
 System Services
 Scheduled Services
 Practice
 NVIEW ADMINISTRATION
o NVIEW Services
 System Services
 Scheduled Services
o Security Management
 User Definition
 Groups Definition
 User Privileges
 Network Nodes Restrictions
 Practice
• FINAL REVIEW

INTRODUCTION
The NView NNM system adopts the Client/Server (C/S) architecture. One NMS Server
can be connected with multiple NMS Client for network management. At present, the
NView NNM system program includes the following items:
– NMS Server (including the database, NMS Console, upgrade tool)
– NMS Client
– PM service
– SLA Portal

NVIEW OVERVIEW
NView NNM (Network Node Management) system is designed for
monitoring and managing Raisecom network manageable devices
on a uniform platform integrated with topology, resource, alarm,
customer, configuration, performance, security management
functions.

7
NView NNM system covers the lower two layers in the TMN architecture, and implement Fault,
Configuration, Performance, and Security management in the FCAPS model. A CORBA-based
northbound interface is available for the integration to higher-lever NMS such as OSS.
NVIEW OVERVIEW
NVIEW STRUCTURE

NVIEW OVERVIEW
NVIEW STRUCTURE
Upper-level NMS/OSS/BSS
CORBA-based and TMF814 northbound interface
EMS for NID
Nview NNM Platform
Performance
Inventory
MGT
Fault
MGT
Topology
Customer
MGT
Log
MGT
Datacenter
Data
Dump
Security
MGT
configura
tion
CEView-
provision
RFC 2544
SLA monitor
Y.1564
ZTP
SLA-
portal
WEB
Server
WEB
Client
APPs
Client
Raisecom Products
Business MGT
Layer
Service MGT
Layer
Network MGT
Layer
Element MGT
Layer
Network
Element
TMN
NView NNM system covers the lower two layers in the TMN architecture, and implement Fault,
Configuration, Performance, and Security management in the FCAPS model. A CORBA-based
northbound interface is available for the integration to higher-lever NMS such as OSS.

NVIEW OVERVIEW
NVIEW STRUCTURE

NVIEW OVERVIEW
TMN ARCHITECTURE
• Java-based development
• SNMP-compliant system, with
support for SNMP V1/2c/3
• Server-Client architecture
• Network management over all
Raisecom product lines which
implements configurations,
performance and security
management in the FCAPS
model.
• CORBA-based and TMF814-
compliant northbound interface
enables the integration with
upper-level NMS

NVIEW DEPLOYMENT
DEPLOYMENT TOPOLOGY
Stand-alone Deployment:
deploy database, server and
client on one PC
Distributed Deployment:
deploy clients on separate
PCs, several clients may
operate opposite one
server
The device under management should have an SNMP agent.

NVIEW DEPLOYMENT
DISTRIBUTED DEPLOYMENT

NVIEW DEPLOYMENT
Different EMS running
on the uniform
platform NView NNM
realizes the network
management over
different Raisecom
product lines.
License file (charge per
network management
node) validates the use
of NView NNM.
NView NNM (Network
Node Management)
system provides a uniform
network management
platform for Raisecom
product lines.

NVIEW DEPLOYMENT
HARDWARE REQUIREMENTS FOR < 5000 NETWORK ELEMENTS
Central Processing Unit
Intel® Xeon® E5-2407 2.20GHz, 10M Cache, 6.4GT/s QPI, No Turbo,
4C, 80W, Max Mem 1066MHz
Main memory
4GB RDIMM, 1600 MT/s, Low Volt, Single Rank, x8 Data Width
Cache memory 2.5MB per core
Hard Disk capacity
2x 500GB 7.2k RPM SATA 6Gbps
Expansion Slot
2 PCIe slots:
One x8 PCIe slot with x4 bandwidth, half-length, half-height
One x16 PCIe slot with x16 bandwidth, half-length, full-height
LAN Communication interfaces Broadcom 5720 Dual Port 1Gb LOM
Backup device
SW RAID 1 for S110 (2 SATA HDDs) with Cabled Chassis
S110, Software RAID (for Microsoft OS Only)
Power Supply Dual, Hot-plug, Redundant Power Supply, 350W
Monitor Dell UltraSharp 24 Monitor, U2412M, 24"
The Dell Power Edge R320 server is recommended when the NEs are less than 5000. The specific
configuration parameters are as follows:

NVIEW DEPLOYMENT
HARDWARE REQUIREMENTS FOR 5000 TO LESS THAN 20000 NETWORK ELEMENTS
2x Intel® Xeon® E5-2603 v3 1.6GHz,15M Cache,6.40GT/s QPI,No
Turbo,No HT,6C/6T (85W) Max Mem 1600MHz
Main memory
2x 4GB RDIMM, 2133MT/s, Single Rank, x8 Data Width
Hard Disk capacity
2x 500GB 7.2k RPM SATA 6Gbps
Expansion Slot
slot 1: Half length, half height - PCIe 3.0 x16
slot 2: 3/4 length, full height - PCIe 3.0 x16
Dedicated RAID card slot
LAN Communication interfaces Broadcom 5720 Dual Port 1Gb LOM
Backup device
RAID 1 for S130
S130, Software RAID
Power Supply Dual, Hot-plug, Redundant Power Supply (1+1), 495W
The Dell Power Edge R630 server is recommended when the NEs are more than 5000 but less than
20000. The specific configuration parameters are as follows:

NVIEW DEPLOYMENT
HARDWARE REQUIREMENTS FOR 20000 TO LESS THAN 50000 NETWORK ELEMENTS
4x Intel® Xeon® E5-4620 2.20GHz, 16M Cache, 7.2GT/s QPI, Turbo, 8
Core, 95W, Max Mem 1333MHz
Main memory
2x 8GB RDIMM, 1600MT/s, Low Volt, Dual Rank, x8 Data Width
Hard Disk capacity
2x 600GB 10K RPM SAS 6Gbps 2.5in Hot-plug Hard Drive
Expansion Slot
7 PCIe slots:
Two x16 half-length, full-height
One x8 half-length, full-height
Three x8 half-length, half-height
One x8 half-length, full-height for the RAID controller
LAN Communication interfaces Intel Ethernet I350 QP 1Gb Network Daughter Card
Backup device
RAID 1 for H710P/H710/H310
PERC H710 Adapter RAID Controller, 512MB NV Cache
Power Supply Dual, Hot-plug, Redundant Power Supply (1+1), 750W
The Dell Power Edge R630 server is recommended when the NEs are more than 20000 but less than 50000.
The specific configuration parameters are as follows:

NVIEW DEPLOYMENT
OPERATING SYSTEMS SUPPORTED
Operating system 32bits Operating system 64bits
NView NNM
network
management
service
 Windows Server 2003 SP2 Standard X86
 Windows Server 2003 SP2 Enterprise X86
 Windows XP SP3 Professional X86
 Windows 7 SP1 Professional X86
 Windows 7 SP1 Enterprise X86
 Windows 7 SP1 Ultimate X86
 Windows 8/8.1/10 Professional
 Windows Server 2008 R2 Standard X64
 Windows Server 2008 R2 Enterprise X64
 Windows Server 2012
 Windows 8/8.1/10 Professional x64
NView NNM
distributed
performance
monitoring
service
 Windows 8/8.1/10 x86
 Windows Server 2008 R2 Standard X64
 Windows Server 2008 R2 Enterprise X64
 Windows 8/8.1/10 x64
 Windows Server 2012
NView NNM
distributed clients

NVIEW DEPLOYMENT
NVIEW PORTS
Please refer to the document “NVIEW NNM (V5) Installation Guide (Rel_47) item 1.1.3 (Interface
Requirements) for more detailed information.
Service name The port request marked
DB service 13306 mandatory
Core service 9302, 9304, 9362, 9364, 9367, 16262, 61616, 61617 mandatory
Upgrade tools 9312, 9314, 9303, 9304, 9307 mandatory
DB center service 20, 21, 9320, 9322, 9323 optional
Trap receiving
service
162 mandatory
NBI 9315, 9316, 9317 optional
PM service 13308 optional
SLA Portal service 2121, 8080 optional

NVIEW DEPLOYMENT
INSTALLATION PROCESS

NVIEW DEPLOYMENT
INSTALLATION PROCESS
The following parts will be needed when install NView NNM system:
 NView NNM Installation Program
 Installation program for NView NNM platform and all EMS
 Performance Management Component
 Optional function component
 Independent installation and un-installation
 SLA Portal
 Upgrade Package
 A ‘zip’ file for upgrade using the uniform upgrade manager
 License
 A file to verify the legal use of NView NNM system

NVIEW DEPLOYMENT
LICENSE FILE
 Format: XML file
 License file controls:
o Demo License:
 No need Server MAC or IP address.(Server MAC Address).
 Expiration time.
o Authorized License:
 Needs the Server MAC or IP Address
 No expiration
o Nview Modules Included (Data Center, SLA Portal, etc)
o Components (Nview Model/Reference to be managed)
o Number of Nodes (per Model)
o Number of concurrent sessions (Nview Clients)

NVIEW DEPLOYMENT
INSTALLATION PROCESS: PRE-CHECKs
Before install please verify this:
 Operating System
 Windows
o XP, 7, 8, Server 2003, Server 2008?
o 32 Bytes or 64 Bytes?
 NO Antivirus
 Firewall: NO NVIEW Ports blocked
 Use the Administrator Account (preferred) or an account with Administrator
rights.
 HW Requirements

NVIEW DEPLOYMENT
INSTALLATION PROCESS: INSTALL NVIEW (BASE INSTALL SOFTWARE)
Run the .exe file “NView_NNM_V5_YYYYMMDD_winXX”
• YYYYMMDD: Nview Main installer Release date.
• XX: 32 or 64 (Windows 32 Bytes or 64 Bytes)
• In this case we will use the main installer file: NView_NNM_V5_20150513_win64

NVIEW DEPLOYMENT
1. Run the .exe file
2. Accept the license Agreement

NVIEW DEPLOYMENT
3. Select Server or Client and Installation Path 4. Select License File

NVIEW DEPLOYMENT
5. Select License File

NVIEW DEPLOYMENT
6. Select Server IP Address
7. NVIEW Data Base: Install MySQL (Stand-Alone Deployment)
or connect to an existing MySQL Server (Distributed
Deployment)

NVIEW DEPLOYMENT
 Using Server Global IP Address topo：
 There is two network adapter in server（one use for internal IP address which connect with
nodes, another is connect with extranet IP which connect with client），Below is the topo。
The client is connecting with Server Global IP Address，nodes connecting with Server IP
Address。

NVIEW DEPLOYMENT
 Different network: NAT
 Enable NAT (Network Address Translation) between server and client address connection，
Below is the topology, the client connected via NAT IP of server. When installing client, need
input “Server Global IP address”, it is the translated IP address.

NVIEW DEPLOYMENT
 Different network：double network adapter
 If the net work have double network adapter（one use for internal IP address which connect
with nodes, another is connect with extranet IP which connect with client）,Below is the
topology. The client is connecting with Server Global IP Address, you need to input "Server
Global IP" when install client.

NVIEW DEPLOYMENT
8. Review Installation Parameters 9. Ready to start NVIEW Install

NVIEW DEPLOYMENT
10. Installation Progress 11. NVIEW Installation finished

NVIEW DEPLOYMENT
INSTALLATION PROCESS: PM (PERFORMANCE MANAGER) SERVER
Run the .exe file “NvvvvvvvvvView_NNM_V5_YYYYMMDD_winXX”
• YYYYMMDD: Nview Main installer Release date.
• XX: 32 or 64 (Windows 32 Bytes or 64 Bytes)
• In this case we will use the main installer file: NView_NNM_V5_20150513_win64

NVIEW DEPLOYMENT
1. Run the .exe file 2. Select Language

NVIEW DEPLOYMENT
3. Run the .exe file 4. Select Installation Path (Must be different than Nview Path)

NVIEW DEPLOYMENT
5. Enter PM Server IP Address 6.PM Installation Progress

NVIEW DEPLOYMENT
5. PM Installation finished.

NVIEW DEPLOYMENT
NVIEW SERVER AND PM INSTALLED.

NVIEW DEPLOYMENT
 NVIEW Base Installation
 Version upgrade

NVIEW DEPLOYMENT
NVIEW UPGRADE
The desktop shortcut for the Upgrade Manager. It appears after the
installation of NView NNM V5.2.
NView NNM V5.2 provides a uniform platform for all upgrades, including upgrade of
platform function and upgrade of EMS. The upgrade manager upgrades the current NView
system with an upgrade packet with version information.
The upgrade process includes 3 steps:
Check: check the version and content of the upgrade packet
Backup: backup the current NView system to make sure can the current system can be
restored even if the upgrade fails
Upgrade: upgrade the current system to the new version

NVIEW DEPLOYMENT
NVIEW UPGRADE
 Upgrade validation
 For avoid accident and improve security of upgrading, using at least one of the following two
suggestions to upgrade verification.
o Before upgrading, send DB back to Raisecom for checking.
o Copy DB to another new server to pre-upgrade for checking upgrade result and time
If the version
earlier than V5.4.4.2
upgrade verification
is must.

NVIEW DEPLOYMENT
1. Double Click on Upgrade Icon 2.Start Upgrade and Go to Specify Upgrade Package
NVIEW UPGRADE

NVIEW DEPLOYMENT
NVIEW UPGRADE
3. Select Upgrade Package 4. Select Backup Path

NVIEW DEPLOYMENT
NVIEW UPGRADE
5. Upgrade Process 6. Upgrade finished

Features
• Topology and Node Management
46
Alarm Counter
Tree Topology
User and Client
status
Main Menu
System Toolbar
Network
Topology
Node for
Nview Server
Node with
Sub-graph
Topology
Management
Bar
Real-Time
Current Alarm list
Node with Alarm

• Topology and Node Management
47
Features

• Topology Management
48
Features

• Node Management
49
Features

• Topology Management: Device Auto discovery
50
Device Scan and
Poll Component
Device Scan
Task
Device Scan
Task Settings
Features

• Fault Management
51
Features

• Fault Management: Current Alarms
52
Features

• Fault Management: Alarm Details
53
Features

• Fault Management: Alarms History
54
Features

• Fault Management: Alarms History
55
Features

• Security: Domain
57
Features

• Security: Users
58
Features

• Security: User Group
59
Features

• Security: User Group
60
Features

• PM Server Real-Time Graph
61
Features

How to configure GPON service
 Adding OLT
 VLANs
 DBA Profile
 Line profile
 Service profile
 ONU creation

Adding OLT
 Nview allows to view the device as shelf view and present alarms of the system
 In order to discover the OLT on the Nview it required first to configure the OLT by CLI to communicate
via SNMP with the management server.
snmp-server host 192.168.22.191 version 2c public udpport 162
 Once the Nview server ip address be configured
by the OLT the device could be easily added on the
Nview
 Steps:
1. Click Add Device
2. Type Ip address of device
3. Click on check type
4. Confirm
5. Save
1
2
4
5
3

Panel view
 Show the shelf view of a device
 Click on OLT Control Card

VLANs
 VLAN Add /remove/modify (Go to OLT config  VLAN config  Switch VLAN)
1
2
3
4

VLANs
 Port and VLAN assignment (GE interface)
2
1
5
4
3

VLANs
 Port and VLAN assignment (PON interface)
1 5
6
3
2
4
7

DBA Profile
 DBA configuration (Go to OLT Config  ONU GPON ONU Template  DBA Profile)
2
1
3

Line Profile
 Line-profile configuration [1] (Create new line-profile)
2
1
3
4

Line Profile
 Line-profile configuration [2] (Select mapping mode)
1
2
3
4

Line Profile
 Line-profile configuration [3] (Associate TCONT with DBA Profile)
1 2 3
4
5

Line Profile
 Line-profile configuration [4]. (Associate GEM index under the TCONT)
1 2
3
4
5

Line Profile
 Line-profile configuration [5] (Configure the GEM Mapping within the TCONT)
1
2
Modify GEM mapping settings

Line Profile
If Downlink Speed
Template is used (0-1024,
0-not used)
Vlan List and Mapping ID.
(i.e. 100,200,0,400,0,0,0,0)
means those vlans are included in the
Gem 1 and will be delivered to the ONU.
The mapping ID used are 1,2 an 4
respectively (determined by the position
where the vlans are located)
If Uplink Speed Template
is used (0-1024)
If Vlan Mapping
Mode is selected

Line Profile
If Port + Vlan
Mapping Mode is
selected
3 Vlans (100,200,300) and 3 ports (1,2,5)
Gem 1
Gem 2
Gem 3
Only for SFUs!!!, The mapping for HGUs is
using the ONU web management

Line Profile
 Delete Line-profile (can not be deleted if there is an ONU created with this line profile)
2
3
4
5
1

Service profile
 Service-profile configuration (Go to OLT Config  ONU  GPON ONU Template  Service-Profile)
1
2
3
4

Service profile
 Service-profile configuration (General properties of the service) HGU only!!
1
2
For HGU=1
Qty of POTS ports
in the HGU
Qty of ETH ports=0
Qty of CATV ports
in the HGU
3

1
2
For SFU=0
Qty of POTS ports
in the SFU
Qty of ETH ports=1..24
Qty of CATV ports
in the SFU
3
Service profile
 Service-profile configuration (General properties of the service) SFU only!!

Service profile
 Service-profile configuration i.e. ONU SFU in transparent mode and native vlan 50
Vlan Mode:
Transparent
Native Vlan
number
1
2
3

Service profile
 Service-profile configuration, i.e. ONU SFU in tag mode and native vlan 100
Vlan Mode:
Tag
Native Vlan
number
1
2
3

Service profile
 Service-profile configuration i.e. ONU SFU in trunk mode, native vlan 1 and vlan 100,200, 300 allowed
Vlan Mode:
Trunk
Native Vlan
number
1
2
3
Vlan allowed

Service profile
 Service-profile configuration (unieth2 config, only for SFUs!!!)
Multicast and
QinQ Config
2
1
3

Service profile
 Service-profile configuration ( veip config, only for HGUs!!!)
1
2
3
VEIP=1 for HGU

Service Profile
 Delete Service-profile (can not be deleted if there is an ONU created with this service profile)
2
3
4
5
1

Create new ONU
Select Authentication Mode in the PON Port (Go to OLT Config  Port  PON Port
Config)
1
2
4
3
5

Create new ONU
Verifying the ONU is phisically connected (Go to OLT Config  ONU  Illegal ONU
List)

Create new ONU
1
2
Right Click
3 4

Modify Service or Line profile
If there is an ONU associated to a line-profile or service-profile, these can not be
modified. A way to disassociate a ONU from a service is shown below (Go to ONU
Config  Online Info)
Modified the line-profile or service-profile

Delete ONU
Enabled: The object is deleted in the Nview and
in the OLT
Disabled: The object is deleted only in NView
 Check delete options (Go to PON  PON Preferences)

CATV
Activate or Deactivate CATV port (Go to ONU  ONU Config  Port  CATV Port)
1
2

Raisecom GPON Solution Training - Chapter 4 NView_V2.pptx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Raisecom GPON Solution Training - Chapter 4 NView_V2.pptx

Similar to Raisecom GPON Solution Training - Chapter 4 NView_V2.pptx (20)

Recently uploaded

Recently uploaded (20)

Raisecom GPON Solution Training - Chapter 4 NView_V2.pptx