Support Support Downloads Knowledge Base Juniper Support Portal 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

[MX/PTX] Minor alarm: 'VMHost RE x Disk y Size Incorrect'

0

0

Article ID: KB36009 KB Last Updated: 02 Jul 2020Version: 1.0
Summary:

This article explains the meaning of the alarm, 'VMHost RE x Disk y Size Incorrect', and indicates if any actions need to be taken:

Symptoms:
Alarm seen on the device:
XX@XXXX> show chassis alarms
1 alarms currently active
Alarm time               Class  Description
2019-05-17 12:32:54 UTC  Minor  VMHost RE 0 Disk 1 Size Incorrect

This minor alarm appears when the size of the disks [Disk 0 and Disk 1] present in the Routing Engine is not appropriate for the platform.

Solution:

In the Minor alarm 'VMHost RE x Disk y Size Incorrect', x–0 for RE0 and 1 for RE1, y–1 for disk 1 and 2 for disk 2.

To clear the alarm, insert a disk of the right size and reboot the Routing Engine with the help of the below command.

request vmhost reboot

Then perform a Disk Recovery using the VM Host Snapshot after performing the reboot:

If the state of the primary disk (disk1) is good and the backup disk (disk2) has to be recovered then use the request vmhost snapshot command to recover the backup disk assuming the Routing Engine 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 partition option in the command i.e. request vmhost snapshot partition.

If the state of the backup disk (disk2) is good and the primary disk (disk1) has to be recovered then use the request vmhost snapshot recovery command to recover the primary disk assuming 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 partition option in the command i.e. request vmhost snapshot recovery partition.

To boot from the desired disk, execute the command: request vmhost reboot {disk1, disk2}

In case the issue persists after the above steps, contact JTAC 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