All the paths mentioned below have restrictions:

This configuration was introduced in OcNOS version 6.5.0.

The OpenConfig profile Forwarding-group does not have an equivalent model on OcNOS model, so this object is stored inside Translation Auxiliary Database.

The object name on OpenConfig format allows any string value. However on OcNOS, all Forwarding-profiles have fixed names that follow the pattern q[0-7]. Hence the Forwarding-groups leaf name must follow this pattern.

Here is a sample OpenConfig NetConf Payload to create Forwarding-groups profiles.

The below configuration is used to enable QoS on OcNOS.

This configuration was introduced in OcNOS version 6.1.0

The QoS protocol is enabled by default in OcNOS version 6.5.0. However, the QoS protocol needs to be enabled in the older versions before configuring QoS features.

Note that there is no equivalent configuration to enable/disable QoS protocol in OpenConfig model.

There is no equivalent configuration in OpenConfig model.

The below CLI command is used to enable QoS on OcNOS.

Here is a sample OcNOS NetConf Payload to enable QoS on OcNOS.

There is no equivalent configuration.

The below configuration is used to enable QoS Profile on OcNOS.

This configuration was introduced in OcNOS version 5.1.

The QoS feature on OcNOS model needs the Hw profile to be enabled on SP Hardware types.
Note that there is no equivalent configuration on OpenConfig model.

There is no equivalent configuration.

The below CLI command is used to enable QoS Profile on OcNOS.

Here is the OcNOS NetConf Payload to enable QoS Profile on OcNOS.

There is no equivalent configuration.

None.

The below configuration is used to create Classifiers profiles.

This configuration was introduced in OcNOS version 6.1.0.

The OpenConfig QoS Classifiers is a profile responsible for handling data traffic classification.
This configuration does not have a direct equivalent object on OcNOS model. To configure classifier on OcNOS model it needs to be translated to ACL, class-maps and policy-maps objects.

Here is a sample OpenConfig NetConf Payload to create Classifiers profiles.

The below CLI command is used to create Classifiers profiles for handling data traffic classification.

Here is a sample OcNOS Netconf Payload to create Classifiers profiles for handling data traffic classification.

Here is the NetConf validation response that provides detailed information about creating Classifiers profiles.

This translation is only available for SP Hardware type.

All the paths mentioned below have restrictions:

The below configuration is used to create Forwarding-groups profile.

This configuration was introduced in OcNOS version 6.1.0.

The OpenConfig profile Forwarding-group does not have an equivalent model on OcNOS model, so this object is stored inside Translation Auxiliary Database.

The object name on OpenConfig format allows any string value. However on OcNOS, all Forwarding-profiles have fixed names that follow the pattern q[0-7]. Hence, the Forwarding-groups leaf name must follow this pattern.

Here is a sample OpenConfig NetConf Payload to create Forwarding-groups profiles.

There is no equivalent configuration.

There is no equivalent configuration.

Here is a NetConf validation response that provides detailed information about creating Forwarding-groups profiles.

The below configuration is used to create Queue and Queue-Management-profiles entries.

This configuration was introduced in OcNOS version 6.1.0.

The OpenConfig profiles Queues and Queue-Management-Profiles do not have an equivalent model on OcNOS, so this object is stored inside Translation Auxiliary Database.
These OpenConfig profiles are used to configure on OcNOS model random-detect configuration from policy-map type queuing object.

The object name on OpenConfig format allows any string value. However on OcNOS, they have fixed names that follow the pattern q[0-7]. Hence the Queues and Queue-Management-Profiles leaf name must follow this pattern.

Here is a sample OpenConfig NetConf Payload to create Queues and Queue-Management-profiles entries.

There is no equivalent configuration.

There is no equivalent configuration.

Here is the NetConf response that gives detailed information about creating Queues and Queue-Management-profiles entries.

The below configuration is used to create Scheduler-policies entries.

This configuration was introduced in OcNOS version 6.1.0.

This configuration snippet is used to set a one-rate-two-color VLAN match.

The scheduler-policies input configuration for OpenConfig XPath /oc-qos:qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config now has its leaf queue as mandatory in operations "create", "delete", "remove" and "merge". This is because the translation mapping done on OcNOS datamodel to XPath /qos/global/policy-maps/policy-map/classes/class and the queue leaf points to class-map-name leaf on OcNOS. If this condition is not addressed, the Translation Framework throws an error when the OpenConfig payload is applied.

Here is a sample OpenConfig NetConf Payload to set a one-rate-two-color VLAN match.

The below CLI command is used to set a one-rate-two-color VLAN match.

Here is a sample NetConf Payload to set a one-rate-two-color VLAN match.

Here is a NetConf validation response that provides detailed information about setting a one-rate-two-color VLAN match.

The below configuration is used to create interfaces classifier association.

This configuration was introduced in OcNOS version 6.1.0.

On OpenConfig model, the classifier profile can be associated to an interface on egress and ingress direction, and a list of classifiers can be associated to an interface. But on OcNOS model, the interface only allows one classifier object, and the association is in ingress direction.

On OcNOS model, the association between QoS ingress interface and QoS classifier profile needs the hardware-profile ingress-ipv4-qos to be enabled before the association. The translation adds the hardware-profile ingress-ipv4-qos configuration during translation on XPath /oc-qos:qos/interfaces/interface/input/classifiers/classifier/config/name.

Here is a sample OpenConfig NetConf Payload to create interfaces classifier association.

The below CLi command is used to create interfaces classifier association.

Here is a sample OcNOS NetConf Payload to create interfaces classifier association.

Here is a NetConf validation response that provides detailed information about creating interfaces classifier association.

This configuration is used to create interfaces scheduler-policies association.

This configuration was introduced in OcNOS version 6.1.0.

On Open Config model, the scheduler-policies profile can be associated to an interface on egress and ingress direction.
On OcNOS model, the interface only allows the associate one scheduler-policies object, and the association is on ingress direction.

Here is a sample OpenConfig NetConf Payload to create interfaces scheduler-policies association.

The below CLI command is used to create interfaces scheduler-policies association.

Here is a sample OcNOS NetConf Payload to create interfaces scheduler-policies association.

Here is a NetConf validation response that provides detailed information about creating interfaces scheduler-policies association.