This XML configuration snippet is used to define and configure network interfaces.

This configuration was introduced in OcNOS version 5.0.

Here is the sample OpenConfig NetConf Payload for Interface Configuration.

The below CLI commands are used for Interface Configuration.

Here is the sample OcNOS NetConf Payload for Interface Configuration.

Here is a NetConf validation response for interface configuration, providing details about the current state of the specified interface.

The leaf mentioned below has been restricted to a maximum of 32 characters.

As a general restriction, interface names must have valid OcNOS naming conventions, such as 'eth,' 'xe,' 'ce,' 'so,' 'po,' etc. This naming convention is not configurable.

This XML configuration snippet is used to assign a description to a given interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload to configure interface description.

The below CLI command is used for configuring interface descriptions.

Here is the sample OcNOS NetConf Payload for configuring interface descriptions.

Here is a NetConf validation response for configuring interface descriptions, providing details about the current state of the specified interface.

The leaf mentioned below has been restricted to a maximum of 32 characters.

This XML configuration snippet is used to set the Maximum Transmission Unit (MTU) for an interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload to set the MTU for an interface.

The below CLI command is used to set the MTU for an interface.

Here is the sample OcNOS NetConf Payload to set the MTU for an interface.

Here is a NetConf validation response for setting the MTU for an interface, providing details about the current state of the specified interface.

The leaf mentioned below has been restricted to a maximum of 32 characters.

The leaf mentioned below is used only to configure the physical interface.

This XML configuration snippet is used to specify that an IP address and prefix length will be used by the interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload to indicate that the interface will use an IP address and a prefix length.

The below CLI command is used to configure an IP address and prefix length for an interface.

Here is a sample OcNOS NetConf Payload for assigning a primary IP address and prefix length to an interface.

Here is a NetConf validation response for assigning a primary IP address and prefix length to an interface, providing details about the current state of the specified interface.

The leaf mentioned below has been restricted to a maximum of 32 characters.

The first entry on the below list will be used as the primary address, as OpenConfig does not have this concept.

This XML configuration snippet specifies the use of a secondary IP address and prefix length for an interface. It's important to note that the secondary address cannot be configured if there is no primary IP address present.

This configuration was introduced in OcNOS version 4.2.

Here is a sample OpenConfig NetConf payload that specifies the configuration for an interface. This configuration includes the interface type, subinterface details, and IPv4 addresses with their respective prefix lengths.

The below CLI command is used to configure an interface with both a primary and a secondary IP address.

Here is a sample OcNOS NetConf Payload for configuring interface with both a primary and a secondary IP address.

Here is a NetConf validation response providing details about the current state of the specified interface, as configured in the OpenConfig YANG model.

The leaf mentioned below has been restricted to a maximum of 32 characters.

All leaves of the below list, excluding the first entry, will be treated as secondary addresses.

This XML configuration snippet is used to set the IPv6 addresses of an interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload for configuring IPv6 addresses on an interface.

The below CLI command is used to configure an interface with multiple IPv6 addresses and enable the interface.

Here is a sample OcNOS NetConf Payload for configuring an interface with multiple IPv6 addresses.

The below NetConf validation response provides details about the current state of the specified interface configured with multiple IPv6 addresses using OpenConfig YANG data model elements.

The leaf mentioned below has been restricted to a maximum of 32 characters.

This XML configuration snippet is used to configure the duplex mode for an interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload to configure interface with the FULL duplex mode enabled.

The below CLI command is used to configure an interface with full duplex mode enabled and with no shutdown.

Here is a sample OcNOS NetConf Payload to configure interface with full duplex mode enabled and ensures that the interface is in the enabled state.

Here is a NetConf validation response provides comprehensive information about the current state of an interface, including its operational and administrative status, traffic counters, and Ethernet configuration details.

The leaf mentioned below has been restricted to a maximum of 32 characters.

By default, the duplex mode for an interface is set to full duplex.

This XML configuration snippet is used to set the link speed of the interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload that specifies the configuration for an interface. It sets the interface's state to enabled (true) and defines it as an Ethernet interface (ianaift:ethernetCsmacd). Additionally, it specifies that auto-negotiation for link speed is disabled (false) and sets the port speed for a specified Ethernet interface.

The below CLI command is used to configure an interface for a speed of 1 gigabit and enable it.

Here is a sample OcNOS NetConf Payload that enables an interface and sets its speed.

Here is a NetConf validation response to set the speed of an interface, providing details about the current state of the specified interface.

The leaf mentioned below has been restricted to a maximum of 32 characters.

This leaf can only be used when the auto-negotiate leaf (../auto-negotiate) is set to false.

This XML configuration snippet is used to specify the Ethernet type for an interface.

This configuration was introduced in OcNOS version 5.0.

Here is the sample OpenConfig NetConf Payload that sets the Ethernet Type for an interface.

The below CLI command configures VLAN tagging with Ethernet Type on an interface and ensures that the interface is not in shutdown mode.

Here is a sample OcNOS NetConf Payload that enables an interface and configures it to use a dot1q Ethernet Type for VLAN tagging.

Here is a NetConf validation response for the specified interface, providing comprehensive details about its current state, including operational and administrative statuses, traffic counters, Ethernet configuration, and VLAN tagging settings.

The leaf mentioned below has been restricted to a maximum of 32 characters.

This XML configuration snippet sets both primary and secondary IP addresses, each with its corresponding prefix length, for use by a sub-interface.

This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload for configuring sub-interface with two IPv4 addresses, each having the specified prefix length. This payload specifies the IP addresses to be used by the sub-interface with the specified index.

The below CLI command is used to configure a sub-interface with both a primary and a secondary IPv4 address.

Here is a sample OcNOS NetConf Payload for configuring a sub-interface with both a primary and a secondary IPv4 address.

Here is a NetConf validation response for configuring a sub-interface with two IPv4 addresses, each with a specified prefix length. The response provides information about the current state of the specified sub-interface, including its operational status, interface index, and traffic counters.

The leaf mentioned below has been restricted to a maximum of 32 characters.

The first entry on the below list will be used as the primary address, as OpenConfig does not have this concept.

When using OpenConfig translation, use the sub-interface name in the format <ifname>.<id>, as OpenConfig does not support the <ifname>.<id>.<id> format, even though it is allowed by OcNOS CLI.