When we enable peering between the providers edge and our core switch, the peering establishes, the 3750G goes ito a black hole, hold timer expires and the 3750 is reachable.
All timers are default and should be negotiated be default. We have verified L1 and L2 is operational. I am seeing dropped unknown protocols on the Edge router (1500 or so).
Our setup is pretty simple
ProviderCLOUD ------------- Provider Edge Router (2801|12.4(19a)ADVIPSERV) ------------- 3750G (IPSRV 12.2.55SE4/K9)
3750G BGP config
router bgp 65AAA
no synchronization
bgp log-neighbor-changes
network 10.XXX.0.0 mask 255.255.0.0
redistribute connected
neighbor 10.XXX.10.10 remote-as 64BBB
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.xx.10.10 - default route safety valve while we are in implementation
ip route 10.0.0.0 255.0.0.0 10.xx.10.10 - same as above
ip route 10.xx.250.0 255.255.255.0 10.xx.0.10 - ISO network unrelated
Edge BGP Config
router bgp 64BBB
no synchronization
bgp log-neighbor-changes
network 10.40.0.0 mask 255.255.0.0
network 172.XXX.113.YYY mask 255.255.255.252
network 172.XXX.113.YYY mask 255.255.255.255
redistribute connected
neighbor 10.xx.10.1 remote-as 65AAA
neighbor 152.XXX.63.Y remote-as 65ZZZ
neighbor 152.XXX.63.Y route-map blockzero in - provider upstream router
no auto-summary
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 198.XXX.255.YYY 250 - backup route from provider
ip route 10.XXX.0.0 255.255.0.0 10.XXX.10.1 - your for all site sbnets to our Core
!
ip bgp-community new-format
ip community-list 1 permit 65000:1
!
route-map blockzero deny 10
match community 1
!
route-map blockzero permit 20
!
the configurations look pretty harmless (new bgp commands should effect much at all). Is it possible the BGP keep alives are not in the correct format between the 2801 and the 3750G??? And how would this have changed?
Thanks in advance for any assistance
Chris
