[Xorp-users] Route Redist between RIP and OSPF - working?
Ray Soucy
rps at maine.edu
Mon Mar 26 10:35:51 PDT 2012
You might try looking at: http://soucy.org/xorp/xorp-1.6/CONFIG
I've always put policy statements in a single policy block; I've also
always used numbers for terms, and explicit "accept" or "reject". It has
worked fine in both pre- and post-CT configurations.
On Thu, Mar 22, 2012 at 10:52 AM, <swdickey at rockwellcollins.com> wrote:
> Hi Xorp Users,
>
> I am trying to get some simple route redistribution going between OSPF and
> RIP.
>
> Setup:
>
> OSPF
> RIP
> Xorp1 [30.1] - - - - - - [30.2] Xorp2 [40.1] - - - - - - [40.2] Xorp3
>
>
> What I am seeing is that on Xorp2 the RIP will send out Response messages
> with its routes' metric set to 16 (infinite) when OSPF is running on Xorp2
> (the bridge node). After playing with the config file on Xorp2 it seems
> OSPF just has to be a configured protocol on the router, it doesnt even
> have to be enabled on an interface. All the routes that Xorp2 will send
> out will be metric 16, even the connected routes. The OSPF seems to be
> fine, just a RIP problem happening.
>
> Has anyone else run with a similar setup? I don't see much information
> out there about policytags - is that a possible solution? Has anyone any
> config files that they could send me that have successfully worked for
> route redist between OSPF and RIP?
>
> I'm not sure, but this could be related to issue others have raised:
> *
> http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2008-September/002774.html
> *<http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2008-September/002774.html>
> *
> http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2008-September/002773.html
> *<http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2008-September/002773.html>
>
> Thanks guys,
>
> Steve Dickey
> swdickey at rockwellcollins.com
>
>
>
> Xorp2 config file:
>
> /* $XORP$ */
> interfaces {
> interface "eth4" {
> disable: false
> default-system-config
> }
> interface "eth5" {
> disable: false
> default-system-config
> }
> }
> fea {
> unicast-forwarding4 {
> disable: false
> }
> }
> protocols {
> ospf4 {
> router-id: 192.168.30.2
> export: "connected,rip"
> area 0.0.0.0 {
> interface "eth4" {
> vif "eth4" {
> address 192.168.30.2 {
> hello-interval: 10
> router-dead-interval: 40
> interface-cost: 100
> disable: false
> }
> }
> }
> }
> }
> rip {
> export: "export-connected,ospf"
> interface "eth5" {
> vif "eth5" {
> address 192.168.40.1 {
> metric: 1
> horizon:
> "split-horizon-poison-reverse"
> disable: false
> passive: false
> accept-non-rip-requests: true
> accept-default-route: false
> route-timeout: 180
> deletion-delay: 120
> triggered-delay: 3
> triggered-jitter: 66
> update-interval: 30
> update-jitter: 16
> request-interval: 30
> interpacket-delay: 50
> }
> }
> }
> }
> }
> policy {
> policy-statement export-connected {
> term 100 {
> from {
> protocol: "connected"
> }
> }
> }
> }
> policy {
> policy-statement connected {
> term export {
> from {
> protocol: "connected"
> }
> }
> }
> }
> policy {
> policy-statement rip {
> term export {
> from {
> protocol: "rip"
> }
> }
> }
> }
> policy {
> policy-statement ospf {
> term export {
> from {
> protocol: "ospf4"
> }
> }
> }
> }
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
--
Ray Soucy
Epic Communications Specialist
Phone: +1 (207) 561-3526
Networkmaine, a Unit of the University of Maine System
http://www.networkmaine.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120326/dd59baab/attachment-0001.html
More information about the Xorp-users
mailing list