Implementation of bgp4, Bgp4 neighbor local as – Brocade Virtual ADX Switch and Router Guide (Supporting ADX v03.1.00) User Manual
Page 218
204
Brocade Virtual ADX Switch and Router Guide
53-1003246-01
Implementation of BGP4
8
Implementation of BGP4
BGP4 is described in RFC 1771 and the latest BGP4 drafts. The implementation fully complies with
RFC 1771 and supports the following:
•
RFC 1745 (OSPF Interactions)
•
RFC 1997 (BGP4 Communities Attributes)
•
RFC 2385 (TCP MD5 Signature Option)
•
RFC 2439 (Route Flap Dampening)
•
RFC 2842 and 3392 (Capability Advertisement)
•
RFC 2918 (Route Refresh Capability)
•
RFC 3392 (BGP4 Capability Advertisement)
BGP4 neighbor local AS
This feature allows you to configure a device so that it adds a peer to an AS that is different from
the AS to which it actually belongs. This feature is useful when an ISP is acquired by another ISP. In
this situation, customers of the acquired ISP might not want to (or might not be able to) adjust their
configuration to connect to the AS of the acquiring provider.
, Customer C is connected to ISP-A which is in AS 100 and ISP-B which is in
AS 200.
FIGURE 26
Example of customer connected to two ISPs