The following options are available from from this menu:
CHANGE SERVERS - Selecting this option presents a list of the servers this node is currently attached to. Simply highlight the server from which you wish to monitor users and press <ENTER>. If you wish to monitor users on a server that is not on the list, exit this application, attach to the desired server, and re-enter this application. The server will then appear on the list.
LAN INFORMATION -Selecting this option presents a list of users attached to the server you have selected. Simply highlight the user name and press <ENTER>. NOTE: The server is NOT returning the diagnostic information about the node selected. This application uses the connection information from the server to identify the node for the user name you select. This application then sends Diagnosic request packets directly to the node and relies upon the node to respond with the diagnostic information.
SERVER INFORMATION Selecting this option provides information about the server you have selected.$
Server Name : Name of the server occupying this slot in the connection table.
Server Used : This field indicates whether the corresponding 32-byte server entry is in use. A value of 0x00 means the slot is empty. A value of 0xFF (255) means the entry is in use.
Order Number : This fields indicates the order number (1 - 8) assigned to the corresponding server. The lowest order number indicates the server with the lowest 10-byte network/node address, assuming the first byte is the most significant. The second lowest order number indicates the second lowest address, and so on.
Server Network : This field indicates the 4-byte network address of the associated server.
Server Node : This field indicates the 6-byte node address of the network interface card installed in the associated server.
Server Socket : This field indicates the file server socket number the target workstation uses to communicate with the associated server.
Received Time Out : This field returns a value indicating the estimated round=trip time required for the target workstation to send a request packet to the file server and receive acknowledgement. This value is specifed in "TICKS". One tick = 1/18th of a second.
Immediate Node : This field indicates the node address of the router the workstation uses to send packets to the file server.E
Sequence Number : This field returns the sequence number of the last packet the target workstation sent to the file server. Each time the workstation sends a packet to the file server, the workstation increases this counter. NOTE: For purposes of increased security this value is always 0 for nodes using the DOS REQUESTOR (VLM's). NETX will return a valid sequence number.
Connection Number : This field indicates the connection number the workstation is using to communicate with the file server.
Connection OK : This field returns a value of 0x00 if the connection between the workstation and the server is bad.
Maximum Time Out : This field returns a value indicating the estimated maximum round-trip time required for the target workstation to send a request packet to the file server and receive a reply packet. NOTE: This value is specified in "TICKS". Each is 1/18th of a second.
Send Packet Count : This field indicates the number of times (since IPX was loaded) that applications have called IPX to send a packet.
Malformed Packet Count : This field indicates the number of times (since IPX was loaded) that applications have passed malformed packets to IPX. A packet is malformed if the value in its ECB's FRAGMENT COUNT field is 0 or if the value in the ECB's first FRAGMENT DESCRIPTOR field's SIZE field is less than 30 bytes.
Get ECB Request Count : This field indicates the number of times (since IPX was loaded) that IPX has supplied Receive ECB's for incoming packets.
Get ECB Failure Count : This field indicates the number of times (since IPX was loaded) that IPX has been unable to supply a receive ECB for an incoming packet.
AES Event Count : This field indicates the number of times (since IPX was loaded) that IPX has used the AES (Asynchronous Event Scheduler) to schedule an event.
Postponed AES Event Cnt: This field indicates the number of times (since IPX was loaded) that IPX has been unable to service an AES event on time. For example, IPX cannot send an outgoing packet to a driver that is busy with another packet.
Max Configured Sockets : This field indicates the maximum number of open sockets possible on the target node. (This value is configurable).
Max Open Sockets Count : This field indicates the maximum number of sockets that have been open simultaneously since IPX was loaded.
Open Socket Failure Count : This field indicates the number of times (since IPX was loaded) that applications have unsuccessfully called the IPXOpenSocket function. IPX cannot open a socket if the socket table is full or is the socket is already open.
Listen ECB Count : This field indicates the number of times that applications have given IPX a listen ECB.
ECB Cancel Failure Count : This field indicates the number of times (since IPX was loaded) that IPX has been unable to cancel an ECB. For example, IPX cannot cancel an ECB if the driver and the ECB have entered a critical section just prior to sending a packet. In this case, the cancellation is too late.
Find Route Failure Count : This field indicates the number of times that IPX has been unable to find a route to a requested network address.4$
Max Connections Count : This field indicates the maximum number of SPX connections possible on the target node. (This value is configurable.)
Max Used Connection Count : This field indicates the maximum number of SPX connections that have been open simultaneously since IPX was loaded.
Establish Connection Rqst : This field indicates the number of times (since SPX was loaded) that applications have issued calls to SPXEstablishConnection.
Establish Connection Fail : This field indicates the number of times (since SPX was loaded) that calls to SPXEstablishConnection have failed because the SPXPacketHeader was too small, the SPX Connection Table was full, or no router was found to the target network.
Listen Connection Rqst Cnt : This field indicates the number of times (since SPX was loaded) that applications have issued calls to SPXListenForConnection.
Listen Connection Fail Cnt : This field indicates the number of times (since SPX was loaded) that calls to SPXListenForConnection have failed because the SPX Connection Table was full.
Send Packet Count : This field indicates the number of times (since SPX was loaded) that applications have issued calls to SPXSendSequencedPacket.
Window Choke Count : This field indicates the number of times (since SPX was loaded) that SPX has failed to send a packet because the target station had not allocated a receive buffer.
Bad Send Packet Count : This field indicates the number of times (since SPX was loaded) that applications have incorrectly called SPXSendSequencedPacket by passing an invalid connection ID or bypassing the address of an ECB that indicates a packet header size of less than 42 bytes.
Send Failure Count : This field indicates the number of times (since SPX was loaded) that SPX has been unable to send a packet across and SPX connection and receive acknowledgment. In such a case, SPX aborts the connection and informs the calling application.
Abort Connection Count : This field indicates the number of times (since SPX was loaded) that applications have called SPXAbortConnection.
Listen Packet Count : This field indicates the number of times that applications have given listen ECB's to SPX.
Bad Listen Packet Count : This field indicates the number of times (since SPX was loaded) that applications have passed SPX a packet whose associated ECB is malformed. An ECB is malformed if the value in its FRAGMENT COUNT field is 0, if the value in its first FRAGMENT DESCRIPTOR field's SIZE field is less than 42, or if the listen socket is not open.
Incoming Packet Count : This field indicates the number of times (since SPX was loaded) that the node's driver has given an incoming packet to SPX.
Bad Incoming Packet Cnt : This field indicates the number of times (since SPX was loaded) that SPX has received and discarded a packet because the connection ID in the packet was wrong.
Suppressed Packet Count : This field indicates the number of times (since SPX was loaded) that SPX has discarded inbound packets because they were duplicates of previously received packets.
No Session Listen ECB : This field indicates the number of times (since SPX was loaded) that SPX was forced to discard an inbound SPXEstablishConnection packet because SPX lacked a corresponding SPXListenForConnection ECB.
Watchdog Destroy Session : This field indicates the number of times (since SPX was loaded) that the watchdog process destroyed a connection because the connection was no longer valid.
Shell Requests Count : This field indicates the number of times that the shell has made requests to a file server.
Operator Aborts Count : This field indicates the number of times that the user has aborted the shell-server connection by entering "A" in reply to a "Network Error" message.
Number Of Op. Retries : This field indicates the number of times that the user has instructed the shell to retry an operation.
Number of Time Outs cnt : This field indicates the number of times that the shell has sent a request to a server and then timed out without receiveing a reply. (Normally, the shell sends another request packet.)
Write Error Count : This field indicates the number of times that the driver has been unable to send a request to a file server (after repeated retries). In this case, the shell displays the message "Error writing to network" on the workstation screen. The shell does not increment this counter if, after repeated retries, the driver is able to send the request.
Invalid Reply Header Cnt : This field indicates the number of times that the shell has received a reply packet header whose checksum field was -1 or whose PACKET TYPE field indicated that the packet was not a file server reply.
Invalid Slot Count : This field indicates the number of times that the shell has received a file server reply packet specifying an incorrect connection ID.
Invalid Sequence Number Cnt : This field indicates the number of times that the shell has received a file server reply packet specifying an incorrect sequence number. This usually indicates that the reply was unnecessary.
Error Receiving Count : This field indicates the number of times that IPX has indicated an error even though a packet was received on the socket. This usually indicates an "Overrun" error.
No Router Found Count : This field indicates the number of times that the shell has tried and failed to find a route to a destination node. The shell attempts to reroute a packet when a connection seems to fail and the user requests a "retry".
Being Processed Count : This field indicates the number of times that the shell has received a "being processed" reply from a file server. A file server sends this reply to a shell when the server, while processing the shell's request, receives duplicate requests from the shell for the same service.
Unknown Error Count : This field indicates the number of times that the shell has received a packet containing an undefined error value.
Conn./add. Mismatch Count : This field indicates the number of times that the shell has received an error code from a server indicating that the connection number in one of the shell's request packets did not match the shell's connection number/network address relationship recorded in the server's tables. This usually occurs when the server goes down or when the console operator issues a "clear station" command at the server.
Network Gone Count : This field indicates the number of times that the shell has received a packet from a file server indicating the target network has gone away. Only a 68000 file server can generate this kind of packet.
Allocate Cannot Find Route : This field indicates the number of times that the shell, asked by an application to establish a connection with a file server, could not find a route to the destination network.
Allocate No Slots Available : This field indicates the number of times that the shell, asked by an application to establish a connection with a file server, could not establish the connection because the file server's connection table was full.
Allocate Server Is Down : This field indicates the number of times that the shell, asked by an application to establish a connection with a file server, could not establish the connection because the target file server was down.
NOTE: All of these counts begin once the shell is loaded.
The following options are available from this menu:
Connection ID Table : This option will display the Connection ID table. Each screen represents one entry in the Connection Information Table. Use PAGE UP or UP Arrow and PAGE DOWN or DOWN Arrow to scroll through the eight pages.
IPX Statistics : This option presents a sceen displaying the IPX statistics returned by the selected node's diagnostic responder.
LAN Driver Stats : This option presents a screen displaying the LAN Driver Statistics returned by the selected node's diagnostic responder.
Shell Driver Statistics : This option presents a screen displaying the Shell Driver Statistics returned by the selected node's diagnostic responder.
SPX Statistics : This option presents a screen displaying the LAN Driver Statistics returned by the selected node's diagnostic responder.
Workstation Information: This option presents a screen displaying the Workstation information returned by the selected node's diagnostic responder.
NOTE: All of the statistics presented here are a "snap shot" of the corresponding counters at the moment the option was selected. The counters are NOT dynamic and will not increment while viewing the screen. To see an update of the counters, exit the display screen and select the option again. W
NOTE: All of these counts apply since the last reset or initialization of the LAN adapter board!!
Total Tx Packet Count : This field specifies the number of packets the driver has successfully transmitted.
Total Rx Packet Count : This field specifies the number of packets the driver has successfullly received and passed into the system.
No ECB Available Count : This field specifies the number of packets the driver has received for which there was no listening ECB. (This count will increment when general broadcasts are received, etc.)
Packet Tx Too Big Count : This field specifies the number of times that applications have asked the driver to send a packet that is over the maximum legal size.
(This field is not always used. May be set to 65535, and never changes.)
Packet Tx Too Small Count : This field specifies the number of times that applications have asked the driver to send a packet that is under the minimum legal size.
(This field is not always used. May be set to 65535, and never changes.)
Packet Rx Overflow Count : This field specifies the number of times that the driver has received a packet larger than the buffer space allocated for the packet.
Packet Rx Too Big Count : This field specifies the number of times that the driver has received a packet that is over the maximum legal size.
Packet Rx Too Small Count : This field specifies the number of times that the driver has received a packet that is under the minimum legal size.
(This field is not always used. May be set to 65535, and never changes.)
Packet Tx Misc Error Count : This field specifies the number of miscellaneous errors that have prevented the driver from transmitting a packet.
Packet Rx Misc Error Count : This field specifies the number of miscellaneous errors that have prevented the driver from receiving a packet.
Retry Tx Count : This field specifies the number of times that the driver resent a packet. For example, when the driver detects a collision, the driver resends a packet.
Checksum Error Count : Specifies the number of checksum errors that have occurred while receiving packets.
Hardware Rx Mismatch Count : This field specifies the number of times that the hardware has received more or fewer bytes than expected.
LAN Board Settings : This field specifies the text string returned from the selected node's driver identifying the LAN boards current configuration settings.
Operating System : This field identifies the operating system loaded at the selected node.
Network Address : This field identifies the address of the local network where the shell resides.
Local Node Address : This field identifies the node address of the LAN board installed in the station where the shell resides.
Local Socket : This is the local socket the selected node's shell uses to communicate with the server.
Shell Version : This field indicates the major and minor version numbers of the target workstation's shell.qg
DMA Is Used : These fields indicate whether the value in the following DMA Line field is valid. The following values can appear in a DMA Is Used field:
0x00 -No DMA line defined.
0xFF -DMA line defined for exclusive use.
0xFE -DMA line defined for a particular LAN board but
can be shared by others of the same type.
DMA Line : This field returns the value of the DMA line used by the LAN board. Zeros returned in teh second DMA Line field indicate that the LAN board does not use the field.
Text Description : This field returns a text string that summarizes the configuration information contained in the preceding fields. (l
Memory Addresses : Each of these fields identify the address of a block of memory address space to be decoded by the LAN board. The block is divided into one or more 16-byte paragraphs. Zeros returned in the second memory Address field indicate that the driver is not using the field.
Decode Range : These fields following the memory address fields indicate the number of paragraphs in the block.
Interrupt Is Used : This field indicates whether the value in the folling interrupt LIne field is valid. The following values can appear in an Interrupt Is Used Field:
0x00 -No interrupt line defined.
0xFF -Interrupt line defined for exclusive use.
0xFE -Interrupt line defined for a particular LAN
board but can be shared by others of the same
type.
Interrupt Line : Returns the value of the interrupt used by the board.
LAN Hardware ID : This field returns the hard-coded ID that uniquely identifies the LAN hardware. The OEM/Driver Support Group Manager at Novell assigns this ID.
Transport Time : This field returns a value indicating the speed of the LAN associated with the target driver and board. Time is measured in units of 1/18 of a second and rounded to the next highest 1/18. (e.g. a value of 1 represents 1/18 of a second).
Major & Minor Ver. : These fields return the major and minor versions of the driver release.
LAN Description : This text string lists the LAN hardware supported by the driver.
I/O Addresses : These fields indicate the address of a block of I/O addresses to be decoded by the LAN board. Zeros returned in the second I/O address field indicate that the driver is not using that block.
LAN Configuration
NetWork Address : This field indicates teh 4-Byte network address of the LAN on which the driver communicates.
Node Address : This field returns the 6-byte node address of the LAN board installed in the workstation.
Node Address Type : The following values are defined:
00 -The driver dynamically reads and records the node address by calling DriverInitialize.
01 -The developer hard codes the node address in the driver code Master Configuration Table.
02 -A configuration utility assigns the node address.
Maximum Data Size : This field indicates the maximum size of an NCP packet's data portion for the target driver. The data portion's maximum size is always 64 bytes less than the packet size advertised with the LAN board.
(.txt)