Shadow MUF doesn't take over after an LPAR failure

Products

• Datacom
• DATACOM - AD
• Datacom/AD
• Datacom/DB

Issue/Introduction

In the case of an EOJ to the Primary MUF, the Shadow MUF is notified via XCF that it should take over in an orderly fashion.

In the case of an abend (for instance a program check) of the Primary MUF, XCF immediately notifies the Shadow MUF of the fact that the Primary MUF has left the common XCF group, and thus the Shadow MUF should take over.

However, in case of a hardware failure of the LPAR where the Primary MUF is running, XCF itself may be affected by the crash and be unable to notify the Shadow that the Primary MUF has terminated.

 

 

 

 

Cause

Automatic notification to Shadow may occur only when the affected LPAR is re-IPLed, and XCF is able to process pending cleanup and notifications.

Resolution

In the case of a hardware failure, manual intervention is required to force takeover by the Shadow MUF, using the console command: ALTER_SHADOW_TO_TAKE_OVER.