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


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


ME60 V800R010C10SPC500 Feature Description - WAN Access 01

This is ME60 V800R010C10SPC500 Feature Description - WAN Access

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).
Poison Reverse

Poison Reverse

Poison reverse allows a RIPng-enabled interface to set the cost of the route that it learns from a neighbor to 16 (indicating that the route is unreachable) and then send the route back. After receiving this route, the neighbor can delete the useless route from its routing table, which prevents loops.

Figure 5-5 Networking for poison reverse

In Figure 5-5, if poison reverse is not configured, Device B sends Device A a route learned from Device A. The cost of the route from Device A to network 123::0/64 is 1. If the route from Device A to network 123::0/64 becomes unreachable and Device B does not receive an Update packet from Device A and keeps sending Device A the route from Device A to network 123::0/64, a routing loop occurs.

With poison reverse, after Device B receives the route from Device A, Device B sends a route unreachable message to Device A with cost 16. Device A then no longer learns the reachable route from Device B, which prevents routing loops.

If both poison reverse and split horizon are configured, only poison reverse takes effect.

Updated: 2019-01-04

Document ID: EDOC1100059473

Views: 17874

Downloads: 10

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next