FY24 Champion Program Lab Use Case Challenge

Instructions to follow for this Challenge

• Challenge start Date – 21st of June

• Challenge end Date – 30th of Oct
• Points received for this Challenge completion – 30 points
• This challenge has 3 lab use cases on Routing and Switching, 3 lab use cases on
Optical and 3 lab use cases on Nav NCS. Out of these 9 Lab Use cases Choose any 1
as per your area of focus and complete this challenge.
• R&S Lab Use cases are to be performed on the CAL platform
• Optical Lab Use cases are to be performed on the Planner Plus platform
• Nav NCS Lab Use cases are to be performed on the CEC Platform
• To learn more about these Ciena Sales Design Tools please refer to CPNe - Ciena
Sales Tools Deep-Dive Program
• In case of any query reach out to us via email at [email protected]
• All the submissions to be done via email [email protected] and videos to be
submitted over Champions Community Page.
 Routing and Switching Lab Use Cases

Introduction to the ABC Industry

ABC Technologies intends to deploy a “Green Field” installation throughout the

Atlantis region. They have categorised the whole region into “3 major monitoring
divisions” as per the criticality of the site.

• Lab Use Case 1 (Site 1) - CPE (customer premise equipment) Devices Site.
• Lab Use Case 2 (Site 2) - Access Devices Site (SR – Enable).
• Lab Use Case 3 (Site 3) - Aggregation Site (Layer 3 VPN with ISIS).

NOTE: - As of now ABC is not planning to implement Ciena SDN Controller/NMS on

Site A as they already have Orchestration Software “Apollo” available in the system
to help with provisioning and Orchestration. They want to see consolidated
Topology on the central Apollo server for Ciena and Other devices.

Lab Use Case 1 (Site 1) - CPE (customer premise equipment) Devices Site
To optimize customer experiences, ABC Technologies has implemented a comprehensive
solution at Site 1-CPE, integrating Ciena's Universal Aggregation Solution with PON (Passive
Optical Network) technology. This deployment is further enhanced with the incorporation of
Ciena's virtual Broadband Network Gateway (vBNG) and management via Microclimate
Management System (MCMS). The testing site is equipped with Ciena's 8110 and 5130
platforms operating on Service-Aware Operating System (SAOS) version 10. X, ensuring
robustness and scalability in service delivery.

• Here are your Challenges to perform in this Lab Use Case 1

1. Login to the device and verify the parameters related to the PON plug.
2. Login to MCMS and provide the uOLT plug parameter.
3. Login to vBNG add a new subscriber to the system and assign them a new IP using
DHCP Server
4. Check Login credential validation for new subscriber’s add-in part -3

• Champions to submit the below details over a Word Doc file

1. Verify PON Plug Parameters:

Login to the device (provide instructions for logging in). Navigate to the
section/menu where PON plug parameters are displayed. Take a screenshot showing
the relevant parameters related to the PON plug.
2. Provide uOLT Plug Parameters via MCMS:
Login to the MCMS (Management and Control System). Access the section/menu
that provides uOLT plug parameters. Capture a screenshot displaying the uOLT plug
parameters.
3. Add a New Subscriber and Assign a New IP via vBNG:
Access the vBNG (Virtual Broadband Network Gateway). Navigate to the subscriber
management section. Add a new subscriber and ensure they are assigned a new IP
address using the DHCP server. Take a screenshot showing the successful addition of
the new subscriber and the assigned IP address.
4. Validate Login Credentials for New Subscribers:
Attempt to log in with the credentials of the new subscriber added in step 3. Ensure
that the login is successful. Capture a screenshot showing the successful login screen
or any relevant validation messages.
Lab Use Case 2 (Site 2) - Access Devices Site (SR – Enable)

To enhance customer experiences, ABC Technologies has deployed an extensive solution at

Site 2- Access Device Site. This implementation integrates Ciena's basic point-to-point Layer
3 Virtual Private Network (L3VPN) service within a protected Multiprotocol Label Switching-
Segment Routing (MPLS-SR) architecture. This strategic initiative ensures network
redundancy through a safeguarded infrastructure while streamlining operational efficiency
through Segment Routing.
By incorporating Segment Routing, ABC Technologies gains several advantages, including
enhanced simplicity, precise traffic engineering capabilities, improved scalability, rapid
rerouting capabilities for fault tolerance, service differentiation options, heightened
network flexibility, optimized resource allocation, and seamless interoperability with
existing network frameworks. This holistic approach not only bolsters network resilience but
also elevates service quality and responsiveness, aligning with ABC Technologies'
commitment to delivering unparalleled customer satisfaction.

• Here are your Challenges to perform in this Lab Use Case 2

1. Employing GNS3, replicate the network topology as outlined in the provided

description.
2. Establish MPLS underlay functionality within the designated topology to enhance
network efficiency and scalability.
3. Implement SR-MPLS protocol across the specified topology to leverage its
advantages in simplifying network operations and optimizing traffic routing.
4. Enable a layer-3 Virtual Private Network (VPN) connection from Customer Edge (CE)-
1 to CE-2 within the configured network infrastructure to ensure secure and efficient
data transmission between the designated endpoints.

• Champions to submit the below details over a Word Doc file

1. Replicate Network Topology:

You'll need to create a network topology in GNS3 that matches the provided
description. This involves adding routers, switches, and other necessary devices and
connecting them according to the topology. Please provide a Screenshot of the same
2. Establish MPLS Underlay:
 Configure MPLS on the routers in your topology to create the MPLS underlay
network. This involves enabling MPLS protocols like LDP (Label Distribution Protocol)
or RSVP-TE (Resource Reservation Protocol - Traffic Engineering) on the routers.
Please provide a Screenshot of the same
3. Implement SR-MPLS Protocol:
Configure Segment Routing (SR) on the routers to implement SR-MPLS protocol
across the network. This involves enabling SR on the routers and configuring the
Segment Routing policies for traffic engineering and optimization. Please provide a
Screenshot of the same
4. Enable Layer-3 VPN Connection:
Configure layer-3 VPN (such as MPLS L3VPN) between CE-1 and CE-2 to establish a
secure and efficient data transmission path between them. This involves configuring
VPN-related settings on the PE (Provider Edge) routers, including VRF (Virtual
Routing and Forwarding) instances, route leaking, and VPN routing protocols. Please
provide a Screenshot of the same

Lab Use Case 3 (Site 3) - Aggregation Site (Layer 3 VPN with ISIS)

To enrich customer experiences, ABC Technologies has implemented a robust solution at Site
3- Aggregation Site. This integration features Ciena's fundamental point-to-point Layer 3
Virtual Private Network (L3VPN) service within a resilient Ring architecture, fortified with
ISIS protocol. This strategic deployment ensures network redundancy through a fortified
infrastructure, concurrently streamlining operational efficiency through ISIS.
This comprehensive approach not only fortifies network resilience but also enhances service
quality and responsiveness, aligning seamlessly with ABC Technologies' steadfast dedication
to delivering unparalleled customer satisfaction.

• Here are your Challenges to perform in this Lab Use Case 2

1. Utilize GNS3 to replicate the network topology as specified in the provided

description.
2. Establish MPLS with LDP underlay functionality within the designated topology to
enhance network efficiency and scalability.
3. Implement ISIS protocol across the specified topology to capitalize on its benefits in
simplifying network operations and optimizing traffic routing.
4. Enable a layer-3 Virtual Private Network (VPN) connection from Customer Edge
(16001)-03 to (16004)-03 within the configured network infrastructure to ensure
secure and efficient data transmission between the designated endpoints.

• Champions to submit the below details over a Word Doc file

1. Replicate Network Topology in GNS3:

Use GNS3 to recreate the network layout described in the provided description.
Once the topology is configured, take a screenshot showing the entire network
layout within GNS3, including routers, switches, and connections.
2. Establish MPLS with LDP Underlay:
Capture a screenshot of the router configurations showing the MPLS and LDP
settings. Configure MPLS with LDP (Label Distribution Protocol) on the routers within
the designated GNS3 topology.
3. Implement ISIS Protocol:
Configure ISIS (Intermediate System to Intermediate System) protocol across the
network topology in GNS3. Take a screenshot of the router configurations
demonstrating the ISIS protocol implementation.
4. Enable Layer-3 VPN Connection:
Set up a layer-3 VPN connection between Customer Edge (16001)-03 and (16004)-03
within the GNS3 network infrastructure. Provide a screenshot showing the VPN
configuration on the relevant routers and any verification commands/results
indicating the successful establishment of the VPN connection.
 Optical Lab Use Cases

Lab Use Case 1

The objective of this exercise is to assess your team's ability to collaboratively design and
present a comprehensive network solution that meets customer requirements using Ciena
products. The exercise is designed to evaluate your technical knowledge, teamwork,
presentation skills, and ability to address customer needs effectively.

Network Infrastructure and Traffic Requirements

Introduction

The customer is a Swedish-based investment company belonging to the largest Swedish

public pension funds. We started building our network in 1993, when our Autonomous
System, AS1299, was allocated, and we’ve grown organically ever since. Our network now
stretches 70,000 km across Europe, North America and Asia and lets you connect directly to
more than 2,300 wholesale customers in more than 125 countries.
Customer offers services that help people and companies communicate in an easy, efficient,
and environmentally friendly way by providing network access and telecommunication
services across the globe. Our focus is to deliver a world-class customer experience while
ensuring the quality of our networks and maintaining a cost-efficient structure.

Tender Invitation

The customer aims to select Suppliers for ‘next generation’ Open-Optical Line Systems (O-
OLS) and Open-Optical Transponders (O-OT) platforms for inter-regional networks, i.e., long
haul, and hereby kindly invite you to participate in the tendering procedures via this RFQ for
the supply of optical transport platforms for long-haul networks.

Focus Area
Customer business and brand are built on reliability. Fundamentally, we have high-quality in
our networks in all our markets throughout the world. Every failure will harm our brand.
Demand for capacity is virtually unlimited and requires network upgrades to support new
value-added services. Capital expenditure includes investments in increased network
capacity and upgrades to support new value-added services.
Customers judge us on their total experience of our offerings, functionality, and price as well
as the approach from customer support. Customer support alone cannot resolve the
customers’ problems, but together we can do it. Firstly, we need to have short response
times. Secondly, we need to fix the customers’ problems the first time they contact us.

Description and scope of the RFQ:

Open long-haul DWDM/OLS/OT network.

The customer has deployed a DWDM network throughout its footprint in both the United
States and Europe. The purpose of this RFQ is to secure effective solutions, technology
platforms, and pricing to ensure that we can grow our network further with controlled and
agreed price points to ensure we remain competitive in the market. This RFQ will continue
to focus on openness and disaggregation of the optical technology and therefore optical line
systems and transponders shall be able to function as independent autonomous systems
and be capable of interoperating with other Supplier systems. Customers will choose
Suppliers for an open optical line system and transponders separately in this RFQ. The
continued build-out of the network is ongoing and therefore the desire to secure the
necessary technical and commercial elements relating to this RFQ is paramount as we would
like to execute our plans as soon as practically possible.

Network Topology

Network Infrastructure Requirements and Traffic Matrix

Guidance:
▪ Assumed network with ROADM drop points according to the picture in Slide# 6.
▪ Site 6 cannot support transponder re-gen.
▪ Fiber and ROADM, ILA placement details can be found in separate fiber calculator
attachments. Refer attached sheet
▪ The traffic matrix tab shows yearly traffic growth figures for 100G and 400G
services/clients. Refer attached sheet
▪ From the year 2027 all capacity/traffic growth needs to happen on the L-band, even
if there is an available C-band spectrum.
▪ All C and L band traffic should fit into a single C+L band photonic layer.
▪ No protection is required at the service level
▪ The proposed modem should be 400G and above.
The Site Details – Lab Use Case 1
Source NE Type
Site21 ROADM
Site20 ROADM
ILA22 ILA
ILA23 ILA
ILA24 ILA
ILA25 ILA
Site19 ROADM
ILA26 ILA
Site18 ROADM
ILA27 ILA
ILA28 ILA
ILA29 ILA
Site17 ROADM
ILA30 ILA
ILA31 ILA
ILA32 ILA
ILA33 ILA
ILA34 ILA
ILA35 ILA
Site13 ROADM
Site12 ROADM
ILA71 ILA
ILA70 ILA
ILA69 ILA
ILA68 ILA
Site11 ROADM
ILA67 ILA
ILA66 ILA
ILA65 ILA
ILA64 ILA
ILA63 ILA
Site10 ROADM
ILA6 ILA
ILA5 ILA
ILA4 ILA
ILA3 ILA
ILA2 ILA
ILA1 ILA
Site16 ROADM
Site4 ROADM
ILA52 ILA
ILA51 ILA
ILA50 ILA
Site3 ROADM
ILA49 ILA
ILA48 ILA
Site2 ROADM
ILA53 ILA
ILA54 ILA
ILA55 ILA
ILA56 ILA
ILA57 ILA
ILA58 ILA
ILA59 ILA
ILA60 ILA
ILA61 ILA
ILA62 ILA
Site8 ROADM
Site7 ROADM
ILA36 ILA
ILA37 ILA
ILA38 ILA
ILA39 ILA
ILA40 ILA
ILA41 ILA
Site6 ROADM
ILA42 ILA
Site5 ROADM
ILA7 ILA
ILA8 ILA
ILA9 ILA
ILA10 ILA
ILA11 ILA
ILA12 ILA
Site9 ROADM
ILA14 ILA
ILA15 ILA
ILA16 ILA
ILA17 ILA
ILA18 ILA
ILA19 ILA
ILA20 ILA
ILA21 ILA
ILA72 ILA
ILA73 ILA
Site14 ROADM
ILA43 ILA
ILA44 ILA
ILA45 ILA
ILA46 ILA
 ILA47 ILA
Site15 ROADM
Site1 ROADM

Fiber Details – Lab Use Case 1

Source NE Destination NE Fiber type Length (km) Loss coefficient (dB/km) Fiber loss (dB)
Site21 Site20 NDSF (G.652) 5.5 0.79 4.37
Site20 ILA22 TWC (G.655) 108 0.26 27.92
ILA22 ILA23 TWC (G.655) 97.7 0.25 24.44
ILA23 ILA24 TWC (G.655) 102.7 0.25 25.65
ILA24 ILA25 TWC (G.655) 88.3 0.26 23.2
ILA25 Site19 NDSF (G.652) 1 3.24 3.24
Site19 ILA26 NDSF (G.652) 107 0.26 27.69
ILA26 Site18 NDSF (G.652) 99.8 0.25 24.96
Site18 ILA27 NDSF (G.652) 110.5 0.25 27.52
ILA27 ILA28 TWC (G.655) 96.3 0.25 24.11
ILA28 ILA29 NDSF (G.652) 84 0.25 21.15
ILA29 Site17 NDSF (G.652) 51.8 0.28 14.43
Site17 ILA30 NDSF (G.652) 67.8 0.27 18.27
ILA30 ILA31 NDSF (G.652) 121 0.25 30.03
ILA31 ILA32 NDSF (G.652) 69.8 0.27 18.74
ILA32 ILA33 NDSF (G.652) 83.3 0.26 22
ILA33 ILA34 NDSF (G.652) 88.6 0.25 22.27
ILA34 ILA35 NDSF (G.652) 80.4 0.26 21.3
ILA35 Site16 NDSF (G.652) 8.8 0.58 5.11
Site13 Site12 TWPLUS (G.655) 44 0.31 13.56
Site12 ILA71 TWPLUS (G.655) 91.4 0.26 23.95
ILA71 ILA70 TWPLUS (G.655) 118.4 0.25 29.41
ILA70 ILA69 TWPLUS (G.655) 106.8 0.25 26.64
ILA69 ILA68 TWPLUS (G.655) 103.5 0.25 25.83
ILA68 Site11 NDSF (G.652) 86.2 0.26 22.69
Site11 ILA67 NDSF (G.652) 82.2 0.26 21.73
ILA67 ILA66 NDSF (G.652) 99.3 0.25 24.84
ILA66 ILA65 NDSF (G.652) 98.4 0.25 24.61
ILA65 ILA64 NDSF (G.652) 39.6 0.27 10.52
ILA64 ILA63 NDSF (G.652) 87 0.25 21.89
ILA63 Site10 NDSF (G.652) 96.3 0.26 25.12
Site10 ILA6 TWC (G.655) 22 0.38 8.28
ILA6 ILA5 TWC (G.655) 104 0.26 26.97
ILA5 ILA4 TWC (G.655) 109.5 0.25 27.29
ILA4 ILA3 TWC (G.655) 93.3 0.25 23.4
ILA3 ILA2 TWC (G.655) 97.5 0.25 24.39
ILA2 ILA1 TWC (G.655) 83.7 0.25 21.08
ILA1 Site16 TWC (G.655) 106.5 0.26 27.56
Site16 Site15 NDSF (G.652) 5.5 0.79 4.37
Site4 ILA52 NDSF (G.652) 84.7 0.26 22.33
ILA52 ILA51 NDSF (G.652) 124.4 0.26 31.86
ILA51 ILA50 NDSF (G.652) 96.3 0.25 24.1
ILA50 Site3 NDSF (G.652) 113.3 0.25 28.19
Site3 ILA49 NDSF (G.652) 89.4 0.25 22.46
ILA49 ILA48 NDSF (G.652) 79.1 0.25 19.98
ILA48 Site2 NDSF (G.652) 66 0.27 17.84
Site2 ILA53 NDSF (G.652) 90.8 0.26 23.79
ILA53 ILA54 TWC (G.655) 87.6 0.25 22.03
ILA54 ILA55 TWC (G.655) 92.1 0.25 23.11
ILA55 ILA56 TWC (G.655) 98.8 0.25 24.73
ILA56 ILA57 TWC (G.655) 94.9 0.25 23.77
ILA57 ILA58 TWC (G.655) 99.3 0.25 24.82
ILA58 ILA59 TWC (G.655) 95.3 0.25 23.86
ILA59 ILA60 TWC (G.655) 100.4 0.25 25.1
ILA60 ILA61 TWC (G.655) 98.3 0.25 24.59
ILA61 ILA62 TWC (G.655) 95.7 0.25 23.96
ILA62 Site1 TWC (G.655) 101.2 0.26 26.29
Site8 Site7 NDSF (G.652) 11 0.51 5.64
Site7 ILA36 NDSF (G.652) 97 0.26 25.27
ILA36 ILA37 NDSF (G.652) 92.4 0.25 23.17
ILA37 ILA38 NDSF (G.652) 65.4 0.26 16.7
ILA38 ILA39 NDSF (G.652) 95.6 0.25 23.95
ILA39 ILA40 NDSF (G.652) 81.7 0.25 20.62
ILA40 ILA41 NDSF (G.652) 81.7 0.25 20.62
ILA41 Site6 NDSF (G.652) 87 0.26 22.88
Site6 ILA42 TWC (G.655) 81.6 0.26 21.59
ILA42 Site5 TWC (G.655) 91.8 0.26 24.03
Site5 Site4 NDSF (G.652) 38.5 0.32 12.24
Site6 ILA7 NDSF (G.652) 82.1 0.26 21.71
ILA7 ILA8 TWRS (G.655) 80.5 0.25 20.33
ILA8 ILA9 TWRS (G.655) 74.3 0.25 18.84
ILA9 ILA10 TWRS (G.655) 62 0.26 15.87
ILA10 ILA11 TWRS (G.655) 109.4 0.25 27.26
ILA11 ILA12 NDSF (G.652) 84.4 0.25 21.27
ILA12 Site9 NDSF (G.652) 96.8 0.25 24.24
Site9 ILA14 NDSF (G.652) 93.3 0.25 23.39
ILA14 ILA15 NDSF (G.652) 100.4 0.25 25.09
ILA15 ILA16 NDSF (G.652) 87.8 0.25 22.07
ILA16 ILA17 NDSF (G.652) 75.9 0.25 19.23
ILA17 ILA18 NDSF (G.652) 111.9 0.25 27.85
ILA18 ILA19 NDSF (G.652) 81.1 0.25 20.46
ILA19 ILA20 NDSF (G.652) 70.3 0.25 17.87
ILA20 ILA21 NDSF (G.652) 95.5 0.25 23.92
ILA21 Site10 NDSF (G.652) 85.8 0.26 22.59
Site10 ILA72 NDSF (G.652) 107.6 0.26 28.33
 ILA72 ILA73 TWPLUS (G.655) 98.2 0.25 24.57
ILA73 Site14 TWPLUS (G.655) 101.4 0.26 26.34
Site14 ILA43 LEAF (G.655) 92.8 0.26 24.28
ILA43 ILA44 LEAF (G.655) 99.8 0.25 24.94
ILA44 ILA45 LEAF (G.655) 102.4 0.25 25.58
ILA45 ILA46 LEAF (G.655) 94.8 0.25 23.76
ILA46 ILA47 LEAF (G.655) 101.3 0.25 25.31
ILA47 Site15 NDSF (G.652) 100.5 0.26 26.13

Traffic Matrix – Lab Use Case 1

C-Band Traffic Requirement L-Band Traffic Requirement

Large traffic flows 2024 2025 2026 Large traffic flows 2027 2028
Sector Source Destination 100G 400G 100G 400G 100G 400G Sector Source Destination 100G 400G 100G 400G
Site8-Site4 Site8 Site4 2 1 2 1 1 Site8-Site4 Site8 Site4 1 2 1 2
Site8-Site5 Site8 Site5 1 1 1 1 1 Site8-Site5 Site8 Site5 1 1 1 1
Site7-Site4 Site7 Site4 1 1 1 Site7-Site4 Site7 Site4 1 1 1 1
Site7-Site5 Site7 Site5 1 1 1 Site7-Site5 Site7 Site5 1 1 1
Site4-Site16 Site4 Site16 2 1 2 1 1 Site4-Site16 Site4 Site16 1 2 1 2
Site4-Site15 Site4 Site15 1 1 1 1 1 Site4-Site15 Site4 Site15 1 1 1 1
Site5-Site16 Site5 Site16 1 1 1 Site5-Site16 Site5 Site16 1 1 1 1
Site5-Site15 Site5 Site15 1 1 1 Site5-Site15 Site5 Site15 1 1 1
2024 2025 2026 2027 2028
Medium traffic flows 100G 400G 100G 400G 100G 400G Medium traffic flows 100G 400G 100G 400G
Site13-Site16 Site13 Site16 2 1 2 1 1 Site13-Site16 Site13 Site16 1 1 1 1
Site13-Site15 Site13 Site15 1 1 1 Site13-Site15 Site13 Site15 1 1 1 1
Site12-Site16 Site12 Site16 1 1 1 Site12-Site16 Site12 Site16 1 1
Site12-Site15 Site12 Site15 1 1 1 Site12-Site15 Site12 Site15 1 1
Site13-Site4 Site13 Site4 2 1 2 1 1 Site13-Site4 Site13 Site4 1 1 1 1
Site13-Site5 Site13 Site5 1 1 1 Site13-Site5 Site13 Site5 1 1 1 1
Site12-Site4 Site12 Site4 1 1 1 Site12-Site4 Site12 Site4 1 1
Site12-Site5 Site12 Site5 1 1 1 Site12-Site5 Site12 Site5 1 1
Site21-Site17 Site21 Site17 1 1 2 1 1 Site21-Site17 Site21 Site17 1 1 1 1
Site20-Site17 Site20 Site17 1 2 1 Site20-Site17 Site20 Site17 1 1 1
Site16-Site17 Site16 Site17 1 1 2 1 1 Site16-Site17 Site16 Site17 1 1 1 1
Site15-Site17 Site15 Site17 1 2 1 Site15-Site17 Site15 Site17 1 1 1
Site1-Site4 Site1 Site4 1 1 2 1 1 Site1-Site4 Site1 Site4 1 1 1 1
Site1-Site5 Site1 Site5 1 2 1 Site1-Site5 Site1 Site5 1 1 1
2024 2025 2026 2027 2028
Small traffic flows 100G 400G 100G 400G 100G 400G Small traffic flows 100G 400G 100G 400G
Site8-Site9 Site8 Site9 2 2 1 1 Site8-Site9 Site8 Site9 1 1 1 1
Site16-Site9 Site16 Site9 2 2 1 1 Site16-Site9 Site16 Site9 1 1 1 1
Site1-Site2 Site1 Site2 2 2 1 1 Site1-Site2 Site1 Site2 1 1 1 1
Site4-Site2 Site4 Site2 2 2 1 1 Site4-Site2 Site4 Site2 1 1 1 1
Site3-Site1 Site3 Site1 2 2 1 1 Site3-Site1 Site3 Site1 1 1 1 1
Site3-Site4 Site3 Site4 2 2 1 1 Site3-Site4 Site3 Site4 1 1 1 1
Site16-Site11 Site16 Site11 2 2 1 1 Site16-Site11 Site16 Site11 1 1 1 1
Site12-Site11 Site12 Site11 2 2 1 1 Site12-Site11 Site12 Site11 1 1 1 1
Site15-Site14 Site15 Site14 2 2 1 1 Site15-Site14 Site15 Site14 1 1 1 1
Site12-Site14 Site12 Site14 2 2 1 1 Site12-Site14 Site12 Site14 1 1 1 1
Site5-Site14 Site5 Site14 2 2 1 1 Site5-Site14 Site5 Site14 1 1 1 1
Site20-Site19 Site20 Site19 2 2 1 1 Site20-Site19 Site20 Site19 1 1 1 1
Site16-Site19 Site16 Site19 2 2 1 1 Site16-Site19 Site16 Site19 1 1 1 1
Site20-Site18 Site20 Site18 2 2 1 1 Site20-Site18 Site20 Site18 1 1 1 1
Site16-Site18 Site16 Site18 2 2 1 1 Site16-Site18 Site16 Site18 1 1 1 1

• Champions to submit the below details over a Word Doc or PPT file

1. Device Selection: Select a Ciena device that best meets the customer's
requirements.
2. Link Budgets: Calculate link budgets/ Network planning based on given fiber
parameter
3. Bill of Material: Detailed BOM is required per site with power consumption
4. Utilization: Spectrum utilization is required to check the C+L band fulfillment.
Lab Use Case 2

The objective of this exercise is for the Team to prepare an option to help new
telco/hyperscale customers decide the best possible solutions available with the Ciena
platforms based on Cost and Scalability.

Network Infrastructure and Traffic Requirements

Long Haul Network Topology

Fiber Route Length (KMs) Estimated

TOTAL [ KM
FP / LINK LINK
]
Link#1 Site-B -Site-A I PATH1 1700
Link#2 Site-B -Site-A PATH2 2570
Link#3 Site-B - Site-C 1010
Link#4 Site-B - Site-E 1500
Link#5 Site-B - Site-D 980
Link#6 Site-E - Site-D 460
Link#7 Site-C - Site-D 680
Link#8 Site-C - Site-E 980
Link#9 Site-A - Site-C 1900
Link#10 Site-A - Site-F 1800
Link#11 Site-C - Site-F 2000
Link#12 Site-E- Site-F 2100
 Traffic Matrix | Indicative uniform Traffic Matrix

TRAFFIC MATRIX - Tbps

Tbps Site-A Site-B Site-C Site-D Site-E Site-F

Site-A x 2 Tb 2 Tb 2 Tb 2 Tb 1 Tb
Site-B x x 2 Tb 2 Tb 2 Tb 1 Tb
Site-C x x x 2 Tb 2 Tb 1 Tb
Site-D x x x x 2 Tb 1 Tb
Site-E x x x x x 1 Tb
Site-F x x x x x x
25 Tb
Network Infrastructure requirements and Traffic Matrix

Guidance:
▪ Assumed network with ROADM drop points according to the picture in Slide# 4.
▪ Consider NDSF G652 fiber @ 0.22/dB per KM with 0.5dB HPPL/TPPL + 1dB fiber
repair margin. Consider the ILA’s site’s tentative 80km span between ROADM OR
best as per your knowledge. Refer to slide # 5 for ROADM connectivity and distances.
▪ RLS C&L CDA Architecture with TT OPS
▪ No RAMAN amplifier will be used in the proposal.
▪ The traffic matrix is shown in slide # 5. Day 1 traffic requirement is 25T and need to
check the scalable traffic based on the spectrum available in C+L Band.
▪ All traffic should be OPS-protected.
▪ The proposed modem should be 400G and above

• Champions to submit the below details over a Word Doc or PPT file

1. Device Selection: Select a Ciena device that best meets the customer's
requirements.
2. Link Budgets: Calculate link budgets/ Network planning based on a given fiber
parameter
3. Bill of Material: Detailed BOM is required per site with power consumption
4. Utilization: Spectrum utilization is required to check the C-band fulfilment.
Lab Use Case 3
Network Infrastructure and Traffic Requirements

Network Infrastructure Requirements and Traffic Matrix

Network Design:
• The proposed hardware should be L-band-ready.
• Site 1 to Site 10 all are ROADM Sites
• Line capacity: Minimum 400G and above
• Client port: 100Gbps and 10Gbps
• Ultimate capacity: Minimum 26TBps per fiber pair (C-band)
• Initial Capacity: TBps (Consider 2xWL5e as WL6e wave with 2x channel spacing as well)
Link Budgets:
• Consider NDSF fiber @0.3dB/km loss co-efficient
• 0.5dB HPPL/TPPL loss with 3dB fiber repair margin
• Fiber length is mentioned on the link in the topology diagram. Refer to slide#3.
Traffic Matrix
No of No of
S.no Site-A Site-B Protection
100G 10G
1 Site-1 Site-3 8 NO
2 Site-3 Site-8 10 10 NO
3 Site-10 Site-8 5 NO
4 Site-3 Site-5 2 10 NO
5 Site-3 Site-7 2 10 NO
6 Site-3 Site-4 2 10 NO
7 Site-9 Site-4 2 10 NO
8 Site-7 Site-2 2 NO
9 Site-6 Site-1 2 NO
10 Site-1 Site-10 8 NO
11 Site-1 Site-9 2 NO
12 Site-1 Site-8 2 NO

• Champions to submit the below details over a Word Doc or PPT file

1. Device Selection: Select a Ciena device that best meets the customer's
requirements.
2. Link Budgets: Calculate link budgets/ Network planning based on a given fiber
parameter
3. Bill of Material: Detailed BOM is required per site with power consumption
4. Utilization: Spectrum utilization is required to check the C-band fulfilment.
 Navigator NCS Lab Use Cases

Lab Use Case 1 - Navigator NCS with Optical Networking

Provisioning and Monitoring a High-Capacity Data Center Interconnect (CDC) with

Waveserver Integration
▪ Objective: To demonstrate proficiency in configuring, provisioning, and monitoring a
high-capacity data centre interconnect (CDC) using the Ciena 6500 platform
integrated with Waveserver Ai.
▪ Scenario: Customer XYZ is expanding its data centre infrastructure and needs to
establish a high-capacity connection between two data centres in different
geographical regions. The CDC will facilitate the transfer of large volumes of data
with low latency and high reliability.
Lab Suggestions
Manage Control and Plan lab with Waveserver and 6500 5-node CDC Photonic Network.
Book a lab in Ciena Emulation Cloud (CEC) with:
Config1: Navigator MC 8.0
Config2: Community Pool6500 5 Node CDC Regen Flex V15.5
Config3: Waveserver5 Pt to Pt

Tasks
Topology Verification:
▪ Utilize the Ciena Navigator to visualize the network topology, confirming the
presence of the 6500 CDC configuration with Waveserver Ai connected to its CCMD
port.
▪ Verify the connectivity between the 6500 network elements and the Waveserver Ai.

Configuration and Provisioning:

▪ Access the MCP management system to configure the 6500 network elements for
optimal performance in the CDC.
▪ Configure the Waveserver Ai to align with the CDC requirements, ensuring efficient
utilization of available bandwidth and low latency.
▪ Provision optical circuits between the 6500 network elements and the Waveserver Ai
to establish the CDC link.
▪ Perform service testing to ensure the CDC link meets the specified performance
metrics, such as bandwidth, latency, and reliability. [This task is optional based on
the available resources in the lab]

Monitoring and Maintenance:

▪ Utilize the Ciena Navigator and Site Manager to monitor the performance of the CDC
link in real time.
▪ Monitor key performance indicators (KPIs) such as optical power levels, signal
quality, and error rates to identify any potential issues.
 ▪ Perform routine maintenance tasks, such as firmware upgrades and configuration
backups, to ensure the stability and security of the CDC infrastructure. [This task is
optional based on the available resources in the lab]

Troubleshooting and Optimization: [This task is optional based on the available resources in
the lab]
In case of any performance degradation or service interruptions, use the embedded CLI
terminal in the Waveserver Ai to troubleshoot the issue.
▪ Analyze logs and diagnostic information to identify the root cause of the problem
and implement corrective actions.
▪ Optimize the configuration parameters of the 6500 network elements and
Waveserver Ai to enhance the performance and efficiency of the CDC link.

• Champions are to submit the below details over a Video file uploaded on the
Champion Community Page

1. Please prepare a video by demonstrating how you have completed all the four tasks:
• Topology Verification
• Configuration & Provisioning
• Monitoring & Maintenance
• Troubleshooting & Optimization
Lab Use Case 2 - Navigator NCS with IP networking

Customer XYZ is in location A. They have expanded their support by opening new premises
in location B. Now customers want to establish connectivity between locations A and B.
Moreover, the customer has their infrastructure (optical and packet) and existing NMS. The
customer wants to provision the L3VPN services through NMS to establish secure and
efficient VPN tunnels between corporate networks in existing and newly located premises,
leveraging encryption and authentication protocols.

Lab Topology

Here, the XYZ customer is confidently presenting their packet infrastructure to provision the
highly secure L3VPN service, known for its robust tunnelling capabilities in securely sharing
information between locations A and B.
It is suggested to consider R5-5144 as location A and R8-5166 as location B. Additionally, R1-
2-3-4 are regarded as core network elements.
This infrastructure/Lab is available in the Ciena Emulation Cloud (Ciena Emulation Cloud)
with Lab Configs “Navigator MC 8.0 & SAOS 10.x 8 Node”.
Tasks

L3VPN Service Provisioning

• Please make sure that Full mesh and bidirectional L3VPN service is provisioned.
• Verify the Transport policy, Catalog, Color and Fallback same as selected during
service provisioning.

L3VPN Service Monitoring

• Please make sure that the L3VPN service that has been deployed is not degraded.
• Ensure there is no alarm present on service.
• Customer XYZ wants to ensure that all the service members are connected in a
topological view.
• Please ensure that Locations A and B can share their information.
• Please ensure that customer XYZ does not want to lose data between Locations A
and B.

• Champions are to submit the below details over a Video file uploaded on the
Champion Community Page

1. Please prepare a video demonstrating how you have implemented the following
tasks’ alarm streaming requirements.
• L3VPN Service Provisioning
• L3VPN Service Monitoring

Lab Use Case 3 - Navigator NCS Monitoring

Customer XYZ is looking for a solution where its OSS can access the alarm streaming. The
OSS requirements are given below.
• The customer XYZ wants token authentication to connect the OSS for alarm
streaming. Please ensure proper authentication is taken care of during OSS
connection to Navigator NCS.
• The network is small therefore there are fewer alarms in the network, the customer
XYZ wants to ensure that the OSS connection should remain connected at least for
30 minutes after receiving any alarm.
• During its maintenance window, the customer wants streaming of alarm NE LOA
(Loss of Association) only.
Lab Requirement: Please book any CEC lab with Navigator NCS and NEs to showcase the
above use case.s

• Champions are to submit the below details over a Video file uploaded on the
Champion Community Page

1. Please prepare a video demonstrating how you have implemented alarm streaming
requirements.