For the Network shown above for ASON implementation has the following specifications/prerequisites.

• Three OSN 9500 respectively at;

1. 1 x OSN 9500 at Lahore (ID 1582)
2. 1 x OSN 9500 at Faisalabad (ID 1583)
3. 1 x OSN 9500 at Islamabad (ID 1581)

• Two GNE’s respectively at;

1. Lahore (IP Address 129.9.6.46)
2. Faisalabad (IP Address 129.9.6.47)

• The MSP RING is to be configured for the above mentioned nodes according to the following
connections Between wavelengths (192.7—193.2—192.5)
1. Lahore 3-JL64 TO Faisalabad 10-JL64 on 192.7 THz
2. Lahore 12-JL64 TO Islamabad 5-JL64 on 192.5
3. Faisalabad 25-JL64 TO Islamabad 12-JL64 on 193.2 THz.

• Prerequisites for ASON Implementation;

1. J2SCC or higher version (currently we have SSJ2SCC/ OptiX OSN 9500 V100R003C03 (5.15.04.10)).
2. OptiX OSN 9500 V100R003C03 (5.15.04.10).
3. V2R3C01 or higher version; we shall have V2R4C01B01.
• PREREQUISITES FOR IMPLEMENTATION OF ASON;

a) Set the DCC bytes using the following command

: cm-set-dccpara:160,160,0; *a (for OptiX OSN 9500 there are 160 DCC Bytes).

b) Query the current setting by using the command,

: cm-get-dccpara;

Note: If the result is in accordance with the above then no need to make the modification.
Since the total number of DDC bytes supported are limited (OSN 3500/2500/1500 and OSN 7500 supports transmission of 10-and 100
byte DCC bytes respectively) therefore If too many low-rate optical interfaces occupy the DCC resources, some optical interfaces cannot
allocate the DCC bytes and then the ASON links are not passable. For this, query the DCC bytes by using the command,
: cm-get-bdinfo;
Enable or disable the DCC of optical interfaces by using the command,
: cm-set-fiberport.

c) Set the Node ID of the NE using the command,

: ion-set-node-id:X.X.X.X;

Note: NE ID is a unique identification of the NE in the intelligent control plane of ASON. By default the Node ID is set to 0.0.0.0.
After setting the Node ID the SCC auto resets, *a remember warm reset is must as the DCC bytes gets effective after this.
The NODE ID of the ASON NE is the IP address of the control plane where as the IP address of the NE is the IP address of the
management plane. Therefore the IP addresses of both the planes should be in different network segment to avoid any conflict.
Keep in mind that the ASON features can’t be enabled without setting the node ID. Preferred network segments priority wise are
172.016.0.0 ---- 172.031.255.255
010.000.0.0 ---- 010.255.255.255
192.168.0.0 ---- 192.168.255.255
In case of MOBILINK we shall be using priority one;
172.16.0.20 for Islamabad
172.16.0.21 for Lahore
172.16.0.22 for Faisalabad
 d) Enable the ASON features, after installing the SCC with the ASON software, using the following command;
: cfg-set-itgattrib:enable;

Note: The ASON features once enabled can’t be disabled in the present version. Versions later than NG-SDH V1R6 support disabling the
enabled ASON feature with the condition that no ASON services are traveling and the ASON clock mode is not started. The command for
disabling the ASON features is
: cfg-set-itgattrib:disable;

e) Set/query the LMP Link state which caters for two steps. First checking the status of the control channels
and second enabling/disabling of the control channels accordingly. The commands for this purpose
respectively are;
: lmp-get-ccbyport:0,0; *a
For disabling the control channels use the command;
: sc-set-lmp-adminstatus:Bid,Pid,2; *b

Note: The LMP Link State is assumed to be a link that carries the Data links, TE links and the control channels. There are three types of
LMP Links state:
• Connection between two ASON NE’s.
• Connection between two ASON NE’s with ASON features not enabled.
• Connection between an ASON and a traditional NE.

The LMP link state for “1” succeeds in passing through the ASON NE’s and the resources (VC4’s) are occupied by the control channels
when they pass through the ASON NE’s during negotiation. The LMP link state that need not to be shutdown e.g. for case “1” can be
identified by the command *a in which “up” is written under the “OperStatus”.
The LMP link state for “2” and “3” pass and fail respectively however the resources are occupied in doing so by the control channels
which are needed to be shutdown to free the resources. The LMP link state that need to be shutdown to free the resource e.g. for case “2”
and “3” can be identified by the command *a in which “config_snd” is written under the “OperStatus” and finally can be shutdown by
using the command *b.
Before shutting down the LMP control channels, it is necessary to first confirm which fiber connection is for use of the ASON features and
which is not. This confirmation should not be made on the basis of the queried result but network plan.
If the control channels where the negotiation function is enabled on one ASON NE are more than 20, resources for the control channels
may be insufficient. For this case, if several control channels are between two ASON NE’s, disable the negotiation function of the control
channels between two NE’s and delete some of the control channels to release some resources. However, at least one control channel must
be available. If redundancy backup is required, reserve two control channels. Query whether the control channels are created to an
optical interface by issuing the command: sc-get-port-state. If;
Create CCFlag enable = Control channels are created to the optical interface.
CreateCCFlag disable= Control channels are not created to the optical interface.
Issue the command to create or delete control channels. : sc-set-cc-available:Bid,Pid,enable/disable;

For MOBILINK in case of LMP link state the control channels shall be set as follows;

For Lahore we will shut all other boards except 3JL64, 7JL64 and 12JL64
For Islamabad we will shut all board ports other than 10JL64, 3JL64, 5JL64 and 12 JL64
For Faisalabad we will shut all board ports other than 10 JL64, 12 JL64 and 25JL64

For MOBILINK in case of setting the ports for enabling/disabling when the control channels esceed 20 for a particular ASON NE;

For Lahore we will disable all other board ports except 3JL64, 7JL64 and 12JL64
For Islamabad we will disable all board ports other than 10JL64, 3JL64, 5JL64 and 12 JL64
For Faisalabad we will disable all board ports other than 10 JL64, 12 JL64 and 25JL64

OPERATIONS USING T2000 FOR ASON CONFIGURATION

A. Create ASON Domain and ASON Primary NE by T2000

• Select Configuration > ASON Topology Management from the Main Menu.
• Right-click the root tree field and select Create Domain.
• Enter the name for the ASON domain (MOBILINK) and select the primary NE.
• Click OK to effectuate the settings. We shall create Lahore GNE as primary NE.

B. RESOURCE AUTO DISCOVERY(Create other NE by Primary NE)

• Select Configuration > ASON Topology Management from the Main Menu.
• Select Lahore from the Function Tree.
 • Click Synchronize NE in the ASON NE dialog box. Through the primary NE, the T2000 searches for
other NEs in the ASON domain.
• To create the NEs newly searched out on the T2000, select Creation Flag, and enter the user &
password.
• Select Upload after created
• Click Apply. The ASON NEs are displayed in the Main Topology.

C. SPECIFY SECONDARY NE
• Select Configuration > ASON Topology Management from the Main Menu.
• Select Mobilink from the Function Tree. All NEs in the ASON domain are displayed in the ASON NE
dialog box.
• Specify Faisalabad GNE as secondary NE.

D. CREATING FIBERS
• Select Configuration >TE Link Management from the Main Menu.
• Click Synchronize. The T2000 searches out all TE Links.
• Select all the TE Links.
• Click Create Fiber. The fibers are created.

E. CONFIGURE TWO FIBER MSP-RRING

• Configuration>Protection View> Create> 2_Fiber_Bi_MSP_Ring.
• Select Lahore, Faisalabad and Islamabad then click next and then Finish.

F. CONFIGURE SHARED RESOURCE LINK GROUP

• Select Configuration > TE Link Management from the Main Menu.
• Select the link to be set. Double-click or right-click SRLG and enter the value.
• Enter a number rather than 0, which are for the links in the same risk group. Enter 0 for the links
not in any risk group.

G. CONFIGURE THE LINK DISTANCES

 • Select Configuration > TE Link Management from the Main Menu.
• Select the link whose distance is to be set.
• Click the Distance (km) column and enter the value.
• Click Apply to effectuate the setting.
CREATING SERVICES:

There are five different types of (SLA) services that can be configured according to customer requirement, namely;
1. Diamond.
2. Golden.
3. Silver.
4. Copper.
5. Iron.
These different service level agreements have different priorities and different ways of protecting the services. These services can be
between two ASON NE’s, between two SDH NE’s, and between an ASON and a SDH NE or any other combination of these. An example of
creating a vc12 level service between SDH and ASON NE’s end to end is considered below. The steps shall involve;
1. Using of SDH Service Creation to create vc12 service from SDH NE to ASON NE.
2. Using of ASON Trail creation for creating tunnel service (ASON VC4 server trail) between ASON NE’s. An ASON Server Trail is
used to carry vc12 or vc3 services between adjacent nodes. This server trail is configured between adjacent nodes only. Once a
server trail is enabled the vc12/3 services can be configured without configuring the server trail again and again until the server
trail gets completely occupied.
In short after creating a tunnel service between adjacent nodes, till the tunnel from the source to sink node is complete, create cross-
connection from VC-12/ VC-3 service to tunnel manually in the Service Configuration. The VC-12/ VC-3 service can be created while
creating SDH path.

CONFIGURATION for VC-12 Service from Lahore to Faisalabad is given

OSN 9500-LHR OSN 9500-FSD

Boar P VC12(ST VC V Optic Optic VC V Boar P VC12(ST

NE NE
d ort M) 4 C12 al al 4 C12 d ort M)
 L L
DI- DI-
SD 1JLH1 3-JL64- 10- SD 1-
2 1 1 1 1 1 2 1
H -2 1 JL64-1 H JLH1
LH FS
R D

Service
Lahore
Attribute
Source NE Lahore
Source board-port 1-JLH1-2
Source VC-12 1
Sink NE Lahore
Sink board-port 3-JL64
Sink VC-4 1
Sink VC-12 1

The above mentioned service will be a traditional SDH service

Service
Lahore<->Faisalabad
Attribute
Source NE Lahore
Source board-port 3-JL64
Source VC-4 1
Sink NE Faisalabad
Sink board-port 10-JL64
Sink VC-4 1
Protection type Golden class
Trail constraint The working LSP is 3JL64 to 10 JL64.

To create above service follow the Step

i)Select Configuration > ASON Trail Management from the Main Menu.
ii)Click Create and the creation wizard window is displayed.
iii)Enter the Basic Attributes of NE as shown above.

Service
Faisalabad
Attribute
Source NE Faisalabad
Source board-port 1-JLH1-2
Source VC-12 1
Sink NE Faisalabad
Sink board-port 10-JL64
Sink VC-4 1
Sink VC-12 1

This service will be a traditional SDH service.

• Set Rerouting Priorities for ASON Services

i)Select Configuration > ASON Trail Management from the Main Menu.
ii)Right-click the ASON trail to be set and select Set Rerouting Attributes.
Click Low to lower the priority of an ASON service.
iii)The system prompts that the operation succeeds. View the priority information of the ASON service in the list.
 • Degradation of ASON service into permanent connection.

i)Select Configuration > ASON Trail Management from the Main Menu.
ii)Right-click the ASON trail to degrade it from the ASON trail list, and select Degrade to SDH service.
iii)If the system returns an error message saying "The ASON trial managed by the SDH trail cannot be degraded",
that means the ASON trail exists in SDH Trail Management. Display the SDH Trail Management window, and delete
the trail from network layer.
iv)After the degrading, select Trail > SDH Trail Search form the Main Menu. The degraded service can be searched out.

• Upgrade From Permanent Connections to ASON Services

i)Select Trail > SDH Trail Management from the Main Menu.
ii)Right-click the SDH trail to upgrade it from the SDH trail list, and select Upgrade to ASON Trail.
iii)Make settings in the Class, Revertive Mode, Rerouting Lockout, Rerouting Priority
and Exchange Data with Source/Sink fields.Click OK. When the upgrade is complete,
a prompt appears to ask if you want to open the ASON Trail Management window.

• Query the clock information

First query the ASON feature

:cfg-get-itgattrib;

query the clock information

:cfg-get-clkmode:Bid;
:cfg-get-cursyn:Bid; //For OSN 9500 Bid is 45 or 46

Create pre-configure an ASON clock

i)Select Configuration > Clock Subnet Management from the Main Menu.
 ii)Click Create Clock Subnet and enter the ID. Add the NEs of the subnet. Check the Preconfigured Subnet checkbox.
iii)Click OK. A dialog box is displayed and prompts “No PRC is selected”
iV)If the system prompts that the operation succeeds, the configured subnet can be viewed form the left-hand Subnet
Management Tree pane.
V)Click SSM Mode in the Subnet Attribute interface. Select Disable SSM Mode or Standard Clock Mode.
//When the clock subnet is configured to the SSM protocol mode, all NEs within the subnet are set to this mode.

Set primary clock

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet to be viewed from the Subnet Management Tree. Click the Primary Source Management option button.
iii)Click Create and a dialog box is displayed. Select a primary source.
iV)Click Yes and the selected primary source is added to the primary source management list.
Use the Up or Down button to adjust the priority. Click Apply.

Setting the quality of clock

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet to be viewed from the Subnet Management Tree. Click the PRC Management option button.
iii)Select the primary clock source to set the quality. Right-click the PRC Level and select the quality level.

Set the lockout state of the primary clock source

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet to be viewed from the Subnet Management Tree. Click the PRC Management option button.
iii)Select the primary clock source to be locked. Right-click the Lockout Status column and select Locked.

To set the interface mode

 i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet to be viewed from the Subnet Management Tree. Click the Primary Source Management option button.
iii)Right-click the Interface Mode Management to set the interface mode for the selected optical interfaces

23) Enabling the ASON Clock Functions

Enabling the ASON Clock Features

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet from the Subnet Management Tree to add NEs. Click the Subnet Attribute optical button. Click Add
NE.

Querying the Clock Attributes of NEs in the Entire Network

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii)Select the subnet to be viewed from the Subnet Management Tree.

Query the Primary Source of a Specified ASON Clock Subnet

i)Select Configuration > Clock Subnet Management from the Main Menu.
ii) Select the subnet to be viewed from the Subnet Management Tree.
iii) Click the PRC Management option button. If the primary source information is not displayed, click Query.

Query the Link Clock State

: ospf-get-linkclk-status;

Query the Clock Tracing Relation of Each NE

 i)Select Configuration > Clock View from the Main Menu. The clock tracing relation is displayed.

• Testing of ASON Service

(1) Connect SDH analyzer to the TU port of the Source NE (connected to 1-JLH1-2 in Lahore) and electrically loop the
Sink NE (Connected to 1-JLH1-2 in Faisalabad) and check the Alarm on SDH Analyzer.
(2) Then we shut down the laser of 3 JL64 in Lahore service should shift to 12-JL64 (first MSP switching) and check the
Alarms on SDH Analyzer there should not be any Alarm and it should switch before 50 ms.
(3) Then we shut down the laser of 12 JL64 in Lahore service should shift to 7-JL64 (ASON switching) and
Check the Alarms on SDH Analyzer there should not be any Alarm and it should switch before 50 ms.