Verifying cos-to-cos mutation qos mapping – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual

Page 458

Advertising

426

Network OS NETCONF Operations Guide

53-1003231-02

Queueing

5. Under the <qos> node, include the <cos-mutation> leaf element and specify the CoS-to-CoS

mutation QoS map to activate and apply changes made to the map.

6. Under the <qos> node, include the <trust> node element.

7. Under the <trust> node element, include the empty <trust-cos> leaf element to specify the

trust mode for incoming traffic.

This step specifies the interface ingress QoS trust mode, which controls user priority mapping
of incoming traffic. The untrusted mode overrides all incoming priority markings with the
Interface Default CoS. The CoS mode sets the user priority based on the incoming CoS value. If
the incoming packet is not priority tagged, then fallback is to the interface default CoS value.

8. Issue the <bna-config-cmd> RPC to save the running-config file to the startup-config file.

The following example activates a map named “test” on 10-gigabit interface 22/0/2, and
establishes trust mode.

<?xml version="1.0" encoding="UTF-8"?>

<edit-config>

</target>

<cos-mutation>test</cos-mutation>

<trust>

<trust-cos/>

</trust>

</qos>

</tengigabitethernet>

</interface>

</config>

</edit-config>

</rpc>

<rpc-reply message-id="2305" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">

<ok/>

</rpc-reply>

Verifying CoS-to-CoS mutation QoS mapping

To verify a CoS-to-CoS mutation mapping, issue the <get-config> RPC to retrieve the CoS-to-CoS
mutation QoS map and the interface names to which a map is bound.

1. Verify a CoS-to-CoS mutation QoS map using a subtree filter to view only the contents of the

<qos>/<map>/<cos-mutation> node. To limit the returned information to a specific QoS map,
refine the content match node with the QoS map name.

The following example returns the CoS-to-CoS mutation QoS map for a map named “test.”

<?xml version="1.0" encoding="UTF-8"?>

<get-config>

Advertising