Measure Reference Manual

L2IN-BYTES-F
(G-series, Legacy Style only) Same as L2IN-BYTES but accommodates larger values (64 bits rather
than 32).
Counter type: Accumulating.
L2OUT-BYTES-F
(G-series, Legacy Style only) Same as L2OUT-BYTES but accommodates larger values (64 bits
rather than 32).
Counter type: Accumulating.
Usage Notes for All NETLINE Entities
• In general, the data collected by the Measure L2 counters is very close to the actual line byte
counts. However, line problems or CLIP traces can alter the Measure byte counts.
For CSS-type controllers, the information gathered by Measure is from the controllers to the
line handler. Measure counters are not advanced when retransmission of data occurs because
of line problems. SCF line statistics count events that cause retransmissions (timeouts and FCS
errors). To get detailed information about line problems, use a datascope.
When you take CLIP traces, the trace data is included in the L2IN-BYTES counter. Similarly,
the CIN4-BYTES and COUT4-BYTES counters occasionally include NCP NETMAP packets.
• For descriptions of networks and network protocols, see the Expand Configuration and
Management Manual, the Expand Network Management and Troubleshooting Manual, and
the X25AM Configuration and Management Manual.
Usage Notes for H-Series and J-Series NETLINE Entities
In H-series and J-series RVUs, all byte-count fields accommodate 64 bits. Field names ending in -F
are no longer used in ZMS style records but remain available to applications that request data in
legacy style.
Usage Notes for G-Series NETLINE Entities
• SUBSYSTEM-VERSION for ZMSNLINE records is provided by Expand.
• The 64-bit byte-count fields (fields ending in -F) collect the same data as older 32-bit byte-count
fields. For example, the 64-bit field L2IN-BYTES-F collects the same data as the 32-bit field
L2IN-BYTES. The 64-bit fields are less subject to overflow caused by high levels of I/O activity.
The 32-bit fields are currently active and continue to return values. If no field overflow exists,
the 32-bit fields and the 64-bit fields return the same value. If a 32-bit field overflows, the
corresponding 64-bit field returns the correct value, and the 32-bit field returns a value of -1.
The ERROR field for the measured entity also returns -1 to indicate an overflow condition.
Convert your applications to use the 64-bit fields. The 32-bit fields might be deactivated in a
future RVU.
In MEASCOM commands and in command (OBEY) files, use the names of the 32-bit fields.
For example, issue the command LIST LINE BY INPUT-BYTES, not LIST LINE BY INPUT-BYTES-F.
MEASCOM uses the names of the 32-bit fields in output displays such as reports and plots.
The Measure G09 and later PVUs support up to six CLIPs in a SWAN concentrator.
OPDISK
The OPDISK entity provides information about one or more optical disk systems on the local system.
OPDISK 263