HP NetServer AA 4000, Руководство пользователя

Страница: 264 / 386

Chapter 13 MtcMon Messages
254
IOPn.MtcMon status: IOPx could not be joined because Interconnect ESIy is unavailable.
Variables x – the ID of the IOP that could not be joined
y – the ID of the Endurance System Interconnect (ESI) that is unavailable
Severity Warning
Description This message is generated during IOP join if an Interconnect between the joining IOP and an
active CE is faulted. IOP joining is terminated and is not retried until the specified Interconnect
is enabled.
Related Messages
IOP n .MtcMon status: ESI x is faulted and requires repair.
IOP n .MtcMon status: The join process has failed for IOP x .
Hardware/Software This message is generated when an Interconnect is faulted due to a hardware failure.
Action • Examine the event logs to determine the reason that the specified ESI was set to faulted.
• When the condition is repaired, issue the ESI Enable Operation command. The faulted
state of the ESI is cleared, and the specified IOP automatically rejoins the Endurance
server.
IOPn.MtcMon status: IOPx could not be shut down or disabled because it is the only active IOP, and one or more CEs
are active. Shut down the Windows NT operating system on the CEs first.
Variables x – the ID of the IOP that could not be shut down or disabled
Severity Warning
Description This message is generated in response to an IOP Disable Operation or IOP Shutdown
command when the IOP specified is the only one active, and the CE is running the Windows
NT operating system but the user did not specify Operator Override. The IOP is not removed
from service.
Hardware/Software This message is generated as a result of a software condition.
Action Marathon does not recommend that the IOP be removed in this manner while the CE is running
the Windows NT operating system. File corruption is possible. Instead, shut down Windows
NT on the CE first, and then disable or shut down the IOP. Optionally, you can specify the
Operator Override option to force the IOP removal. Note, however, that this causes
Windows NT on the CE to be terminated abnormally.