Once your Lumen® NaaS Port is ready, you will need to prepare for On‑Demand services and configure your equipment using these guidelines.
Please read this guide carefully.
Before adding On‑Demand services, complete the following steps:
The following configurations affect traffic. We recommend double‑checking the following items to ensure you don't encounter issues with On‑Demand services. Refer to your service activation notice email for technical parameters and information about your service.
The following variables impact actual throughput in a network during data transfer and testing:
Resulting example configuration:
! Match any traffic with class‑map:
class‑map match‑all class‑cpe‑wan‑out
match any
! Parent policy‑map matches class‑map traffic and applies shaper
policy‑map policy‑cpe‑wan‑out
class class‑cpe‑wan‑out
shape average 50000000
!
! Apply policy‑map outbound on Lumen‑facing interface:
interface GigabitEthernet0/2
service‑policy output policy‑cpe‑wan‑out
Verify your router is rated at the maximum speed of your purchased service. Non‑commercial routers (e.g., Linksys, Netgear) support only a few hundred Mbps maximum speed despite the interfaces supporting the GigE (1000Mbps) specification.
Ensure you have configured the following interface options (if available) on your router for the Ethernet port connected to Lumen:
For IP/data services only:
The following reference table provides basic Ethernet interface connectivity standards, cabling and compatibility. Customer edge (CE) device configuration guidance is provided for those Ethernet service speeds most commonly associated with performance issues.
Interface | Media type handoff | Fiber mode | Bandwidth usage limit | Distance limit |
---|---|---|---|---|
1000 Base SX | Fiber | Multi‑mode | 1 Gbps | 220m–550m |
1000 Base LX/LH | Fiber | Single‑mode | 1 Gbps | 10km |
1000 Base ZX | Fiber | Single‑mode | 1 Gbps | 70km |
10000 Base SR | Fiber | Multi‑mode | 10 Gbps | 220m–550m |
10000 Base IR/LR | Fiber | Single‑mode | 10 Gbps | 10km/20km |
40G Base LR | Fiber | Single‑mode | 40 Gbps | 20km |
When connecting like devices (e.g., switch to switch), you may need to use an Ethernet crossover cable.
Learn more about Ethernet crossover cables
All On‑Demand services require VLAN tagging to separate services between the Lumen port and your CPE. Some services require double tagging to nest VLANs within other VLANs. The following examples will help you get started creating a VLAN with On‑Demand services.
Customer router example configuration for Cisco:
interface GigabitEthernet0/0/1
description Lumen UNI Dallas
!
interface GigabitEthernet0/0/1.101
description EoD EVC to Saint Louis (Spoke 1)
encapsulation dot1Q 101
ip address [WAN IP address determined by customer]
!
interface GigabitEthernet0/0/1.102
description EoD EVC to Seattle (Spoke 2)
encapsulation dot1q 102
ip address [WAN IP address determined by customer]
!
interface GigabitEthernet0/0/1.401
description EVC to Internet on Demand (IoD)
encapsulation dot1q 401
ip address [WAN IP address assigned by Lumen]
Spoke 1 example configuration for Cisco:
interface GigabitEthernet0/0/1
description Lumen UNI Saint Louis
!
interface GigabitEthernet0/0/1.101
description EVC to Dallas
encapsulation dot1Q 101
ip address [WAN IP address determined by customer]
Spoke 2 example configuration for Cisco:
interface GigabitEthernet0/0/1
description Lumen UNI Seattle
!
interface GigabitEthernet0/0/1.102
description EVC to Dallas
encapsulation dot1Q 102
ip address [WAN IP address determined by customer
Customer switch example configuration for Cisco:
interface e0
switchport trunk allowed vlan 100,200
switchport trunk encapsulation dot1q
switchport mode trunk
interface e1
switchport access vlan 100
switchport mode access
interface e2
switchport access vlan 200
switchport mode access
interface e3
switchport access vlan 200
switchport mode access
Router 1 example configuration for Cisco:
interface GigabitEthernet0/0/1
description Lumen UNI Saint Louis
!
interface GigabitEthernet0/0/1.101
description Router to Switchport e1
ip address [WAN IP address assigned by Lumen]
Customer switch example configuration for Cisco:
interface GigabitEthernet0/1
description Lumen UNI Dallas – Primary
mtu 1504
!
Interface GigabitEthernet0/1.10125
encapsulation dot1Q 101 second‑dot1q 25
description “Cloud Connection Primary Peer”
Ip address 10.103.224.217 255.255.255.252
interface GigabitEthernet0/2
description Lumen UNI Dallas ‑ Secondary
!
Interface GigabitEthernet0/2.20125
encapsulation dot1Q 201 second‑dot1q 25
description “Cloud Connection Secondary Peer”
Ip address 10.103.224.221 255.255.255.252
Customer switch example configuration for Cisco:
interface e0
switchport trunk allowed vlan 101,201
switchport trunk encapsulation dot1q
switchport mode trunk
mtu 1504
interface e2
switchport access vlan 101
switchport mode dot1q‑tunnel
interface e3
switchport access vlan 201
switchport mode dot1q‑tunnel
Device 1 example configuration for Cisco:
interface GigabitEthernet0/1
description Lumen UNI Dallas – Primary
Interface GigabitEthernet0/1.25
encapsulation dot1Q 25
description “Cloud Connection Primary Peer”
ip address [WAN IP address determined by customer/CSP
Device 2 example configuration for Cisco:
interface GigabitEthernet0/2
description Lumen UNI Dallas – Secondary
Interface GigabitEthernet0/2.25
encapsulation dot1Q 25
description “Cloud Connection Secondary Peer”
ip address [WAN IP address determined by customer/CSP]
Alternate Option to run the switch as trunks and perform Q‑in‑Q on a layer 3 device connected to the switch:
interface e0
switchport trunk allowed vlan 101,201
switchport trunk encapsulation dot1q
switchport mode trunk
mtu 1504
interface e1
switchport trunk allowed vlan 101,201
switchport trunk encapsulation dot1q
switchport mode trunk
mtu 1504
Router 1 example configuration for Cisco:
interface GigabitEthernet0/1
description Router to Switchport e1
mtu 1504
Interface GigabitEthernet0/1.10125
encapsulation dot1Q 101 second‑dot1q 25
description “Cloud Connection Primary Peer”
Ip address 10.103.224.217 255.255.255.252
Interface GigabitEthernet0/1.20125
encapsulation dot1Q 201 second‑dot1q 25
description “Cloud Connection Secondary Peer”
Ip address 10.103.224.221 255.255.255.252
For additional support configuring or troubleshooting your network services, review our expanded index of technical topics: