Juniper Olive Dynamic routing RIP configuration case

Source: Internet
Author: User

The diagram above is a configuration topology diagram

R1,R2,R3,R4 all RIPv2 get the route, the following is the configuration document.

System {root-authentication {Encrypted-password "$1$pc0igedw$xh19u99vsa6azotdk9bfz."; # Secret-data} logi   
n {User Mengmeng {UID 2001;   
Class Super-user; Authentication {Encrypted-password "$1$keim0kf/$ezlHwRupnb 7HFdUZVdIvE."; # # Secret-data}}} Services   
{telnet;   
   Web-management {http {port 80;   
}}} logical-routers {R1 {interfaces {em1 {unit {Vlan-id 12;   
 Family inet {address 12.1.1.1/24;   
} \ {Vlan-id 13;   
   Family inet {address 13.1.1.1/24;   
}}} protocols {rip {Group juniper {export Juniper1;   
  Neighbor em1.13;//is equivalent to enabling RIP neighbor em1.12 on the interface; }} policy-options {policy-statement juniper1 {Term 1 {from interface [em1.12 em1.13];//juniper Default   
If you learn a rip route from a neighbor, but do not forward it, use the policy-option (routing strategy) here to implement the forwarding of RIP routes, which means that the direct connection port where the interface em1.12,em1.13 is routed to rip.   
   then accept;  }   
  } 
 }} R2 {interfaces {em2 {Vlan-id 12;   
 Family inet {address 12.1.1.2/24;   
{Vlan-id 24;   
   Family inet {address 24.1.1.2/24;    
}}} protocols {rip {Group juniper {export Juniper2;//define forwarding policy, juniper default does not announce direct-attached network, need to define forwarding policy  Neighbor em2.12;   
  Equivalent to enabling RIP neighbor em2.24 on the interface; }} policy-options {policy-statement Juniper2 {Term 1 {from interface [em2.12 em2.24];//will be on these interfaces   
   The routes received are released, including the network number of these interfaces then accept;   
}}} R3 {interfaces {em3 {Vlan-id 13;   
 Family inet {address 13.1.1.3/24;   
{Vlan-id 34;   
   Family inet {address 34.1.1.3/24;   
}}} protocols {rip {Group juniper {export Juniper3;   
Neighbor em3.13;   
  Neighbor em3.34;   }} policy-options {policy-statement Juniper3 {Term 1 {from interface [em3.13 em3.34];
then accept;   
}}} R4 {interfaces {em4 {Vlan-id 24;   
 Family inet {address 24.1.1.4/24;   
{Vlan-id 34;   
   Family inet {address 34.1.1.4/24;   
}}} protocols {rip {Group juniper {export juniper4;   
Neighbor em4.24;   
  Neighbor em4.34; }}} policy-options {policy-statement Juni   
Per4 {Term 1 {from interface [em4.24 em4.34];   
    then accept;   
  }}}} interfaces {em0 {unit 0 {family inet {address 192.168.1.254/24;   
}}} em1 {vlan-tagging;   
} em2 {vlan-tagging;   
} em3 {vlan-tagging;   
 } em4 {vlan-tagging; } mengmeng# run show rip neighbor Logical-router all logical-router:r1 Source destination S End Receive in Neighbor State address mode Met---------------------------------------------em1.12 up 12.1.1.1 224.0.0.9 mcast both 1 em1.13 up 13.1.1.1 224.0.  0.9 Mcast both 1-----logical-router:r2 em2.12 up 12.1.1.2 224.0.0.9 mcast both 1 em2.24 up 24.1.1.2 224.0.0.9 mcast both 1-----logical-router:r3 em3.13 up 13.1.1.3 224.0.0.9 mcast both 1 em3.34 up 34.1.1.3 224.0.0.9 mcast both 1-----logical-router:r4 em4.24 up 24.1.1.4 224.0.0.9 mcast both 1 em4.34 up 34.1.1.4 2  24.0.0.9 mcast both 1-----logical-router:default RIPv2 instance is not running [edit] mengmeng# run Show Route logical-router all LOGICAL-ROUTER:R1 inet.0:7 destinations, 7 routes (7 active, 0 hold Down, 0 hidden) + = Active Route,-= Last Active, * = Both 12.1.1.0/24 *[direct/0] 07:22:59 > via EM1 12.1.1.1/32 *[local/0] 07:22:59 Local via em1.12 13.1.1.0/24 *[direct/0] 07:22:59 > via em1.13 13.1. 1.1/32 *[local/0] 07:22:em1.13 24.1.1.0/24 *[rip/100] 00:47:09, metric 2, Tag 0 > to 12.1.1.2 via em1.12 34.1.1.0/24 * [rip/100] 00:28:07, metric 2, Tag 0 > to 13.1.1.3 via em1.13 224.0.0.9/32 *[rip/100] 00:24:48, metric 1 Multir   
ECV-----LOGICAL-ROUTER:R2 inet.0:7 Destinations, 7 routes (7 active, 0 holddown, 0 hidden)  + = Active Route,-= last active, * = Both 12.1.1.0/24 *[direct/0] 07:22:59 > via em2.12 12.1.1.2/32 *[LOCAL/0] 07:22:59 Local via em2.12 13.1.1.0/24 *[rip/100] 00:47:10, metric 2, Tag 0 > to 12.1.1.1 via em2.1 2 24.1.1.0/24 *[direct/0] 07:22:59 > via em2.24 24.1.1.2/32 *[local/0] 07:22:59 local via em2.24 34.1.1.   
0/24 *[rip/100] 00:24:43, metric 2, Tag 0 > to 24.1.1.4 via em2.24 224.0.0.9/32 *[rip/100] 00:24:48, metric 1 MULTIRECV-----LOGICAL-ROUTER:R3 inet.0:7 Destinations, 7 routes (7 active, 0 holddown, 0 Hidd EN) + = Active Route, -= Last Active, * = Both 12.1.1.0/24 *[rip/100] 00:28:11, metric 2, Tag 0 > to 13.1.1.1 via em3.13 1 3.1.1.0/24 *[direct/0] 07:20:09 > via em3.13 13.1.1.3/32 *[local/0] 07:20:09 Local via em3.13 24.1.1.0/24 *   
[rip/100] 00:24:43, metric 2, Tag 0 > to 34.1.1.4 via em3.34 34.1.1.0/24 *[direct/0] 07:20:09 > via em3.34    
       
34.1.1.3/32 *[local/0] 07:20:09 Local via em3.34 224.0.0.9/32 *[rip/100] 00:24:48, metric 1 multirecv----- LOGICAL-ROUTER:R4 inet.0:7 Destinations, 7 routes (7 active, 0 holddown, 0 hidden) + = Active Route,-= Last Active, * = Both 12.1.1.0/24 *[rip/100] 00:24:46, metric 2, Tag 0 > to 24.1.1.2 via em4.2   
4 13.1.1.0/24 *[rip/100] 00:24:48, metric 2, Tag 0 > to 34.1.1.3 via em4.34 24.1.1.0/24 *[direct/0] 07:20:09 > via em4.24 24.1.1.4/32 *[local/0] 07:20:09 Local via em4.24 34.1.1.0/24 *[direct/0] 07:20:09 > via E m4.34 34.1.1.4/32 *[lOCAL/0] 07:20:09 Local via em4.34 224.0.0.9/32 *[rip/100] 00:24:48, metric 1 multirecv-----Logica L-router:default inet.0:2 Destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route,-= Last   
Active, * = Both 192.168.1.0/24 *[direct/0] 08:16:17 > via em0.0 192.168.1.254/32 *[local/0] 08:31:57 Local via em0.0 __juniper_private2__.inet.0:1 destinations, 1 routes (0 active, 0 holddown, 1 hidden)

This article is from the "Rista" blog, please be sure to keep this source http://rista.blog.51cto.com/2526140/851440

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.