Enterasys micrommac 22es Manuel De Montage

Chapter 4: Troubleshooting Procedures

Generally, two problems cause boot failures: the Micro-CS is not 
configured properly, or the load server host is not responding. The 
Micro-CS requests a boot either from a pre-defined load host, or by 
broadcasting its boot request. When a host responds, the Micro-CS loads 
its operational code.

The Micro-CS requires setting certain configuration parameters. Enter 
these parameters with ROM Monitor commands for the initial boot 
sequence. See Chapter 3 for more information on these commands.

If the problem is a non-responsive host the boot error report displays that 
information under the Rsp T/O’s: field. This field indicates that the 
Micro-CS timed out while waiting for a response to its boot request; if 
this field is empty, check the Micro-CS’s configuration parameters.

If an error occurs, a boot error report is generated only if the Micro-CS 
has opened the boot file. The report uses the following format:

BOOT ERROR REPORT (for BFS files only)
Boot attempt from host nn.nn.nn.nn:
Errors from Last Open Request:
0 ARP errors 0 ERPC layer errors 0 Aborts rx’d 
Errors from Last Read Request:
0 Msgs w/ wrong size 0 ERPC layer errors 0 Aborts rxd 
Errors from Last ERPC Layer Invocation:
0 H/W errors 1 Msgs from wrong host 0 Rsp T/O’s 0 Msgs of wrong type

The Micro-CS generates a boot error report for the Internet address from 
which it tried and failed to boot. Table 4-5 describes the Errors from Last 
Open Request; Table 4-6 describes the Errors from Last Read Request; 
and Table 4-7 describes the Errors from Last ERPC Layer Invocation.

The Micro-CS generates a boot error report only if it opens the 
boot file and an error occurs during the boot process.

TFTP error reporting complies with the standard, pre-defined 
TFTP error codes.