Boot FailuresMicro-CS Installation Guide4-7The error count pinpoints the error that caused the boot failure. Forexample, if the boot failed during a Read Request due to excessiveExpedited Remote Procedure Call (ERPC) layer errors, the Errors fromLast ERPC Layer Invocation lists only errors that occurred during thefailed Read Request. The report does not list errors that occurred duringany other Read Request or during the Open Request.The Open Request and the Read Request layers communicate with theblock file server (BFS) on the host. The ERPC layer resides below theOpen Request and the Read Request layers. It is responsible for sending agiven message to a specific host UDP port and for receiving the correctresponse to that message from the port.Table 4-5 Errors from Last Open RequestARP errorsAddress Resolution Protocol (ARP) errors indicate thatthe Micro-CS is configured to boot from a specifiedhost, but the host would not transmit its Ethernetaddress to the Micro-CS. Possibly, the Micro-CSconfiguration includes the wrong IP encapsulation.ERPC layer errors See Errors from Last ERPC Layer Invocation below.Aborts rx’dThe host’s BFS transmitted an abort in response to theMicro-CS’s Open Request. This often means that therequested file does not exist on that server. Runerpcd -D on the host to obtain more information.Table 4-6 Errors from Last Read RequestMsgs with wrongsizeThe correct host responded to the Read Request, butthe data size is incorrect.ERPC layer errors See Errors from Last ERPC Layer Invocation below.Aborts rx’dThe host’s BFS transmitted an abort in response to theMicro-CS’s Read Request. Run erpcd -D on the hostto obtain more information.