Scribd
Upload
5 views1 page

Requirement

The document outlines the requirements for configuring MPLS over metro links as part of the L3 enablement in the ME to MA migration process, specifically transitioning from outdated hardware to Cisco NCS 540 switches. It details the current and target configurations for various metro aggregation devices and emphasizes the need for successful provisioning of multiple metro links during designated out-of-order (OOO) change windows. The provisioning process involves creating a SPARK ticket, performing pre-checks, configuring devices, conducting post-checks, and includes rollback procedures in case of failure.

Uploaded by

rshyamanandan
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views1 page

Requirement

The document outlines the requirements for configuring MPLS over metro links as part of the L3 enablement in the ME to MA migration process, specifically transitioning from outdated hardware to Cisco NCS 540 switches. It details the current and target configurations for various metro aggregation devices and emphasizes the need for successful provisioning of multiple metro links during designated out-of-order (OOO) change windows. The provisioning process involves creating a SPARK ticket, performing pre-checks, configuring devices, conducting post-checks, and includes rollback procedures in case of failure.

Uploaded by

rshyamanandan
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Requirement

The requirements for this usecase is to configure MPLS over metro links as part of the L3 enablement required in ME to MA migration
process. Below
Table shows the Metro aggregation device type information and how currently they are setup with physical topology and their logical
configuration. Huawei
CX600-M2F and Nokia 7210 SAS-X hardware types have reached EOL - ‘End of Sale’. Hence, they cannot be purchased for Metro network
expansion; Sky has decided to use the Cisco NCS 540 as new metro switches. Currently these NCS540 are deployed with legacy
configuration; Our target is to develop this use case on DNE in order to migrate these Metro aggregation devices to the strategic (target)
topology and configurations.
Hostname prefix Hardware type Today (Legacy configuration) Strategic (Target)

Physical Logical Physical Logical

MA[n] NCS540 Core – LAG with sub-interfaces MPLS and L2 (Vlan switch) Core* – LAG MPLS + BGP

ME[n] CX600-M2F Core – LAG with sub-interfaces MPLS and L2 (Vlan switch) Core* – LAG MPLS + BGP

AS10[x] 7210 SAS-X Core – Physical interface with sub-interfaces MPLS and L2 (Vlan switch) Core* – LAG MPLS + BGP

As part of this use case, This document states design for Metro Link only. The links can be for POP, Tier 1 and Tier 2 Topologies. There can
be multiple metro links provisioning request in a OOO time and either all links must be provisioned successfully or None of them. The Metro
service provisioning process will require a SPARK ticket so the work can happen during the OOO change window. The process consists of
the DNE updating the provided SPARK, performing pre-checks, configuration of devices and then post-checks. there would be rollback of
configurations in case of failure. Process ends with updating SPARK ticket with work-notes and logs.

You might also like