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

Configuration Guide - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - IP Routing
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).
Limitations for BGP-NE05E

Limitations for BGP-NE05E

Restrictions

Guidelines

Impact

If non-Huawei devices, Huawei devices running V300R003C10, and Huawei devices running versions earlier than V300R003C10 are deployed on the network, the VPN ORF function is not recommended.

Configure a default route for VPN ORF.

Because the address family capability supported by VPN ORF varies according to different devices, L2VPN MVPN services are affected.

If an IPv4 BGP peer's status changes, an alarm is reported to the NMS based on the bgpEstablishedNotification or bgpBackwardTransNotification object in the public MIB. However, if an IPv6 BGP peer's status changes, no alarm is reported to the NMS.

View related alarm information on the device.

IPv6 BGP peer status change alarms cannot be viewed on the NMS.

EBGP peers do not support the following features:

1. Route reflector

2. RPKI

3. Best-external

4. Add-path

IBGP peers do not support the following features:

1. EBGP-max-hop

2. MPLS local IFNET

3. Fake AS

Feature exclusiveness:The ebgp-max-hop and valid-ttl-hops functions are mutually exclusive.

No action is required.

None

If the as-set parameter is specified when configuring route summarization, the AS_Sequence of the summary route is generated according to the same AS_Sequence in the AS_Path attribute of all specific routes. The rest AS numbers form the AS_Set. The number of AS_Path attributes after summarization must not exceed 250; otherwise, the AS_Path attribute is empty.

Plan the test configurations properly.

The service function is incorrect.

The undo peer x.x.x.x group and undo peer commands have the same function.

Plan the test configurations properly.

The service function is incorrect.

If a feature is not configured for a peer or the default value is configured for the peer, and then the peer is added to a peer group which has a non-default value of the feature configured, the peer inherits the feature configuration from the peer group.

If a peer in a peer group has the same configuration of a feature with the peer group, and then the feature is modified for the peer group, the feature configuration of the peer changes accordingly.

If a peer in a peer group and the peer group have different configurations of a feature, and then the feature is modified for the peer, the feature configuration of the peer remains inconsistent with that of the peer group.

Plan the test configurations properly.

The service function is incorrect.

To advertise default routes, you need to run both the default-route imported and import-route commands. If either command is not run, default routes cannot be advertised even when they are available in the routing table.

Plan the test configurations properly.

The service function is incorrect.

IPv6 IBGP peers can be enabled in the BGP VPNv4 address family, whereas IPv6 EBGP peers cannot.

IPv6 IBGP peers can be enabled in the BGP VPNv4 address family, whereas IPv6 EBGP peers cannot.

None

IPv4 peers and IPv6 peers cannot be both enabled in the BGP VPNv4 address family.

IPv4 peers and IPv6 peers cannot be both enabled in the BGP VPNv4 address family.

None

BGP routes cannot be iterated to SRv6 LSPs; otherwise, the routes are inactive after iteration.

BGP routes cannot be iterated to SRv6 LSPs; otherwise, the routes are inactive after iteration.

None

Static routes cannot be iterated to SRv6 LSPs; otherwise, the routes are inactive after iteration.

Static routes cannot be iterated to SRv6 LSPs; otherwise, the routes are inactive after iteration.

None

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 38048

Downloads: 57

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