Thank you, I’ll get in contact with tail-f representative.
Just to conclude:
The first RMON MIB for Ethernet was issued as RFC 1271 in 1991. Later, this specification was superseded by RFC 1757 for SMIv1 and by RFC 2819 for SMIv2.
RFC 2819 extends RFC 1757 specification by documenting the RMON MIB in SMIv2 format while remaining semantically identical to the existing SMIv1-based MIB.
RMON version 2 (RMON 2) is an extension to RMON version 1 (RMON 1), which refers to the initial RMON specifications monitoring on OSI Layer 2. RMON 2 focuses on the layers of traffic above the Media Access Control (MAC) layer; the main enhancement of RMON 2 is the capability to measure Layer 3 network traffic and application statistics.
I’m interest in RMON 1 since it includes only data link layer (Layer 2) details.
I’m not interest in RMON 2, since it offers network layer to application layer details (Layer 3 and up).
In the initial RMON MIB, the EntryStatus textual convention was introduced to provide table entry creation, validation, and deletion. This function then was added to the SNMP framework as the RowStatus textual convention (RFC 2579, Textual Conventions for SMIv2). The RowStatus textual convention is used to define all new tables. The old RMON 1 MIB (RFC 2819) uses EntryStatus, and the new RMON 2 MIB (RFC 4502) uses RowStatus.
Concluding, RFC 2819 for SMIv2 uses EntryStatus.
RFC 4502 for SMIv2 uses rowStatus for the new defined tables in RMON2-MIB, but entryStatus for the tables imported from RMON-MIB.
Thanks