No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NETCONF YANG API Reference

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

NETCONF YANG API Reference
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
MQC

MQC

NOTE:

MQC is not supported by the 4GE-2S, 4ES2G-S, 4ES2GP-S, 9ES2 and 24ES2GP cards.

Data Model

The data model files matching MQC are huawei-mqc.yang and huawei-mqc-apply.yang.

Table 3-1737 MQC

Object

Description

huawei-mqc:mqc

Indicates that the object of requesting an operation (creation, deletion, or modification) is the MQC configuration. It is a root object, which is only used to contain sub-objects.

huawei-mqc:mqc/traffic-classifier/name

Indicates the name of a traffic classifier. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-classifier/operator

Indicates the logical relationship between rules in a traffic classifier.

huawei-mqc:mqc/traffic-classifier/match-condition/acl

Indicates the ACL number. The value is an integer that ranges from 2000 to 4999.

huawei-mqc:mqc/traffic-classifier/match-condition/acl6

Indicates the IPv6 ACL number. The value is an integer that ranges from 2000 to 3999.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/dscp-value

Indicates the DSCP value of packets. The value is an integer that ranges from 0 to 63.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/source-mac/mac

Indicates the source MAC address. The value is in H-H-H format. An H is a hexadecimal number of 4 digits.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/source-mac/mac-mask

Indicates the mask of the source MAC address. The value is in H-H-H format. An H is a hexadecimal number of 4 digits. The value cannot be 0000-0000-0000.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/destination-mac/mac

Indicates the destination MAC address. The value is in H-H-H format. An H is a hexadecimal number of 4 digits.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/destination-mac/mac-mask

Indicates the mask of the destination MAC address. The value is in H-H-H format. An H is a hexadecimal number of 4 digits. The value cannot be 0000-0000-0000.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/l2-protocol-value

Indicates the protocol type value. The value is a hexadecimal number that ranges from 0x0600 to 0xFFFF. The value must start with 0x.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/protocol-mask

Indicates the mask of the protocol type value. The value is a hexadecimal number that ranges from 0x0000 to 0xFFFF. The value must start with 0x.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-name

Indicates the protocol type. The value can be arp, ip, mpls, rarp, and ipv6.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/vlan/start-vlan

Indicates the start outer VLAN ID. The value is an integer that ranges from 1 to 4094.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/vlan/end-vlan

Indicates the end outer VLAN ID. The value is an integer that ranges from 1 to 4094. The end outer VLAN ID must be greater than the start outer VLAN ID.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/cvlan/start-vlan

Indicates the start inner VLAN ID of a QinQ packet. The value is an integer that ranges from 1 to 4094.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/cvlan/end-vlan

Indicates the end inner VLAN ID of a QinQ packet. The value is an integer that ranges from 1 to 4094. The end inner VLAN ID must be greater than the start inner VLAN ID of a QinQ packet.

huawei-mqc:mqc/traffic-classifier/match-condition/inbound-interface

Indicates the inbound interface.

huawei-mqc:mqc/traffic-classifier/match-condition/qos-group/start-group

Indicates the start index of a QoS group. The value is an integer that ranges from 1 to 99.

huawei-mqc:mqc/traffic-classifier/match-condition/qos-group/end-group

Indicates the end index of a QoS group. The value is an integer that ranges from 1 to 99. The end index of the QoS group must be greater than the start index of the QoS group.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/applications/application-name

Indicates the name of an application protocol. The value is a string of 1 to 32 characters.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/applications/time-range

Indicates the name of a time range. The value is a string of 1 to 32 case-sensitive characters without spaces and must begin with a letter. To avoid confusion, do not use all as the name. This parameter is optional.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/categorys/category-name

Indicates the name of an SA application group.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/categorys/time-range

Indicates the name of a time range. The value is a string of 1 to 32 case-sensitive characters without spaces and must begin with a letter. To avoid confusion, do not use all as the name. This parameter is optional.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/app-groups/app-group-name

Indicates the name of a user-defined application group. The value is a string of 1 to 32 characters, and the question mark (?), comma (,), quotation mark ("), and hyphen (-) are not supported.

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/app-groups/time-range

Indicates the name of a time range. The value is a string of 1 to 32 case-sensitive characters without spaces and must begin with a letter. To avoid confusion, do not use all as the name. This parameter is optional.

huawei-mqc:mqc/traffic-behaviour/name

Indicates the name of a traffic behavior. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-behaviour/remark-dot1q

Indicates the action of re-marking 802.1p priorities of VLAN packets. The 802.1p priority value is an integer that ranges from 0 to 7.

huawei-mqc:mqc/traffic-behaviour/dscp-name

Indicates the action of re-marking DSCP priority names of IP packets. The DSCP priority can be ef, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, or default.

huawei-mqc:mqc/traffic-behaviour/dscp-value

Indicates the action of re-marking DSCP priority value of IP packets. The DSCP priority value is an integer that ranges from 0 to 63.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

Indicates the next-hop IP address where packets are redirected.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/vpn-instance

Indicates the name of a VPN instance. The value is a string of 1 to 31 case-sensitive characters without spaces. If the string is enclosed in double quotation marks (" "), the string can contain spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/interface/interface

Indicates the name of the redirection association interface. Only Ethernet, VLANIF, and Dialer interfaces are supported.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-nqa/admin-name

Indicates the administrator name of an NQA test instance. The value is a string of 1 to 32 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-nqa/test-name

Indicates the name of an NQA test instance. The value is a string of 1 to 32 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/si-index

Indicates the Service Index (SI) added to packets during redirection. The value is an integer that ranges from 1 to 255.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/spi-index

Indicates the Service Path Identifier (SPI) index added to packets during redirection. The value is an integer that ranges from 1 to 16777215.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-vrrp/interface

Indicates the type and number of an interface associated with a VRRP group.

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-vrrp/vrid

Indicates the virtual router ID (VRID). The value is an integer that ranges from 1 to 255.

huawei-mqc:mqc/traffic-behaviour/redirect/interface

Indicates the interface where packets are redirected. Packets can be redirected to only 3G cellular and dialer interfaces. In MPoEoA mode, packets cannot be redirected to dialer interfaces.

huawei-mqc:mqc/traffic-behaviour/redirect/vpn-instance

Indicates the name of a VPN instance to which packets need to be redirected. The value is a string of 1 to 31 case-sensitive characters without spaces. If the string is enclosed in double quotation marks (" "), the string can contain spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop/next-hop-ip

Indicates the IP address of the backup next hop.

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop/vpn-instance

Indicates the name of the backup VPN instance to which packets need to be redirected. The value is a string of 1 to 31 case-sensitive characters without spaces. If the string is enclosed in double quotation marks (""), the string can contain spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop/track-nqa/admin-name

Indicates the administrator name of the NQA test instance associated with backup redirection. The value is a string of 1 to 32 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop/track-nqa/test-name

Indicates the name of the NQA test instance associated with backup redirection. The value is a string of 1 to 32 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop/interface/interface

Indicates the name of the interface associated with backup redirection. Only Ethernet, VLANIF, and Dialer interfaces are supported.

huawei-mqc:mqc/traffic-behaviour/sub-traffic-policy

Indicates the name of a user-defined traffic policy.

huawei-mqc:mqc/traffic-behaviour/gts/cir

Indicates the CIR for traffic shaping. The value is an integer that ranges from 8 to 4294967295, in kbit/s.

huawei-mqc:mqc/traffic-behaviour/gts/pct

Indicates the percentage of the bandwidth for a type of traffic to the actual available bandwidth. The value is an integer that ranges from 1 to 100.

NOTE:
  • If the traffic behavior in the parent traffic policy defines traffic shaping, a sub traffic policy queue bandwidth is equal to the queue bandwidth of the parent traffic policy times the value of pct.
  • If a traffic policy is applied to an interface with interface-based traffic policing configured, the interface queue bandwidth is equal to the specified committed information rate (CIR) times the value of pct.
  • In other cases, the queue bandwidth is equal to the interface bandwidth times the value of pct.

huawei-mqc:mqc/traffic-behaviour/car/cir

Indicates the CIR for traffic policing. The value is an integer that ranges from 8 to 4294967295, in kbit/s.

huawei-mqc:mqc/traffic-behaviour/car/pct

Indicates the percentage of the PIR value to the interface bandwidth. The value is an integer that ranges from 1 to 100.

huawei-mqc:mqc/traffic-behaviour/ef/bandwidth

Indicates the maximum bandwidth for Expedited Forwarding (EF) queues. The value is an integer that ranges from 8 to 4294967295, in kbit/s.

huawei-mqc:mqc/traffic-behaviour/af/bandwidth

Indicates the minimum bandwidththat for EF queues. The value is an integer that ranges from 8 to 4294967295, in kbit/s.

huawei-mqc:mqc/traffic-behaviour/llq/bandwidth

Indicates the maximum bandwidth for LLQ queues. The value is an integer that ranges from 8 to 4294967295, in kbit/s.

huawei-mqc:mqc/traffic-behaviour/wfq/wfq

Indicates WFQ scheduling.

huawei-mqc:mqc/traffic-behaviour/action

Indicates that access control is performed for service packets based on traffic classification.

huawei-mqc:mqc/traffic-policy/name

Indicates the name of a traffic policy. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-policy/match-extended

Indicates that the matching mode of a traffic classifier in a traffic policy is extended.

huawei-mqc:mqc/traffic-policy/rule/traffic-classifier

Indicates the name of a traffic classifier. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-policy/rule/traffic-behaviour

Indicates the name of a traffic behavior. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc:mqc/traffic-policy/rule/precedence

Indicates the priority of the bound traffic classifier and traffic behavior. This parameter is optional. The value is an integer that ranges from 1 to 65535, and a smaller value indicates a higher priority.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/name

Indicates the name of a traffic policy. The value is a string of 1 to 31 case-sensitive characters without spaces.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/name

Indicates the name of the interface to which a traffic policy is applied.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound

Indicates that a traffic policy is applied in the inbound direction.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound

Indicates that a traffic policy is applied in the outbound direction.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-preprocess

Indicates that a preprocessing traffic policy is applied to the inbound direction of an interface.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-preprocess

Indicates that a preprocessing traffic policy is applied to the outbound direction of an interface.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-firstprocess

Indicates that a preferential processing traffic policy is applied to the inbound direction of an interface.

NOTE:

Only V300R003C00 supports the preferential processing traffic policy.

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-firstprocess

Indicates that a preferential processing traffic policy is applied to the outbound direction of an interface.

Configuring a Traffic Classifier

Creating a Traffic Classifier

This section provides a sample of creating a traffic classifier.

Table 3-1738 Creating a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier

Data Requirements
Table 3-1739 Creating a traffic classifier named classifier1

Item

Data

Description

Name of a traffic classifier

classifier1

Create a traffic classifier named classifier1, and configure the relationship between rules in the traffic classifier as AND.

Relationship between rules in the traffic classifier

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <operator>true</operator> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Traffic Classifier

This section provides a sample of deleting a traffic classifier.

Table 3-1740 Deleting a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier

Data Requirements
Table 3-1741 Deleting a traffic classifier named classifier1

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a traffic classifier named classifier1.

Relationship between rules in the traffic classifier

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier xc:operation="remove"> 
     <name>classifier1</name> 
     <operator>true</operator> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching an ACL

Referencing an ACL in a Traffic Classifier

This section provides a sample of referencing an ACL in a traffic classifier.

Table 3-1742 Referencing an ACL in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/acl

Data Requirements
Table 3-1743 Referencing ACL 3501 in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Reference ACL 3501 in the traffic classifier classifier1.

Number of an ACL

3501

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl>3501</acl> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Changing the ACL Referenced by a Traffic Classifier

This section provides a sample of changing the ACL referenced by a traffic classifier.

Table 3-1744 Changing the ACL referenced by a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/acl

Data Requirements
Table 3-1745 Changing ACL 3501 referenced by traffic classifier classifier1 to ACL 3502

Item

Data

Description

Name of a traffic classifier

classifier1

Change ACL 3501 referenced by the traffic classifier classifier1 to ACL 3502.

Number of an ACL

3502

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl>3502</acl> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting the ACL Referenced by a Traffic Classifier

This section provides a sample of deleting the ACL referenced by a traffic classifier.

Table 3-1746 Deleting the ACL referenced by a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/acl

Data Requirements
Table 3-1747 Deleting the ACL referenced by a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete the ACL referenced by the traffic classifier classifier1.

Number of an ACL

3502

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl xc:operation="remove">3502</acl> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching an IPv6 ACL

Configuring an IPv6 ACL in a Traffic Classifier

This section provides a sample of configuring an IPv6 ACL in a traffic classifier.

Table 3-1748 Configuring an IPv6 ACL in a traffic classifier

Operation

XPATH

edit-config:default

huawei-mqc:mqc/traffic-classifier/match-condition/acl6

Data Requirements
Table 3-1749 Configuring IPv6 ACL 3501 in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

onfigure IPv6 ACL 3501 in traffic classifier classifier1.

Number of an IPv6 ACL

3501

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl6>3001</acl6> 
     </match-condition> 
    </traffic-classifier> 
 </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting an IPv6 ACL in a Traffic Classifier

This section provides a sample of deleting an IPv6 ACL in a traffic classifier.

Table 3-1750 Deleting an IPv6 ACL in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/acl6

Data Requirements
Table 3-1751 Deleting an IPv6 ACL in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete IPv6 ACL 3002 in traffic classifier classifier1.

Number of an IPv6 ACL

3002

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl6 xc:operation="remove">3002</acl6> 
     </match-condition> 
    </traffic-classifier> 
 </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Matching the Layer 2 Protocol Type

Matching DSCP Priorities of IP Packets

Configuring a Matching Rule Based on DSCP Priorities of IP Packets in a Traffic Classifier

This section provides a sample of configuring a matching rule based on DSCP priorities of IP packets in a traffic classifier.

Table 3-1752 Configuring a matching rule based on DSCP priorities of IP packets in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/dscp-value

Data Requirements
Table 3-1753 Configuring a matching rule based on DSCP priority 5 of IP packets in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on DSCP priority 5 of IP packets in traffic classifier classifier1.

DSCP priority

5

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <dscp-value>5</dscp-value> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on DSCP Priorities of IP Packets in a Traffic Classifier

This section provides a sample of deleting a matching rule based on DSCP priorities of IP packets in a traffic classifier.

Table 3-1754 Deleting a matching rule based on DSCP priorities of IP packets in a traffic classifier

Operation

XPATH

edit-config: remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/dscp-value

Data Requirements
Table 3-1755 Deleting a matching rule based on DSCP priority 5 of IP packets in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on DSCP priority 5 of IP packets in traffic classifier classifier1.

DSCP priority

5

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <dscp-value xc:operation="remove">5</dscp-value> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Source MAC Address

Configuring a Matching Rule Based on the Source MAC Address in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the source MAC address in a traffic classifier.

Table 3-1756 Configuring a matching rule based on the source MAC address in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/source-mac

Data Requirements
Table 3-1757 Configuring a matching rule based on the source MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on the source MAC address of 00:50:ba:27:be:d3 and mask of 0x00ff-f00f-ffff in the traffic classifier classifier1.

Source MAC address

00:50:ba:27:be:d3

Mask of the source MAC address

0x00ff-f00f-ffff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <source-mac> 
        <mac>00:50:ba:27:be:d3</mac> 
        <mac-mask>0x00ff-f00f-ffff</mac-mask> 
       </source-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Matching Rule Based on the Source MAC Address in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the source MAC address in a traffic classifier.

Table 3-1758 Modifying a matching rule based on the source MAC address in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/source-mac

Data Requirements
Table 3-1759 Modifying a matching rule based on the source MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Change the source MAC address from 00:50:ba:27:be:d3 to 04:35:ba:27:be:d3 and mask from 00ff-f00f-ffff to 0f0f-000f-f0ff in the traffic classifier classifier1.

Source MAC address

04:35:ba:27:be:d3

Mask of the source MAC address

0x0f0f-000f-f0ff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <source-mac> 
        <mac>04:35:ba:27:be:d3</mac> 
        <mac-mask>0x0f0f-000f-f0ff</mac-mask> 
       </source-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on the Source MAC Address in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the source MAC address in a traffic classifier.

Table 3-1760 Deleting a matching rule based on the source MAC address in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/source-mac

Data Requirements
Table 3-1761 Deleting a matching rule based on the source MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the source MAC address in the traffic classifier classifier1.

Source MAC address

04:35:ba:27:be:d3

Mask of the source MAC address

0x0f0f-000f-f0ff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <source-mac xc:operation="remove"> 
        <mac>04:35:ba:27:be:d3</mac> 
        <mac-mask>0x0f0f-000f-f0ff</mac-mask> 
       </source-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Destination MAC Address

Configuring a Matching Rule Based on the Destination MAC Address in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the destination MAC address in a traffic classifier.

Table 3-1762 Configuring a matching rule based on the destination MAC address in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/destination-mac

Data Requirements
Table 3-1763 Configuring a matching rule based on the destination MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on the destination MAC address of 00:50:ba:27:be:d3 and mask of 0x00ff-f00f-ffff in the traffic classifier classifier1.

Destination MAC address

00:50:ba:27:be:d3

Mask of the destination MAC address

0x00ff-f00f-ffff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <destination-mac> 
        <mac>00:50:ba:27:be:d3</mac> 
        <mac-mask>0x00ff-f00f-ffff</mac-mask> 
       </destination-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Matching Rule Based on the Destination MAC Address in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the destination MAC address in a traffic classifier.

Table 3-1764 Modifying a matching rule based on the destination MAC address in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/destination-mac

Data Requirements
Table 3-1765 Modifying a matching rule based on the destination MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Change the destination MAC address from 00:50:ba:27:be:d3 to 04:35:ba:27:be:d3 and mask from 00ff-f00f-ffff to 0f0f-000f-f0ff in the traffic classifier classifier1.

Destination MAC address

04:35:ba:27:be:d3

Mask of the destination MAC address

0x0f0f-000f-f0ff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <destination-mac> 
        <mac>04:35:ba:27:be:d3</mac> 
        <mac-mask>0x0f0f-000f-f0ff</mac-mask> 
       </destination-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on the Destination MAC Address in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the destination MAC address in a traffic classifier.

Table 3-1766 Deleting a matching rule based on the destination MAC address in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/destination-mac

Data Requirements
Table 3-1767 Deleting a matching rule based on the destination MAC address in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the destination MAC address in the traffic classifier classifier1.

Destination MAC address

04:35:ba:27:be:d3

Mask of the destination MAC address

0x0f0f-000f-f0ff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <destination-mac xc:operation="remove"> 
        <mac>04:35:ba:27:be:d3</mac> 
        <mac-mask>0x0f0f-000f-f0ff</mac-mask> 
       </destination-mac> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Modifying a Matching Rule Based on the Layer 2 Protocol Type in a Traffic Classifier

This section provides a sample of modifying an IPv6 ACL in a traffic classifier.

Table 3-1768 Modifying an IPv6 ACL in a traffic classifier

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-classifier/match-condition/acl6

Data Requirements
Table 3-1769 Modifying IPv6 ACL 3002 in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Modify IPv6 ACL 3002 in traffic classifier classifier1.

Number of an IPv6 ACL

3002

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <acl6 xc:operation="replace">3002</acl6> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Configuring a Matching Rule Based on the Layer 2 Protocol Type in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the Layer 2 protocol type in a traffic classifier.

Table 3-1770 Configuring a matching rule based on the Layer 2 protocol type in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/l2-protocol-value

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/protocol-mask

Data Requirements
Table 3-1771 Configuring a matching rule based on the Layer 2 protocol type of 0x0fff in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Create a matching rule based on the Layer 2 protocol type of 0x0fff in the traffic classifier classifier1, and set the mask of the protocol type to 0xffff.

Protocol type value

0x0fff

Mask of the protocol type value

0xffff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
 <edit-config>  
  <target>  
 <running/>  
  </target>  
  <error-option>rollback-on-error</error-option>  
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">  
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">  
    <traffic-classifier>  
     <name>classifier1</name>  
     <match-condition>  
      <named-field>  
       <l2-protocol-value-mask>  
        <l2-protocol-value>0x0fff</l2-protocol-value>  
        <protocol-mask>0xffff</protocol-mask> 
       </l2-protocol-value-mask>  
      </named-field>  
     </match-condition>  
    </traffic-classifier>  
   </mqc>  
  </config>  
 </edit-config>  
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying a Matching Rule Based on the Layer 2 Protocol Type in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the Layer 2 protocol type in a traffic classifier.

Table 3-1772 Modifying a matching rule based on the Layer 2 protocol type in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/l2-protocol-value

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/protocol-mask

Data Requirements
Table 3-1773 Changing the Layer 2 protocol type from 0x0fff to 0x0f0f

Item

Data

Description

Name of a traffic classifier

classifier1

Change the Layer 2 protocol type from 0x0fff to 0x0f0f in the traffic classifier classifier1.

Protocol type value

0x0f0f

Mask of the protocol type value

0xffff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
 <edit-config>  
  <target>  
 <running/>  
  </target>  
  <error-option>rollback-on-error</error-option>  
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">  
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">  
    <traffic-classifier>  
     <name>classifier1</name>  
     <match-condition>  
      <named-field>  
       <l2-protocol-value-mask>  
        <l2-protocol-value>0x0f0f</l2-protocol-value>  
        <protocol-mask>0xffff</protocol-mask> 
       </l2-protocol-value-mask>  
      </named-field>  
     </match-condition>  
    </traffic-classifier>  
   </mqc>  
  </config>  
 </edit-config>  
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply>
Modifying an Action of Redirecting Packets to the Next-Hop Address Associated with a VPN Instance

This section provides a sample of modifying an action of redirecting packets to the next-hop address associated with a VPN instance.

Table 3-1774 Modifying an action of redirecting packets to the next-hop address associated with a VPN instance

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/vpn-instance

Data Requirements
Table 3-1775 Modifying an action of redirecting packets to the next-hop address associated with a VPN instance

Item

Data

Description

Name of a traffic behavior

behavior1

Modify an action of redirecting packets to next-hop address 10.1.1.2 that is associated with VPN instance vpn_test1 in traffic behavior behavior1.

Next-hop address

10.1.1.2

Name of a VPN instance

vpn_test1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="replace"> 
       <next-hop-ip>10.1.1.2</next-hop-ip> 
       <vpn-instance>vpn_test1</vpn-instance> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Creating an Action of Redirecting Packets to the Next-Hop Address Associated with a VPN Instance

This section provides a sample of creating an action of redirecting packets to the next-hop address associated with a VPN instance.

Table 3-1776 Creating an action of redirecting packets to the next-hop address associated with a VPN instance

Operation

XPATH

edit-config:default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/vpn-instance

Data Requirements
Table 3-1777 Creating an action of redirecting packets to the next-hop address associated with a VPN instance

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of redirecting packets to next-hop address 10.1.1.1 that is associated with VPN instance vpn_test in traffic behavior behavior1.

Next-hop address

10.1.1.1

Name of a VPN instance

vpn_test

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <vpn-instance>vpn_test</vpn-instance> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Redirecting Packets to the Next-Hop Address Associated with a VPN Instance
Deleting an Action of Redirecting Packets to the Next-Hop Address Associated with a VPN Instance

This section provides a sample of deleting an action of redirecting packets to the next-hop address associated with a VPN instance.

Table 3-1778 Deleting an action of redirecting packets to the next-hop address associated with a VPN instance

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/vpn-instance

Data Requirements
Table 3-1779 Deleting an action of redirecting packets to the next-hop address associated with a VPN instance

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of redirecting packets to the next-hop address that is associated with a VPN instance in traffic behavior behavior1.

Next-hop address

10.1.1.2

Name of a VPN instance

vpn_test1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="remove"> 
       <next-hop-ip>10.1.1.2</next-hop-ip> 
       <vpn-instance>vpn_test1</vpn-instance> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Redirecting Packets to the Next-Hop Address and Adding SI/SPI to Packets

Matching the Outer VLAN ID

Configuring a Matching Rule Based on the Outer VLAN ID in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the outer VLAN ID in a traffic classifier.

Table 3-1780 Configuring a matching rule based on the outer VLAN ID in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/vlan

Data Requirements
Table 3-1781 Configuring a matching rule based on outer VLAN IDs 10 to 20 in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on outer VLAN ID range from 10 to 20 in the traffic classifier classifier1.

Start outer VLAN ID

10

End outer VLAN ID

20

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <vlan> 
        <start-vlan>10</start-vlan> 
        <end-vlan>20</end-vlan> 
       </vlan> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Matching Rule Based on the Outer VLAN ID in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the outer VLAN ID in a traffic classifier.

Table 3-1782 Modifying a matching rule based on the outer VLAN ID in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/vlan

Data Requirements
Table 3-1783 Changing the outer VLAN ID range from 10-20 to 100-200

Item

Data

Description

Name of a traffic classifier

classifier1

Change the outer VLAN ID range from 10-20 to 100-200 in the traffic classifier classifier1.

Start outer VLAN ID

100

End outer VLAN ID

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <vlan> 
        <start-vlan>100</start-vlan> 
        <end-vlan>200</end-vlan> 
       </vlan> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on the Outer VLAN ID in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the outer VLAN ID in a traffic classifier.

Table 3-1784 Deleting a matching rule based on the outer VLAN ID in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/vlan

Data Requirements
Table 3-1785 Deleting a matching rule based on the outer VLAN ID in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the outer VLAN ID in the traffic classifier classifier1.

Start outer VLAN ID

100

End outer VLAN ID

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <vlan xc:operation="remove"> 
        <start-vlan>100</start-vlan> 
        <end-vlan>200</end-vlan> 
       </vlan> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Inner VLAN ID of QinQ Packets

Configuring a Matching Rule Based on the Inner VLAN ID of QinQ Packets in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier.

Table 3-1786 Configuring a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/cvlan

Data Requirements
Table 3-1787 Configuring the inner VLAN ID range from 10 to 20

Item

Data

Description

Name of a traffic classifier

classifier1

Change the inner VLAN ID range from 10 to 20 in the traffic classifier classifier1.

Start outer VLAN ID

10

End outer VLAN ID

20

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">
    <traffic-classifier>
     <name>classifier1</name>
     <match-condition>
      <named-field>
       <cvlan>
        <start-vlan>10</start-vlan>
        <end-vlan>20</end-vlan>
       </cvlan>
      </named-field>
     </match-condition>
    </traffic-classifier>
   </mqc>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Matching Rule Based on the Inner VLAN ID of QinQ Packets in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier.

Table 3-1788 Modifying a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/cvlan

Data Requirements
Table 3-1789 Changing the inner VLAN ID range from 10-20 to 100-200

Item

Data

Description

Name of a traffic classifier

classifier1

Change the inner VLAN ID range from 10-20 to 100-200 in the traffic classifier classifier1.

Start outer VLAN ID

100

End outer VLAN ID

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <cvlan> 
        <start-vlan>100</start-vlan> 
        <end-vlan>200</end-vlan> 
       </cvlan> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on the Inner VLAN ID of QinQ Packets in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier.

Table 3-1790 Deleting a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/cvlan

Data Requirements
Table 3-1791 Deleting a matching rule based on the inner VLAN ID of QinQ packets in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the inner VLAN ID of QinQ packets in the traffic classifier classifier1.

Start outer VLAN ID

100

End outer VLAN ID

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <cvlan xc:operation="remove"> 
        <start-vlan>100</start-vlan> 
        <end-vlan>200</end-vlan> 
       </cvlan> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Inbound Interface

Configuring a Matching Rule Based on the Inbound Interface in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the inbound interface in a traffic classifier.

Table 3-1792 Configuring a matching rule based on the inbound interface in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/inbound-interface

Data Requirements
Table 3-1793 Configuring a matching rule based on GigabitEthernet0/0/0 in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on GigabitEthernet0/0/0 in the traffic classifier classifier1.

Interface name

GigabitEthernet0/0/0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>GigabitEthernet0/0/0</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <inbound-interface>GigabitEthernet0/0/0</inbound-interface> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Matching Rule Based on the Inbound Interface in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the inbound interface in a traffic classifier.

Table 3-1794 Modifying a matching rule based on the inbound interface in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/inbound-interface

Data Requirements
Table 3-1795 Changing the inbound interface from GigabitEthernet0/0/0 to Ethernet0/0/0

Item

Data

Description

Name of a traffic classifier

classifier1

Change the inbound interface from GigabitEthernet0/0/0 to Ethernet0/0/0 in the traffic classifier classifier1.

Interface name

Ethernet0/0/0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>Ethernet0/0/0</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <inbound-interface>Ethernet0/0/0</inbound-interface> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Matching Rule Based on the Inbound Interface in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the inbound interface in a traffic classifier.

Table 3-1796 Deleting a matching rule based on the inbound interface in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/inbound-interface

Data Requirements
Table 3-1797 Deleting a matching rule based on the inbound interface in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the inbound interface in the traffic classifier classifier1.

Interface name

Ethernet0/0/0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <inbound-interface xc:operation="remove">Ethernet0/0/0</inbound-interface> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Index of a QoS Group

Configuring a Traffic Classifier That Matches the Index of a QoS Group

This section provides a sample of configuring a traffic classifier that matches the index of a QoS group.

Table 3-1798 Configuring a traffic classifier that matches the index of a QoS group

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/qos-group

Data Requirements
Table 3-1799 Configuring a traffic classifier that matches the index of a QoS group

Item

Data

Description

Name of a traffic classifier

cy

Configure a rule matching the index of a QoS group in the range from 10 to 20 in the traffic classifier cy.

Start index of a QoS group

10

End index of a QoS group

20

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>cy</name> 
     <match-condition> 
      <qos-group xc:operation="merge"> 
        <start-group>10</start-group> 
        <end-group>20</end-group> 
      </qos-group> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying a Traffic Classifier That Matches the Index of a QoS Group

This section provides a sample of modifying a traffic classifier that matches the index of a QoS group.

Table 3-1800 Modifying a traffic classifier that matches the index of a QoS group

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/qos-group

Data Requirements
Table 3-1801 Modifying a traffic classifier that matches the index of a QoS group

Item

Data

Description

Name of a traffic classifier

cy

Modify a rule matching the index of a QoS group in the range from 10 to 30 in the traffic classifier cy.

Start index of a QoS group

10

End index of a QoS group

30

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>cy</name> 
     <match-condition> 
      <qos-group xc:operation="merge"> 
        <start-group>10</start-group> 
        <end-group>30</end-group> 
      </qos-group> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Traffic Classifier That Matches the Index of a QoS Group

This section provides a sample of deleting a traffic classifier that matches the index of a QoS group.

Table 3-1802 Deleting a traffic classifier that matches the index of a QoS group

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/qos-group

Data Requirements
Table 3-1803 Deleting a traffic classifier that matches the index of a QoS group

Item

Data

Description

Name of a traffic classifier

cy

Delete a rule matching the index of a QoS group in the traffic classifier cy.

Start index of a QoS group

10

End index of a QoS group

30

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>cy</name> 
     <match-condition> 
      <qos-group xc:operation="remove"> 
        <start-group>10</start-group> 
        <end-group>30</end-group> 
      </qos-group> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the Application Protocol

Configuring a Matching Rule Based on the Application Protocol in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the application protocol in a traffic classifier.

Table 3-1804 Configuring a matching rule based on the application protocol in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/applications/application-name

Data Requirements
Table 3-1805 Configuring a matching rule based on 3adisk in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on 3adisk in the traffic classifier classifier1.

Name of an application protocol

3adisk

NOTE:

Before defining a matching rule based on an application protocol, enable Smart Application Control (SA) and load the signature file.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <security-engine-config xmlns="urn:huawei:params:xml:ns:yang:huawei-security-engine"> 
    <enable-security-engine/> 
   </security-engine-config> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <applications> 
        <application-name>3adisk</application-name> 
       </applications> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply>
Configuring a Matching Rule Based on an Application Protocol in a Traffic Classifier and Setting a Time Range

This section provides a sample of configuring a matching rule based on an application protocol in a traffic classifier and setting a time range.

Table 3-1806 Configuring a matching rule based on an application protocol in a traffic classifier and setting a time range

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/applications

Data Requirements
Table 3-1807 Configuring a matching rule based on the application protocol 3adisk in a traffic classifier and setting a time range

Item

Data

Description

Name of a traffic classifier

classifier1

In the traffic classifier classifier1, configure a matching rule based on the SA application protocol 3adisk, and set the time range name to test2.

Name of an application protocol

3adisk

Name of a time range

test2

NOTE:
  • Before defining a matching rule based on an application protocol, enable the SA function and load the signature file.
  • Ensure the time range has been created before the configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <time-ranges xmlns="urn:huawei:params:xml:ns:yang:huawei-time-range"> 
    <time-range> 
     <vsys>vsys_test</vsys> 
     <name>test2</name> 
     <absolute-time> 
      <start>2018-12-02T13:12:12.1-08:00</start> 
      <end>2018-12-03T13:12:12.1-08:00</end> 
     </absolute-time> 
    </time-range> 
   </time-ranges>  
   <security-engine-config xmlns="urn:huawei:params:xml:ns:yang:huawei-security-engine"> 
    <enable-security-engine/> 
   </security-engine-config> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <applications xc:operation="merge"> 
        <application-name>3adisk</application-name> 
        <time-range>test2</time-range> 
       </applications> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Matching Rule Based on the Application Protocol in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the application protocol in a traffic classifier.

Table 3-1808 Deleting a matching rule based on the application protocol in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/applications/application-name

Data Requirements
Table 3-1809 Deleting a matching rule based on the application protocol in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on 3adisk in the traffic classifier classifier1.

Name of an application protocol

3adisk

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <applications xc:operation="remove"> 
        <application-name>3adisk</application-name> 
       </applications> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching the SA Protocol Group

Configuring a Matching Rule Based on the SA Protocol Group in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the SA protocol group in a traffic classifier.

Table 3-1810 Configuring a matching rule based on the SA protocol group in a traffic classifier

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/categorys/category-name

Data Requirements
Table 3-1811 Configuring a matching rule based on the SA protocol group Database in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on the SA protocol group Database in the traffic classifier classifier1.

Name of an SA protocol group

Database

NOTE:

Before defining a matching rule based on an SA protocol group, enable Smart Application Control (SA) and load the signature file.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <security-engine-config xmlns="urn:huawei:params:xml:ns:yang:huawei-security-engine"> 
    <enable-security-engine/> 
   </security-engine-config> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <protocol-group> 
     <name>Database</name> 
    </protocol-group> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <categorys> 
        <category-name>Database</category-name> 
       </categorys> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Configuring a Matching Rule Based on an SA Protocol Group in a Traffic Classifier and Setting a Time Range

This section provides a sample of configuring a matching rule based on an SA protocol group in a traffic classifier and setting a time range.

Table 3-1812 Configuring a matching rule based on an SA protocol group in a traffic classifier and setting a time range

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/categorys

Data Requirements
Table 3-1813 Configuring a matching rule based on the SA protocol group Database in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

In the traffic classifier classifier1, configure a matching rule based on the SA protocol group Database, and set the time range name to test2.

Name of an SA protocol group

Database

Name of a time range

test2

NOTE:
  • Before defining a matching rule based on an application protocol, enable the SA function and load the signature file.
  • Ensure the time range has been created before the configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <time-ranges xmlns="urn:huawei:params:xml:ns:yang:huawei-time-range"> 
    <time-range> 
     <vsys>vsys_test</vsys> 
     <name>test2</name> 
     <absolute-time> 
      <start>2018-12-02T13:12:12.1-08:00</start> 
      <end>2018-12-03T13:12:12.1-08:00</end> 
     </absolute-time> 
    </time-range> 
   </time-ranges>  
   <security-engine-config xmlns="urn:huawei:params:xml:ns:yang:huawei-security-engine"> 
    <enable-security-engine/> 
   </security-engine-config> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <protocol-group> 
     <name>Database</name> 
    </protocol-group> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <categorys xc:operation="merge"> 
        <category-name>Database</category-name> 
        <time-range>test2</time-range> 
       </categorys> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Matching Rule Based on the SA Protocol Group in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the SA protocol group in a traffic classifier.

Table 3-1814 Deleting a matching rule based on the SA protocol group in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/categorys/category-name

Data Requirements
Table 3-1815 Deleting a matching rule based on the SA protocol group Database

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the SA protocol group Database in the traffic classifier classifier1.

Name of an SA protocol group

Database

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <categorys xc:operation="remove"> 
        <category-name>Database</category-name> 
       </categorys> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Matching Rule Based on a User-defined Protocol Group

Configuring a Matching Rule Based on a User-defined Protocol Group in a Traffic Classifier

This section provides a sample of configuring a matching rule based on a user-defined protocol group in a traffic classifier.

Table 3-1816 Configuring a matching rule based on a user-defined protocol group in a traffic classifier

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/app-groups

Data Requirements
Table 3-1817 Configuring a matching rule based on a user-defined protocol group in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Configure a matching rule based on the user-defined protocol group Group1 in the traffic classifier classifier1.

Name of a user-defined protocol group

Group1

NOTE:
  • Before defining a matching rule based on an application protocol, enable the SA function and load the signature file.
  • Ensure that the user-defined protocol group has been created before the configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier xc:operation="merge"> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <app-groups xc:operation="merge"> 
        <app-group-name>Group1</app-group-name> 
       </app-groups> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Configuring a Matching Rule Based on a User-defined Protocol Group in a Traffic Classifier and Setting a Time Range

This section provides a sample of configuring a matching rule based on a user-defined protocol group in a traffic classifier and setting a time range.

Table 3-1818 Configuring a matching rule based on a user-defined protocol group in a traffic classifier and setting a time range

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/app-groups

Data Requirements
Table 3-1819 Configuring a matching rule based on a user-defined protocol group in a traffic classifier and setting a time range

Item

Data

Description

Name of a traffic classifier

classifier1

In the traffic classifier classifier1, configure a matching rule based on the user-defined protocol group Group1, and set the time range name to test2.

Name of a user-defined protocol group

Group1

Name of a time range

test2

NOTE:
  • Before defining a matching rule based on an application protocol, enable the SA function and load the signature file.
  • Ensure that the user-defined protocol group has been created before the configuration.
  • Ensure the time range has been created before the configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <time-ranges xmlns="urn:huawei:params:xml:ns:yang:huawei-time-range"> 
    <time-range> 
     <vsys>vsys_test</vsys> 
     <name>test2</name> 
     <absolute-time> 
      <start>2018-12-02T13:12:12.1-08:00</start> 
      <end>2018-12-03T13:12:12.1-08:00</end> 
     </absolute-time> 
    </time-range> 
   </time-ranges>  
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier xc:operation="merge"> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <app-groups xc:operation="merge"> 
        <app-group-name>Group1</app-group-name> 
        <time-range>test2</time-range> 
       </app-groups> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Matching Rule Based on a User-defined Protocol Group from a Traffic Classifier

This section provides a sample of deleting a matching rule based on a user-defined protocol group from a traffic classifier.

Table 3-1820 Deleting a matching rule based on a user-defined protocol group from a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/app-groups

Data Requirements
Table 3-1821 Deleting a matching rule based on a user-defined protocol group from a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete the matching rule based on the user-defined protocol group Group1 from the traffic classifier classifier1.

Name of a user-defined protocol group

Group1

NOTE:
  • Before defining a matching rule based on an application protocol, enable the SA function and load the signature file.
  • Ensure that the user-defined protocol group has been created before the configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier xc:operation="merge"> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <app-groups xc:operation="remove"> 
        <app-group-name>Group1</app-group-name> 
       </app-groups> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring a Traffic Behavior

Creating a Traffic Behavior

This section provides a sample of creating a traffic behavior.

Table 3-1822 Creating a traffic behavior

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/name

Data Requirements
Table 3-1823 Creating a traffic behavior named behavior1

Item

Data

Description

Name of a traffic classifier

behavior1

Create a traffic behavior named behavior1.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Traffic Behavior

This section provides a sample of deleting a traffic behavior.

Table 3-1824 Deleting a traffic behavior

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/name

Data Requirements
Table 3-1825 Deleting a traffic behavior named behavior1

Item

Data

Description

Name of a traffic classifier

behavior1

Delete a traffic behavior named behavior1.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour xc:operation="remove"> 
     <name>behavior1</name> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Re-Marking the 802.1p Priority

Creating an Action of Re-Marking the 802.1p Priority

This section provides a sample of creating an action of re-marking the 802.1p priority.

Table 3-1826 Creating an action of re-marking the 802.1p priority

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/remark-dot1p

Data Requirements
Table 3-1827 Creating an action of re-marking the 802.1p priority

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of re-marking the 802.1p priority with 4 in the traffic behavior behavior1.

802.1p priority

4

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <remark-dot1p>4</remark-dot1p> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Re-Marking the 802.1p Priority

This section provides a sample of modifying an action of re-marking the 802.1p priority.

Table 3-1828 Modifying an action of re-marking the 802.1p priority

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/remark-dot1p

Data Requirements
Table 3-1829 Modifying an action of re-marking the 802.1p priority

Item

Data

Description

Name of a traffic behavior

behavior1

Change the re-marked 802.1p priority from 4 to 5 in the traffic behavior behavior1.

802.1p priority

5

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
   <name>behavior1</name> 
     <remark-dot1p>5</remark-dot1p> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Re-Marking the 802.1p Priority

This section provides a sample of deleting an action of re-marking the 802.1p priority.

Table 3-1830 Deleting an action of re-marking the 802.1p priority

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/remark-dot1p

Data Requirements
Table 3-1831 Deleting an action of re-marking the 802.1p priority

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of re-marking the 802.1p priority in the traffic behavior behavior1.

802.1p priority

5

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <remark-dot1p xc:operation="remove">5</remark-dot1p> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Re-Marking the DSCP Priority Name

Creating an Action of Re-Marking the DSCP Priority Name

This section provides a sample of creating an action of re-marking the DSCP priority name.

Table 3-1832 Creating an action of re-marking the DSCP priority name

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/dscp-name

Data Requirements
Table 3-1833 Creating an action of re-marking the DSCP priority name

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of re-marking the DSCP priority with af22 (20) in the traffic behavior behavior1.

DSCP priority name

af22

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-name>af22</dscp-name> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Re-Marking the DSCP Priority Name

This section provides a sample of modifying an action of re-marking the DSCP priority name.

Table 3-1834 Modifying an action of re-marking the DSCP priority name

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/dscp-name

Data Requirements
Table 3-1835 Modifying an action of re-marking the DSCP priority name

Item

Data

Description

Name of a traffic behavior

behavior1

Change the re-marked DSCP priority from af22 (20) to af33 (30) in the traffic behavior behavior1.

DSCP priority name

af33

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-name>af33</dscp-name> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Re-Marking the DSCP Priority Name

This section provides a sample of deleting an action of re-marking the DSCP priority name.

Table 3-1836 Deleting an action of re-marking the DSCP priority name

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/dscp-name

Data Requirements
Table 3-1837 Deleting an action of re-marking the DSCP priority name

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of re-marking the DSCP priority name in the traffic behavior behavior1.

DSCP priority name

af33

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-name xc:operation="remove">af33</dscp-name> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Re-marking the DSCP Priority

Creating an Action of Re-Marking the DSCP Priority

This section provides a sample of creating an action of re-marking the DSCP priority.

Table 3-1838 Creating an action of re-marking the DSCP priority

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/dscp-value

Data Requirements
Table 3-1839 Creating an action of re-marking the DSCP priority

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of re-marking the DSCP priority with 20 in the traffic behavior behavior1.

DSCP priority

20

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-value>20</dscp-value> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Re-Marking the DSCP Priority

This section provides a sample of modifying an action of re-marking the DSCP priority.

Table 3-1840 Modifying an action of re-marking the DSCP priority

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/dscp-value

Data Requirements
Table 3-1841 Modifying an action of re-marking the DSCP priority

Item

Data

Description

Name of a traffic behavior

behavior1

Change the re-marked DSCP priority from 20 to 30 in the traffic behavior behavior1.

DSCP priority

30

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-value>30</dscp-value> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Re-Marking the DSCP Priority

This section provides a sample of deleting an action of re-marking the DSCP priority.

Table 3-1842 Deleting an action of re-marking the DSCP priority

Operation

XPATH

edit-config: remove

huawei-mqc:mqc/traffic-behaviour/dscp-value

Data Requirements
Table 3-1843 Deleting an action of re-marking the DSCP priority

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of re-marking the DSCP priority in the traffic behavior behavior1.

DSCP priority

30

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <dscp-value xc:operation="remove">30</dscp-value> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to the Next-Hop Address

Creating an Action of Redirecting Packets to the Next-Hop Address

This section provides a sample of creating an action of redirecting packets to the next-hop address.

Table 3-1844 Creating an action of redirecting packets to the next-hop address

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

Data Requirements
Table 3-1845 Creating an action of redirecting packets to 10.1.1.1

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of redirecting packets to the next-hop address of 10.1.1.1 in the traffic behavior behavior1.

Next-hop address

10.1.1.1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
      </next-hop> 
     </redirect> 
   </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Next-Hop Address

This section provides a sample of modifying an action of redirecting packets to the next-hop address.

Table 3-1846 Modifying an action of redirecting packets to the next-hop address

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

Data Requirements
Table 3-1847 Changing the next-hop address to 10.1.1.2

Item

Data

Description

Name of a traffic behavior

behavior1

Change the next-hop address to 10.1.1.2 in the traffic behavior behavior1.

Next-hop address

10.1.1.2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.2</next-hop-ip> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Next-Hop Address

This section provides a sample of deleting an action of redirecting packets to the next-hop address.

Table 3-1848 Deleting an action of redirecting packets to the next-hop address

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/next-hop-ip

Data Requirements
Table 3-1849 Deleting an action of redirecting packets to the next-hop address

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of redirecting packets to the next-hop address in the traffic behavior behavior1.

Next-hop address

10.1.1.2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="remove"> 
       <next-hop-ip>10.1.1.2</next-hop-ip> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Creating an Action of Redirecting Packets to the Next-Hop Address and Adding SI/SPI to Packets

This section provides a sample of creating an action of redirecting packets to the next-hop address and adding SI/SPI to packets.

Table 3-1850 Creating an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Operation

XPATH

edit-config:default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/si-index

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/spi-index

Data Requirements
Table 3-1851 Creating an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of redirecting packets to next-hop address 10.1.1.1 in traffic behavior behavior1, and set SI and SPI added to packets to 10 and 100 respectively.

Next-hop address

10.1.1.1

SI value

10

SPI value

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <nsh> 
        <si-index>10</si-index> 
        <spi-index>100</spi-index> 
       </nsh> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Matching Rule Based on the Layer 2 Protocol Type in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the Layer 2 protocol type in a traffic classifier.

Table 3-1852 Deleting a matching rule based on the Layer 2 protocol type in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/l2-protocol-value

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-value-mask/protocol-mask

Data Requirements
Table 3-1853 Deleting a matching rule based on the Layer 2 protocol type in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on the Layer 2 protocol type in the traffic classifier classifier1.

Protocol type value

0x0f0f

Mask of the protocol type value

0xffff

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
 <edit-config>  
  <target>  
  <running/>  
  </target>  
  <error-option>rollback-on-error</error-option>  
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">  
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">  
    <traffic-classifier>  
     <name>classifier1</name>  
     <match-condition>  
      <named-field>  
       <l2-protocol-value-mask xc:operation="remove">  
        <l2-protocol-value>0x0f0f</l2-protocol-value>  
        <protocol-mask>0xffff</protocol-mask> 
       </l2-protocol-value-mask>  
      </named-field>  
     </match-condition>  
    </traffic-classifier>  
   </mqc>  
  </config>  
 </edit-config>  
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply>
Matching the Layer 2 Protocol Type Name
Configuring a Matching Rule Based on the Layer 2 Protocol Type Name in a Traffic Classifier

This section provides a sample of configuring a matching rule based on the Layer 2 protocol type name in a traffic classifier.

Table 3-1854 Configuring a matching rule based on the Layer 2 protocol type name in a traffic classifier

Operation

XPATH

edit-config:default

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-name

Data Requirements
Table 3-1855 Configuring a matching rule based on Layer 2 protocol type arp in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Create a matching rule based on Layer 2 protocol type arp in traffic classifier classifier1.

Protocol type name

arp

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <l2-protocol-name>arp</l2-protocol-name> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Next-Hop Interface for Redirection (Specifying Associated Interface)

Associating an Interface with the Next-Hop IP Address for Redirection

This section provides a sample of associating an interface with the next-hop IP address for redirection.

Table 3-1856 Associating an interface with the next-hop IP address for redirection

Operation

XPATH

edit-config:default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/interface/interface

Data Requirements
Table 3-1857 Associating an interface with the next-hop IP address for redirection

Item

Data

Description

Traffic behavior name

behavior1

In the traffic behavior behavior1, associate GigabitEthernet0/0/4 with the next-hop IP address 10.1.1.1.

Next-hop IP address

10.1.1.1

Interface name

GigabitEthernet0/0/4

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <interface> 
        <interface>GigabitEthernet0/0/4</interface> 
       </interface> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc> 
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying the Interface Associated with the Next-Hop IP Address for Redirection

This section provides a sample of modifying the interface associated with the next-hop IP address for redirection.

Table 3-1858 Modifying the interface associated with the next-hop IP address for redirection

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/interface/interface

Data Requirements
Table 3-1859 Modifying the interface associated with the next-hop IP address for redirection

Item

Data

Description

Traffic behavior name

behavior1

In the traffic behavior behavior1, modify the interface associated with the next-hop IP address 10.1.1.1 to GigabitEthernet0/0/3.

Next-hop IP address

10.1.1.1

Interface name

GigabitEthernet0/0/3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <interface xc:operation="merge"> 
        <interface>GigabitEthernet0/0/3</interface> 
       </interface> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting the Interface Associated with the Next-Hop IP Address for Redirection

This section provides a sample of deleting the interface associated with the next-hop IP address for redirection.

Table 3-1860 Deleting the interface associated with the next-hop IP address for redirection

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/interface/interface

Data Requirements
Table 3-1861 Deleting the interface associated with the next-hop IP address for redirection

Item

Data

Description

Traffic behavior name

behavior1

In the traffic behavior behavior1, delete the interface associated with the next-hop IP address for redirection.

Next-hop IP address

10.1.1.1

Interface name

GigabitEthernet0/0/3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <interface xc:operation="remove"> 
        <interface>GigabitEthernet0/0/3</interface> 
       </interface> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to the Next-Hop Address Associated with an NQA Test Instance

Creating an Action of Redirecting Packets to the Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of creating an action of redirecting packets to the next-hop address associated with an NQA test instance.

Table 3-1862 Creating an action of redirecting packets to the next-hop address associated with an NQA test instance

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-nqa

Data Requirements
Table 3-1863 Creating an action of redirecting packets to the next-hop address associated with an NQA test instance

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of redirecting packets to the next-hop address of 10.1.1.1 that is associated with an NQA test instance test1 with the administrator name jitter1 in the traffic behavior behavior1.

Next-hop address

10.1.1.1

Administrator name of an NQA test instance

jitter1

Name of an NQA test instance

test1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa> 
        <admin-name>jitter1</admin-name> 
        <test-name>test1</test-name> 
       </track-nqa> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of modifying an action of redirecting packets to the next-hop address associated with an NQA test instance.

Table 3-1864 Modifying an action of redirecting packets to the next-hop address associated with an NQA test instance

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-nqa

Data Requirements
Table 3-1865 Modifying an action of redirecting packets to the next-hop address associated with an NQA test instance

Item

Data

Description

Name of a traffic behavior

behavior1

Change the name and administrator name of the NQA test instance to test2 and jitter2 respectively in the traffic behavior behavior1.

Next-hop address

10.1.1.1

Administrator name of an NQA test instance

jitter2

Name of an NQA test instance

test2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa> 
        <admin-name>jitter2</admin-name> 
        <test-name>test2</test-name> 
       </track-nqa> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of deleting an action of redirecting packets to the next-hop address associated with an NQA test instance.

Table 3-1866 Deleting an action of redirecting packets to the next-hop address associated with an NQA test instance

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-nqa

Data Requirements
Table 3-1867 Deleting an action of redirecting packets to the next-hop address associated with an NQA test instance

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of redirecting packets to the next-hop address associated with an NQA test instance in the traffic behavior behavior1.

Next-hop address

10.1.1.1

Administrator name of an NQA test instance

jitter2

Name of an NQA test instance

test2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa xc:operation="remove"> 
        <admin-name>jitter2</admin-name> 
        <test-name>test2</test-name> 
       </track-nqa> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Modifying a Matching Rule Based on the Layer 2 Protocol Type Name in a Traffic Classifier

This section provides a sample of modifying a matching rule based on the Layer 2 protocol type name in a traffic classifier.

Table 3-1868 Modifying a matching rule based on the Layer 2 protocol type name in a traffic classifier

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-name

Data Requirements
Table 3-1869 Modifying a matching rule based on Layer 2 protocol type mpls in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Modify a matching rule based on Layer 2 protocol type mpls in traffic classifier classifier1.

Protocol type name

mpls

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
     <match-condition> 
      <named-field> 
       <l2-protocol-name xc:operation="replace">mpls</l2-protocol-name> 
      </named-field> 
     </match-condition> 
    </traffic-classifier> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply>
Deleting a Matching Rule Based on the Layer 2 Protocol Type Name in a Traffic Classifier

This section provides a sample of deleting a matching rule based on the Layer 2 protocol type name in a traffic classifier.

Table 3-1870 Deleting a matching rule based on the Layer 2 protocol type name in a traffic classifier

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-classifier/match-condition/named-field/l2-protocol-name

Data Requirements
Table 3-1871 Deleting a matching rule based on the Layer 2 protocol type name in a traffic classifier

Item

Data

Description

Name of a traffic classifier

classifier1

Delete a matching rule based on Layer 2 protocol type mpls in traffic classifier classifier1.

Protocol type name

mpls

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
 <edit-config>  
  <target>  
   <running/>  
  </target>  
  <error-option>rollback-on-error</error-option>  
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">  
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">  
    <traffic-classifier>  
     <name>classifier1</name>  
     <match-condition>  
      <named-field>  
       <l2-protocol-value-mask xc:operation="remove">  
        <l2-protocol-value>0x0f0f</l2-protocol-value>  
       </l2-protocol-value-mask>  
      </named-field>  
     </match-condition>  
    </traffic-classifier>  
   </mqc>  
  </config>  
 </edit-config>  
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Next-Hop Address and Adding SI/SPI to Packets

This section provides a sample of modifying an action of redirecting packets to the next-hop address and adding SI/SPI to packets.

Table 3-1872 Modifying an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/si-index

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/spi-index

Data Requirements
Table 3-1873 Modifying an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Item

Data

Description

Name of a traffic behavior

behavior1

Modify an action of redirecting packets in traffic behavior behavior1, and set SI and SPI added to packets to 20 and 200 respectively.

Next-hop address

10.1.1.1

SI value

20

SPI value

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect xc:operation="replace"> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <nsh> 
        <si-index>20</si-index> 
        <spi-index>200</spi-index> 
       </nsh> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Next-Hop Address and Adding SI/SPI to Packets

This section provides a sample of deleting an action of redirecting packets to the next-hop address and adding SI/SPI to packets.

Table 3-1874 Deleting an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/si-index

huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/nsh/spi-index

Data Requirements
Table 3-1875 Deleting an action of redirecting packets to the next-hop address and adding SI/SPI to packets

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of redirecting packets to the next-hop address in traffic behavior behavior1.

Next-hop address

10.1.1.1

SI value

20

SPI value

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect xc:operation="remove"> 
      <next-hop> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <nsh> 
        <si-index>20</si-index> 
        <spi-index>200</spi-index> 
       </nsh> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Redirection to the Next Hop (Monitoring the VRRP Group Status)

Creating Redirection to the Next Hop (Monitoring the VRRP Group Status)

This section describes how to create redirection to the next hop (monitor the VRRP group status).

Table 3-1876 Creating redirection to the next hop (monitoring the VRRP group status)

Operation

XPATH

edit-config:default

/huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-vrrp

Data Requirements
Table 3-1877 Creating redirection to the next hop (monitoring the VRRP group status)

Item

Data

Description

VRID

1

Create redirection to the next hop associated with the VRRP group.

Type and number of an interface associated with a VRRP group

GigabitEthernet0/0/4

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>test1_0</name> 
     <redirect> 
       <next-hop> 
        <next-hop-ip>192.168.2.5</next-hop-ip> 
        <track-vrrp> 
        <vrid>1</vrid> 
        <interface>GigabitEthernet0/0/4</interface> 
       </track-vrrp> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting Redirection to the Next Hop (Monitoring the VRRP Group Status)

This section describes how to delete redirection to the next hop (monitor the VRRP group status).

Table 3-1878 Deleting redirection to the next hop (monitoring the VRRP group status)

Operation

XPATH

edit-config:remove

/huawei-mqc:mqc/traffic-behaviour/redirect/next-hop/track-vrrp

Data Requirements
Table 3-1879 Deleting redirection to the next hop (monitoring the VRRP group status)

Item

Data

Description

VRID

1

Delete redirection to the next hop associated with the VRRP group.

Type and number of an interface associated with a VRRP group

GigabitEthernet0/0/4

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>test1_0</name> 
      <redirect xc:operation="remove"> 
       <next-hop> 
        <next-hop-ip>192.168.2.5</next-hop-ip> 
        <track-vrrp> 
        <vrid>1</vrid> 
        <interface>GigabitEthernet0/0/4</interface> 
       </track-vrrp> 
      </next-hop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to the Outbound Interface

Creating an Action of Redirecting Packets to the Outbound Interface

This section provides a sample of creating an action of redirecting packets to the outbound interface.

Table 3-1880 Creating an action of redirecting packets to the outbound interface

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/interface

Data Requirements
Table 3-1881 Creating an action of redirecting packets to Cellular0/0/0

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of redirecting packets to Cellular0/0/0 in the traffic behavior behavior1.

Interface name

Cellular0/0/0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>Cellular0/0/0</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <interface>Cellular0/0/0</interface> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Outbound Interface

This section provides a sample of modifying an action of redirecting packets to the outbound interface.

Table 3-1882 Modifying an action of redirecting packets to the outbound interface

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/redirect/interface

Data Requirements
Table 3-1883 Modifying an action of redirecting packets to the outbound interface

Item

Data

Description

Name of a traffic behavior

behavior1

Change the outbound interface from Cellular0/0/0 to Cellular0/0/1 in the traffic behavior behavior1.

Interface name

Cellular0/0/1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>Cellular0/0/1</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <interface>Cellular0/0/1</interface> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Outbound Interface

This section provides a sample of deleting an action of redirecting packets to the outbound interface.

Table 3-1884 Deleting an action of redirecting packets to the outbound interface

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/interface

Data Requirements
Table 3-1885 Deleting an action of redirecting packets to the outbound interface

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of redirecting packets to the outbound interface in the traffic behavior behavior1.

Interface name

Cellular0/0/1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <interface xc:operation="remove">Cellular0/0/1</interface> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to a VPN Instance

Creating an Action of Redirecting Packets to a VPN Instance

This section provides a sample of creating an action of redirecting packets to a VPN instance.

Table 3-1886 Creating an action of redirecting packets to a VPN instance

Operation

XPATH

edit-config:default

huawei-mqc/mqc/traffic-behavior/redirect/destination/vpn-instance

Data Requirements
Table 3-1887 Creating an action of redirecting packets to a VPN instance

Item

Data

Description

Name of a traffic behavior

behaviour1

Create an action of redirecting packets to VPN instance vpn_test in traffic behavior behaviour1.

Name of a VPN instance

vpn_test

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">               
    <traffic-behaviour> 
     <name>behaviour1</name> 
     <redirect> 
      <vpn-instance>vpn_test</vpn-instance> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying an Action of Redirecting Packets to a VPN Instance

This section provides a sample of modifying an action of redirecting packets to a VPN instance.

Table 3-1888 Modifying an action of redirecting packets to a VPN instance

Operation

XPATH

edit-config:replace

huawei-mqc/mqc/traffic-behavior/redirect/destination/vpn-instance

Data Requirements
Table 3-1889 Modifying an action of redirecting packets to a VPN instance

Item

Data

Description

Name of a traffic behavior

behaviour1

Modify an action of redirecting packets to VPN instance vpn_test1 in traffic behavior behaviour1.

Name of a VPN instance

vpn_test1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">               
    <traffic-behaviour> 
     <name>behaviour1</name> 
     <redirect xc:operation="replace"> 
      <vpn-instance>vpn_test1</vpn-instance> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting an Action of Redirecting Packets to a VPN Instance

This section provides a sample of deleting an action of redirecting packets to a VPN instance.

Table 3-1890 Deleting an action of redirecting packets to a VPN instance

Operation

XPATH

edit-config:remove

huawei-mqc/mqc/traffic-behavior/redirect/destination/vpn-instance

Data Requirements
Table 3-1891 Deleting an action of redirecting packets to a VPN instance

Item

Data

Description

Name of a traffic behavior

behaviour1

Delete an action of redirecting packets to the VPN instance in traffic behavior behaviour1.

Name of a VPN instance

vpn_test1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
 </target> 
 <error-option>rollback-on-error</error-option> 
   <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
    <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">               
     <traffic-behaviour> 
      <name>behaviour1</name> 
      <redirect xc:operation="remove"> 
       <vpn-instance>vpn_test1</vpn-instance> 
      </redirect> 
     </traffic-behaviour> 
    </mqc> 
   </config> 
  </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to the Backup Next-Hop Address Associating an Interface

Creating an Action of Redirecting Packets to the Backup Next-Hop Address Associating an Interface

This section provides a sample of creating an action of redirecting packets to the backup next-hop address associating an interface.

Table 3-1892 Creating an action of redirecting packets to the backup next-hop address associating an interface

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1893 Creating an action of redirecting packets to the backup next-hop address associating an interface

Item

Data

Description

IP address of the backup next hop

10.1.1.3

In the traffic behavior, redirect packets to the backup next-hop IP address 10.1.1.3. Set the backup next-hop VPN instance name to vpn1, and configure association with GigabitEthernet0/0/1.

VPN instance name

vpn1

Interface name

GigabitEthernet0/0/1

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
      </next-hop>  
      <backup-nexthop xc:operation="merge"> 
       <next-hop-ip>10.1.1.3</next-hop-ip> 
       <vpn-instance>vpn1</vpn-instance> 
       <interface> 
        <interface>GigabitEthernet0/0/1</interface> 
       </interface> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Backup Next-Hop Address Associating an Interface

This section provides a sample of modifying an action of redirecting packets to the backup next-hop address associating an interface.

Table 3-1894 Modifying an action of redirecting packets to the backup next-hop address associating an interface

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1895 Modifying an action of redirecting packets to the backup next-hop address associating an interface

Item

Data

Description

IP address of the backup next hop

10.1.1.4

In the traffic behavior, modify the backup next-hop IP address to which packets are redirected to 10.1.1.4. Modify the backup next-hop VPN instance name to vpn2, and configure association with GigabitEthernet0/0/2.

VPN instance name

vpn2

Interface name

GigabitEthernet0/0/2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
      </next-hop>  
      <backup-nexthop xc:operation="merge"> 
       <next-hop-ip>10.1.1.4</next-hop-ip> 
       <vpn-instance>vpn2</vpn-instance> 
       <interface> 
        <interface>GigabitEthernet0/0/2</interface> 
       </interface> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Backup Next-Hop Address Associating an Interface

This section provides a sample of deleting an action of redirecting packets to the backup next-hop address associating an interface.

Table 3-1896 Deleting an action of redirecting packets to the backup next-hop address associating an interface

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1897 Deleting an action of redirecting packets to the backup next-hop address associating an interface

Item

Data

Description

IP address of the backup next hop

10.1.1.4

Delete the action of redirecting packets to the backup next-hop address from the traffic behavior.

VPN instance name

vpn2

Interface name

GigabitEthernet0/0/2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
      </next-hop>  
      <backup-nexthop xc:operation="remove"> 
       <next-hop-ip>10.1.1.4</next-hop-ip> 
       <vpn-instance>vpn2</vpn-instance> 
       <interface> 
        <interface>GigabitEthernet0/0/2</interface> 
       </interface> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Redirecting Packets to the Backup Next-Hop Address Associated with an NQA Test Instance

Creating an Action of Redirecting Packets to the Backup Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of creating an action of redirecting packets to the backup next-hop address associated with an NQA test instance.

Table 3-1898 Creating an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1899 Creating an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Item

Data

Description

IP address of the backup next hop

10.1.1.3

In the traffic behavior, redirect packets to the backup next-hop IP address 10.1.1.3. Set the backup next-hop VPN instance name to vpn1, the name of the administrator for the NQA test instance to jitter5, and the NQA test instance name to testname5.

VPN instance name

vpn1

Name of the administrator for the NQA test instance

jitter5

Name of the NQA test instance

testname5

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa> 
        <admin-name>jitter2</admin-name> 
        <test-name>testname</test-name> 
       </track-nqa> 
      </next-hop>  
      <backup-nexthop xc:operation="merge"> 
       <next-hop-ip>10.1.1.3</next-hop-ip> 
       <vpn-instance>vpn1</vpn-instance> 
       <track-nqa> 
        <admin-name>jitter5</admin-name> 
        <test-name>testname5</test-name> 
       </track-nqa> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Modifying an Action of Redirecting Packets to the Backup Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of modifying an action of redirecting packets to the backup next-hop address associated with an NQA test instance.

Table 3-1900 Modifying an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1901 Modifying an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Item

Data

Description

IP address of the backup next hop

10.1.1.4

In the traffic behavior, modify the backup next-hop IP address to which packets are redirected to 10.1.1.4. Modify the backup next-hop VPN instance name to vpn2, set the name of the administrator for the NQA test instance to jitter6 and the NQA test instance name to testname6.

VPN instance name

vpn2

Name of the administrator for the NQA test instance

jitter6

Name of the NQA test instance

testname6

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa> 
        <admin-name>jitter2</admin-name> 
        <test-name>testname</test-name> 
       </track-nqa> 
      </next-hop>  
      <backup-nexthop xc:operation="merge"> 
       <next-hop-ip>10.1.1.4</next-hop-ip> 
       <vpn-instance>vpn2</vpn-instance> 
       <track-nqa> 
        <admin-name>jitter6</admin-name> 
        <test-name>testname6</test-name> 
       </track-nqa> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting an Action of Redirecting Packets to the Backup Next-Hop Address Associated with an NQA Test Instance

This section provides a sample of deleting an action of redirecting packets to the backup next-hop address associated with an NQA test instance.

Table 3-1902 Deleting an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/redirect/backup-nexthop

Data Requirements
Table 3-1903 Deleting an action of redirecting packets to the backup next-hop address associated with an NQA test instance

Item

Data

Description

IP address of the backup next hop

10.1.1.4

Delete the action of redirecting packets to the backup next-hop address from the traffic behavior.

VPN instance name

vpn2

Name of the administrator for the NQA test instance

jitter6

Name of the NQA test instance

testname6

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <redirect> 
      <next-hop xc:operation="merge"> 
       <next-hop-ip>10.1.1.1</next-hop-ip> 
       <track-nqa> 
        <admin-name>jitter2</admin-name> 
        <test-name>testname</test-name> 
       </track-nqa> 
      </next-hop>  
      <backup-nexthop xc:operation="remove"> 
       <next-hop-ip>10.1.1.4</next-hop-ip> 
       <vpn-instance>vpn2</vpn-instance> 
       <track-nqa> 
        <admin-name>jitter6</admin-name> 
        <test-name>testname6</test-name> 
       </track-nqa> 
      </backup-nexthop> 
     </redirect> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Binding a Sub Traffic Policy

Creating an Action of Binding a Sub Traffic Policy

This section provides a sample of creating an action of binding a sub traffic policy.

Table 3-1904 Creating an action of binding a sub traffic policy

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/sub-traffic-policy

Data Requirements
Table 3-1905 Creating an action of binding the sub traffic policy policy2

Item

Data

Description

Name of a traffic behavior

behavior1

Create an action of binding the sub traffic policy policy2 in the traffic behavior behavior1.

Name of a traffic policy

policy2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <sub-traffic-policy>policy2</sub-traffic-policy> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an Action of Binding a Sub Traffic Policy

This section provides a sample of modifying an action of binding a sub traffic policy.

Table 3-1906 Modifying an action of binding a sub traffic policy

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/sub-traffic-policy

Data Requirements
Table 3-1907 Modifying an action of binding a sub traffic policy

Item

Data

Description

Name of a traffic behavior

behavior1

Change the sub traffic policy policy2 to policy3 in the traffic behavior behavior1.

Name of a traffic policy

policy3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <sub-traffic-policy>policy3</sub-traffic-policy> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an Action of Binding a Sub Traffic Policy

This section provides a sample of deleting an action of binding a sub traffic policy.

Table 3-1908 Deleting an action of binding a sub traffic policy

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/sub-traffic-policy

Data Requirements
Table 3-1909 Deleting an action of binding a sub traffic policy

Item

Data

Description

Name of a traffic behavior

behavior1

Delete an action of binding the sub traffic policy in the traffic behavior behavior1.

Name of a traffic policy

policy3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <sub-traffic-policy xc:operation="remove">policy3</sub-traffic-policy> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Traffic Shaping

Creating Traffic Shaping

This section provides a sample of creating traffic shaping.

Table 3-1910 Creating traffic shaping

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/gts/cir

Data Requirements
Table 3-1911 Creating traffic shaping

Item

Data

Description

Name of a traffic behavior

behavior1

Create traffic shaping and set the CIR to 200 kbit/s in the traffic behavior behavior1.

CIR

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config>
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <gts> 
      <cir>200</cir> 
     </gts> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying Traffic Shaping

This section provides a sample of modifying traffic shaping.

Table 3-1912 Modifying traffic shaping

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/gts/cir

Data Requirements
Table 3-1913 Modifying traffic shaping

Item

Data

Description

Name of a traffic behavior

behavior1

Change the CIR to 300 kbit/s in the traffic behavior behavior1.

CIR

300

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <gts> 
      <cir>300</cir> 
     </gts> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting Traffic Shaping

This section provides a sample of deleting traffic shaping.

Table 3-1914 Deleting traffic shaping

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/gts/cir

Data Requirements
Table 3-1915 Deleting traffic shaping

Item

Data

Description

Name of a traffic behavior

behavior1

Delete traffic shaping in the traffic behavior behavior1.

CIR

300

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <gts xc:operation="remove"> 
      <cir>300</cir> 
     </gts> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Traffic Shaping by Percentage

Creating a Traffic Shaping Percentage

This section provides a sample of creating a traffic shaping percentage.

Table 3-1916 Creating a traffic shaping percentage

Operation

XPATH

edit-config: merge

huawei-mqc:mqc/traffic-behaviour/gts/pct

Data Requirements
Table 3-1917 Creating a traffic shaping percentage

Item

Data

Description

Percentage of the bandwidth for a type of traffic to the actual available bandwidth

50

Create traffic shaping by percentage and set the percentage to 50%.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <edit-config> 
   <target> 
    <running/> 
   </target> 
  <error-option>rollback-on-error</error-option> 
   <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
    <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
     <traffic-behaviour> 
      <name>test</name> 
      <gts xc:operation="merge"> 
       <pct>50</pct> 
      </gts> 
     </traffic-behaviour> 
    </mqc> 
   </config> 
  </edit-config> 
 </rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying the Traffic Shaping Percentage

This section provides a sample of modifying the traffic shaping percentage.

Table 3-1918 Modifying the traffic shaping percentage

Operation

XPATH

edit-config: merge

huawei-mqc:mqc/traffic-behaviour/gts/pct

Data Requirements
Table 3-1919 Modifying the traffic shaping percentage

Item

Data

Description

Percentage of the bandwidth for a type of traffic to the actual available bandwidth

60

Modify the percentage configured for traffic shaping to 60%.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <edit-config> 
   <target> 
    <running/> 
   </target> 
 <error-option>rollback-on-error</error-option> 
   <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
    <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
     <traffic-behaviour> 
      <name>test</name> 
      <gts xc:operation="merge"> 
       <pct>60</pct> 
      </gts> 
     </traffic-behaviour> 
    </mqc> 
   </config> 
  </edit-config> 
 </rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting the Traffic Shaping Percentage

This section provides a sample of deleting the traffic shaping percentage.

Table 3-1920 Deleting the traffic shaping percentage

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/gts/pct

Data Requirements
Table 3-1921 Deleting the traffic shaping percentage

Item

Data

Description

Percentage of the bandwidth for a type of traffic to the actual available bandwidth

60

Delete the percentage configured for traffic shaping.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <edit-config> 
   <target> 
    <running/> 
   </target> 
   <error-option>rollback-on-error</error-option> 
   <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
    <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
     <traffic-behaviour> 
      <name>test</name> 
      <gts xc:operation="remove"> 
       <pct>60</pct> 
      </gts> 
     </traffic-behaviour> 
    </mqc> 
   </config> 
  </edit-config> 
 </rpc>
Response Example

Sample of successful response

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

Configuring Traffic Policing

Creating Traffic Policing

This section provides a sample of creating traffic policing.

Table 3-1922 Creating traffic policing

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/car/cir

Data Requirements
Table 3-1923 Creating traffic policing

Item

Data

Description

Name of a traffic behavior

behavior1

Create traffic policing and set the CIR to 100 kbit/s in the traffic behavior behavior1.

CIR

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <car> 
      <cir>100</cir> 
     </car> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying Traffic Policing
Table 3-1924 Modifying traffic policing

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/car/cir

Data Requirements
Table 3-1925 Modifying traffic policing

Item

Data

Description

Name of a traffic behavior

behavior1

Change the CIR to 200 kbit/s in the traffic behavior behavior1.

CIR

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <car> 
      <cir>200</cir> 
     </car> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting Traffic Policing
Table 3-1926 Deleting traffic policing

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/car/cir

Data Requirements
Table 3-1927 Deleting traffic policing

Item

Data

Description

Name of a traffic behavior

behavior1

Delete traffic policing in the traffic behavior behavior1.

CIR

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
   <name>behavior1</name> 
     <car xc:operation="remove"> 
      <cir>200</cir> 
     </car> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Percentage-based Traffic Policing

Creating a Percentage-based Traffic Policing Action

This section provides a sample of creating a percentage-based traffic policing action.

Table 3-1928 Creating a percentage-based traffic policing action

Operation

XPATH

edit-config:merge

huawei-mqc:mqc/traffic-behaviour/car/pct

Data Requirements
Table 3-1929 Creating a percentage-based traffic policing action

Item

Data

Description

Percentage of the PIR value to the interface bandwidth

96

Create a percentage-based traffic policing action in a traffic behavior. Set the percentage of the PIR value to the interface bandwidth to 96%.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">
    <traffic-behaviour>
     <name>cy</name>
     <car xc:operation="merge">
      <pct>96</pct>
     </car>
    </traffic-behaviour>
   </mqc>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying a Percentage-based Traffic Policing Action

This section provides a sample of modifying a percentage-based traffic policing action.

Table 3-1930 Modifying a percentage-based traffic policing action

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-behaviour/car/pct

Data Requirements
Table 3-1931 Modifying a percentage-based traffic policing action

Item

Data

Description

Percentage of the PIR value to the interface bandwidth

99

Modify the percentage of the PIR value to the interface bandwidth to 99% for a percentage-based traffic policing action in a traffic behavior.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">
    <traffic-behaviour>
     <name>cy</name>
     <car xc:operation="replace">
      <pct>99</pct>
     </car>
    </traffic-behaviour>
   </mqc>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Percentage-based Traffic Policing Action

This section provides a sample of deleting a percentage-based traffic policing action.

Table 3-1932 Deleting a percentage-based traffic policing action

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/car/pct

Data Requirements
Table 3-1933 Deleting a percentage-based traffic policing action

Item

Data

Description

Percentage of the PIR value to the interface bandwidth

-

Delete a traffic policing action from a traffic behavior.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">
    <traffic-behaviour>
     <name>cy</name>
     <car xc:operation="remove">
     </car>
    </traffic-behaviour>
   </mqc>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

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

Configuring Congestion Management (EF)

Creating an EF Queue

This section provides a sample of creating an EF queue.

Table 3-1934 Creating an EF queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/ef/bandwidth

Data Requirements
Table 3-1935 Creating an EF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Create an EF queue and set the maximum bandwidth to 100 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for EF queues

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <ef> 
      <bandwidth>100</bandwidth> 
     </ef> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an EF Queue

This section provides a sample of modifying an EF queue.

Table 3-1936 Modifying an EF queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/ef/bandwidth

Data Requirements
Table 3-1937 Modifying an EF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Change the maximum bandwidth to 200 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for EF queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <ef> 
      <bandwidth>200</bandwidth> 
     </ef> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an EF Queue

This section provides a sample of deleting an EF queue.

Table 3-1938 Deleting an EF queue

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/ef/bandwidth

Data Requirements
Table 3-1939 Deleting an EF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Delete the EF queue in the traffic behavior behavior1.

Maximum bandwidth for EF queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <ef xc:operation="remove"> 
      <bandwidth>200</bandwidth> 
     </ef> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Congestion Management (AF)

Creating an AF Queue

This section provides a sample of creating an AF queue.

Table 3-1940 Creating an AF queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/af/bandwidth

Data Requirements
Table 3-1941 Creating an AF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Create an AF queue and set the maximum bandwidth to 100 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for AF queues

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <ef> 
      <bandwidth>100</bandwidth> 
     </ef> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an AF Queue

This section provides a sample of modifying an AF queue.

Table 3-1942 Modifying an AF queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/af/bandwidth

Data Requirements
Table 3-1943 Modifying an AF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Change the maximum bandwidth to 200 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for AF queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <af> 
      <bandwidth>200</bandwidth> 
     </af> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <ok/> 
</rpc-reply> 
Deleting an AF Queue

This section provides a sample of deleting an AF queue.

Table 3-1944 Deleting an AF queue

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/af/bandwidth

Data Requirements
Table 3-1945 Deleting an AF queue

Item

Data

Description

Name of a traffic behavior

behavior1

Delete the AF queue in the traffic behavior behavior1.

Maximum bandwidth for AF queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <af xc:operation="remove"> 
      <bandwidth>200</bandwidth> 
     </af> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Congestion Management (LLQ)

Creating an LLQ Queue

This section provides a sample of creating an LLQ queue.

Table 3-1946 Creating an LLQ queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/llq/bandwidth

Data Requirements
Table 3-1947 Creating an LLQ queue

Item

Data

Description

Name of a traffic behavior

behavior1

Create an LLQ queue and set the maximum bandwidth to 100 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for LLQ queues

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <llq> 
      <bandwidth>100</bandwidth> 
     </llq> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying an LLQ Queue

This section provides a sample of modifying an LLQ queue.

Table 3-1948 Modifying an LLQ queue

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/llq/bandwidth

Data Requirements
Table 3-1949 Modifying an LLQ queue

Item

Data

Description

Name of a traffic behavior

behavior1

Change the maximum bandwidth to 200 kbit/s in the traffic behavior behavior1.

Maximum bandwidth for LLQ queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <llq> 
      <bandwidth>200</bandwidth> 
     </llq> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting an LLQ Queue

This section provides a sample of deleting an LLQ queue.

Table 3-1950 Deleting an LLQ queue

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/llq/bandwidth

Data Requirements
Table 3-1951 Deleting an LLQ queue

Item

Data

Description

Name of a traffic behavior

behavior1

Delete the LLQ queue in the traffic behavior behavior1.

Maximum bandwidth for LLQ queues

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <llq xc:operation="remove"> 
      <bandwidth>200</bandwidth> 
     </llq> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Sending Packets Matching the Default Traffic Classifier to BE Queues in WFQ Mode

Configuring an Action of Sending Packets Matching the Default Traffic Classifier to BE Queues in WFQ Mode

This section provides a sample of configuring an action of sending packets matching the default traffic classifier to BE queues in WFQ mode.

Table 3-1952 Configuring an action of sending packets matching the default traffic classifier to BE queues in WFQ mode

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/wfq/wfq

Data Requirements
Table 3-1953 Configuring an action of sending packets matching the default traffic classifier to BE queues in WFQ mode

Item

Data

Description

Name of a traffic behavior

behavior1

Configure an action of sending packets matching the default traffic classifier to BE queues in WFQ mode in the traffic behavior behavior1.

WFQ

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <wfq> 
      <wfq/> 
     </wfq> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Canceling an Action of Sending Packets Matching the Default Traffic Classifier to BE Queues in WFQ Mode

This section provides a sample of canceling an action of sending packets matching the default traffic classifier to BE queues in WFQ mode.

Table 3-1954 Canceling an action of sending packets matching the default traffic classifier to BE queues in WFQ mode

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/wfq/wfq

Data Requirements
Table 3-1955 Canceling an action of sending packets matching the default traffic classifier to BE queues in WFQ mode

Item

Data

Description

Name of a traffic behavior

behavior1

Cancel an action of sending packets matching the default traffic classifier to BE queues in WFQ mode in the traffic behavior behavior1.

WFQ

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <wfq xc:operation="remove"> 
      <wfq/> 
     </wfq> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring Packet Filtering

Creating Packet Filtering

This section provides a sample of creating packet filtering.

Table 3-1956 Creating packet filtering

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/action

Data Requirements
Table 3-1957 Creating packet filtering

Item

Data

Description

Name of a traffic behavior

behavior1

Set the packet filtering rule to permit in the traffic behavior behavior1.

Packet filtering rule

permit

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <action>permit</action> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying Packet Filtering

This section provides a sample of modifying packet filtering.

Table 3-1958 Modifying packet filtering

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-behaviour/action

Data Requirements
Table 3-1959 Modifying packet filtering

Item

Data

Description

Name of a traffic behavior

behavior1

Change the packet filtering rule to deny in the traffic behavior behavior1.

Packet filtering rule

deny

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <action>deny</action> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting Packet Filtering

This section provides a sample of deleting packet filtering.

Table 3-1960 Deleting packet filtering

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-behaviour/action

Data Requirements
Table 3-1961 Deleting packet filtering

Item

Data

Description

Name of a traffic behavior

behavior1

Delete the packet filtering rule in the traffic behavior behavior1.

Packet filtering rule

deny

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-behaviour> 
     <name>behavior1</name> 
     <action xc:operation="remove">deny</action> 
    </traffic-behaviour> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring a Traffic Policy

Creating a Traffic Policy

This section provides a sample of creating a traffic policy.

Table 3-1962 Creating a traffic policy

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-policy

Data Requirements
Table 3-1963 Creating a traffic policy named policy1

Item

Data

Description

Name of a traffic policy

policy1

Create a traffic policy named policy1 and set the matching mode of traffic classifiers to extended.

Matching mode of traffic classifiers in a traffic policy

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-policy> 
     <name>policy1</name> 
     <match-extended>true</match-extended> 
    </traffic-policy> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Traffic Policy

This section provides a sample of deleting a traffic policy.

Table 3-1964 Deleting a traffic policy

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-policy

Data Requirements
Table 3-1965 Deleting a traffic policy

Item

Data

Description

Name of a traffic policy

policy1

Delete a traffic policy named policy1.

Matching mode of traffic classifiers in a traffic policy

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-policy xc:operation="remove"> 
     <name>policy1</name> 
     <match-extended>true</match-extended> 
    </traffic-policy> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Binding a Traffic Classifier and a Traffic Behavior to a Traffic Policy

Binding a Traffic Classifier and a Traffic Behavior to a Traffic Policy

This section provides a sample of binding a traffic classifier and a traffic behavior to a traffic policy.

Table 3-1966 Binding a traffic classifier and a traffic behavior to a traffic policy

Operation

XPATH

edit-config: default

huawei-mqc:mqc/traffic-policy/rule

Data Requirements
Table 3-1967 Binding a traffic classifier and a traffic behavior to a traffic policy

Item

Data

Description

Name of a traffic classifier

classifier1

Bind the traffic classifier classifier1 and traffic behavior behaviour1 to the traffic policy policy1, and set the priority of the bound traffic classifier and traffic behavior to 200.

Name of a traffic behavior

behaviour1

Name of a traffic policy

policy1

Priority of the bound traffic classifier and traffic behavior

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>behaviour1</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>policy1</name> 
     <rule> 
      <traffic-classifier>classifier1</traffic-classifier> 
      <traffic-behaviour>behaviour1</traffic-behaviour> 
      <precedence>200</precedence>
     </rule> 
    </traffic-policy> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Modifying the Traffic Classifier and Traffic Behavior from the Traffic Policy

This section provides a sample of modifying the traffic classifier and traffic behavior from the traffic policy.

Table 3-1968 Modifying the traffic classifier and traffic behavior from the traffic policy

Operation

XPATH

edit-config:replace

huawei-mqc:mqc/traffic-policy/rule

Data Requirements
Table 3-1969 Modifying the traffic classifier and traffic behavior from the traffic policy

Item

Data

Description

Name of a traffic classifier

classifier1

Modify the priority of the bound traffic classifier and traffic behavior to 100 in the traffic policy policy1.

Name of a traffic behavior

behaviour1

Name of a traffic policy

policy1

Priority of the bound traffic classifier and traffic behavior

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>behaviour1</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>policy1</name> 
     <rule xc:operation="replace"> 
      <traffic-classifier>classifier1</traffic-classifier> 
      <traffic-behaviour>behaviour1</traffic-behaviour>
      <precedence>100</precedence> 
     </rule> 
    </traffic-policy> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Unbinding the Traffic Classifier and Traffic Behavior from the Traffic Policy

This section provides a sample of unbinding the traffic classifier and traffic behavior from the traffic policy.

Table 3-1970 Unbinding the traffic classifier and traffic behavior from the traffic policy

Operation

XPATH

edit-config:remove

huawei-mqc:mqc/traffic-policy/rule

Data Requirements
Table 3-1971 Unbinding the traffic classifier and traffic behavior from the traffic policy

Item

Data

Description

Name of a traffic classifier

classifier1

Unbind the traffic classifier classifier1 and traffic behavior behaviour1 from the traffic policy policy1.

Name of a traffic behavior

behaviour1

Name of a traffic policy

policy1

Priority of the bound traffic classifier and traffic behavior

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>behaviour1</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>policy1</name> 
     <rule xc:operation="remove"> 
      <traffic-classifier>classifier1</traffic-classifier> 
      <traffic-behaviour>behaviour1</traffic-behaviour> 
      <precedence>100</precedence>
     </rule> 
    </traffic-policy> 
   </mqc> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Applying Traffic Policies

Applying a Traffic Policy

This section provides a sample of applying a traffic policy to an interface.

Table 3-1972 Applying a traffic policy to an interface

Operation

XPATH

edit-config: default

huawei-mqc-apply:mqc-apply/traffic-policy-apply

Data Requirements
Table 3-1973 Applying a traffic policy to GigabitEthernet0/0/0

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Apply the traffic policy policy1 to GigabitEthernet0/0/0 in inbound and outbound directions.

Name of a traffic policy

policy1

inbound

-

outbound

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
   <name>GigabitEthernet0/0/0</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>classifier1</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>behaviour1</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>policy1</name> 
     <match-extended>true</match-extended> 
     <rule> 
      <traffic-classifier>classifier1</traffic-classifier> 
      <traffic-behaviour>behaviour1</traffic-behaviour> 
     </rule> 
    </traffic-policy> 
   </mqc> 
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply"> 
    <traffic-policy-apply> 
     <name>policy1</name> 
     <interface> 
      <name>GigabitEthernet0/0/0</name> 
      <inbound/> 
      <outbound/> 
     </interface> 
    </traffic-policy-apply> 
   </mqc-apply> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Traffic Policy from an Interface

This section provides a sample of deleting a traffic policy from an interface.

Table 3-1974 Deleting a traffic policy from an interface

Operation

XPATH

edit-config:remove

huawei-mqc-apply:mqc-apply/traffic-policy-apply

Data Requirements
Table 3-1975 Deleting a traffic policy from GigabitEthernet0/0/0

Item

Data

Description

Name of a traffic policy

policy1

Delete the traffic policy policy1 from GigabitEthernet0/0/0 in inbound and outbound directions.

Interface name

GigabitEthernet0/0/0

inbound

-

outbound

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply"> 
    <traffic-policy-apply xc:operation="remove"> 
     <name>policy1</name> 
     <interface> 
      <name>GigabitEthernet0/0/0</name> 
      <inbound/> 
      <outbound/> 
     </interface> 
    </traffic-policy-apply> 
   </mqc-apply> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Applying a Preprocessing Traffic Policy

This section provides a sample of applying a preprocessing traffic policy.

Table 3-1976 Applying a preprocessing traffic policy to an interface

Operation

XPATH

edit-config:merge

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-preprocess

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-preprocess

Data Requirements
Table 3-1977 Applying a preprocessing traffic policy to GigabitEthernet0/0/0

Item

Data

Description

Name of the preprocessing traffic policy

policy-pre

Apply the preprocessing traffic policy policy-pre to the inbound and outbound directions of GigabitEthernet0/0/0.

Interface name

GigabitEthernet0/0/0

inbound-preprocess

-

outbound-preprocess

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
    <interface>
     <name>GigabitEthernet0/0/0</name>
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type>
    </interface>
   </interfaces>
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc">
    <traffic-classifier>
     <name>classifier-pre</name>
    </traffic-classifier>
    <traffic-behaviour>
     <name>behaviour-pre</name>
    </traffic-behaviour>
    <traffic-policy>
     <name>policy-pre</name>
     <match-extended>true</match-extended>
     <rule>
      <traffic-classifier>classifier-pre</traffic-classifier>
      <traffic-behaviour>behaviour-pre</traffic-behaviour>
     </rule>
    </traffic-policy>
   </mqc>
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply">
    <traffic-policy-apply>
     <name>policy-pre</name>
     <interface>
      <name>GigabitEthernet0/0/0</name>
      <inbound-preprocess xc:operation="merge"/>
      <outbound-preprocess xc:operation="merge"/>
     </interface>
    </traffic-policy-apply>
   </mqc-apply>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Deleting a Preprocessing Traffic Policy from an Interface

This section provides a sample of deleting a preprocessing traffic policy from an interface.

Table 3-1978 Deleting a preprocessing traffic policy from an interface

Operation

XPATH

edit-config:remove

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-preprocess

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-preprocess

Data Requirements
Table 3-1979 Deleting the preprocessing traffic policy applied to GigabitEthernet0/0/0

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Delete the preprocessing traffic policy from the inbound and outbound directions of GigabitEthernet0/0/0.

inbound-preprocess

-

outbound-preprocess

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply">
    <traffic-policy-apply>
     <name>policy-pre</name>
     <interface>
      <name>GigabitEthernet0/0/0</name>
      <inbound-preprocess xc:operation="remove"/>
      <outbound-preprocess xc:operation="remove"/>
     </interface>
    </traffic-policy-apply>
   </mqc-apply>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
  <ok/> 
</rpc-reply> 
Applying a Preferential Processing Traffic Policy
NOTE:

Only V300R003C00 supports the preferential processing traffic policy.

This section provides a sample of applying a preferential processing traffic policy.

Table 3-1980 Applying a preferential processing traffic policy to an interface

Operation

XPATH

edit-config:merge

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-firstprocess

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-firstprocess

Data Requirements
Table 3-1981 Applying a preferential processing traffic policy to GigabitEthernet0/0/4

Item

Data

Description

Name of the preferential processing traffic policy

cy

Apply the preferential processing traffic policy cy to the inbound and outbound directions of GigabitEthernet0/0/4.

NOTICE:

A preferential processing traffic policy can be applied only to Layer 3 interfaces.

Interface name

GigabitEthernet0/0/4

inbound-firstprocess

-

outbound-firstprocess

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>GigabitEthernet0/0/4</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>cy</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>cy</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>cy</name> 
     <match-extended>true</match-extended> 
     <rule> 
      <traffic-classifier>cy</traffic-classifier> 
      <traffic-behaviour>cy</traffic-behaviour> 
     </rule> 
    </traffic-policy> 
   </mqc> 
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply"> 
    <traffic-policy-apply> 
     <name>cy</name> 
     <interface> 
      <name>GigabitEthernet0/0/4</name> 
      <inbound-firstprocess xc:operation="merge"/> 
      <outbound-firstprocess xc:operation="merge"/> 
     </interface> 
    </traffic-policy-apply> 
   </mqc-apply> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Deleting a Preferential Processing Traffic Policy

This section provides a sample of deleting a preferential processing traffic policy from an interface.

Table 3-1982 Deleting a preferential processing traffic policy from an interface

Operation

XPATH

edit-config:remove

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/inbound-firstprocess

huawei-mqc-apply:mqc-apply/traffic-policy-apply/interface/outbound-firstprocess

Data Requirements
Table 3-1983 Deleting the preferential processing traffic policy from GigabitEthernet0/0/4

Item

Data

Description

Interface name

GigabitEthernet0/0/4

Delete the preferential processing traffic policy from the inbound and outbound directions of GigabitEthernet0/0/4.

inbound-firstprocess

-

outbound-firstprocess

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> 
    <interface> 
     <name>GigabitEthernet0/0/4</name> 
     <type xmlns:iana="urn:ietf:params:xml:ns:yang:iana-if-type">iana:ethernetCsmacd</type> 
    </interface> 
   </interfaces> 
   <mqc xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc"> 
    <traffic-classifier> 
     <name>cy</name> 
    </traffic-classifier> 
    <traffic-behaviour> 
     <name>cy</name> 
    </traffic-behaviour> 
    <traffic-policy> 
     <name>cy</name> 
     <match-extended>true</match-extended> 
     <rule> 
      <traffic-classifier>cy</traffic-classifier> 
      <traffic-behaviour>cy</traffic-behaviour> 
     </rule> 
    </traffic-policy> 
   </mqc> 
   <mqc-apply xmlns="urn:huawei:params:xml:ns:yang:huawei-mqc-apply"> 
    <traffic-policy-apply> 
     <name>cy</name> 
     <interface> 
      <name>GigabitEthernet0/0/4</name> 
      <inbound-firstprocess xc:operation="remove"/> 
      <outbound-firstprocess xc:operation="remove"/> 
     </interface> 
    </traffic-policy-apply> 
   </mqc-apply> 
  </config> 
 </edit-config> 
</rpc>    
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_5ee00fa0ad45400183e13c78171e3cca">  
  <ok/>  
</rpc-reply> 
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100022096

Views: 8430

Downloads: 69

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next