Successfully pass the free certification exam at IW Academy and become an Infinet Certified Engineer.
Table of content
Routes redistribution from ODR to OSPF
Let's look at the example of routing information redistribution from ODR protocol to OSPF using scheme described in the main document (Figure 1).
Figure 1 - Route redistribution scheme from ODR to OSPF
Pre-configuration
Description | Perform a devices preliminary configuration consisting of the following steps:
|
---|---|
BS1 | Set device ID system prompt BS_1 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.10.1/24 ifc rf5.0 172.16.1.1/29 ifc lo0 192.168.0.1/32 Disable switching switch stop Set radio link rf rf5.0 band 20 rf rf5.0 freq 5100 mint rf5.0 -name "BS_1" mint rf5.0 -type master |
BS2 | Set device ID system prompt BS_2 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.10.2/24 ifc rf5.0 172.16.2.2/29 ifc lo0 192.168.0.2/32 Disable switching switch stop Set radio link rf rf5.0 band 20 rf rf5.0 freq 5000 mint rf5.0 -name "BS_2" mint rf5.0 -type master |
CPE3 | Set device ID system prompt CPE_3 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.30.3/24 ifc rf5.0 172.16.2.3/29 ifc lo0 192.168.0.3/32 Disable switching switch stop Set radio link mint rf5.0 -name "CPE_3" mint rf5.0 -type slave mint rf5.0 prof 1 -band 20 -freq 5000 -type slave |
ODR protocol configuration
Description | Configure the ODR protocol in accordance with the scheme. Step 1: launch the ODR protocol on the rf5.0 interfaces of the BS2 and CPE3 routers. BS2 will be configured asa hub role, CPE3 - as a spoke. Step 2: announce directly connected networks on CPE3 router. |
---|---|
BS1 | No changes are required. |
BS2 | Start ODR: mint rf5.0 -odr hub |
CPE3 | Start ODR: mint rf5.0 -odr spoke Announce directly connected networks: mint rf5.0 -odr spoke connected |
OSPF protocol configuration
Description | Configure the OSPF protocol in accordance with the scheme. Step 1: start the OSPF daemon on the BS1 and BS2 routers. Step 2: set routers IDs. The identifiers will be equal to the IP addresses assigned to the loopback interface. Step 3: define the interfaces where OSPF should be started. Step 4: redistribute routes from the ODR protocol. Such routes have a kernel type. Step 5: make redistribution of directly connected networks on the BS2 router. During redistributing routes from ODR, only routes received from devices with the spoke role will be imported. Thus, to transmit routing information about networks 172.16.2.0/29 and 192.168.0.2/32, it is necessary to announce directly connected networks on BS2. |
---|---|
BS1 | Start OSPF: ospf start Set router-id: ospf config router router-id 192.168.0.1 Start OSPF on interfaces: ospf config router network 172.16.1.0/29 area 0.0.0.0 network 192.168.0.1/32 area 0.0.0.0 network 10.10.10.0/24 area 0.0.0.0 |
BS2 | Start OSPF: ospf start Set router-id: ospf config router router-id 192.168.0.2 Start OSPF on interfaces: ospf config router network 10.10.10.0/24 area 0.0.0.0 Route redistribution from ODR: ospf config router redistribute kernel Directly connected networks announcement: ospf config router redistribute connected |
CPE3 | No changes are required. |
Command output analyzing
Routing table
Description | Analyze the routing table on each device. The routing tables of wireless devices contain entries that each device has information about each subnet shown in the scheme. This means that routes redistribution from ODR to OSPF were made successfully. The CPE3 routing table consists of routes to directly connected networks and a default route. This confirms the statement about the unidirectional redistribution. |
---|---|
BS1 | BS_1#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface 10.10.10.0/24 link#2 UC 0 0 eth0 10.10.30.0/24 10.10.10.2 UG3 0 0 eth0 127.0.0.1 127.0.0.1 UH 3 19 lo0 172.16.1.0/29 link#3 UC 0 0 rf5.0 172.16.2.0/29 10.10.10.2 UG3 0 0 eth0 192.168.0.1 192.168.0.1 UH 0 0 lo0 192.168.0.2 10.10.10.2 UGH3 0 0 eth0 192.168.0.3 10.10.10.2 UGH3 0 0 eth0 224.0.0.0/8 127.0.0.1 UGS 1 335 lo0 |
BS2 | BS_2#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface 10.10.10.0/24 link#2 UC 0 0 eth0 10.10.30.0/24 00:04:35:13:5e:4e ULO 0 0 rf5.0 127.0.0.1 127.0.0.1 UH 3 27 lo0 172.16.1.0/29 10.10.10.1 UG3 0 0 eth0 172.16.2.0/29 link#3 UC 0 0 rf5.0 192.168.0.1 10.10.10.1 UGH3 0 0 eth0 192.168.0.2 192.168.0.2 UH 0 0 lo0 192.168.0.3 00:04:35:13:5e:4e UHLO 0 0 rf5.0 224.0.0.0/8 127.0.0.1 UGS 1 167 lo0 |
CPE3 | CPE_3#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface mintGateway BS_2 rf5.0 10.10.30.0/24 link#2 UC 0 0 eth0 127.0.0.1 127.0.0.1 UH 1 0 lo0 172.16.2.0/29 link#3 UC 0 0 rf5.0 192.168.0.3 192.168.0.3 UH 0 0 lo0 224.0.0.0/8 127.0.0.1 UGS 0 0 lo0 |
Routes redistribution from RIP to OSPF
Let's look at the example of routing information redistribution from RIP to OSPF using scheme described in the main document (Figure 2).
Figure 2 - Scheme of the routes redistribution from RIP to OSPF
Pre-configuration
Description | Perform a devices preliminary configuration consisting of the following steps:
|
---|---|
BS1 | Set device ID system prompt BS_1 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.10.1/24 ifc rf5.0 172.16.1.1/29 ifc lo0 192.168.0.1/32 Disable switching switch stop Set radio link rf rf5.0 band 20 rf rf5.0 freq 5100 mint rf5.0 -name "BS_1" mint rf5.0 -type master |
BS2 | Set device ID system prompt BS_2 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.10.2/24 ifc rf5.0 172.16.2.2/29 ifc lo0 192.168.0.2/32 Disable switching switch stop Set radio link rf rf5.0 band 20 rf rf5.0 freq 5000 mint rf5.0 -name "BS_2" mint rf5.0 -type master |
CPE3 | Set device ID system prompt CPE_3 Remove svi1 interface ifc svi1 destroy Assign IP addresses ifc eth0 10.10.30.3/24 ifc rf5.0 172.16.2.3/29 ifc lo0 192.168.0.3/32 Disable switching switch stop Set radio link mint rf5.0 -name "CPE_3" mint rf5.0 -type slave mint rf5.0 prof 1 -band 20 -freq 5000 -type slave |
RIP configuration
Description | Configure RIP on the BS2 and CPE3 devices. Step 1: Start RIP on the routers. Step 2: define the interfaces through which routing information should exchanged. |
---|---|
BS1 | No changes are required. |
BS2 | Start RIP: arip start Start RIP on interfaces: arip config router network 172.16.2.0/29 |
CPE3 | Start RIP: arip start Start RIP on interfaces: arip config router network 10.10.30.0/24 network 172.16.2.0/29 network 192.168.0.3/32 |
OSPF protocol configuration
Description | Configure the OSPF protocol in accordance with the scheme. Step 1: start the OSPF daemon on the BS1 and BS2 routers. Step 2: set routers IDs. The identifiers will be equal to the IP addresses assigned to the loopback interface. Step 3: define the interfaces where OSPF should be started. Step 4: redistribute routes from the RIP protocol. Such routes have a rip type. Step 5: make announcement of directly connected networks on the BS2 router to announce route to the BS2 loopback interface. |
---|---|
BS1 | Start OSPF: ospf start Set router-id: ospf config router router-id 192.168.0.1 Start OSPF on interfaces: ospf config router network 172.16.1.0/29 area 0.0.0.0 network 192.168.0.1/32 area 0.0.0.0 network 10.10.10.0/24 area 0.0.0.0 |
BS2 | Start OSPF: ospf start Set router-id: ospf config router router-id 192.168.0.2 Start OSPF on interfaces: ospf config router network 10.10.10.0/24 area 0.0.0.0 Route redistribution from RIP: ospf config router redistribute rip Directly connected networks announcement: ospf config router redistribute connected |
CPE3 | No changes are required. |
Command output analyzing
Routing table
Description | Analyze the routing table on each device. The routing tables of BS1 and BS2 are synchronized and contain entries that each device has information about each subnet shown in the scheme. This means that routes redistribution from RIP to OSPF were made successfully. The CPE3 routing table consists of routes to directly connected networks and a default route. This confirms the statement about the unidirectional redistribution. |
---|---|
BS1 | BS_1#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface 10.10.10.0/24 link#2 UC 0 0 eth0 10.10.30.0/24 10.10.10.2 UG3 0 0 eth0 127.0.0.1 127.0.0.1 UH 3 35 lo0 172.16.1.0/29 link#3 UC 0 0 rf5.0 172.16.2.0/29 10.10.10.2 UG3 0 0 eth0 192.168.0.1 192.168.0.1 UH 0 0 lo0 192.168.0.2 10.10.10.2 UGH3 0 0 eth0 192.168.0.3 10.10.10.2 UGH3 0 0 eth0 224.0.0.0/8 127.0.0.1 UGS 1 862 lo |
BS2 | BS_2#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface 10.10.10.0/24 link#2 UC 0 0 eth0 10.10.30.0/24 172.16.2.3 UG3 0 0 rf5.0 127.0.0.1 127.0.0.1 UH 5 60 lo0 172.16.1.0/29 10.10.10.1 UG3 0 0 eth0 172.16.2.0/29 link#3 UC 0 0 rf5.0 192.168.0.1 10.10.10.1 UGH3 0 0 eth0 192.168.0.2 192.168.0.2 UH 0 0 lo0 192.168.0.3 172.16.2.3 UGH3 0 0 rf5.0 224.0.0.0/8 127.0.0.1 UGS 1 462 lo |
CPE3 | AS_3#1> netstat -r Routing tables Destination Gateway Flags Refs Use Interface 10.10.30.0/24 link#2 UC 0 0 eth0 127.0.0.1 127.0.0.1 UH 3 60 lo0 172.16.2.0/29 link#3 UC 0 0 rf5.0 192.168.0.3 192.168.0.3 UH 0 0 lo0 224.0.0.0/8 127.0.0.1 UGS 0 91 lo |
Additional materials
Webinars
- Typical scenario of routing setting using Infinet Wireless devices. Part I.
- Typical scenario of routing setting using Infinet Wireless devices. Part II