Owners Manual
Interfaces
You can create and manage physical and virtual interfaces—physical port interfaces are ports on the NPU and do not include the
Management port. Each physical port on the NPU maps to a data port on the front panel of the device.
Applications access physical and virtual ports using mapped Linux interfaces. The software allocates an ifindex for each Linux interface,
and the value is used in CPS APIs to refer to a Linux interface.
Map ports to Linux interfaces
Each physical port is mapped to an internal Linux interface:
eNSS-PPP-F.vvv
• e — Ethernet port
• N — node ID (set to 1)
• SS — slot number (set to 01)
• PPP — port number (1 to 999)
• F — number of a 4x10G fan-out port (0 to 9)
• vvv — VLAN ID number (0 to 4095)
The e101-031-0 interface refers to physical port 31 without a fan-out—e101-005-4 identies fanout port 4 on physical port 5, and
e101-001-2 identies fanout port 2 on physical port 1.
Interfaces are created during system boot up and represent the physical ports on the NPU in a one-to-one mapping.
Internal interfaces allow applications to congure physical port parameters, such as MTU, port state, and link state. Interfaces also provide
packet input/output functionality and support applications sending and receiving control plane packets.
Map CPU port to Linux interface
The software creates a dedicated interface (npu0) that maps to the CPU port. Congure control plane policy (CoPP) queue rates by
specifying npu0 as the port in the QoS CPS API.
Topics:
• Physical ports
2
Interfaces 5