Virtual hardware configuration
Overview
The vCPAA mimics an SR-12 chassis equipped with:
Each vCPAA should be configured as follows, where KVM or VMware is configured as the hypervisor:
Table 3-2: Virtual machine configuration
Parameter |
Supported |
Recommended |
---|---|---|
Memory |
4GB+ |
4GB+ |
Virtual CPUs - mode |
Custom |
Custom |
Virtual CPUs - number |
1 with dual core |
1 with dual core |
Virtual CPUs - pinning |
Required |
Required |
Virtual disks - number |
1 |
1 |
Virtual disks - type |
KVM: QCOW2 image file VMware: OVF image file |
KMV: QCOW2 image file VMware: OVF image file |
Virtual disks - driver |
KVM: virtIO VMware: vmhba |
KMV: virtIO VMware: vmhba |
Virtual NIC - interfaces |
1-5 |
1-5 |
Virtual NIC - type |
KVM: bridge or direct VMware: vSwitch, bridge, or direct |
KVM: bridge or direct VMware: vSwitch |
Virtual NIC - model |
KVM: virtIO VMware: vmnic |
KVM: virtIO VMware: vmnic |
Console serial port |
KVM: physical serial port, or bind to available host TCP port VMware: bind to available host TCP port |
Bind to available host TCP port |
Note: Nokia recommends providing 1 GB of HDD space for each virtual machine, in addition to any HDD space required to run the host OS or hypervisor.
The vCPAA must be shutdown before performing certain tasks on the host, such as increasing or decreasing the amount of virtual CPUs, changing CPU pinning information, increasing or decreasing the VM memory, adding or removing a disk, or adding or removing network interfaces.
The setup process for vCPAA on VMware is user-specific, and may vary depending on your system configuration. For issues that are not resolved by existing resources, contact your Nokia representative for assistance.
© 2022 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.