Measure Reference Manual

Usage Notes for G-Series LINE Entities
• 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 INPUT-BYTES-F collects the same data as the 32-bit field
INPUT-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.
• SUBSYSTEM-VERSION for ZMSLINE records is provided by the specific product subsystem of
the line represented by each ZMSLINE record; for example, SNAX/XF, X25AM, or ENVOY.
In G-series RVUs, the value of SUBSYSTEM-VERSION is zero.
• The G09 PVU of Measure supports up to six CLIPs in a SWAN concentrator.
NETLINE
The NETLINE entity provides information about network communications lines.
PageTopic
255Entity specification syntax for NETLINE entities
256DDL records for NETLINE entities
258DDL field definitions for NETLINE entities
263Usage notes for NETLINE entities
Entity Specification Syntax for NETLINE Entities
To describe NETLINE entities:
NETLINE entity-spec [,entity-spec] ...
NOTE: You can measure G-series network communication lines with a D-series measurement
application if it specifies all NETLINE entities (ADD NETLINE *) or only $device or $device
(cpu). If the application specifies controller, channel, or unit, you must modify the entity
identifiers to measure G-series NETLINE entities.
NETLINE
collects information about one or more network communications lines.
entity-spec
is specified as:
{ * }
{ $device }
{ cpu [ ( %Htrackid [, clip [, line ] ] ) ] [ ( type [, subtype ] ) ] }
or for D-series data only, specified as:
{ $device [ ( cpu [ , channel [ , ctrl [ , unit ] ] ] ) ] }
where:
NETLINE 255