3_OptiX ASON V100R002 Deployment Guide

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

Huawei Confidential

Security Level: Internal Use Only23/4/10

Ling Yongwu/92683

OptiX ASON V100R002 Deployment Guide

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Preface

This course is developed based on the Optix GCP

Deployment Guide V1.2X.

This course aims at guiding technical support engineers

to complete the ASON features deployment of OSN

series products.


Learning Guide

This course is organized according

to the contents in the OptiX GCP

Deployment Guide V1.2X.

Before learning this course, you are

suggested to learn the OptiX ASON

Principles.


Learning Guide Key Points

Methods of enabling ASON features

FAQs of enabling ASON features

Methods of creating, deleting, optimizing,

converting, and upgrading/downgrading basic

ASON trails/ASON tunnels

Methods and points for attention of the ASON

feature test

Hard Points Service configuration method of mixed

networking of traditional NEs and ASON NEs

Deployment process of traditional network

with services enabled upgrading to ASON

network


Reference

OptiX GCP User Guide (V100R002_02)

OptiX GCP Deployment Guide V1.20


Objective

After learning this course, you can grasp: Detailed operations of enabling ASON features of OSN

devices

FAQs of enabling the ASON features

Methods of creating, deleting, optimizing, converting, and

upgrading/downgrading basic ASON trails/ASON tunnels

Service configuration method of mixed networking of

traditional NEs and ASON NEs

Deployment process of traditional network with services

enabled upgrading to ASON network

Methods and points for attention of the ASON test


Contents

ASON Features Deployment

Procedure ASON Features New Deployment Procedure

Traditional network with services enabled upgrading to

ASON network

ASON Feature Test


ASON Features New Deployment Procedure

PreparationsPreparations

EnableEnable ASON ASON

featuresfeatures

• Control channel verification

• Data link verification

• TE link verification

Create ASON Create ASON domaindomain

Necessary Necessary settingssettings

Auto create fiberAuto create fiberOptional Optional settingssettings

• Create SRLG

• Create link distance

• Reserve link resource

• Create/modify ASON Create/modify ASON domaindomain

• NE synchronizationNE synchronization

• Secondary NE Secondary NE configurationconfiguration

Create ASON Create ASON servicesservices

• ASON service• Tunnel service• Service association• Scenario service• Path constraint• Service optimization• Service conversion

Manage Manage ASON ASON

protocolprotocol

Plan MSPlan MS

• Deployment Deployment requestrequest• Hardware Hardware configurationconfiguration• NE NE commissioningcommissioning•Network Network commissioningcommissioning

• Create logical board• DCC setting•NODEID setting


Deployment request

Currently, the deployment of ASON feature versions of OSN products must be

backed up in HQ. The backup application scope covers demonstration, test

and commercial use. Thus, no matter whether the ASON features are

included in the market sales contract, all the ASON features deployment must

be approved through the process. The operation method is as follows: Before the OSN ASON features deployment, the front line customer service

personnel must ask for the HQ approval. The Market department must apply for the ASON features deployment from the HQ. The request must be approved by the manager of OSN PDT.

Before the application of ASON deployment, fill in the version application form, which must be attached with the mail or file formally approved by the OSN PDT manager.

After the version request is approved, the regional office/representative office can use the version to enable the ASON feature.

Preparations


Apply for ASON features deployment version

Deployment version related with ASON R2

OSN 9500: V100R004

OSN 7500: V100R006

OSN 3500: V100R006

OSN 2500: V100R006

OSN 1500: V100R006

NMS T2000: V200R004CO1 and later version

Preparations


Apply for two SCC boards (in the case that only one SCC is

provided according to the contract) OSN 9500: SSJ2JSCC/SSJ3JSCC, SSJ3ESCC OSN 7500: SSN2GSCC, SSN3GSCC OSN 3500: SSN1GSCC, SSN3GSCC OSN 2500: SSQ2CXL OSN 1500: SSQ2CXL

Implement NE commissioning Make sure 100% accuracy of the 2M lines. Make sure there is no fault on the board.

Implement network commissioning Make sure the system performance is good and there is no error in 24

hours. Make sure 100% accuracy of the fiber connection.

Preparations





featuresfeatures







• Create SRLG



• Create/modify ASON domain

• NE synchronization

• Secondary NE configuration




protocolprotocol

Plan MSPlan MS




Some services may be configured on NEs during NE commissioning and

network commissioning. To initialize NEs for deleting the configuration,

perform the initialization before enabling the ASON features. Skip this

step for certain NEs, on which services are operating.

Logical boards must be created before enabling the ASON features. The

logical boards must be identical with the physical boards. If the logical

slots are not created or the logical slots and physical slots are not

identical, data links cannot be generated.

Question:

What channel of LMP protocol is related with the physical slots?

Initializing the NE and Creating Boards


Querying/Setting DCC Bytes

Product SCC Default DCC Channel Mode

OSN9500

J3ESCC 288, 288, 0

J2JSCC

J3JSCC

252, 252, 0

OSN7500

N2GSCC

N3GSCC 40, 40, 0

OSN3500

N1GSCC 10, 10, 0

N3GSCC 40, 40, 0

OSN2500&1500 Q2CXL 10, 10, 0

The DCC mode settings of NEs to be enabled ASON features must be consistent with the contents in the table.


Before setting, query the current configuration. If the

current configuration meets with the requirements,

modification is unnecessary. If not, re-set DCC bytes. You

can query and set the DCC bytes on T2000.

On the Main View, select the target NE. Right-click and select NE

Manager.

Select Communication > DCC Management from the Function Tree.

Select the DCC Resource Allocation tab to set parameters as shown in

the following figure.



You can also query/set the DCC bytes by using the

following command lines: :cm-get-dccpara This command is used to query the DCC channel

allocation mode and use condition.

:cm-get-chanallocinfo This command is used to query the DCC

channel allocation mode provided by the devices.

Or, use the command :cm-get-chanmode to query the DCC channel

allocation mode used by the devices.

:cm-set-dccpara or :cm-set-chanmode The commands are used to set

the DCC channel allocation mode.

After changing the DCC channel allocation mode, you need to soft reset the SCC to validate the settings. If you use T2000 for setting and modification, the NEs automatically soft reset the SCC after you click Apply in the setting window. If you use the command line for setting and modification, you need to manually soft reset the SCC. It is recommended to let NEs automatically soft reset the SCC after setting the NE NODEID in the next step.



Before enabling the ASON features, set the node ID of the ASON NEs.

NODE ID is the unique identity of an NE in the ASON control plane. If

you change the NODE ID after enabling the ASON features, this will

confuse the ASON control plane and as a result services are

interrupted. The features and setting requirements of NODE ID are as

follows: In one ASON domain, the NODE ID cannot be repeated.

The format of NODE ID is x.x.x.x. The parameter x ranges from 1 to 254. The

NODE ID cannot be in the same network segment with the NE IP address.

Set the NODE ID before enabling the ASON software. After the setting, the NE

automatically soft reset the SCC.

After the network is put into use, do not modify the NODE ID. If modification is

required, modify when there are no ASON services. After the modification, note

the ASON NEs adjacent to the soft reset.

Setting NE NODE ID


The following network segments are recommended for

NODEID:

172.16.0.0 — 172.31.255.255 (172.16/12 prefix)

10.0.0.0 — 10.255.255.255 (10/8 prefix)

192.168.0.0 — 192.168.255.255 (192.168/16 prefix)

If the customer wants to select an address out of the recommended

network segments, contact the HQ experts because some addresses

cannot be used as the NODEID.

Use the following commands to query and set the NODEID.

Currently, T2000 does not support this function.

:icon-get-node-id This command is used to query the NODE ID of the local

NE.

:ion-set-node-id This command is used to set the NODE ID of the NE.

After the setting, the NE automatically performs soft reset. ）

Setting NE NODE ID





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS

• Deployment Deployment requestrequest• Hardware Hardware configurationconfiguration• NE NE commissioningcommissioning• Network Network commissioningcommissioning



Enabling ASON Features

After the previous steps are completed, make sure all NEs are

in running state before enabling the ASON features. :cfg-get-nestate This command is used to query whether the NE status is

running.

:cfg-set-itgattrib:enable This command is used to enable the NE ASON

features.

:cfg-get-itgattrib This command is used to query whether the ASON features

are enabled for the NE.

After the ASON features are enabled, you can use the command

to disable the ASON features. The prerequisite for successful

command execution is that the current NE has no ASON

services. If ASON services exist, a failure prompt is returned

after you carry out the command to disable the ASON features. :cfg-set-itgattrib:disable NEs automatically perform soft reset after sending

the command of disabling ASON features.





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




Querying Status of Control Channel

:lmp-get-ccbyport:0,0:lmp-get-ccbyport:0,0

LMP_GET_CC_BY_PORT

LocalCCID LocalBid LocalPid AdminStatus OperStatus NbrNodeID RemoteCCID DestAddr NextHop

0x00000001 7 1 AdminUp up 9.1.1.2 0x00000001 9.1.1.2 9.1.1.2

0x00000002 10 1 AdminUp up 9.1.1.4 0x00000002 9.1.1.4 9.1.1.4

0x00000003 12 1 AdminUp up 9.1.1.3 0x00000001 9.1.1.3 9.1.1.3

0x00000004 11 1 AdminDown down 0.0.0.0 0000000000 224.0.0.1 224.0.0.1

0x00000005 11 2 AdminUp config_snd 0.0.0.0 0000000000 224.0.0.1 224.0.0.1

Total records :5

Query through the command line:

Query through the NMS:

As shown in the red circle, the operation status of relevant optical port is Up, which means the verification passes.


Querying Status of Control Channel

To avoid the limitation on the number of control

channels in the config_snd status, ASON R2 version

does not create control channels for low-rate line

port (STM-1/4) by default. The low-rate ASON optical

channels must be created manually. The command

lines are shown as follows:

:sc-set-cc-available:Bid,Pid,enable/disable This command is used to

create the control channel of relevant optical ports.

:sc-get-cc-available:0,0 This command is used to query whether the

control channels are created on the optical ports.


Querying Status of Data Link

LMP_GET_DBL

LocalDblID LocalBid LocalPid AdminStatus OperStatus RemoteDblID

0x4c000001 7 1 AdminUp up_free 0x4c000001


0x4c000003 11 1 AdminDown down 0000000000

0x4c000004 11 2 AdminUp down 0000000000


Total records :5



:lmp-get-dbl:0,0:lmp-get-dbl:0,0

As shown in the red circle, the operation status of relevant optical ports is Up/Free, which means the verification passes.


Querying Status of TE Link

LMP_GET_TEL

LocalTelID LocalBid LocalPid AdminStatus OperStatus NbrNodeID RemoteTelID Verify

0x6c000001 7 1 AdminUp up 9.1.1.2 0x6c000001 enable


0x6c000003 11 1 AdminDown down 0.0.0.0 0000000000 enable

0x6c000004 11 2 AdminUp down 0.0.0.0 0000000000 enable


Total records :5



:lmp-get-tel:0,0:lmp-get-tel:0,0

As shown in the red circle, the operation status of relevant optical port is UP, which means the verification passes.


Three Optical Channels to Be Noticed

D1D1D2D2

A1A1

BB

AA DD

Optical channels between ASON Optical channels between ASON

NEs and non-ASON NEsNEs and non-ASON NEs

Optical channels Optical channels

between two ASON between two ASON

NEs but not provided NEs but not provided

for ASON featuresfor ASON features

Non-ASON

ASON

CC

Disable the LMP protocol of the first and second optical channels not provided for ASON features.

Optical channels between Optical channels between

two ASON NEs and two ASON NEs and

provided for ASON provided for ASON

featuresfeatures


Disabling/Enabling LMP Protocol

:sc-set-lmp-adminstatus:bid,pid,AdminStatus:sc-set-lmp-adminstatus:bid,pid,AdminStatus

By disabling the LMP protocol, you can disable the control channels, TE links and data links.

Interface Entry: NE manager/ASON/Advanced maintenance/ASON protocol management

Disable the LMP protocol of optical channels not provided for ASON features.


There are three interfaces related to the OSPF protocol:

Port of the ASON NE connecting to ASON NE fibers

Ethernet port of the ASON NE

Port of the ASON NE connecting to non-ASON NE fibers

The first port uses the OSPF protocol by default but the second port does not. The two ports use the default settings directly. Do not modify them.

The default setting of the third port also uses the OSPF protocol. Because the third port connects with non-ASON NEs, you need to manually disable the OSPF protocol of the port.

Disabling OSPF Protocol


Interface Entry: NE manager/ASON/Advanced maintenance/ASON protocol management

Use the following commands to disable or enable the OSPF protocol of relevant ports:

:lim-set-ospf: bid,pid,0,disable/enable This command is used to disable/enable the OSPF

protocol.

:lim-get-ctrllink:0,0 This command is used to query relevant interfaces of whether the OSPF

protocol is enabled.

Disabling OSPF Protocol


R2 adds the encrypted transfer of RSVP and OSPF message functions, which are mainly to prevent the messages from being listened in or divulged and to improve the network security. For the encryption function of the OSPF and RSVP protocols, it is recommended to use the default values. MD5 certification is the default value of OSPF, and the certification code is AOSV100R002. The default value of RSVP is no certification. Do not modify the default values: If the encryption function is required, pay attention to the following:

Certification support: no certification, simple plain text certification (not

supporting RSVP), MD5 certification

RSVP certification configuration is for nodes and the OSPF certification

configuration is for ports (boards and optical ports). The certification passes

only when the certification configuration of the two nodes are consistent.

Make sure the certification types of OSPFs in the same ASON domain must

be consistent and the RSVP in the same ASON domain must be consistent.

Encrypting OSPF and RSVP Protocols


Encrypting OSPF and RSVP Protocols

Interface Entry: NE manager > ASON > OSPF Protocol

Management

Interface Entry: NE manager > ASON > RSVP Protocol Management





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




Creating/Modifying ASON Domain

After the NE enables the ASON features and the NMS reload the NE data, query and

open the NE list of the ASON features in the ASON topology management. Make sure

the NMS can normally detect the NEs that already open the ASON features and

modify the ASON domain name based on the actual condition.

Interface Entry: Main Menu > Configuration > ASON Topology

Management > ASON Domain


After creating the ASON domain, manually synchronize the NEs

and make sure all NEs are added into relevant ASON domain. Interface Entry: Main Menu > Configuration > ASON

Topology Management > ASON Domain

NE Synchronization


Configuring Secondary NE

In the ASON network, each ASON NE stores the topology information of the

entire network. The NMS only needs to communicate with one NE, which is

called "communication NE". Set the Active NE and Standby NE to select the

communication NE. The NMS select the active NE as the communication NE

first. If a fault occurs on the active node, the standby NE acts as the

communication NE.

Interface Entry: Main Menu > Configuration > ASON Topology Management

> ASON Domain





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




Creating Fiber Automatically

In ASON R2, the number of TE links is equal to the number of

optical ports; that is, each optical port relates to a TE link. Create

the fiber based on the TE links. The fiber connection between

ASON NEs in the ASON domain can be automatically created

through this function.

Interface Entry: Main Menu > Configuration > TE Link

ManagementSelect all TE links

Press Create Fiber





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




Creating SRLG (Optional)

Shared risk link group is abbreviated as SRLG. Generally,

fibers in the same cable have the same risk, that is, if the

cable is cut off, all fibers in the cable are cut off. In this

case, the rerouting of ASON services should not be on the

links with the same risk. Thus, correctly set the SRLG for

the links with the same risk in the network.


Management


Creating Link Distance (Optional)

When creating ASON trail or rerouting, users need to set the link

distance as required to ensure that the path of long link distance is

not selected during service creation and rerouting.


Management


Reserving Link Resources (Optional)

Besides creating ASON services, you can also create traditional services on

the ASON network. Reserving link resources is to reserve partial timeslots

of the links for creating traditional services. The reserved timeslots cannot

be used when creating ASON services or during the ASON services

rerouting. There are two ways to reserve timeslots:

Interface Entry (method one): NE > NE Manager > Functional Tree of

Relevant Boards > ASON > Resource Reservation

The resources are reserved or canceled at the same time on both ends of the link.


Reserving Link Resources (Optional)

Interface Entry (method two):

Main Menu > Configuration > Component Link Management > Select

relevant link and right-click > Set ASON resources reservation





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




Planning MS

Before creating ASON services of any level, confirm the

planning of the multiplex section (MS) and make necessary

service planning. During planning, fully consider the future

expansion requirements and ask for the opinions of the

customer. After reaching an agreement with the customer,

create the multiplex section and then the ASON services.

New functions of multiplex section planning supported by ASON R2 Dynamic add and delete functions of the multiplex section

Dynamic adjustment functions of the multiplex section bandwidth

For 2.5G/10G line board, support the NG-SDH to configure multiple

multiplex sections on one link.

Multiplex sections supporting ASON service creation

1:1 linear multiplex section

Two-fiber bidirectional multiplex section

Four-fiber bidirectional multiplex section





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS




ASON Services

Creating ASON Services

Creating Tunnel Services

Service Association

Creating Services with Different Scenarios

Route Restriction

Service Optimization

Service Conversion

Case Analysis


Interface Entry

Configuration > ASON Trail

Management > Create

Properties of ASON trail

ASON trail (including 5 types):

Diamond

Gold

Silver

Copper

Iron



Interface Entry Configuration > ASON Trail Management >

Create > Rerouting Attributes

Description of major setting items:

Revertive Mode (set as required) WTR Time (600-43200, default value is recommended) Lockout (the default value is recommended) Priority (the default value is recommended) Trigger Condition (valid for diamond services, set the value as required) CrankBack (the default value is recommended) Policy (set as required)



ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis



Tunnels also called "ASON trails" are used to carry VC12 or

VC3 lower-order services.

The supported protection types include: gold, silver (non-revertive),

and copper tunnel services.

Currently, only the tunnels of VC4 class are supported; however, VC4

class services cannot be loaded.

The cross-connection from the tributary to the line needs manual

creation and deletion.

When rerouting or optimization occurs on tunnel services, the cross-

connection of the source and sink NEs automatically switch to the new

port without manual interference.

Support converting tunnel services to the channel of static service

layer.


Interface Entry


Management > Create

ASON trail property

ASON service trail (including 3 types):

Gold Silver Copper



Interface Entry Configuration > ASON Trail Management >

Create > Rerouting Attributes

Description of configuration items:

Lockout (the default value is recommended)

Priority (the default value is recommended)

CrankBack (the default value is recommended)

Policy (set as required)



Configure segmented tunnel services

The main function of segmented tunnels is to improve the resource

utilization of each tunnel and enable the middle NEs of the tunnel to

operate services.

NE1

NE2Tunnel 1

Tunnel 2

Lower order

services from

NE1 to NE2

Lower order

services from

NE1 to NE3NE3



ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis


Association services are similar to diamond services, and used for the

service containing two access points. An association service remembers the

peer LSP ID to associate two common services. During the rerouting or

optimization of an LSP, the remove strategy of 1+1 route is adopted to avoid

secondary associated LSP; thus, co-bearing a service to improve the

protection level.

Support the association between silver services, between copper services, and between

silver services and copper services.

Support the service association between the same or different source and sink nodes, and support the association between silver tunnels, between copper tunnels and between silver tunnels and copper tunnels. Two two-end tunnels can be associated. Two single-end tunnels of the same time (indicating the source or sink single-end) can also be associated.

The association of diamond services is not supported, and neither is the association of gold services.

Service Association


Service Association

Method One: Interface

Entry


Management

Select two ASON trails on the

list. Right-click and then select

Set Association.


Service Association

Method Two: Interface Entry

If there are many ASON trails and the

two trails to be associated are far from

each other on the list, you can associate

them as follows. Select Configuration >

ASON Trail Management. Right-click an

ASON trail from the ASON trail list, and

select Set Association Source. Find

another ASON trail to be associated on

the list, and select Set Association.


ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis


According to the networking, there are five scenarios with

regard to services:

ASON services from ASON NEs to ASON NEs (VC4)

Tunnel services from ASON NEs to ASON NEs (VC3/VC12)

ASON services from non-ASON NEs to ASON NEs (VC4)

Tunnel services from non-ASON NEs to ASON NEs (VC3/VC12)

Configure associated silver tunnel services



Method of service creation

END

ASON Services from ASON NEs to ASON NEs (VC4)



regard to services:








Step 1: Interface Entry: Trail > SDH Trail Creation to create VC4 service trail

Tunnel Services from ASON NEs to ASON NEs (VC3/VC12)


Step 2: Set attributes of the ASON service trail in the displayed dialog box.

Step 3: Click OK to return to the Create SDH Trail window. Then, click Apply.



Step 4: Interface Entry: Trail > Create SDH Trail to create the VC12 service.

END




regard to services:








Step 1: Interface Entry: Trail > Create SDH Trail to directly create the VC4 service.

ASON Services from Non-ASON NEs to ASON NEs (VC4)


Step 2: Set attributes of the ASON trail in the displayed dialog box.


END

ASON Services from Non-ASON NEs to ASON NEs (VC4)



regard to services:








Note

This type of service is called single-end tunnel service. The single-end tunnel service refers to that the lower order cross-connection is created on one end of the tunnel service nodes in the ASON domain.

R2 supports single-end tunnels and can create an end-to-end tunnel service between the ASON NE and non-ASON NE.

NE2

vc12

NE3NE1

NE4 NE5vc12

vc4

Non-ASONASON ASON service trail Traditional service trail

Tunnel Services from Non-ASON NEs to ASON NEs (VC3/VC12)


Step 1: Interface Entry: Trail > Create SDH Trail to create VC4 Server Trail.



Step 2: Set attributes of the ASON service trail in the displayed dialog box.




Step 4: Interface Entry: Trail > Create SDH Trail to create the VC12 service.

END




regard to services:








Configure associated silver tunnel services as follows:

If the silver tunnel association is not set, when rerouting

occurs, the silver tunnel may be overlapped with another

silver tunnel. At this time, you need to manually optimize the

silver tunnel to other routes. Ensure that the routes of two

silver tunnels are separated to implement the 1+1 protection

for VC12 services.

ASON R2 version together with the T2000 V200R004C01

version support the association setting of silver tunnel

services.

Configuring Associated Silver Tunnel Services


Configuring Associated Silver Tunnel Services

Interface Entry: Configuration > ASON Trail Management

A window is displayed as follows. Select two silver tunnel services to set the association.


ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis


Configure through the NMSInterface Entry: Select Configuration > ASON Trail Management > Create in the main menu.

The route restriction includes compulsory and excluded nodes, compulsory and excluded links, loose constraint and strict constraint.

Set the compulsory nodes according to the route sequence; otherwise, the route calculation fails. Specify the compulsory link in the sequence starting from the source node; otherwise, the route calculation fails.

Route Restriction


How can gold services restrict the route?

D

G

F

C

HE

B

A msp1 msp2

Route Restriction


Conditions of gold service restriction: Make sure the timeslots of gold services are consistent on the ring.

For gold services on the same ring, there are two ways to restrict

the route:

a. Perform loose constraint on the service head node.

b. Perform strict constraint on the intermediary node.

For gold services crossing multiplex segment ring, you can loosely

specify a cross-ring node as the compulsory node.

Route Restriction


ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis



After many changes of the topology, the LSP of each service on the ASON optical network is not the optimized. In this case, the optimization function is provided.

Optimization is to create an LSP, switch the optimized services to the new

LSP, and delete the original LSP. That is to say, optimization is to change and

optimize the service route without interrupting services.

When you are optimizing the ASON trail, you can only change the passed

route and timeslot without changing the level and other attributes of the ASON

trail.

Service types supporting the optimization function include: diamond service,

gold service, silver service, copper service, iron service, associated service

and tunnel service.


Interface Entry:Configuration > ASON Trail Management

Select a service to be optimized. Select Maintenance > Optimize Route, and

then select a compulsory node or link for the optimization setting.



ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis


Interface Entry: Configuration > ASON Trail Management

Right-click the service to be degraded, and then select

Degrade to SDH Service.

SPC (ASON service) PC (Permanent service)

Diamond service sncp service

Gold service MS service

Silver service Non-protection service

Copper service Non-protection service

Iron service Additional service

Note: After the degrading, implement NE cross synchronization. Then, select Trail > SDH Trail Search in the main menu. The degraded service can be searched out.

Degrading ASON Services to Permanent Connections


Interface Entry: SDH Trail Management

Click the permanent connection to be upgraded, right-

click and then select Upgrade to ASON Trail.

PC (Permanent service) SPC (ASON service)

sncp service Diamond service

MS service Gold service

Non-protection service Silver service

Non-protection service Copper service

Additional service Iron service

Upgrading Permanent Connections to ASON Services


ASON R2 support direct

online conversion between

diamond, silver and copper

SLAs. Interface Entry:


Management

Right-click the SLA to be

converted, select In-Service

Migration, and then select the

destination SLA.

Conversion Between Different SLAs


The migration from gold ASON services to diamond, silver and copper

services is complex, but the migration can still be performed without

disturbing services. The operation is as follows: If the original service is gold service, to convert to diamond, silver or copper

service, the service must be optimized to a non-protection trail. Degrade the

gold service to static service, change the attribute of the permanent service

(such as adding SNCP protection) and then upgrade relevant permanent

service to the destination ASON service.

If the original service is diamond, silver or copper service, degrade the ASON

service to permanent service. Then, adjust the service time slot or adjust, add

or delete MS based on the actual condition. The objective is to let permanent

service run on the working timeslot of the MS and then upgrade the relevant

permanent service to gold service.

Conversion Between Different SLAs


ASON Services



Service Association


Route Restriction


Service Conversion

Case Analysis


The route calculation failure is prompted when creating the LSP Description:

When creating ASON services by using the NMS, the route calculation failure is returned.

Identification:

Check whether there are available resources on the network. Diamond, silver and copper services can only be created on non-protection trails.

Case Analysis


Errors occur when upgrading static service to diamond service Description:

When upgrading static service to diamond service by using the NMS, the system

prompts the SNCP source and sink are not the trail source and sink, and the

upgrading fails.

Identification:

The problem occurs because static service is not the SNCP service pair. You need to manually change the static service to SNCP service for the upgrading.

Case Analysis


ASOS service degrading fails Description:

When degrading the ASON service to static service through the NMS, the system prompts that

the ASON trail managed by SDH trail cannot be degraded. The degrading fails.

Identification:

If the error information "the ASON trail managed by SDH trail cannot be degraded" is returned, it indicates the ASON service exists in the SDH Trail Management. Delete the service from the network layer on the SDH trail management, and then re-degrade it.

Case Analysis





featuresfeatures







• Create SRLG









protocolprotocol

Plan MSPlan MS



Complete!!

Complete!!


Questions

Q1: What are the steps included in the procedure of ASON new deployment?

Q2: What are the three types of LMP protocol links? What are the relations between them?

Q3: Regarding the five types of services defined by SLA, what are the migration relations?


Summary In this section, we learn:

Basic Deployment Procedure of ASON

Common Service Type Configuration of

ASON

FAQs of ASON Deployment


Contents



Traditional Network with Services Enabled

Upgrading to ASON Network

ASON Feature Test


ASON solutions provided by Huawei can help the OptiX OSN optical

transmission devices OSN9500, OSN7500, OSN3500, OSN2500 and

OSN1500 to easily upgrade from the traditional NE to the ASON NE.

In general, the methods for commissioning the ASON features with services

enabled and commissioning new ASON features are not greatly different.

The methods and procedures are roughly the same. The impact of ASON

features with service enabled is mainly embodied on the reconstruction of

the traditional network; for example, the requirement of two SCC boards,

the change of networking form, the change of the protection subnet and the

adjustment of the services.

Traditional Network with Services Enabled Upgrading to ASON Network


Upgrade of product software version

Requirements on SCC boards of high

performance

Requirements on T2000 license update

If the traditional NMS T2000 does not support the ASON features, you

need to ask the customer to purchase new T2000 license that supports

the ASON features again.

Version requirements: T2000 V200R004 or later

The same as the software and main

control requirements of ASON (R2)

Key Points


Network re-planning For the ASON with service enabled, the network planning and ASON service

planning must be finished before the implementation.

The ASON network is typically networked in MESH mode while the traditional

network is typically networked in ring and link mode. Thus, consolidating and using

current network resources is important. Besides, fiber resources should be added

accordingly for the sake of the ASON network features.

The expansion of partial lines (as required) may relates to the adjustment of board

insertion timeslot.

Re-plan the existing MS based on the actual condition. The ASON R2 version does

not support 1+1 linear MS on the ASON network.

Backing up NE database Before enabling the ASON features, back up the NE database to avoid rollback after

an NE enables the ASON features.

Key Points


Impact on NE attribute settings Allocation of DCC channels:

For the current version of OSN3500&2500&1500, if the DCC channel uses D4-

D12 bytes, the number of DCC channels using D1-D3 bytes will be reduced

accordingly.

NODEID planning:

Before enabling ASON features, the NodeID and IP (including NE IP and IP

used by inner network) in the entire ASON domain must be planned uniformly

to prevent conflicts.

Key Points



FAQs and focus points of traditional

network with services enabled upgrading

to ASON network


Contents



Traditional Network with Services Enabled Upgrading

to ASON Network

ASON Feature Test7


ASON feature test mainly covers the following items:

Automatic discovery and update of resources and topology

Diamond service switchover

Switching time < 50 ms. Mount meters on both ends to solve the timeout

problem. The diamond services adopt two-end switching. If the loop test is

adopted, the 37718 meter will be unable to identify that the switching is

performed twice.

Gold service

Switching time < 50 ms. The switching test timeout problem also exists. Mount

meters on both ends to solve this problem.

Main Contents of ASON Feature Test


Silver service -- switching time < 2000 ms

Service optimization -- switching time < 5 ms

Rerouting lock -- services do not reroute but are interrupted

Batch rerouting -- switching time is long but is less than 2000 ms

Main Contents of ASON Feature Test

For more information, refer to the ASON part in the product acceptance manual.


Item: Test the switching time of diamond services

Meter: Agilent37718

Test mode: single-end test, remote end loop

Test phenomenon: "timeout", which is about 200 ms

Cause: The scan frequency of Agilent37718 meter is 300 ms. The

diamond service is two-end switching.

Note: The problem occurs by probability.

Avoidance: Mount meters on both ends for test

Use ANT20SE meter (50 ms)

Points for Attention During Diamond Service Commissioning


300ms

300ms 300ms

a b

ba

c

Flash Demonstration



Test methods and points for

attention of the ASON feature test


Summary This course mainly covers:

ASON Features Deployment Procedure

FAQs and troubleshooting methods of ASON

feature deployment

Test methods of ASON features

Thank You

www.huawei.com

3_OptiX ASON V100R002 Deployment Guide

Documents

Transcript of 3_OptiX ASON V100R002 Deployment Guide