To view port details, go to the Network > Interfaces page in the portal. Click one of the table rows to view an overview of that port. For complete information, click More Details.
The PacketFabric status can have the following values:
ProvisioningOn 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.
The administrative status refers to whether the router is enabled (Up) or disabled (Down).
- Operational Status
- The operational status is read from your router and refers to the state of your cross connect.
- Time Created
- Date and time the port was provisioned.
- Time Updated
- Date and time the port information was last modified.
- Last Flap
- This indicates the last recorded route flap. Route flapping can be caused by a variety of hardware, software, and connection errors.
(1Gbps ports only)
When you create the port, you have the option to toggle autonegotiation on or off. You can also toggle it on or off when editing the port.
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.**NOTE:** While autonegotiation is togglable on 1Gbps interfaces, it is also enabled on all 10Gbps and larger interfaces.
- Link Mode
(1Gbps ports only)
- By default, link mode is set to auto. However, in some cases you can request that this be set to full duplex.
The data center in which this port is located.
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.
- The contract length for the port.
Device and media
This is the device name. It has the following format:
<router type><number>.<POP ID>.
The router type is one of the following:
- Core Fabric Router.
- These routers are large and can support many 40 Gbps and 100 Gbps connections. Our CFR hardware is either the Juniper QFX10k series or Cisco NCS5500 series.
- 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.
This is the interface name followed by the optic. For more information about our optics, see Optic Specifications.
Each interface name follows a different format depending on the manufacturer.
The interface name has the following format:
The type can be one of the following:
gi: Gigabit Ethernet interface
te: 10 Gigabit Ethernet interface
tw: 25 Gigabit Ethernet interface
fo: 40 Gigabit Ethernet interface
hu: 100 Gigabit Ethernet interface
For more information, see Cisco - Interface Naming Overview.
The interface name has the following format:
The type can be one of the following
ae: Aggregated Ethernet interface
ge: Gigabit Ethernet interface
xe: 10 gigabit Ethernet interface
et: 100 and 40 Gigabit Ethernet interface
For more information, see Juniper - Interface Naming Overview.
This is the circuit ID.
- PF-AP identifies it as a port
- Followed by the POP name
- Followed by a unique numerical ID
For a list of all PacketFabric ID abbreviations, see our FAQ.
This is the availability zone.
The availability zone signifies device diversity. Provisioning connections across availability zones builds redundancy in your network.
You can disable and re-enable the port as necessary. For more information, see Disable a Port.
Where the connection is located on the PacketFabric equipment. This information is formatted differently depending on the site and hardware used.
The device description. You can change this by editing the port.
These are the optical light levels.
Optical light levels are measured in terms of transmitted power (TX) and received power (RX).
When working correctly, the optical signal strength should fall within a certain power range.
A green arrow next to the RX/TX value indicates a healthy connection.
An orange arrow indicates that the optic levels are in the “warning” range.
A red arrow indicates that the optic levels are in the “alarm” range.
Gray arrows indicate that the cross connect has not been installed yet.
The acceptable range is different depending on the optics. For more information, see Optic Specifications.
There is approximately a 30-60 second lag between optical light events and when they appear in the portal or through the API.
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.
If you order an outbound cross connect through PacketFabric, you can track its installation progress.
Click Delete to remove the cross connect. For example, if you are moving how or where you are connecting to us, upgrading equipment, or if the connection is faulty.
For more information, see Cross Connects.
The Active VCs table lists all the virtual circuits attached to the port. You cannot delete a port if it has virtual circuits associated with it.
Click View Virtual Circuit to go to the details page for that VC.
Disabled cross connects
This table lists any previously disconnected cross connects.
This only applies to outbound cross connects ordered through PacketFabric.
The statistics page presents graphical information on traffic, errors, and optics.
By default, you are shown metrics over the past 12 hours. You can use the drop-down menus to select a different time frame, or select Custom to specify a date and time range.
You can view the following traffic metrics. Hover to see TX and RX details.
- Header Row
- Row 1
- Bits per second
- How many bits of data were transmitted per second.
- Row 2
- Packets per second
- Total number of packets per second.
- Row 3
- Unicast Packets
- Unicast packets are sent from a single source to a single receiver. Most LAN and internet traffic is unicast packets. This includes TCP traffic.
- Row 4
- Broadcast Packets
- Broadcast packets are sent from a single source to all receivers on the connection. This includes ARP traffic.
- Row 5
- Multicast Packets
- Multicast packets are sent from one or more sources to one or more receivers. This includes UDP traffic.
Framing errors occur when a data frame is read at the wrong starting point or is not in the format expected.
Common causes include hardware issues (optic cables, serial ports, NIC), duplex mismatches, and mismatched settings between the serial port and device.
- Resource Errors
- The number of transmit drops. This typically indicates a buffer error or that packets are too large to add to the buffer.
- MTU Errors
- The number of packets whose size exceeded the interface MTU. This is an output error.
- CRC Errors
- CRC errors indicate data corruption. These can be caused by a faulty cable, PIC, or FPC.
- The number of packets ASIC’s RED mechanism drops from the input queue. This can indicate traffic congestion or inadequate buffer size.
- The number of discarded packets over the burst allowance (your committed rate). Our default burst size is 6250000 bytes.
- The number of frames that have been received and are smaller than the minimum frame size (64 bytes). These are typically caused by collisions
- The number of packets that spent so much time in memory that they have been automatically purged. This can indicate software and hardware malfunctions.
- Module Temperature
- We use commercial transceivers, which have a temperature range of approximately 0-70° C.
- Transmit and Receive Power
- Transceiver power over time.
The information that is logged varies depending on the device. Common log messages are SNMP_TRAP_LINK_UP and SNMP_TRAP_LINK_DOWN, which are logged when an interface changes state.
Any optical light level warnings or alarms are also logged here.
The History page shows event logs specific to the interface.
Events that are logged include the following:
- When the interface was created
- The creation and deletion of virtual circuits
- LOA generation
- Disable and enable actions
- Any changes to the port name
Click Toggle Details to view more information about the event.
From here you can find and download the LOA and any service orders on the Documents page.