To configure BGP sessions between peering networks, you must configure point-to-point sessions between the external peers of the networks. Additionally, you must configure BGP internally to provide a means by which BGP route advertisements can be forwarded throughout the network. Because of the full mesh requirement of IBGP, you must configure individual peering sessions between all internal nodes of the network—unless you use route reflectors or confederations.
Figure 53 shows a typical network with external and internal peer sessions. In the sample network, the Services Router in AS 17 is fully meshed with its internal peers in the group internal-peers, which have IP addresses starting at 192.168.6.4.
Figure 53: Typical Network with EBGP External Sessions and IBGP Internal Sessions

To configure IBGP in the network shown in Figure 53:
Table 56: Configuring IBGP Peering Sessions
|
Task |
J-Web Configuration Editor |
CLI Configuration Editor |
|---|---|---|
|
Navigate to the Bgp level in the configuration hierarchy. |
In the configuration editor hierarchy, select Protocols>Bgp. |
From the top of the configuration hierarchy, enter edit protocols bgp |
|
Create the BGP group internal-peers, and add the internal neighbor addresses to the group. You must configure a full IBGP mesh, which requires that each peer be configured with every other internal peer as a BGP neighbor. |
|
|
|
Set the group type to internal. |
|
From the [edit protocols bgp group internal-peers] hierarchy level: set type internal |
|
Configure a routing policy to advertise BGP routes. |
See Injecting OSPF Routes into the BGP Routing Table (Optional). |
|