Hi Bob,
Thanks a lot.. Its working with "disable connected check".
Now what bothers me a lot is, how if this kind of issue we get in the Lab
and how do we know all possible work around?
PE1#show running-config | b r b
router bgp 65001
bgp router-id 10.1.1.1
no bgp fast-external-fallover
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 10.1.1.100 remote-as 100
neighbor 10.1.1.100 ttl-security hops 2
neighbor 10.1.1.100 disable-connected-check
neighbor 10.1.1.100 update-source Loopback0
neighbor 10.1.1.254 remote-as 65001
neighbor 10.1.1.254 update-source Loopback0
neighbor 140.100.1.2 remote-as 1540
neighbor 140.100.1.2 ttl-security hops 1
neighbor 140.100.1.2 password ieMENTOR
!
address-family ipv4
neighbor 10.1.1.100 activate
neighbor 10.1.1.254 activate
neighbor 140.100.1.2 activate
neighbor 140.100.1.2 filter-list 10 out
no auto-summary
no synchronization
network 11.11.11.0 mask 255.255.255.0
PE1#show ip bgp | include 10.1.1.100
*> 0.0.0.0 10.1.1.100 0 100 200 i
*> 101.101.101.0/24 10.1.1.100 0 0 100 i
r> 172.16.111.0/24 10.1.1.100 0 0 100 i
*> 172.16.113.0/24 10.1.1.100 0 100 200 i
PE1#
Thanks,
John
Blogs and organic groups at http://www.ccie.net
Received on Wed Sep 08 2010 - 20:39:35 ART
This archive was generated by hypermail 2.2.0 : Fri Oct 01 2010 - 05:58:05 ART