Point-to-Point Connection Details

Because a point-to-point connection is essentially two ports connected by a single virtual connection, the details page comprises a combination of the same information you would find on a port details page and virtual circuit details page.

To view a connection’s details, double-click its row in point-to-point connections table or click its overflow menu and select View Point-to-Point:

alt_text

For information about the other pages available under Package Info, see Point-to-Point Connection Details Pages.

Details

  • Header Row
    • Col1
    • Col2
  • r
    • Description
    • The name you provided for the connection.
  • r
    • Circuit ID
    • A unique identifier for this connection that includes the metros in which the interfaces are located.
  • r
    • Package
    • The product type.
  • r
    • Time Created
      Time Updated
    • The date and time the connection was created and updated (if applicable).
  • r
    • Status
    • Status can have the following values:
      • Active

      • Deleted

      • Provisioning

        NOTE: On rare occasions, you might order a port at a location in which there is a temporary lack of pre-configured ports. When this happens, your port remains in the Provisioning state for 1-3 business days as we manually complete its configuration.

        An informational message should appear in the portal as you create the port letting you know about any lead times before you proceed.

  • r
    • Billing

    • Charges begin to accrue 24 hours after you create a port (allowing you to cancel your order without incurring costs). Billing begins 15 days after the port is created.

      This field tells you how many days you have until billing begins. After 15 days, the status is updated to Active.

      TIP: Hover over Active to see the date that billing started.

Billing

This section reflects your pricing plan, speed, rate, and term.

You can upgrade the connection to move to a dedicated plan, extend your contract term, or increase capacity.

Source

The Source column provides details about the source port.

  • Header Row
    • Col1
    • Col2
  • r
    • Interface ID
    • A unique identifier for the source port that includes the metro in which the port is located.
  • r
    • Speed/Media
    • The speed and optic you selected when creating the connection. For more information, see LINK> The speed and optic values are the same between the source and destination ports.
  • r
    • Device Name

    • The device name has the following format: <router type><number>.<POP ID>.

      The router type is one of the following:

      • CFR: Core Fabric Router
        These routers are large and can support many 40 Gbps and 100 Gbps connections. Our CFR hardware is either Juniper QFX10k series or Cisco NCS5500 series.
      • EFR: Edge Fabric Router
        These routers are usually smaller. If the POP already has a CFR setup, the EFR typically handles the 1 Gbps connections. At smaller sites, EFR can support a limited number of 100 Gbps connections.

      For more information about device hardware, such as make and model, use the Device-Info API call.

  • r
    • Interface

    • The interface name has the following format: type-fpc/pic/port.

      Type

      • xe: 10 gigabit Ethernet interface
      • et: 100 and 40 Gigabit Ethernet interface
      • ge: Gigabit Ethernet interface
      • ae: Aggregated Ethernet interface

      FPC: The slot number in which the FPC (flexible PIC concentrator) or DPC (dense port concentrator) line card is installed.

      PIC: The PIC (physical interface card) location number on the FPC.

      Port: The port number on the PIC or DPC.

      For more information, see Juniper - Interface Naming Overview.

  • r
    • Demarc LOA Information

    • The demarc LOA information specifies connection placement, including:

      • Panel
      • Module
      • Position

      How this information is formatted varies depending on the site and hardware used.

  • r
    • Availability Zone
    • The availability zone signifies device diversity. Provisioning connections across availability zones builds redundancy in your network.
  • r
    • Admin
    • The Admin state refers to whether the router is enabled (Up) or disabled (Down).
  • r
    • Operational
    • The Operational state is read from your router and refers to the state of your cross connect link.
  • r
    • Autonegotiation
      (1G connections only)

    • Autonegotiation is enabled by default. You can toggle it off for troubleshooting purposes or if you are connecting to a device operating in full-duplex mode.

      You can also toggle this on or off when editing the connection.

      NOTE: While autonegotiation is togglable on 1Gbps interfaces, it is also enabled on all 10Gbps and larger interfaces.
  • r
    • Last Flap
    • This indicates the last recorded route flap. Route flapping can be caused by a variety of hardware, software, and connection errors.
  • r
    • Market
      POP
      Site
      Address
    • Location information for the source or destination port.
  • r
    • Trend
    • Graphical representation of network traffic over the last 24 hours.

Destination

The Destination column repeats the information above for the destination port.

Optical light levels

Fiber optic connections work by translating binary data into light. The light is then transmitted through fiber cabling using different pulses, wavelengths, and intensity to convey that data.

The optical light level is the strength of that light when it is transmitted on one end and received on the other.

Optical light levels are measured in terms of transmitted power (TX) and received power (RX). Light lanes are the electrical lanes in the optic interface. The example below is a 40G optic, which has four lanes:

alt_text

When working correctly, the optical signal strength should fall within a certain power range. A green dot next to the RX/TX value indicates a healthy connection; a red dot indicates that either the optic levels are outside the acceptable range or that the cross connect has not been installed yet:

alt_text

  • Optical power that is too high can saturate the receiver and prevent a clean decode, resulting in errors. This is typically caused by the wrong type of optic, a too-short fiber span, or an active device in the path (such as an amplifier or DWDM transponder).

  • Optical power that is too low can result in slow connections, connections that won’t pass data, and connections that might not link at all. This is typically caused by unseated or dirty patches, a bad cross connection, or a longer fiber span than expected.

    If your optical light levels are consistently too low, you can have the patches cleaned, scoped, and replaced as needed.

NOTE: The acceptable range is different depending on the optics. For more information, see Optic Specifications.