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).
QoS

QoS

Data Model

The data model file matching QoS is huawei-qos.yang.

Table 3-1711 QoS

Object

Description

ietf-interfaces:interfaces/interface/huawei-qos:qos

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

ietf-interfaces:interfaces/interface/huawei-qos:qos/shaping/cir

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

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter/inbound

Indicates that inbound traffic policing is configured on a specified interface.

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter/outbound

Indicates that outbound traffic policing is configured on a specified interface.

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter/cir

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

ietf-interfaces:interfaces/ietf-interfaces:interface/huawei-qos:qos/group

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

NOTE:

This object can be configured only on a tunnel interface.

Traffic Shaping Configuration

Configuring Traffic Shaping on an Interface

This section provides a sample of configuring traffic shaping on an interface.

Table 3-1712 Configuring traffic shaping on an interface

Operation

XPATH

edit-config: default

ietf-interfaces:interfaces/interface/huawei-qos:qos/shaping

Data Requirements
Table 3-1713 Configuring traffic shaping on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Configure traffic shaping on GigabitEthernet0/0/0 and set the CIR to 2000 kbit/s.

CIR

2000

NOTE:
  • LAN interfaces of the AR100&AR120&AR150&AR160&AR200&AR1200 series do not support this configuration.
  • 9ES2, 4GE-2S, 4ES2G-S and 4E2GP-S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <shaping> 
       <cir>2000</cir> 
      </shaping> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 
Modifying Traffic Shaping on an Interface

This section provides a sample of modifying traffic shaping on an interface.

Table 3-1714 Modifying traffic shaping on an interface

Operation

XPATH

edit-config: replace

ietf-interfaces:interfaces/interface/huawei-qos:qos/shaping

Data Requirements
Table 3-1715 Modifying traffic shaping on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Change the CIR for traffic shaping on GigabitEthernet0/0/0 to 3000 kbit/s.

CIR

3000

NOTE:
  • LAN interfaces of the AR100&AR120&AR150&AR160&AR200&AR1200 series do not support this configuration.
  • 9ES2, 4GE-2S, 4ES2G-S and 4E2GP-S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <shaping xc:operation="replace"> 
       <cir>3000</cir> 
      </shaping> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 
Deleting Traffic Shaping on an Interface

This section provides a sample of deleting traffic shaping on an interface.

Table 3-1716 Deleting traffic shaping on an interface

Operation

XPATH

edit-config: remove

ietf-interfaces:interfaces/interface/huawei-qos:qos/shaping

Data Requirements
Table 3-1717 Deleting traffic shaping on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Delete traffic shaping on GigabitEthernet0/0/0.

CIR

3000

NOTE:
  • LAN interfaces of the AR100&AR120&AR150&AR160&AR200&AR1200 series do not support this configuration.
  • 9ES2, 4GE-2S, 4ES2G-S and 4E2GP-S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <shaping xc:operation="remove"> 
       <cir>3000</cir> 
      </shaping> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 

Traffic Policing Configuration

Configuring Traffic Policing on an Interface

This section provides a sample of configuring traffic policing on an interface.

Table 3-1718 Configuring traffic policing on an interface

Operation

XPATH

edit-config: default

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter

Data Requirements
Table 3-1719 Configuring traffic policing on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Configure traffic policing on GigabitEthernet 0/0/0 in the inbound direction and set the CIR to 5000 kbit/s.

CIR

5000

inbound

-

NOTE:
  • LAN interfaces of the AR100&AR120 series, AR161, AR161W, AR169, AR161G-L, AR161G-Lc, AR161EW, AR161EW-M1, AR161G-U, AR169G-L, AR169EW, AR169CVW, AR169CVW-4B4S, AR169EGW-L, AR169W-P-M9, AR169RW-P-M9, AR169-P-M9, AR1220E, AR1220EV and AR1220EVW do not support this configuration.
  • The 4GE-2S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <meter> 
       <cir>5000</cir> 
       <inbound/> 
      </meter> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 
Modifying Traffic Policing on an Interface

This section provides a sample of modifying traffic policing on an interface.

Table 3-1720 Modifying traffic policing on an interface

Operation

XPATH

edit-config: replace

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter

Data Requirements
Table 3-1721 Modifying traffic policing on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Configure traffic policing on GigabitEthernet 0/0/0 in the outbound direction and set the CIR to 3000 kbit/s.

CIR

3000

outbound

-

NOTE:
  • LAN interfaces of the AR100&AR120 series, AR161, AR161W, AR169, AR161G-L, AR161G-Lc, AR161EW, AR161EW-M1, AR161G-U, AR169G-L, AR169EW, AR169CVW, AR169CVW-4B4S, AR169EGW-L, AR169W-P-M9, AR169RW-P-M9, AR169-P-M9, AR1220E, AR1220EV and AR1220EVW do not support this configuration.
  • The 4GE-2S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <meter xc:operation="replace"> 
       <cir>3000</cir> 
       <outbound/> 
      </meter> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 
Deleting Traffic Policing on an Interface

This section provides a sample of deleting traffic policing on an interface.

Table 3-1722 Deleting traffic policing on an interface

Operation

XPATH

edit-config: remove

ietf-interfaces:interfaces/interface/huawei-qos:qos/meter

Data Requirements
Table 3-1723 Deleting traffic policing on an interface

Item

Data

Description

Interface name

GigabitEthernet0/0/0

Delete traffic policing on GigabitEthernet 0/0/0 in the outbound direction

CIR

3000

outbound

-

NOTE:
  • LAN interfaces of the AR100&AR120 series, AR161, AR161W, AR169, AR161G-L, AR161G-Lc, AR161EW, AR161EW-M1, AR161G-U, AR169G-L, AR169EW, AR169CVW, AR169CVW-4B4S, AR169EGW-L, AR169W-P-M9, AR169RW-P-M9, AR169-P-M9, AR1220E, AR1220EV and AR1220EVW do not support this configuration.
  • The 4GE-2S card does not support this configuration.
Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <meter xc:operation="remove"> 
       <cir>3000</cir> 
       <outbound/> 
      </meter> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
  <ok/> 
</rpc-reply> 

Configuration of the QoS Group to Which the Packet Belongs

Configuring the QoS Group to Which the Packet Belongs

This section provides a sample of configuring the QoS group to which the packet belongs.

Table 3-1724 Configuring the QoS group to which the packets belongs

Operation

XPATH

edit-config:default

ietf-interfaces:interfaces/ietf-interfaces:interface/huawei-qos:qos/group

Data Requirements
Table 3-1725 Configuring the QoS group to which the packet belongs

Item

Data

Description

Interface name

Tunnel0/0/0

Set the index of the QoS group to which the packet belongs to 8 on Tunnel0/0/0.

Index of the QoS group to which the packet belongs

8

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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>Tunnel0/0/0</name> 
     <type xmlns:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos"> 
      <group>8</group> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96">  
  <ok/>  
</rpc-reply> 
Deleting the QoS Group to Which the Packet Belongs

This section provides a sample of deleting the QoS group to which the packet belongs.

Table 3-1726 Deleting the QoS group to which the packet belongs

Operation

XPATH

edit-config:remove

ietf-interfaces:interfaces/ietf-interfaces:interface/huawei-qos:qos/group

Data Requirements
Table 3-1727 Deleting the QoS group to which the packet belongs

Item

Data

Description

Interface name

Tunnel0/0/0

Delete the QoS group to which the packet belongs on Tunnel0/0/0.

Index of the QoS group to which the packet belongs

8

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96"> 
 <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>Tunnel0/0/0</name> 
     <type xmlns:x="urn:ietf:params:xml:ns:yang:iana-if-type">x:ethernetCsmacd</type> 
     <qos xmlns="urn:huawei:params:xml:ns:yang:huawei-qos" xc:operation="remove"> 
      <group>8</group> 
     </qos> 
    </interface> 
   </interfaces> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="l2vpn-2102114484P0F5000013-c02d58d2-7a3c-40f3-8be8-b71d47919e96">  
  <ok/>  
</rpc-reply> 
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100022096

Views: 8295

Downloads: 69

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next