From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Sat Aug 14 2004 - 21:22:23 GMT-3
I have not read the link but traffic coming from R3 means routes sent to R3.
This would explain the route-map applied out to R3.
Also as a side note, even if it is R2 who sends routes to R3, by default
traffic whose destination is R1 will have R1 as a next hop because they are
on the same network,
--Richard
-----Original Message-----
From: Sean C [mailto:Upp_and_Upp@hotmail.com]
Sent: sabado, 14 de agosto de 2004 22:45
To: ccielab@groupstudy.com
Subject: set ip next-hop peer-address
Can someone explain this statement from the CD concerning set ip next-hop
peer-address:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr
r
p_r/bgp_r/1rfbgp2.htm#wp1021368
I'm at the example:
In the following example, three routers are on the same LAN (with IP
addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3). Each is in a different
autonomous system. The set ip next-hop peer-address command specifies that
traffic from the router (10.1.1.3) in remote autonomous system 300 for the
router (10.1.1.1) in remote autonomous system 100 that matches the route map
is passed through the router bgp 200, rather than sent directly to the
router (10.1.1.1) in autonomous system 100 over their mutual connection to
the LAN.
router bgp 200
neighbor 10.1.1.3 remote-as 300
neighbor 10.1.1.3 route-map set-peer-address out
neighbor 10.1.1.1 remote-as 100
route-map set-peer-address permit 10
set ip next-hop peer-address
I think I have the theory exactly backwards as I thought it would be setting
traffic destined for 10.1.1.3 with a next-hop of the peer-address - not FROM
10.1.1.3. The above description mentions that it is from 10.1.1.3. I'm
lost on the route-map being applied to traffic coming IN from 10.1.1.3 yet
the route-map is an 'out' route-map.
I'm learning this in conjunction with NMC Lab13.7
Thanks in advance, Sean
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.737 / Virus Database: 491 - Release Date: 8/11/2004
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:43 GMT-3