Professional Documents
Culture Documents
Sklmds Mds
Sklmds Mds
"R1(conf)# router ospf 10 We can also use 11 or multiple process id on R1, but
which network you are assigning under which process id does matter. process id is
locally significant no. the router,
meaning you can have multiple process id on the same router or process id 10 on R1
and process-id 11 on R2, but this create confusion."
"OSPF configuration on R1 and R2 connected with 1.1.1.0/24 over wan link. R1 lan or
fa0/0 is 10.50.0.0/16 and R2 lan is 172.16.0.0/24 to 172.16.7.0/24, ospf Area is 0
and Process id is 10.
1 > R1(conf)# router ospf 10 > network 1.1.1.1 0.0.0.0 area 0 or
[ (conf)# int s0/0 > ip ospf 10 area 0 > no shut ] > network
10.50.0.0 0.0.255.255 area 0 This says:
i) Advertise 1.1.1.1/32 and 10.50.0.0/16 routes with their subnet mask to
all the neighbors of R1 from where it has establsihed the Neigbor relationship
ii) Listen for incoming ospf routing information or hello message on any
interface of R1 that starts with 1.1.1.1/32 and 10.50.0.0/16
iii) Permitted to send outbound hello message and dynamically learn any
neigbor and established neighbor relationship (if neighbor parameters matches) on
any interface
whose ip starts with 1.1.1.1/32 and 10.50.0.0/16
R2(conf)# router ospf 10 > network 1.1.1.2 0.0.0. area 0 >
network 172.16.0.0 0.0.0.255 area 0 [ on ASA network 172.16.0.0
255.255.255.0 ] or
R2(conf)# router ospf 10 > network 0.0.0.0 255.255.255.255 area 0
[Advertise all interface of R2 in ospf doamin which has an ip set, and also send
ospf hello to establish neighbor
from all interfaces], For each interface there would be a router LSA
advertise by router.
2 > R1/R2(conf-router)# passive-interface fa0/0 (Do not send ospf hello to
establish NR from lan interfaces of R1/R2 because only switches are connected
there).
3 > R1/R2(conf)# int s0/0 > ip ospf hello-interval 1 > ip ospf
dead-interval 3 [ To set OSPF hello interval to 1 second and dead interval to 3
second, timer we defined on router interface ]"