3-CEN Service Configuration

CEN Service Configuration

Contents

NMS Overview Basic Configuration Service Configuration Process

Contents


Contents


NMS Overview  NMS Diagram

Connecting to NMS Server  Via Remote Desktop Connection

界面介绍界面介绍

OTNM2000 and DevCfg .

OTNM2000 NMS collect the alarm data and performance data through the data acquisition module. After data processing module analyzing and processing ，the data is stored in the database. Data processing module also can provide alarm management, performance management, configuration management and security management for GUI management module. The GUI management module composed of the configuration management Module (DEVCFG) and interface management module (OTNM2000) Configuration management module

the program for equipment and system

：

running environment configuration in NMS 。It used for device configuration (include

device type, network界面介绍 type, IP address, etc.), configuration managers (including manager IP, protocol type, etc.), the database Settings, data check and so on . Interface management module

OTNM2000's main interface program

：

。

界面介绍 OTNM2000 Implement the managing function according to the configuration data in DEVCFG, its main function is the configuration management, alarm management, performance management and security management, etc.

Interface Overall introduction After the installation of OTNM2000 network is completed, we can see two icon for DEVCFG and OTNM2000. Network users must be based on actual situation using the configuration management module (Devcfg) to configure network , and to save configuration in the data database, so we could use the management interface module to (OTNM2000) realize all management functions，according to the configuration data.

Connecting to OTNM2000 1. Double click the OTNM 2000 Server icon.

界面介绍界面介绍

Connecting to DevCfg 1. Double click the DevCfg icon.

2. Click Read DB.

3. Login. Username: 1 Password: 1

Contents


Uploading New Network Element Click the devcfg icon(

).

Read DB Login to devcfg. Username: 1 ; Password: 1

Click Logical Cfg. Scenario: 1. If the new NE is not part of existing area(e.g. Ilocos, Pangasinan), right click on the Current Project then select “Add Part”. 2. If the new NE will be a part of existing area, right click at the area(ex. Right click on “ILOCOS NORTE” then select “Add NE”

Adding New Part Scenario: If the new NE is not part of existing area(e.g. Ilocos, Pangasinan), right click on the Current Project then select “Add Part”. Part Type: select “SDH” Manager Service: drop down and select “Number 1 Manager Service” Part Name: the new area(example: TARLAC) Click “Add”.

Adding the Node/NE Right-click the corresponding part in the Logical Cfg tab of the browse tree pane, and then click Add NE… of the shortcut menu. Add node dialog box will Appear.

Adding the Logical Configuration Object Item list

Description

NE Type

According to actual installed equipment(R865 or R845).

EMU Card Type

For R865 and R845, choose “RCU”.

Switch 1

ID number 1 of NE hardware, which is usually set as the third numerical value of the NE IP Address. Together with Switch 2, it composes the ID number of NE, which identifies different NEs.

Switch 2

ID number 2 of NE hardware, which is usually set as the forth numerical value of the NE IP Address. Together with Switch 1, it composes the ID number of NE, which identifies different NEs.

IP Address

IP address of NE.

IP Mask

NE’s mask address. Usually, it is 255.255.255.0.

IP Gateway

Usually keep default value -- 0.0.0.0

Adding the Physical Configuration Object Adding Bureau  Click Physical

.

browse

tree

Cfg on the

pane

and

the

Physical Cfg tab appears.  Right-click the blank area of the

tab

and

then

click

Add

Bureau… of the shortcut menu. Add

bureau

appear.

window

will

Adding the Physical Configuration Object Adding Rack  Right-click

.

the

corresponding

bureau in the Physical Cfg tab of the browse tree pane, and then click Add Rack… of the shortcut menu. Add rack dialog box will appear.

Usually, only Rack layers needs to be configured in the Add rack dialog box.

Adding the Physical Configuration Object Adding Shelf  Right-click

.

the

corresponding

rack in the Physical Cfg tab of thebrowse tree pane, and then click Add Shelf ….

 Click the corresponding rack to

open the rack view, right-click the shelf in the view and then click Add Shelf ….  Shelf Type: R865/R845 (CEN)

Adding the Physical Configuration Object Adding Card  Right-click the slot and then

.

click Add card option in the shortcut

menu

and

the

selected card will be added to the slot. If the card to be added is not displayed in the shortcut menu directly, please select Add thers and choose from the submenu.

Configuring the NE Connection  In the Logical Cfg tab of the browse tree pane in configuration management

window, right-click the project that need to implement structure configuration, .

select Structure Config in the shortcut menu, the Structure Config tab appears in the view window.

Configuring the NE Connection click one part of a project on the Logical Cfg tab and then

drag it to the Structure Config tab.

Configuring the NE Connection  Right-click

topology,

one then

node

in

select

the Add

Connection Line in the shortcut menu.  Drag the cursor to another node

and release the mouse. Then Add Connection Line dialog box will appear

Validating the Configuration Data

 Correct configuration data: If .

there are no red letters, that means the configuration data is correct

Validating the Configuration Data

 Incorrect configuration data: If

. there

are red letters, that

means the configuration data is incorrect

Saving the Configuration Data  You can save the configuration data after completing and verifying the configuration.  Click

button in the toolbar and the devcfg dialog box appears. Click Yes, the

original configuration data in database (including the configuration data of card) will be cleared and replaced by current data. Click No will cancel this operation.

Saving as file Click

button in the toolbar to save the configuration data

as a *.dcg file for convenient view and modification in the future. Saving data and configuration in this format is relatively safe.

Synchronizing the NE to the existing network Click Advance, Choose NE IP Remote Config

Synchronizing the new NE to the existing network Find your Source Site, which is the adjacent NE(existing

NE/online), then click Operation

Detecting the new NE’s Serial Number  Click Get Remote NE SN. The Serial Number (SN) must be validated

on the actual SN found in RCU(2xRCU) card installed on-site.

Detecting the new NE’s Serial Number  Click Get Neighbor NE by SN. Only choose the right NE based on SN

or NE IP address.

Detecting the new NE’s Serial Number

Put the SN(any of the two RCU SN) in object of the new site. Make sure that this is the

correct SN. Ex: Put the Existing Node Source Site NE IP in Source NE IP Address of the new node to upload. For Default Domain: Choose NOT DEFAULT DOMAIN

Detecting the new NE’s Serial Number

Detecting the new NE’s Serial Number Choose the row of the new site under Operation Status, then click Set Remote NE IP

Config.

Detecting the new NE’s IP Address Choose the row of the new site under Operation Status, then click Set Remote NE IP

Config.

Detecting the new NE’s IP Address Choose the row of the new site under Operation Status, then click Set Remote NE IP

Config. We must detect the Existing Node NE IP address using our new node.

Verifying the uploaded NE Do not click “Save”. Go to OTNM or devcfg, right click the new NE and choose ping.

Read DB again after you can ping the new Node.

Verifying the uploaded NE Exit the DevCfg and choose NO in prompt “Save modification to file?”.

Downloading the Management Config of NE Open OTNM2000. Click the Part that contain the new site in OTNM2000 Logical Tree.

In the Task Panel(located on rightmost of OTNM screen), click “Management Configuration” . Click “Yes”.

Uploading multiple sites Condition: You have finished the NE creation of the site/s in devcfg. Next Step: Detecting the new NE SN/IP Address and Synchronizing it to the live network. Caution: Example: If you have 3 new sites to upload, to avoid errors, upload the site one by one. And always click no when saving modifications to file. You can “ download management configuration” on sites if they are in the same part(e.g Tuguegarao Part).

Contents


NE Configuration  NE configurations include all configuration

information of Metro-E/CEN devices: interfaces, protocols, service information, and protection information.  After service configuration is completed on the multi-

service management GUI and delivered, corresponding records are generated on the NE Config GUI.

Service Configuration Process  Configure Management port  Configure NNI port  Configure OSPF protocol  Configure RSVP protocol  Configure LDP protocol  Configure UNI port  Configure Tunnel.  Configure VC.  Configure L2VPN .

NE Configuration Right-click an NE and select NE Config from the shortcut menu.

NE Configuration – Management Port NE configuration:

NE Configuration - Port Configuration Management port Key Parameter

Parameter Description

name

Indicates the name of a management port. Usually, an Ethernet port is named "eth+SN", and a loopback port is named "loopback". In Smart CEN: lo0

type

Indicates the type of a management port. LOOPBACK: To facilitate router management, the IP address of the LOOPBACK port is used as the management address and used for remote login of routers. ETHER: This port is used as a virtual network interface.

prim ip and prim mask

The IP address is set according to the project planning. The mask is usually 32 bits long.

NE Configuration - Port Configuration Management ports

 A management port must be configured for each Metro-E NE. This port

identifies a device on the network.  prim ip: This IP address must be unique and set according to planning.  The IP address cannot start with 0, that is, the IP address cannot be 0.X.X.X.

NE Configuration - Port Configuration Logic interfaces

NNI Interface

L3 Interface TP Interface

Logic Interface UNI Interface

L2 Interface L3 Interface

NE Configuration - Port Configuration Logic interfaces L3 Interface: Between Metro-E devices NNI Interface TP Interface: Between Metro-E and PTN

L3 Interface: For L3VPN services, include L3VPORT UNI Interface L2 Interface: For L2VPN services, include L2VPORT

NE Configuration - Port Configuration Logical interfaces Key Parameter

Parameter Description

Add(Button)

Add Sub Eth-Interface(Configure VLAN according to service needs.)

Check update(B)

Automatically update all the card’s port you have configured in devcfg.

Port mode

Select L2, L3, or TP (for interconnecting with PTN devices) according to the port type.

ip_mode

For L3 and TP ports, manually specify the IP mode; for L2 ports, retain the default value.

prim ip and prim mask

For L2 ports, you do not need to set these two parameters; for L3 and TP ports, set the IP address normally.

RSVP enable

To implement dynamic services, enable RSVP for the L3 NNI.

LDP enable

To implement dynamic services, enable LDP for the L3 NNI.

MPLS enable

NNI for L3 port

NE Configuration - Port Configuration Logical interfaces

L2 UNI interface

 VLAN: Just click “Add” button and enter the VLAN value according to planning.  Port mode: Select L2 from the drop-down list.

NE Configuration – Port Configuration Ethernet Interface Configuration: •General Info: Port Description •Physical Property Tab Operating Mode: Full, Half or Self Negotiate Duplex mode Photovoltaic Mode: Electrical or Laser mode Port Rate Type: Auto(Default), 10/100/1000 Mbps •Ethernet Property Tab, Select L3 for NNI interface and L2 for UNI. Check rsvp and mpls (for L3) Write the subnet mask and the interface IP Address (applicable for L3)

NE Configuration - Port Configuration Logic interfaces

L3 port

 VLAN: Just click “Add” button and enter the VLAN value according to planning.  Port mode: Select L3 from the drop-down list.  IP addresses are manually specified.

prim_ip_addr: Enter the IP address according to planning. prim_ip_mask: Enter the IP mask. mpls_en: If for NNI,select Yes else ignore it. Note: If dynamic services are involved, enable LDP and RSVP for the NNI and perform configuration according to actual protocols.

NE Configuration - Port Configuration Logic interfaces Configuration rules for logic interface IP addresses:

A logic interface IP address cannot be 0.x.x.x. The loopback IP address 127.X.X.X cannot be specified as the logic interface IP address. A logic interface IP address cannot start with 224 or larger, for example, 224.x.x.x. The mask bit cannot be all 0s or all 1s. For example, if the mask is 24, the last bit cannot be 0 or 255. If the mask is 30, the last bit cannot be 4*X or 4*x+3. For the ports on the same NE, their IP addresses cannot belong to the same network segment. Except for loopback interfaces, the mask of other interfaces cannot be 31 or 32.

NE Configuration - Port Configuration CES interface

• CES interface name – Example of STM-1 card: STM1-CES0/18/1.20 • STM1-CES0 is the fixed prefix of STM-1 cards. • 18 indicates the slot number of the card. • 1 indicates the first STM-1. • 20 indicates the 20th E1 timeslot in the STM-1.

– Example of E1 card: E1-CES0/19/3 • E1-CES0 is the fixed prefix of E1 cards. • 19 indicates the slot number of the card. • 3 indicates the third E1 timeslot.

NE Configuration - Port Configuration CES interface 1) STM1-CES interface

2) E1-CES interface

NE Configuration - Protocol Configuration • RSVP: Resource Reservation Protocol – Set php to No, and retain the default settings other parameters.

PHP: Penultimate Hop Popping. It is recommended that PHP be disabled.

NE Configuration - Protocol Configuration • LDP: Label Distribution Protocol

• ldp_advert_trigger  Select host-only. Tunnel and PW labels can be distributed.

• transport_addr  Usually, it is set to the IP address of the local loopback interface.

• LDP_Item_Peer  Remote IP address

Note: Configure the protocol according to the device supporting capability and actual networking scheme.

NE Configuration - Protocol Configuration IS-IS: Intermediate System to Intermediate System Parameters to be configured:  IS-IS Basic

•

Tag: IS-IS area ID

•

Type: Level 1, Level 1 /2 , Level 2 IS-IS level

•

Net: 47.0(3 digits is the isis area).0(3 first digits of Management IP).(Next 4 digits of Management IP).(Last 4 digits of Management IP).00

Example: ISIS area is 200 and Mgt IP is 10.112.136.278 Net is 47.0300.0101.1213.6278.00 •

Wide metric: enable

•

Wide metric level: same with Type

•

MPLS TE: enable

•

CSPF: enable

•

TE Route ID: Loopback IP address

NE Configuration - Protocol Configuration

IS-IS Basic Figure 1

Figure 2

Figure 3

Figure 4

NE Configuration - Protocol Configuration IS-IS Interface Configure for the loopback interface and NNI L3 Ports  Example:



ifname: Port Name(e.g. Loopback0 or XGE0/3/1)



tag: IS-IS Area (e.g. 300)



circuit type: level_1 or level1_2

Service Configuration - Static Service Configuration Process and Common Models Creating a static L2VPN service    

Configure the UNI port. Create an L3 port as the NNI port and create a tunnel. Create a VC. Create a service on the VC.

Rules:  The tunnel port must be a MPLS-enabled L3 port.  Before delivering a service, ensure that tunnels and protection pairs have been delivered.

Service Configuration - Configuring Tunnels Right-click a project and select Business Management from the shortcut menu. The Business Management View GUI is displayed.

Service Configuration - Configuring Tunnels On the Business Management View page, choose Service Configuration > IP config > Tunnel Config.

Service Configuration - Configuring Tunnels Tunnel parameter list Parameter Name

Meaning

Path Name

Name of the created tunnel. Set the tunnel name as planned or leave this field blank.

Signaling

Specifies whether a static or dynamic tunnel is to be created.

Protection

No protection or 1:1 path protection

Source and Sink LSR

Source and sink NEs of an LSP tunnel (a port must be specified for the PTN NE).

Preset Label

Forward and reserve labels

BFD&OAM

Determine whether to enable BFD or OAM based on the failure detection mechanism. For a mixed tunnel from the PTN to the Metro-E, enable proactive OAM. For a tunnel between MetroEs, enable BFD.

Routing Constraints

The EMS enables automatic routing. To make the LSP traverse specific NEs or ports, you can specify the NE that the tunnel must pass through.

Service Configuration - Configuring Tunnels Unprotected static tunnel

Service Configuration - Configuring Tunnels As shown in the figure, select the source LSR and sink LSR and specify the preset labels.

Constraint-based routing (default settings can be retained)

Service Configuration - Configuring Tunnels The EMS enables automatic routing. Click Completed to complete tunnel configuration.

Service Configuration - Configuring Tunnels The following figure shows the detailed routing information of the tunnels.

Service Configuration - Configuring Tunnels Configure a protected tunnel and select 1:1 Trail Protection for Protection.

Configure the failure detection mode.

Service Configuration - Configuring Tunnels Enable automatic routing and complete the working path configuration according to the preset labels.

Service Configuration - Configuring Tunnels After the working path is configured, proceed with the protection path configuration.

Service Configuration - Configuring Tunnels Configure the protection attributes. Up to now, now, the tunnel configuration is complete.

Note: LDP to peer site must be configured/established after tunnel configuration.

Service Configuration - Configuring VCs To add a VC, choose Service Configuration > IP config > VC Config.

Service Configuration - Configuring VCs Alternatively, Alternatively, right-click a tunnel and select Add Metro-E VC Circuit from Circuit from the shortcut menu (recommended).

Service Configuration - Configuring VCs VC parameter list Parameter Name

Meaning

VC Circuit

Name of a VC circuit. Ex: 20160617 1052am

User Label

VC circuit label set by the user. user. Can be the riding service(ex. N1601 3G)

Signaling

Dynamic or static signaling type, corresponding to dynamic or static VCs.

Source and Sink

Source and sink nodes of a VC.

Positive and Reverse

VC label.

BFD&OAM

Select whether to enable BFD or OAM. When PW protection is configured, enable proactive OAM.

Service Configuration - Configuring VCs Configure basic information.

Select service layer circuit and complete the configuration.

Service Configuration - Configuring L2VPN Services The E-LINE service can be configured only after Ethernet/CES ports, tunnels and VCs are configured.

Service Configuration - Configuring L2VPN Services To configure E-LINE services, choose Service Configuration > IP config > L2VPN Config.

Service Configuration - Configuring L2VPN Services Alternatively, right-click a VC and select Add ETH Service from the shortcut menu.

Service Configuration - Configuring L2VPN Services Configure the service type. ex: 3835 S2P1 VLAN 2432

Select the source NE, sink NE, source port, and sink port.

Service Configuration - Configuring L2VPN Services Select the VC that carries the E-line.

Service Configuration - Configuring L2VPN Services E-Line service configuration

Service Configuration - Configuring L2VPN Services

There are 7 IS-IS Areas in the Smart CEN Network.

Service Configuration - Configuring L2VPN Services E-LAN can be configured on VPLS or HVPLS setup. In CEN Terms, VPLS (Virtual Private LAN Service): Composed of one destination NE and many source NE, all belongs in the same IS-IS Area. HVPLS (Hierarchical VPLS): Composed of one destination NE, a middle NE and many source NEs. Middle and Source NEs belongs to the same IS-IS Area and different from the Destination NE.

Service Configuration - Configuring L2VPN Services The E-LAN service can be configured only after Ethernet/CES ports, tunnels and VCs are configured. For HVPLS, we need two tunnels and VC / Pseudowire 1. Destination to Middle NE tunnel and VC 2. Middle NE to Source NE tunnel and VC For VPLS, only one tunnel and one VC is needed for each E-LAN service. Destination to Source NE tunnel and VC.

Service Configuration - Configuring L2VPN Services Open Business Management. On Service configuration Tab, select IP config then L2VPN. Parameter Name

Meaning

Service Name

Client Info

The service (e.g. TDLTE)

Service Type

E-LAN

Select an NE Choose the Destination Node first, then the Middle Site(for HVPLS) then the Source Site.

Service Configuration - Configuring L2VPN Services Select two tunnels and two VC.

Service Configuration - Configuring L2VPN Services Configure Split Horizon and cross connect mode on UNI and NNI.

For HVPLS, •Destination Site UNI Cross connect mode: VPLS NNI split horizon: enable •Middle Site Source to Middle Site NNI split horizon: enable Middle to Destination Site NNI split horizon: disable •Source Site UNI Cross connect mode: VPLS UNI split horizon: enable NNI split horizon: disable

For VPLS, •Destination Site UNI Cross connect mode: VPLS •Source Site UNI Cross Connect mode: VPLS UNI split horizon: enable NNI split horizon: disable

Service Configuration - Configuring L2VPN Services Select cancel before delivering the service’s cross connect.

Right Click the E-LAN with the partly Active status and select " Deliver Crossconnect of the selected path". Select “Download”.

Service Configuration - Configuring L2VPN Services E-CES service Select the service type.

Select NEs and ports.

Service Configuration - Configuring L2VPN Services E-CES service Select the VC that carries the service (usually, the default setting can be retained).

Configure flow classification values (usually, the default settings can be retained).

Service Configuration - Configuring L2VPN Services Deleting a static L2VPN service  Delete the L2VPN.  Delete the VC (if the protection relation exists, delete it first).  Delete the LSP that carries the VC (if the protection relation exists,

delete it first).  Delete the UNI port.

Rules:  An LSP can be deleted only after the service carried by it has been

deleted.  A UNI port can be deleted only after the VC is deleted.  A UNI port can be deleted only after the LSP is deleted.

Functions of Multi-service Management Platform

 Powerful service configuration function

 Personalized search and location mechanism

 Other features and functions

Powerful Service Configuration Function Support various device services such as SDH, PTN, OTN, Metro-E, and POTS.

Powerful Service Configuration Function

 List route

details.

 List circuit

data by types.

Personalized Search and Location Mechanism

Quickly locate the corresponding tunnels or VCs from the service.

Personalized Search and Location Mechanism

Quickly locate VCs, services, or protection groups from a tunnel.

Personalized Search and Location Mechanism Support various filter operations.

Personalized Search and Location Mechanism Support various filter operations.  Support filter by

source NE, sink NE, source port, sink port, or intermediate port.  Support filter by network layers (VCs or tunnels), service types (PTN or SDH), or circuit status (to-beactivated or activated).  Support full filter

and incremental filter.

Practice Device Configuration -Create a new node “COMMEL” under Tuguegarao SB3 Part -NE IP: 10.6.19.6 -SM: 255.255.255.0 COMMEL slot 3 port 1 <> BAYOMBONG TP slot 4 port 1

Practice E-CES Scenario/Condition 1: No created tunnel New E1 service configuration Scenario/Condition 2: -There is available tunnel. -New E1 service. -Setup is STM-1 port to E1 port. Scenario/Condition 3: -Need to provision E-CES -Source and destination site is on different IS-IS domain -With existing Static tunnel source to a site(MAIN DOMAIN ROUTER) that has protection and a tunnel from destination site to that last site with protection(with west and east link) -source site has no protection

Practice E-LINE -Create E-Line Service using Dynamic Tunnel -Create E-Line Service using Static Tunnel

Practice E-LAN VPLS Scenario/Condition 1: No existing tunnel. For creation of new 3G service on the source site. Scenario/Condition 2: -With existing tunnel. -With existing 3G Service linked to the Destination Site port and VLAN. -For adding of new node Scenario/Condition 3: -With existing Tunnel and Service. -For adding of port to the existing Node of the existing service. Scenario / Condition 4 -Existing 3G service -You will be adding a site which is on a different ISIS domain.

Practice E-LAN HVPLS Scenario/Condition 1: -To create new TD-LTE service -LTE service has 3 VLAN sub-interface. -No tunnel created yetHas a middle site Scenario/Condition 2: -We have an existing tunnel (Source site to Middle Site and Middle site to Destination site). Where middle site is L2 Core Layer Router. -We have an existing TD-LTE service. -We will be adding a node to this existing service Scenario/Condition 3: -We have an existing tunnel -TD-LTE service is existing. -You will add a new port on the existing NE of the TD-LTE service.

3-CEN Service Configuration

Recommend Documents