Field Name	Description
`Total Interrupts`	Total number of interrupts received by the board.
`Transmits Started`	Indicates the number of packet sends initiated by host applications to the TX 3220.
`Receives`	Total number of valid messages received by the driver from the board. (Not used with TX 3220).
`OS READY interrupts`	Number of interrupts the driver received from the TX 3220, indicating the OS was loaded successfully.
`MSG interrupts`	Number of interrupts the driver received from the board for a message.
`MSGACK interrupts`	Total number of times the driver was interrupted by the TX 3220 for a new message combined with an acknowledgement for a previously transmitted message.
`RXACK interrupts`	Total number of times the driver was interrupted by the board for the acknowledgement of a message it sent to the TX 3220.
`OS LOAD packet interrupts`	Number of interrupts the driver received from a board indicating it was ready for another OS LOAD packet.
`Stray interrupts`	Number of interrupts the driver received for which a TX 3220 board could not be identified.
`Out of State errors`	Number of times the driver received a valid request, but was in the wrong state.
`Out of memory errors`	Number of times the driver could not allocate memory from the OS.
`Messages for Unbound Channel`	Number of times the driver could not send a message from the host application because the destination channel was unknown.
`Unknown errors`	Number of errors not matching the aforementioned criteria. (Not used with TX 3220).
`Successful OS runs`	Number of times the OS was successfully started. (Not used with TX 3220).
`Unexpected ACK received`	Number of acknowledgements the driver received for messages it didn't send. (Not used with TX 3220).
`Unexpected ACK during load`	Number of unexpected acknowledgements the driver received while loading the OS onto the board. (Not used with TX 3220).

(Page 1 of 1 in this chapter) Version

Chapter 5

Verifying the Installation

5.1 Introduction

5.2 Status Indicator LEDs

5.3 TX 3220 Board Status LEDs

5.4 Verifying the TX 3220 is Installed Correctly

: 5.4.1 Viewing the Statistics for the TX 3220 Board (Windows NT)
: 5.4.2 Viewing the Statistics for the TX 3220 Board (Solaris)

5.1 Introduction

This chapter lists the procedures to verify that your TX 3220 board is installed and configured properly.

5.2 Status Indicator LEDs

The TX 3220 boards have indicators (LEDs) for each connection on the end bracket. The location of the indicators are shown in Figure 8: Figure 8. TX 3220 LEDs
The following table describes the functionality of each LED. All descriptions apply to both T1/E1 connections, unless otherwise stated. LED Description Green (Left) · Connection A - Indicates transmitting/receiving activity on the Ethernet link. When Ethernet activity is present, the LED will flicker. · Connection B - Indicates the status of the Ethernet link. This LED will be ON if the Ethernet link is sound. Red Indicates loss of frame, loss of signal, or bit rate error. Yellow Indicates remote loss of frame, or remote loss of signaling multiframe. Green (Right) Indicates proper frame SYNC to the trunk. All required framing alignment has been found. This LED will be OFF is one or more of the following conditions exist: all ones alarm (AIS), loss of frame, loss of signaling multiframe, or CRC errors (when the board is configured for ESF).

LED	Description
Green (Left)	· Connection A - Indicates transmitting/receiving activity on the Ethernet link. When Ethernet activity is present, the LED will flicker. · Connection B - Indicates the status of the Ethernet link. This LED will be ON if the Ethernet link is sound.
Red	Indicates loss of frame, loss of signal, or bit rate error.
Yellow	Indicates remote loss of frame, or remote loss of signaling multiframe.
Green (Right)	Indicates proper frame SYNC to the trunk. All required framing alignment has been found. This LED will be OFF is one or more of the following conditions exist: all ones alarm (AIS), loss of frame, loss of signaling multiframe, or CRC errors (when the board is configured for ESF).

5.3 TX 3220 Board Status LEDs

In addition to the status indicator LEDs mentioned in Section 5.2, there are also eight LEDs on the top of the board (D10-D17). These LEDs indicate the current status of the TX 3220 board. When the TX 3220 board is booted, the lights will light up and then turn off. If D17 is ON and D16 is flashing, the boot was successful. If this does not occur, consult the following table for debugging information and contact Developer Support. LED Number Description (when LED is ON) D15 Application-controlled LED. (Reserved for future use). D14 ON when KERNEL detects a problem. Use the 'log' command in cpcon to view logged error information. D13 ON when KERNEL detects host communication error. D12 ON when board receives a message from the host. D11 ON when board transmits a message to the host. D10 ON when a memory full condition occurs on the board.

LED Number	Description (when LED is ON)
D15	Application-controlled LED. (Reserved for future use).
D14	ON when KERNEL detects a problem. Use the '`log`' command in `cpcon` to view logged error information.
D13	ON when KERNEL detects host communication error.
D12	ON when board receives a message from the host.
D11	ON when board transmits a message to the host.
D10	ON when a memory full condition occurs on the board.

5.4 Verifying the TX 3220 is Installed Correctly

After you have installed the TX software and rebooted your Windows NT system, you can verify that the hardware/software installation is successful with Event Viewer.
To run Event Viewer, point to Programs, then Administrative Tools, and then click Event Viewer. In the Event Viewer system log, you will see one or more messages from the source:

NMS TxPCI

If these messages are Informational, the driver loaded successfully.

If these messages are Warnings or Errors, see Section 5.4.1, Viewing the Statistics for the TX 3220 Board (Windows NT), to identify the source of the error(s).
If you are using a Solaris (Intel or SPARC) system, you can check to see whether or not the TX driver loaded successfully with the following command: modinfo | grep txpci
If the TX driver loaded successfully, the output should look similar to this: 101 fea0b570 71a1 82 1 txpci (txpci)
If the previous output does not appear, the driver did not load successfully. Refer to Section 5.4.2, Viewing the Statistics for the TX 3220 Board (Solaris) for help in determining the cause of the problem.

5.4.1 Viewing the Statistics for the TX 3220 Board (Windows NT)

The TX configuration utility provides an interface which allows the administrator or software developer to view driver-level statistics describing the packet flow and certain error conditions. In addition, this utility also reports the current logical state of the associated CP.
The rest of this section describes the procedure for displaying the Statistics dialog box and interpreting the data provided.

Click the Start button, point to Settings, and click Control Panel.

Click the NMS TX CPs icon. The Configure/Install/Remove TX dialog box appears. A list of currently installed TX CPs is displayed.

Highlight the name of the CP for which you want to see the statistics and click Configure Selected CP. The NMS PCI TX Configuration dialog box appears.

Click the Statistics tab. The Statistics dialog box appears.

The Statistics dialog box is a snapshot of the current driver statistics for the selected CP. While the statistics will not automatically update themselves on the screen, the statistic counters continue to update themselves in the driver independently of the snapshots. To update this screen at any time, click on Refresh. A new snapshot will be taken and the new statistics will appear on the screen. To reset all of the values to zero, click Zero Stats.
The following table provides a brief description of each statistic:

Statistic

Description

Adapter State

This field should always indicate "running". If this field ever displays a value other than "running", record the information from this screen and contact Developer Support.

Send Requests

Indicates the number or packet sends initiated by host applications to the TX 3220.

Sends Successful

Indicates the number of send requests that were received by the TX 3220 and successfully posted to a process running on the TX 3220. In almost all cases, this value will be equal to the Send Requests field.

Send Errors

Indicates the number of errors reported by the TX 3220 to sends initiated by host applications. In most situations, this will indicate a serious problem with the TX 3220 and Developer Support should be called. However, this may also indicate an application error on the host. For example, if the user application sends a request to the RTP process, but has not loaded the RTP process, an error will be returned by the TX adapter.

Bytes Sent

Indicates the total number of bytes sent by applications to the TX 3220.

Sends Deferred

Indicates the number of sends the TX 32xx driver has had to queue as a result of the TX 3220 not responding fast enough to the sends. It is unlikely that this value will ever be any other value than zero. If this value is greater than zero, it indicates the TX 3220 is operating beyond its performance capabilities.

Control Msgs Sent

Indicates the number of specialized control messages sent between the TX32xx driver and the TX 3220 board. An example of a control message is the configurable "alive" message that is sent by the driver to the TX 3220 to determine the state of the adapter.

FIFO Msgs from CP

Indicates the total number of I20 messages received from the TX 3220.

Send Replies Seen

Indicates the total number of send replies seen from the TX 3220. This value should always equal the total number of successful sends PLUS send errors.

Valid Data Msgs Rcvd.

Indicates the number of messages/packets received from the TX 3220.

Valid Cntl Msgs Rcvd.

Indicates the number of specialized control messages received by the TX 32xx driver and the TX 3220 board. An example of this is the "I'm alive" message that is sent by the TX 3220 in response to an "alive" message sent by the TX 32xx driver.

Invalid Msgs Rcvd.

Indicates the number of messages received by the TX 32xx driver that do not pass validation checks. If this value is ever greater than zero, contact Developer Support.

Bad Function Msgs Rcvd.

Indicates the number of messages received by the TX 32xx driver that do not pass validation checks. If this value is ever greater than zero, contact Developer Support.

Target Unknown Msgs Rcvd.

Indicates the number of messages received from the TX 3220 that could not be delivered to an application. This is the result of a failure to register an application for a particular message.

Msgs Discarded - Que Full

Indicates the number of messages received from the TX 3220 that have been discarded due to a queue overflow to the host application. This usually indicates a host application is having difficulties posting reads to the driver as fast as messages are being sent from the TX 3220. This may indicate a blocking problem with the application, or a faster host CPU is required.

Bytes Received

Indicates the total number of data bytes received by the TX 32xx driver from the TX 3220 board.

Unexpected Reply Msgs Received

Indicates the number of replies to Message Sends Received that cannot be correlated with a message send. If this value is ever greater than zero, contact Developer Support.

Replies to Input Deferred

Indicates the number of times the TX 32xx driver could not send a reply to the TX 3220, resulting from a lack of message frames. It is unlikely this field will ever display a non-zero value. However, if this value is ever greater than zero, it indicates the TX 3220 has either failed, or is operating beyond its performance capabilities.

Replies to Input Not Sent

Indicates a serious error with the TX 32xx driver. If this value is ever greater than zero, contact Developer Support.

Statistic	Description
`Adapter State`	This field should always indicate "running". If this field ever displays a value other than "running", record the information from this screen and contact Developer Support.
`Send Requests`	Indicates the number or packet sends initiated by host applications to the TX 3220.
`Sends Successful`	Indicates the number of send requests that were received by the TX 3220 and successfully posted to a process running on the TX 3220. In almost all cases, this value will be equal to the `Send Requests` field.
`Send Errors`	Indicates the number of errors reported by the TX 3220 to sends initiated by host applications. In most situations, this will indicate a serious problem with the TX 3220 and Developer Support should be called. However, this may also indicate an application error on the host. For example, if the user application sends a request to the RTP process, but has not loaded the RTP process, an error will be returned by the TX adapter.
`Bytes Sent`	Indicates the total number of bytes sent by applications to the TX 3220.
`Sends Deferred`	Indicates the number of sends the TX 32xx driver has had to queue as a result of the TX 3220 not responding fast enough to the sends. It is unlikely that this value will ever be any other value than zero. If this value is greater than zero, it indicates the TX 3220 is operating beyond its performance capabilities.
`Control Msgs Sent`	Indicates the number of specialized control messages sent between the TX32xx driver and the TX 3220 board. An example of a control message is the configurable "alive" message that is sent by the driver to the TX 3220 to determine the state of the adapter.
`FIFO Msgs from CP`	Indicates the total number of I20 messages received from the TX 3220.
`Send Replies Seen`	Indicates the total number of send replies seen from the TX 3220. This value should always equal the total number of successful sends PLUS send errors.
`Valid Data Msgs Rcvd.`	Indicates the number of messages/packets received from the TX 3220.
`Valid Cntl Msgs Rcvd.`	Indicates the number of specialized control messages received by the TX 32xx driver and the TX 3220 board. An example of this is the "I'm alive" message that is sent by the TX 3220 in response to an "alive" message sent by the TX 32xx driver.
`Invalid Msgs Rcvd.`	Indicates the number of messages received by the TX 32xx driver that do not pass validation checks. If this value is ever greater than zero, contact Developer Support.
`Bad Function Msgs Rcvd.`	Indicates the number of messages received by the TX 32xx driver that do not pass validation checks. If this value is ever greater than zero, contact Developer Support.
`Target Unknown Msgs Rcvd.`	Indicates the number of messages received from the TX 3220 that could not be delivered to an application. This is the result of a failure to register an application for a particular message.
`Msgs Discarded - Que Full`	Indicates the number of messages received from the TX 3220 that have been discarded due to a queue overflow to the host application. This usually indicates a host application is having difficulties posting reads to the driver as fast as messages are being sent from the TX 3220. This may indicate a blocking problem with the application, or a faster host CPU is required.
`Bytes Received`	Indicates the total number of data bytes received by the TX 32xx driver from the TX 3220 board.
`Unexpected Reply Msgs Received`	Indicates the number of replies to Message Sends Received that cannot be correlated with a message send. If this value is ever greater than zero, contact Developer Support.
`Replies to Input Deferred`	Indicates the number of times the TX 32xx driver could not send a reply to the TX 3220, resulting from a lack of message frames. It is unlikely this field will ever display a non-zero value. However, if this value is ever greater than zero, it indicates the TX 3220 has either failed, or is operating beyond its performance capabilities.
`Replies to Input Not Sent`	Indicates a serious error with the TX 32xx driver. If this value is ever greater than zero, contact Developer Support.

5.4.2 Viewing the Statistics for the TX 3220 Board (Solaris)

The cputil utility, located in the /opt/nmstx/bin/ directory, can be used to access the statistics for a TX 3220 board. This can be useful in troubleshooting problems that occur. The following steps explain how to run the cputil utility and interpret the results: Log on as root, and, at the command prompt, type: cputil -b 1 -R This will reset board number 1. To bring up a list of current statistics for board 1, type: cputil -b 1 -S The output should look similar to this: Board(1) statistics: Total Interrupts [455] Transmits Started [0] Receives [0] OS READY interrupts [0] MSG interrupts [0] MSGACK interrupts [0] RXACK interrupts [0] OS LOAD packet interrupts [0] Stray interrupts [0] Out of State errors [0] Out of Memory Errors [0] Messages for Unbound Channel [0] Unknown errors [0] Successful OS runs [0] Unexpected ACK received [0] Unexpected ACK during load [0] The following table explains each field that appears in the cputil output: Field Name Description Total Interrupts Total number of interrupts received by the board. Transmits Started Indicates the number of packet sends initiated by host applications to the TX 3220. Receives Total number of valid messages received by the driver from the board. (Not used with TX 3220). OS READY interrupts Number of interrupts the driver received from the TX 3220, indicating the OS was loaded successfully. MSG interrupts Number of interrupts the driver received from the board for a message. MSGACK interrupts Total number of times the driver was interrupted by the TX 3220 for a new message combined with an acknowledgement for a previously transmitted message. RXACK interrupts Total number of times the driver was interrupted by the board for the acknowledgement of a message it sent to the TX 3220. OS LOAD packet interrupts Number of interrupts the driver received from a board indicating it was ready for another OS LOAD packet. Stray interrupts Number of interrupts the driver received for which a TX 3220 board could not be identified. Out of State errors Number of times the driver received a valid request, but was in the wrong state. Out of memory errors Number of times the driver could not allocate memory from the OS. Messages for Unbound Channel Number of times the driver could not send a message from the host application because the destination channel was unknown. Unknown errors Number of errors not matching the aforementioned criteria. (Not used with TX 3220). Successful OS runs Number of times the OS was successfully started. (Not used with TX 3220). Unexpected ACK received Number of acknowledgements the driver received for messages it didn't send. (Not used with TX 3220). Unexpected ACK during load Number of unexpected acknowledgements the driver received while loading the OS onto the board. (Not used with TX 3220).

(Page 1 of 1 in this chapter) Version

tech_support@nmss.com