Other Initialization Considerations

Entering User Commands

Node Manager commands cannot be processed during initialization, and command entries will time out.

Initialization Errors

Node Manager software initialization errors that occur are returned to the terminal from which initialization originated.

In some cases, an error type and error number (in decimal) are returned. These will correspond to the Node Manager software errors provided in Appendix A. For example, the following message specifies a driver error (type 4) with a •powerfail" error code (1).

NMGR INITIALIZATION ERROR

Error Type = 4

Error Number =

1

Other error messages may also be returned. These messages are generally clear and self"explanatory. For example, when Node Manager software retrieves the MCAST.TXT file for initializing a LANIC card with Multicast Addresses, the following error indicates a corrupt file.

NMGR INITIALIZATION ERROR

Corrupt file: /FILES802/ADDRxxxxxxxxxxxx/MCAST.TXT:::4:2

where:

xxxxxxxxxxxxis the Station Address that identifies the applicable LANIC card. Finally, some messages such as the following should occur only rarely:

NMGR

ABORTED––NO

LUs ARE

AVAILABLE

NMGR

ABORTED––NO

AVAILABLE CLASS NUMBER

NM ABORTED––NO AVAILABLE

CLASS NUMBER

NO AVAILABLE 802.3 LU

(Note: this message pertains to the NM2 Module)

4%16 Node Manager Operations