Loopback Interfaces - HPE 5800 Series Configuration Manual

Configure IBGP:
2.
To prevent route flapping caused by port state changes, this example uses loopback
interfaces to establish IBGP connections.
Because loopback interfaces are virtual interfaces, use the peer connect-interface
command to specify the loopback interface as the source interface for establishing BGP
connections.
Enable OSPF in AS 65009 to make sure Switch B can communicate with Switch C through

loopback interfaces.

# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp] router-id 2.2.2.2
[SwitchB-bgp] peer 3.3.3.3 as-number 65009
[SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0
[SwitchB-bgp] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.1 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp] router-id 3.3.3.3
[SwitchC-bgp] peer 2.2.2.2 as-number 65009
[SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0
[SwitchC-bgp] quit
[SwitchC] ospf 1
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
[SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
[SwitchC] display bgp peer
BGP local router ID : 3.3.3.3
Local AS number : 65009
Total number of peers : 1
Peer
2.2.2.2
The output shows that Switch C has established an IBGP peer relationship with Switch B.
Configure EBGP:
3.
The EBGP peers, Switch A and Switch B (usually belong to different carriers), are located in
different ASs. Typically, their loopback interfaces are not reachable to each other, so directly
connected interfaces are used for establishing BGP sessions.
AS MsgRcvd MsgSent OutQ PrefRcv Up/Down
65009 2
218
Peers in established state : 1
2 0 0 00:00:13 Established
State