The peer connected-check-ignore command configures a device not to check the hop count when establishing a one-hop EBGP peer relationship using loopback interface addresses.
The undo peer connected-check-ignore command cancels the configuration.
By default, a device checks the hop count when establishing a one-hop EBGP peer relationship using loopback interface addresses.
peer{ group-name | ipv4-address | ipv6-address } connected-check-ignore
undo peer{ group-name | ipv4-address | ipv6-address } connected-check-ignore
Parameter | Description | Value |
---|---|---|
group-name | Specifies the name of a peer group. | The value is a string of 1 to 47 case-sensitive characters, spaces not supported. |
ipv4-address | Specifies the IPv4 address of a peer. | - |
ipv6-address | Specifies the IPv6 address of a peer. | - |
ipv4-address is valid only in the BGP view and BGP-VPN instance IPv4 address family view.
ipv6-address is valid only in the BGP view and BGP-VPN instance IPv6 address family view.
BGP view, BGP-VPN instance IPv4 address family view, or BGP-VPN instance IPv6 address family view
Usage Scenario
To allow one-hop EBGP peer relationships to be established using loopback interface addresses, run the peer connected-check-ignore command or the peer ebgp-max-hop command (in which hop-count is greater than or equal to 2).
Prerequisites
Peer relationships have been established using the peer as-number command.
Precautions
If the peer connected-check-ignore command is used on one end of an EBGP connection, it must also be used on the other end.