Transport Provisioning Guidelines

Transport Provisioning
Guidelines

Rev Date Reason for Issue Prepared by Checked by Approved

by
0 3/6/2008 Provisioning Procedure Puneet Khurana Vishal Garg Sh Nusrat
Mohammad
1 11/12/2008 Steps to Resolve Provisioning Related Constraints Puneet Khurana Vishal Garg Sh Nusrat
Mohammad
2 12/4/2009 Addition of ‘Provisioning Parameters –Desired Vishal Garg Sh Nusrat Sh Udit
Configuration’ Mohammad Bajpayi
3 30/5/2011 Addition of input in Point No. 4.1 of Do’s and Don’ts Vaibhav Bhatnagar Siddharth Goswami Sh PC Jain
& Marconi realignment Escalation in point no 5.2
3 30/5/2011 Approval format for Spur provisioning Javed Akhtar Siddharth Goswami Sh PC Jain
3 30/5/2011 Concepts of 3-way or 4-way Cross connection Vaibhav Bhatnagar Siddharth Goswami Sh PC Jain
3 30/5/2011 Frequently Asked questions Vaibhav Bhatnagar Siddharth Goswami Sh PC Jain

1/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

INDEX
1 Summary……………………………………………………………………………………………….……3

1.1 Background………………………………………………………………………………………………….3
1.2 Scope…………………………………………………………………………………………….…..……….3
1.3 Validity……………………………………………………………………….………………….…………...3
1.4 Audience.……………………………………………………………………….………….……….……….3
1.5 Frequency of Revision…………………………………………………………………………….…….3

2 Core Steps……………………………………………………………………………………………….……4

2.1 Create Customer………………..………………………………………………………………………….4

2.2 Generate Service Order…………………………………………………………………….…..……….4
2.3 Create Circuit……………………………………………………………….………………….…………...4
2.4 Validation.……………………………………………………………………….………….……….……….4
2.5 Create CLR…………………………………….……………………………………………………….…….5
2.6 Provision Preside………………….…………………………………………………………………….….5
2.7 Conduct Logical Testing ……………………………………………………………..…….…..……...6
2.8 E2E Testing and Customer Acceptance……………………..……………………………………..7
2.9 Service Delivery & Close Service Order…………………………….………….……….….……...7

3 Training & Supporting Documents.......………………………………………………………….……8

3.1 Training……………………………………………………………………………………………………….8
3.2 Documents Reqd……………………………………………………………………………..…………..8
3.2.1 NDD……………………………………………………………………………………………..8
3.2.2 Support Portals.…………………………………………….………………………………8

4 Do’s & Don’ts……………………….........……………………………………….………………….……9

4.1 Special Instructions while executing Provisioning SO…………………………………….…9

4.2 Responsibility for Provisioning Leads………………………………………………..…………...10
4.3 Precautions for Executing a De-provisioning SO…………………………………….…..…..11

5 Provisioning Related Constraints & Resolution….………………………………………….……11

5.1 Comms Fail Resolution Steps…………….…………………………………………..…………...11

5.2 Marconi Nodes Realignment Steps ………………………………………………….…..…..….11
5.3 Steps for Checking/Deleting Hanging circuit………………………………..…………….….12
5.3.1 NORTEL (TN-1C /1X/4XE/16XE)………………………….………………………..12
5.3.2 NORTEL (N61, N63&N65).………………………………….………………………..12
5.3.3 MARCONI ………………………………………………..……………………….………..12
5.3.4 FIBCOM …………………………………………………..………………………………..13

6 Provisioning Parameters – Desired Configuration …..………………………………………....13

7 Spur Approval Format ………………………………………………………………………………….15

8 Concepts of 3-way & 4-way Cross Connection…………………….…………………………….15

9 Frequently Asked Questions (FAQ)…………………….…………………………………………….16

2/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

1) SUMMARY

1.1 Background

SOMG-Transport group provides interconnect services to internal and external customers

.Service delivery constitutes bandwidth from E1 to STM-16 connectivity from point to point.

1.2 Scope

The scope of this provisioning guideline is the actions to be taken and decisions to be made
when an internal Business Unit wishes to send or receive traffic via the Reliance Network. The
network capacity required to manage this traffic is then checked and the requisite actions
taken to allocate, activate or upgrade the appropriate network elements are made before
implementation of service order. This process deals with the following Service Order Types:
Create, Modify (Relocate), Regrade (Upgrade/Downgrade), and Delete (Disconnect).

The “Modify” (Relocate) process refers to relocation of one or both terminating ends. It will be
handled as two separate SO, one of type “Create” to establish the new routing and terminating
end assignments, and one of type “Delete” to disconnect the old routing and terminating end
assignments to the service. For “Regrade” (Upgrade/Downgrade) the process is the same as
for Create/Delete. Since the customer account and Trunk group details already exist, only the
path and device assignments need to be created/removed and added/deleted from the
records.

1.3 Validity

This document is valid till the next revision is issued

1.4 Audience

Circle Transport Provisioning Teams & Transport Provisioning Team in DAKC

1.5 Frequency of Revision

This document will be revised only on need basis

3/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

2) Core Steps

2.1 Create Customer

The „Reliance Business Unit‟ requiring any bandwidth connectivity from point to point raises a
request for the same with a customer creation.
2.2 Generate Service Order
The Service Manager module of the OSS contains the request for the Provisioning of any
bandwidth This activity applies to “Service Order for internal Customer”, “Move / Change
Service” or “Disconnect Service”. The data associated with this activity is manually input to the
system.
2.3 Create Circuit
Circuit headers are created on the basis of originators request and the status is updated.
2.4. Validation
Provisioning inputs are validated before processing .Snapshots shown are for RIC_MSC_BTS
service type where BSC end hand-off details & Take-Off ID information is checked before
provisioning

Fig 4.1

4/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

Fig 4.2
2.5 Create CLR
Using the Configuration Manager module of the OSS, input the trail cross connects details
from the end point of the network at the A-end to the end point of the network at the Z-end.
This activity applies to a new service order, a move service order and in some cases a change
service order such as an upgrade or downgrade in bandwidth.

Fig 5.1
2.6 Provision Preside
Using the Preside Conn. Manager/CLUI/OCM, Marconi MV38, Fibcom Network Manager UI
provision the connection as per CLR created in the cross-connect step.

Fig 6.1

5/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

Fig 6.2

Fig 6.3
2.7 Conduct Logical testing
The provisioning Engineer is responsible to carry out testing of the service using the payload
and switching mechanism in SDH equipment. Test procedure for this is as given below.

NE-1 Ring-1 NE-2 Ring-2 NE-3 Ring-3 NE-4

Electrical drop Electrical drop

Electrical drop at both ends

• Check payload label for all four arms of circuit at NE-2. This will ensure that
protection has been defined for Ring-1 and Ring -2.

• Protection for Ring-3 can be verified by checking payload label at NE-3 (

towards NE-4) or by checking payload label at NE-4 ( towards NE-3)

Fig 7.1

6/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

NE-1 Ring-1 NE-2 Ring-2 NE-3 Ring-3 NE-4

Electrical drop
Optical handoff

Electrical drop at one end and optical at other

• Start from the side which has optical hand off (NE-4 in this case)
• Check for payload label at both arms of connections towards NE-3
• Check for payload label at both arms of connections towards NE-2
• Check for payload label at both arms of connections towards NE-1

Fig 7.2

NE-1 Ring-1 NE-2 Ring-2 NE-3 Ring-3 NE-4

Optical handoff
Optical handoff

Optical hand off at both ends

• In this case the protection verification can be done only after integration of
the end devices.

• Protection switching can used to determine if the working and protection

paths are configured properly

Fig 7.3

2.8 E2E Testing and Customer Acceptance

After the provisioning tasks are closed by the provisioning engineer, Clarity will generate WOs
for conducting end to end test of the circuit. This will be done by the Transport O&M Engineer
in the field by giving hard loop at one end of the circuit and putting a BER tester at the other
end for carrying out 5 minutes stability test. The test results will be recorded by the Transport
O&M Engineer. This test is valid if both the ends are electrical. In case of one end being
optical, Performance Stability is to be carried out for 15 minutes. This test report is to be
presented to the customer who has to accept the circuit.

2.9 Service Delivery & Close Service Order

Service Order is closed and the status is changed from PROPOSED to IN SERVICE after
closure of these auto tasks.

7/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

3) Training, Supporting Documents & Portals

Proper O&M training on all the equipment is required for correct provisioning and trouble
shooting.

3.1 Trainings Required

o SDH Basics
o Clarity CLR making
o Nortel Equipment and NMS
o Marconi Equipment & NMS
o Fibcom Equipment and NMS

3.2 Documents & Support Required

The required Documents/ Database for CLR generation can be referred as below in Gyan
Mandir / other portals as referred below

3.2.1 NDD: EWC Long Distance > 03. Transport > 04. Nodal Design > Network
Drawings > All India Transport NEDs Year 2011 >

3.2.2 Support Portals

S/N IP address Significance

http://97.253.88.71:82/transport_ops/first.ht NE search using FACID or MAC
1
ml ADDRESS
NE Comms. Fail Cases Tracking
2 http://97.253.9.199/its/
System
3 http://97.253.9.199/hicap/ HI-CAP Network Tracking System
Escalation to Transport OPS for
4 http://97.253.15.31/query/
resolution for EMS/NMS server issues
Transport Network Logical Inventory
5 http://97.253.9.199/nis/ Data Bank for optical connectivity &
cross-connect dump

8/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

4) DO’s and DON'Ts

4.1 Special Instructions while executing Provisioning SO

1. For all Service Orders, E2E CLR has to be made in Clarity.

2. If there is any change in the actual provisioning, then the same should be updated in
Clarity database before closing the WO.
3. Normally, not more than two Inter-box optical patches should be taken while preparing
CLR.
4. While selecting the KLM from Network, payload label should be checked to ascertain if
the KLM is hanging or not.
5. KLM of another provisioned circuit should not be used unless it is confirmed that it is a
hanging circuit.
6. Any new inter box patching (Intra or inter-vendor or end equipment like
MSC/BSC/GMSC/ILT/RDN) which is created during provisioning should be entered in
Clarity using „Patch-create‟ utility

7. If for any reason some circuit has to be provisioned on spur then pls select the „Spur „
attribute in the respective SO for further tracking & closure.
8. All circuits have to be provisioned with Protection path unless it is to be on spur as per
NDD.
9. Working and Protection paths should have physical path (Fiber) diversity also.
10. No provisioning to be done manually in Marconi at NE level in MV-36 server
11. Proper user labels as generated in Clarity to be put on each circuit.
12. In case of modify SOs (for swapping / re-homing), existing E1 CLR should be first
validated with actual network and accordingly corrected in Clarity before preparing the
actual Modify CLR.
13. In case of Re-homing and Swap SOs it should be ensured that the hanging trails are
deleted.
14. After re-homing, new User Label has to be applied across the entire trail, and not only
in the modified section.

9/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

15. The connectivity of nodes should be verified by either Trace on RS Section or MAC
address of the node.
16. Within MCN while provisioning priority should be given to Inter Box MSP protected
patches & thereafter unprotected patches used in SNC/P manner. If there is no option
feasible then take unprotected patches.
17. End to End trace should be checked from both the direction for a provisioned circuit
before doing the testing.
18. Spur provisioning can only be done with CTO/Business Head Approval, as per
attached format.
19. Check payload /Trace at the junction points to avoid protection path issues.
20. MSP (1+1) Settings should be identical at both transport as well as switch end, plz
refer point no 6 for detailed configuration of MSP.
21. Alternate Name of the circuit in clarity should be same as in the network.
22. Fiber commonality should be checked before selecting the worker and the protection
path.
23. Inter box patches of more than STM1 level must be always have MSP (1+1) protection
scheme, for Marconi contact DAKC SOMG team.
24. For routing the circuits from BAN/Access rings to Collector Paths always take the
longer path for closing the traffic via DX/HDX Layer.
25. KLM Should be uniquely used in access rings.
26. Always realign the Marconi nodes after adding/deleting any inventory in the Node.
Addition of patch on Marconi should be done in MV-38 in the form of link creation.
27. Always realign the Marconi nodes after creating MSP(1+1) protection scheme.
28. In Fibcom Nodes , while creating the Add / Drop connection always have SNC/N
enabled.
29. Granularity of the circuit should not be different at the SNC/P Switching points for any
new provisioned circuit.
30. Userlabel/Alternate Name of the circuit should be same across vendors.
31. Never delete any drop port without delete SO, otherwise it will create issue with its
original SO.

4.2 Responsibility for Provisioning Leads

1. Weekly sample audit checks maybe initiated to ensure that the provisioned circuits in
the Network are available in Clarity accurately.

10/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

2. Weekly sample audit checks maybe initiated to ensure that the provisioned circuits in
the Network are with protection paths.

4.3 Precautions for Executing a De-provisioning SO

1) All de-provisioning to be done against valid Clarity SO only.

2) In case of Electrical terminations, at least one of the ports should carry an alarm
indicating that it is not carrying any traffic.
3) In case of Optical connectivity like MSC to ILT, confirmation should be taken from the
interface owner regarding traffic, before deleting.
4) Inter-federation circuits are to be deleted end to end to ensure there are no hanging
cross-connects.

5. Provisioning Related Constraints & Resolution

5.1 Comms Fail Resolution Steps

1) Check whether any Fiber cut is there in the parent ring, if yes then coordinates with
Circle OSP team for resolution

2) Check the alarms (service affecting) in the whole parent ring, if yes then resolve that in
coordination with FM NOC

3) Check whether the parent router is ok or not, if not then escalate it to RDN NOC for
resolution

4) Check whether the EMS/NMS server is ok or not, if not then escalate it to Transport
OPS for resolution

5) Check the DCN connectivity and check the area address, dcc, Mac, ip the entire
configuration in all the NEs of the ring and server should be as per DCN/MOP. In case
of any mismatch take guidance from planning team.

5.2 Marconi Nodes Realignment Steps

1) Initiate Realignment & check whether the Realignment process completed successfully
or with the error “Realignment Completed with Failure”.

2) Refer RH-Multiple Report File generated on EMS for the Circuit Ids information
required to be disassociated for all conflict cases.

3) Disassociate all such conflict circuits & try again to realign the problematic NE

11/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

4) Check whether the realignment process completed without error, if not coordinate with
following Eng in DAKC

i. Mr Dinesh P Dabhade/RCOM/RelianceADA,
ii. Amol C Borgavkar/RCOM/RelianceADA,
iii. Kanchan Shilankar/RCOM/RelianceADA,
iv. Snehal Bhagat/RCOM/RelianceADA,

5) If not resolved same can be escalated to

Siddharth Goswami/RCOM/RelianceADA,

5.3 Steps for Checking/Deleting Hanging circuits

5.3.1 NORTEL (TN-1C /1X/4XE/16XE)

1. View the Cross connects by using the command ~ C N V C Cross Connect.

2. Check the Payload of East /West direction ports by using the Command ~V VC.

3. If both East/west Side port are showing payload 0 then only Delete the respective
Cross Connect by using the command ~C N D else Not.

4. Never delete the Cross Connects showing payload 2,5 or 7 at either side.

5.3.2 NORTEL (N61, N63&N65)

1. Verify the connectivity between the End NE and Subtending Head NE by using the
Path trace Feature.

2. Now Check the KLM„s free on both Subtending Ports and if ring is subtending to
another NE check the same on that NE also

3. Delete the KLM‟s found free on Head NE Ports on both side in STM1 ring.

5.3.3 MARCONI

1. Check the free Available Free cross Connects in MV 36,

2. Verify the connectivity between the End NE and Subtending Head NE by using the
Path trace Feature.

3. If KLM‟s are busy in MV38, check the same KLM‟s in „Remove cross Connects‟ and
Remove protection Cross Connects

4. If Not Available in the above then realign the NE and repeat the second step

5. Check if the status is Unequipped

12/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

5.3.4 FIBCOM

8. Verify the connectivity between the End NE and Subtending Head NE by using the
Path trace Feature.

8. Now Check the KLM„s free on both Subtending Ports and if ring is subtending to
another NE check the same on that NE also

8. Delete the KLM‟s found free on Head NE Ports on both side in STM1 ring.

6. Provisioning Parameters –Desired Configuration

The parameters given below are to be set / checked while provisioning as per the table given
below. If these parameters are not properly set, it may result in outages.

PROVISIONING
S.NO EQUIPMENT DESIRED CONFIGURATION
PARAMETER

BI DIRECTIONAL, NON REVERTIVE.

Replication of MSP parameters (All MSP
1 SDH to SDH parameters like Bi/Uni, Revertive / Non
Revertive etc) from one node to another or
slot change in a node during RPR execution.
BSC <-> TC / BTS <-> BSC :: 1 + 1 MSP
2 Huawei GSM ,Bidirectional , Non-revertive ,Enable
(Excessive BER (EBER) Configuration)
Huawei CDMA(PARC BTS <-> BSC : 1+1 MSP , Unidirectional , Non
3
BSC) revertive
BTS <-> MSC : 1+1,Bi-directional ,Non-
4 Lucent CDMA revertive ,Enable (Excessive BER (EBER)
Configuration)
ALL SDH
5 ZTE CDMA BTS <-> BSC : 1 + 1 , Revertive , Bidirectional
MSP 1+1
All SDH patches above STM1 (STM4
PROTECTION MSP requirement in
6 onwards) should have MSP/SNCP protection
intra MCN Connectivity
except collector closures.

7 ILT 1+1 MSP , Unidirectional , Non revertive

MSP protection between the patches

MSP Protection
passing through Metro DWDM Rings is not
8 through Metro DWDM
recommended. SNCP can be preferred
Patches
instead of MSP
Route diversity Ensure the STM16 DWDM patches using for
9 through Metro DWDM SNCP/MSP should have route diversity
patches before provisioning any services.
Hp_pay load_label on
Should be set to "2" on all VC4's of Standby
10 Nortel 4XE, 16XE standby port of
port.
1+1MSP group

APS ID in BLSR Correct APS ID should be used for making

11
NORTEL SNCP & BLSR Connections BLSR connections in NLD Rings
HDX,OME6500 PROTECTION Should have Identical Granularity through
12 SNCP Protection
out a Ring.

13/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

Prefer 4Way SNCP connection instead of

13 4Way SNCP
two 2way connections
Nortel OGT (Oscillation Guard
14 Should be "0"sec"
16X,4X,41X,1C,1X Time)

Expected Section Trace Expected Section Trace should be in

15
EXPECTED Mode "Disable" mode
ALL SDH
TRACE Expected HP/HO Expected Section Trace should be in
16
Trace Mode "Disable" mode

PROVISIONING
S.NO EQUIPMENT DESIRED CONFIGURATION
PARAMETER

MS Signal Degrade Should be "ON" for NE & all

17
Consequent Action optical ports
All SDH Elements DEGRADED
MS EXC Degrade Should be "ON" for NE & all
18 SIGNAL
Consequent Action optical ports
CONDITIONS
Nortel LP DEG/LP EXC LP EXC consequent action should
19
16X,4X,41X,1C,1X Consequent action be "ON"

Path alarm profile should be

OME6110,
20 PATH PROFILE Path Alarm Profile "Mask Tim Only". NO other alarm
OME6130
profile is allowed.

Remove channels with

21 OME6110/6130 SD (WAN Should be enabled.
configuration)
LLF (Link loss forwarding) mode
should be in ON (Switch OFF
LLF PARAMETER in
22 MARCONI, Ethernet Transmit) mode for all
LAN & WAN on Eth Eth over SDH
the internal RDN links provisioned
over SDH
on GE links
TX Conditioning GE
23 OME6500 Should be enabled.
port configuration
Link fault pass through
24 Fibcom 6325 Should be enabled.
on GE port

Flow Control & Flow Control – Disabled

25 All SDH RDN Connectivity
Negotiation Negotiation –Full Duplex

14/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

9. Format For SUPR Approval, to be filled by planning Eng

Approval for SPUR Provisioning- Format

Ring
NE Media
SO Service Customer Proposed protection to Approved Approval
SN. Circle FAC (Fiber/ Remark
No. type Name by be Planned by by date
ID MW)
(DD/MM/YYYY)

Note : Tracking of ring closure is the sole responsibility of circle Head / CTO.

8. Concepts on 3-way and 4-way Crossconnection

8.1 3 way & 4 way Cross connection

Type of General
Concept Diagrammatic View
Connections Terminology

Add-drop (protected) connections

allow traffic to add or drop between
a payload on a tributary port and a
Add Drop payload on either of the aggregate
3 way
Connection ports.Added traffic from a tributary
is sent to the ports on both
aggregates and then transmitted in
both directions around the network.

From SW Mate

A ring to ring connection contains a

single payload connected between
a pair of STM-N ports located on
Ring to Ring one ring and a second pair of STM- To DS Mate
4 way
Connection N ports located on a different ring.
This type of connection is available
between STM-4 and STM-1 or
between STM-1 and STM-1 rings.

15/16 Version 1.3 30th May 2011 SOMG N/W Provisioning

 Transport Provisioning Guidelines

9. Frequently Asked Questions

Q 1. I cant modify any cross connect?

Ans 1. Plz check if your user rights are configuration rights, otherw ise cont act
w ith Transport OPS team in DAKC.

Q 2. In w hich scenarios, the Marconi node needs to be realigned before

going ahead for provisioning?
Ans 2. If you have added any new SFP / card or change in MSP, then node
needs to be realigned.

Q 3. Can I provision circuit on SPUR?

Ans 3. NO, Spur provisioning can only be done w ith CTO/Business Head
Approval.

Q 4. What alarms are generated during fiber cut in the net w ork?
Ans 4 RS_LOS Alarm w ill be generated on the concerned ports.

Q 5. What is CLR in clarit y?

Ans 5 CLR stands f or circuit layout record for individual circuits in clarity.

Q 6. Which Team is responsible for loading the cards/ports in clarit y?

Ans 6. NPE Team loads the cards/port s in clarity after Node installation &
commissioning.

Q 7. What is the difference betw een Alternate Name & User label for a new
provisioning ?
Ans 7. Alternat e Name & User label are same. One is used for reference in
clarity & other is used for reference in netw ork.

Q.8 What if 7 VC4‟ s have been used and f acing constraint in Fibcom nodes?
Ans : Plz check if Box can be upgraded to F25 node, w hich can provide max 16
VC4.
Q 8 . I am unable to define MSP in node?
Ans 8 : Plz check if any connection is present on protection port, if yes then it
is not possible to define MSP on that port until connections are removed or
shifted to another port.

Q9: What is sw itch mate?

Ans 9 : Port on w hich protection path w ill sw itch.

Q10 : Can I close SO, after finishing netw ork provisioning only?
Ans 10 : NO, Untill CLR is loaded in the clarity, SO tasks must not be closed.

Q11 : What is protected circuit?

Ans 11 : When w orker and protection are on different Fiber, then only it is truly
protected circuit.

16/16 Version 1.3 30th May 2011 SOMG N/W Provisioning