Juniper NFX250 - Allocating Resources for a VNF; Specifying CPU for VNF

•
To launch a VNF using an XML descriptor file:
user@jdm# set virtual-network-functions vnf-name init-descriptor file-path
user@jdm# commit
•
To launch a VNF using an image:
user@jdm# set virtual-network-functions vnf-name image file-path
user@jdm# commit
•
To specify a UUID for the VNF:
user@jdm# set virtual-network-functions vnf-name [uuid vnf-uuid]
uuid is an optional parameter, and it is recommended to allow the system to allocate
a UUID for the VNF.
NOTE: You cannot change the init-descriptor or image configuration after
saving and committing the init-descriptor and image configuration. To change
the init-descriptor or image for a VNF, you must delete and create a VNF
again.
Allocating Resources for a VNF
This topic covers the process of allocating various resources to a VNF.
•
Specifying CPU for VNF on page 109
•
Allocating Memory for a VNF on page 110
•
Configuring VNF Storage Devices on page 110
•
Configuring VNF Interfaces and VLANs on page 111
Specifying CPU for VNF
To specify the number of virtual CPUs that are required for a VNF, type the following
command:
user@jdm# set virtual-network-functions vnf-name virtual-cpu count 1-4
To pin a virtual CPU to a physical CPU, type the following command:
user@jdm# set virtual-network-functions vnf-name virtual-cpu vcpu-number physical-cpu
pcpu-number
The physical CPU number can either be a number or a range. By default, a VNF is allocated
with one virtual CPU that is not pinned to any physical CPU.
NOTE: You cannot change the CPU configuration of a VNF when the VNF is
in running state. Restart the VNF for changes to take effect.
109Copyright © 2017, Juniper Networks, Inc.
Chapter 5: Virtual Network Functions