Fujitsu multipath disk control mechanism asynchronous events (SNMP trap)
When the Agent version of the server node is 1.x
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
One path blocked | Error | MPType access path(MPAccessPath) fault | Refer to the manual for the multipath driver and take required actions. Generally, the connection to storage devices and the cable connections must be checked. |
Failure in detecting a part of paths on server node startup (failure in starting multipath operation) | Warning | Some paths could not be detected | |
A multipath asynchronous event (SNMP trap) was reported to Manager; however, Manager does not manage the corresponding multipath information. (This may occur when Manager was either uninstalled or installed following a server node unit search.) | Error | Multi path(Controler port Target target) fault | Search the server node related to the asynchronous event (SNMP trap). |
"MPType" of the event display is displayed, "MP".
"MPAccessPath" of the event display is displayed, "p2b0t0" etc.
"port" of the event display is displayed, "No.2" etc (SCSI port number).
"target" of the event display is displayed, "ID0" etc (target number).
When the Agent version of the server node is 2.0 and 13.0 or later
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
1 path inhibition | Warning | [MPtype: 403] "Access path (pPbBtT) fault | Refer to the manual for the multipath driver and take required actions. Generally, the connection to storage devices and the cable connections must be checked. |
[MPtype: 1010] "Access path (pPbBtT) fault | |||
Some paths could not be detected at a server node startup. (Multipath operation could not be started.) | Warning | [MPtype: 301] "Access path (pPbBtT) could not be detected. |
"GRMPD" or "MPHD" is displayed under "MPtype" in the event.
"P", "B", and "T" in the event display are variables that are displayed e.g. in the form "p2b0t0".
MPIO asynchronous events (SNMP trap)
The events of msdsm (the multi path driver that is built into Windows operating system since Windows Server 2008 by the standard) are reported as MPIO events. When the multi path driver that is compliant to MPIO is used, e.g. Fujitsu ETERNUS multipath driver, these events may be reported.
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
Path inhibition | Warning | [MPIO:16] Access path fault. | Path switching has occurred. |
Path switching was failed | Warning | [MPIO:32] Fail-over failed. | Path switching has occurred, but it has been failed. |
Event reporting a changed host name
Manager uses the host name to identify each of the server nodes. However, in cases where server nodes cannot be identified correctly after their host name has changed, the following event is output:
Event | Level | Event display | Troubleshooting |
|---|---|---|---|
The host name of a server node has changed | Warning | hostname of server node (IPaddress) has been changed from Server-A to Server-B | The hostname for the server having the IP address indicated in the event display has been changed to Server-B. Reset the hostname to Server-A. To do so, edit %WINDIR%system32\drivers\etc\hosts file, which contains the definitions of the hostnames. |
The "IPaddress" indicated in the event display is the IP address of the corresponding server node.
"Server-A" is the name set to which the corresponding server node was originally set.
"Server-B" is the name to which the corresponding server node is currently set.
