Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Minor Alarm:"VMHost RE x Disk y Wrong Slot"

0

0

Article ID: KB36006 KB Last Updated: 07 Jul 2020Version: 1.0
Summary:

This article explains the meaning of the minor alarm "VMHost RE x Disk y Wrong Slot" that is seen on MX and PTX devices, and indicates if any actions need to be taken to clear the alarm.

 

Symptoms:
The following alarm might be seen on the MX/PTX device: 
xx@xxxx> show system alarms
4 alarms currently active
Alarm time               Class  Description
2020-05-12 14:40:17 UTC  Minor  VMHost RE 0 Disk 2 Wrong Slot
2020-05-12 14:40:17 UTC  Minor  VMHost RE 0 Disk 1 Wrong Slot

 

Cause:

The above minor alarms are caused when both disks (Disk 1 and Disk 2) of a Routing Engine are swapped from their positions. The alarms also may occur when a ​pre-labeled disk is inserted in a wrong slot. These are usually transient.

In alarm VMHost RE x Disk y Wrong Slot:

  • For X, there are two options for an alarm to occur: 0 for RE 0 and 1 for RE 1.

  • For Y, there are two options for an alarm to occur with X: 1 for Disk 1 and 2 for Disk 2.

 

Solution:

To clear the alarm, perform the following steps:

  1. If both disks (Disk 1 and Disk 2) are present in the wrong slot in the Routing Engine, swap the disks manually and reboot the Routing Engine by using the following command in order to clear the alarm.

> request vmhost reboot
  1. If only one disk is in the wrong slot, recover the disk via snapshot after booting from a healthy disk.

The snapshot feature enables you to create copies of the currently running and active file system partitions on a device.

On the device, you can back up the snapshot of the host OS image along with the Junos OS image. You can use the request vmhost snapshot command to create a VM host recovery snapshot on the backup disk.

  • If the slot of the primary disk (disk1) is correct and the backup disk (disk2) is in the wrong slot and has to be recovered, then use the request vmhost snapshot command to recover the backup disk, assuming that the RE is booted from the primary disk.

  • If the state of the secondary disk is not known or the file systems in the disk are not in a consistent state, then include a partition option in the command; that is, use request vmhost snapshot partition.

  • If the state of the backup disk (disk2) is correct and the primary disk (disk1) is in the wrong slot and has to be recovered, then use the request vmhost snapshot recovery command to recover the primary disk, assuming that the Routing Engine is booted from the backup disk.

  • If the state of the primary disk is not known or the partition tables are in bad condition, then include the partition option in the command; that is, use request vmhost snapshot recovery partition.

If the alarm does not clear after performing the above steps, contact Support for further investigation.

 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search