neighbor collide-established
Use this command to include a neighbor already in an established state for conflict resolution when a TCP connection collision is detected. This command is not required for most network deployments, so users should only use this command when required.
Note: The associated functionality of including an “established” neighbor into TCP connection collision conflict resolution is automatically enabled when a neighbor is configured for BGP graceful-restart.
Use the no option with this command to turn this feature off.
Command Syntax
neighbor (A.B.C.D|X:X::X:X|WORD) collide-established
no neighbor (A.B.C.D|X:X::X:X|WORD) collide-established
For BGP unnumbered mode:
neighbor WORD collide-established
no neighbor WORD collide-established
Parameters
A.B.C.D
Address of the BGP neighbor in an IPv4 format
X:X::X:X
Address of the BGP neighbor in an IPv6 format
WORD
Name of a BGP peer group created with the
neighbor WORD peer-group command. When you specify this parameter, the command applies to all peers in the group.
Default
By default, neighbor collide is disabled
Command Mode
Router mode and BGP unnumbered mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#router bgp 10
(config-router)#neighbor 3.3.3.3 collide-established
For unnumbered peer below configuration is given in BGP unnumbered-mode.
(config)#router bgp 100
(config-router)#bgp unnumbered-mode
(config-router-unnum)#neighbor eth1 collide-established
Last modified date: 07-13-2023