07-18-2025 02:31 AM - edited 07-18-2025 03:51 AM
Hello, everyone.
I am studying virtualization for my ENCOR exam and I have some questions regarding the NFVI Framework Architecture
Credit: NetworkLessons.com
I understand that the VNF/NFV (I'll use both interchangeably) runs on some sort of server and connects to the network which is basically the bottom part of the framework (NFVI) - all the hardware and software that it runs on.
I am a bit unsure about what my book says regarding VIM
The NFVI Virtualized Infrastructure Manager (VIM) is responsible for managing and controlling the NFVI hardware resources (compute, storage, and network) and the virtual- ized resources. It is also responsible for the collection of performance measurements and fault information. In addition, it performs lifecycle management (setup, maintenance, and teardown) of all NFVI resources
Is VIM considered the hypervisor here or does it run on top of a hypervisor or how should I view it? Because hypervisors allocate and manage resources of the VMs, or not?
Also, my other resource states that both the VIM and the VNF Manager (VNFM) perform lifecycle management
So do they both just perform the same function or do they split it somehow?
Thank you
David
Solved! Go to Solution.
07-18-2025 02:53 AM
Hello David,
No, the VIM is not an hypervisor; rather, it’s a higher‑level managment layer that orchestrate one or more hypervisors (like KVM, ESXi, Xen) to control NFVI resources. VIM sits above the hypervisor, using its APIs to provision and manage VMs, storage, and networking across infrastructure, collect metrics and faults, and expose interfaces to higher MANO components like VNFM and NFVO...
As concerned VNFM and VIM, I have this basic example:
The VNFM asks: I need a new router VNF running. Please give me 2 vCPUs, 4 GB RAM, and network interface on VLAN 100.
The VIM respond: Sure. Spinning up a VM with those specs now. It’s ready—install your app.
07-18-2025 02:53 AM
Hello David,
No, the VIM is not an hypervisor; rather, it’s a higher‑level managment layer that orchestrate one or more hypervisors (like KVM, ESXi, Xen) to control NFVI resources. VIM sits above the hypervisor, using its APIs to provision and manage VMs, storage, and networking across infrastructure, collect metrics and faults, and expose interfaces to higher MANO components like VNFM and NFVO...
As concerned VNFM and VIM, I have this basic example:
The VNFM asks: I need a new router VNF running. Please give me 2 vCPUs, 4 GB RAM, and network interface on VLAN 100.
The VIM respond: Sure. Spinning up a VM with those specs now. It’s ready—install your app.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide