cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
262
Views
0
Helpful
2
Replies
Highlighted
Beginner

BGP intra confederation AS error

R1 show nei state is Idel for R5. what could be the issues?

R1

router bgp 65505
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65507
neighbor 10.0.9.1 remote-as 900
neighbor 192.168.2.1 remote-as 65505
neighbor 192.168.2.1 update-source Loopback0
neighbor 192.168.2.1 next-hop-self
neighbor 192.168.5.1 remote-as 65507
neighbor 192.168.5.1 update-source Loopback0

 

R5

router bgp 65507
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65505
neighbor 10.0.11.1 remote-as 1100
neighbor 192.168.1.1 remote-as 65505
neighbor 192.168.1.1 update-source Loopback0
neighbor 192.168.7.1 remote-as 65507
neighbor 192.168.7.1 update-source Loopback0
neighbor 192.168.7.1 next-hop-self

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

 

 

hello @NayAungLin7876 ,

 

without seeing any useful output from command "show bgp <AFI> <SAFI> neighbors x.x.x.x" one thing that came into my mind is that you may probably need to disable connected-check since you're using the loopback address to establish the peering.

Otherwise by looking to the output of command i've post above you may find additional info to what could be the reason of idle session among peers.

 

hope this may help.

Regards.

 

 

 

 


@NayAungLin7876 wrote:

R1 show nei state is Idel for R5. what could be the issues?

R1

router bgp 65505
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65507
neighbor 10.0.9.1 remote-as 900
neighbor 192.168.2.1 remote-as 65505
neighbor 192.168.2.1 update-source Loopback0
neighbor 192.168.2.1 next-hop-self
neighbor 192.168.5.1 remote-as 65507
neighbor 192.168.5.1 update-source Loopback0

 

R5

router bgp 65507
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65505
neighbor 10.0.11.1 remote-as 1100
neighbor 192.168.1.1 remote-as 65505
neighbor 192.168.1.1 update-source Loopback0
neighbor 192.168.7.1 remote-as 65507
neighbor 192.168.7.1 update-source Loopback0
neighbor 192.168.7.1 next-hop-self

 


 

View solution in original post

2 REPLIES 2
Highlighted
Cisco Employee

 

 

hello @NayAungLin7876 ,

 

without seeing any useful output from command "show bgp <AFI> <SAFI> neighbors x.x.x.x" one thing that came into my mind is that you may probably need to disable connected-check since you're using the loopback address to establish the peering.

Otherwise by looking to the output of command i've post above you may find additional info to what could be the reason of idle session among peers.

 

hope this may help.

Regards.

 

 

 

 


@NayAungLin7876 wrote:

R1 show nei state is Idel for R5. what could be the issues?

R1

router bgp 65505
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65507
neighbor 10.0.9.1 remote-as 900
neighbor 192.168.2.1 remote-as 65505
neighbor 192.168.2.1 update-source Loopback0
neighbor 192.168.2.1 next-hop-self
neighbor 192.168.5.1 remote-as 65507
neighbor 192.168.5.1 update-source Loopback0

 

R5

router bgp 65507
bgp log-neighbor-changes
bgp confederation identifier 700
bgp confederation peers 65505
neighbor 10.0.11.1 remote-as 1100
neighbor 192.168.1.1 remote-as 65505
neighbor 192.168.1.1 update-source Loopback0
neighbor 192.168.7.1 remote-as 65507
neighbor 192.168.7.1 update-source Loopback0
neighbor 192.168.7.1 next-hop-self

 


 

View solution in original post

Highlighted

Your answer is really help me. As you said, the problem is neighboring EBGP router by using loopback address. So, I use disable-connected-chek that solve this issues. Thank for your kindly suggestions.