-
Notifications
You must be signed in to change notification settings - Fork 35
Interface management
The NAS port management feature consists of managing physical ports and providing logical resources for applications to use.
- NAS port management exposes the
dell-base-phy-interface.yang
model to clients. Through this model, applications are given access to NPU port resources. - Users will generally add and delete interfaces using physical port objects.
- Advanced users may also split a single front panel port into multiple physical ports. This operation is called breakout. There is also the opposite operation called breakin.
- To breakout or breakin a port, a user must first delete all of the interfaces associated with the physical ports that are effected. Developers can check the front panel port object to determine which hardware ports are related to the physical port and then map these hardware ports into physical ports which then can be mapped to interfaces.
This object model provides a list of all front panel ports in the system that are known to NAS. The key for these objects is unit, slot, and front panel port.
Name | Description |
---|---|
unit-id | Chassis that contains the front panel port information |
slot-id | Contains the hardware port ID |
front-panel-port | Front panel port number |
media-id | PAS media ID for the interface — can be used to query the PAS to retrieve port information |
port | List of hardware ports the front panel contains — ports can be mapped to NAS ports through the physical port model |
control-port | Front panel control port — this special port takes any breakout/breakin requests |
default-name | Suggested name for the front panel port interfaces |
This object model provides a list of all hardware ports in the system — active or not. Review the fanout mode to determine if it is a valid port.
Name | Description |
---|---|
unit-id | Chassis for the hardware port |
slot-id | Slot ID containing the hardware port |
npu-id | NPU ID containing the hardware port |
hw-port | Physical port |
hw-control-port | Control port (or master hardware port) for this specific hardware port |
subport-id | NPU-specific hardware port — generally 0-3 for 4x1 ports |
fanout-mode | Current fanout mode of the hardware port |
This object model provides the control of the actual NPU port.
Name | Description |
---|---|
unit-id | Chassis for the physical port |
slot-id | Slot ID for the physical port |
npu-id | NPU that owns the port |
port-id | System assigned port ID |
hardware-port-id | Corresponding hardware port |
breakout-capabilities | Breakout modes supported by the port |
phy-media | Configurable SFP or QSFP that is plugged into the port |
loop-back | Loopback mode for the port |
This object is what you generally interact with from a system perspective. Through the interface object, you can create ifindex
files to send/receive packets, and configure or provide higher level functions. The interface object can be either Layer 2 or Layer 3 interfaces.
Name | Description |
---|---|
ifindex | Central key for the interface which is globally unique |
name | Port name |
interface-type | Type of interface |
supported-speed | Possible speeds supported by the port |
mode | Sets the port for either L2 or L3 mode |
mtu | Interface MTU |
speed | Interface speed |
oper-status | Operational status of the port |
admin-status | Administrative status of the port |
This action allows you to select a port and configure the breakout mode.
NOTE: To successfully configure breakout mode for a port, you must delete all previous configuration information.
Name | Description |
---|---|
unit-id | Chassis that contains the front panel port |
slot-id | Slot ID owning the front panel port |
front-panel-port | Front panel port number |
breakout-mode | Port breakout mode |
© 2019 OpenSwitch project. All information is contributed to and made available by OPX under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).
- Home
- System overview
- Software releases
- Hardware support
- FAQs
- Install
- Build
- Configure
- Develop
- Administer
- Troubleshoot
- Software compatibility
- Contribute
- DevOps
- Join