Select the type of nodes to view, or run point to point tests.
Workstations:
View a list of workstations by address. You may select an address from the list and view statistics for that workstation.
Users:
View a list of server/user names to select from. This is the same as the list of workstations, however the primary server/user name is shown instead of the address.
Servers:
View a list of servers (by name). You may select from that list and view statistics for that server.
(PGDN for more)
Bridges:
View a list of bridges (internal and external). External bridges are shown as the address only, Internal bridges are shown as the address and the server name.
Point To Point:
This selection shown a list of all nodes on the network. You may select a source and a destination node for a point to point test. When you have selected the nodes that will participate in the test you will be prompted for test parameters. This selection can be useful in finding network problems.
Network Managment:
This option allows you to create or view the database of nodes. You may add your own notes to each node record. You can also cause a re-scan of the network to rebuild the list of active nodes.
Select the workstation address you wish to view statistics for. If you want to see a list of users you may select the user option from the main menu, or select the address here and choose the login info option.
This is a list of each server/user that is logged in at the workstation. If a workstation is not logged in to a primary server the user is shown as "NOT LOGGED IN". If the user name is not available it is shown as "???". In order to get the user name for a given server you must be attached to that server and have rights to scan the bindery for the user names.
The IPX (Internetwork Packet Exchange protocol) statistics for the selected node are shown here.
Total Packets Sent:
This is the total number of packets that have been sent
since IPX was loaded. Since this program is sending
and receiving packets from this node it will always be
changing.
Malformed ECB's:
This is the number of incorrectly formed ECB's that
were passed to IPX from applications. This number
will normally be zero.
Get ECB Requests:
The number of times that the nodes driver has given an
incomming packet to IPX.
(PGDN for more)
Get ECB Failures:
The number of times that IPX has been unable to supply
an ECB (event control block) for an incomming packet.
AES Events:
The number of times IPX has used the AES (Asynchrous
Event Scheduler)
AES Events Postponed:
The number of times IPX has been unable to service an
AES event on time. This would occur because IPX was
busy with something else.
MAX Configured Sockets:
The number of allowed open at one time. (Configured
through SHELL.CFG)
(PGDN for more)c
MAX Open Sockets:
The maximum number of sockets opened at one time.
Open Socket Failures:
The total number of times that applications have failed
to open a socket (because it was already open or the
maximum number had been reached)
Listen ECB Count:
The number of times that applications have given IPX a
Listen ECB.
ECB Cancel Failures:
The number of times IPX has been unable to cancel an
ECB. This usually happens when the cancel request is
too late.
(PGDN for more)
Find Route Failures:
The number of times IPX has been unable to
find a route to the specified destination.?
The SPX (Sequenced Packet Exchange) statistics are shown here. All numbers start at zero when SPX is loaded at the target machine. They are being updated once a second.
Max Possible Connections:
The maximum number of SPX connections available at this
node. (Configurable via Shell.cfg)
Max Open Connections:
The maximum number of connections open at one time since
SPX was loaded.
Establish Connection Requests:
The number of connection establish requests issued at
this node.
<PGDN for more>
Establish Connection Failures:
The number of establish requests that failed because the
SPX packet header was too small, the maximum number of
connections had been reached, or the target machine
could not be found.
Listen Requests:
The number of times SPX was called to listen for a
connection request from another machine.
Listen Failures:
The number of times a Listen Request failed because the
maximum number of connections had been reached.
Send Packet Count:
The number of times SPX was called to send a packet.
<PGDN for more>
No Listen Failures:
The number of sends that failed because the receiving
side was not listening.
Bad Send Request Count:
The number of sends that failed because the connection
ID was wrong or the SPX packet header was incorrect.
Send Failures:
The number of times SPX failed to send a packet and
aborted the connection.
Connection Aborts:
The number of connections that were aborted by the
owner (application program).
<PGDN for more>
Listen Packet Requests:
The number of times SPX has been requested to receive a
packet.
Bad Listen ECBs:
The number of listen requests that were incorrectly
formed, or were for a socket that was not open.
Packets Received:
The number of packets received by SPX.
Bad Packets Received:
The number of packets discarded because the connection
ID was wrong.
Duplicate Packets:
Duplicate packets that were discarded.
<PGDN for more>
No Listen ECBs:
The number of connection requests from other machines
that were rejected because there was not a listening
ECB.
Destroyed Connections:
The number of connections that SPX terminated because
it detected the other machine had died or went away.1
The Netware shell and shell driver configuration information is shown here. This includes IPX/SPX versions, the shell version, the operating system type and version. A machine ID of zero means the computer is an IBM or compatible. The address of this LAN is shown along with a description of the network hardware.
Maximum Data Size: The largest amount of data that can be
transmitted in one packet.
LAN Hardware ID: A number assigned by Novell to identify the
LAN hardware.
Transport Time: The amount of time it takes for one 576 byte
packet to travel from one node on this LAN to another.
Measured in units of 1/18 second.
<PGDN More>
LAN Driver Version: The internal version number of the LAN
Driver. This will differ from the Netware version.
Ethernet Type: This is shown only if this is an ethernet
driver. Only drivers with identical ethernet types
can communicate.p!
The shell driver statistics are shown here. Some of the values may not be used for a particular type of hardware and will always be 65535.
Too Many Hops: The number of packets that were discarded because
they crossed too many bridges (15).
Unknown Network Count: The number of packets discarded because
they were destined for an unknown network address.
No Space For Service: The number of packets discarded because
there was not enough room in the drivers data segment for
the packet.
No Receive Buffer Count: The number of packets discarded because
ther was not enough buffer space for the packet.
<PGDN More>
Transmit Too Big: The number of times that application programs
programs have asked the driver to send a packet that is over
the maximum allowable size.
Transmit Too Small: The number of times that application
programs have asked the driver to send a packet that is under
the minimum allowable size.
Receive Overflow: The number of packets recevied by the driver
driver that were too large for the buffer space allocated
for the packet.
Receive Too Small: The number of packets received by the driver
that have been under the minimum allowable size.
<PGDN More> '
Misc Transmit Errors: The number of miscellaneous errors that
have prevented the driver from transmitting a packet.
Misc Receive Errors: The number of miscellaneous errors that
have prevented the driver from receiving a packet.
Transmit Retries: The number of packets that were resent because
of errors. (Collision detected, etc.)
Checksum Errors: The number of packets rejected because the
checksum of the data was incorrect.
Hardware Mismatch: The number of times that the driver hardware
has received more or fewer bytes than expected.
<PGDN More>
The rest of the statistics shown are defined by the developer of the driver software.
The shell statistics are shown here. This screen is updated once a second. The values here reflect requests made to the Netware shell by applications, or error conditions detected by the shell.
Shell Requests: The number of requests made by the shell to a
file server.
Operator Aborts: The number of times the user has aborted the
shell-server connection by entering 'A' in reply to a
"Network Error" message.
Operator Retries: The number of times the user has instructed the
shell to retry an operation.
Timeouts: the number of times the shell has timed out waiting
for a reply from a server.
<PGDN More>
Write Error Count: The number of times the shell has failed to
send a request to a server (After retries). The shell
displays the message "Error writing to network" on the
screen when this condition occurs.
Invalid Reply Header Count: The number of reply packets received
by the shell that were not of the correct type.
Invalid Slot Count: The number of reply packets received by the
shell that specified an incorrect connection ID.
Invalid Sequence Number Count: The number of packets received by
the shell that specified an incorrect sequence number. This
usually indicated that the reply packet was retried
unnecessarly.
<PGDN More>
Error Receiving Count: The number of times that IPX returned an
error even though a packet was received. This usually
indicates a packet that was too large was received.
No Router Found Count: The number of times that the shell was
unable to find a route to the destination node. The shell
will attempt to reroute a packet when the user specifies
"Retry" to a network error prompt.
Being Processed Count: The number of times a server informed
the shell that a request was being processed. The server
sends this reply when the shell retries requests that the
server is processing.
<PGDN More>
Unknown Error Count: The number of reply packets received by the
shell that contained an unknown error value.
Invalid Server Slot Count: The number of replies received by the
shell that indicated that the connection ID in the shell's
request packet did not match the servers connection ID. This
usually happens when the server goes down or the console
operator issues a "clear station" command at the server.
Network Gone Count: The number of replies received by the shell
from a server that indicated that the target network has
gone away. (Only 68000 servers generate this reply)
Allocate Cannot Find Route Count: The number of times that the
shell could not find a route to a server when requested to
by an application program.
<PGDN More>
Allocate No Slots Available Count: The number of times the shell
could not establish a connection with a server because the
servers connection table was full.
Allocate Server Is Down Count: The number of times the shell
could not establish a connection with a server because the
server was down.g8
You may view the statistics or configuration information for the selected workstation.
Login Info:
Display a list of each server/user that is logged in at the selected workstation.
IPX Statistics:
Display the IPX statistics for the workstation.
SPX Statistics:
Display SPX statistics for the selected workstation.
Shell Configuration:
Show configuration information for the selected workstation. This includes the hardware and software configuration for the machine and the network driver.
(PGDN for more)
Driver Statistics:
Show the network driver statistics for the selected workstation.
Shell Statistics:
Show shell statistics for the selected workstation.
Select a User to view statistics for. The workstation the user is logged at will be selected for viewing. The individual statistics for that workstation may then be selected.
Select a server to view statistics for. When this selection is made you will be able to select IPX, SPX or server statistics for viewing.
Select IPX, SPX, or Server Statistics. Server statistics will allow further selection of specific areas to view.
Select the specific area of server statistics to view. The areas shown are a subset of what is available using FCONSOLE. These statistics are not available for Netware 386 servers.
Server cache statistics are shown here. This screen is updated once a second. For more information on the meaning of these statistics consult your Netware manual. (Look under FCONSOLE)
The server channel statistics are shown here. This information is the same as shown by the Netware FCONSOLE utility.
Server lan IO statistics are shown here. This screen is updated once a second. The information shown here is the same as shown by the Netware FCONSOLE utility.
Server file system statistics are shown here. This screen is updated once a second. The information shown here is the same as shown by the Netware FCONSOLE utility.
Select the bridge to view statistics for. The network address and the server or user name is shown.
Select the type of statistics to view. Bridge driver statistics and configuration will be shown for each of up to 4 networks. 2C
The configuration of the driver for each LAN (up to 4) is shown here. The configuration information is shown only if the LAN is installed. A server is also a bridge even if it has only one LAN. To view the information for each successive LAN press escape.
The address of this LAN is shown along with a description of the network hardware.
Maximum Data Size: The largest amount of data that can be
transmitted in one packet.
LAN Hardware ID: A number assigned by Novell to identify the
LAN hardware.
Transport Time: The amount of time it takes for one 576 byte
packet to travel from one node on this LAN to another.
Measured in units of 1/18 second.
<PGDN More>
LAN Driver Version: The internal version number of the LAN
Driver. This will differ from the Netware version.
Ethernet Type: This is shown only if this is an ethernet
driver. Only drivers with identical ethernet types
can communicate.
The bridge driver statistics are shown here. Each LAN has it's own driver and driver statistics. To view the statistics for each successive LAN press escape. Statistics with a value of 65535 do not apply to this driver.
Total Packets Sent: The number of packets successfully sent since
the last driver reset or initialization.
Version: The internal version number specified by the developer
of the driver.
Total Packets Received: The total number of packets received since
the last driver reset or initialization.
No ECB Available Count: The number of packets received for which
there was no listening ECB (Event Control Block)
<PGDN More>uJ
Transmit Too Big: The number of times that application programs
programs have asked the driver to send a packet that is over
the maximum allowable size.
Transmit Too Small: The number of times that application
programs have asked the driver to send a packet that is under
the minimum allowable size.
Receive Overflow: The number of packets recevied by the driver
driver that were too large for the buffer space allocated
for the packet.
Receive Too Small: The number of packets received by the driver
that have been under the minimum allowable size.
<PGDN More>AM
Misc Transmit Errors: The number of miscellaneous errors that
have prevented the driver from transmitting a packet.
Misc Receive Errors: The number of miscellaneous errors that
have prevented the driver from receiving a packet.
Transmit Retries: The number of packets that were resent because
of errors. (Collision detected, etc.)
Checksum Errors: The number of packets rejected because the
checksum of the data was incorrect.
Hardware Mismatch: The number of times that the driver hardware
has received more or fewer bytes than expected.
<PGDN More>
The rest of the statistics shown are defined by the developer of the driver software.
The statistics shown here reflect packets received and routed by the bridge from all of the installed LANs. For a server that has only one LAN most of these valued will remain zero.
Too Many Hops: The number of packets that were discarded because
they crossed too many bridges (15).
Unknown Network Count: The number of packets discarded because
they were destined for an unknown network address.
No Space For Service: The number of packets discarded because
there was not enough room in the drivers data segment for
the packet.
No Receive Buffer Count: The number of packets discarded because
ther was not enough buffer space for the packet.
<PGDN More>
Propagate Count: The number of Netbios broadcast packets that
that have been received.
Total Packets Serviced: The total number of packets that the
bridge has serviced.
Total Packets Routed: The total number of packets that the bridge
has routed to another network.
Select the source or destination (as specified on the bottom line) for the point to point test. After selecting the nodes you will specify the parameters for the test. When all parameters have been specified the source node will send the specified number of packets to the destination node. The results will show how many packets were received. Note that it is possible to send packets faster than the receiving node can handle them. You may have to play with the values until all packets are received.
Enter the specified option.
Packet Size: This is the size (in bytes) of each packet sent.
Number Of Packets: The total number of
packets to be sent.
Interval: The number of clock tics (1/18 sec) to wait between group of packets.
Packets Per Interval: How many packets to send
before waiting for the Interval.
Packet Change Size: The number of bytes to
change the packet size by for each packet sent.
Select the scan option if you wish to re-scan the network to build a current list of active nodes. Select the print option to send the information to a printer or file. The database option allows you to view or edit the permanent node database.
The results of the point to point tests are shown here. The number of packets received and the number of errors encountered are shown. If an error was encountered getting one of the nodes to respond to the test the SPX error code is shown. The most common is (ed), which means we were unable to establish a SPX connection with one of the nodes.
This option allows you to view the users at each attached server. When a user is selected you are shown the address of the workstation that the user is logged in from. The same user may be logged in at more than one workstation. Once a user is selected you can view the same set of information provided from the workstation option of the main menu.
Select the node you want to view database information for. You will be shown the node configuration information and can append your own notes to the database record. You can also modify the name associated with a given network address.
Database Options
Browse: View database records and edit or view notes.
Update: Compares the database with the
currently active nodes and adds
any new ones.
Report: Generate report information on specified nodes and send output
to a printer or file.
Database View Options
F2: Print the information for this node.
The output will be sent to the device
or file you specify.
F4: Edit the notes for this node. You may enter up to 2000 characters for
each node.
F6: Modify the name associated with this
record. You may enter up to 32
characters for a name.
You may enter up to 2000 characters of information. Press F1 again for a list of editing keys available.
You may enter any text up to 32 characters in length. Press F1 again for a list of edit keys.
(.txt)