Juniper JNCIA – Juniper RIP Route Configuration

  • View
    247

  • Download
    11

Embed Size (px)

Text of Juniper JNCIA – Juniper RIP Route Configuration

CISCO CCNA DHCP SERVER

Juniper JNCIJuniper OSPF Route Configuration

Juniper JNCIA

ASM Educational Center Inc. (ASM)WhereTraining,Technology&ServiceConvergeCheck out our Juniper Training Videos: www.asmed.com/j1

Juniper RIP Route Configuration

Juniper RIP Route Configuration

Understanding Basic RIP Routing

RIP is an interior gateway protocol (IGP) that routes packets within a single autonomous system (AS). By default, RIP does not advertise the subnets that are directly connected through the device's interfaces. For traffic to pass through a RIP network, you must create a routing policy to export these routes. Advertising only the direct routes propagates the routes to the immediately adjacent RIP-enabled router only. To propagate all routes through the entire RIP network, you must configure the routing policy to export the routes learned through RIP.

Juniper RIP Route Configuration

Juniper RIP Route ConfigurationGoal is that R2 be able to ping R4 Loopback address =4.4.4.4 via RIPStep 1) I go to R2 and enable RIP routing Hint: for the neighbors you cannot use the neighbor Ip address ; you need to use interface in this case of R2 neighbor is R4 with interface em2.0root@R2# set protocols rip group RIPGROUP neighbor em2.0

Juniper RIP Route ConfigurationNow When I go to R4#show route I do not see any neighbor yetroot@R4> show routeinet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both4.4.4.4/32 *[Direct/0] 00:40:13 > via lo0.020.20.20.0/24 *[Direct/0] 00:42:30 > via em2.020.20.20.4/32 *[Local/0] 00:42:30 Local via em2.0

Juniper RIP Route ConfigurationStep 2) Now I will enable RIP on R4root@R4# set protocols rip group RIPGROUP4 neighbor em2Hint: The Group name is local significance does not need to be same

Juniper RIP Route ConfigurationStep 3) You configure a basic RIP network, create a RIP group called rip-group, and add the directly connected interfaces to the RIP group. Then you configure a routing policy to advertise direct routes using policy statement advertise-routes-through-rip.By default, Junos OS does not advertise RIP routes, not even routes that are learned through RIP. To advertise RIP routes, you must configure and apply an export routing policy that advertises RIP-learned and direct routes.Now I need to create a Policy with Statements for Example RIPPOLICY

root@R4# set policy-options policy-statement RIPPOLICY term 1 from protocol rip set policy-options policy-statement RIPPOLICY term 1 from protocol direct set policy-options policy-statement RIPPOLICY term 1 then acceptAs we see in above in order to create a Policy I need a term 1 , from , Then I need action.

Juniper RIP Route ConfigurationHere is show configuration so far on R4#policy-options { policy-statement RIPPOLICY { term 1 { from protocol [ rip direct ]; then accept; } }}Now we need to export (Apply) this policy to Rip Group Called RIPGROUP4root@R4# set protocols rip group RIPGROUP4 export RIPPOLICY

Juniper RIP Route ConfigurationHint: I need to do export ; since we are trying to bring ( the directed Connected network) to the RIP , now let say on the left we had OPSF network between R1, R2,R3 and we need all those Loopback of R1,R2,R3 being seen inside the RIP Network or routing table of R4 ,then I need to have this on my policy option ( instead of RIP I will have OSPF) . We will do this on next Labpolicy-options { policy-statement OSPFPOLICY { term 1 { from protocol [ OSPF ]; then accept; } }}So on R4 we have this so far :R4> Show configuration

Juniper RIP Route Configurationprotocols { rip { group RIPGROUP4 { export RIPPOLICY; neighbor em2.0; } }}policy-options { policy-statement RIPPOLICY { term 1 { from protocol [ rip direct ]; then accept; } }}

Juniper RIP Route ConfigurationStep 4) Now If I go to R2 and do show route I will see the loopback address of R4=4.4.4.4root@R2> show routeinet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both2.2.2.2/32 *[Direct/0] 01:14:43 > via lo0.04.4.4.4/32 *[RIP/100] 00:14:27, metric 2, tag 0 > to 20.20.20.4 via em2.010.10.10.0/24 *[Direct/0] 01:28:38 > via em1.010.10.10.2/32 *[Local/0] 01:28:38 Local via em1.020.20.20.0/24 *[Direct/0] 01:28:37 > via em2.020.20.20.2/32 *[Local/0] 01:28:37 Local via em2.030.30.30.0/24 *[Direct/0] 01:28:37 > via em3.030.30.30.2/32 *[Local/0] 01:28:37 Local via em3.0224.0.0.9/32 *[RIP/100] 00:52:33, metric 1 MultiRecv

Juniper RIP Route ConfigurationNow why I see it? Since On the R4 I did export the Policy; but If I go to R4 and do show route I do not see the loopback of R2=2.2.2.2 , since On the R2 I did not export the Policy . root@R4> show routeinet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both4.4.4.4/32 *[Direct/0] 01:33:15 > via lo0.020.20.20.0/24 *[Direct/0] 01:35:32 > via em2.020.20.20.4/32 *[Local/0] 01:35:32 Local via em2.0224.0.0.9/32 *[RIP/100] 00:20:16, metric 1 MultiRecvAnd here what I have so far on R2>root@R2> show configuration

Juniper RIP Route Configurationprotocols { rip { group RIPGROUP { neighbor em2.0; } }} Now On R2 we need to do create a Policy and then Export under the Protocol RIP ; so lets do the Policy-Option firstroot@R2#set policy-options policy-statement RIPPOLICY2 term 1 from protocol ripset policy-options policy-statement RIPPOLICY2 term 1 from protocol directset policy-options policy-statement RIPPOLICY2 term 1 then acceptNow I will Export under the Protocols Rip

Juniper RIP Route ConfigurationHere what we have on R2 up to now :root@R2> show configurationprotocols { rip { group RIPGROUP { neighbor em2.0; } }}policy-options { policy-statement RIPPOLICY2 { term 1 { from protocol [ rip direct ]; then accept; } }}root@R2# set protocols rip group RIPGROUP export RIPPOLICY2

Juniper RIP Route Configurationso here what we have at R2 so Far:root@R2> show configurationprotocols { rip { group RIPGROUP { export RIPPOLICY2; neighbor em2.0; } }}policy-options { policy-statement RIPPOLICY2 { term 1 { from protocol [ rip direct ]; then accept; } }}

Juniper RIP Route ConfigurationStep 5) Now If I go to R4 and look at routing table I should be able to see Loopback of R2=2.2.2.2 and also be able to ping 2.2.2.2 from R4>root@R4> show route

Juniper RIP Route Configurationinet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both2.2.2.2/32 *[RIP/100] 00:03:04, metric 2, tag 0 > to 20.20.20.2 via em2.04.4.4.4/32 *[Direct/0] 01:54:11 > via lo0.010.10.10.0/24 *[RIP/100] 00:03:04, metric 2, tag 0 > to 20.20.20.2 via em2.020.20.20.0/24 *[Direct/0] 01:56:28 > via em2.020.20.20.4/32 *[Local/0] 01:56:28 Local via em2.030.30.30.0/24 *[RIP/100] 00:03:04, metric 2, tag 0 > to 20.20.20.2 via em2.0224.0.0.9/32 *[RIP/100] 00:41:12, metric 1 MultiRecv

Juniper RIP Route Configurationroot@R4> ping 2.2.2.2

PING 2.2.2.2 (2.2.2.2): 56 data bytes64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=0.510 ms64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=1.173 ms64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=1.086 ms^C

Juniper RIP Route ConfigurationSo Summary in order to make RIP works ; not only you need to have neighbor statements on router ; you need to Create a Policy that has both RIP and Direct inside it and make sure you export it under the Set Protocols RipNow If I go to R2 and create another loopback =2.2.2.3/32 then it will shown on R4 routing tablesHere what I have on R2root@R2# show interfaceslo0 { unit 0 { family inet { address 2.2.2.2/32; } }}

Juniper RIP Route ConfigurationNow I will add another loopback as follow :root@R2# set interfaces lo0 unit 0 family inet address 2.2.2.3/32[edit]root@R2# commithere what I have on R2#show interfasceroot@R2# show interfaceslo0 { unit 0 { family inet { address 2.2.2.2/32; address 2.2.2.3/32; } }}

Juniper RIP Route ConfigurationNow When I go to R4> show route I will see the new loopback 2.2.2.3 and I should be able to ping it;root@R4> show routeinet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both

Juniper RIP Route Configuration2.2.2.2/32 *[RIP/100] 00:13:27, metric 2, tag 0 > to 20.20.20.2 via em2.02.2.2.3/32 *[RIP/100] 00:01:54, metric 2, tag 0 > to 20.20.20.2 via em2.04.4.4.4/32 *[Direct/0] 02:04:34 > via lo0.010.10.10.0/24 *[RIP/100] 00:13:27, metric 2, tag 0 > to 20.20.20.2 via em2.020.20.20.0/24 *[Direct/0] 02:06:51 > via em2.020.20.20.4/32 *[Local/0] 0