User's Manual
ALFOplus 24GHz (North America) - Release 01.05.0x - MN.00395.E - 004 53
In other words, the “RMON Statistics” are the data that are collected and stored in the Network Equipment,
while the “RMON History” is an aggregation of the data collected from each network equipment and the
database is located in the NMS.
7.8 RMON COUNTERS
RMON statistics are composed by counters for each port of the device that are stored in the equipment
deployed on field.
Into the equipment it can be chosen to store the values with a sampling period that can be defined between
two values: 1 min, 15 min, or both. For each sampling period the counters values are stored into the equip-
ment. After a predefined period (polling period), all the RMON data stored by the equipment are get by the
NMS. The polling period can be either less than 4 hours (if the sampling period is 1 min) or 1 day (in case
the sampling period is 15 min). The NMS aggregates the files received to create a bigger database with
the History of the Performance Monitoring samples.
Here below are described the RMON counters available for each device interface (both LAN and radio
ports):
• DropEvents: Total number of events (frames, or whole queue contents) in which packets were
dropped by the interface due to lack of resources.
• Octets RX: Total number of octets of data (including those in bad packets) received by the interface.
• Pkts RX: Total number of packets (including bad packets, broadcast packets, and multicast packets)
received.
• BroadcastPkts RX: Total number of good packets received that were directed to the broadcast ad-
dress.
• Multicast Pkts RX: Total number of good packets received that were directed to a multicast address.
• CRC Align Errors: Total number of packets received that had a length between 64 and the Max Pack-
et Size configured on the equipment switch (in any case not exceeding 10240 bytes) with bad Frame
Check Sequence (FCS) and an integral number of octets (FCS Error) or a bad FCS with a non-inte-
gral number of octets (Alignment Error).
• Undersize Pkts: Total number of packets received that were less than 64 octets long and were oth-
erwise well formed.
• Oversize Pkts: The number of packets received during this sampling interval that were longer than
maximum allowable length (excluding framing bits but including FCS octets) but were otherwise
well formed.
• Fragments: Total number of packets received that were less than 64 octets in length and had either
a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with
a nonintegral number of octets (Alignment Error).
• Jabbers: Total number of packets received that were longer than n (parameter Max Packet Size, it
can be set to 1522, 2048 bytes or 10240 Kbytes) octets, and had either a bad Frame Check Se-
quence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number
of octets (Alignment Error).
• Collisions: The best estimate of the total number of collisions on this EthLannet segment.
• Utilization Rx: The best estimate of the mean physical layer network utilization on this interface dur-
ing this sampling interval, in hundredths of a percent. The percentage is always referred to a 1Gbit/
s port speed. So, it represents the mean RX throughput measured on the port during the sampling
period and it is expressed as a percentage of a port speed.
• Octets TX: Total number of octets of data (including those in bad packets) transmitted.
• Pkts TX: Total number of packets transmitted.
• BroadcastPkts TX: Total number of good packets transmitted that were directed to the broadcast
address.
• Multicast Pkts TX: Total number of good packets transmitted that were directed to a multicast ad-
dress.