03 - Hit 7300 GMPLS - ASON Components and Layers [PDF]

Zitiervorschau

hiT 7300 GMPLS ASON Components and Layers

Objectives Upon completion of this eLearning, you will be able to:

• Describe ASON Components/Layers • • • • •

Describe Resources/Physical Interface Describe Component Link Describe Traffic Engineering-Link Describe LSP (Label Switched Path) Describe GMPLS Call

© 2018 Coriant. All rights reserved

00232 R7

2

ASON Components/Layers Overview © 2018 Coriant. All rights reserved

00232 R7

3

ASON Components/Layers Overview • ASON Components and Layers – – – – –

Physical Interface: Actual physical port. Component Link: Logical link between two I-NNI ports (representing the physical fiber connection). TE-Link: Association of traffic engineering parameters (metric and SRLG) to the Component Link. LSP (Label Switched Path): E2E GMPLS tunnel (ODUk). CALL: E2E ASON service built upon one (unprotected) or more (protected) LSPs. Calls are managed by (and stored in) the ingress node (A-node).

TE-Link Component Link

Physical Interface

Component Link

TE-Link

LSP

CALL

LSP

CALL

…

LSP

Configuration sequence

Frame encapsulation sequence

Call

Physical Interface

(Compliant with ITU ASON standard naming) © 2018 Coriant. All rights reserved

00232 R7

4

Physical Interface / Resources

Physical Interface / Resources

– Line Interface of I10T100G, – Line Interfaces of I02L200G, …

Physical Interface

Component Link

• Optical –TTP of Optical Coupler cards – Port of O09CC-2, …

• Optical –TTP of Filter cards – Port of F48MDV-1/S, …

• Amplifier Cards – LAMIC-2 – LAMPBC-1, …

Physical Interface / Resources

TE-Link

LSP

CALL

LSP

CALL

…

Resources are • Containment Ports of Transponder Cards

Physical Interface / Resources • Resources are the termination points of calls. • Amplifier, Filter Cards, Optical Coupler Cards, Transponder Cards, Muxponder Cards

Physical Interface I02L200G-2 CloudWave Line Card

Connections (CC)

CALL

Physical

CALL

Interface

Physical Interface Amplifier faced to Direction 01

Component Link

TE-Link

LSP

CALL

LSP

CALL

…

Line Interface 1 Cross

I-NNI

Physical Interface

CALL

Physical Interface Amplifier

…

Physical Alien Wavelength  Interface

© 2018 Coriant. All rights reserved

00232 R7

CALL

faced to Direction n

LSP Component Link

TE-Link

CALL

…

I10T100G-2 or Transponder Cards

Line Interface

…

…

Line Interface 2

LSP

CALL

I-NNI

O09CC-1 or Filter Cards 7

Resources • Resources are the termination points of calls. • GMPLS Calls are terminated on the – transponder, – filter or – amplifier cards.

ASON Browser: Resources, New Call © 2018 Coriant. All rights reserved

00232 R7

ASON Browser: Resources 8

View Port Properties of Line Port of Transponder Card • Properties of Line Port of Transponder card

1

ASON Browser: Resources

© 2018 Coriant. All rights reserved

00232 R7

Containment Port Properties of Line Port of Transponder Card

9

View Port Properties of Line Tx of Booster Card • Properties of Line Tx of Booster card – – – –

Port classifier Component Link name TE-Link name Remote NE ID

1

ASON Browser: Resources

© 2018 Coriant. All rights reserved

00232 R7

Containment Port Properties of Line Tx of Booster Card

10

View Port Properties of Optical Coupler cards

1

© 2018 Coriant. All rights reserved

00232 R7

11

Video: Physical Interface / Resources

© 2018 Coriant. All rights reserved

00232 R7

12

Component Links © 2018 Coriant. All rights reserved

00232 R7

13

Component Links A component link (CL) is a connection between two I-NNI ASON ports.

Optical Link

hiT 7300 Node A

I-NNI

LSP

Component Link

TELink

LSP

CALL

CALL

…

Physical Interface

CALL

LSP

…

Amplifier faced to Direction n

CALL

LSP

Component Link

TELink

Component Link

Physical Interface I-NNI

Amplifier faced to Direction m

hiT 7300 Node B

Component Link Management

Physical Interface

Component Link

TE-Link

ASON Browser: Component Links

LSP

CALL

LSP

CALL

…

Topics • Component link management • Component link management details • Creating a component link • Deactivate component link • Activate component link • Delete a component link

Component Link Management • Component Link Management window • Main > Configuration > ASON > Component Link > Management

1

Component Link Management

ASON Browser: Component Links © 2018 Coriant. All rights reserved

00232 R7

16

Component Link Properties • Component Link details, shows the configuration of a particular CL. 1

Component Link Management

Component Links Properties © 2018 Coriant. All rights reserved

00232 R7

17

Creating a Component Link • Click Main > Configuration > ASON > Component Link > New 1

5

Component Link Management

2

3

4 Component Link Management 18 © 2018 Coriant. All rights reserved

00232 R7

Deactivate Component Link When disable the component link Admin State, its TE-Link disappears.

3 2

Component Link Management

1

3

Component Link Management

© 2018 Coriant. All rights reserved

00232 R7

GMPLS Interface Configuration

19

Activate Component Link • Component Management: Configuration - ASON – Component Link - Management

1

Component Link Management

When Activiating the component link its administrative status enabled automatically When Activiate the component link its TE-Link is discovered automatically Component Link Management © 2018 Coriant. All rights reserved

00232 R7

20

Delete a Component Link • The operator could delete component links from TNMS DataBase only if they are with inactive status. 1

Component Link Management

© 2018 Coriant. All rights reserved

00232 R7

GMPLS Interface Configuration

2

21

Traffic Engineering (TE) Links © 2018 Coriant. All rights reserved

00232 R7

22

Traffic Engineering (TE) Links

Physical Interface

Component Link

TE-Link

LSP

CALL

LSP

CALL

…

• Traffic Engineering (TE) Links are connections between the NEs inside GMPLS domain which are used for path calculation and GMPLS signaling. • The control plane automatically build unbundled TE-Links. • ASON Manager displays the TE Links.

Topics • TE-Link Management • TE-Link Management Window © 2018 Coriant. All rights reserved

00232 R7

ASON Browser: TE-Links

23

TE Link Management • A traffic-engineering link is a configurable connection between ASON nodes or NEs. • The control plane automatically build unbundled TE-Links, and then no manual configuration by the operator will be required. • After triggering the Auto TE Link detection by LCT, the Control Plane will automatically create a TE-Link for each Component Link existent in the NE. • Then, ASON Manager is only required to retrieve, update and display the TE Links automatically created by the NEs. • If one Component Link is disabled and if the respective TE-Link have an inactive Call associated, the TE-Link will be in deactivate state. After the call be deleted it’s possible to delete TE-Link too.

© 2018 Coriant. All rights reserved

00232 R7

24

TE-Link Management Window • The TE-Link Management window displays the TE-Links that exist in the network and database. 1

TE-Link Management

© 2018 Coriant. All rights reserved

00232 R7

25

TE-Link Properties • Settings, Component Links, SRLGs, Bandwidth, Performance metrics 1

2 TE-Link Management

TE-Link Properties SRLGs

TE-Link Properties Component Links TE-Link Properties Settings © 2018 Coriant. All rights reserved

00232 R7

TE-Link Properties Bandwidth

TE-Link Properties Performance metrics 26

Label Switched Path (LSP) © 2018 Coriant. All rights reserved

00232 R7

27

Label Switched Path (LSP)

Physical Interface

Component Link

TE-Link

LSP

CALL

LSP

CALL

…

• A Label Switch Path (LSP) is a path through the network formed of crossconnected labels on a series of data plane links.

ASON Browser: Calls – Label Switched Path (LSP) © 2018 Coriant. All rights reserved

00232 R7

28

Routing and LSP Provisioning Ingress Node

• Route used by the LSP – can be selected in two different ways depending on the requirements of the Call, – the same route can be specified hop by hop by the user. – are preplanned in Coriant TransNet or – are calculated by the control plane.

• Dynamic Source Routing (DSR) calls – are calculated by the control plane at the call ingress node.

• Preplanned calls with explicit paths are – calculated by Coriant TransNet (one explicit route for each connection (working or restoration)).

ASON Map: Highlighted LSP

• The connection request to the ingress node must contain an explicit route for each connection.

Ingress Node

– This is a list of unnumbered component/data interfaces and label (wavelength) pairs.

LSP

• Connection management is only possible at ingress nodes. ASON Browser © 2018 Coriant. All rights reserved

00232 R7

29

GMPLS Call © 2018 Coriant. All rights reserved

00232 R7

30

Three Types of Connections • Permanent connection (PC) – The connection has two fixed endpoints and fixed cross-connect configuration along the path and stays up until deleted.

• Switched connection (SC) – Connection is created using the control plane with the exchange of signaling information between signaling elements within the control planes.

• Soft Permanent Connection (SPC) – are user-to-user connections created via the network management system specifying the properties of the connection at the end-point (ingress). © 2018 Coriant. All rights reserved

00232 R7

Reference Points and Connection Types

31

GMPLS Call

Physical Interface

Component Link

LSP

CALL

LSP

CALL

…

• One Call is one OCh Connection with one or more LSPs. • Calls management tasks, such as creation, deletion and other procedures can only be done at ingress NEs. • The GMPLS Calls are terminated on the transponder, filter or amplifier cards (Resources).

TE-Link

• Properties: – Direction: » bidirectional.

– Elementary signal/rate: » 2.5G, 10G, 40G, 100G and 200G.

– Connection type: » Soft Permanent Connection (SPC). » The connection is established within a single domain between two GMPLS peers.

ASON Browser: Calls © 2018 Coriant. All rights reserved

00232 R7

32

GMPLS Protection and Restoration in the hiT 7300 supported Calls

Supported types of Calls in the hiT 7300 NEs: • Unprotected Call: One LSP where the operator can provide an explicit or a dynamic full route (calculated by Coriant TransNet) or only the ingress and egress nodes (calculated by the GMPLS control plane). • Shared mesh restored Call: One LSP to be signaled and established (working LSP) and a restoration LSP only signaled but not cross-connected. • Dynamic Source Rerouting (DSR) Call: One LSP where the operator can include or exclude available resources of the route for the control plane recalculate restoration paths when failures occur. • Dynamically routed call with Shared Risk Link Group (SRLG) diversity: LSPs are routed with SRLG diversity to the LSPs of another call.

© 2018 Coriant. All rights reserved

00232 R7

GMPLS supported Calls

33

Call Protection/Restoration Schemes overview on hiT7300

• Unprotected - If the working path fails, there is no protection. The communication will be interrupted. • DSR (Dynamic Source Rerouting) - Multiple failure restoration. - Upon failure, a new restoration path (E2E) is computed and established by the ingress node. - The new LSP is established before the old LSP is torn down.  Pre-Planned Shared Restoration - Restores a path affected by a failure end-to-end to a preplanned restoration path. - Highly resources efficiency: the transport resources that are not occupied can be shared among restoration paths that don’t need the resources at the same time.

X

X

© 2018 Coriant. All rights reserved

00232 R7

Working Protecting Link failure

34

Scenario 1: Pre-Planned Shared Mesh Restoration • In scenario 1 switching is controlled by the GMPLS control plane. • Each working path (A-B-F-H and A-C-H) has a pre-planned restoration path which is not established. • The resources are pre-reserved but not used and can be shared among different restoration paths.

Pre-Planned Shared Mesh Restoration © 2018 Coriant. All rights reserved

00232 R7

35

Scenario 2: 1+1 Protection Combined with Shared-mesh Restoration

• In scenario 2, protection against double failures can be achieved by combining classic 1+1 Optical Channel Protection with GMPLS shared mesh restoration. • In order to achieve this, two independent GMPLS Calls are provisioned via RSVPTE signaling. Each Call comprises a working and a pre-planned restoration LSP, both disjointedly routed. 1+1 Protection Combined with Shared-mesh Restoration © 2018 Coriant. All rights reserved

00232 R7

36

Scenario 3: Dynamic Source Routing (DSR) • In scenario 3, protection can be achieved by DSR. • This process is completely treated by the distributed control plane signaling.

Dynamic Source Routing (DSR) © 2018 Coriant. All rights reserved

00232 R7

37

Scenario 4: DSR with Shared Risk Link Group (SRLG) Diversity

• In scenario 4, the call protection is achieved by using dynamic source routing with SRLG diversity. • In this scenario, the two optical channels OCh #1 and OCh #2 are routed as separate OCH DSR GMPLS calls (GMPLS routes the two optical channels SRLG diverse). • OCh #1 is routed via SRLG 3-4 and OCh #2 is routed via SRLG 5-9 being fully SRLG diverse to OCh #1. Dynamic Source Routing with Shared Risk Link Group diversity © 2018 Coriant. All rights reserved

00232 R7

38

Connection Types of Calls The following types of Calls are supported: • Transponder Calls (connection starting at transponder): – this is the normal connection type. It is possible to use different wavelengths on the working and restoration paths.

• Alien/friendly Calls (in case of an alien wavelength or friendly wavelength): – GMPLS services (unprotected or shared mesh restored) can only start at filter ports; working and restoration path must use the same wavelength.

• Mixed transponder/alien Calls: – GMPLS services can start/end at a filter port and end/start at a transponder; working and restoration path must use the same wavelength.

© 2018 Coriant. All rights reserved

00232 R7

39

Call Management – Call Properties • Manage GMPLS Calls

Call Properties ASON Browser: Call Management © 2018 Coriant. All rights reserved

00232 R7

40

Call Management – Route Path / LSP Mangement • Route Path / LSP Mangement

Call Cross Connection (CC)

ASON Traffic Engineering Link Route Path of an unprotected Call

LSP Management ASON Browser: Call Management © 2018 Coriant. All rights reserved

00232 R7

41

Call Management – PMP Configuration • PMP Configuration Activate selected PMPs Call

Selected PMP

PMP Configuration of a call ASON Browser: Call Management © 2018 Coriant. All rights reserved

00232 R7

42

Call Management – Graphical View of PM Data • Graphical View of PM Data

Current or History

Call

ASON Browser: Call Management © 2018 Coriant. All rights reserved

00232 R7

Graphical View of PM Data… 43

Call Management – Create New Call / Duplicate Call • The New Call window allows you to create a new call object either from scratch or by duplicating an existing call. • On the left pane of the New Call window you can find the steplist to create a call. • If you are duplicating a call, all fields are prefilled in with the original call settings, except for the name and A-/Z-end TP . © 2018 Coriant. All rights reserved

00232 R7

New Call Wizard

ASON Browser: New Call…

Flow of steps to create a call Call Management: Duplicate Call…

New Call Wizard

44

Summary In this eLearning, the following content was covered: • Describing ASON Components/Layers – – – – –

Describing Resources/Physical Interface Describing Component Link Describing Traffic Engineering-Link Describing LSP (Label Switched Path) Describing GMPLS Call

© 2018 Coriant. All rights reserved

00232 R7

45

For more information on Coriant Training Services: [email protected]