How do I troubleshoot layer 1 issues in Direct Connect?

Resolution

Note: For layer 2 issues, see How do I troubleshoot layer 2 issues in Direct Connect? For layer 3 issues, see How do I troubleshoot layer 3 issues in Direct Connect?

Troubleshoot an existing connection

If your existing Direct Connect connection is DOWN and your backup connection is UP, then take the following actions:

• Check your AWS Health Dashboard for notifications of planned maintenance or unplanned outages.
• Contact your AWS Direct Connect Partner to check whether they have planned or unplanned network outages.
• Use Amazon CloudWatch to check the ConnectionLightLevelTx and ConnectionLightLevelRx metrics.
  Note: The levels must be within the range of -14.4–2.50 decibel-milliwatts (dBm) for 1 gigabit per second (Gbps) and 10 Gbps Direct Connect connections. For 100 Gbps connections, keep the ConnectionLightLevelTx value between -4.3–4.5 dBm. For ConnectionLightLevelRx, keep the value between -10.6–4.5 dBm. There are four optical lanes for 100 and 400 Gbps connections. You must check the light signal for each optical lane.

Troubleshoot a new connection

If you can't establish a new connection, then take the following actions:

• Complete a cross-connect network connection from your colocation or network provider. Then, compare the ports with the ones that are listed in your Letter of Authorization - Connecting Facility Assignment (LOA-CFA).
• Check that your router or your provider's router is on and the ports are activated.
• Make sure that your routers use the correct optical transceiver fiber type:
  1 gigabit (Gb) Ethernet: Single-mode fiber with a 1000BASE-LX (1310 nm) transceiver
  10 Gb Ethernet: Single-mode fiber with a 10GBASE-LR (1310 nm) transceiver
  100 Gb Ethernet: Single-mode fiber with a 100GBASE-LR4 transceiver
  400 Gb Ethernet: Single-mode fiber with a 400GBASE-LR4 transceiver
• Turn off auto-negotiation for ports with speeds that are faster than 1 Gbps.
  Note: Depending on the Direct Connect endpoint that serves your connection, you can turn on or off auto-negotiation for 1 Gbps connections. If you must turn it off for your connections, then you must manually configure port speeds and full-duplex mode.
• Verify that your router receives an acceptable optical signal over the cross connect.
• If needed, then swap the Tx/Rx fiber strands.
• Use CloudWatch to check the ConnectionLightLevelTx and ConnectionLightLevelRx metrics.
  Note: The levels must be within the range of -14.4–2.50 dBm for 1 Gbps and 10 Gbps Direct Connect connections. For 100 Gbps connections, keep the ConnectionLightLevelTx value between -4.3–4.5 dBm. For ConnectionLightLevelRx, keep the value between -10.6–4.5 dBm. There are four optical lanes for 100 and 400 Gbps connections. You must check the light signal for each optical lane.
• Request a written report for the Tx/Rx optical signal across the cross connect from your service provider or colocation provider.
• Request that your service provider or colocation partner perform the following loop tests at the Meet-Me-Room (MMR):
  Send data toward the customer router. If the port on the on-premises device shows the UP status, then the link up to MMR works. You can also check the Tx/Rx light levels on your device. To check whether the light levels are in range, use the show interfaces eth1 transceiver command or your device-specific command.
  Send data toward the AWS router and keep it on for at least 10 minutes. If the layer 1 cable and transceiver is good, then the port status is UP on the AWS side. To confirm the UP status, view the ConnectionState CloudWatch metric.

Related information

Troubleshoot layer 1 (physical) issues