Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Mapping Interfaces on NFX150 Devices

Mapping Physical Interfaces to Virtual Interfaces on NFX150 Devices

The NFX150 devices are shipped with the default mapping as described in NFX150 Feature Overview. You can change the mapping to suit your needs. Any of the physical ports can be mapped to the ge-0/0/x or ge-1/0/x interfaces. Any change in port mapping configuration will automatically reset the affected FPC.


On NFX150 devices, the link does not come up if 1G SFP port is connected from heth-0-4 and heth-0-5 ports to a peer device. As a workaround, disable the auto-negotiation for the interface connected to the NFX150 device on the remote device.

  • To map a physical port to a virtual interface:

    For example, to map the physical port heth-0-2 to the Layer 2 dataplane (FPC0) interface ge-0/0/3, the command is as follows:

    For example, to map the physical port heth-0-5 to the Layer 3 dataplane (FPC1) interface ge-1/0/2, the command is as follows

  • To map a physical port to two FPC1 interfaces:

    For example, to map the physical port heth-0-1 to the Layer 3 data plane(FPC1) interfaces ge-1/0/1 and ge-1/0/2:

Mapping Physical Ports to VNF Interfaces Through SR-IOV

You can configure Layer 3 services using single-root I/O virtualization (SR-IOV). To map a VNF interface to a physical interface by using the SR-IOV virtual function, use the following command:

Mapping Layer 3 Dataplane Interfaces to OVS

The ge-1/0/0 interface is always mapped to the service chaining backplane (OVS). To map additional Layer 3 dataplane interfaces to the system bridge, use the following command: