Redistributing Ripv2 Route Into Ospf Network - Motorola PMP320 Configuration Manuallines

Note: Customer will not be able to ping wireless interface of access point or subscriber
module from the IP Cloud (Core Network). In order to perform this, we will have to
redistribute RIPv2 routes into core network via Edge Router or configure Static routes.
Note: From Step 7 onwards we show specific configuration required by Cisco Routers to
redistribute RIPv2 networks into OSPF, EIGRP and BGP networks.
Step 7: Redistribute RIPv2 routes into the Core Network via Edge Router:

7.1.2.1 Redistributing RIPv2 route into OSPF network

Enter configuration commands, one per line. End with CNTL/Z.
Edge-Router(config)#router ospf 1
Edge-Router(config-router)#redistribute rip subnets
The statement "redistribute rip subnets" will redistribute RIPv2 routes into the Core
network.
Routing table of "Core Router" before RIPv2 redistribution:
Core-Router#show ip route
<output truncated>
Gateway of last resort is not set
100.0.0.0/30 is subnetted, 1 subnets
C 100.100.100.0 is directly connected, FastEthernet0/0
Routing table of "Core Router" after RIPv2 redistribution:
Core-Router#show ip route
<output truncated>
Gateway of last resort is not set
O E2 201.201.201.0/24 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
O E2 202.202.202.0/24 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
O E2 203.203.203.0/24 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
100.0.0.0/30 is subnetted, 1 subnets
C 100.100.100.0 is directly connected, FastEthernet0/0
172.16.0.0/24 is subnetted, 3 subnets
O E2 172.16.30.0 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
O E2 172.16.20.0 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
O E2 172.16.10.0 [110/20] via 100.100.100.1, 00:01:38, FastEthernet0/0
Core-Router#