IPR-10GETHERNET Altera, IPR-10GETHERNET Datasheet - Page 68

• Manufacturer Part Number: IPR-10GETHERNET
• Description: IP CORE Renewal Of IP-10GETHERNET
• Manufacturer: Altera

Specifications of IPR-10GETHERNET

• Software Application: IP CORE, Interface And Protocols, ETHERNET
• Supported Families: Quartus II
• Features: IEEE 802.3 2005 And 802.1Q Ethernet Standards, Management Data I/O (MDIO) Master Interface
• Core Architecture: FPGA
• Core Sub-architecture: Arria, HardCopy, Stratix
• Rohs Compliant: NA
• Lead Free Status / RoHS Status: na

3–42
Table 3–20. IEFT RMON MIB Object Support (Part 1 of 2)
10-Gbps Ethernet IP Functional Description
etherStatsDropEvents
etherStatsOctets
etherStatsPkts
etherStatsUndersizePkts
etherStatsOversizePkts
etherStatsPkts64Octets
etherStatsPkts65to127Octets
etherStatsPkts128to255Octets
etherStatsPkts256to511Octets
MIB Object Name
Table 3–19. IETF MIB (MIB-II) Objects Support (Part 2 of 2)
3.6.5.1.IETF Remote Network Monitoring Support
The IETF RFC 2819 defines objects for managing remote network monitoring devices.
These objects are usually implemented in a dedicated device (monitor/probe) for
traffic monitoring and analysis within a network segment. Such a probe usually
samples the values in a periodic manner to give relative usage estimations rather than
absolute values.
MIB counts good and bad packets, using the following definitions:
■
■
ifInErrors
ifOutErrors
Goodpackets(validframes)—Goodpacketsareerror-freepacketsthathaveavalid
frame length. A valid frame length is defined as between 64 bytes long and the
value set in the frm_length register. The length does not include framing bits
(preamble, SFD) but includes the FCS field.
Bad packets (invalid frames)—Bad packets are packets that have proper framing
and are therefore recognized as packets, but contain errors within the packet or
have an invalid length. On the Ethernet, bad packets have a valid preamble and
SFD, but have a bad CRC, or are either shorter than 64 bytes or longer than and the
value set in the frm_length register, or contain a control character such as |E| in
the frame.
MIB Object Name
Table 3–20
Counts the number of dropped frames due to internal errors of the client.
Occurs when FIFO overflow condition persists.
Total number of bytes received. Good and bad frames.
Total number of frames received. Counts good and bad frames.
Number of frames received with less than 64 bytes, (good and bad frames
are counted).
Incremented with each well-formed frame that exceeds the valid maximum
programmed frame length, (good and bad frames are counted).
Incremented when a frame of 64 bytes length is received (good and bad
frames are counted).
Frames (good and bad) with 65–127 bytes.
Frames (good and bad) with 128–255 bytes.
Frames (good and bad) with 256–511 bytes.
Number of frames received with one of the following errors:
■
■
■
■
Number of frames transmitted with one of the following errors:
■
■
■
lists the defined objects. The remote monitoring (RMON)
FIFO overflow error
CRC error
Length error
Terminated frame with an error or error during a frame
FIFO overflow error
FIFO underflow error
User application defined error
Support
Description
© July 2010 Altera Corporation
Register Descriptions