cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why AWS EC2 instance not detected correctly by FNP library, it was detected as UNKNOWNVM

Why AWS EC2 instance not detected correctly by FNP library, it was detected as UNKNOWNVM

Question

Why AWS EC2 instance not detected correctly when we run lmvminfo.exe -long, getting UNKNOWNVM

--------------------
Virtual Machine Information
===========================
Hypervisor Detected: True
Running on Virtual Platform
FAMILY=UNKNOWNVM
NAME=UNKNOWNVM
UUID: ERROR - Unavailable.
GENID: ERROR - Unavailable.

Error: Failed to access virtual machine information

-----------------

Answer

Try to check what Instance Metadata Service (IMDS) version is used by the EC2 instance. If the ‘IMDSv2’ setting is configured in AWS then this is not currently supported by FNP instance detection so try to use ‘IMDSv1’ to detect the instance correctly. 

Note: Our Engineering team is working on IMDSv2 currently and we will keep you updated.  Also, read more about Use IMDSv2

Update On 31/Jan/2023: 

AWS EC2 IMDSv2 detection capability has been added to FNP and is planned for release from FNP 11.19.3.0 (2023 R1).
Labels (6)
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Jan 31, 2023 03:00 AM
Updated by:
Contributors