HDX_-_Presentation_-_12.01.2005

8/12/2019 HDX_-_Presentation_-_12.01.2005

1/54

HDX deployment Plan

January 12th2005

NPE - TX


2/54

Existing Backbone NetworkAfter Resiliency Phase -I


3/54

25

18

25

28

29

24

31

9

7

31

24

29

25

23

31

23

24

29

21

31

25

5

6

7

1

12

20

2

4

10

11

17

14

6

7

6

6

9

11

6

9

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

0 16 32 48 64

R1-1 AHDB-JIPR

R1-1 DLHI-JIPR

R1-1 BHPL-DLHI

R1-1 AHDB-BHPL

R1-1 AHDB-INDR

R1-1 BHPL-INDR

R1-2 MUMB-SURT

R1-2 AHDB-SURT

R1-2 AHDB-INDR

R1-2 BHPL-INDR

R1-2 BHPL-NGPR

R1-2 MUMB-NGPR

R1-2 KLYN-NGPR

R1-2 KLYN-MUMB

R1-3 HYDR-NGPR

R1-3 HYDR-SNGR

R1-3 PUNE-SNGR

R1-3 MUMB-PUNE

R1-3 MUMB-NGPR

R1-3 DHUL-KLYN

R1-3 KLYN-MUMB

R1-3 DHUL-PUNE

R2 BANG-HYDR

R2 BANG-KSGR

R2 KSGR-CHNN

R2 CHNN-VWDA

R2 HYDR-VWDA

L1 Used L1 Free L2 Used L2 Free

EXPRESS BANDWIDTH UTILISATION FOR RING 1-1, 1-2, 1-3, 2

[Part-1]


4/54

EXPRESS BANDWIDTH UTILISATION FOR RING 3-1, 3-2, 3-3, 4, 6

, 7 & 8 [Part-2]

25

18

25

28

29

24

31

9

7

31

24

29

25

23

31

23

24

29

21

31

25

5

6

7

1

12

20

2

4

10

11

17

14

6

7

6

6

9

11

6

9

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

not available

0 16 32 48 64

R1-1 AHDB-JIPR

R1-1 DLHI-JIPR

R1-1 BHPL-DLHI

R1-1 AHDB-BHPL

R1-1 AHDB-INDR

R1-1 BHPL-INDR

R1-2 MUMB-SURT

R1-2 AHDB-SURT

R1-2 AHDB-INDR

R1-2 BHPL-INDR

R1-2 BHPL-NGPR

R1-2 MUMB-NGPR

R1-2 KLYN-NGPR

R1-2 KLYN-MUMB

R1-3 HYDR-NGPR

R1-3 HYDR-SNGR

R1-3 PUNE-SNGR

R1-3 MUMB-PUNE

R1-3 MUMB-NGPR

R1-3 DHUL-KLYN

R1-3 KLYN-MUMB

R1-3 DHUL-PUNE

R2 BANG-HYDR

R2 BANG-KSGR

R2 KSGR-CHNN

R2 CHNN-VWDA

R2 HYDR-VWDA

L1 Used L1 Free L2 Used L2 Free


5/54

Driving Forces for Backbone Capacity Enhancement

RDN Bandwidth requirements

Need to carry FLAG - ILD traffic between Mumbai and

Chennai Cable landing Stations on three diverse paths with

terrestrial availability matching to that of sub-marine network

ILD bandwidth dispersion across NLD network

CDMA Phase-I expansion & CDMA Phase II

Wire line & Leased Bandwidth

Need for improving Network availability ~99.99% using the

stateof the artmesh restoration functionality


6/54

Supports only 2F-BLSR Ring

140 Gbps switch fabric (40 + 40) Gbps/(4X2F) Ring in Aggregate

& 60 Gbps on tribs.

Reserves 50% bandwidth for BLSR protection

In current architecture additional lambda in all rings exceptingRing 4 & Ring 6 require additional DX in central line (Delhi,

Bhopal, Nagpur, Hyderabad, Bangalore)

Additional DX required at all three way locations Mumbai,

Allahabad, Ahmedabad, Pune and Vijayawada etc. after everysecond lambda.

Interconnection between collocated DXs through hard patches

truncates the capacity of DX and require additional trib cards

Limitations of existing Nortel DX


7/54

Features of Nortel HDX vs DX

Features HDX Nortel Nortel Optera DX

Cross Connect Fabric

Size

640 Gbps scalable upto 3.84

Tbps ( Multiple Chasis)140 Gbps

BLSR Rings about 20 X 2 F BLSR 4 X 2 F BLSR

Network Architecture /Topology

Linear, Ring and Mesh

Architecture/ Mesh

Restoration is available

Linear & Ring

Protection Restoration

Capabilities

Mesh Restoration improves the

availability across multiple

routes

Does not support

more than one Fiber

Cut in Ring

Capacity truncation on

account of hard

patches

No capacity truncated Capacity istruncated

One Nortel HDX is equivalent to approx five DXs


8/54

Higher switch fabric size supporting multiple rings

Besides BLSR, supports Shared Protection and Intelligent

mesh restoration functionality,which makes network more

resilient.

It can provide availability better than the Ring Architecture

Better bandwidth utilization(can be loaded up to 70% of

ring capacity as against 50% in BLSR).

Significant reduction in electronics for wavelengthaugmentation & Quick deployment

(Only 10G ports at HDX & XR cards at in between

REGENs to be added)

Benefits of HDX


9/54

Grow HDX way instead of adding more DXs

Identified 14 strategic locations for HDX deployment

Deploy HDX

HDX to HDX Mesh Wavelengths addition for

backbone capacity augmentation

Transfer of Existing BLSR Rings to HDX

Redeploy 16 nos. of freed DXs at identified sites for resiliencyproject / Other Switch locations / Collector Splitting

Backbone Network Growth Plan


10/54

Strategic Locations for HDX (Having at least threediverse routes)

S. No. DX Locations HDX

1 Mumbai Landing Station HDX

2 Mumbai MCN HDX

3 Chennai Landing Station HDX

4 Chennai MCN HDX

5 Hyderabad HDX

6 Bangalore HDX

7 Delhi HDX

8 Bhopal HDX

9 Nagpur HDX

10 Ahmedabad HDX

11 Allahabad HDX

12 Vijayawada HDX

13 Bhuvaneshwar HDX

14 Ranchi HDX

TOTAL 14


11/54

HDXEquipment Description &

Protection Schemes

January 12th2005


12/54

ASON: ITU-T, IETF, OIF

ITU-T

IETF

OIFImplementation

agreements

GMPLS protocols

ASON requirements

and architecture

OIF: Optical Interworking Forum

IETF: Internet Engineering Task Force


13/54

Optical Cross-Connect: HDXHighly Modular / Scalable OXC Infrastructure

Fully Non-blocking STS-1 / VC-4 Switch Matrix

HDX: 640G-1.28T, Single Shelf 3.84Tb/s Multi-Shelf Architecture

Integrated DWDM Optics - SFP Modules

Flexible service restoration and topologies

Mesh, Ring, Linear Protection

Restoration based on service attributes

Intelligent OXC enabling Next Generation Networking

Distributed, redundant & Integrated Control Plane

ITU-T ASON G.807/G.8080 ASON, GMPLS (Generalized MultiProtocol Label Switching) signaling

Network topology discovery and awareness

Multi-Services Management

STS-1/VC-4 to STS-192c/VC-4-64c Ports at 2.5/10/40Gb/s, 155/622Mb/s

Managed by Preside Optical Manager

Dimension : L X W X H : 1500 X 600 X 2200 cm

Power Consumption : 5400 Watts (Max)


14/54

1. Switch circuit pack2. Shelf Controller

3. MXT card

4. Traffic Cards ( 16 Nos of traffic slots)

1. 10G SR or DWDM cards4 ports per card2. 2.5G (STM16) card16 ports per card (IR, SR, LR)

3. STM4 / STM1 card - 16 ports per card (IR, SR, LR )

5. Power Supply Module (PSM)

6. Fan Module

Switch circuit pack.

Main Circuit Packs of HDX


15/54

Matrix and Timing (MXT) circuit pack.

Switch circuit pack diag


16/54

Switchcircuit pack diag

Fig. A.


17/54

Link Protection Mechanism offers the flexibility & simplicity to engineer Availability

Additionally, Mesh Restoration can be applied over any protection as a 2nd level

Protection & Restoration Schemes

DedicatedW

P

Predetermined andreserved backup forfast switching (nosharing)

Revertive Fast switching High availability At least half of the

network capacity is

reserved forprotection

Unprotected

W

No protection attransmission laye

Lowest cost &availability

Shared

Predetermined &configured backup forfast switching

Revertive Sharing over

segments w/ocommon risks

SDH like performance& behavior

Availability function ofnetwork Engineering

May beshared

W

W

P

P

Dynamic

Restoration paths aredynamically created(not predetermined)

Revertive High sharing Slower restoration

time Restoration &

availability function of

network Engineering

W

P

Mesh Protection Mesh Protection Mesh Restoration No Protection

APS

Standard APS Ring Linear

Fast switching Limited / no sharing of

protection capacity

APS Protection

50 msec N/AUp to 200 msec Secs50 msec


18/54

Acallis a service between two service access points. (End to End as in DX OPC)

A Connectionis a collection of Nodal cross-connections that allow the

transport of data between two service access points. (Nodal as in DX OPC).At

least one connectionmustbeassociated with a call.

The following figure-A shows an example of the call and connection

concept.

A call between node A and node Z needs to be established . The original

connection for tat call could be passing through A-B-Z.If the call needs to be restored due to failure in the original connection,

an alternative connection will be required and it could be A-C-D-Z.

Call and connection concept

Call and connection concept


19/54

Call and connection concept ( Continued)

Figure-A


20/54

Control Plane Call Management

Two types of call routing are supported at call creation: implicit andexplicit.

Implicit Routing:

An implicit call is a call for which only the source and destination pointsare specified for its connection(s), along with other service attributes

specified at the time of the connection request include:

Rate

CoS- Class of Service is used to define the call protection.

Routing Matric (Cost and Metric2)Maximum Martic Value

Restoration option (enable or disable)


21/54

Expl ic it Rou t ing:

An explicit call is a call for which the route is manually specified for its connection(s).

Explicit call are supported with three levels of granularity.

Node only : The control plane will compute the missing information (port / timeslot)

based on the given CoS and constraints.

Node and ports :The control plane will compute the timeslot for each port

Nodes, ports and timeslots: No calculation required from the control plane.

Control Plane Call Management


22/54

Call Engineering rules

The following is the list of call engineering rules.

Implicit routing is supported for all CoS , expect APS rings.

Explicit routing is supported for all CoS, including APS rings.

Explicit calls can be routed over failed and blocked ports.

For any given call a max. of 20 hops is allowed.

C t l Pl C ll M t


23/54

Control Plane Call Managementenables Rapid Service Delivery

1. Simple Point & Click service activation Single Step Provisioning

2. Automated Route selection (constrain-based routing engine)

1. Support Implicit Routing as well as Explicit Routing

3. Routing based on CoS / Protection, diversity and various Call attributes1. Protection: Ring, Linear, Shared Mesh, Unprotected

2. Attributes: Mesh Restoration, Call alarms ( Loss of Service, Restoration Complete)

3. Diversity based on Nodes, Trunks and SRLG

Steps:

1) Select Call Attributes:

- Dest./Egress point

- Bandwidth

- Source/Ingress point

- CoS / Protection

2) Select Activation

Successful creation of circuit

between A & Z points

Optical ManagerEMS

- Routing Metric

Distributed Intelligence


24/54

Call Management on HDX

Call Manager offers simple point and click operations for

call creation, deletion, query, restoration, edit and bridge and roll.

It also provide a graphical display of all connections associated with a particular call.

Call Edit Capabil i ty :

After the call has been created, the following attributes can be modified.

1. Call label2. Automatic mesh restoration options (enable/disable)3. Call alarms (enable/disable)

Call editing is supporting for any established calls in any call state, up, down, restored,

etc.


25/54

Protection and Restoration : CoS & AMR

The control plane supports the co-existence of multiple protection and /or

restoration mechanism through the use of Class o f Service (CoS) andautomatic mesh restorat ion (AMR).

CoS : is a call attribute used to define the call protection behavior and todifferentiate service quality levels.

Along with other routing criteria, CoS is specified at the time of call creation.

The control plan routes the calls over facilities which match the desired CoS.

Three Types of CoS :

APS - Automatic Protection Switching


26/54

Automatic protection switching(APS)

APS refers to well known protection schemes1+1

Linear/MSP and 2 Fiber / 4 Fiber BLSR / MSSP Ring

The control plane helps in automatic routing of calls over

APS working facilities.

The APS CoS supports all call rates from VC4 to VC4-64c.

Calls over 1+1 Linear/MSP facilities can be implicitly or

explicitly routed.

APS Automatic Protection Switching


27/54

Unprotected CoS does not offer any protection at the transportlayer, thus provides the lowest cost service.

Calls over unprotected facilities can be implicitly or explicitly

routed.

The unprotected CoS is supported on all call rates from VC4 to

VC4-64c.

Unprotected

SCN Communications


28/54

SCN CommunicationsCon tro l Plane I-NNI Traff ic

Overview Control Plane requires a Signaling

Communication Network to carry routing &

signaling traffic.

In-band SCN, using underlying DCC channels

MSDCC and RSDCC ports

Characteristics

In-fiber through embedded control channels

running IP over PPP (as per ITU-T G.7712)

IETF Standard (RFC2328) IP OSPF protocol

Resiliency; Multiple DCC for redundancy per link

IP-Reroute around failure

Dedicated to Control Plane traffic

Comms linkOptical fibre

I-NNI

SCN

I-NNI

SCN

SCN / IP Traffic re-route

SCN

Failure

No I-NNI

Failure

Control Plane


29/54

Control PlaneRout ing & Signal ing

1. GMPLS based protocols to establish and manage optical circuits

Distributed Routing for topology management (GMPLS OSPF-TE based, ITU-T G.7715.1)

- Distributed Signaling for Connection Management (GMPLS CR-LDP based, ITU-T G.7713.3).Support Call / Connection model required in G.8080, OIF latest IA.

2. Path Computation

1. Source based routing, Least hop-shortest path Dijkstra algorithm

2.Two user provisionable TE metrics are provided; cost, metric2

3.Traffic differentiation & CoS support

3. Control Plane resiliency & re-synchronization1) Each OXC/NE regularly broadcasts link sta

information (LSI)

2) OXC/NE uses LSIs to build/update local

network topology database

3) Local topology database is used to comput

optimal route based routing criteria

4) Signaling message sent along optimal rout

for path establishment

Auto Discovery


30/54

Controller

Controller

EMS/OSS

(OM)

Adjacency Discovery

AutoDiscoveryContro l Plane Disco very and Init ia l izat ion

Auto-Discovery features supported :

1. NE Self Discovery :1. Process to learn facilities learns local facilities characteristics and status, and updates its database with this local

node information.

2. Adjacency Discovery1. Adjacency discovery information is automatically propagated identifying the source network element and port

information.

3. Peer Discovery1. Automatic initiation of an I-NNI (Link Mgmt) and an OSPF-TE session (bandwidth availability) with neighbors.

2. Link Attributes validation and synchronization the Topology Databases on both nodes.

4. Network Topology Discovery1. Each NE shares its Topology Database to all its neighbors. Each NE Topology Manager therefore learns /

maintains the complete network topology through this process (via LSALink State Advertisement)

I-NNI


31/54

Cost and Metric

What is Cost?

What is Metric2 ?

Routing Criteria (Metric):


32/54

Shared mesh (SM)

The shared mesh protecting route is pre-determined and configured for fast

switching.

Provides deterministic and guaranteed performance(like APS) with a switch

time between 50 msec to 200 msec.

The control plane is involved in the provisioning of the shared mesh tunnels.

The control plane helps in automatic routing of calls over shared mesh

working routes.

Can be implicitly or explicitly routed.

The Shared mesh CoS is supported on all call rates from VC4 to VC4-64c

Shared Mesh Protection


33/54


34/54

Tunnel

W ki T l


35/54

Working Tunnel


36/54

Protection Tunnel

Protection Tunnels are reserved bandwidth that can be

used upon a failure of the working tunnel.

Shared Mesh Protection Tunnel Segments ( PTS) are always

configured on a per span basis for maximum sharing

Each PTS can be shared up to a maximum of three diversely

routed working tunnels


37/54

Protection tunnel

Shared Mesh Protection


38/54

1. Mesh Protection defined on a Tunnel / logical facility (bundling)

2. Protection Tunnel is pre-determined and shared (on a per link basis)

3. Control Channel associated with Protection Tunnel

4. Sharing is possible when W & P Tunnels dont have a common risk (SRLG Shared RiskLink Group)

5. Engineering rules to provide switch times < 200 msec1. SDH like behavior, predictable & deterministic2. Reversion, WTR

6. W & P build by control plane, however protection switch doesnt require any control planeassistance

7. Protection Switching Priorities: Lockout, Force, Automatic, Manual

MSPP

Mesh Restorationenabled

Mesh Restoration

disabled


39/54

1stLevel of Restoration

Upon a single failure ring,

linear, shared mesh, ordedicated systems will

rapidly restore service

2ndLevel of Restoration

Mesh Restoration used as a

2nd Level of Restoration isactivated upon a dual link, or

node failure event

Leverages existing capacity

to re-route services

improving availability

Initiate 2ndlevel backup for each of

the spare segments in use

Primary Protect Path

Secondary Protect Path

Working

Path

Dynamic Second Level of Restoration

Mesh Restoration as a 2ndlevel ofrestoration improves the networks

resiliency to multiple outages

Mesh Restoration


40/54

Mesh Restoration

1. Failure Detection using SDH failure indicators ( LOS, LOF, AIS etc.)

2. Dynamic restoration for best survivability and efficiency

3. Revertive behavior with Wait To RestoreWTR

4. Maintenance Friendly; Force Restoration, Lockout Restoration

5. Common Approach for Unprotected, APS Ring and Mesh Protection1. On first failure, Ring or Mesh protection attempts to protect service

2. Mesh Restoration takes over if 1stlevel cant protect (i.e. 2ndlevel) or facility is unprotected

6. Higher Availability & Robustness could be achieved by using mesh restoration orprotection & restoration with proper spare capacity to survive multiple failures

failure

notification

I1S1 D1I2

P1 P2

M h R i


41/54

Mesh Restoration

Built on the distributed routing and signaling capabilities of the control plane, using a

simple and robust restoration algorithm.

The control plane, in conjunction with SDH transport layer detection mechanism, learns

the location of the failure in the signaling notification,computes the next best route

based on feedback information, and reroutes each connection.

Since this mechanism relies heavily on software processing and signaling networks, therestoration time is slower than APS or shared mesh protection.

A t ti M h R t ti


42/54

Automatic Mesh Restoration

AMR is a call attribute used to enable to disable the automaticMesh restoration on a per call basis.

Can be used with any type of CoS and can be edited after

call creation.

Initiated upon failure detection and the first level of protection

is failed or there is no first level of protection .

AMR uses the same SDH failure indicators for rapid failure

detection ( LOS, LOF, AIS etc.)

A t ti M h R t ti


43/54


Mesh Restoration will recover from multiple failures as long as the bandwidth isavailable for restoration.

If a fault occurs such that service on the working call path is affected (after all

underlying protection schemes have been applied), the Control Plane will attempt

to restore the call by redialinga new path through the network.

This restoration will (implicitly) make use of any available working or sparebandwidth on Unprotected, 1+ 1 Linear working ports or Shared Mesh working

tunnels.

Restoration over ring working facilities is not allowed.

The control plane will make periodic attempt to restore traffic every 60 seconds

until resources are available and call is successfully restored or until the failureaffecting the call has been cleared.

HDX does not support pre-emption of existing traffic.

A t ti M h R t ti


44/54


User Request Based Restoration


45/54

Use equest ased esto at o

Forced restorat ion :

The forced restoration is a user initiated restoration, which moves a call

from its original path to the next best route based on the routing

criteria, if no higher priority request is (lockout) active.

Loc kou t restorat ion :

Lockout restoration ensures that a call is not moved from its original path

by suppressing the restoration, even in the presence of failure

condition or other manual operations.

Mesh Protection / Mesh Restoration


46/54

Trade-off : Bandwid th Eff ic iency v s. Resto rat ion Speed

Dedicated DynamicShared

Increased intelligence, control & complexity

Efficient bandwidth utilization & low cost

Simple, fast & reliable

Redundant & high cost

Shared Mesh ProtectionA nice balance Bandwidth efficiency CAPEX savings ...

Deploy working only where required

Share protection capacity network-wide

Deterministic switch times ... 50 - 200 ms

Simple to manage, pre-determined protection paths ... SDH-like

Shared Mesh Protection combines the advantages of Mesh and

SDH protection

HDX / HDXc & Optical IntelligenceM i M h N t k


47/54

Managing a Mesh Network

OpticalManager

Traffic Plane

Control Plane

Network

Data,

Events

Optical

Planner

Mesh Protection

Shared Protection built in Transport Plane Protection Switching Priorities (Lockout, Forced, Auto, Manual)

Protection Switch alarms (active, failed, etc.)

Single & Multi-Link, Priority levels, Local, Revertive, WTR

Unavailability of protection path notifications

In-Service Roll Over (local)

Mesh Restoration & Connect Mgmt Distributed architecture with local & end-to-end

Priority levels, Revertive, WTR

Restoration Priorities (Lockout, Forced, Auto)

Nesting of Restoration over Protection (APS & Mesh)

Call/Service failure and Restoration notifications

Optimization, Bridge & Roll (end-to-end)

Mesh & Control Plane Management Fit into the existing management architecture

Addition to basic functionsSLAT, Config, S/W download

Addition of call management functions

Management of Mesh restoration/protections (Tunnels)

Planning Tools Capacity Planning

Mesh Protection / Restoration analysis Traffic impact assessment under failure/maintenance scenarios

Capacity planning with what if scenarios

Traffic optimizationBulk Export /

Import

Montreal Lab Config :2.5G APS & Unp rotected CoS


48/54

5G S & U p otected CoS

501-P6 503-P6

502-P6 504-P6

502-12 501-P8

504-P13

501-P13

503-P16

501-P4

501-P1 504-P1

503-P1

502-P1

502-P9

501-P12

1+1

2FR 2.5G

501-P5

501-P1

502-P15

502-P4

Unprotected

NODE3NODE1

NODE2 NODE4

502-P12

502-P14

502-P3

503-P13

503-P15

501-P6

Montreal Lab Config:2 5G Shared Mesh


49/54

504-P2

501-P2

501-P3 504-P3

504-P12

501-P12

502-P11

501-P3

502-P7

501-P16

501-P9

501-P14

W3

W1

W2

W2P2

P3

P1-P2-P3

P3

P1

P2P4 W4

2.5G Shared Mesh

503-P14

503-P12

501-P10

NODE3NODE1

NODE2 NODE4

502-P10

502-11

501-P7

503-P11

503-P10

501-P2 501-P6

502-P2

501-P12

501-P11

501-P10

501-P5

502-P3

501-P4

Montreal Lab Config10G Shared Mesh/APS/Unp rotected


50/54

509/510-4

503/504-2

509/510-3

503/504-1

10G 4FR

510-1

509-3 503-3

507-2

509-4

10G Shared Mesh/APS/Unp rotected

NODE3NODE1

NODE2 NODE4

Unprotected

10G 2FR

509-1

509-2

510-2

10G 1+1

503-P8

502-P8

503-P3

503-P2

501-14

501-P16

501-P15

501-P8

507-P1

502-P8

508-P1

502-P3

501-P5

501-P10

W1

P1

P1

2.5G

1+1

Subtending

DX network

HDX DeploymentPhase I & II & Wavelength Plan


51/54

HDX DeploymentPhase I : 7 nos. of HDX Ordered

for MumbaiChennai Connectivity ( WavelengthsLambda 5 & 6 Chosen)

Mumbai MCN & Mumbai Cable Landing Station

Nagpur, Hyderabad, Bangalore, Chennai & VijayawadaI & C to start from second week of January 2005.

Resiliency Site : Ranchi HDX Ordered

HDX DeploymentPhase II : 5nos. of HDXTo be ordered

for remaining sites ( Wavelengths : Lambda 9 & 10 Chosen)

Ahmedabad, Delhi, Bhopal Bhuvaneshwar, Allahabad,

HDX DeploymentPhase I & II :


52/54

For all HDX to HDX - 10G mesh links, the

wavelength is to be taken through REGENXR cardsonly.

Mesh wavelengths can not be taken through DX

10G aggregates.

Hence, REGEN bays are being introduced at the in-

between DX sites likeSurat, Pune, Belgaum,

Hassan, Madurai etc.

Additional DWDM route created between Bangaloreto Chennai via Kolar by blowing G.655 cable from

Kolar to Krishanagiri.

Improved Network Availability


53/54

The Resiliency improvement program by way of providing

multiple paths to Switch locations and DWDM rings splitting (shorter ring circumference)

&

HDX basedMesh Restoration capability on diverse paths

will definitely improve the overall back bone network

availability and customer satisfaction.

Other SDH resiliency rings being implemented will provide multiple(diverse) routes for non-DX switch and STP locations connectivities.


54/54

Thank You!

Date post:	03-Jun-2018
Category:	Documents
Upload:	hassam-ahmad
View:	215 times
Download:	0 times

HDX_-_Presentation_-_12.01.2005

Documents