Platform Node Stuck at GRUB Menu After Executing Shutdown Script

Products

• VCF Operations for Networks

Issue/Introduction

After executing the shutdown script process per KB 314428, Platform Node 1 fails to boot and becomes stuck at the GRUB menu. The system prompts for a username and password, but immediately returns to the GRUB prompt loop upon entering standard support credentials. Platform Nodes 2 and 3 may boot successfully but cannot initialize properly if Node 1 remains offline.

Powered off snapshots were not taken before executing booting the platform node back up, so there are no back ups to revert to. 

Environment

Aria Operations for Networks 6.14.x

Cause

The boot sequence is interrupted at the GRUB bootloader when standard support or default Ubuntu credentials are used to authenticate following a shutdown script execution.

Resolution

1. If KB 314428 is followed correctly, powered off snapshots should be taken after executing the shutdown script. The correct process is to revert to these snapshots if nodes fail to boot properly after executing the shutdown script. 
2. If powered off snapshots are not taken and platform node 1 is not booting past GRUB: 
   1. Try using your support and consoleuser account credentials. 
   2. If support and consoleuser fail to get past the GRUB menu, you will need to open a support case with Broadcom to have an engineer enter internal credentials on the node that will bypass the GRUB menu.  
3. After Broadcom support enters credentials to bypass the GRUB menu, proceed with following KB 314428 to boot up the rest of the platform and collector nodes. 

Note: It is normal for there to be processing lag after platform nodes have been powered off for extended periods of time. Monitor the platform node(s) for 24 hours after the platform nodes are back online.