Support Center > Search Results > SecureKnowledge Details
Maintenance mode for Azure, AWS and Google Cloud Platform (GCP) Technical Level
Solution

Overview

The Maintenance Mode boot option is known on UNIX systems as 'single-user mode'.
In this mode, a Virtual Machine (VM) boots to run level 1 the local file systems will be mounted, but the network will not be activated. 
 
This article explains how to:
  • Enter maintenance mode in Azure.
  • Enter maintenance mode in AWS(Amazon Web Services).
  • Enter maintenance mode in GCP (Google Cloud Platform).

Configuration

Enter maintenance using administrator credentials

Starting the following images, you can connect to Maintenance Mode from the Serial Console by using the administrator user and password. For older versions, see the instructions below (grub.conf):

Version/Platform AWS Gateway AWS Management Azure Gateway Azure Management
R81.10 R81.10-335.1101 R81.10-335.1096 R81.10-335.1108 R81.10-335.1108
R81 R81-392.1096 R81-392.1096 R81-392.1108 R81-392.1108
R80.40 R80.40-294.1096 R80.40-200.1096 R80.40-294.1108 R80.40-294.1108
R80.30 R80.30-273.1108


How to enter maintenance mode (grub.conf)

  1. Connect to the VM (with SSH client or serial console).
  2. Back up /boot/grub/grub.conf
    1. Run: cp /boot/grub/grub.conf /boot/grub/grub.conf.backup
  3. Copy grub.conf from GitHub and place it in /boot/grub/
  4. Reboot the VM.
  5. After it boots, click on Serial Console to enter maintenance mode.

How to return to normal mode (grub.conf)

  1. Connect to the serial console.
  2. Rename the backup file as grub.conf
    1. Run: mv /boot/grub/grub.conf.backup /boot/grub/grub.conf
  3. Reboot the VM.
  4. After the boot, your VM is in normal mode.

How to connect to Serial Console

Azure Serial console:

GCP Serial console:

AWS Serial console:

Show / Hide this section

1. Navigate to EC2 Dashboard -> Account attributed –> EC2 Serial Console:

2. Click on Manage - > Launch checkbox “Allow”:

3. Navigate to "Instances" and right click on required EC2 instance.
4. Chose "Monitor and Troubleshooting" -> EC2 Serial Console:

5. Click Connect:

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment