NS 3000/iX LAPBMUX Link Statistics
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
LINKSTATE Parameter Fields
The following is an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=LINKSTATE command:
Linkname: PLSPLNK7 Linktype: PCI LAPBMUX Linkstate: CONNECTED LEVEL 2Linkname — The Likname field specifies the name of the link. Linktype — The Linktype field specifies the type of link, such as LAP-B, LAPBMUX, 100BT, or IEEE 802.3, that is being monitored, and the type of I/O bus it is on (will be preceded with "PCI" for PCI LAPBMUX links). Linkstate — The Linkstate field specifies the current state of the link. The possible link states are as follows:
Not connected
Connected level 1.
Connected level 2
Connecting level 1.
Connecting level 2.
Disconnecting level 1.
Disconnecting level 2.
CONFIGURATION Parameter Fields
The CONFIGURATION parameter for LAPBMUX links displays the LINKSTATE parameter fields and many additional fields. These additional fields display information that is related to the link configuration and which, except for the Cable Type parameter, are input through the NMMGR configuration program. LAPBMUX CONFIGURATION Parameter Output provides an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=CONFIGURATION command:
Linkname: PLAPLNK7 Linktype: PCI LAPBMUX Linkstate: CONNECTED LEVEL 2 Physical Path: 0/6/2/1.7 Physical interface V.35 LAPB parm T1 :sec 3 Transmission speed 20480009 LAPB parm N2 :retry 20 Clock source External LAPB parm K 7 Local mode DTE Module Count 8 Connect timeout :sec 900 Buffer size :bytes 4096 Adapter timeout :sec 10Physical Path — The Physical Path field displays the current physical path for the adapter card as specified in the NMCONFIG configuration file.
 |
NOTE: On PCI LAPBMUX links, the physical path generally has more components and is a "longer" path (e.g., 0/6/0/1.2, in which 0/6/0/1 is the path .2 is the port number) along with the port number associated with that link. The output for PCI links is different from that HP-PB. |
RS232
V.35
None
External
Internal
DTE, for connection to a device that is configured as a DCE.
DCE, for connection to a device that is configured as a DTE.
STATISTICS Parameter Fields
The STATISTICS parameter for LAPBMUX links displays many fields in addition to the LINKSTATE parameter fields. The CONFIGURATION parameter fields are not displayed when this parameter is used. For an example of the data that is displayed when you issue the LINKCONTROL linkname;STATUS=STATISTICS command:
Transmit bytes 11543567876 Receive bytes 32948732576 TransmitS 13166130 ReceiveS 18338778 Transmits ctrl bytes 0 Receive ctrl bytes 0 Transmit ctrl 0 Receive ctrl 0 Transmit overruns 0 Receive overruns 0 Tx deferred: iova 0 Recv deferred: iova 0 Tx deferred: buffer 0 Recv dropped: buffer 0 Level-2 connects 1 Recv dropped: addr 0 Level-2 disconnects 0 Recv dropped: other 0 Connect timeouts 0 Secs since clear 173980This command displays statistics about data transmitted and received across the link. Many field values are summations. Over time, the values in these fields reach their maximum possible value. When this occurs, these fields can only be reset manually. Transmit bytes — Total number of bytes successfully transmitted onto the medium. This includes normal data bytes as well as control data bytes. The maximum printable value of this 64-bit field is 17 digits, or about 99 million Gbytes. In the previous example, 10.1 million bytes were transmitted, or about 9.7 Mbytes. Transmits — Total number of frames successfully transmitted onto the medium at normal priority. Normal data as well as the control data frames. The byte count given by Transmit bytes is distributed over this number of frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example above, 127700 frames were transmitted at normal priority. Transmit ctrl bytes — Total number of control bytes successfully transmitted onto the medium. The maximum printable value of this 64-bit field is 17 digits, or about 99 million Gbytes. In the previous example, 0 control data bytes were transmitted. Transmit ctrl — Total number of control frames successfully transmitted onto the medium at normal priority. The byte count given by Transmit ctrl bytes is distributed over this number of frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 0 control frames were transmitted at normal priority. Transmits overruns — Total number of frames that were deferred to other network traffic before their initial transmission onto the network. This means that the 100Base-T card had to wait for carrier to drop and stay dropped for a few nanoseconds, before attempting to transmit the frame. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 1738 transmit frames were deferred. Level-2 connects — Number of times the link driver noticed the link had previously been established, but was no longer up. This may occur because the cable was unplugged, the hub was powered off, the hub automatically requested a reconnect, or normally (at link shutdown time). This total does not include repetitive, failed attempts by the link driver to reestablish the link. The maximum value of this 32-bit field is 2147483647. Level-2 disconnects — Number of times the link driver noticed the link had previously been established, but was no longer up. This may occur because the cable was unplugged, the hub was powered off, the hub automatically requested a reconnect, or normally (at link shutdown time). This total does not include repetitive, failed attempts by the link driver to reestablish the link. The maximum value of this 32-bit field is 2147483647. Receive bytes — Total number of bytes successfully transmitted onto the medium. This includes normal data bytes as well as control data bytes. The maximum printable value of this 64-bit field is 17 digits, or about 99 million Gbytes. In the previous example, 10.1 million bytes were transmitted, or about 9.7 Mbytes. Receives — Total number of frames successfully received from the card at normal priority. This includes normal data as well as control data frames. The byte count given by Receive bytes is distributed over this number of frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 127700 frames were transmitted at normal priority. Receive ctrl bytes — Total number of control bytes successfully received from the card. The maximum printable value of this 64-bit field is 17 digits, or about 99 million Gbytes. In the previous example, 10.1 million bytes were received, or about 9.7 Mbytes. Receive ctrl — Total number of control frames successfully received from the card at normal priority. The byte count given by Receive Ctrl bytes is distributed over this number of frames. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 0 control frames were received at normal priority. Receive overruns — Total number of frames that were deferred to other network traffic before their initial transmission onto the network. This means that the 100Base-T card had to wait for carrier to drop and stay dropped for a few nanoseconds, before attempting to transmit the frame. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 1738 transmit frames were deferred. Recv dropped: buffer — Total number of frames received from the adapter card, but dropped because no data buffers were available from the upper layer protocol requesting to receive these frames. This is a relatively common occurrence, amounting to flow control for all protocols sharing those buffers. Many protocols include built-in mechanisms for detecting lost frames and requesting their retransmission from the remote side. The maximum value of this 32-bit field is 2147483647. In the example above, out of 66.4 million frames received, 262 have been dropped for lack of buffer resources; any similar level would be considered normal. Recv dropped: addr — Total number of frames received by the adapter card, but dropped because no upper layer protocol had requested future reception of those frames, or because that protocol unbound itself from the link while the received frame was still in motion. Older, intelligent adapter cards can invisibly receive and drop these frames, often without ever reporting them as statistics. But today's adapters are not intelligent, and require link driver involvement. For users unfamiliar with seeing it, this statistic may seem excessive. But it is important because it gives an indication of the amount of unnecessary traffic present on the network segment to which the adapter card is connected. High values may indicate a need to resegment the network, since systems and their adapters are spending a large amount of time and resources recognizing and dropping frames they do not care to see. High volumes of such traffic can also limit network bandwidth. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, out of 15.7 million frames received, 9.87 million have been dropped based on address: about 63% of all frames received are then being dropped. This level would be considered high. Recv dropped: other — Sum total number of frames received from the adapter card, but dropped because: an upper layer protocol error was returned; the required address format was not supported; the frame arrived while the link driver was in an unusual state; or for perfect multicast filtering reasons. The maximum value of this 32-bit sum is 2147483647. In the example above, 24785 frames have been dropped for one or more of the reasons listed; this number would be considered high, and further investigation might be needed if it appears to be impacting any applications. Recv deferred — Number of times an address-matched receive frame was temporarily held (queued) by the link driver, because of a momentary lack of DMA resources. Once those resources became available, the frame was automatically transferred to the host. The maximum printable value of this 64-bit field is 17 digits, or about 99 million billion frames. In the previous example, 123 frames were temporarily held. Secs since clear — The number of seconds elapsed since statistics were last reset via the LINKCONTROL linkname; STATUS=RESET command. This gives the sample time over which the displayed statistics have been collected. Per-time-unit figures may then be calculated if desired. The maximum value of this 32-bit field is 2147483647, or about 68 years.
RESET Parameter Fields
The RESET parameter for LAPBMUX links reset all the accumulated statistics for the links, The command also displays all of the LINKSTATE, CONFIGURATION, and STATISTICS parameter fields. Refer to the STATISTICS parameter for a description of the displayed fields.
ALL Parameter Fields
The ALL parameter for LAPBMUX links displays all of the LINKSTATE, CONFIGURATION, and STATISTICS parameter fields. This is an example of the ALL parameter output:
Linkname: PLAPLNK7 Linktype: PCI LAPBMUX Linkstate: CONNECTED LEVEL 2 Physical Path: 0/6/2/1.7 Physical interface V.35 LAPB parm T1 :sec 3 Transmission speed 56000 LAPB parm N2 :retry 20 Clock source External LAPB parm K 7 Local mode DTE Module Count 8 Connect timeout :sec 900 Buffer size :bytes 4096 Adapter timeout :sec 10 Transmit bytes 11543567876 Receive bytes 32948732576 TransmitS 13166130 ReceiveS 18338778 Transmits ctrl bytes 0 Receive ctrl bytes 0 Transmit ctrl 0 Receive ctrl 0 Transmit overruns 0 Receive overruns 0 Tx deferred: iova 0 Recv deferred: iova 0 Tx deferred: buffer 0 Recv dropped: buffer 0 Level-2 connects 1 Recv dropped: addr 0 Level-2 disconnects 0 Recv dropped: other 0 Connect timeouts 0 Secs since clear 173980
|
NS 3000/iX 100Base-T Link Statistics |
Appendix B Submitting an CR |