Juniper JNCIA – Juniper RIP and OSPF Route Configuration

Juniper JNCIA
ASM Educational Center Inc. (ASM)
Where Training,Technology& Service Converge
CheckoutourJuniperTrainingVideos:www.asmed.com/j1
Juniper RIP and OSPF Route Configuration

The Goal is when I configure OSPF on the left side ( between R1,R2,R3) ; R4
be able to ping 1.1.1.1 and 3.3.3.3 after I export from OSPF to RIP.
Up to now R2 has loopback address 2.2.2.2/32 and 2.2.2.3/32 that will be
seen on R4 Routing tables since I have done RIP on R2 and R4

Here what we have on R4:
root@R4> show configuration
em2 {
unit 0 {
family inet {
address 20.20.20.4/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 4.4.4.4/32;
}
}
}
}

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

Here what I have on R2#
interfaces {
em1 {
unit 0 {
family inet {
address 10.10.10.2/24;
}
}
}
em2 {
unit 0 {
family inet {
address 20.20.20.2/24;
}
}
}

em3 {
unit 0 {
family inet {
address 30.30.30.2/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 2.2.2.2/32;
address 2.2.2.3/32;
}
}
}
}

protocols {
rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}
policy-options {
policy-statement RIPPOLICY2 {
term 1 {
then accept;
}
}
}

Now remember from last lab R4 can ping loopback address 2.2.2.2 and 2.2.2.3
root@R4> show route
inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2.2.2.2/32 *[RIP/100] 00:01:48, metric 2, tag 0
> to 20.20.20.2 via em2.0
2.2.2.3/32 *[RIP/100] 00:01:48, metric 2, tag 0
> to 20.20.20.2 via em2.0
4.4.4.4/32 *[Direct/0] 00:02:59
> via lo0.0
10.10.10.0/24 *[RIP/100] 00:01:52, metric 2, tag 0
> to 20.20.20.2 via em2.0
20.20.20.0/24 *[Direct/0] 00:03:00
> via em2.0
20.20.20.4/32 *[Local/0] 00:03:00
Local via em2.0
30.30.30.0/24 *[RIP/100] 00:01:48, metric 2, tag 0
> to 20.20.20.2 via em2.0
224.0.0.9/32 *[RIP/100] 00:03:01, metric 1
MultiRecv

root@R4> ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes
64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=0.462 ms
^C
--- 2.2.2.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.462/0.693/1.029/0.243 ms

PING 2.2.2.3 (2.2.2.3): 56 data bytes
64 bytes from 2.2.2.3: icmp_seq=3 ttl=64 time=0.^C
•

Now I go to R1 and R3 and create all my interface and loopback address :
Here is R1 configuration:
root@R1# set interfaces em1 unit 0 family inet address 10.10.10.1/24
set interfaces lo0 unit 0 family inet address 1.1.1.1/32
Now I will do on R3:
root@R3#set interfaces em3 unit 0 family inet address 30.30.30.1/24
set interfaces lo0 unit 0 family inet address 3.3.3.3/32

Now I will go configure OPPF on R1#
root@R1#set protocols ospf area 0.0.0.0 interface em1.0
set protocols ospf area 0.0.0.0 interface lo0.0
Now I will go configure OPSF on R2#
root@R2# set protocols ospf area 0.0.0.0 interface em1.0
set protocols ospf area 0.0.0.0 interface em3.0

Now we see R2 is neighbor with R1
root@R2> show ospf neighbor
Address Interface State ID Pri Dead
10.10.10.1 em1.0 Full 1.1.1.1 128 35
Lets look at R1 , routing table : I can see the loopback of R2 , not Loopback
of R3 =3.3.3.3 since I need to finish my OSPF configuration on R3

root@R1> show route
1.1.1.1/32 *[Direct/0] 00:23:25
> via lo0.0
2.2.2.2/32 *[OSPF/10] 00:09:04, metric 1
> to 10.10.10.2 via em1.0
2.2.2.3/32 *[OSPF/10] 00:09:04, metric 1
> to 10.10.10.2 via em1.0
10.10.10.0/24 *[Direct/0] 00:31:53
> via em1.0
10.10.10.1/32 *[Local/0] 00:31:53
Local via em1.0
30.30.30.0/24 *[OSPF/10] 00:09:04, metric 2
> to 10.10.10.2 via em1.0
224.0.0.5/32 *[OSPF/10] 00:13:11, metric 1
MultiRecv

Now I will configure OSPF on R3#
root@R3# set protocols ospf area 0.0.0.0 interface em3.0
Now when I go to R3 and I should have two neighbors on R3
root@R2> show ospf neighbor
Address Interface State ID Pri Dead
10.10.10.1 em1.0 Full 1.1.1.1 128 34
30.30.30.1 em3.0 Full 3.3.3.3 128 39
Lets look at R1 routing table I should see the loopback of R2=2.2.2.2 , 2.2.2.3 and Loopback
of R3=3.3.3.3

root@R1> show route
1.1.1.1/32 *[Direct/0] 00:30:12
> via lo0.0
2.2.2.2/32 *[OSPF/10] 00:15:51, metric 1
> to 10.10.10.2 via em1.0
2.2.2.3/32 *[OSPF/10] 00:15:51, metric 1
> to 10.10.10.2 via em1.0
3.3.3.3/32 *[OSPF/10] 00:03:03, metric 2
> to 10.10.10.2 via em1.0
10.10.10.0/24 *[Direct/0] 00:38:40
> via em1.0
10.10.10.1/32 *[Local/0] 00:38:40
Local via em1.0
30.30.30.0/24 *[OSPF/10] 00:15:51, metric 2
> to 10.10.10.2 via em1.0
224.0.0.5/32 *[OSPF/10] 00:19:58, metric 1
MultiRecv

So up to now R1, R2, R3 are talking via OPSF and R2 and R4 are
talking via RIP ; now when I go to R4 routing table I do not see the
loopback of R1=1.1.1.1 and R3=3.3.3.3 inside R4
Lets go to R4#
root@R4> show route

2.2.2.2/32 *[RIP/100] 00:48:21, metric 2, tag 0
> to 20.20.20.2 via em2.0
2.2.2.3/32 *[RIP/100] 00:48:21, metric 2, tag 0
> to 20.20.20.2 via em2.0
4.4.4.4/32 *[Direct/0] 00:49:32
> via lo0.0
10.10.10.0/24 *[RIP/100] 00:48:25, metric 2, tag 0
> to 20.20.20.2 via em2.0
20.20.20.0/24 *[Direct/0] 00:49:33
> via em2.0
20.20.20.4/32 *[Local/0] 00:49:33
Local via em2.0
30.30.30.0/24 *[RIP/100] 00:48:21, metric 2, tag 0
> to 20.20.20.2 via em2.0
224.0.0.9/32 *[RIP/100] 00:49:34, metric 1
MultiRecv

In order R4 be able to see loopback 1.1.1.1 and 3.3.3.3 I need to go to Middle router R2 and export the
OSPF into RIP ( the same way we did on RIP and connected) let’s look at R2 , what we have so far:
protocols {
ospf {
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}

rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}
policy-options {
term 1 {
then accept;
}
}
}
•

Now in above Policy-option I need to Add OSFF that is :
root@R2#set policy-options policy-statement RIPPOLICY2 term 1 from protocol ospf
Now let’s look at show configuration on R2 again and make sure OSPF has been added :
protocols {
ospf {
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}
rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}

term 1 {
from protocol [ rip direct ospf ];
then accept;
}
}
}
Now when I go to R4 routing tables I see all the Loopback address of R1=1.1.1.1 and R3=3.3.3.3
root@R4> show route

1.1.1.1/32 *[RIP/100] 00:03:11, metric 2, tag 0
> to 20.20.20.2 via em2.0
2.2.2.2/32 *[RIP/100] 00:59:32, metric 2, tag 0
> to 20.20.20.2 via em2.0
2.2.2.3/32 *[RIP/100] 00:59:32, metric 2, tag 0
> to 20.20.20.2 via em2.0
3.3.3.3/32 *[RIP/100] 00:03:11, metric 2, tag 0
> to 20.20.20.2 via em2.0
4.4.4.4/32 *[Direct/0] 01:00:43
> via lo0.0

10.10.10.0/24 *[RIP/100] 00:59:36, metric 2, tag 0
> to 20.20.20.2 via em2.0
20.20.20.0/24 *[Direct/0] 01:00:44
> via em2.0
20.20.20.4/32 *[Local/0] 01:00:44
Local via em2.0
30.30.30.0/24 *[RIP/100] 00:59:32, metric 2, tag 0
> to 20.20.20.2 via em2.0
224.0.0.9/32 *[RIP/100] 01:00:45, metric 1
MultiRecv

Now ; if I Go to R4 I will see all the loopback but I can not ping 1.1.1.1 and 3.3.3.3 ? why ?
Since remember Ping is Echo and Echo-reply and also when I go to R1 and look at Routing
table I do not see
The loopback address of R4=4.4.4.4 (since I need to export RIP into OSPF) , lets look at R1
routing table
root@R1> show route

1.1.1.1/32 *[Direct/0] 00:50:22
> via lo0.0
2.2.2.2/32 *[OSPF/10] 00:36:01, metric 1
> to 10.10.10.2 via em1.0
2.2.2.3/32 *[OSPF/10] 00:36:01, metric 1
> to 10.10.10.2 via em1.0
3.3.3.3/32 *[OSPF/10] 00:23:13, metric 2
> to 10.10.10.2 via em1.0
10.10.10.0/24 *[Direct/0] 00:58:50
> via em1.0
10.10.10.1/32 *[Local/0] 00:58:50
Local via em1.0
30.30.30.0/24 *[OSPF/10] 00:36:01, metric 2
> to 10.10.10.2 via em1.0
224.0.0.5/32 *[OSPF/10] 00:40:08, metric 1
MultiRecv

So how do you solve the problem ; I must go to Middle Router R2 and do same concept as
before ; but in this case I need to export RIP into OSPF , before we did export OSPF into
RIP.
The above concept is called redistribution that is cover in Cisco CCNP class.
Let’s look at what I have on R2 so far :
protocols {
ospf {
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}

rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}
policy-options {
term 1 {
then accept;
}
}
}

So what I need to do create another Policy-option and lets called it OSPFPOLICY and then export it
(apply) it under Protocol ospf
root@R2# set policy-options policy-statement OSPFPOLICY term 1 from protocol rip
set policy-options policy-statement OSPFPOLICY term 1 then accept
now I need to Export it under OSPF (apply this policy) , lets see what we have so far :

protocols {
ospf {
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}
rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}

policy-options {
policy-statement OSPFPOLICY {
term 1 {
from protocol ospf;
then accept;
}
}
term 1 {
then accept;
}
}
}

Now all I have to do Export ( apply OSPFPOLICY) under protocol ospf same as RIP.
root@R2# set protocols ospf export OSPFPOLICY
let’s see what we have on R2 now :
root@R2# run show configuration
protocols {
ospf {
export OSPFPOLICY;
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}

rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}
policy-options {
term 1 {
from protocol rip;
then accept;
}
}

term 1 {
then accept;
}
}
}
Now If I go to R1 and look at Routing table I will see the loopback of R4 as OSPF with tag 2 (
similar to Cisco which is called OE2 =means external ) and here the prefarcane for external
is 150 instead of 10

root@R1> show route
1.1.1.1/32 *[Direct/0] 01:21:26
> via lo0.0
2.2.2.2/32 *[OSPF/10] 01:07:05, metric 1
> to 10.10.10.2 via em1.0
2.2.2.3/32 *[OSPF/10] 01:07:05, metric 1
> to 10.10.10.2 via em1.0
3.3.3.3/32 *[OSPF/10] 00:54:17, metric 2
> to 10.10.10.2 via em1.0

4.4.4.4/32 *[OSPF/150] 00:00:54, metric 2, tag 0
> to 10.10.10.2 via em1.0
10.10.10.0/24 *[Direct/0] 01:29:54
> via em1.0
10.10.10.1/32 *[Local/0] 01:29:54
Local via em1.0
30.30.30.0/24 *[OSPF/10] 01:07:05, metric 2
> to 10.10.10.2 via em1.0
224.0.0.5/32 *[OSPF/10] 01:11:12, metric 1
MultiRecv

PING 4.4.4.4 (4.4.4.4): 56 data bytes
^C
Now even R3 can see loopback of R4=4.4.4.4 and can ping it : (With Preference of 150 and
metric 2 instead of default Preference of 10 and metric 1)

root@R3> show route
1.1.1.1/32 *[OSPF/10] 01:04:56, metric 2
> to 30.30.30.2 via em3.0
2.2.2.2/32 *[OSPF/10] 01:04:56, metric 1
> to 30.30.30.2 via em3.0
2.2.2.3/32 *[OSPF/10] 01:04:56, metric 1
> to 30.30.30.2 via em3.0
3.3.3.3/32 *[Direct/0] 01:28:34
> via lo0.0

4.4.4.4/32 *[OSPF/150] 00:10:14, metric 2, tag 0
> to 30.30.30.2 via em3.0
10.10.10.0/24 *[OSPF/10] 01:04:56, metric 2
> to 30.30.30.2 via em3.0
30.30.30.0/24 *[Direct/0] 01:30:19
> via em3.0
30.30.30.1/32 *[Local/0] 01:30:19
Local via em3.0
224.0.0.5/32 *[OSPF/10] 01:05:01, metric 1
MultiRecv

PING 4.4.4.4 (4.4.4.4): 56 data bytes
^C
Now If I go to R4 and look at Routing table of R4 I see the loopback 1.1.1.1 and 3.3.3.3 but
still can not ping it ? Since I need under OSPF also export direct connection on R2
Here what we had before on R2#

root@R2> run show configuration
protocols {
ospf {
export OSPFPOLICY;
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}
rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}

policy-options {
term 1 {
from protocol rip;
then accept;
}
}
term 1 {
then accept;
}
}
}

As we see I have this on R2:
policy-options {
term 1 {
from protocol rip;
then accept;
The above means redistribute or export RIP into ospf that is what R1 can ping 4.4.4.4 but
R1 can not ping the link 20.20.20.2 or 20.20.20.4

So If I add the export Direct in above , then It means I am also exporting RIP and direct
connection to OSPF then R1 can ping 20.20.20.2 and 20.20.20.4 , and then R4 will be able
to ping 1.1.1.1 and 3.3.3.3
So I go to R2#
root@R2# set policy-options policy-statement OSPFPOLICY term 1 from protocol
Now here what I have in R2 compare in above :

policy-options {
term 1 {
then accept;
Now above means export RIP and directed connection into OSPF
Now R1 should be able ping directly connection link 20.20.20.2 and 20.20.20.4 and R4 be
able to ping 1.1.1.1 and 3.3.3.3

root@R1> ping 20.20.20.2
PING 20.20.20.2 (20.20.20.2): 56 data bytes
^C

root@R1>
root@R1> ping 20.20.20.4
PING 20.20.20.4 (20.20.20.4): 56 data bytes
^C

Now R4 should be able to ping 3.3.3.3 and 1.1.1.1 of R3 and R1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
^C

PING 3.3.3.3 (3.3.3.3): 56 data bytes
^C

So summary on R2 we had this :
root@R2# run show configuration
protocols {
ospf {
export OSPFPOLICY;
area 0.0.0.0 {
interface em1.0;
interface em3.0;
interface lo0.0;
}
}

rip {
group RIPGROUP {
export RIPPOLICY2;
neighbor em2.0;
}
}
}
policy-options {
term 1 {
from protocol [ rip direct ]; ( This means export Rip and directed connection to
OSPF)
then accept;
}
}

term 1 {
from protocol [ rip direct ospf ]; ( this means Export RIP, Directed connection and
OSPF
into RIP)
then accept;
}
}
}

ASM Educational Center Inc. (ASM)
WhereTraining,Technology&ServiceConverge
www.asmed.com

Juniper JNCIA – Juniper RIP and OSPF Route Configuration

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (13)

Semelhante a Juniper JNCIA – Juniper RIP and OSPF Route Configuration

Semelhante a Juniper JNCIA – Juniper RIP and OSPF Route Configuration (20)

Mais de Hamed Moghaddam

Mais de Hamed Moghaddam (10)

Último

Último (20)

Juniper JNCIA – Juniper RIP and OSPF Route Configuration