>First try without "tcp md5sig" and enable it only when it is 
>working.
>But I guess your problem is that the other side is expecting the
>connection to come from a different IP than the one selected by 
>the route
>lookup. In that case set "local-address 172.16.101.170" in the 
>iBGP group.
>
>Setting "local-address" is a good habit and necessary if you use 
>loopback
>interfaces or have non directly attached peers.
>-- 
>:wq Claudio

Per your kind comments, I have re-configured IBGP group as below.  
This time it seems that despite "local-address" being configured, 
it seems one of the peers is picking up its bge0 address 
(172.16.101.178)

group "iBGP_Neighbors" {
    remote-as $MY_ASN
    announce all
    neighbor 172.16.101.169
    local-address $MY_ROUTER_ID
}

group "iBGP_Neighbors" {
    remote-as $MY_ASN
    announce all
    neighbor 172.16.101.170
    local-address $MY_ROUTER_ID
}


# bgpd -dv
startup
MY_ASN = "65015"
MY_IPV4NET = "172.16.101.0/21"
MY_ROUTER_ID = "172.16.101.169"
route decision engine ready
session engine ready
listening on 0.0.0.0
listening on ::
SE reconfigured
neighbor 172.16.101.170: state change None -> Idle, reason: None
neighbor 172.16.101.170: state change Idle -> Connect, reason: Start
neighbor 172.16.101.170: state change Connect -> OpenSent, reason: 
Connection opened
neighbor 172.16.101.170: state change OpenSent -> Active, reason: 
Connection closed
RDE reconfigured
neighbor 172.16.101.170: state change Active -> Idle, reason: Stop
session engine exiting
Lost child: session engine exited
route decision engine exiting
kernel routing table decoupled
Terminating

# bgpd -dv
startup
MY_ASN = "65015"
MY_IPV4NET = "172.16.101.0/21"
MY_ROUTER_ID = "172.16.101.170"
route decision engine ready
RDE reconfigured
session engine ready
listening on 0.0.0.0
listening on ::
SE reconfigured
neighbor 172.16.101.169: state change None -> Idle, reason: None
neighbor 172.16.101.169: state change Idle -> Connect, reason: Start
neighbor 172.16.101.169: socket error: Connection refused
neighbor 172.16.101.169: state change Connect -> Active, reason: 
Connection open failed
connection from non-peer 172.16.101.178 refused
neighbor 172.16.101.169: socket error: Connection refused
neighbor 172.16.101.169: state change Active -> Idle, reason: Stop
session engine exiting
Lost child: session engine exited
route decision engine exiting
kernel routing table decoupled
Terminating

Reply via email to