show [node node-id] csma-cd version
all [attributes]
all characteristics
Example:
show csma-cd all
1 – Characteristic
o version
Default: Current version number
Version number of the CSMA/CD Data Link architecture
specification to which the implementation conforms. You cannot
modify this characteristic.
2 – port
show [node node-id] csma-cd -
port port-name attribute [,attribute...]
all [attributes]
all counters
all identifiers
all status
The port-name can be either a simple name to uniquely
identify a particular PORT instance, or a wildcard to
identify multiple PORT instances.
Examples:
show csma-cd port CSMACD$ETA_0010 all
show csma-cd port * all
2.1 – Counters
Unless stated otherwise, counts include both normal and multicast
traffic and all protocol types, service access points (SAPs), and
protocol identifiers.
o creation time
Time at which the port was created.
o multicast octets received
Number of multicast data octets that were successfully received
and made available to the port user. The count is the number
of octets in the CSMA/CD user data field and does not include
MAC (medium access control, a sublayer of the CSMA/CD Data Link
layer) headers. Comparing this count to the octets received count
yields the gross percentage of bandwidth that was consumed (over
time) by multicast PDUs received by the port.
o multicast octets sent
Number of multicast data octets that were successfully sent
through the port. The count is the number of octets in the MAC
user data field, including any padding or length fields; it does
not include MAC headers. Comparing this count to the octets sent
count yields the gross percentage of bandwidth that was consumed
(over time) by multicast pdus transmitted by the port.
o multicast pdus received
Number of multicast PDUs that were successfully received and
made available to the port user. Counted PDUs passed address and
protocol filtering and were received without errors. Comparing
this count to the pdus received count yields a gross percentage
of CSMA/CD usage for multicast pdus received by this port.
o multicast pdus sent
Number of multicast PDUs that were successfully sent through the
port. Comparing this count to the pdus sent count yields a gross
percentage of CSMA/CD usage for multicast pdus sent by this port.
o octets received
Total number of MAC user data octets that were successfully
received and made available to the port user. Counted frames
passed address and protocol filtering for both individual and
multicast MAC addresses and were received without errors. The
count is the number of octets in the CSMA/CD user data field
plus any padding, Ethernet length fields, or logical link control
(LLC) header fields; it does not include MAC headers. Adding the
octets received count to the protocol overhead calculated from
the pdus received count yields the amount of CSMA/CD bandwidth
consumed by frames received by the port.
o octets sent
Total number of user data octets that were successfully sent
through the port. The count is the number of octets in the MAC
user data field including any padding or length fields; it does
not include MAC headers. Adding the octets sent count to the
protocol overhead calculated from the pdus sent count yields the
amount of CSMA/CD bandwidth consumed (over time) by frames sent
by the port.
o pdus received
Total number of PDUs that were successfully received and made
available to the port user. Counted PDUs passed address and
protocol filtering and were received without errors. The count
provides a gross measurement of incoming CSMA/CD usage by the
port.
o pdus sent
Total number of PDUs that were successfully sent through the
port. The count provides a gross measurement of outgoing CSMA/CD
usage by the port.
o unavailable user buffers
Number of times that no user buffer was available at the port for
an incoming frame that passed all filtering for the port. Used
in conjunction with the pdus received count, this counter can
indicate the rate of user buffer receive problems.
2.2 – Identifier
o name
Simple name assigned to the port when it is created.
2.3 – Status
o client
Name specified by the data link user when the port was opened.
o ethernet protocol types
Set of Ethernet protocol types that are currently recognized for
this port.
o length present
The data link adds (1) a length field on transmit frames, and (2)
assumes the presence of a length field and attempts to remove it
on received Ethernet frames. When false, the data link does not
add and remove length fields. This attribute is irrelevant for
ISO 8802-3 formatted frames, which always have a length field.
false The data link does not add and remove length fields.
true The data link adds and removes length fields.
o llc sap addresses
Set of individual and group logical link control (LLC) service
access point (SAP) addresses that are currently recognized for
this port.
o llc service
Type of LLC (logical link control) PDU processing that is
required on the port (as defined by the user when the port was
opened).
class 1 The data link provides class 1, type 1 service.
user- The user is responsible for handling the LLC
supplied protocol.
o mac addresses
Set of individual and multicast MAC (medium access control)
addresses that are currently recognized for this port.
o receive mode
Type of receive mode that is currently enabled for the port.
normal The port receives only those frames that meet the
normal address and protocol filtering requirements
requested by the user.
promiscuous The port receives all frames regardless of format
and MAC address.
o snap protocol identifiers
Set of subnetwork access protocol (SNAP) identifiers that are
currently recognized for this port.
o station
Name of the station associated with this port as specified by the
user when the port was opened.
o uid
Entity's unique identifier, which is generated when the port is
created.
3 – station
show [node node-id] csma-cd -
station station-name attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
Examples:
show csma-cd station * station buffers
show csma-cd station * all
show csma-cd station csmacd-1 all
3.1 – Characteristic
o station buffers
Default: implementation specific Value: 1-64
Number of receive buffers reserved for the station. You cannot
modify this characteristic.
3.2 – Counters
Unless stated otherwise, counts include both normal and multicast
traffic and all protocol types, service access points (SAPs), and
protocol identifiers.
o alignment errors
Number of times a received frame did not contain an integral
number of octets.
o carrier check failures
Number of times the data link did not sense the receive carrier
signal or detected an error in the receive carrier signal during
transmission of a frame.
o collision detect check failures
Number of times the collision detect test signal was not sensed
after a transmission. If this count approximates the number of
frames sent, either the collision detect circuitry is not working
correctly or the test signal is not implemented.
o creation time
Time at which the station was created.
o data overruns
Number of times the hardware lost one or more consecutive,
partially complete, incoming frames because it could not keep
up with the incoming frame rate. Used in conjunction with pdus
received, this count provides a measure of hardware resource and
bandwidth failures.
o excessive collisions
Number of times a transmission failed because the maximum
allowable number of retransmission attempts all culminated in
collisions.
o frame check errors
Number of times a received frame containing an integral number of
octets failed the frame check sequence (FCS).
o frame size errors
Number of times the user requested transmission of a frame
outside the range of valid frame sizes.
o frames too long
Number of times a received frame exceeded the maximum length
allowed by CSMA/CD medium access control.
o initially deferred pdus sent
Number of times a PDU was deferred by the station access
algorithm on the first attempt at transmission, but was then
transmitted successfully without collision. Used in conjunction
with pdus sent, this count measures the rate of CSMA/CD
contention with no collisions.
o late collisions
Number of times a collision was detected after the allotted time
for collisions had expired.
o multicast octets received
Number of multicast data octets that were successfully received.
The count is the number of octets in the CSMA/CD user data field
and does not include MAC headers. Comparing this count to the
octets received count yields the gross percentage of bandwidth
that was consumed (over time) by multicast frames received by the
local system.
o multicast octets sent
Number of multicast data octets that were successfully sent.
The count is the number of octets in the MAC user data field,
including any padding or length fields; it does not include MAC
headers. Comparing this count to the octets sent count yields the
gross percentage of bandwidth that was consumed (over time) by
multicast frames transmitted by the local system.
o multicast pdus received
Number of multicast PDUs that were successfully received.
Comparing this count to the pdus received count yields a gross
percentage of CSMA/CD usage for multicast PDUs received by this
system.
o multicast pdus sent
Number of multicast PDUs that were successfully sent. Comparing
this count to the pdus sent count yields a gross percentage of
CSMA/CD usage for multicast PDUs sent by this system.
o multiple collisions pdus sent
Number of times a PDU was successfully transmitted on the third
or later attempt by the station access algorithm after normal
collisions on previous attempts. Used in conjunction with pdus
sent, this count provides a measure of CSMA/CD media contention
at a level where there are collisions and the backoff algorithm
no longer works efficiently.
o octets received
Total number of MAC user data octets that were successfully
received from frames that passed address and protocol filtering
for both individual and multicast MAC addresses. The count is
the number of octets in the CSMA/CD user data field plus any
padding, Ethernet length fields, or LLC header fields; it does
not include MAC headers. Adding the octets received count to the
protocol overhead calculated from the pdus received count yields
the amount of CSMA/CD bandwidth consumed by frames received by
the local system.
o octets sent
Total number of user data octets that were successfully sent.
The count is the number of octets in the MAC user data field
including any padding or length fields; it does not include MAC
headers. Adding the octets sent count to the protocol overhead
calculated from the pdus sent count yields the amount of CSMA
/CD bandwidth consumed (over time) by frames sent by the local
system.
o pdus received
Total number of PDUs that passed address and protocol filtering
and were received without errors. The count provides a gross
measurement of incoming CSMA/CD usage by the local system; this
information can be used in conjunction with other counters to
approximate the average receive frame size or to determine the
ratio of errors to successful receives.
o pdus sent
Total number of PDUs successfully sent. The count provides a
gross measurement of outgoing CSMA/CD usage by the local system;
this information can be used in conjunction with other counters
to approximate the average transmit frame size or to determine
the ratio of errors to successful transmissions.
o receive data length errors
Number of times a frame was received with a length field value
that was invalid for the number of octets actually received by
medium access control.
o send data length errors
Number of times the user requested transmission of an 802.3 frame
with a length field value that was not valid for the number of
octets actually passed.
o single collision pdus sent
Number of times a PDU was successfully transmitted on the second
attempt by the station access algorithm after a normal collision
occurred on the first attempt. Used in conjunction with pdus
sent, this count provides a measure of CSMA/CD media contention
at a level where there are collisions, but the backoff algorithm
still works efficiently.
o station failures
Number of times that the station self-testing procedures reported
failure.
o unavailable station buffers
Number of times a complete, fully received PDU was discarded
because no station buffer was available. Used with pdus received,
this count provides a measure of receive problems related to the
station buffer.
o unavailable user buffers
Number of times no user buffer was available for an incoming
frame that passed all filtering for the port. Used in conjunction
with the pdus received count, this counter can indicate the rate
of user buffer receive problems.
o unrecognized individual destination pdus
Number of times a received PDU with an individual destination MAC
address was discarded because there was no port with the correct
Ethernet protocol type, SNAP protocol identifier, or link logical
control SAP address enabled.
o unrecognized multicast destination pdus
Number of times a received PDU with a multicast destination MAC
address was discarded because there was no port with the correct
Ethernet protocol type, SNAP protocol identifier, or link logical
control SAP address enabled.
3.3 – Identifier
o name
Simple name assigned to the station when it is created.
3.4 – Status
o address filters
All individual MAC addresses currently enabled by any of the
ports on the station.
o communication port
DECnet-Plus device name for the station.
o hardware address
Individual medium access control (MAC) address that was assigned
during manufacture of the communications hardware that is
associated with the station.
o mac address
Current MAC address (if any) of the station. For more information
about the MAC address, see the enable command.
o receive mode
Current receive mode for the station. Some stations may not
support all modes.
normal The station receives only those frames (individual
and multicast) that meet the normal format,
protocol, and access control requirements.
all The station receives all individual-addressed
multicast frames that meet the normal format, protocol, and
address requirements, and all multicast-addressed
frames regardless of their format, protocol, and
address types. This function is only supported on
OpenVMS.
promiscuous The station receives all frames (individual and
multicast) regardless of format, Ethernet protocol
type, SNAP identifier, LLC SAP address, or MAC
address. This function is only supported on
OpenVMS.
o state
Operational state of the station.
failed Either an attempt to enable the station failed
during the self-test or the station was on and the
data link determined that the station would now
fail the self-test.
initializing The station is currently being initialized and
tested by the data link.
off The station is disabled.
on The station is enabled and available for use.
For more information on station states, see the Network
Management manual.
o uid
Entity's unique identifier, which is generated when the station
is created.