Once I have configure everything I am going to wipe the lab and start again seeing if I can clean up some of the mess, but I won't post line by line here, I will just post the final configs.
Got OSPF up and running
Rush through redistribution (export) between protocols
Getting smoother with configuring interface ip addressing
Like the way OSPF is assigned by Interface not a silly network statement. To be fair you can do that on IOS but being old school I often still do it the old way.
Finally - Just had a fight with word press, having trouble pasting show route output, no more editing just publish raw.
Notes from the day
OSPF Today.
set host name and domain name to all ospf routers
set system host-name
set system root-authentication plain-text-password
apply interface configuration to all ospf routers
now do ospf???
I haven't looked at a book yet so doing this by feel
Junos2
configure protocols
set ospf area 0 interface em1
Junos3
edit protocol interface em0
Junos 3 immediately formed a neighbot with Junos 2
do the same for 4,6 and 7
ok a quick peak at a book and look like I can just add the intefaces into the area
edit protocols
set ospf area 0 interface lo0.10 passive
can see all loopback at junos 3
*** redist into rip
root@Junos2>
http://forums.juniper.net/t5/Routing/redistribute-RIP-routes-to-OSPF/td-p/22294
root@Junos2> configure
Entering configuration mode
[edit]
root@Junos2# edit policy-options
[edit policy-options]
root@Junos2# set policy-statement rip->ospf term 1 from protocol rip
[edit policy-options]
root@Junos2# set policy-statement rip->ospf term 1 then accept
[edit policy-options]
root@Junos2# set policy-statement rip->ospf term 2 then reject
[edit policy-options]
root@Junos2# commit
commit complete
[edit policy-options]
root@Junos2# set policy-statement ospf->rip term 1 from protocol ospf
[edit policy-options]
root@Junos2# set policy-statement ospf->rip term 1 then accept
[edit policy-options]
root@Junos2# set policy-statement ospf->rip term 2 then reject
[edit policy-options]
root@Junos2# commit
commit complete
[edit policy-options]
root@Junos2# top
[edit]
root@Junos2# edit protocols ospf
[edit protocols ospf]
root@Junos2# set export rip->ospf
[edit protocols ospf]
root@Junos2# up
[edit protocols]
root@Junos2# edit rip
[edit protocols]
root@Junos2# commit
commit complete
[edit]
root@Junos2# exit
Exiting configuration mode
protocols {
ospf {
export rip->ospf;
area 0.0.0.0 {
interface em1.0;
interface lo0.10 {
passive;
}
}
}
rip {
send multicast;
receive version-2;
group 1 {
export [ advertise-rip-routes ospf->rip ];
neighbor em0.0;
neighbor lo0.10;
}
}
}
policy-options {
policy-statement advertise-rip-routes {
term 1 {
from protocol direct;
then accept;
}
}
policy-statement ospf->rip {
term 1 {
from protocol ospf;
then accept;
}
term 2 {
then reject;
}
}
policy-statement rip->ospf {
term 1 {
from protocol rip;
then accept;
}
term 2 {
then reject;
}
}
}
root@Junos2>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\JohnMcManus>ping 10.254.200.6
Pinging 10.254.200.6 with 32 bytes of data:
Reply from 10.254.200.6: bytes=32 time=2ms TTL=62
Reply from 10.254.200.6: bytes=32 time=2ms TTL=62
Ping statistics for 10.254.200.6:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
Control-C
C:\Users\JohnMcManus>
I can ping from 192.168.1.0/24 network
What I achieved
Got OSPF up and running
Rush through redistribution (export) between protocols
Getting smoother with configuring interface ip addressing
Noteworth thoughts
Like the way OSPF is assigned by Interface not a silly network statement. To be fair you can do that on IOS but being old school I often still do it the old way.
Finally - Just had a fight with word press, having trouble pasting show route output, no more editing just publish raw.
Comments
Post a Comment