Supporting Faster File Copy or Transfer
On the NFX series devices with the NFX-3 architecture, a user can log into the vJunos0 through the front panel management port (fxp0) using protocols such as SSH.
The /var/public/ directory accessible inside the vJunos0 is meant for storing image files required for launching and supporting VNFs. The /var/public/ is a directory on the hypervisor that is mounted as a virtFS (virtual file system) inside the vJunos0. A file copy or file transfer operation between external network and vJunos0 through fxp0 interface goes through the virtFS to reach the /var/public/ directory on the Linux hypervisor.
Starting in Junos OS Release 24.2R1, Junos OS allows creating an external network interface directly on the hypervisor and associating an IPv4 address with it. The external network access is through the front panel management interface (out-of-band) or through one of the front panel revenue ports (in-band), depending on the configuration.
NFX series devices support the following types of faster file copy or file transfer:
-
Remote file copy—Use
request vmhost remote-file-copycommand to copy a file directly between the hypervisor and an external fileserver. -
Local file copy of a file on the hypervisor—Use
request vmhost local-file-copycommand to copy a file or a directory present under /var/public/ directory structure on the hypervisor to a different name under /var/public/ directory structure.
Configuring for in-band External Interface
The topology requirement for in-band external interface configuration, irrespective of the type of SKU is a VNF with SR-IOV interface mapped to a front panel port connected to another front panel port on the same device.
For example, on an NFX150 device, you can map the VNF SR-IOV interface to a front panel port (heth-0-x) directly with a cable connecting heth-0-x port to another heth-0-y port on the same device.
On an NFX250 or an NFX350 device, you can map the VNF SR-IOV interface an internal NIC hsxeX and map to a front panel port ge-0/0/X through a VLAN. Connect the ge-0/0/X with a direct cable to another ge-0/0/Y on the same device. Note that ge-0/0/Y and hsxeY are together in a different VLAN.
user@host#set vmhost external-interface in-band mapping interface interface-name user@host#set vmhost external-interface in-band mapping interface virtual-function user@host#set vmhost external-interface in-band family inet address ipv4_inet_address user@host#set vmhost external-interface in-band family inet gateway ipv4_gateway user@host#set vmhost external-interface in-band vlan-id vlan_id
For example, to configure an in-band external interface on an NFX150 device:
user@host#set vmhost external-interface in-band mapping interface heth-0-0 user@host#set vmhost external-interface in-band mapping interface virtual-function user@host#set vmhost external-interface in-band family inet address 10.10.10.10/24 gateway 10.10.10.254 user@host#set vmhost external-interface in-band vlan-id 10
For example, to configure an in-band external interface on an NFX250 or an NFX350 device:
user@host#set vmhost external-interface in-band mapping interface hsxe0 user@host#set vmhost external-interface in-band mapping interface virtual-function user@host#set vmhost external-interface in-band family inet address 10.10.10.10/24 gateway 10.10.10.254 user@host#set vmhost external-interface in-band vlan-id 10
Configuring for out-of-band External Interface
The topology requirement irrespective of the type of SKU is a VNF with an out-of-band management interface reachable on the same management network as the out-of-band management interface (eth0) of the NFX device.
user@host#set vmhost external-interface out-of-band family inet address ipv4_net_addres user@host#set vmhost external-interface out-of-band family inet gateway ipv4_gateway
For example:
user@host#set vmhost external-interface out-of-band family inet address 10.204.97.175/20 user@host#set vmhost external-interface out-of-band family inet gateway 10.204.111.254/32