BGP
98
• RFC2385 TCP MD5 protection
• RFC2796 Route reflector peers
• RFC3392 Capabilities negotiation
• RFC3065 Confederation peers
• RFC5082 TTL Security
• Multiple independent routing tables allowing independent BGP operations
• Multiple AS operation
15.2.3. Simple example setup
A typical installation may have transit connections from which a complete internet routing table is received,
peers which provide their own routes only, internal peers making an IBGP mesh, customers to which transit
is provided and customer routes may be accepted. To make this set up simple the <peer> definition contains a
type attribute. This allows simple BGP configuration such as:-
<bgp as="12345">
<peer as="666" name="transit1" type="transit" ip="1.2.3.4"/>
<peer as="777" name="transit2" type="transit" ip="2.3.4.5 2.3.4.6"/\>
<peer type="internal" ip="5.6.7.8"/\>
</bgp>
This example has two transit providers, the second of which is actually two peer IP addresses, and one internal
connection. Note that the peer AS is optional and unnecessary on internal type as it has to match ours.
The exact elements that apply are defined in the XML/XSD documentation for your software release.
15.2.4. Peer type
The type attribute controls some of the behaviour of the session and some of the default settings as follows.
Table 15.1. Peer types
Type
Meaning
normal
Normal mode, no special treatment. Follows normal BGP rules.
transit
Used when talking to a transit provider, or a peer that provides more than just their own
routes. Peers only with different AS. The community no-export is added to imported routes
unless explicitly de-tagged
peer
Used when talking to a peer providing only their own routes. Peers only with different AS.
The community no-export is added to imported routes unless explicitly de-tagged allow-
only-their-as defaults to true
customer
Used when talking to customers routers, expecting transit feed and providing their own
routes Peers only with different AS allow-only-their-as defaults to true allow-export
defaults to true The community no-export is added to exported routes unless explicitly de-
tagged
internal
For IBGP links. Peers only with same AS allow-own-as defaults to true
reflector
For IBGP links that are a route-reflector. Route reflector rules apply Peers only with same
AS allow-own-as defaults to true
