Thanks HC,
Two things. I was told this was not a topic for this list. Sorry about that.
Since I've already posted, I think I should post what the problem was.
Problem=I'm stupid. I wasn't looking in the right place for what I was advertising.
I ran:
router#sh ip bgp nei 10.99.200.75 adv
BGP table version is 43, local router ID is 10.1.80.44
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Originating default network 0.0.0.0
Network Next Hop Metric LocPrf Weight Path
*> 1.2.3.0/24 1.2.3.3 0 32768 i
router#
I was looking for the network, but not the line that stated:
Originating default network 0.0.0.0
So it was advertising and I've verified it on the remote peers (which I should have done first!).
Still doesn't answer why CISCO says you apply default orig to the peer, not the peer group (which we've proven is backwards). It shouldn't be this way since you may want to use the peer group as a template for multiple customers, but they may not all want 0/0 sent to them.
ALSO I didn't need to have 0/0 in my local routing table nor did I need to add the BGP command "Synchronization."
According to CISCO (which is actually accurate), it will originate default UNCONDITIONALLY, which it does.
I'm still concerned about applying the command to the peer vs. the peer group issue.
Sorry about having posted this to Nanog, I'll filter my future questions more carefully.
Thanks for everyone who answered!
Well, the idea of peer-group is to.. as what the name sugests 'group' the peers into a single and simple configuration.. Default route origination to a peer although may be specific to a neighbor like in your situation, is still a configuration for peering neighbor; hence making it possible to be grouped into peer-group commands.
But.. whether or not default-originate goes in seperate peer config or peer-group config I guess is debatable. In application for my network, I find default-originate feature under peer-group useful; as I originate default route to some aggregation switches in route-reflector client peer group.
Still doesn't answer why CISCO says you apply default orig to the peer, not
the peer group (which we've proven is backwards). It shouldn't be this way
since you may want to use the peer group as a template for multiple customers,
but they may not all want 0/0 sent to them. ALSO I didn't need to have 0/0 in
my local routing table nor did I need to add the BGP command
"Synchronization."
My understanding of the peer group feature is that it uses a single outbound
policy, routes are checked to the peer group and all group members are then sent
the update. This is very efficient and means you cannot have any exceptions to
the per peer outbound route policy. If you have some wanting 0/0 and some not
then you need to create a new peer group.
You wouldnt need it in the routing table, thats why you used the
default-originate command.
And synchronization would be used to check whether to install the route if its
in the igp or not, as again we're not using learned routes I guess it doesnt
care about sync. (I'm also not sure how sync interacts with confed members, I
assume it should for sync purposes treat them like regular ebgp peers and hence
honor sync but i dont know!)
Btw, check cisco-nsp@puck.nether.net if you're getting flamed for your OT
posting
