Small ISP peering with upstream (ATT) and a customer to act as redundant link for that customer. I am getting routes from customer and I am advertising them to AT&T. AT&T tech says their side shows a problem with the route map but can provide no other details. They are set to accept the subnet as well as my other subnets and receive my other subnets just fine. I've been over it and over it, hopefully it's something obvious...
The 65.x.x.0 network is the one in question. The other subnets are on my network. I have routes for all of mine, but no "ip route" statements for the 65.x.x.0 as it is acquired by BGP.
!
router bgp xxxx1
no synchronization
bgp log-neighbor-changes
network 65.x.x.0 mask 255.255.255.0
network 67.x.x.0 mask 255.255.255.0
network 68.1x.x.0 mask 255.255.255.0
network 68.2x.x.0 mask 255.255.255.0
network 68.3x.x.0 mask 255.255.255.0
network 70.x.x.0 mask 255.255.254.0
network 72.x.x.0 mask 255.255.254.0
neighbor 67.x.x.8 remote-as xxxx3
neighbor 67.x.x.8 version 4
neighbor 67.x.x.8 prefix-list Cust in
neighbor 68.x.x.9 remote-as xxxx5
neighbor 68.x.x.9 version 4
neighbor 68.x.x.9 route-map bellout out
no auto-summary
!
ip as-path access-list 1 permit ^$
!
!
ip prefix-list Cust seq 5 permit 65.x.x.0/24
!
access-list 1 permit 67.x.x.0 0.0.0.255
access-list 1 permit 68.1x.x.0 0.0.0.255
access-list 1 permit 68.2x.x.0 0.0.0.255
access-list 1 permit 68.3x.x.0 0.0.0.255
access-list 1 permit 65.x.x.0 0.0.0.255
access-list 1 permit 70.x.x.0 0.0.1.255
access-list 1 permit 72.x.x.0 0.0.1.255
!
route-map bellout permit 10
match ip address 1
!
route-map bellout permit 20
match as-path 1
