Configuration guidelines for On‑Demand services

Once your NaaS Port is ready, prepare for On‑Demand services by configuring your equipment. 

Please read this guide carefully.

Before adding On‑Demand services, complete the following steps:

1. Work with property management or a vendor to extend the connection from the NaaS Port to your equipment. If you ordered a third‑party cross‑connect, verify installation has been completed.
   
   
2. Connect your equipment to the extended connection or third‑party cross‑connect.
   
   
3. Configure your hardware with the port settings in the NaaS Port ready notification email and ensure light levels are adequate (if applicable). Our policy is to hardcode speed and duplex at 10/100 base T, including ports with a 10/100 combination.
   
   
4. Verify the NaaS Port is active.

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.

1. Verify power is correctly connected to your equipment by cycling it or turning it off and back on if this will not disrupt any other services.
   
   
2. Confirm the physical port/SFP type (optical, electrical, OCn, ethernet) and cabling/fiber type (coax, single‑mode, multi‑mode) associated with the service type and adjacent equipment physical output are compatible.
   
   
3. If applicable, verify optical bandwidth (10 Mbps, 100 Mbps, 1000 Mbps) matches the adjacent Lumen equipment. Our policy is to hardcode speed and duplex at 10/100 base T, including ports with a 10/100 combination.
   
   
4. Unplug the cable and plug it back in to confirm it is installed correctly. If that does not provide resolution, the cable may need a straight‑through or crossover, or the fiber connection may need to be rolled.
   
   
5. Verify that the distance of the cabling run is within specifications for CAT‑5/CAT‑6/CAT‑7/other fiber types related to the equipment transmit/receive parameters.
   
   
6. If applicable, verify light levels being received and transmitted are within equipment specifications.
   
   
7. Confirm the equipment interface's current state is ‘up’ or ‘in service.’ 
   
   
8. Confirm that the interface settings match the Lumen configuration speed, duplex, and other port attributes, as applicable. If the port is an Ethernet port, ensure that auto‑negotiation is set to ‘no’ or ‘off.’
   
   
9. If applicable, and if you ordered service with another carrier between your equipment and our service, validate the local exchange carrier (LEC) loop/circuit is working as you requested. Confirm power to the LEC device and port connectivity. If there appears to be an issue with your LEC loop, engage and troubleshoot with the LEC before contacting chat support.

Layer 2

• Verify VLAN ID. VLAN stacking (provider bridging) may have been configured depending on the service. Please verify that your VLAN ID matches the IP configuration email and the expected requirements. All On‑Demand services require VLAN tagging using the VLAN provided in your service activation email. 
  
  
• For layer 2 point‑to‑point private services (Ethernet On‑Demand, EVPL, E‑Access, ELINE), we forward based on the layer 2 MAC address. Bidirectional MAC address learning is required for the service to function between A and Z endpoints.
  
  
• MTU requirements to pass standard IP traffic to the UNI is 1500. At layer 2 service must support 1522 for single tag. Any unfragmented IP traffic that requires IP payload higher than 1500 isn't currently supported.
  
  
• Verify that CoS profile matches the service activation notice and the expected requirements for Ethernet On‑Demand and IP VPN On‑Demand; depending on the service type, the marking may be 802.1p, IPP, or DSCP.
  
  
• For cloud service providers with Ethernet On‑Demand and IP VPN On‑Demand, verify the service key, account information, and IP configuration provided in your service activation email. Contact your cloud service provider if you have determined your problem is not a Lumen service issue.

Layer 3

• Verify that IPv4 addressing (and IPv6 if applicable) matches the service activation email and the expected requirements. Internet On‑Demand activations may include additional LAN block(s).
  
  
• MTU requirements to pass standard IP traffic to the UNI is 1500. Any unfragmented IP traffic that requires IP payload higher than 1500 isn't currently supported.
  
  
• Verify that static routes or dynamic routing protocol specifications match the service activation email and the expected requirements. Please note that protocols such as BGP may include additional details such as remote and local ASN, MD5, BFD, etc.
  
  
• For Internet On‑Demand activations, a routing registry object will translate to a list of allowed prefixes, as well as a combination of prefixes advertised by Lumen (full internet, internet + default, default only, Lumen customers only). On IP VPN On‑Demand, we announce the full VRF routing table and the default maximum is 10,000 unless specified otherwise by special requirements.
  
  
• Verify that CoS profile matches the service activation email and the expected requirements for Ethernet On‑Demand and IP VPN On‑Demand. Depending on the service type the marking may be either IPP, DSCP, or EXP (certain NNI offerings).
  
  
• For cloud service providers with Ethernet On‑Demand and IP VPN On‑Demand, verify the service key, account information, and IP configuration provided in your service activation email. Contact your cloud service provider if you have determined your problem is not a Lumen service issue.

The following variables impact actual throughput in a network during data transfer and testing:
 

1. To ensure maximum throughput efficiency, enable traffic shaping on your equipment (CPE) switch or router.
   
   
2. Traffic shaping is required to ensure that packets are not dropped when entering the network as traffic policing is applied on the Lumen network.
   
   
3. If shaping is not enabled, Lumen (or one of our third-party access vendors) will randomly drop traffic if your signal exceeds the committed information rate (CIR) that is contracted for the connection.
   
   
4. Most enterprise-class routers on the market should support traffic shaping.
   
   
5. Lumen Ethernet services can scale from 3 Mbps to 1 Gbps as long as you can shape your traffic; if you are not able to shape your traffic, you should purchase service in the 10/100/1000 Mbps speed tiers to achieve maximum use of the bandwidth. Failure to comply with this recommendation will result in reduced throughput and performance.
   
   
6. Example traffic-shaping configuration parameters:
   
   
   • Purchased service = 50 Mbps CDR
   • Customer router = Cisco 2900
   • Configure port level traffic shaper to 50 Mbps
      
7. 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