Deployment in a VM

Description

The requirements and restrictions below apply to NFM-P component deployment in a virtual machine, or VM. VM deployment is supported in the following environments:

• KVM

• Openstack

• VMware

Note: The requirements and restrictions in NFM-P deployment requirements also apply to VM deployments.

Note: Before you deploy an NFM-P component in a VMware VM, you must install the latest VMware Tools software.

See the NSP Planning Guide for the hardware virtualization requirements, and for the specific configuration requirements of a supported environment.

VM deployment using disk images

You can use disk images to deploy the following in a KVM or RHEL OpenStack environment:

• RHEL OS, for subsequent NFM-P component installation; see Introduction

• NFM-P system; see Using an NFM-P disk image

NFM-P server and database virtualization

The following conditions apply to main server, auxiliary server, client delegate server, or database deployments in VMs.

• The guest OS must be a supported version of RHEL, as specified in the NSP Planning Guide.

• RHEL deployment on VMware requires VMXNET 3 NIC adapters; see the VMware documentation for information.

Client virtualization

The following conditions apply to NFM-P single-user GUI client deployment in a VM.

• You can deploy a VM client in a live network environment only if the client resources are dedicated to the guest OS, and not shared or oversubscribed.

• The guest OS must be a supported OS version; see the NSP Planning Guide.

• The supported connection application for a VMware ESXi Windows platform is Windows Remote Desktop.

Additional EMS requirements and restrictions

The following conditions apply to an NFM-P single-user GUI client or client delegate server in a VM that requires the installation of an additional element manager on the same platform, or is to use an additional NE management interface.

• You can use two or more NICs to isolate network traffic between the client VM and the managed NEs. Such a configuration may be required when an additional element manager, for example, NEtO, must share the client resources, or when web-based NE management is to be performed from the client station.

• Additional RAM, disk space, and CPU resources are required to accommodate an element manager that shares a client platform; see the NSP Planning Guide.