Point-to-Point Connection Details Pages
To view the connection details, go to the Network > Point-to-Point page in the portal. Click one of the table rows to view an overview of that connection. For complete information, click More Details.
For information about the Details page, see Point-to-Point Connection Details.
The statistics page presents a graphical view of the network traffic for the EPL connecting the to ports.
By default, you are shown metrics over the past hour. You can use the drop-down menus to select a different time frame, or select Enter Date Range to specify a date and time range.
You can view traffic in bits per second or packets per second.
Interface A and Z Statistics
The statistics pages present graphical information on traffic, errors, and optics for the ports at both sides of the point-to-point connection.
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.
Interface A and Z Router Logs
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 connection.
Events that are logged include the following:
- When the interfaces were created
- LOA generation
- Any changes to the connection name
Click Toggle Details to view more information about the event.