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

BGP

Data Model

The data model files matching BGP are ietf-routing.yang and huawei-bgp.yang.

Table 3-532 BGP

Object

Description

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router

Indicates that the operation request (creating, deleting, and modifying) object is the BGP-related configurations. It is only used to contain sub-objects, but does not have any data meaning.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/local-as-number

Indicates the number of the local AS. The value is an integer that ranges from 1 to 4294967295.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/router-id/ip-address

Indicates the IP address of the BGP route.

The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/enable

Indicates that the GR function of BGP routes is enabled.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/restart-time

Indicates the maximum waiting time for a BGP session to be reestablished after the remote end discovers the restart of the local end. The value is an integer ranging from 1 to 3600, in seconds. The default value is 150.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/external

Indicates the external priority of BGP routing protocols. The value is an integer ranging from 1 to 255. The smaller the value is, the higher the preference is.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/internal

Indicates the internal priority of BGP routing protocols. The value is an integer ranging from 1 to 255. The smaller the value is, the higher the preference is.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/local

Indicates the local priority of BGP routing protocols. The value is an integer ranging from 1 to 255. The smaller the value is, the higher the preference is.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-ip-address

Indicates the IPv4 address of the BGP aggregation route. The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-prefix-length

Indicates that the network mask length is specified for an aggregation route. The value is an integer that ranges from 0 to 32.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-netmask

Indicates that the network mask is specified for an aggregation route. The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/as-set-falg

Indicates the AS-SET flag of a BGP aggregation route. The value is of the Boolean type and can be true or false. The default value is false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/import-protocol

Indicates the imported route type and routing protocol whose routes are imported. The value is of the enumerated type and can be direct, isis, ospf, static, or unr.

NOTE:

If this parameter is set to isis or ospf, a process ID must be specified.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/import-route-policy

Indicates that routes are filtered and route attributes are modified using the route-policy specified based on this parameter when these routes are imported from other routing protocols. The value is a string of 1 to 40 case-sensitive characters without spaces. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/med-for-route

Indicates the MED value of an imported route. The value is an integer that ranges from 0 to 4294967295.

ietf-routing:routing/ietf-routing:routing-instance/ietf-routing:routing-protocols/ietf-routing:routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/ospf/ospf-id

Indicates an OSPF process ID. The value is an integer that ranges from 1 to 65535.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/ospf/import-route-policy

Indicates that routes are filtered and route attributes are modified using the route-policy specified based on this parameter when these routes are imported from other routing protocols. The value is a string of 1 to 40 case-sensitive characters without spaces. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/ospf/med-for-route

Indicates the MED value of an imported OSPF route. The value is an integer that ranges from 0 to 4294967295.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/isis/isis-id

Indicates an IS-IS process ID. The value is an integer that ranges from 1 to 65535.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/isis/import-route-policy

Indicates that routes are filtered and route attributes are modified using the route-policy specified based on this parameter when these routes are imported from other routing protocols. The value is a string of 1 to 40 case-sensitive characters without spaces. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route/isis/med-for-route

Indicates the MED value of an imported IS-IS route. The value is an integer that ranges from 0 to 4294967295.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/cluster-id

Indicates the cluster ID of an RR. The value is an integer that ranges from 1 to 4294967295.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/peer-address

Indicates the remote IP addresses of IPv4 peers. The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/remote-as

Indicates the remote AS numbers of IPv4 peers. The value is an integer that ranges from 1 to 4294967295.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/identifier-interface

Indicates the source interface for sending BGP packets.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/active

Indicates that the route exchange function is enabled. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/prefix-list

Indicates the name of routing policy for filtering routes. The value is a string of 1 to 169 characters.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/direction

Indicates that direction of the route filtering policy of a BGP peer. Enumerated value. The value can be import or export.
NOTE:

The object values import and export cannot be configured simultaneously.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/apply-policys/apply-policy/direction

Indicates the direction of the route filtering policy of a BGP peer. Enumerated value. The value can be import or export.

NOTE:

If both import and export are configured, both incoming and outgoing routes of a BGP peer can be filtered.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/apply-policys/apply-policy/route-policy-name

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

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/active

Indicates that the route exchange function in the EVPN address family is enabled. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/password/cipher-password

Indicates the password verified by the MD5 value for configuring BGP peers. A plaintext password is a string of 1 to 255 characters, while a ciphertext password is a string of 20 to 392 characters.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/bgp-neighbor-keychain

Indicates the Keychain verified by the Keychain for configuring BGP peers. The value is a string of 1 to 47 characters.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/nbr-grp-name

Indicates the name of a BGP peer group.The value is a string of 1 to 47 characters. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/bgp-type

Indicates the type of a BGP peer group.

Enumerated value. The value can be external or internal. The default value is internal.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/active

Indicates that the route exchange function of a BGP peer group is enabled. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/route-reflector-client

Indicates that route reflection function of a BGP peer group is enabled. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/apply-policys/apply-policy/direction

Indicates the direction of the route filtering policy of a BGP peer group. Enumerated value. The value can be import or export.

NOTE:

If both import and export are configured, both incoming and outgoing routes of a BGP peer group can be filtered.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/apply-policys/apply-policy/route-policy-name

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

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/address

Indicates the IPv4 address of the specified network segment for BGP snooping. The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/mask

Indicates the mask of the specified network segment for BGP snooping. The value is in dotted decimal notation.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/ospf/ospf-id

Indicates the number of the OSPF protocol imported to BGP. The value is an integer that ranges from 1 to 65535, and the default value is 1.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/default-route-imported

Indicates the BGP flag for importing default routes. The value is of the Boolean type and can be true or false, and the default value is false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/load-balancing/max-number

Indicates the maximum number of equal-cost routes for load balancing. The value is an integer that ranges from 1 to 4.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/filter-policy/ip-prefix-name

Indicates the name of an IPv4 prefix list. The value is a string of 1 to 169 case-sensitive characters without spaces. The string can contain spaces if it is enclosed in double quotation marks (").

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/filter-policy/direction

Indicates the direction in which global received and sent routes are filtered based on an IPv4 prefix list.

Enumerated value. The value can be import or export. The value import indicates that the device filters incoming routes, and the value export indicates that the device filters outgoing routes.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/cipher-password

Indicates the ciphertext password used for MD5 authentication on BGP messages when a TCP connection is established between BGP peers based on the peer address. A plaintext password is a string of 1 to 255 characters, without spaces, and a ciphertext password is a string of 20 to 392 characters.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/cipher-password

Indicates the ciphertext password used for MD5 authentication on BGP messages when a TCP connection is established between BGP peers based on the peer group name. A plaintext password is a string of 1 to 255 characters, without spaces, and a ciphertext password is a string of 20 to 392 characters.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/hold-time

Indicates the hold time of a BGP peer. The value is an integer that can be 0 or ranges from 3 to 65535, in seconds.

NOTE:

Setting the hold time of a BGP peer to be longer than 20s is recommended. If the hold time is shorter than 20s, the BGP peer session may be interrupted.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/keepalive-time

Indicates the keepalive time of a BGP peer. The value is an integer that ranges from 0 to 21845, in seconds.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/hold-time

Indicates the hold time of a BGP peer group. The value is an integer that can be 0 or ranges from 3 to 65535, in seconds.

NOTE:

Setting the hold time of a BGP peer to be longer than 20s is recommended. If the hold time is shorter than 20s, the BGP peer session may be interrupted.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/keepalive-time

Indicates the keepalive time of a BGP peer group. The value is an integer that ranges from 0 to 21845, in seconds.

NOTE:

V300R003C10 and later versions support the objects listed below.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/tunnel-encap/cluster-id

Indicates the cluster ID of an RR in the tunnel-encap-ext view. The value can be an integer that ranges from 1 to 4294967295 or in the format of an IPv4 address.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/active

Enables the route switching function for a BGP peer group in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Enables the route reflection function for a BGP peer group in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Indicates the route-policy used for the routes sourced from or advertised to a BGP peer group in the tunnel-encap-ext view.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/advertise-community

Enables the function of advertising community attributes to a BGP peer group in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/active

Enables the route switching function for a BGP peer in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Enables the route reflection function for a BGP peer in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Indicates the route-policy used for the routes sourced from or advertised to a BGP peer in the tunnel-encap-ext view.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/advertise-community

Enables the function of advertising community attributes to a BGP peer in the tunnel-encap-ext view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/neighbour-group-name

Indicates the name of a BGP peer group in the tunnel-encap-ext view. The value is a string of 1 to 47 case-sensitive characters without spaces. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/cluster-id

Indicates the cluster ID of an RR in the BGP-EVPN address family view. The value can be an integer that ranges from 1 to 4294967295 or in the format of an IPv4 address.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/enable-change-path-attribute-reflection

Enable the RR to change the path attributes of the BGP routes by using an export policy. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/route-reflector-client

Enables the route reflection function for a BGP peer group in the BGP-EVPN address family view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Indicates the route-policy used for the routes sourced from or advertised to a BGP peer group in the BGP-EVPN address family view.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/advertise-encap-type

Indicates the encap type advertised to a BGP peer group in the BGP-EVPN address family view. The current value is sd-wan.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/route-reflector-client

Enables the route reflection function for a BGP peer in the BGP-EVPN address family view. The value is of the Boolean type and can be true or false.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Indicates the route-policy used for the routes sourced from or advertised to a BGP peer in the BGP-EVPN address family view.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/advertise-encap-type

Indicates the encap type advertised to a BGP peer in the BGP-EVPN address family view. The current value is sd-wan.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/neighbour-group-name

Indicates the name of a BGP peer group in the BGP-EVPN address family view. The value is a string of 1 to 47 case-sensitive characters without spaces. If the string is enclosed in double quotation marks ("), the string can contain spaces.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/apply-policys/apply-policy

Indicates the route-policy used for the routes sourced from or advertised to a BGP peer in the BGP-VPNv4 address family view.

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/advertise-community

Enables the function of advertising community attributes to a BGP peer in the BGP-VPNv4 address family view. The value is of the Boolean type and can be true or false.

Table 3-533 Creating the BGP configuration

Operation

XPATH

edit-config:default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing

Data Requirements
Table 3-534 Creating the BGP configuration

Item

Data

Description

Number of the local AS

56

Configure the BGP.

IP address of the BGP route

192.168.1.1

Enabling the GR function of the BGP route

-

Maximum waiting time for a BGP session to be reestablished after the remote end discovers the restart of the local end

100

External priority of BGP routing protocols

11

Internal priority of BGP routing protocols

12

Local priority of BGP routing protocols

13

IPv4 address of the BGP aggregation route

192.170.5.25

Network mask length of an aggregation route

16

AS-SET flag of a BGP aggregation route

true

BGP flag for importing direct routing protocols

true

BGP flag for importing static routing protocols

true

BGP flag for importing UNR routing protocols

true

Cluster ID of an RR

58

IP address of an IPv4 peer

192.168.2.5

AS number of an IPv4 peer

59

IPv4 peer

Source interface of sending BGP packets

192.168.2.5

LoopBack2

Name of an IPv4 address prefix list

site1

Serial number of the IPv4 address prefix list

1

IP address of the IPv4 address prefix list

192.168.5.2/24

Action of the IPv4 address prefix list

permit

Enabling the route exchange function

true

Name of the routing policy for filtering routes

site1

Direction of the routing policy for filtering routes

import

Enabling the route exchange function in the EVPN address family

true

Disabling the route exchange function in the EVPN address family

false

Password for MD5 authentication of a BGP peer

ab12

Keychain for Keychain authentication of a BGP peer

huawei

Name of a BGP peer group

test1

Type of a BGP peer group

internal

Enabling the route exchange function of a BGP peer group

true

Disabling the route exchange function of a BGP peer group

false

Enabling the route reflection function of a BGP peer group

true

Disabling the route reflection function of a BGP peer group

false

IPv4 address of the specified network segment for BGP snooping

192.165.6.5

Mask of the specified network segment for BGP snooping

255.255.0.0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> 
    <routing-instance> 
     <name>aaaaa</name> 
     <routing-protocols> 
      <routing-protocol> 
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type> 
       <name>adfa</name> 
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp"> 
        <prefix-lists> 
         <prefix-list> 
          <prefix-list-name>site1</prefix-list-name> 
          <prefixes> 
           <prefix> 
            <seq-nr>1</seq-nr> 
            <prefix-filter> 
             <ip-address>192.168.5.2/24</ip-address> 
             <action>permit</action> 
            </prefix-filter> 
           </prefix> 
          </prefixes> 
       </prefix-list> 
         </prefix-lists> 
         <bgp-router> 
         <local-as-number>56</local-as-number> 
            <af-configuration> 
               <ipv4> 
                  <unicast> 
                   <cluster-id>58</cluster-id> 
                   <protocol>            
                    <direct>true</direct> 
                    <static>true</static> 
                    <unr>true</unr> 
                   </protocol> 
                   <aggregate>      
                    <aggregate-ip-address>192.170.5.25</aggregate-ip-address> 
                    <aggregate-prefix-length>16</aggregate-prefix-length> 
                    <aggregate-netmask>255.255.0.0</aggregate-netmask> 
                    <as-set-falg>true</as-set-falg> 
                    <as-set-falg>false</as-set-falg> 
                   <aggregate>  
                     <external>11</external> 
                     <internal>12</internal> 
                     <local>13</local> 
                  </unicast>             
               </ipv4>             
            </af-configuration> 
         <router-id>       
          <ip-address>192.168.1.1</ip-address>      
         </router-id> 
         <graceful-restart> 
          <enable>true</enable>       
          <restart-time>100</restart-time>      
         </graceful-restart> 
        </bgp-router> 
        <bgp-neighbor-groups> 
         <bgp-neighbor-group> 
          <nbr-grp-name>test1</nbr-grp-name> 
          <bgp-type>internal</bgp-type> 
          <remote-as>59</remote-as> 
          <listen-net> 
           <address>192.165.6.5</address> 
           <mask>255.255.0.0</mask> 
          </listen-net> 
          <af-specific-config> 
          <ipv4> 
           <unicast> 
            <active>true</active> 
            <active>false</active> 
            <route-reflector-client>true</route-reflector-client> 
            <route-reflector-client>false</route-reflector-client> 
           </unicast> 
          </ipv4> 
          </af-specific-config> 
         </bgp-neighbor-group>           
        </bgp-neighbor-groups> 
        <bgp-neighbors> 
         <bgp-neighbor> 
          <peer-address>192.168.2.5</peer-address> 
          <remote-as>59</remote-as> 
          <bgp-neighbor-keychain>huawei</bgp-neighbor-keychain> 
          <identifier-interface>LoopBack2</identifier-interface> 
             <password> 
               <cipher-password>ab12</cipher-password> 
             </password> 
         <af-specific-config> 
           <ipv4> 
            <unicast> 
             <active>true</active> 
             <prefix-list>site1</prefix-list> 
             <direction>import</direction> 
            </unicast> 
           </ipv4> 
          </af-specific-config> 
          <l2vpn> 
            <evpn> 
             <active>true</active> 
             <active>false</active> 
            </evpn> 
           </l2vpn> 
         </bgp-neighbor>          
        </bgp-neighbors> 
       </bgp-routing> 
      </routing-protocol> 
     </routing-protocols> 
    </routing-instance> 
 </routing> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <ok/> 
</rpc-reply> 
]]>]]>

Sample of failed response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <rpc-error> 
    <error-type>application</error-type> 
    <error-tag>data-exists</error-tag> 
    <error-severity>error</error-severity> 
    <error-message>parse rpc config error.</error-message> 
  </rpc-error> 
</rpc-reply> 
]]>]]>

Table 3-535 Modifying the BGP configuration

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing

Data Requirements
Table 3-536 Modifying the BGP configuration

Item

Data

Description

IP address of the BGP route

192.168.1.2

Modify the BGP configuration.

Enabling the GR function of the BGP route

-

External priority of BGP routing protocols

-

Internal priority of BGP routing protocols

-

Local priority of BGP routing protocols

-

Cluster ID of an RR

59

Name of an IPv4 address prefix list

site1

Serial number of the IPv4 address prefix list

1

IP address of the IPv4 address prefix list

192.168.1.2/16

Action of the IPv4 address prefix list

deny

Password for MD5 authentication of a BGP peer

cd34

Keychain for Keychain authentication of a BGP peer

suzhou

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> 
    <routing-instance> 
     <name>aaaaa</name> 
     <routing-protocols> 
      <routing-protocol> 
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type> 
       <name>adfa</name> 
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp"> 
       <prefix-lists> 
        <prefix-list> 
         <prefix-list-name>site1</prefix-list-name> 
         <prefixes> 
          <prefix xc:operation="replace"> 
           <seq-nr>1</seq-nr> 
           <prefix-filter> 
            <ip-address>192.168.1.2/16</ip-address> 
            <action>deny</action> 
           </prefix-filter> 
          </prefix> 
         </prefixes> 
        </prefix-list> 
        </prefix-lists> 
        <bgp-router xc:operation="replace"> 
         <local-as-number>56</local-as-number> 
         <af-configuration> 
          <ipv4> 
           <unicast>  
            <cluster-id>59</cluster-id>    
           </unicast>             
          </ipv4>             
         </af-configuration>  
         <graceful-restart> 
          <enable>true</enable>       
          <restart-time>200</restart-time>      
         </graceful-restart> 
         <router-id>       
          <ip-address>192.168.1.2</ip-address>      
         </router-id> 
        </bgp-router> 
        <bgp-neighbors> 
         <bgp-neighbor> 
          <peer-address>192.168.2.5</peer-address> 
          <remote-as>59</remote-as> 
          <bgp-neighbor-keychain xc:operation="replace">suzhou</bgp-neighbor-keychain> 
          <password xc:operation="replace"> 
           <cipher-password>cd34</cipher-password> 
          </password>  
         </bgp-neighbor>          
        </bgp-neighbors> 
       </bgp-routing> 
      </routing-protocol> 
     </routing-protocols> 
    </routing-instance> 
 </routing> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <ok/> 
</rpc-reply> 
]]>]]>

Sample of failed response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <rpc-error> 
    <error-type>application</error-type> 
    <error-tag>data-exists</error-tag> 
    <error-severity>error</error-severity> 
    <error-message>parse rpc config error.</error-message> 
  </rpc-error> 
</rpc-reply> 
]]>]]>

This section provides a sample of deleting the BGP configuration.

Table 3-537 Deleting the BGP configuration

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing

Data Requirements
Table 3-538 Deleting the BGP configuration

Item

Data

Description

IPv4 address of the BGP aggregation route

192.170.5.25

Delete the BGP configuration.

BGP flag for importing direct routing protocols

false

BGP flag for importing static routing protocols

false

BGP flag for importing UNR routing protocols

false

Cluster ID of an RR

-

IP address of an IPv4 peer

192.168.2.5

Name of an IPv4 address prefix list

site1

Enabling the route exchange function

false

Password for MD5 authentication of a BGP peer

-

Keychain for Keychain authentication of a BGP peer

-

Name of a BGP peer group

test1

Type of a BGP peer group

external

IPv4 address of the specified network segment for BGP snooping

192.165.6.5

Mask of the specified network segment for BGP snooping

255.255.0.0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
 <edit-config> 
  <target> 
 <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
 <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> 
    <routing-instance> 
     <name>aaaaa</name> 
     <routing-protocols> 
      <routing-protocol> 
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type> 
       <name>adfa</name> 
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp"> 
        <prefix-lists> 
         <prefix-list xc:operation="remove"> 
          <prefix-list-name>site1</prefix-list-name> 
         </prefix-list> 
        </prefix-lists> 
        <bgp-router xc:operation="remove"> 
         <local-as-number>56</local-as-number> 
         <af-configuration> 
          <ipv4> 
           <unicast> 
           <protocol>            
             <direct>false</direct> 
             <static>false</static> 
             <unr>false</unr> 
            </protocol>    
            <aggregate xc:operation="remove">      
             <aggregate-ip-address>192.170.5.25</aggregate-ip-address> 
            </aggregate>  
           </unicast>             
          </ipv4>             
         </af-configuration>  
        </bgp-router> 
        <bgp-neighbor-groups> 
         <bgp-neighbor-group> 
          <nbr-grp-name>test1</nbr-grp-name> 
        <remote-as>59</remote-as> 
          <listen-net xc:operation="remove"> 
           <address>192.165.6.5</address> 
           <mask>255.255.0.0</mask> 
          </listen-net> 
         </bgp-neighbor-group>    
         <bgp-neighbor-group xc:operation="remove"> 
          <nbr-grp-name>test1</nbr-grp-name> 
          <bgp-type>external</bgp-type> 
          <remote-as>59</remote-as> 
         </bgp-neighbor-group>           
        </bgp-neighbor-groups> 
        <bgp-neighbors> 
         <bgp-neighbor xc:operation="remove"> 
          <peer-address>192.168.2.5</peer-address> 
          <remote-as>59</remote-as> 
          <bgp-neighbor-keychain xc:operation="remove"></bgp-neighbor-keychain> 
          <password xc:operation="remove"> 
            </password>  
            <af-specific-config> 
             <ipv4> 
              <unicast> 
               <active>false</active> 
              </unicast> 
             </ipv4> 
            </af-specific-config> 
         </bgp-neighbor>          
        </bgp-neighbors> 
       </bgp-routing> 
      </routing-protocol> 
     </routing-protocols> 
    </routing-instance> 
 </routing> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <ok/> 
</rpc-reply> 
]]>]]>

Sample of failed response

<?xml version="1.0" encoding="UTF-8"?> 
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1001"> 
  <rpc-error> 
    <error-type>application</error-type> 
    <error-tag>data-exists</error-tag> 
    <error-severity>error</error-severity> 
    <error-message>parse rpc config error.</error-message> 
  </rpc-error> 
</rpc-reply> 
]]>]]>

Configuring the Local AS Number

Creating the Local AS Number

This section provides a sample of creating the local AS number.

Table 3-539 Creating the local AS number

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/local-as-number

Data Requirements
Table 3-540 Creating the local AS number

Item

Data

Description

Local AS number

56

Create local AS 56.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 
Deleting the Local AS Number

This section provides a sample of deleting the local AS number.

Table 3-541 Deleting the local AS number

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/local-as-number

Data Requirements
Table 3-542 Deleting the local AS number

Item

Data

Description

Local AS number

56

Delete local AS 56.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="remove">
         <local-as-number>56</local-as-number>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 

Configuring the IP Address of a BGP Route

Creating the IP Address of a BGP Route

This section provides a sample of creating the IP address of a BGP route.

Table 3-543 Creating the IP address of a BGP route

Operation

XPATH

edit-config:default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/router-id/ip-address

Data Requirements
Table 3-544 Creating the IP address of a BGP route

Item

Data

Description

IP address of a BGP route

192.168.1.1

Create the IP address of 192.168.1.1 for a BGP route.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <router-id>      
          <ip-address>192.168.1.1</ip-address>     
         </router-id>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 
Deleting the IP Address of a BGP Route

This section provides a sample of deleting the IP address of a BGP route.

Table 3-545 Deleting the IP address of a BGP route

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/router-id/ip-address

Data Requirements
Table 3-546 Deleting the IP address of a BGP route

Item

Data

Description

IP address of a BGP route

-

Delete IP address 1 of a BGP route.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 
Modifying the IP Address of a BGP Route

This section provides a sample of modifying the IP address of a BGP route.

Table 3-547 Modifying the IP address of a BGP route

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/router-id/ip-address

Data Requirements
Table 3-548 Modifying the IP address of a BGP route

Item

Data

Description

IP address of a BGP route

192.168.1.2

Change the IP address of a BGP route to 192.168.1.2.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>
         <router-id>      
          <ip-address>192.168.1.2</ip-address>     
         </router-id>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 

Configuring the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablished

Configuring the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablished

This section provides a sample of configuring the maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished.

Table 3-549 Configuring the maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/enable

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/restart-time

Data Requirements
Table 3-550 Configuring the maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished

Item

Data

Description

Whether BGP GR is enabled

true

Set the maximum period to 100s.

Maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished

100

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <graceful-restart>
          <enable>true</enable>      
          <restart-time>100</restart-time>     
         </graceful-restart>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Restoring the Default Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablished

This section provides a sample of Restoring the default maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished.

Table 3-551 Restoring the default maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/enable

Data Requirements
Table 3-552 Restoring the default maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished.

Item

Data

Description

Whether BGP GR is enabled

false

Restore the default maximum period to 150s.

Maximum period from the time when the peer finds that the local peer restarts to the time when the BGP session is reestablished

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>
         <graceful-restart>
          <enable>false</enable>        
         </graceful-restart>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Modifying the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablished

This section provides a sample of modifying the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablished.

Table 3-553 Modifying the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablishe

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/enable

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/graceful-restart/restart-time

Data Requirements
Table 3-554 Modifying the Maximum Period from the Time When the Peer Finds That the Local Peer Restarts to the Time When the BGP Session Is Reestablish

Item

Data

Description

Whether BGP GR is enabled

true

Change the maximum period to 200s.

Maximum period from the time when the peer finds that the local peer restarts to the time when the BGP

200

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>
         <graceful-restart>
          <enable>true</enable>      
          <restart-time>200</restart-time>     
         </graceful-restart>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply> 

Configuring External, Internal, and Local Priorities of a BGP Route

Configuring External, Internal, and Local Priorities of a BGP Route

This section provides a sample of configuring external, internal, and local priorities of a BGP route.

Table 3-555 Configuring external, internal, and local priorities of a BGP route

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/external

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/internal

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/local

Data Requirements
Table 3-556 Configuring external, internal, and local priorities of a BGP route

Item

Data

Description

External priority of a BGP route

11

Configure external, internal, and local priorities of a BGP route.

Internal priority of a BGP route

12

Local priority of a BGP route

13

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
            <af-configuration>
               <ipv4>
                  <unicast>
                     <external>11</external>
                     <internal>12</internal>
                     <local>13</local>
                  </unicast>            
               </ipv4>            
            </af-configuration> 
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Restoring External, Internal, and Local Priorities of a BGP Route

This section provides a sample of restoring external, internal, and local priorities of a BGP route

Table 3-557 Restoring external, internal, and local priorities of a BGP route

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/external

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/internal

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/local

Data Requirements
Table 3-558 Restoring external, internal, and local priorities of a BGP route

Item

Data

Description

External priority of a BGP route

-

Restore external, internal, and local priorities of a BGP route.

Internal priority of a BGP route

-

Local priority of a BGP route

-

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number> 
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring an Aggregated Route

Configuring the IPv4 Address, Mask Length, and Mask Address of the Aggregated Route

This section provides a sample of configuring the IPv4 address, mask length, and mask address of the aggregated route.

Table 3-559 Configuring the IPv4 address, mask length, and mask address of the aggregated route

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-ip-address

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-prefix-length

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-netmask

Data Requirements
Table 3-560 Configuring the IPv4 address, mask length, and mask address of the aggregated route

Item

Data

Description

IPv4 address of an aggregated route

192.170.5.25

Configure the IPv4 address, mask length, and mask address of the aggregated route.

Mask length of an aggregated route

16

Mask address of an aggregated route

255.255.0.0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <aggregate>     
             <aggregate-ip-address>192.170.5.25</aggregate-ip-address>
             <aggregate-prefix-length>16</aggregate-prefix-length>
             <aggregate-netmask>255.255.0.0</aggregate-netmask>
            </aggregate> 
           </unicast>            
          </ipv4>            
         </af-configuration>                                      
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting the IPv4 Address of an Aggregated Route

This section provides a sample of deleting the IPv4 address of an aggregated route.

Table 3-561 Deleting the IPv4 address of an aggregated route

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/aggregate-ip-address

Data Requirements
Table 3-562 Deleting the IPv4 address of an aggregated route

Item

Data

Description

IPv4 address of an aggregated route

192.170.5.25

Delete the IPv4 address of an aggregated route.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <aggregate xc:operation="remove">     
             <aggregate-ip-address>192.170.5.25</aggregate-ip-address>
            </aggregate> 
           </unicast>            
          </ipv4>            
         </af-configuration>                                    
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring a BGP Route with the AS-SET

Specifying a Route with the AS-SET

This section provides a sample of specifying a route with the AS-SET.

Table 3-563 Specifying a route with the AS-SET

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/as-set-falg

Data Requirements
Table 3-564 Specifying a route with the AS-SET

Item

Data

Description

Whether the BGP route contains the AS-SET

true

Specify a route with the AS-SET.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <aggregate>     
             <aggregate-ip-address>192.170.5.25</aggregate-ip-address>
             <aggregate-netmask>255.255.0.0</aggregate-netmask>
             <as-set-falg>true</as-set-falg>
            </aggregate>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Specifying a Route Without the AS-SET

This section provides a sample of specifying a route without the AS-SET.

Table 3-565 Specifying a route without the AS-SET

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/aggregate/as-set-falg

Data Requirements
Table 3-566 Specifying a route without the AS-SET

Item

Data

Description

Whether the BGP route contains the AS-SET

false

Specify a route without the AS-SET.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration xc:operation="replace">
          <ipv4>
           <unicast>
            <aggregate>     
             <aggregate-ip-address>192.170.5.25</aggregate-ip-address>
             <aggregate-netmask>255.255.0.0</aggregate-netmask>
             <as-set-falg>false</as-set-falg>
            </aggregate>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring BGP to Import Routes of Other Routing Protocols

Configuring BGP to Import Default Routes

This section provides a sample of configuring BGP to import default routes.

Table 3-567 Configuring BGP to import default routes

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/default-route-imported

Data Requirements
Table 3-568 Configuring BGP to import default routes

Item

Data

Description

Number of the local AS

56

Configure BGP to import default routes.

Importing default routes

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <default-route-imported xc:operation="merge">true</default-route-imported>          
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the Configuration of BGP to Import Default Routes

This section provides a sample of deleting the configuration of BGP to import default routes.

Table 3-569 Deleting the configuration of BGP to import default routes

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/default-route-imported

Data Requirements
Table 3-570 Deleting the configuration of BGP to import default routes

Item

Data

Description

Number of the local AS

56

Delete the configuration of BGP to import default routes.

Importing default routes

true

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <default-route-imported xc:operation="remove">true</default-route-imported>          
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Configuring BGP to Import a Direct Route

This section provides a sample of configuring BGP to import a direct route

Table 3-571 Configuring BGP to import a direct route

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/direct

Data Requirements
Table 3-572 Configuring BGP to import a direct route

Item

Data

Description

Direct route

true

Configure BGP to import a direct route.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>           
             <direct>true</direct>
            </protocol>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting the Direct Route Imported by BGP

This section provides a sample of deleting the direct route imported by BGP.

Table 3-573 Deleting the direct route imported by BGP

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/direct

Data Requirements
Table 3-574 Deleting the direct route imported by BGP

Item

Data

Description

Direct route

false

Delete the direct route imported by BGP.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
         <protocol>           
    <direct>false</direct>
      </protocol>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Configuring BGP to Import a Static Route

This section provides a sample of configuring BGP to import a static route.

Table 3-575 Configuring BGP to import a static route

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/static

Data Requirements
Table 3-576 Configuring BGP to import a static route

Item

Data

Description

Static route

true

Configure BGP to import a static route.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>           
             <static>true</static>
            </protocol>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply>
Deleting the Static Route Imported by BGP

This section provides a sample of deleting the static route imported by BGP.

Table 3-577 Deleting the static route imported by BGP

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/static

Data Requirements
Table 3-578 Deleting the static route imported by BGP

Item

Data

Description

Static route

false

Delete the static route imported by BGP.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>           
             <static>false</static>
            </protocol>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting the UNR Route Imported by BGP

This section provides a sample of deleting the UNR route imported by BGP.

Table 3-579 Deleting the UNR route imported by BGP

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/unr

Data Requirements
Table 3-580 Deleting the UNR route imported by BGP

Item

Data

Description

UNR route

false

Delete the UNR route imported by BGP.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>           
             <unr>false</unr>
            </protocol>            
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Configuring BGP to Import OSPF

This section provides a sample of configuring BGP to import OSPF.

Table 3-581 Configuring BGP to import OSPF

Operation

XPATH

edit-config:default

/ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/ospf

Data Requirements
Table 3-582 Configuring BGP to import OSPF

Item

Data

Description

Number of the local AS

56

Configure BGP to import the OSPF protocol 20.

OSPF protocol number

20

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>
            <ospf>
            <ospf-id>20</ospf-id>
            </ospf>
            </protocol>       
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Changing the OSPF Protocol Imported to BGP

This section provides a sample of changing the OSPF protocol imported to BGP.

Table 3-583 Changing the OSPF protocol imported to BGP

Operation

XPATH

edit-config:replace

/ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/ospf

Data Requirements
Table 3-584 Changing the OSPF protocol imported to BGP

Item

Data

Description

Number of the local AS

56

Change the number of the OSPF protocol imported to BGP from 20 to 40.

OSPF protocol number

40

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>
            <ospf xc:operation="replace">
            <ospf-id>40</ospf-id>
            </ospf>
            </protocol>       
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the OSPF Protocol Imported to BGP

This section provides a sample of deleting the OSPF protocol imported to BGP.

Table 3-585 Deleting the OSPF protocol imported to BGP

Operation

XPATH

edit-config:remove

/ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/protocol/ospf

Data Requirements
Table 3-586 Deleting the OSPF protocol imported to BGP

Item

Data

Description

Number of the local AS

56

Delete the OSPF protocol 40 imported to BGP.

OSPF protocol number

40

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <protocol>
            <ospf xc:operation="remove">
            <ospf-id>40</ospf-id>
            </ospf>
            </protocol>       
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply> 

Configuring BGP to Import Routes of Other Routing Protocols

Configuring BGP to Import Routes of Other Routing Protocols

This section provides a sample of configuring BGP to import routes of other routing protocols.

Table 3-587 Configuring BGP to import routes of other routing protocols

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route

Data Requirements
Table 3-588 Configuring BGP to import routes of other routing protocols

Item

Data

Description

Imported route type and routing protocol whose routes are imported

isis

Import the IS-IS route with the process ID 81 that matches the route-policy test1, and set the MED value of the imported route to 58. Import the OSPF route with the process ID 82 that matches the route-policy test2, and set the MED value of the imported route to 59. Import the UNR route that matches the route-policy test3, and set the MED value of the imported route to 60. Import the direct route that matches the route-policy test4, and set the MED value of the imported route to 61. Import the static route that matches the route-policy test5, and set the MED value of the imported route to 62.

IS-IS process ID

81

Route-policy name

test1

MED value of an imported IS-IS route

58

Imported route type and routing protocol whose routes are imported

ospf

OSPF process ID

82

Route-policy name

test2

MED value of an imported OSPF route

59

Imported route type and routing protocol whose routes are imported

unr

Route-policy name

test3

MED value of an imported route

60

Imported route type and routing protocol whose routes are imported

direct

Route-policy name

test4

MED value of an imported route

61

Imported route type and routing protocol whose routes are imported

static

Route-policy name

test5

MED value of an imported route

62

NOTE:

After BGP is configured to import static routes, routes to the network segment where the IP address of the management interface belongs are also imported into the BGP routing table. Therefore, exercise caution when configuring BGP to import static routes.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <import-routes>
             <import-route>
              <import-protocol>isis</import-protocol>
              <isis xc:operation="merge">              
               <isis-id>81</isis-id>               
               <import-route-policy>test1</import-route-policy>
               <med-for-route>58</med-for-route>
              </isis>
             </import-route>  
             <import-route>
              <import-protocol>ospf</import-protocol>
              <ospf xc:operation="merge">              
               <ospf-id>82</ospf-id>               
               <import-route-policy>test2</import-route-policy>
               <med-for-route>59</med-for-route>
              </ospf>
             </import-route> 
             <import-route>
              <import-protocol>unr</import-protocol>
              <import-route-policy>test3</import-route-policy>
              <med-for-route>60</med-for-route> 
             </import-route>
             <import-route>
              <import-protocol>direct</import-protocol>
              <import-route-policy>test4</import-route-policy>
              <med-for-route>61</med-for-route> 
             </import-route>
             <import-route>
              <import-protocol>static</import-protocol>
              <import-route-policy>test5</import-route-policy>
              <med-for-route>62</med-for-route> 
             </import-route>
            </import-routes>
           </unicast>            
          </ipv4>            
         </af-configuration> 
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the Routes Imported from Other Routing Protocols to BGP

This section provides a sample of deleting the routes imported from other routing protocols to BGP.

Table 3-589 Deleting the routes imported from other routing protocols to BGP

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/import-routes/import-route

Data Requirements
Table 3-590 deleting the routes imported from other routing protocols to BGP

Item

Data

Description

-

-

Delete the routes imported from other routing protocols to BGP.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <import-routes>
             <import-route xc:operation="remove">         
             </import-route>
            </import-routes>
           </unicast>            
          </ipv4>            
         </af-configuration> 
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring the Cluster ID of an RR

Configuring the Cluster ID of an RR(in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of configuring the cluster ID of an RR.

Table 3-591 Configuring the cluster ID of an RR

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/cluster-id

Data Requirements
Table 3-592 Configuring the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

58

Configure cluster 58 for an RR.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast> 
            <cluster-id>58</cluster-id>   
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting the Cluster ID of an RR(in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of deleting the cluster ID of an RR.

Table 3-593 Deleting the cluster ID of an RR

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/cluster-id

Data Requirements
Table 3-594 Deleting the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

-

Delete the cluster ID of an RR.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>        
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Changing the Cluster ID of an RR(in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of changing the cluster ID of an RR.

Table 3-595 Changing the cluster ID of an RR

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/cluster-id

Data Requirements
Table 3-596 Changing the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

59

Change the cluster ID of an RR to 59.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router xc:operation="replace">
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast> 
            <cluster-id>59</cluster-id>   
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Configuring the Cluster ID of an RR (in the tunnel-encap-ext View)

This section provides a sample of configuring the cluster ID of an RR.

Table 3-597 Configuring the cluster ID of an RR

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/tunnel-encap/cluster-id

Data Requirements
Table 3-598 Configuring the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

10.10.0.11

Set the cluster ID of an RR to 10.10.0.11.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
          <ipv4>
           <tunnel-encap>
            <cluster-id xc:operation="merge">10.10.0.11</cluster-id>
           </tunnel-encap>
          </ipv4>
         </af-configuration>   
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/>
</rpc-reply>
Deleting the Cluster ID of an RR (in the tunnel-encap-ext View)

This section provides a sample of deleting the cluster ID of an RR.

Table 3-599 Deleting the cluster ID of an RR

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/tunnel-encap/cluster-id

Data Requirements
Table 3-600 Deleting the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

10.10.0.11

Delete the cluster ID of an RR.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
         <ipv4>
          <tunnel-encap>
           <cluster-id xc:operation="remove">10.10.0.11</cluster-id>
          </tunnel-encap>
         </ipv4>
         </af-configuration>   
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/>
</rpc-reply>
Configuring the Cluster ID of an RR (in the BGP-EVPN Address Family View)

This section provides a sample of configuring the cluster ID of an RR.

Table 3-601 Configuring the cluster ID of an RR

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/cluster-id

Data Requirements
Table 3-602 Configuring the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

192.168.2.5

Configure the cluster ID of an RR.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
         <l2vpn>
          <evpn>
           <cluster-id xc:operation="merge">192.168.2.5</cluster-id>                                 
          </evpn>
         </l2vpn>
         </af-configuration>   
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/>
</rpc-reply>
Deleting the Cluster ID of an RR (in the BGP-EVPN Address Family View)

This section provides a sample of deleting the cluster ID of an RR.

Table 3-603 Deleting the cluster ID of an RR

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/cluster-id

Data Requirements
Table 3-604 Deleting the cluster ID of an RR

Item

Data

Description

Cluster ID of an RR

192.168.2.5

Delete the cluster ID of an RR.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
         <af-configuration>
         <l2vpn>
          <evpn>
           <cluster-id xc:operation="remove">192.168.2.5</cluster-id>                                 
          </evpn>
         </l2vpn>
         </af-configuration>   
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/>
</rpc-reply>

Configuring an IPv4 Peer

Configuring an IPv4 Peer

This section provides a sample of configuring an IPv4 peer.

Table 3-605 Configuring an IPv4 peer

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/peer-address

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/remote-as

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/identifier-interface

Data Requirements
Table 3-606 Configuring an IPv4 peer

Item

Data

Description

IP address of the MSDP peer of which the SA messages are filtered

192.168.2.5

Configure an IPv4 peer, with AS 59 and source interface as LoopBack2.

AS number

59

Source interface that sends BGP packets

LoopBack2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <identifier-interface>LoopBack2</identifier-interface>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply>
Deleting an IPv4 Peer

This section provides a sample of deleting an IPv4 peer.

Table 3-607 Deleting an IPv4 peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/peer-address

Data Requirements
Table 3-608 Deleting an IPv4 peer

Item

Data

Description

IP address of the MSDP peer of which the SA messages are filtered

192.168.2.5

Delete an IPv4 peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor xc:operation="remove">
          <peer-address>192.168.2.5</peer-address>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply>

Configuring an IPv4 Prefix List

Creating an IPv4 Prefix List

This section provides a sample of creating an IPv4 prefix list.

Table 3-609 Creating an IPv4 prefix list

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/prefix-lists/prefix-list

Data Requirements
Table 3-610 Creating an IPv4 prefix list

Item

Data

Description

Name of an IPv4 prefix list

site1

Create an IPv4 prefix list named site1 and numbered 1, with the IP address of 192.168.5.2/24 and action of permit.

Number of an IPv4 prefix list

1

IP address of an IPv4 prefix list

192.168.5.2/24

Action of an IPv4 prefix list

permit

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <prefix-lists>
        <prefix-list>
         <prefix-list-name>site1</prefix-list-name>
         <prefixes>
          <prefix>
           <seq-nr>1</seq-nr>
           <prefix-filter>
            <ip-address>192.168.5.2/24</ip-address>
            <action>permit</action>
           </prefix-filter>
          </prefix>
         </prefixes>
        </prefix-list>
        </prefix-lists>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting an IPv4 Prefix List

This section provides a sample of deleting an IPv4 prefix list.

Table 3-611 Deleting an IPv4 prefix list

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/prefix-lists/prefix-list/prefix-list-name

Data Requirements
Table 3-612 Deleting an IPv4 prefix list

Item

Data

Description

Name of an IPv4 prefix list

site1

Delete the IPv4 prefix list named site1.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <prefix-lists>
        <prefix-list xc:operation="remove">
         <prefix-list-name>site1</prefix-list-name>
        </prefix-list>
        </prefix-lists>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Modifying an IPv4 Prefix List

This section provides a sample of modifying an IPv4 prefix list.

Table 3-613 Modifying an IPv4 prefix list

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/prefix-lists/prefix-list

Data Requirements
Table 3-614 Modifying an IPv4 prefix list

Item

Data

Description

Name of an IPv4 prefix list

site1

Change the IP address to 192.168.1.2/16 and action to deny for the IPv4 prefix list site1.

Number of an IPv4 prefix list

1

IP address of an IPv4 prefix list

192.168.1.2/16

Action of an IPv4 prefix list

deny

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <prefix-lists>
        <prefix-list>
         <prefix-list-name>site1</prefix-list-name>
         <prefixes>
          <prefix xc:operation="replace">
           <seq-nr>1</seq-nr>
           <prefix-filter>
            <ip-address>192.168.1.2/16</ip-address>
            <action>deny</action>
           </prefix-filter>
          </prefix>
         </prefixes>
        </prefix-list>
        </prefix-lists>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring a Route Filtering Policy of a BGP Peer (Unidirectional Filtering)

Configuring a Route Filtering Policy of a BGP Peer (Unidirectional Filtering)

This section provides a sample of configuring a route filtering policy of a BGP peer.

Table 3-615 Configuring a route filtering policy of a BGP peer

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast

Data Requirements
Table 3-616 Configuring a route filtering policy of a BGP peer

Item

Data

Description

Whether the route switching function is enabled

true

Configure a route filtering policy named site1 where the route switching function is enabled and the direction is import.

Route filtering policy name

site1

Direction where a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <af-specific-config>
           <ipv4>
            <unicast>
             <active>true</active>
             <prefix-list>site1</prefix-list>
             <direction>import</direction>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting a Route Filtering Policy of a BGP Peer (Unidirectional Filtering)

This section provides a sample of deleting a route filtering policy of a BGP peer.

Table 3-617 Deleting a route filtering policy of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/active

Data Requirements
Table 3-618 Deleting a route filtering policy of a BGP peer

Item

Data

Description

Whether the route switching function is enabled

false

Disable the route switching function.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <af-specific-config>
           <ipv4>
            <unicast>
             <active>false</active>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

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

Configuring a Route Filtering Policy of a BGP Peer (Bidirectional Filtering)

Configuring a Route Filtering Policy of a BGP Peer (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of configuring a route filtering policy of a BGP peer.

Table 3-619 Configuring a route filtering policy of a BGP peer

Operation

XPATH

edit-config:default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-620 Configuring a route filtering policy of a BGP peer

Item

Data

Description

Number of the local AS

100

Configure a route filtering policy named policy3 to filter routes of a BGP peer in both directions.

Remote AS number of an IPv4 peer

10

Remote IP address of an IPv4 peer

10.199.231.1

Name of a route filtering policy

policy3

Direction of the route filtering policy

import

Name of a route filtering policy

policy3

Direction of the route filtering policy

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">   
    <route-policy xc:operation="merge">
     <name>policy3</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>sdwan</name>
     <routing-protocols>
      <routing-protocol>
       <name>sdwan</name>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <remote-as>10</remote-as>
          <peer-address>10.199.231.1</peer-address>
          <af-specific-config>
           <ipv4>
            <unicast>
             <apply-policys>
              <apply-policy>
               <direction>import</direction>
               <route-policy-name>policy3</route-policy-name>
              </apply-policy>
              <apply-policy>
               <direction>export</direction>
               <route-policy-name>policy3</route-policy-name>
              </apply-policy>
             </apply-policys>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
  <ok/> 
</rpc-reply> 
Deleting a Route Filtering Policy of a BGP Peer (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of deleting a route filtering policy of a BGP peer.

Table 3-621 Deleting a route filtering policy of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-622 Deleting a route filtering policy of a BGP peer

Item

Data

Description

Number of the local AS

100

Delete the route filtering policy that is named policy3 and used to filter routes of a BGP peer in both directions.

Remote AS number of an IPv4 peer

10

Remote IP address of an IPv4 peer

10.199.231.1

Name of a route filtering policy

policy3

Direction of the route filtering policy

import

Name of a route filtering policy

policy3

Direction of the route filtering policy

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>sdwan</name>
     <routing-protocols>
      <routing-protocol>
       <name>sdwan</name>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <remote-as>10</remote-as>
          <peer-address>10.199.231.1</peer-address>
          <af-specific-config>
           <ipv4>
            <unicast>
             <apply-policys  xc:operation="remove">
              <apply-policy>
               <direction>import</direction>
               <route-policy-name>policy3</route-policy-name>
              </apply-policy>
              <apply-policy>
               <direction>export</direction>
               <route-policy-name>policy3</route-policy-name>
              </apply-policy>
             </apply-policys>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DDEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Configuring Route Filtering Policies for a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of configuring route filtering policies for a BGP peer.

Table 3-623 Configuring route filtering policies for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-624 Configuring route filtering policies for a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Configure route filtering policies named policy1 and policy2 to filter routes of a BGP peer in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
       <name>policy2</name>
        <nodes>
         <node>
          <node-index>10</node-index>
          <match-mode>permit</match-mode>
         </node>
        </nodes>
      </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <apply-policys>
              <apply-policy xc:operation="merge">
               <direction>export</direction>
                <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="merge">
               <direction>import</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply> 
Changing the Route Filtering Policies of a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of changing the route filtering policies of a BGP peer.

Table 3-625 Changing the route filtering policies of a BGP peer

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-626 Changing the route filtering policies of a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Change the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <apply-policys>
              <apply-policy xc:operation="replace">
              <direction>export</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="replace">
              <direction>import</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply> 
Deleting the Route Filtering Policy of a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of deleting the route filtering policies of a BGP peer.

Table 3-627 Deleting the route filtering policies of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-628 Deleting the route filtering policies of a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Delete the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <apply-policys>
               <apply-policy xc:operation="remove">
                <direction>export</direction>
                <route-policy-name>policy2</route-policy-name>
               </apply-policy>
               <apply-policy xc:operation="remove">
                 <direction>import</direction>
                 <route-policy-name>policy1</route-policy-name>
               </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Configuring Route Filtering Policies for a BGP Peer (in the BGP-EVPN Address Family View)

This section provides a sample of configuring route filtering policies for a BGP peer.

Table 3-629 Configuring route filtering policies for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-630 Configuring route filtering policies for a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Configure route filtering policies named policy1 and policy2 to filter routes of a BGP peer in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
          <l2vpn>
           <evpn>
            <active>true</active>
            <apply-policys>
            <apply-policy xc:operation="merge">
             <direction>export</direction>
             <route-policy-name>policy1</route-policy-name>
            </apply-policy>
           <apply-policy xc:operation="merge">
            <direction>import</direction>
            <route-policy-name>policy2</route-policy-name>
           </apply-policy>
           </apply-policys>
          </evpn>
         </l2vpn>
         </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply> 
Changing the Route Filtering Policies of a BGP Peer (in the BGP-EVPN Address Family View)

This section provides a sample of changing the route filtering policies of a BGP peer.

Table 3-631 Changing the route filtering policies of a BGP peer

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-632 Changing the route filtering policies of a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Change the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
           <af-specific-config>
           <l2vpn>
            <evpn>
            <active>true</active>
            <apply-policys>
             <apply-policy xc:operation="replace">
             <direction>export</direction>
             <route-policy-name>policy2</route-policy-name>
             </apply-policy>
             <apply-policy xc:operation="replace">
             <direction>import</direction>
             <route-policy-name>policy1</route-policy-name>
             </apply-policy>
             </apply-policys>
            </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply> 
Deleting the Route Filtering Policies of a BGP Peer (in the BGP-EVPN Address Family View)

This section provides a sample of deleting the route filtering policies of a BGP peer.

Table 3-633 Deleting the route filtering policies of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-634 Deleting the route filtering policies of a BGP peer

Item

Data

Description

Name of a route filtering policy

policy1

Delete the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
    </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
          <l2vpn>
           <evpn>
           <active>true</active>
           <apply-policys>
            <apply-policy xc:operation="remove">
            <direction>export</direction>
            <route-policy-name>policy2</route-policy-name>
            </apply-policy>
            <apply-policy xc:operation="remove">
            <direction>import</direction>
            <route-policy-name>policy1</route-policy-name>
            </apply-policy>
           </apply-policys>
           </evpn>
          </l2vpn>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Configuring Route Filtering Policies for a BGP Peer (in the BGP-VPNv4 Address Family View)

This section provides a sample of configuring route filtering policies for a BGP peer.

Table 3-635 Configuring route filtering policies for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-636 Configuring route filtering policies for a BGP peer

Item

Data

Description

Route filtering policy name

policy1

Configure route filtering policies named policy1 and policy2 to filter routes of a BGP peer in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Route filtering policy name

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
    <route-policy>
     <name>policy1</name>
     <nodes>
      <node>
       <node-index>20</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>   
    <route-policy>
     <name>policy2</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <vpnv4>
            <unicast>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="merge">
               <direction>export</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="merge">
               <direction>import</direction>
               <route-policy-name>policy2</route-policy-name>
             </apply-policy>
             </apply-policys>
            </unicast>
           </vpnv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply> 
Deleting Route Filtering Policies of a BGP Peer (in the BGP-VPNv4 Address Family View)

This section provides a sample of deleting the route filtering policies of a BGP peer.

Table 3-637 Deleting the route filtering policies of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-638 Deleting the route filtering policies of a BGP peer

Item

Data

Description

Route filtering policy name

policy1

Delete the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Route filtering policy name

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
    <route-policy>
     <name>policy1</name>
     <nodes>
      <node>
       <node-index>20</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>   
    <route-policy>
     <name>policy2</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <vpnv4>
            <unicast>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="remove">
               <direction>export</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="remove">
               <direction>import</direction>
               <route-policy-name>policy2</route-policy-name>
              </apply-policy>
             </apply-policys>
            </unicast>
           </vpnv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring the EVPN Address Family Route Switching Function

Enabling the EVPN Address Family Route Switching Function

This section provides a sample of enabling the EVPN address family route switching function.

Table 3-639 Enabling the EVPN address family route switching function

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/active

Data Requirements
Table 3-640 Enabling the EVPN address family route switching function

Item

Data

Description

Whether the EVPN address family route switching function is enabled

true

Enable the EVPN address family route switching function.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <af-specific-config>
           <ipv4>
            <unicast>
             <active>true</active>
             <prefix-list>site1</prefix-list>
             <direction>import</direction>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Disabling the EVPN Address Family Route Switching Function

This section provides a sample of disabling the EVPN address family route switching function.

Table 3-641 Disabling the EVPN address family route switching function

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/active

Data Requirements
Table 3-642 Disabling the EVPN address family route switching function

Item

Data

Description

Whether the EVPN address family route switching function is enabled

false

Disable the EVPN address family route switching function.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>false</active>
            </evpn>
           </l2vpn> 
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/>
</rpc-reply> 

Configuring the MD5 Authentication Password of a BGP Peer

Configuring the MD5 Authentication Password of a BGP Peer

This section provides a sample of configuring the MD5 authentication password of a BGP peer.

Table 3-643 Configuring the MD5 authentication password of a BGP peer

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/password/cipher-password

Data Requirements
Table 3-644 Configuring the MD5 authentication password of a BGP peer

Item

Data

Description

MD5 authentication password of a BGP peer

ab12

Configure the MD5 authentication password of a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <password>
           <cipher-password>ab12</cipher-password>
          </password> 
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Changing the MD5 Authentication Password of a BGP Peer

This section provides a sample of changing the MD5 authentication password of a BGP peer.

Table 3-645 Changing the MD5 authentication password of a BGP peer

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/password/cipher-password

Data Requirements
Table 3-646 Changing the MD5 authentication password of a BGP peer

Item

Data

Description

MD5 authentication password of a BGP peer

cd34

Change the MD5 authentication password of a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <password xc:operation="replace">
           <cipher-password>cd34</cipher-password>
          </password> 
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting the MD5 Authentication Password of a BGP Peer

This section provides a sample of deleting the MD5 authentication password of a BGP peer.

Table 3-647 Deleting the MD5 authentication password of a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/password/cipher-password

Data Requirements
Table 3-648 Deleting the MD5 authentication password of a BGP peer

Item

Data

Description

MD5 authentication password of a BGP peer

-

Delete the MD5 authentication password of a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <password xc:operation="remove">
          </password> 
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring Keychain Authentication for a BGP Peer

Configuring Keychain Authentication for a BGP Peer

This section provides a sample of configuring Keychain authentication for a BGP peer.

Table 3-649 Configuring Keychain authentication for a BGP peer

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/bgp-neighbor-keychain

Data Requirements
Table 3-650 Configuring Keychain authentication for a BGP peer

Item

Data

Description

Name for Keychain authentication

huawei

Configure Keychain authentication for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <bgp-neighbor-keychain>huawei</bgp-neighbor-keychain>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting Keychain Authentication for a BGP Peer

This section provides a sample of deleting Keychain authentication for a BGP peer.

Table 3-651 Deleting Keychain authentication for a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/bgp-neighbor-keychain

Data Requirements
Table 3-652 Deleting Keychain authentication for a BGP peer

Item

Data

Description

Name for Keychain authentication

-

Delete Keychain authentication for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <bgp-neighbor-keychain xc:operation="remove"></bgp-neighbor-keychain>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Modifying the Name for Keychain Authentication for a BGP Peer

This section provides a sample of modifying the name for Keychain authentication for a BGP peer.

Table 3-653 Modifying the name for Keychain authentication for a BGP peer

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/bgp-neighbor-keychain

Data Requirements
Table 3-654 Modifying the name for Keychain authentication for a BGP peer

Item

Data

Description

Name for Keychain authentication

suzhou

Change the name for Keychain authentication for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <bgp-neighbor-keychain xc:operation="replace">suzhou</bgp-neighbor-keychain>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring a BGP Peer Group

Creating a BGP Peer Group

This section provides a sample of creating a BGP peer group.

Table 3-655 Creating a BGP peer group

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/nbr-grp-name

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/bgp-type

Data Requirements
Table 3-656 Creating a BGP peer group

Item

Data

Description

Name of a BGP peer group

test1

Create a BGP peer group.

Type of a BGP peer group

internal

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>59</remote-as>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting a BGP Peer Group

This section provides a sample of deleting a BGP peer group.

Table 3-657 Deleting a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/nbr-grp-name

Data Requirements
Table 3-658 Deleting a BGP peer group

Item

Data

Description

Name of a BGP peer group

test1

Delete a BGP peer group.

Type of a BGP peer group

internal

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group xc:operation="remove">
          <nbr-grp-name>test1</nbr-grp-name>
          <bgp-type>external</bgp-type>
          <remote-as>59</remote-as>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Configuring Route Switching of a BGP Peer Group

Enabling Route Switching of a BGP Peer Group (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of enabling route switching of a BGP peer group.

Table 3-659 Enabling route switching of a BGP peer group

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/active

Data Requirements
Table 3-660 Enabling route switching of a BGP peer group

Item

Data

Description

Whether route switching of a BGP peer group is enabled

true

Enable route switching of a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
          <ipv4>
           <unicast>
            <active>true</active>
           </unicast>
          </ipv4>  
          </af-specific-config>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Disabling Route Switching of a BGP Peer Group (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of disabling route switching of a BGP peer group.

Table 3-661 Disabling route switching of a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/active

Data Requirements
Table 3-662 Disabling route switching of a BGP peer group

Item

Data

Description

Whether route switching of a BGP peer group is enabled

false

Disable route switching of a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
          <ipv4>
           <unicast>
            <active>false</active>
           </unicast>
          </ipv4>  
          </af-specific-config>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Enabling the Route Switching Function for a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of enabling the route switching function for a BGP peer group.

Table 3-663 Enabling the route switching function for a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/active

Data Requirements
Table 3-664 Enabling the route switching function for a BGP peer group

Item

Data

Description

Enabling the route switching function for a BGP peer group

true

Enabling the route switching function for a BGP peer group

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active xc:operation="merge">true</active>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling the Route Switching Function for a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of disabling the route switching function for a BGP peer group.

Table 3-665 Disabling the route switching function for a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/active

Data Requirements
Table 3-666 Disabling the route switching function for a BGP peer group

Item

Data

Description

Disabling the route switching function for a BGP peer group

true

Disabling the route switching function for a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
            <active xc:operation="remove">true</active>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring RR of a BGP Peer Group

Enabling RR of a BGP Peer Group (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of enabling RR of a BGP peer group.

Table 3-667 Enabling RR of a BGP peer group

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/route-reflector-client

Data Requirements
Table 3-668 Enabling RR of a BGP peer group

Item

Data

Description

Whether RR of a BGP peer group is enabled

true

Enable RR of a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
          <ipv4>
           <unicast>
            <route-reflector-client>true</route-reflector-client>
           </unicast>
          </ipv4>  
          </af-specific-config>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Disabling RR of a BGP Peer Group (in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of disabling RR of a BGP peer group.

Table 3-669 Disabling RR of a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/route-reflector-client

Data Requirements
Table 3-670 Disabling RR of a BGP peer group

Item

Data

Description

Whether RR of a BGP peer group is enabled

false

Disable RR of a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
          <ipv4>
           <unicast>
            <route-reflector-client>false</route-reflector-client>
           </unicast>
          </ipv4>  
          </af-specific-config>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Enabling RR for a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of enabling RR for a BGP peer group.

Table 3-671 Enabling RR for a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Data Requirements
Table 3-672 Enabling RR for a BGP peer group

Item

Data

Description

Enabling RR for a BGP peer group

true

Enabling RR for a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
            <active>true</active>
            <route-reflector-client xc:operation="merge">true</route-reflector-client>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling RR for a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of disabling RR for a BGP peer group.

Table 3-673 Disabling RR for a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Data Requirements
Table 3-674 Disabling RR for a BGP peer group

Item

Data

Description

Disabling RR for a BGP peer group

true

Disabling RR for a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
            <active>true</active>
            <route-reflector-client xc:operation="remove">true</route-reflector-client>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Enabling RR for a BGP Peer Group (in the BGP-EVPN Address Family View)

This section provides a sample of enabling RR for a BGP peer group.

Table 3-675 Enabling RR for a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/route-reflector-client

Data Requirements
Table 3-676 Enabling RR for a BGP peer group

Item

Data

Description

Enabling RR for a BGP peer group

true

Enabling RR for a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>site1</nbr-grp-name>
           <bgp-type>internal</bgp-type>
           <remote-as>65001</remote-as>
           <af-specific-config>
            <l2vpn>
             <evpn>
              <active>true</active>
              <route-reflector-client xc:operation="merge">true</route-reflector-client>
             </evpn>
            </l2vpn>
           </af-specific-config>
          </bgp-neighbor-group>                                     
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling RR for a BGP Peer Group (in the BGP-EVPN Address Family View)

This section provides a sample of disabling RR for a BGP peer group.

Table 3-677 Disabling RR for a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/route-reflector-client

Data Requirements
Table 3-678 Disabling RR for a BGP peer group

Item

Data

Description

Disabling RR for a BGP peer group

true

Disabling RR for a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
         <bgp-neighbor-groups>
          <bgp-neighbor-group>
           <nbr-grp-name>site1</nbr-grp-name>
           <bgp-type>internal</bgp-type>
           <remote-as>65001</remote-as>
           <af-specific-config>
            <l2vpn>
             <evpn>
              <active>true</active>
              <route-reflector-client xc:operation="remove">true</route-reflector-client>
             </evpn>
            </l2vpn>
           </af-specific-config>
          </bgp-neighbor-group>
         </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>

Configuring a Route Filtering Policy of a BGP Peer Group (Bidirectional Filtering)

Configuring a Route Filtering Policy of a BGP Peer Group(in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of configuring a route filtering policy of a BGP peer group.

Table 3-679 Configuring a route filtering policy of a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-680 Configuring a route filtering policy of a BGP peer group

Item

Data

Description

Number of the local AS

100

Configure a route filtering policy named policy1 to filter routes of a BGP peer group in both directions.

Remote AS number of an IPv4 peer group

59

Name of an IPv4 peer group

test1

Name of a route filtering policy

policy1

Direction of the route filtering policy

import

Name of a route filtering policy

policy1

Direction of the route filtering policy

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">   
    <route-policy xc:operation="merge">
     <name>policy1</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>sdwan</name>
     <routing-protocols>
      <routing-protocol>
       <name>sdwan</name>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" xc:operation="merge">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
           <ipv4>
            <unicast>
             <active>true</active>
             <apply-policys>
              <apply-policy>
               <direction>import</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy>
               <direction>export</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
  <ok/> 
</rpc-reply> 
Deleting a Route Filtering Policy of a BGP Peer Group(in the BGP-IPv4 Unicast Address Family View)

This section provides a sample of deleting a route filtering policy of a BGP peer group.

Table 3-681 Deleting a route filtering policy of a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/unicast/apply-policys/apply-policy

Data Requirements
Table 3-682 Deleting a route filtering policy of a BGP peer group

Item

Data

Description

Number of the local AS

100

Delete the route filtering policy that is named policy1 and used to filter routes of a BGP peer group in both directions.

Remote AS number of an IPv4 peer group

59

Name of an IPv4 peer group

test1

Name of a route filtering policy

policy1

Direction of the route filtering policy

import

Name of a route filtering policy

policy1

Direction of the route filtering policy

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="NETCONFIG_60ab9d6e963d4862b5288ed12e61f302">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>sdwan</name>
     <routing-protocols>
      <routing-protocol>
       <name>sdwan</name>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <af-specific-config>
           <ipv4>
            <unicast>
             <active>true</active>
             <apply-policys xc:operation="remove">
              <apply-policy>
               <direction>import</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy>
               <direction>export</direction>
               <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
            </unicast>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DDEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Configuring Route Filtering Policies for a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of configuring route filtering policies for a BGP peer group.

Table 3-683 Configuring route filtering policies for a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-684 Configuring route filtering policies for a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Configure route filtering policies named policy1 and policy2 to filter routes of a BGP peer group in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="merge">
              <direction>export</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="merge">
              <direction>import</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Changing the Route Filtering Policies of a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of changing the route filtering policies of a BGP peer group.

Table 3-685 Changing the route filtering policies of a BGP peer group

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-686 Changing the route filtering policies of a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Change the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer group in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="replace">
              <direction>export</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="replace">
              <direction>import</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Deleting the Route Filtering Policies of a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of deleting the route filtering policies of a BGP peer group.

Table 3-687 Deleting the route filtering policies of a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/apply-policys/apply-policy

Data Requirements
Table 3-688 Deleting the route filtering policies of a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Delete the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer group in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="remove">
              <direction>export</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="remove">
              <direction>import</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Configuring Route Filtering Policies for a BGP Peer Group (in the BGP-EVPN Address Family View)

This section provides a sample of configuring route filtering policies for a BGP peer group.

Table 3-689 Configuring route filtering policies for a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-690 Configuring route filtering policies for a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Configure route filtering policies named policy1 and policy2 to filter routes of a BGP peer group in the export and import directions respectively.

Direction in which a route filtering policy is applied

export

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>site1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="merge">
              <direction>export</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="merge">
             <direction>import</direction>
             <route-policy-name>policy2</route-policy-name>
             </apply-policy>
            </apply-policys>
           </evpn>
          </l2vpn>
         </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Changing the Route Filtering Policies of a BGP Peer Group (in the BGP-EVPN Address Family View)

This section provides a sample of changing the route filtering policies of a BGP peer group.

Table 3-691 Changing the route filtering policies of a BGP peer group

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-692 Changing the route filtering policies of a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Change the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer group in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>site1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
           <af-specific-config>
            <l2vpn>
             <evpn>
              <active>true</active>
              <apply-policys>
               <apply-policy xc:operation="replace">
               <direction>export</direction>
               <route-policy-name>policy2</route-policy-name>
               </apply-policy>
               <apply-policy xc:operation="replace">
               <direction>import</direction>
               <route-policy-name>policy1</route-policy-name>
               </apply-policy>
              </apply-policys>
             </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Deleting the Route Filtering Policies of a BGP Peer Group (in the BGP-EVPN Address Family View)

This section provides a sample of deleting the route filtering policies of a BGP peer group.

Table 3-693 Deleting the route filtering policies of a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/ietf-routing:routing-protocols/ietf-routing:routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/apply-policys/apply-policy

Data Requirements
Table 3-694 Deleting the route filtering policies of a BGP peer group

Item

Data

Description

Name of a route filtering policy

policy1

Delete the route filtering policies named policy1 and policy2, which are used to filter routes of a BGP peer group in the import and export directions respectively.

Direction in which a route filtering policy is applied

import

Name of a route filtering policy

policy2

Direction in which a route filtering policy is applied

export

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
     <route-policy>
      <name>policy1</name>
       <nodes>
        <node>
         <node-index>20</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>   
     <route-policy>
      <name>policy2</name>
       <nodes>
        <node>
         <node-index>10</node-index>
         <match-mode>permit</match-mode>
        </node>
       </nodes>
     </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>site1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
           <af-specific-config>
            <l2vpn>
             <evpn>
             <active>true</active>
             <apply-policys>
              <apply-policy xc:operation="remove">
              <direction>export</direction>
              <route-policy-name>policy2</route-policy-name>
              </apply-policy>
              <apply-policy xc:operation="remove">
              <direction>import</direction>
              <route-policy-name>policy1</route-policy-name>
              </apply-policy>
             </apply-policys>
             </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring a Specified Listening Network Segment

Configuring a Specified Listening Network Segment

This section provides a sample of configuring a specified listening network segment.

Table 3-695 Configuring a specified listening network segment

Operation

XPATH

edit-config: default

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/address

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/mask

Data Requirements
Table 3-696 Configuring a specified listening network segment

Item

Data

Description

IPv4 address of a specified listening network segment

192.165.6.5

Configure a specified listening network segment.

Mask of a specified listening network segment

255.255.0.0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <listen-net>
           <address>192.165.6.5</address>
           <mask>255.255.0.0</mask>
          </listen-net>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 
Deleting a Specified Listening Network Segmen

This section provides a sample of deleting a specified listening network segment.

Table 3-697 Deleting a specified listening network segment

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/address

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/listen-net/mask

Data Requirements
Table 3-698 Deleting a specified listening network segment

Item

Data

Description

IPv4 address of a specified listening network segment

192.165.6.5

Delete a specified listening network segment.

Mask of a specified listening network segment

255.255.0.0

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>56</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <listen-net xc:operation="remove">
           <address>192.165.6.5</address>
           <mask>255.255.0.0</mask>
          </listen-net>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
<ok/> 
</rpc-reply> 

Setting the Number of BGP Routes for Load Balancing

Setting the Number of BGP Routes for Load Balancing

This section provides a sample of setting the number of BGP routes for load balancing.

Table 3-699 Setting the number of BGP routes for load balancing

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/load-balancing/max-number

Data Requirements
Table 3-700 Setting the number of BGP routes for load balancing

Item

Data

Description

Number of the local AS

56

Set the number of BGP routes for load balancing to 2.

Number of routes for load balancing

2

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <load-balancing>
            <max-number xc:operation="merge">2</max-number>
            </load-balancing>         
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Changing the Number of BGP Routes for Load Balancing

This section provides a sample of changing the number of BGP routes for load balancing.

Table 3-701 Changing the number of BGP routes for load balancing

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/load-balancing/max-number

Data Requirements
Table 3-702 Changing the number of BGP routes for load balancing

Item

Data

Description

Number of the local AS

56

Change the number of BGP routes for load balancing to 3.

Number of routes for load balancing

3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <load-balancing>
            <max-number xc:operation="replace">3</max-number>
            </load-balancing>         
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the Setting of the Number of BGP Routes for Load Balancing

This section provides a sample of deleting the setting of the number of BGP routes for load balancing.

Table 3-703 Deleting the setting of the number of BGP routes for load balancing

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/ipv4/unicast/load-balancing/max-number

Data Requirements
Table 3-704 Deleting the setting of the number of BGP routes for load balancing

Item

Data

Description

Number of the local AS

56

Delete the setting of the number of BGP routes for load balancing

Number of routes for load balancing

3

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol>
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>56</local-as-number>
         <af-configuration>
          <ipv4>
           <unicast>
            <load-balancing>
            <max-number xc:operation="remove">3</max-number>
            </load-balancing>         
           </unicast>            
          </ipv4>            
         </af-configuration>          
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring BGP to Filter Global Received and Sent Routes Based on an IPv4 Prefix List

Configuring BGP to Filter Global Received and Sent Routes Based on an IPv4 Prefix List

This section provides a sample of configuring BGP to filter global received and sent routes based on an IPv4 prefix list.

Table 3-705 Configuring BGP to filter global received and sent routes based on an IPv4 prefix list

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/filter-policy

Data Requirements
Table 3-706 Configuring BGP to filter global received and sent routes based on an IPv4 prefix list

Item

Data

Description

Name of an IPv4 prefix list

site1

Configure BGP to filter global received routes based on the IPv4 prefix list site1.

Route filtering direction

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> 
    <routing-instance> 
     <name>sdwan</name> 
     <routing-protocols> 
      <routing-protocol> 
       <type xmlns:huawei-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">huawei-bgp:bgp-routing-protocol</type> 
       <name>sdwan</name> 
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" xc:operation="merge"> 
        <bgp-router> 
         <local-as-number>65001</local-as-number> 
         <filter-policy> 
          <ip-prefix-name>site1</ip-prefix-name> 
          <direction>import</direction> 
         </filter-policy> 
        </bgp-router> 
       </bgp-routing> 
       <enabled>true</enabled> 
      </routing-protocol> 
     </routing-protocols> 
     <enabled>true</enabled> 
     <type xmlns:ietf-routing="urn:ietf:params:xml:ns:yang:ietf-routing">ietf-routing:default-routing-instance</type> 
    </routing-instance> 
   </routing> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> 
 <ok/> 
</rpc-reply>
Deleting BGP from Filtering Global Received and Sent Routes Based on an IPv4 Prefix List

This section provides a sample of deleting BGP from filtering global received and sent routes based on an IPv4 prefix list.

Table 3-707 Deleting BGP from filtering global received and sent routes based on an IPv4 prefix list

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/filter-policy

Data Requirements
Table 3-708 Deleting BGP from filtering global received and sent routes based on an IPv4 prefix list

Item

Data

Description

Name of an IPv4 prefix list

site1

Indicates that received routes are not filtered.

Route filtering direction

import

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> 
 <edit-config> 
  <target> 
   <running/> 
  </target> 
  <error-option>rollback-on-error</error-option> 
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> 
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing"> 
    <routing-instance> 
     <name>sdwan</name> 
     <routing-protocols> 
      <routing-protocol> 
       <type xmlns:huawei-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">huawei-bgp:bgp-routing-protocol</type> 
       <name>sdwan</name> 
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" xc:operation="merge"> 
        <bgp-router> 
         <local-as-number>65001</local-as-number> 
         <filter-policy xc:operation="remove"> 
          <ip-prefix-name>site1</ip-prefix-name> 
          <direction>import</direction> 
         </filter-policy> 
        </bgp-router> 
       </bgp-routing> 
       <enabled>true</enabled> 
      </routing-protocol> 
     </routing-protocols> 
     <enabled>true</enabled> 
     <type xmlns:ietf-routing="urn:ietf:params:xml:ns:yang:ietf-routing">ietf-routing:default-routing-instance</type> 
    </routing-instance> 
   </routing> 
  </config> 
 </edit-config> 
</rpc>
Response Example

Sample of successful response

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

Configuring MD5 Authentication for BGP Messages Based on the Peer Address

Configuring MD5 Authentication for BGP Messages Based on the Peer Address

This section provides a sample of configuring MD5 authentication for BGP messages based on the peer address.

Table 3-709 Configuring MD5 authentication for BGP messages based on the peer address

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/cipher-password

Data Requirements
Table 3-710 Configuring MD5 authentication for BGP messages based on the peer address

Item

Data

Description

Peer address

192.168.2.5

Configure MD5 authentication for BGP messages exchanged between the local device and the peer 192.168.2.5 to establish a TCP connection and set the ciphertext password to huawei123.

Peer AS number

59

Ciphertext password

huawei123

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>65001</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <cipher-password xc:operation="merge">huawei123</cipher-password>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting MD5 Authentication Configured for BGP Messages Based on the Peer Address

This section provides a sample of deleting MD5 authentication configured for BGP messages based on the peer address.

Table 3-711 Deleting MD5 authentication configured for BGP messages based on the peer address

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/cipher-password

Data Requirements
Table 3-712 Deleting MD5 authentication configured for BGP messages based on the peer address

Item

Data

Description

Peer address

192.168.2.5

Delete MD5 authentication configured for BGP messages exchanged between the local device and the peer 192.168.2.5 to establish a TCP connection.

Peer AS number

59

Ciphertext password

huawei123

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>65001</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <cipher-password xc:operation="remove">huawei123</cipher-password>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring MD5 Authentication for BGP Messages Based on the Peer Group Name

Configuring MD5 Authentication for BGP Messages Based on the Peer Group Name

This section provides a sample of configuring MD5 authentication for BGP messages based on the peer group name.

Table 3-713 Configuring MD5 authentication for BGP messages based on the peer group name

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/cipher-password

Data Requirements
Table 3-714 Configuring MD5 authentication for BGP messages based on the peer group name

Item

Data

Description

Peer group name

test1

Configure MD5 authentication for BGP messages exchanged between the local device and the peer group named test1 and set the ciphertext password to huawei123.

Peer group AS number

59

Peer group type

external

Ciphertext password

huawei123

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>65001</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups >
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <bgp-type>external</bgp-type>
          <cipher-password xc:operation="merge">huawei123</cipher-password>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting MD5 Authentication Configured for BGP Messages Based on the Peer Group Name

This section provides a sample of deleting MD5 authentication configured for BGP messages based on the peer group name.

Table 3-715 Deleting MD5 authentication configured for BGP messages based on the peer group name

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/cipher-password

Data Requirements
Table 3-716 Deleting MD5 authentication configured for BGP messages based on the peer group name

Item

Data

Description

Peer group name

test1

Delete MD5 authentication configured for BGP messages exchanged between the local device and the peer group named test1 to establish a TCP connection.

Peer group AS number

59

Peer group type

external

Ciphertext password

huawei123

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>65001</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups >
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <bgp-type>external</bgp-type>
          <cipher-password xc:operation="remove">huawei123</cipher-password>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring the Hold Time and Keepalive Time for a BGP Peer

Configuring the Hold Time and Keepalive Time for a BGP Peer

This section provides a sample of configuring the hold time and keepalive time for a BGP peer.

Table 3-717 Configuring the Hold Time and Keepalive Time for a BGP Peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/keepalive-time

Data Requirements
Table 3-718 Configuring the Hold Time and Keepalive Time for a BGP Peer

Item

Data

Description

Hold time of a BGP peer

600

Set the hold time and keepalive time of a BGP peer to 600s and 62s respectively.

Keepalive time of a BGP peer

62

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>65001</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <hold-time xc:operation="merge">600</hold-time>
          <keepalive-time xc:operation="merge">62</keepalive-time>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Changing the Hold Time and Keepalive Time of a BGP Peer

This section provides a sample of changing the hold time and keepalive time of a BGP peer.

Table 3-719 Changing the Hold Time and Keepalive Time of a BGP Peer

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/keepalive-time

Data Requirements
Table 3-720 Changing the Hold Time and Keepalive Time of a BGP Peer

Item

Data

Description

Hold time of a BGP peer

700

Change the hold time and keepalive time of a BGP peer to 700s and 35s respectively.

Keepalive time of a BGP peer

35

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>65001</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <hold-time xc:operation="replace">700</hold-time>
          <keepalive-time xc:operation="replace">35</keepalive-time>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the Hold Time and Keepalive Time of a BGP Peer

This section provides a sample of deleting the hold time and keepalive time of a BGP peer.

Table 3-721 Deleting the Hold Time and Keepalive Time of a BGP Peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/keepalive-time

Data Requirements
Table 3-722 Deleting the Hold Time and Keepalive Time of a BGP Peer

Item

Data

Description

Hold time of a BGP peer

600

Delete the hold time 600s and keepalive time 62s of a BGP peer.

Keepalive time of a BGP peer

62

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>65001</local-as-number>         
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>59</remote-as>
          <hold-time xc:operation="remove">600</hold-time>
          <keepalive-time xc:operation="remove">62</keepalive-time>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring the Hold Time and Keepalive Time for a BGP Peer Group

Configuring the Hold Time and Keepalive Time for a BGP Peer Group

This section provides a sample of configuring the hold time and keepalive time for a BGP peer group.

Table 3-723 Configuring the Hold Time and Keepalive Time for a BGP Peer Group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/keepalive-time

Data Requirements
Table 3-724 Configuring the Hold Time and Keepalive Time for a BGP Peer Group

Item

Data

Description

Hold time of a BGP peer group

600

Set the hold time and keepalive time of a BGP peer group to 600s and 62s respectively.

Keepalive time of a BGP peer group

62

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>65001</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups >
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <bgp-type>external</bgp-type>
          <hold-time xc:operation="merge">600</hold-time>
          <keepalive-time xc:operation="merge">62</keepalive-time>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Changing the Hold Time and Keepalive Time of a BGP Peer Group

This section provides a sample of changing the hold time and keepalive time of a BGP peer group.

Table 3-725 Changing the Hold Time and Keepalive Time of a BGP Peer Group

Operation

XPATH

edit-config:replace

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/keepalive-time

Data Requirements
Table 3-726 Changing the Hold Time and Keepalive Time of a BGP Peer Group

Item

Data

Description

Hold time of a BGP peer group

700

Change the hold time and keepalive time of a BGP peer group to 700s and 35s respectively.

Keepalive time of a BGP peer group

35

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>65001</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups >
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <bgp-type>external</bgp-type>
          <hold-time xc:operation="replace">700</hold-time>
          <keepalive-time xc:operation="replace">35</keepalive-time>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>
Deleting the Hold Time and Keepalive Time of a BGP Peer Group

This section provides a sample of deleting the hold time and keepalive time of a BGP peer group.

Table 3-727 Deleting the Hold Time and Keepalive Time of a BGP Peer Group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/hold-time

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/keepalive-time

Data Requirements
Table 3-728 Deleting the Hold Time and Keepalive Time of a BGP Peer Group

Item

Data

Description

Hold time of a BGP peer group

600

Delete the hold time 600s and keepalive time 62s of a BGP peer group.

Keepalive time of a BGP peer group

62

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>adfa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp" >
        <bgp-router>
         <local-as-number>65001</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups >
         <bgp-neighbor-group>
          <nbr-grp-name>test1</nbr-grp-name>
          <remote-as>59</remote-as>
          <bgp-type>external</bgp-type>
          <hold-time xc:operation="remove">600</hold-time>
          <keepalive-time xc:operation="remove">62</keepalive-time>
         </bgp-neighbor-group>          
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <ok/>
</rpc-reply>

Configuring the Route Switching Function for a BGP Peer (in the tunnel-encap-ext View)

Enabling the Route Switching Function for a BGP Peer

This section provides a sample of enabling the route switching function for a BGP peer.

Table 3-729 Enabling the route switching function for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/ietf-routing:routing-protocols/ietf-routing:routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/active

Data Requirements
Table 3-730 Enabling the route switching function for a BGP peer

Item

Data

Description

Enabling the route switching function for a BGP peer

true

Enabling the route switching function for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active xc:operation="merge">true</active>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling the Route Switching Function for a BGP Peer

This section provides a sample of disabling the route switching function for a BGP peer.

Table 3-731 Disabling the Route Switching Function for a BGP Peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/active

Data Requirements
Table 3-732 Disabling the Route Switching Function for a BGP Peer

Item

Data

Description

Disabling the Route Switching Function for a BGP Peer

true

Disabling the Route Switching Function for a BGP Peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active xc:operation="remove">true</active>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring RR for a BGP Peer

Enabling RR for a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of enabling RR for a BGP peer.

Table 3-733 Enabling RR for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Data Requirements
Table 3-734 Enabling RR for a BGP peer

Item

Data

Description

Enabling RR for a BGP peer

true

Enabling RR for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <route-reflector-client xc:operation="merge">true</route-reflector-client>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Disabling RR for a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of disabling RR for a BGP peer.

Table 3-735 Disabling RR for a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/route-reflector-client

Data Requirements
Table 3-736 Disabling RR for a BGP peer

Item

Data

Description

Disabling RR for a BGP peer

true

Disabling RR for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <route-reflector-client xc:operation="remove">true</route-reflector-client>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Enabling RR for a BGP Peer (in the BGP-EVPN Address Family View)

This section provides a sample of enabling RR for a BGP peer.

Table 3-737 Enabling RR for a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/route-reflector-client

Data Requirements
Table 3-738 Enabling RR for a BGP peer

Item

Data

Description

Enabling RR for a BGP peer

true

Enabling RR for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <route-reflector-client xc:operation="merge">true</route-reflector-client>
            </evpn>
           </l2vpn>
         </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling RR for a BGP Peer (in the BGP-EVPN Address Family View)

This section provides a sample of disabling RR for a BGP peer.

Table 3-739 Disabling RR for a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/route-reflector-client

Data Requirements
Table 3-740 Disabling RR for a BGP peer

Item

Data

Description

Disabling RR for a BGP peer

true

Disabling RR for a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <route-reflector-client xc:operation="remove">true</route-reflector-client>
            </evpn>
           </l2vpn>
         </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring BGP to Advertise the Community Attribute to a BGP Peer

Enabling BGP to Advertise the Community Attribute to a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of enabling BGP to advertise the community attribute to a BGP peer.

Table 3-741 Enabling BGP to advertise the community attribute to a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/advertise-community

Data Requirements
Table 3-742 Enabling BGP to advertise the community attribute to a BGP peer

Item

Data

Description

Enabling BGP to advertise the community attribute to a BGP peer

true

Enable BGP to advertise the community attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <advertise-community xc:operation="merge">true</advertise-community>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling BGP from Advertising the Community Attribute to a BGP Peer (in the tunnel-encap-ext View)

This section provides a sample of disabling BGP from advertising the community attribute to a BGP peer.

Table 3-743 Disabling BGP from advertising the community attribute to a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/advertise-community

Data Requirements
Table 3-744 Disabling BGP from advertising the community attribute to a BGP peer

Item

Data

Description

Disabling BGP from advertising the community attribute to a BGP peer

true

Disable BGP from advertising the community attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <advertise-community xc:operation="remove">true</advertise-community>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Enabling BGP to Advertise the Community Attribute to a BGP Peer (in the BGP-VPNv4 Address Family View)

This section provides a sample of enabling BGP to advertise the community attribute to a BGP peer.

Table 3-745 Enabling BGP to advertise the community attribute to a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/advertise-community

Data Requirements
Table 3-746 Enabling BGP to advertise the community attribute to a BGP peer

Item

Data

Description

Enabling BGP to advertise the community attribute to a BGP peer

true

Enable BGP to advertise the community attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
    <route-policy>
     <name>policy1</name>
     <nodes>
      <node>
       <node-index>20</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>   
    <route-policy>
     <name>policy2</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <vpnv4>
            <unicast>
             <active>true</active>            
              <advertise-community xc:operation="merge">true</advertise-community>            
            </unicast>
           </vpnv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Disabling BGP from Advertising the Community Attribute to a BGP Peer (in the BGP-VPNv4 Address Family View)

This section provides a sample of disabling BGP from advertising the community attribute to a BGP peer.

Table 3-747 Disabling BGP from advertising the community attribute to a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/vpnv4/unicast/advertise-community

Data Requirements
Table 3-748 Disabling BGP from advertising the community attribute to a BGP peer

Item

Data

Description

Disabling BGP from advertising the community attribute to a BGP peer

true

Disable BGP from advertising the community attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <route-policys xmlns="urn:huawei:params:xml:ns:yang:huawei-route-policy">
    <route-policy>
     <name>policy1</name>
     <nodes>
      <node>
       <node-index>20</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>   
    <route-policy>
     <name>policy2</name>
     <nodes>
      <node>
       <node-index>10</node-index>
       <match-mode>permit</match-mode>
      </node>
     </nodes>
    </route-policy>
   </route-policys>
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <vpnv4>
            <unicast>
             <active>true</active>            
              <advertise-community xc:operation="remove">true</advertise-community>            
            </unicast>
           </vpnv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring BGP to Advertise the Community Attribute to a BGP Peer Group

Enabling BGP to Advertise the Community Attribute to a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of enabling BGP to advertise the community attribute to a BGP peer group.

Table 3-749 Enabling BGP to advertise the community attribute to a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/advertise-community

Data Requirements
Table 3-750 Enabling BGP to advertise the community attribute to a BGP peer group

Item

Data

Description

Enabling BGP to advertise the community attribute to a BGP peer group

true

Enable BGP to advertise the community attribute to a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active>true</active>
             <advertise-community xc:operation="merge">true</advertise-community>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Disabling BGP from Advertising the Community Attribute to a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of disabling BGP from advertising the community attribute to a BGP peer group.

Table 3-751 Disabling BGP from advertising the community attribute to a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/ipv4/tunnel-encap/advertise-community

Data Requirements
Table 3-752 Disabling BGP from advertising the community attribute to a BGP peer group

Item

Data

Description

Disabling BGP from advertising the community attribute to a BGP peer group

true

Disable BGP from advertising the community attribute to a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
             <active>true</active>
             <advertise-community xc:operation="remove">true</advertise-community>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring an RR to Change the Path Attribute of BGP Routes Through an Export Policy

Enabling an RR to Change the Path Attribute of BGP Routes Through an Export Policy

This section provides a sample of enabling an RR to change the path attribute of BGP routes through an export policy.

Table 3-753 Enabling an RR to change the path attribute of BGP routes through an export policy

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/enable-change-path-attribute-reflection

Data Requirements
Table 3-754 Enabling an RR to change the path attribute of BGP routes through an export policy

Item

Data

Description

Enabling an RR to change the path attribute of BGP routes through an export policy

true

Enable an RR to change the path attribute of BGP routes through an export policy.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
          <af-configuration>
           <l2vpn>
            <evpn>
             <enable-change-path-attribute-reflection xc:operation="merge">true</enable-change-path-attribute-reflection> 
            </evpn>
          </l2vpn>
         </af-configuration>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884">
  <ok/> 
</rpc-reply>
Disabling an RR from Changing the Path Attribute of BGP Routes Through an Export Policy

This section provides a sample of disabling an RR from changing the path attribute of BGP routes through an export policy.

Table 3-755 Disabling an RR from changing the path attribute of BGP routes through an export policy

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-router/af-configuration/l2vpn/evpn/enable-change-path-attribute-reflection

Data Requirements
Table 3-756 Disabling an RR from changing the path attribute of BGP routes through an export policy

Item

Data

Description

Disabling an RR from changing the path attribute of BGP routes through an export policy

true

Disable an RR from changing the path attribute of BGP routes through an export policy.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
          <af-configuration>
           <l2vpn>
            <evpn>
             <enable-change-path-attribute-reflection xc:operation="remove">true</enable-change-path-attribute-reflection>
            </evpn>
           </l2vpn>
         </af-configuration>
        </bgp-router>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring BGP to Advertise the encap Type Attribute to a BGP Peer

Configuring BGP to Advertise the encap Type Attribute to a BGP Peer

This section provides a sample of configuring BGP to advertise the encap type attribute to a BGP peer.

Table 3-757 Configuring BGP to advertise the encap type attribute to a BGP peer

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/advertise-encap-type

Data Requirements
Table 3-758 Configuring BGP to advertise the encap type attribute to a BGP peer

Item

Data

Description

encap type

sd-wan

Configure BGP to advertise the encap type (sd-wan) attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <advertise-encap-type xc:operation="merge">sd-wan</advertise-encap-type>
            </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>
Deleting Configuring BGP to Advertise the encap Type Attribute to a BGP Peer

This section provides a sample of deleting configuring BGP to advertise the encap type attribute to a BGP peer.

Table 3-759 Deleting configuring BGP to advertise the encap type attribute to a BGP peer

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/l2vpn/evpn/advertise-encap-type

Data Requirements
Table 3-760 Deleting configuring BGP to advertise the encap type attribute to a BGP peer

Item

Data

Description

encap type

sd-wan

Delete configuring BGP to advertise the encap type (sd-wan) attribute to a BGP peer.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <advertise-encap-type xc:operation="remove">sd-wan</advertise-encap-type>
            </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Configuring BGP to Advertise the encap Type Attribute to a BGP Peer Group

Configuring BGP to Advertise the encap Type Attribute to a BGP Peer Group

This section provides a sample of configuring BGP to advertise the encap type attribute to a BGP peer group.

Table 3-761 Configuring BGP to advertise the encap type attribute to a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/advertise-encap-type

Data Requirements
Table 3-762 Configuring BGP to advertise the encap type attribute to a BGP peer group

Item

Data

Description

encap type

sd-wan

Configure BGP to advertise the encap type (sd-wan) attribute to a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
         <bgp-neighbor-groups>
          <bgp-neighbor-group>
           <nbr-grp-name>site1</nbr-grp-name>
           <bgp-type>internal</bgp-type>
           <remote-as>65001</remote-as>
           <af-specific-config>
            <l2vpn>
             <evpn>
              <active>true</active>
              <advertise-encap-type xc:operation="merge">sd-wan</advertise-encap-type>
             </evpn>
            </l2vpn>
           </af-specific-config>
          </bgp-neighbor-group>
         </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>  
Deleting Configuring BGP to Advertise the encap Type Attribute to a BGP Peer Group

This section provides a sample of deleting configuring BGP to advertise the encap type attribute to a BGP peer group.

Table 3-763 Deleting configuring BGP to advertise the encap type attribute to a BGP peer group

Operation

XPATH

edit-config:remove

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbor-groups/bgp-neighbor-group/af-specific-config/l2vpn/evpn/advertise-encap-type

Data Requirements
Table 3-764 Deleting configuring BGP to advertise the encap type attribute to a BGP peer group

Item

Data

Description

encap type

sd-wan

Delete configuring BGP to advertise the encap type (sd-wan) attribute to a BGP peer group.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>site1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>65001</remote-as>
          <af-specific-config>
           <l2vpn>
            <evpn>
             <active>true</active>
             <advertise-encap-type xc:operation="remove">sd-wan</advertise-encap-type>
            </evpn>
           </l2vpn>
          </af-specific-config>
         </bgp-neighbor-group>
        </bgp-neighbor-groups>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </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_44b89c8aa8fd4a918f793b73409d0884"> 
  <ok/> 
</rpc-reply>

Adding a BGP Peer to a BGP Peer Group

Adding a BGP Peer to a BGP Peer Group (in the tunnel-encap-ext View)

This section provides a sample of adding a BGP peer to a BGP peer group.

Table 3-765 Adding a BGP peer to a BGP peer group

Operation

XPATH

edit-config:merge

ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/huawei-bgp:bgp-routing/bgp-neighbors/bgp-neighbor/af-specific-config/ipv4/tunnel-encap/neighbour-group-name

Data Requirements
Table 3-766 Adding a BGP peer to a BGP peer group

Item

Data

Description

Name of a BGP peer group

nbrgrp1

Add a BGP peer to the BGP peer group nbrgrp1.

Request Example
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_44b89c8aa8fd4a918f793b73409d0884">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
   <routing xmlns="urn:ietf:params:xml:ns:yang:ietf-routing">
    <routing-instance>
     <name>aaaaa</name>
     <routing-protocols>
      <routing-protocol >
       <type xmlns:hw-bgp="urn:huawei:params:xml:ns:yang:huawei-bgp">hw-bgp:bgp-routing-protocol</type>
       <name>adfa</name>
       <bgp-routing xmlns="urn:huawei:params:xml:ns:yang:huawei-bgp">
        <bgp-router>
         <local-as-number>100</local-as-number>        
        </bgp-router>
        <bgp-neighbor-groups>
         <bgp-neighbor-group>
          <nbr-grp-name>nbrgrp1</nbr-grp-name>
          <bgp-type>internal</bgp-type>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
            <active>true</active>
            <route-reflector-client>true</route-reflector-client>
            <apply-policys>
             <apply-policy>
              <direction>export</direction>
              <route-policy-name>policy1</route-policy-name>
             </apply-policy>
             <apply-policy>
              <direction>import</direction>
              <route-policy-name>policy2</route-policy-name>
             </apply-policy>
            </apply-policys>
            <advertise-community>true</advertise-community>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor-group>         
        </bgp-neighbor-groups>
        <bgp-neighbors>
         <bgp-neighbor>
          <peer-address>192.168.2.5</peer-address>
          <remote-as>100</remote-as>
          <af-specific-config>
           <ipv4>
            <tunnel-encap>
              <active>true</active>
              <neighbour-group-name xc:operation="merge">nbrgrp1</neighbour-group-name>
            </tunnel-encap>
           </ipv4>
          </af-specific-config>
         </bgp-neighbor>         
        </bgp-neighbors>
       </bgp-routing>
      </routing-protocol>
     </routing-protocols>
    </routing-instance>
   </routing>
  </config>
 </edit-config>
</rpc>
Response Example