Motorola PMP 320 Configuration Manuallines

Brand: Motorola

Model: PMP 320

Category: Gateways/controllers

Type: Configuration Manuallines

Motorola PMP 320 is a wireless broadband radio that provides high-speed Internet access to homes and businesses. It is designed to be easy to install and use, and it comes with a variety of features that make it a great choice for anyone looking for a reliable and affordable wireless Internet connection.

Some of the key features of the Motorola PMP 320 include:

High-speed Internet access with speeds of up to 100 Mbps
Easy installation and setup
A variety of security features to protect your network
Compatibility with a wide range of devices, including computers, smartphones, and tablets

Some of the key features of the Motorola PMP 320 include:

High-speed Internet access with speeds of up to 100 Mbps
Easy installation and setup
A variety of security features to protect your network
Compatibility with a wide range of devices, including computers, smartphones, and tablets

PMP320 – Edge Router

Configuration Guideline

Release 1.1

1 Revision History

Revision # Description Date Author

1.0 Internal Release for

First Informal review

April 12, 2010 Akbar Lokhandwala

1.1 External Release April 19, 2010 Akbar Lokhandwala

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no

liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained

herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,

function, or design, and reserves the right to revise this document and to make changes from time to time in

content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume

any liability arising out of the application or use of any product, software, or circuit described herein; neither does

it convey license under its patent rights or the rights of others. It is possible that this publication may contain

references to, or information about Motorola products (machines and programs), programming, or services that

are not announced in your country. Such references or information must not be construed to mean that Motorola

intends to announce such Motorola products, programming, or services in your country.

Copyrights

This document, Motorola products, and 3

Party Software products described in this document may include or

describe copyrighted Motorola and other 3

Party supplied computer programs stored in semiconductor

memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and

other 3

Party supplied software certain exclusive rights for copyrighted material, including the exclusive right

to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,

any copyrighted material of Motorola, its licensors, or the 3

Party software supplied material contained in the

Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,

merged or modified in any manner without the express written permission of Motorola. Furthermore, the

purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or

otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party

supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law

in the sale of a product.

Restrictions

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No

part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system,

or translated into any language or computer language, in any form or by any means, without prior written

permission of Motorola, Inc.

License Agreements

The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by

express license agreement only and may be used only in accordance with the terms of such an agreement.

High Risk Materials

Components, units, or 3

Party products used in the product described herein are NOT fault-tolerant and are

NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous

environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft

Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola

and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.

Trademarks

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or

service names are the property of their respective owners.

The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product.

Copies of the Declaration of Compliance and installation information in accordance with the requirements of

EN50385 can be obtained from the local Motorola representative or by contacting the Customer Network

Resolution Center (CNRC). The 24–hour telephone numbers are listed at in the overview section of this manual or

visit www.motorola.com/pmp

2 Table of Content

1 Revision History ...........................................................................................................2

2 Table of Content ...........................................................................................................4

3 List of Figures...............................................................................................................5

4 Abstract.........................................................................................................................6

5 Introduction to RIPv2 ...................................................................................................6

5.1 RIP Timers and Stability Features........................................................................6

5.2 RIP Message Format.............................................................................................7

5.3 Difference: RIPv1 and RIPv2...............................................................................8

5.4 Comparison between Various Routing Protocols.................................................8

6 Sample Customer Network...........................................................................................9

6.1 Edge Router Running OSPF.................................................................................9

6.1.1 Solution 1-Redistribute RIPv2 into OSPF network ....................................10

6.1.2 Solution 2- Static routes on Edge and Core Routers..................................11

6.1.3 Solution 3 - Static routes on Edge Router and Redistribute into Core

network 12

6.2 Edge Router Running BGP.................................................................................13

6.2.1 Solution 1-Redistribute RIPv2 into BGP network ......................................14

6.2.2 Solution 2- Configure Static routes on Edge and Core Routers.................15

6.2.3 Solution 3 – Configure Static routes on Edge Router and Redistribute into

Core network...............................................................................................................15

6.3 Edge Router Running EIGRP.............................................................................16

6.3.1 Solution 1-Redistribute RIPv2 into EIGRP network ..................................17

6.3.2 Solution 2- Configure Static routes on Edge and Core Routers.................18

6.3.3 Solution 3 – Configure Static routes on Edge Router and Redistribute into

Core network...............................................................................................................18

7 Configuration example................................................................................................19

7.1 AP IP parameters:...............................................................................................20

7.1.1 Configuration of IP parameters on Access Point PMP320........................21

7.1.2 Configuration of IP Parameters on Cisco 6500/7200 Series Edge Router 27

7.1.2.1 Redistributing RIPv2 route into OSPF network...........................29

7.1.2.2 Redistributing RIPv2 routes into BGP network............................31

7.1.2.3 Redistributing RIPv2 routes into EIGRP network........................33

7.1.2.4 Configure Static Routes on the Edge Router and Core Network

7.1.2.5 Configure Static routes only on the Edge Router and

Redistribute into Core Network..........................................................................35

7.1.2.5.1 Redistribute Static routes into OSPF Network.........................36

7.1.2.5.2 Redistribute Static routes into EIGRP Network .......................36

7.1.2.5.3 Redistribute Static routes into BGP Network ...........................36

3 List of Figures

Figure 1 Sample Customer Network: Edge Router running OSPF ......................................9

Figure 2 Redistribute RIPv2 into OSPF network ...............................................................10

Figure 3 Configure static routes on edge and core routers ................................................11

Figure 4 Configure static routes on edge router and redistribute into core network ..........12

Figure 5 Sample Customer Network: Edge Router running BGP......................................13

Figure 6 Redistribute RIPv2 into BGP network.................................................................14

Figure 7 Edge Router Running EIGRP...............................................................................16

Figure 8 Redistribute RIP2 into EIGPR Network...............................................................17

Figure 9 Sample Customer Network setup.........................................................................20

Figure 10 Redistribution of RIPv2 routes in OSPF............................................................29

Figure 11 Redistribution of RIPv2 routes in BGP..............................................................31

Figure 12 Redistribution of RIPv2 routes in EIGRP..........................................................33

Figure 13 Configure Static routes in Edge Router/Core Network......................................37

4 Abstract

Primary purpose of this document is to cover Layer3 functionality of PMP320 and how to

integrate PMP320 into an existing customer network. We start with the Introduction of

RIPv2 routing protocol, then we move on to compare some popular routing protocols with

RIPv2. Our next section provides sample customer network setups and “redistribution”

configuration examples in relation to integrating PMP320 with RIPv2.Routing protocols

covered include RIPv2, OSPF, EIGRP and BGP on Cisco Routers (6500 and 7200 series).

5 Introduction to RIPv2

RIP process operates from UDP port 520, all RIP messages are encapsulated in a UDP

datagram with both the source and destination port fields set to 520. RIP defines two

messages types: Request and Response messages. A Request message is used to ask

neighboring routers to send an update. A Response message carries the update. The metric

used by RIP is “hop count”, with 1 signifying a directly connected network of the

advertising router and 16 signifying as unreachable network.

RIPv2 uses multicast updates to other RIPv2 speaking routers, using the reserved class D

address 224.0.0.9. The advantage of multicasting is that devices on the local network that

are not connected with RIP routing do not have to spend time “unwrapping” broadcast

packets from the router.

5.1 RIP Timers and Stability Features

After the RIP process is enabled, the router sends a Response message out every RIP

enabled interface every 30 seconds. The Response message (update) contains the routers

“full” route table with the exception of entries suppressed by the split horizon rule.

RIP process employs several timers, they are as follows:

Update Timer: RIP routers send periodic updates every 30 seconds to directly connected

neighbors. These updates contain the entire route table. The update timer initiating this

periodic update includes a random variable to prevent table synchronization. As a result,

the time between individual updates from a typical RIP process might be from 25 to 35

seconds.

Expiration Timer: The expiration timer is initialized to 180 seconds, whenever a new

route is established. If an update for a route is not heard within that 180 seconds

(equivalent to six update periods), the hop count for the route is changed to 16, marking

the router as unreachable. Cisco IOS refers this timer as “invalid” timer.

Flush timer: It is set to 300 seconds (120 seconds longer then the expiration timer or 10

times the Update timer). During this period the route will be advertised with the

unreachable metric (hop count is set to 16) until the Flush timer expires, at which time the

route will be removed from the route table.

NOTE: Cisco routers use a 60 second garbage collection timer (Flush), although RFC

1058 prescribes 120 seconds. PMP320 Access point uses 300 seconds for garbage

collection timer. Currently RIPv2 timers in PMP320 Access Point are pre-defined as per

RFC 1058.

Customers who wish to integrate PMP320 with a Cisco Router, they will have to modify

the garbage collection timer in the Cisco router to match with PMP320 system. It is

important that these timers (update, expiration and garbage collection timer) employed by

RIP process are same throughout the network.

5.2 RIP Message Format

Command Version Unused (Set to all zeros)

Address Family Identifier Route Tag

IP Address

Subnet Mask

Next Hop

Metric

32 bits (4 bytes)

RIPv2 updates can contain entries for up to 25 routes. Maximum datagram size with an

eight byte UDP header is 512 bytes.

Command: Will always be set to one, signifying a Request message or two, signifying a

Response message.

Version: Will be set to two for RIPv2. RIPv2 will process valid RIPv1 message. It will be

set to one for RIPv1.

Address Family Identifier: It is set to two for IPv4.

Route Tag: Provides a field for tagging external routes or routes that have been

“Redistributed” into RIPv2 process.

IP Address: The IPv4 address of the destination of the route. It may be a major network

address, a subnet or a host route.

Subnet Mask: Identifies the network and subnet portion of the IPv4 address. VLSM

(Variable Length Subnet Masking) feature is available due to the presence of this field.

Next Hop: Identifies a better next-hop address

Metric: is a hop count between 1 and 16.

5.3 Difference: RIPv1 and RIPv2

RIPv1 RIPv2

Classful Routing protocol Classless Routing protocol

Does not support VLSM Supports VLSM

Uses Broadcast to send updates

255.255.255.255

Uses Multicast to send updates

224.0.0.9

Does not support Authentication Supports Authentication – MD5

Subnet mask not present in route entry Subnet mask present with each route entry

Does not support External route tags Supports External route tags

5.4 Comparison between Various Routing Protocols

Property RIPv2 OSPF EIGRP BGP

Method Distance

Vector

Link State Hybrid Distance

Vector

Path Vector

Summarization Auto and

Manual

Manual Auto and Manual Auto Manual

VLSM Yes Yes Yes Yes

Convergence

Speed

slow fast Very fast slow

Timers (seconds) Update = 30,

Expiration =

180

Flush = 300

LAN

Hello = 10

Router Dead

interval = 40

WAN

Hello = 30

Router Dead

Interval = 120

LAN

Hello = 5

Router Dead

Interval = 15

WAN

Hello = 60

Router Dead

Interval = 180

Update = 60

Expiration =

180

Network Size Medium Large Large Very Large

Metric Hop Count Bandwidth Bandwidth, Delay,

Reliability and

Load

Various Path

attributes

Administrative

Distance

120 110 90 EBGP - 20

iBGP - 200

Protocol/Port UDP/520 IP/89 IP/88 TCP/179

Authentication Yes Yes Yes Yes

6 Sample Customer Network

6.1 Edge Router Running OSPF

Customer has an existing Core network and the edge router is running OSPF as the

Routing protocol. Customer plans to integrate PMP320 as a layer 3 device (Router

Functionality).

Figure 1 Sample Customer Network: Edge Router running OSPF

LAN INTERFACE

CPE

IP CLOUD

OSPF Network

ACCESS POINT

EXISTING NETWORK TOPOLOGY NETWORK TO BE INTEGRATED IN THE EXISTING CORE SETUP

Edge Router

Three Possible Solutions can be implemented to integrate PMP320 system to the existing

Core Network.

6.1.1 Solution 1-Redistribute RIPv2 into OSPF network

Step 1: Configure PMP320 as a Layer 3 device. Currently this is the only mode available

for PMP320 systems. By default PMP320 system uses RIPv2 as the routing protocol. Only

the Fast Ethernet (wired) interface of the AP takes part in RIPv2 routing protocol.

Step 2: Once the AP is configured as a layer 3 device, both the interfaces (wired and

wireless) on the AP should be in 2 different distinct subnets.

Step 3: Configure RIPv2 as a second routing protocol on the edge router. Once RIPv2

process is enabled on the Edge Router, it will learn the subnets behind the Access Point

(Wireless interface of the AP).

Step 4: Redistribute RIPv2 networks into OSPF domain. This way the

Devices/Application Servers which are northbound (inside the IP Cloud) will be able to

reach the CPE.

Note: sample configurations are provided in Configuration example section 7.1.2.1

Figure 2 Redistribute RIPv2 into OSPF network

LAN

INTERFACE

CPE

IP CLOUD

OSPF Network

ACCESS POINT

EXISTING NETWORK TOPOLOGY

Edge Router

RIPv2 Network

ilable

ute (with different next-hop address on all the subsequent routers present in the IP

on example section 7.1.2.4

Figure 3 Configure static routes on edge and core routers

6.1.2 Solution 2- Static routes on Edge and Core Routers

Step 1: Configure PMP320 as a Layer 3 device. Currently this is the only mode ava

for PMP320 systems. By default PMP320 system uses RIPv2 as the routing protocol. Only

the Fast Ethernet (wired) interface of the AP takes part in RIPv2 routing protocol.

Step 2: Once the AP is configured as a layer 3 device, both the interfaces (wired and

wireless) on the AP should be in 2 different distinct subnets.

Step 3: Configure a Static route on the Edge Router. Also we will have to add the same

static ro

Cloud to provide connectivity to the “wireless subnet” (wireless interface of the AP and

CPE).

Step 4: Customer should be able to reach the CPE and AP’s wireless interface. This can be

confirmed with a simple test of using ping.

ote: sample configurations are provided in ConfiguratiN

LAN

INTERFACE

CPE

IP CLOUD

OSPF Network

ACCESS POINT

EXISTING NETWOR

Edge Router

STATIC ROUTES

K TOPOLOGY

Note: This solution would be useful for Customers who do not want to redistribute RIPv2

in there core network setup. In certain circumstances it would not be advisable to run

multiple routing protocols on a single router si

nce this would be CPU intensive. But this

depends on the type/make of Router. Most of the Cisco routers are capable of handling

multiple routing protocols at the same time.

6.1.3 Solution 3 - Static routes on Edge Router and Redistribute into

Core network

Step 1: Configure PMP320 as a Layer 3 device. Currently this is the only mode available

for PMP320 systems. By default PMP320 system uses RIPv2 as the routing protocol. Only

the Fast Ethernet (wired) interface of the AP takes part in RIPv2 routing protocol.

Step 2: Once the AP is configured as a layer 3 device, both the interfaces (wired and

wireless) on the AP should be in 2 different distinct subnets.

Step 3: Configure a Static route on the Edge Router only.

Step 4: Redistribute Static routes and into OSPF domain.

Note: sample configurations are provided in Configuration example section 7.1.2.5.1

Figure 4 Configure static routes on edge router and redistribute into core network

LAN

INTERFACE

CPE

IP CLOUD

OSPF Network

ACCESS POINT

EXISTING NETWORK TOPOLOGY

Edge Router

STATIC ROUTES

Note: The main advantage of this solution over solution#2 is the operator does not have to

worry about adding Static routes in all the subsequent routers. The OSPF process or any

other dynamic routing protocol (like EIGRP, IS-IS, BGP) will take care of this.

6.2 Edge Router Running BGP

Customer has an existing Core network and the edge router is running BGP as the Routing

protocol. Customer plans to integrate PMP320 as a layer 3 device (Router Functionality).

Figure 5 Sample Customer Network: Edge Router running BGP

LAN INTERFACE

CPE

IP CLOUD

BGP Network

ACCESS POINT

EXISTING NETWORK TOPOLOGY NETWORK TO BE INTEGRATED IN THE EXISTING CORE SETUP

Edge Router

Three Possible Solutions can be implemented to integrate PMP320 system to the existing

Core Network.

6.2.1 Solution 1-Redistribute RIPv2 into BGP network

Step 1: Configure PMP320 as a Layer 3 device. Currently this is the only mode available

for PMP320 systems. By default PMP320 system uses RIPv2 as the routing protocol. Only

the Fast Ethernet (wired) interface of the AP takes part in RIPv2 routing protocol.

Step 2: Once the AP is configured as a layer 3 device, both the interfaces (wired and

wireless) on the AP should be in 2 different distinct subnets.

Step 3: Configure RIPv2 as a second routing protocol on the edge router. Once RIPv2

process is enabled on the Edge Router, it will learn the subnets behind the Access Point

(Wireless interface of the AP).

Step 4: Redistribute RIPv2 networks into BGP Autonomous System domain. This way the

Devices/Application Servers which are northbound (inside the IP Cloud) will be able to

reach the CPE.

Note: sample configurations are provided in Configuration example section 7.1.2.2

Figure 6 Redistribute RIPv2 into BGP network

LAN

INTERFACE

CPE

IP CLOUD

BGP Network

ACCESS POINT

EXISTING NETWORK TOPOLOGY

Edge Router

RIPv2 Network

6.2.2 Solution 2- Configure Static routes on Edge and Core Routers

Same as explained in section 6.1.2

6.2.3 Solution 3 – Configure Static routes on Edge Router and

Redistribute into Core network

Same as explained in section 6.1.3

6.3 Edge Router Running EIGRP

Customer has an existing Core network and the edge router is running EIGRP as the

Routing protocol. Customer plans to integrate PMP320 as a layer 3 device (Router

Functionality).

Figure 7 Edge Router Running EIGRP

Three Possible Solutions can be implemented to integrate PMP320 system to the existing

Core Network.

6.3.1 Solution 1-Redistribute RIPv2 into EIGRP network

Step 1: Configure PMP320 as a Layer 3 device. Currently this is the only mode available

for PMP320 systems. By default PMP320 system uses RIPv2 as the routing protocol. Only

the Fast Ethernet (wired) interface of the AP takes part in RIPv2 routing protocol.

Step 2: Once the AP is configured as a layer 3 device, both the interfaces (wired and

wireless) on the AP should be in 2 different distinct subnets.

Step 3: Configure RIPv2 as a second routing protocol on the edge router. Once RIPv2

process is enabled on the Edge Router, it will learn the subnets behind the Access Point

(Wireless interface of the AP).

Step 4: Redistribute RIPv2 networks into EIGRP autonomous System domain. This way

the Devices/Application Servers which are northbound (inside the IP Cloud) will be able

to reach the CPE.

Note: sample configurations are provided in Configuration example section 7.1.2.3

Figure 8 Redistribute RIP2 into EIGRP Network

LAN

INTERFACE

CPE

IP CLOUD

ACCESS POINT

EXISTING NETWORK TOPOLOGY

Edge Router

RIPv2 Network

EIGRP Network

6.3.2 Solution 2- Configure Static routes on Edge and Core Routers

Same as explained in section 6.1.2

6.3.3 Solution 3 – Configure Static routes on Edge Router and

Redistribute into Core network

Same as explained in section 6.1.3

7 Configuration example

Based on the Sample IP address scheme shown below we are going to configure PMP320

Access Point wired/wireless interface. Once the AP is configured with appropriate IP

addresses, we move on to configure Edge Router to perform redistribution of RIPv2 into

Core network.

Assumption: Edge Router and Core network are pre-configured with appropriate dynamic

routing protocols (OSPF, EIGRP or BGP) or static routes are in place. Hence from

router’s perspective we only concentrate on how to redistribute RIPv2 routes learned via

PMP320 into the Core Network. In this document we do not show on how to configure the

Edge Router or Core Network for OSPF

7.1 AP IP parameters:

Example of IP addresses Scheme:

Access

Point

LAN

Network

Address

LAN IP

Address

Default GW

(Router

Interface)

Subnet Mask Wireless

Network

Address

Wireless IP

address

Subnet Mask

AP#1 172.16.10.0 172.16.10.254 172.16.10.1 255.255.255.0 201.201.201.0 201.201.201.1 255.255.255.0

AP#2 172.16.20.0 172.16.20.254 172.16.20.1 255.255.255.0 202.202.202.0 202.202.202.1 255.255.255.0

AP#3 172.16.30.0 172.16.30.254 172.16.30.1 255.255.255.0 203.203.203.0 203.203.203.1 255.255.255.0

AP#4 172.16.40.0 172.16.40.254 172.16.40.1 255.255.255.0 204.204.204.0 204.204.204.1 255.255.255.0

Network Topology

Figure 9 Sample Customer Network setup

TOWER #1

Edge Router

SWITCH

201.201.201.0/24

203.203.203.0/24 204.204.204.0/24

202.202.202.0/24

CPE

CPECPE

CPE

.254

.254 .254

.254

172.16.10.1/24

172.16.20.1/24

172.16.30.1/24

172.16.40.1/24

.254

RIP v2 Network

E1/0

E1/1

E1/2

Core Router

IP CLOUD / CUSTOMER’S

CORE NETWORK

OSPF, EIGRP or BGP

already running on

Edge Router

E0/0

E1/4

NETWORK TO BE INTEGRATED IN THE EXISTING CORE

SETUP

EXISTING NETWORK TOPOLOGY

100.100.100.0/24

.1.2

Note: In the above Figure 9 either you can create a “Trunk Link” between the Edge Router

and Switch (Commonly referred as Router on a Stick) or you can have individual

connections between the interfaces of the Edge Router and switch.

Page is loading ...

Motorola PMP 320 Configuration Manuallines

Brand: Motorola

Model: PMP 320

Category: Gateways/controllers

Type: Configuration Manuallines

Some of the key features of the Motorola PMP 320 include:

High-speed Internet access with speeds of up to 100 Mbps
Easy installation and setup
A variety of security features to protect your network
Compatibility with a wide range of devices, including computers, smartphones, and tablets

Download PDF

report

Motorola PMP 320 Configuration Manuallines

Motorola PMP 320 Configuration Manuallines

Related papers

Other documents