Managing VNFs on NFX350 Devices

Managing VNF States

By default, a VNF automatically starts when the VNF configuration is committed.

To disable autostart of a VNF when the VNF configuration is committed:

To manually start a VNF:

To stop a VNF:

To restart a VNF:

To access the console of an active VNF:
Note:
The request virtual-network-functions vnf-name console command is supported only for root login over ssh.

To access a VNF through SSH:

To access a VNF through Telnet:

Managing VNF MAC Addresses

VNF interfaces that are defined, either using the CLI, are assigned a globally unique and persistent MAC address. A common pool of 176 MAC addresses is used to assign MAC addresses to VNF interfaces. These MAC addresses are automatically allocated when a VNF is instantiated. You can configure a MAC address other than what is available in the common pool, and this address will not be overwritten.

To configure a specific MAC address for a VNF interface:

To delete the MAC address configuration of a VNF interface:

Note:

To delete or modify the MAC address of a VNF interface, you must stop the VNF, make the necessary changes, and then restart the VNF.
The MAC address specified for a VNF interface can be either a system MAC address or a user-defined MAC address.
The MAC address specified from the system MAC address pool must be unique for the VNF interfaces.

Managing the MTU of a VNF Interface

The maximum transmission unit (MTU) is the largest data unit that can be forwarded without fragmentation. You can configure either 1500 bytes or 9216 bytes as the MTU size. The default MTU value is 1500 bytes, and the maximum MTU size for both VNF and L3 interface is 9216 bytes.

Note:

MTU configuration is supported only on VLAN interfaces.

To configure the MTU on a VNF interface:
Note:
You must restart the VNF after configuring the MTU, if the VNF does not support hot-plugging functionality.
To delete the MTU of a VNF interface:
Note:
After the MTU is deleted, the MTU of the VNF interface is reset to 1500 bytes.

Note:

The maximum number of VLAN interfaces on the OVS that are supported in the system is 64.

Accessing a VNF from the JCP

You can access a VNF from the JCP through SSH or by using the console.

To access a VNF from the JCP through SSH:

user@host> request virtual-network-functions ssh vnf-name

To access a VNF from the JCP by using the console:

user@host> request virtual-network-functions console vnf-name

Viewing the List of VNFs

To view the list of VNFs:

The Liveliness field of a VNF indicates whether the IP address of the VNF is reachable from the JCP. The default IP address of the liveliness bridge is 192.0.2.1/24.

Displaying the Details of a VNF

To display the details of a VNF:

Deleting a VNF

To delete a VNF:

Note:

The VNF image remains in the disk even after you delete a VNF.

Non-Root User Access for VNF Console

You can use Junos OS to create, modify, or delete VNF on the NFX Series routers.

Junos OS CLI allows the following management operations on VNFs:

Table 1: VNF Management Operations
Operation	CLI
start	`request virtual-network-functions <vnf-name> start`
stop	`request virtual-network-functions <vnf-name> stop`
restart	`request virtual-network-functions <vnf-name> restart`
console access	`request virtual-network-functions <vnf-name> console [force]`
ssh access	`request virtual-network-functions <vnf-name> ssh [user-name <user-name>]`
telnet access	`request virtual-network-functions <vnf-name> ssh [user-name <user-name>]`

The following table lists the user access permissions for the VNF management options:

Table 2: User Access Permissions for VNF Management Operations before Junos OS 24.1R1.
Operation	`root` class user	`super-user` class user	`operator` class user	`read-only` class user
start	command available and works	command available and works	command not available	command not available
stop	command available and works	command available and works	command not available	command not available
restart	command available and works	command available and works	command not available	command not available
console access	command available and works	command available; but not supported	command not available	command not available
ssh access	command available and works	command available; but not supported	command not available	command not available
telnet access	command available and works	command available; but not supported	command not available	command not available

Starting In Junos OS 24.1R1, Junos OS CLI allows the management operations on VNFs for a non-root user.

A new Junos OS user permission, vnf-operation allows the request virtual-network-functions CLI hierarchy available to Junos OS users that do not belong to the root and the super-user class.

You can add the user permission to a custom user class using the statement vnf-operation at [edit system login class custom-user permissions]

The following table lists the VNF management options available for a user belonging to a custom Junos OS user class with vnf-operation permission.

Table 3: User Access Permissions for VNF Management Operations after Junos OS 24.1R1.
Operation	`root` user	`super-user` class user	User of a custom Junos OS user class with `vnf-operation` permission
start	command available and works	command available and works	command available and works
stop	command available and works	command available and works	command available and works
restart	command available and works	command available and works	command available and works
console access	command available and works	command available and works	command available and works
ssh access	command available and works	command available and works	command available and works

Accessing the VNF Console
Exiting the VNF Console

Accessing the VNF Console

Starting in Junos OS 24.1R1, the following message is displayed when you access the console initially:

The messages Trying 192.168.1.1... and Connected to 192.168.1.1. come from telnet client that is launched using the Junos OS CLI command request virtual-network-functions <vnf-name> console.

Note:

The IP addresses present in the message cannot be replaced with the name of the VNF.

Exiting the VNF Console

Starting in Junos OS 24.1R1, when the user uses the escape sequence ^] the console session terminates, and the telnet command prompt is displayed to the user.

You must enter quit or close or you must enter qor c to exit from the terminal command prompt and return to Junos OS command prompt.

ON THIS PAGE

Managing VNF States

Managing VNF MAC Addresses

Managing the MTU of a VNF Interface

Accessing a VNF from the JCP

Viewing the List of VNFs

Displaying the Details of a VNF

Deleting a VNF

Non-Root User Access for VNF Console

Accessing the VNF Console

Exiting the VNF Console