H3C Technologies H3C SecPath F1000-E - Manual (Page 517)

492
AS-path : 100
Origin : igp
Attribute value : MED 0, localpref 100, pref-val 0, pre 255
State : valid, internal, best,
Not advertised to any peers yet
The output information shows that:
{
SecPath F can send route information to SecPath B and SecPath C through the confederation by
establishing only an EBGP connection with SecPath A.
{
SecPath B and SecPath D are in the same confederation, but belong to different sub ASs. They
obtain external route information from SecPath A and generate the same BGP route entries; it
seems like that they reside in the same AS although they have no direct connection in between.
BGP path selection configuration at the CLI
Network requirements
In Figure 294 , all firewalls run BGP. Between SecPath A and SecPath B, and between SecPath A and
SecPath C are EBGP connections. Between SecPath B and SecPath D, and between SecPath D and
SecPath C are IBGP connections. OSPF is the IGP protocol in AS 200.
Configure routing policies to make SecPath D give priority to the route 1.0.0.0/8 learned from SecPath
C.
Figure 294 Network diagram
Device Interface IP address Device Interface IP address
SecPath A GE0/1 1.0.0.0/8 SecPath D GE0/1 195.1.1.1/24
GE0/2 192.1.1.1/24 GE0/2 194.1.1.1/24
GE0/3 193.1.1.1/24 SecPath C GE0/1 195.1.1.2/24
SecPath B GE0/1 192.1.1.2/24 GE0/2 193.1.1.2/24
GE0/2 194.1.1.2/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown)
2. Configure OSPF on SecPath B, C, and D:
# Configure SecPath B.
<SecPathB> system-view
[SecPathB] ospf
[SecPathB-ospf] area 0