Configuration Services

Node Manager software may be used to configure a node. Configuration refers to the setting of various interface card and driver parameters that govern a node's behavior, as well as maintaining special data in software directories and files.

For example, a node may be configured into one or more modes for receiving and accepting packets from the LAN. These Packet Filter Modes (Individual, Multicast, Broadcast, and Promiscuous) are described later.

In addition, a node's Station Address and Download Server Station Address stored on the LANIC card may be temporarily or permanently altered.

Other items configurable include the node's Retry Limit, and whether or not to save and log •bad" or •trace" packets. These and others will be discussed in detail later in this manual.

Statistical Services

Node Manager software may be used to access and provide a number of useful statistics of node performance. These include, for example, •Good Bytes" transmitted, •Good Packets" transmitted, transmission errors, receiving errors, collisions, and packets discarded. In addition, the statistical counters may be reset. A complete list of statistical data available and how to retrieve it (local and remote nodes) are provided later in this manual.

Diagnostic Services

Node Manager software can be used for limited diagnostics of the local node, and of a remote node if communications to the remote Node Manager software remains intact.

For example, you can initiate an interface card self"test that checks card hardware and firmware operation. For the integrity of the connection between the interface card and LAN coaxial cable, you can initiate an External Loopback test. In addition, special IEEE 802.3 packets (TEST, and XID packets) may be transmitted to remote nodes, where they are processed and returned.

Finally, Node Manager software can check for the existence of applicable files and directories of both local and remote nodes.

Event Logging Services

On occasion, received packets cannot be delivered to an intended program (•orphan" packets), or do not meet IEEE 802.2/802.3 criteria (•bad" packets). Or, it may be desirable to track unsuccessfully transmitted packets (•trace" packets). When a node is properly configured, the Node Manager software will log key information from these packets to an Event Log file saved on disk. This information may be accessed through Node Manager software for examination and analysis. Further details of this feature are provided later.

1%6 Introduction