Delta RMC101 - Manual (Page 308)

RMC100 and RMCWin User Manual
5-58
• Total Broadcast Pkts Sent
This is the count of packets the RMC sent to the broadcast MAC address. This is typically done
only when the RMC is requesting a BOOTP or DHCP server to respond with its IP address.
• CPU Load % (Last) (requires 20010831 or newer RMC ENET firmware)
This value gives the percent of CPU time that is currently being used. The closer this number
approaches 100, the slower it will respond to incoming requests.
• CPU Load % (Max) (requires 20010831 or newer RMC ENET firmware)
This value holds the maximum CPU load percentage that has been reached since the RMC
ENET was started.
Rx Errors (Receive Errors)
Occasional occurrences of the following errors are expected. However, it is important to ensure
that you do not get a lot of these errors. Also, if you are experiencing network instability, check
these counters for clues to what might be going wrong.
• Missed Packets (Ethernet Controller)
This is the count of packets missed because the Ethernet controller chip's internal buffer filled up
temporarily.
• Missed Packets (RMC ENET)
This is the count of packets missed because the RMC ENET's internal buffer filled up temporarily.
This is differentiated from Missed Packets (Ethernet Controller) for internal troubleshooting
purposes.
• Runts Received
This is a count of all packets received under the 64-byte minimum specified by the Ethernet IEEE
802.3 specification. This indicates a problem in other devices on the network and could result in
network performance problems.
• Extra Data Received
This is a count of all packets received over the 1518-byte maximum specified by the Ethernet
IEEE 802.3 specification. This indicates a problem in other devices on the network and could
result in network performance problems.
• Bad CRC Received
This is a count of all packets received with a problem with their Frame Check Sequence (FCS),
which is a 32-bit Cyclic Redundancy Check (CRC). This could indicate electrical noise or an error
in another device on the network.
Tx Errors (Transmit Errors)
• Single Tx Collisions (20010608 RMC ENET firmware or older)
This counts the number of times the RMC ENET sent a packet, had a collision, but succeeded on
the first retry. This retry happens within 500ms from the collision. High numbers of single
collisions will degrade network performance. The simplest solutions are (1) reducing the number
of devices on the network, and (2) using an Ethernet switch instead of an Ethernet hub to reduce
the size of the collision domain.
In 20010724 RMC ENET firmware, this field was replaced by a collision histogram. See below.
• Multiple Tx Collisions (20010608 RMC ENET firmware or older)
This counts the number of times the RMC ENET sent a packet and had more than one collision.
Therefore, it took more than one retry to send the packet. The RMC's Ethernet controller will give
up trying to send the packet after 16 attempts.
In 20010724 RMC ENET firmware, this field was replaced by a collision histogram. See below.