Commissioning Manual v06-460 PDF

ASWipLL and
AS3010 Systems
Wireless IP-Based Local Loop System
Release 4.6
Commissioning Manual
Leading the World in Wireless DSL

The ASWipLL product bears the CE marking. This CE marking demonstrates ASWipLL's full compliance with
applicable European Union (EU) directives:
The ASWipLL product bears the Underwriters Laboratories (UL) marking, demonstrating full compliance with UL's
safety requirements:
ASWipLL products also bear the Federal Communications Commission (FCC) marking, demonstrating compliance
with FCC Part 15 regulations.
Revision Record: ASWipLL Commissioning Manual

Rev Date Update Description
- Mar-02 (Marconi)
01 Feb-03 ASWipLL Release 4.0 and 4.1. Auth: InterDoc. Conversion of previous version’s PDF to
Word (Airspan template); SDTA deleted; screens updated; ASWipLL Software and
Database Upgrade manual incorporated; VoIP procedures added.
02 Jun-03 ASWipLL Release 4.2F. Auth: InterDoc. Updated with PPR, Auto Connect.
03 Jul-03 ASWipLL Release 4.2A. Auth: InterDoc. Updated with Transp. Bridging.
04 Oct-03 ASWipLL Rel. 4.2B. Auth: InterDoc. Updates: combined IP routing and transparent
bridging; repeater solution; pictures; troubleshooting.
05 Feb-04 ASWipLL Rel. 4.4. Auth: InterDoc. Updates: drawings; miscellaneous.
06 Aug-04 ASWipLL Rel. 4.6. Auth: InterDoc. Updates: link quality; static routes; virtual ports; Tx
power; synchronization; rate; traps; miscellaneous.
Publication No. 01040311-06

 Copyright by Airspan Networks Inc., 2004. All rights reserved worldwide.
The information contained in this document is proprietary and is subject to all relevant copyright, patent and other
laws protecting intellectual property, as well as any specific agreement protecting Airspan Networks Inc. rights in
the aforesaid information. Neither this document nor the information contained herein may be published,
reproduced or disclosed to third parties, in whole or in part, without the express, prior, written permission of
Airspan Networks Inc. In addition, any use of this document or the information contained herein for any purposes
other than those for which it was disclosed is strictly forbidden.
Airspan Networks Inc. reserves the right, without prior notice or liability, to make changes in equipment design or
specifications.
Information supplied by Airspan Networks Inc. is believed to be accurate and reliable. However, no responsibility
is assumed by Airspan Networks Inc. for the use thereof nor for the rights of third parties which may be effected in
any way by the use thereof.
Any representation(s) in this document concerning performance of Airspan Networks Inc. product(s) are for
informational purposes only and are not warranties of future performance, either express or implied. Airspan
Networks Inc. standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty
offered by Airspan Networks Inc. in relation thereto.
This document may contain flaws, omissions or typesetting errors; no warranty is granted nor liability assumed in
relation thereto unless specifically undertaken in Airspan Networks Inc. sales contract or order confirmation.
Information contained herein is periodically updated and changes will be incorporated into subsequent editions. If
you have encountered an error, please notify Airspan Networks Inc. All specifications are subject to change
without prior notice.
Main Operations:
Airspan Communications Ltd.
Cambridge House
Oxford Road
Uxbridge
Middlesex
UB8 1UN
United Kingdom
Tel: (44)-895 467100
Web site: http//www.airspan.com
Customer Service (TAC): Wipll.tech_support@airspan.com or (+972) 3 9777 555
This page is intentionally left blank.
Commissioning Manual Contents
Contents
About this Manual............................................................................................... xvii
Purpose ...................................................................................................... xvii
Targeted Audience ..................................................................................... xvii
Referenced Documentation........................................................................xviii
Organization of this Manual........................................................................xviii
Typographical Conventions......................................................................... xxi
Customer Service........................................................................................ xxi
1. Introduction .............................................................................................. 1-1

1.1. Main Features ..................................................................................... 1-2
1.2. Customer Benefits............................................................................... 1-4
1.3. System Architecture ............................................................................ 1-5
1.3.1. Base Station Site .................................................................. 1-7
1.3.2. Subscriber Site ................................................................... 1-10
1.3.2.1. Outdoor Radio with Indoor Ethernet Switch/Hub . 1-10
1.3.2.2. Indoor Radio Unit Only......................................... 1-14
1.3.3. Network Management Tools............................................... 1-15
1.4. Applications ....................................................................................... 1-16
1.4.1. Broadband Data Access..................................................... 1-16
1.4.2. High Speed Internet Access ............................................... 1-17
1.4.3. Voice over IP ...................................................................... 1-18
1.4.4. Traffic Engineering in Multi-Tenant Application .................. 1-19
1.4.4.1. VLAN Tagging...................................................... 1-19
1.4.4.2. Without VLAN Tagging ........................................ 1-21
1.4.5. Repeater Solution............................................................... 1-22
01040311-06 Airspan Networks Inc. v

Contents Commissioning Manual
2. Installing ASWipLL Management Software ........................................... 2-1

2.1. System Requirements ......................................................................... 2-2
2.2. Installing WipConfig............................................................................. 2-3
2.3. Installing WipManage ........................................................................ 2-11
3. Initial Configuration ................................................................................. 3-1

3.1. Overview ............................................................................................. 3-2
3.2. Initial Serial Configuration ................................................................... 3-4
3.2.1. Summary of Tasks................................................................ 3-5
3.2.2. Task 1: Start WipConfig........................................................ 3-6
3.2.3. Task 2: Initialize BSDU......................................................... 3-8
3.2.4. Task 3: Initialize BSR ......................................................... 3-12
3.2.5. Task 4: Initialize SPR ......................................................... 3-16
3.3. Establishing a Network Connection................................................... 3-20
3.3.1. Summary of Tasks.............................................................. 3-22
3.3.2. Task 1: Configure PC’s IP Subnet Address........................ 3-22
3.3.3. Task 2: Connect WipConfig to the Device.......................... 3-28
4. Establishing BSR-SPR Link in Router Mode ......................................... 4-1

4.1. Summary of Tasks .............................................................................. 4-2
4.2. Task 1: Configure BSR for IP Routing................................................. 4-4
4.3. Task 2: Configure SPR for IP Routing................................................. 4-9
4.4. Task 3: Start WipManage.................................................................. 4-14
4.5. Task 4: Add a BS Group ................................................................... 4-15
4.6. Task 5: Add a Base Station............................................................... 4-16
4.7. Task 6: Add a BSDU ......................................................................... 4-18
4.8. Task 7: Add a BSR............................................................................ 4-20
4.9. Task 8: Add an SPR.......................................................................... 4-23
4.10. Task 9: Test the BSR-SPR Network Link........................................ 4-29
4.11. Color-Coding of SPR Icons ............................................................. 4-30
vi Airspan Networks Inc. 01040311-06

5. Establishing BSR-SPR Link in Bridge Mode ......................................... 5-1

5.1. Summary of Tasks .............................................................................. 5-2
5.2. Task 1: Configure BSR for Transparent Bridging................................ 5-4
5.3. Task 2: Configure SPR for Transparent Bridging................................ 5-9
5.4. Task 3: Start WipManage.................................................................. 5-14
5.5. Task 4: Add a BS Group ................................................................... 5-15
5.6. Task 5: Add a Base Station............................................................... 5-16
5.7. Task 6: Add a BSDU ......................................................................... 5-18
5.8. Task 7: Add a BSR............................................................................ 5-20
5.9. Task 8: Add an SPR.......................................................................... 5-23
5.10. Task 9: Test the BSR-SPR Network Link........................................ 5-26
5.11. Advanced Tasks.............................................................................. 5-27
5.11.1. Task 1: View MAC Addresses .......................................... 5-27
5.11.2. Task 2: Define MAC Address Aging Time ........................ 5-29
5.11.3. Task 3: Enable Forwarding of Various Packets................ 5-30
6. Changing Link from Router to Bridge .................................................... 6-1

6.1. Overview ............................................................................................. 6-2
6.2. Summary of Tasks .............................................................................. 6-4
6.3. Task 1: Install WipManage that Supports Transparent Bridging ......... 6-5
6.4. Task 2: Upgrade SPR to Support Transparent Bridging ..................... 6-5
6.5. Task 3: Upgrade BSR to Support Transparent Bridging ..................... 6-6
6.6. Task 4: Configure BSR for Transparent Bridging................................ 6-6
6.7. Task 5: Configure SPR for Transparent Bridging.............................. 6-11
6.8. Task 6: Add SPR in WipManage....................................................... 6-16
6.9. Task 7: Test the BSR-SPR Network Link.......................................... 6-21
7. Changing Link from Bridge to Router .................................................... 7-1

7.1. Overview ............................................................................................. 7-2
7.2. Summary of Tasks .............................................................................. 7-4
7.3. Task 1: Configure BSR for IP Routing................................................. 7-5
7.4. Task 2: Configure SPR for IP Routing............................................... 7-10
01040311-06 Airspan Networks Inc. vii

7.5. Task 3: Add an SPR.......................................................................... 7-15

7.6. Task 4: Test the BSR-SPR Network Link.......................................... 7-23
8. Establishing BSR-SPR Link with AutoConnect..................................... 8-1

8.1. Overview ............................................................................................. 8-2
8.1.1. Automatically Connecting SPRs to BSRs............................. 8-4
8.1.2. Redirecting SPRs to Specific BSRs ..................................... 8-5
8.2. Configuring Repeating AutoConnect................................................... 8-8
8.2.1. Summary of Tasks................................................................ 8-8
8.2.2. Task 1: Add AutoConnect SPRs .......................................... 8-9
8.2.3. Task 2: Define AutoDisconnect Interval ............................. 8-14
8.2.4. Task 3: Configure AutoConnect for SPR............................ 8-16
8.2.4.1. Using WipConfig .................................................. 8-16
8.2.4.2. Using WipManage................................................ 8-20
8.2.5. Task 4: Verify BSR-SPR Link ............................................. 8-26
8.3. Configuring AutoConnect with Redirection........................................ 8-27
8.3.1. Summary of Tasks.............................................................. 8-28
8.3.2. Task 1: Enable WipManage to Receive Redirection Traps 8-29
8.3.3. Task 2: Add "Fixed" SPRs .................................................. 8-30
8.3.4. Task 3: Add AutoConnect SPRs ........................................ 8-32
8.3.5. Task 4: Define AutoDisconnect Interval ............................. 8-36
8.3.6. Task 5: Configure "Fixed" SPRs for Redirection ................ 8-37
8.3.7. Task 6: Power on or Reset SPR Device............................. 8-40
8.4. Redirecting Previously Redirected SPRs .......................................... 8-42
8.4.1. Summary of Tasks.............................................................. 8-43
8.4.2. Task 1: Add a "Fixed" SPR for Redirection ........................ 8-44
8.4.3. Task 2: Add an AutoConnect SPR ..................................... 8-46
8.4.4. Task 3: Redefine AutoConnect for Currently Redirected
SPR................................................................................... 8-48
8.4.5. Task 4: Reset the SPR Device ........................................... 8-52
8.5. Color-Coding of AutoConnect SPR Icons ......................................... 8-56
8.6. AutoConnect Trap Messages............................................................ 8-58
viii Airspan Networks Inc. 01040311-06

9. Configuring a Point-to-Point Radio Link................................................ 9-1

9.1. Overview ............................................................................................. 9-2
9.2. Summary of Tasks .............................................................................. 9-6
9.3. Task 1:Configure the PPR................................................................... 9-6
9.4. Task 2: Configure the SPR................................................................ 9-10
9.5. Task 3: Test the PPR-SPR Link ........................................................ 9-15
10. Configuring a Repeater Solution .......................................................... 10-1

10.1. Overview ......................................................................................... 10-2
10.2. Summary of Tasks .......................................................................... 10-4
10.3. Task 1: Add BS-1 and BS-2 ............................................................ 10-6
10.4. Task 2: Add BSR-1 and BSR-2 ....................................................... 10-8
10.5. Task 3: Define BSR-1’s Default Gateway ..................................... 10-12
10.6. Task 4: Define BSR-2’s Default Gateway ..................................... 10-14
10.7. Task 5: Add SPR-1 and SPR-2 ..................................................... 10-15
10.8. Task 6: Add Routes for SPRs behind BSR-2 toward SPR-1......... 10-19
10.9. Task 7: Define SPR-1’s Default Gateway ..................................... 10-22
10.10. Task 8: Add Routes for SPRs behind BSR-2 toward BSR-2....... 10-23
10.11. Task 9: Define SPR-2’s Default Gateway ................................... 10-26
11. Managing Bandwidth ............................................................................. 11-1

11.1. Overview ......................................................................................... 11-2
11.2. Configuring Asymmetric Bandwidth ................................................ 11-3
11.2.1. Summary of Tasks............................................................ 11-4
11.2.2. Task 1: Enable Asymmetric Bandwidth Policy ................. 11-4
11.2.3. Task 2: Define Downlink and Uplink CIR and MIR Values 11-6
12. Defining Static Routes ........................................................................... 12-1

12.1. Overview ......................................................................................... 12-1
12.2. Adding Static Routes to a BSR ....................................................... 12-2
12.2.1. Summary of Tasks............................................................ 12-3
01040311-06 Airspan Networks Inc. ix

12.2.2. Task 1: Add Static Route to BSR ..................................... 12-4

12.2.3. Task 2: Add Default Gateway to BSR .............................. 12-6
13. Defining Virtual Ports............................................................................. 13-1
14. Defining VLANs ...................................................................................... 14-1

14.1. Overview ......................................................................................... 14-2
14.1.1. Transparent Mode ............................................................ 14-3
14.1.2. Tagging Mode................................................................... 14-4
14.2. Defining VLANs for IP Routing ........................................................ 14-4
14.2.1. Defining Gateways per VLAN........................................... 14-4
14.2.1.1. Summary of Tasks ............................................. 14-6
14.2.1.2. Task 1: Enable Gateway per VLAN Mode ......... 14-6
14.2.1.3. Task 2: Reset the BSR ...................................... 14-8
14.2.1.4. Task 3: Define Gateway Addresses per VLAN .. 14-8
14.2.1.5. Task 4: Define SPR VLAN ID(s) ...................... 14-10
14.2.2. Defining BSR VLAN Policy and Management ................ 14-12
14.2.3. Defining SPR VLAN Policy and Management ................ 14-14
14.3. Defining VLANs for Transparent Bridging ..................................... 14-17
14.3.1. Defining BSR VLAN Policy and Management ................ 14-17
14.3.2. Defining SPR VLAN Policy and Management ................ 14-20
15. Defining Air Subnets.............................................................................. 15-1

15.1. Overview ......................................................................................... 15-2
15.2. Configuring Air Subnet Addresses for Private Networks................. 15-5
15.2.1. Summary of Tasks............................................................ 15-6
15.2.2. Task 1: Define BSR's Air Subnet using WipConfig........... 15-6
15.2.3. Task 2: Verify BSR's Air Subnet Address......................... 15-9
15.2.4. Task 3: Define SPR's Air Subnet using WipConfig......... 15-10
15.2.5. Task 4: Verify SPR's Air Subnet Address....................... 15-14
15.2.6. Task 5: Return PC's IP Settings for Connectivity with
BSR................................................................................. 15-16
x Airspan Networks Inc. 01040311-06

15.2.7. Task 6: Add BSR and SPR in WipManage..................... 15-16

15.2.8. Task 7: View Air Subnets in WipManage ....................... 15-16
16. Defining ASWipLL as a DHCP Relay Agent ......................................... 16-1

16.1. Overview ......................................................................................... 16-1
16.2. Defining ASWipLL as a DHCP Relay Agent.................................... 16-2
17. Defining PPPoE ...................................................................................... 17-1

17.1. Overview ......................................................................................... 17-2
17.2. Enabling PPPoE for BSR and Associated SPRs ............................ 17-4
17.2.1. Summary of Tasks............................................................ 17-4
17.2.2. Task 1: Select PPPoE Enabled Option for BSR ............... 17-4
17.2.3. Task 2: Reset the BSR ..................................................... 17-6
17.2.4. Task 3: Verify BSR in PPPoE Mode................................. 17-7
17.2.5. Task 4: Select PPPoE Enabled Option for SPRs ............. 17-8
17.2.6. Task 5: Reset the SPRs ................................................. 17-10
17.2.7. Task 6: Verify SPRs in PPPoE Mode ............................. 17-13
18. Configuring BSR Antenna ..................................................................... 18-1
19. Configuring Radio Transmit Power ...................................................... 19-1

19.1. Overview ......................................................................................... 19-2
19.2. Defining BSR Transmit (Tx) Power ................................................. 19-3
19.2.1. Summary of Tasks............................................................ 19-3
19.2.2. Task 1: Define the BSR Power Level ............................... 19-4
19.3. Configuring BSR Control over SPR Transmit Power ...................... 19-7
19.3.1. Summary of Tasks............................................................ 19-7
19.3.2. Task 1: Enable BSR Power Management for SPRs......... 19-8
19.3.3. Task 2: Reset the SPRs ................................................. 19-10
19.3.4. Task 3: Verify BSR Power Control is Enabled................ 19-12
01040311-06 Airspan Networks Inc. xi

20. Managing Frequency Tables ................................................................. 20-1

20.1. Overview ......................................................................................... 20-2
20.1.1. Considerations for Frequency Allocations ........................ 20-4
20.1.2. ROM Frequency Tables ................................................... 20-6
20.2. Defining NVRAM Frequency Table for BSR-to-SPRs Wireless
Communication............................................................................. 20-8
20.2.1. Summary of Tasks............................................................ 20-8
20.2.2. Task 1: Add Frequency Table for BSR............................. 20-9
20.2.3. Task 2: Add Frequency Table for SPR........................... 20-12
20.2.4. Task 3: Assign Identical Frequency Table to Multiple
SPRs............................................................................... 20-15
20.2.5. Task 4: Specify Operating Frequency Table ID.............. 20-18
20.2.6. Task 5: Reset the BSR ................................................... 20-19
21. Defining Synchronization ...................................................................... 21-1

21.1. Overview ......................................................................................... 21-2
21.2. Synchronizing a Base Station ......................................................... 21-4
21.2.1. Summary of Tasks............................................................ 21-5
21.2.2. Task 1: Enable GPS ......................................................... 21-6
21.2.3. Task 2: Reset BSDU ........................................................ 21-7
21.2.4. Task 3: Verify GPS Synchronization ................................ 21-8
21.2.5. Task 4: Define Synchronization for BSDUs ...................... 21-9
21.2.6. Task 5: Reset the BSDUs............................................... 21-12
21.2.7. Task 6: Verify BSDU Synchronization ............................ 21-14
21.2.8. Task 7: Enable BSR Synchronization............................. 21-16
21.2.9. Task 8: Reset BSRs ....................................................... 21-18
21.2.10. Task 9: Verify BSRs Synchronization........................... 21-20
xii Airspan Networks Inc. 01040311-06

22. Defining Transmission Rate.................................................................. 22-1

22.1. Overview ......................................................................................... 22-2
22.2. Defining Maximum Rate Mode ........................................................ 22-3
22.2.1. Summary of Tasks............................................................ 22-4
22.2.2. Task 1: Define Maximum Rate Mode ............................... 22-5
22.2.3. Task 2: Reset the SPRs/IDRs .......................................... 22-6
22.3. Defining Transmission Rate Options............................................. 22-10
23. Defining Security.................................................................................... 23-1

23.1. Overview ......................................................................................... 23-2
23.2. Defining Management Stations ....................................................... 23-3
23.3. Defining SNMP Read/Write Community Strings ............................. 23-4
23.3.1. Summary of Tasks............................................................ 23-5
23.3.2. Task 1: Define BSR's SNMP Read/Write Community
Strings............................................................................... 23-5
23.3.3. Task 2: Verify BSR's SNMP Read/Write Strings .............. 23-8
23.4. Defining Public-Key Encryptions ..................................................... 23-9
23.4.1. Summary of Tasks............................................................ 23-9
23.4.2. Task 1: Enable Encryption-Based Security .................... 23-10
23.4.4. Task 3: Define SPR's Private Key .................................. 23-12
23.4.5. Task 4: Reset the SPR ................................................... 23-13
23.5. Adding IP Filters ............................................................................ 23-14
23.5.1. Summary of Tasks.......................................................... 23-14
23.5.2. Task 1: Enable IP Filtering ............................................. 23-15
23.5.4. Task 3: Verify BSR in IP Filtering Mode ......................... 23-17
23.5.5. Task 4: Add BSR IP Filtering Rules................................ 23-18
23.5.6. Task 5: Enable IP Filtering for SPR ................................ 23-22
01040311-06 Airspan Networks Inc. xiii

23.5.7. Task 6: Reset the SPR ................................................... 23-23

23.5.8. Task 7: Add SPR IP Filter Rule ...................................... 23-23
23.6. Defining IntraComm Gateways ..................................................... 23-24
23.6.1. Summary of Tasks.......................................................... 23-25
23.6.2. Task 1: Select IntraComm Gateway Option ................... 23-26
23.6.4. Task 3: Define Gateway IP Address per SPR ................ 23-28
24. Defining Quality of Service.................................................................... 24-1

24.1. Overview ......................................................................................... 24-2
24.2. Defining QoS for Data ..................................................................... 24-5
24.3. Defining QoS for VoIP ..................................................................... 24-9
24.3.1. Summary of Tasks.......................................................... 24-10
24.3.2. Task 1: Define QoS for IP Addresses of SIP Server and
Softswitch........................................................................ 24-11
24.3.3. Task 2: Configure DiffServ Tagging for RGW ................ 24-14
24.3.4. Task 3: Map DiffServ Tags to ASWipLL Prioritization
Scheme........................................................................... 24-15
25. Managing Traps...................................................................................... 25-1

25.1. Overview ......................................................................................... 25-1
25.2. Defining Management Stations ....................................................... 25-2
25.3. Enabling Trap Display in WipManage ............................................. 25-4
25.4. Showing the Traps Pane ................................................................. 25-6
25.5. Viewing the Alarms Table................................................................ 25-7
25.6. Enabling Pop-up Notifications and Execution of Batch Files on
Trap Receipt ................................................................................. 25-8
25.7. Enabling/Disabling Receipt of Specific Traps................................ 25-10
26. Upgrading ASWipLL Database ............................................................. 26-1

26.1. Overview ......................................................................................... 26-1
26.2. Summary of Tasks .......................................................................... 26-2
26.3. Task 1: Install WipLL DB Upgrade .................................................. 26-3
xiv Airspan Networks Inc. 01040311-06

26.4. Task 2: Start WipLL DB Upgrade .................................................. 26-10

26.5. Task 3: Upgrade the ASWipLL Database ..................................... 26-11
26.6. Task 4: Compact the ASWipLL Database..................................... 26-15
27. Upgrading ASWipLL Devices................................................................ 27-1

27.1. Overview ......................................................................................... 27-2
27.2. Remote Upgrade using WipManage ............................................... 27-5
27.2.1. Upgrading Multiple SPRs ................................................. 27-6
27.2.2. Upgrading a Single BSR................................................. 27-13
27.3. Local Serial Upgrade using WipConfig.......................................... 27-20
27.4. Troubleshooting............................................................................. 27-29
28. Evaluating Link Quality.......................................................................... 28-1

28.1. Overview ......................................................................................... 28-1
28.2. RSSI Levels..................................................................................... 28-2
28.2.1. Measuring RSSI at SPR using WipConfig........................ 28-3
28.2.2. Measuring RSSI at BSR using WipManage ..................... 28-4
28.3. Carrier-to-Interference Ratio ........................................................... 28-5
28.3.1. Spectrum Analysis using WipConfig................................. 28-6
28.3.1.1. Accessing the Spectrum Analyzer ..................... 28-7
28.3.1.2. Setting up the Spectrum Analyzer ..................... 28-7
28.3.1.3. Starting the Spectrum Analyzer ......................... 28-8
28.3.1.4. Viewing Results ................................................. 28-9
28.4. Bit Error Rate (BER)...................................................................... 28-10
28.4.1. Measuring BER Using WipConfig................................... 28-11
28.4.2. Measuring BER Using WipManage ................................ 28-12
28.5. Generating Traffic to Measure Throughput ................................... 28-13
29. Troubleshooting ..................................................................................... 29-1

29.1. No PC-BSR Network Link ............................................................... 29-2
29.2. No BSR-SPR/IDR Air Link............................................................... 29-2
29.3. No PC-SPR Network Link ............................................................... 29-3
01040311-06 Airspan Networks Inc. xv

xvi Airspan Networks Inc. 01040311-06

About this Manual
This section discusses the purpose, targeted audience, references, organization, and
technical support for this manual.
Purpose
This manual provides step-by-step procedures for commissioning Airspan’s
ASWipLL system. These procedures include, for example:
Installation of ASWipLL configuration and management software
Initial configuration of ASWipLL devices
Advanced configurations such as configuring transparent bridging, IP routing,
AutoConnect, and frequency tables
Upgrade procedures
Troubleshooting
Targeted Audience
This manual is intended for the person who is responsible for commissioning the
ASWipLL system. This person should be familiar with working with Airspan’s
ASWipLL WipConfig and WipManage programs.
01040311-06 Airspan Networks Inc. xvii

Ab o u t t h i s M a n u a l Commissioning Manual
Referenced Documentation
The following documentation is referenced in some places in this manual:
WipManage User’s Guide: This manual assumes that you are familiar with
WipManage’s GUI. Airspan recommends that you refer to the WipManage
User’s Guide for descriptions on using WipManage.
WipConfig User’s Guide: This manual assumes that you are familiar with
WipConfig’s GUI. Airspan recommends that you refer to this manual when
performing initial configuration procedures.
ASWipLL Hardware Installation Guide: The manual describes serial
configurations of ASWipLL devices. Therefore, Airspan recommends that you
refer to the ASWipLL Hardware Installation Manual for detailed description of
connecting the cables for serial (or IP network) connections.
Organization of this Manual

This manual is organized into the following chapters:
Chapter 1, "Introduction": provides an overview of the ASWipLL system.
Chapter 2, "Installing ASWipLL Management Software": provides step-by-
step instructions for installing WipManage and WipConfig.
Chapter 3, "Initial Configuration": provides step-by-step instructions for
initializing BSDU, BSR/PPR, and SPR/IDR devices. In addition, this chapter
also describes the procedure for establishing a network link.
Chapter 4, "Establishing BSR-SPR Link in Router Mode": provides step-by-
step instructions for establishing communication link between the BSR/PPR and
SPR based on IP routing.
Chapter 5, "Establishing BSR-SPR Link in Bridge Mode": provides step-by-
step instructions for establishing communication link between the BSR/PPR and
SPR based on transparent bridging.
xviii Airspan Networks Inc. 01040311-06

Commissioning Manual Ab o u t t h i s M a n u a l
Chapter 6, "Changing Link from Router to Bridge Mode": provides step-by-

step instructions for changing the communication link between the BSR/PPR
and SPR from IP routing mode to transparent bridging mode.
Chapter 7, "Changing Link from Bridge to Router Mode": provides step-by-
step instructions for changing the communication link between the BSR/PPR
and SPR from transparent bridging mode to IP routing mode.
Chapter 8, "Establishing BSR-SPR Link with AutoConnect": provides step-
by-step instructions for establishing communication link between the BSR and
SPR/IDR using the ASWipLL AutoConnect feature.
Chapter 9, "Configuring a Point-to-Point Radio Link": provides step-by-step
instructions for establishing a point-to-point radio (PPR) link between the PPR
and SPR devices.
Chapter 10, "Configuring a Repeater Solution": provides step-by-step
instructions for configuring a repeater solution using a BSR-to-SPR back-to-
back Ethernet connectivity.
Chapter 11, "Managing Bandwidth": provides step-by-step instructions for
defining bandwidth such as Maximum Information Rate (MIR) and Committed
Information Rate (CIR).
Chapter 12, "Defining Static Routes": provides step-by-step instructions for
defining static routes such as from BSR to SPR, and default gateways.
Chapter 13, "Defining Virtual Ports": provides step-by-step instructions for
defining virtual interface ports (i.e. IP addresses).
Chapter 14, "Defining VLANs": provides step-by-step instructions for defining
VLANs for the ASWipLL devices.
Chapter 15, "Defining Air Subnets": provides step-by-step instructions for
defining subnet addresses for the virtual ports of the ASWipLL radios
interfacing with the wireless communication path.
Chapter 16, "Defining ASWipLL as a DHCP Relay Agent": provides a step-
by-step instruction for defining ASWipLL as a DHCP relay agent.
01040311-06 Airspan Networks Inc. xix

Chapter 17, "Defining PPPoE": provides step-by-step instructions for defining

Point-to-Point Protocol over Ethernet (PPPoE).
Chapter 18, "Configuring BSR Antenna": provides a step-by-step instruction
for configuring the BSR/PPR antenna for antenna diversity.
Chapter 19, "Configuring Radio Transmit Power": provides step-by-step
instructions for configuring transmit power levels for the ASWipLL devices.
Chapter 20, "Managing Frequency Tables": provides step-by-step instructions
for defining frequency tables used in wireless communicate between the
BSR/PPR and SPR.
Chapter 21, "Defining Synchronization": provides step-by-step instructions for
configuring synchronization at an ASWipLL Base Station.
Chapter 22, "Defining Transmission Rate": provides step-by-step instructions
for defining transmission rate in the ASWipLL system.
Chapter 23, "Defining Security": provides step-by-step instructions for defining
security settings such as management stations, public-key encryptions, and IP
filters.
Chapter 24, "Defining Quality of Service": provides step-by-step instructions
for configuring Quality of Service for data and VoIP traffic.
Chapter 25, "Managing Traps": provides step-by-step instructions for receiving
traps in WipManage.
Chapter 26, "Upgrading ASWipLL Database": provides step-by-step
instructions for upgrading the ASWipLL database using WipLL DB Upgrade.
Chapter 27, "Upgrading ASWipLL Devices": provides step-by-step
instructions for upgrading ASWipLL devices.
Chapter 28, "Evaluating Link Quality": provides step-by-step instructions on
evaluating the BSR-SPR link.
Chapter 29, "Troubleshooting": provides solutions to possible problems that
you might encounter when managing and configuring the ASWipLL network.
xx Airspan Networks Inc. 01040311-06

Commissioning Manual Ab o u t t h i s M a n u a l
Typographical Conventions
This manual uses the following typographical conventions:
Convention Meaning Example
Bold Command and menu names, Click the Next button.

icons, buttons, and fields
Bold Courier New ASCII commands At the DOS prompt,
type ipconfig
Words in parenthesis Messages that are displayed in "Download Complete"
the GUI.
Note that provides useful
information
Customer Service
For service and support for your ASWipLL system, contact your regional Airspan
representative, or Airspan’s Technical Assistance Center (TAC) at:
E-mail: WipLL.tech_support@Airspan.com
Boca Raton Call Center: (+1)-561-893-8679
Hotline (only for emergencies): (+972)-3-9777 555
01040311-06 Airspan Networks Inc. xxi

xxii Airspan Networks Inc. 01040311-06

1
Introduction
Airspan’s ASWipLL system provides a low-cost, high-performance point-to-
multipoint IP-based Broadband Fixed Wireless (BFW) Access solution. ASWipLL
provides wireless local-loop (last-mile) connectivity designed to deliver high-speed
data, Voice over IP (VoIP), and multimedia services to residential, SOHO (small
office/home office), and SME (small medium enterprise). ASWipLL offers service
providers an integrated access solution, providing quick-to-market deployment and
low-market entry cost for broadband services.
ASWipLL operates in the licensed band (700 MHz, 925 MHz, 1.5 GHz, 2.3 GHz,
2.5 GHz Multichannel Multipoint Distribution Services - MMDS, 2.8 GHz, and 3.x
GHz - ranging from 3.3 to 3.8 GHz), and unlicensed band (900 MHz, 2.4 GHz ISM,
and 5.8 GHz).
Each ASWipLL Base Station, at maximum configuration, supports up to 3,024
subscribers, providing connectivity speeds of up to 4 Mbps.
ASWipLL enables interconnection with the Public Switched Telephone Network
(PSTN) by the use of an IP-to-PSTN gateway. ASWipLL provides VoIP by its
interoperability with a wide range of third-party products such as residential
gateways (RGW), access gateways, gatekeepers, and softswitches.
ASWipLL utilizes air protocol technology for wireless packet switching using
Frequency Hopping technology. ASWipLL's in-house Preemptive Polling Multiple
Access (PPMA) Air MAC protocol technology, which recognizes transmission type
and allocates bandwidth, is highly efficient—80% throughput (e.g., 80% of 4 Mbps
= 3.2 Mbps net capacity)—allowing multiple concurrent subscribers to utilize
bandwidth.
01040311-06 Airspan Networks Inc. 1-1

Introduction Commissioning Manual
ASWipLL provides bandwidth management by supporting both asymmetric and

aggregated Committed Information Rate (CIR) and Maximum Information Rate
(MIR), guaranteeing bandwidth levels to subscribers. In asymmetric CIR/MIR,
different values are defined for uplink and downlink traffic: in aggregated CIR/MIR,
values are defined as the sum of the uplink and downlink traffic.
ASWipLL supports VLANs and VPNs based on IEEE 802.1Q/p. ASWipLL
supports IP routing and PPPoE bridging, as well as transparent bridging.
ASWipLL provides embedded security features such as IP (packet) filtering based
on addresses, protocols, and applications.
The ASWipLL system provides SNMP-based management, allowing remote and
local management, configuration, and monitoring of ASWipLL equipment.
1.1. Main Features

The ASWipLL system provides the following main features:
Low initial investment, maximum return on investment (ROI)
Packet-based air interface supporting high speed data, VoIP, and multimedia
services
Modular architecture with flexible deployment architectures
4 Mbps (3.2 Mbps net) per sector—up to 24 sectors per Base Station
Compact, integrated design allowing easy and quick deployment
Advanced Quality of Service (QoS)
Simultaneous support of IP routing and PPPoE bridging
Supports transparent bridging, allowing easy IP addressing schemes
Bandwidth management: aggregated and asymmetric CIR and MIR
Supports 802.1Q/p for VLANs/VPNs and end-to-end QoS

Commissioning Manual Introduction
Provides automatic connection and configuration of first-time powered-on,

unconfigured subscriber devices
Allows redirecting subscriber devices to connect to a different Base Station radio
Supports configuration files, allowing the same configuration settings to be
applied to multiple ASWipLL devices
Base Station (i.e., BSR) redundancy using ASWipLL’s AutoConnect feature
Power redundancy when using the BSPS unit
Supports local and remote SNMP-based management, providing an intuitive
GUI for easy management

1.2. Customer Benefits

The ASWipLL system offers the following customer benefits and advantages over
competitors:
No IF or RF cables required for indoor unit-to-outdoor unit (IDU-to-ODU)
connectivity. Instead of IF/RF cables, ASWipLL uses standard CAT-5 Ethernet
cables, providing cost-effective and easy installation.
Scalability and modular Base Station architecture, allowing customers to add
equipment when needed, thereby, allowing low initial cost entry and pay-as-you-
grow strategy. Unlike competitors, the ASWipLL Base Station is not a chassis-
based design, and, therefore, provides flexibility and space-saving at Base
Stations.
ASWipLL's open architecture allows interoperability with multi-vendor products
such as residential gateways (RGW), access gateways, gatekeepers, and
softswitches, thereby, operating seamlessly in multi-vendor environments.
ASWipLL’s proprietary PPMA Air MAC protocol is highly efficient—80%
throughput—allowing multiple concurrent subscribers to utilize bandwidth
without network degradation (from collisions and high BER).
Long-distance radio coverage.
ASWipLL is both an IP router and a PPPoE bridge.
Supports transparent bridging for easy implementation of IP addressing schemes.
ASWipLL’s IP routing provides efficiency and eliminates the need for additional
hardware.
Enhanced QoS based on IP addresses, protocols, and applications.
End-to-end QoS based on DiffServ/TOS and 802.1p.
Quick-and-easy installation and configuration using ASWipLL's AutoConnect
feature.

Embedded security features such as IP (packet) filtering based on addresses,

protocols, and applications.
Rich networking packages such as 802.1Q/p VLANs/VPNs.
1.3. System Architecture

The ASWipLL system architecture is composed of the following three basic areas:
Base Station site: consists of ASWipLL access units that interface between the
provider’s backbone and the ASWipLL subscriber sites.
Subscriber site: consists of ASWipLL customer premises equipment (CPE) that
interfaces between the Base Station and the subscriber’s network.
Network management tools: consists mainly of Windows- and SNMP-based
programs, providing fault, configuration, performance, and security
management.

Figure 1-1 displays a block diagram of the main areas of the ASWipLL system.
Figure 1-1: ASWipLL System Architecture

1.3.1. Base Station Site

The ASWipLL Base Station interfaces between the subscriber sites and the service
provider's backbone, providing subscribers with high-speed data, Internet, and VoIP
services.
The ASWipLL Base Station is comprised of the following units (some optional):
Base Station Radio (BSR):
The BSR is an outdoor radio unit, typically mounted on a pole or wall, involved
in providing a wireless link between the Base Station and subscribers. The
standard BSR provides 60-degree radio coverage, serving up to 126 subscribers
in a sector.
The BSR is available in various models that either provide built-in antennas or
N-type ports for attaching a third-party antenna(s) for increasing radio coverage
or providing dual antenna diversity.
For Base Stations consisting of multiple BSRs, the BSRs connect to the
ASWipLL Base Station Distribution Unit (BSDU), which provides the interface
to the provider’s backbone, and power. For a Base Station consisting of a single
BSR, the BSR is typically powered and connected to the provider’s backbone by
the ASWipLL Subscriber Data Adapter (SDA).
Point-to-Point Radio (PPR):
The PPR is similar to the BSR, but implemented in a point-to-point radio
application, providing wireless communication with a single remote subscriber
(i.e. ASWipLL Subscriber Premises Radio).
Base Station Distribution Unit (BSDU):
The BSDU is an Ethernet switch implemented at Base Stations consisting of
multiple BSRs. The BSDU provides 100Base-T interface between the BSRs and
the provider's backbone. The BSDU is also responsible for providing BSRs with
–48 VDC power supply and frequency hop synchronization for multiple BSDUs
and BSRs.

The BSDU is installed indoors in a standard 19-inch cabinet, connecting to the

BSRs by standard CAT-5 cables. Each BSDU can service a maximum of six
BSRs. In addition, up to four BSDUs can be daisy-chained at a Base Station,
supporting up to 24 BSRs. Therefore, a Base Station at maximum configuration
can serve up to 3,024 subscribers (i.e. 24 BSRs * 126 subscribers).
Subscriber Data Adapter (SDA):
The SDA is typically implemented at the subscriber site; however, it is also
implemented at Base Stations consisting of a single BSR. The SDA provides the
BSR with -48 VDC power supply and Ethernet interface to the provider's
backbone.
The SDA is installed indoors and connected to the BSR by a CAT-5 cable.
SDA-1/48V:
Designed for use when available voltage is 48VDC rather than AC power,
providing –48VDC power output, and used when no synchronization is needed
(i.e. in licensed bands). It also provides Ethernet connectivity between BSR/PPR
radio and the indoor LAN switch or router.
In some scenarios such as repeater applications, it may be implemented to power
the SPR.
Base Station Power Supply (BSPS):
The BSPS is an optional unit that provides the ASWipLL Base Station with –48
VDC power supply and power redundancy. The BSPS is installed at the Base
Station site in a standard 19-inch cabinet. The BSPS connects to, and services a
maximum of four BSDUs.
Global Positioning System (GPS) antenna:
The GPS antenna is a rugged, self-contained GPS receiver and antenna that
receives a universal GPS satellite clock signal. The GPS is an optional unit that
connects to the BSDU. The GPS synchronizes frequency hopping of multiple
Base Stations ensuring that the entire ASWipLL network operates with the same
clock based on a universal satellite clock signal, and, thereby, eliminating radio
frequency ghosting effects.

Figure 1-2 shows a fully populated ASWipLL Base Station at maximum

configuration (i.e. 24 BSRs, 4 BSDUs, 1 BSPS, and 1 GPS).
BSR BSR BSR

BSR BSR BSR
BSR BSR BSR
BSR BSR BSR
BSR BSR BSR
BSR BSR BSR
BSR BSR BSR
BSR BSR BSR
BSDU
BSDU -48 VDC
BSDU
GPS BSDU
100BaseT BSPS
Interface unit
(e.g. router, switch)
Backbone
(IP, ATM,FR, MPLS)
Figure 1-2: ASWipLL Base Station at maximum configuration

1.3.2. Subscriber Site

The ASWipLL subscriber site is located at the subscriber's premises. The ASWipLL
subscriber site consists of a radio transceiver that receives and transmits signals from
and to the Base Station. The radio transceiver provides the subscriber with high-
speed data access, Internet access, and VoIP at up to 4 Mbps. The ASWipLL radios
interface to the subscriber's Ethernet network either through a hub or switch, or
directly, depending on the ASWipLL radio model.
Note: For VoIP support, Airspan can provide a third-party residential gateway
(RGW). The RGW typically provides two POTS ports for telephony, a 10BaseT
LAN port for subscriber PC/network, and a 10BaseT port for connecting to the
SDA or IDR (depending on subscriber site configuration).
The ASWipLL system provides two different subscriber site configurations:

Outdoor radio with indoor Ethernet switch/hub
Indoor radio only
1.3.2.1. Outdoor Radio with Indoor Ethernet Switch/Hub

The outdoor radio with indoor Ethernet switch/hub configuration consists of the
ASWipLL Subscriber Premises Radio (SPR) and the ASWipLL Subscriber Data
Adapter (SDA), respectively. These two devices are described below:
Subscriber Premises Radio (SPR):
The SPR is the outdoor radio transceiver that provides a wireless link between
the subscriber’s network and the Base Station.
The SPR connects to the subscriber’s network through the ASWipLL SDA, an
Ethernet hub or switch (depending on SDA model). The SDA provides the SPR
with DC power, lightening protection, and Ethernet (10Base-T and/or 100Base-
T) interface to the subscriber’s PCs/network (up to four PCs depending on SDA
model). The SPR connects to the SDA by a standard CAT-5 cable.
The SPR is mounted outside, typically on an external wall or on a pole to
provide a clear line-of-site with the Base Station.

The SPR is available in various models that either provide built-in antennas or
N-type ports for attaching a third-party antenna for increasing radio coverage
(antenna gain).
Subscriber Data Adapter (SDA):
The SDA is a switch or hub (depending on model), providing the SPR with -48
VDC power supply (from AC power outlet), lightening protection, and
10/100Base-T interface to the subscriber’s PCs/network.
The SDA is installed indoors and can be mounted on a wall or simply placed on
a desktop. The SDA connects to the SPR by a standard CAT-5 cable.
The SDA is available in the following models:
SDA-1: hub that provides one 10BaseT interface to the subscriber’s
computer or LAN network if connected to another hub or a switch.
SDA-1/DC: adapter that provides Ethernet (one 10BaseT) and regulated
–48 VDC power to the SPR. This model can be powered from a voltage of
10 – 52 VDC (e.g. from a solar panel that typically provides 12 VDC). This
model is typically implemented in mobile wireless applications, e.g. in a car
or truck.
SDA-4H: hub that provides four 10BaseT interfaces to the subscriber’s
computers and/or networks. One of the 10BaseT ports provides crossover
cabling for interfacing to another hub or LAN switch. Alternatively, it may
be connected to another PC via a crossed Ethernet cable.
SDA-4S: integrated LAN switches, providing four 10/100BaseT interfaces to
the subscriber’s PCs/network. The ports of the SDA-4S models support Auto
Negotiation, allowing automatic configuration for the highest possible speed
link: 10BaseT or 100BaseT, and Full Duplex or Half Duplex mode. In other
words, the speed of the connected device (e.g., a PC) determines the speed at
which packets are transmitted through the SDA-4S port. For example, if the
device to which the port is connected is running at 100 Mbps, the port
connection will transmit packets at 100 Mbps. If the device to which the port
is connected is running at 10 Mbps, the port connection will transmit packets
at 10 Mbps.

The SDA-4S ports also support automatic MDI/MDI-X crossover detection,

allowing connection of straight-through or crossover CAT-5 cables to any
port.
The SDA-4S is available in the following models:
− SDA-4S (standard): standard integrated LAN switch, providing four
10/100BaseT interfaces to the subscriber’s computers. This model is
ideal for SOHO implementation.
− SDA-4S/VL: provides VLANs between ports and the SPR, ensuring
privacy between LAN users of the different ports. For example, all users
connected to Port 1 do not “see” users connected to Port 2. This model is
ideal for multi-tenant (VLAN security) implementation.
− SDA-4S/VLtag: ideal for multi-tenant applications where traffic
engineering and privacy is required. SDA-4S/VLtag assigns a specific
VLAN ID to traffic, based on the SDA-4S/Vltag port at which the traffic
arrives. The VLAN IDs are fixed (since SDA-4S/VLtag is not user
configurable). SPR converts the four VLAN IDs tagged by SDA-
4S/VLtag to four VLAN IDs configured through ASWipLL’s network
management system (WipManage). The tag conversion is performed by
SPR before sending the traffic to the air and vice versa when coming
from the air.
− SDA-4S/1H3L: provides a high priority port (left-most port) for VoIP
traffic.
− SDA-4S/VL/1H3L: combines the functionality of the SDA-4S/VL and
SDA-4S/1H3L models (i.e., VLAN for each port and a high priority port
for VoIP).

Figure 1-3 displays a typical setup at a subscriber site implementing an ASWipLL

outdoor radio unit (SPR) and an ASWipLL indoor Ethernet switch /hub (SDA).
Figure 1-3: Subscriber site with SPR and SDA units (optional RGW)

1.3.2.2. Indoor Radio Unit Only

The indoor radio unit configuration consists of the ASWipLL Indoor Data Radio
(IDR). The IDR combines the functionality of the SPR and SDA, functioning as a
transceiver and a hub. The IDR provides one 10Base-T Ethernet interface to the
subscriber's network. The IDR receives its power from a separate power supply unit
(AC-DC power adapter).
The IDR provides a built-in antenna and a TNC-type port for attaching a third-party
antenna for increasing radio coverage (antenna gain) and ensuring line-of-site with
the Base Station.
The IDR with a built-in antenna is typically mounted on an interior wall or on a
desktop with line-of-site with the Base Station. The antenna of the IDR model with
an external antenna is typically mounted outdoors to provide line-of-site with the
Base Station.
The IDR can be used for data and voice transmissions. In the case of voice, the IDR
uses a third-party RGW to interface with the subscriber’s IP phone. Figure 1-4
displays a typical setup for data and voice at a subscriber site implementing an IDR.
Figure 1-4: Subscriber site with IDR (optional third-party external antenna and RGW)

1.3.3. Network Management Tools

Airspan’s ASWipLL system provides comprehensive set of state-of-the-art, use-
friendly configuration and management tools for the ASWipLL system. These
management tools provide fault, configuration, performance, and security
management for the ASWipLL system.
The ASWipLL system provides the following management tools:
WipManage™: Windows-based program, functioning as the ASWipLL
network (element) management system (NMS) providing fault, configuration,
performance, and security management.
WipManage is based on Simple Network Management Protocol (SNMP),
providing both local and remote network management through SNMP Get, Set,
and Trap commands.
WipConfig™: Windows-based program, providing serial initial configuration
(e.g. IP addresses) of the ASWipLL devices, used typically at the factory, or
during installation. WipConfig also provides received signal strength indication
(RSSI) for subscriber radios allowing accurate device orientation and positioning
for optimal reception with Base Station. In addition, WipConfig provides a
license-dependant Spectrum Analyzer that scans a user-defined frequency range,
measuring RSSI values for each frequency, and therefore, allowing the operator
to choose “clean” frequencies for operating the ASWipLL system.
WipConfig PDA™: designed to run on a personal digital assistant (PDA),
providing an alternative tool to WipConfig (described above) for performing
initial configuration.
WipAD™: Windows-based program, providing quick-and-easy automatic
simultaneous downloading of software version files to multiple ASWipLL
devices.

1.4. Applications
The following subsections provide examples of typical ASWipLL applications.
1.4.1. Broadband Data Access

In a non-ASWipLL environment, using a standard PSTN modem in circuit-switched
networks, subscribers are limited to 56 Kbps of throughput, and in most cases, to
28.8 Kbps. From the provider's perspective, once a subscriber has dialed up with a
PSTN modem, a full channel is occupied for as long as the session lasts.
In contrast, ASWipLL subscribers are limited only by their own configuration, with
a maximum of 4 Mbps—70 times faster than the fastest PSTN modem. In addition,
subscribers do not necessarily consume more bandwidth from the provider, since
bandwidth is used only when a data packet is transmitted.
These characteristics of ASWipLL make it suitable for providing data access to
subscribers while maintaining best usage of bandwidth and capacity.

1.4.2. High Speed Internet Access

One of the advantages of ASWipLL is the fact that subscribers are "always on"
Internet. This means that there is no dialing process and no need for the hassle
involved with dialup access. Subscribers need only to open their Web browser or e-
mail to be instantly connected.
ASWipLL can also distinguish between applications and subscribers, thus, enabling
the provider to provide different class of service to subscribers. For example, it can
provide different services to Web browsing and e-mail by prioritizing Web browsing
for ensuring best "Internet experience".
Figure 1-5 shows a typical ASWipLL application for high-speed Internet access.
Figure 1-5: Typical ASWipLL Application for High-Speed Internet Access

1.4.3. Voice over IP

The ASWipLL system enables providers the flexibility of migration from a data-
only network to an integrated Voice-over-IP and data network. The ASWipLL voice
solution provides interoperability with any IP-to-PSTN network gateway. The use of
the IP-to-PSTN gateway allows providers seamless PSTN connectivity such as SS7
(signaling network), G3-303, and V5.2 over E1, allowing deployment in multi-
national markets.
Figure 1-6 shows a typical ASWipLL application for VoIP.
Figure 1-6: Typical ASWipLL Application for VoIP

1.4.4. Traffic Engineering in Multi-Tenant Application

The ASWipLL system provides high-speed wireless broadband (e.g., Internet)
access for multiple-tenant units (MTU). ASWipLL provides a dedicated high-speed
connection to the building, and then distributes that bandwidth among the tenants,
providing them with a private, secure connection. ASWipLL’s MTU solution
supports both data and VoIP. When VoIP is required, a third-party VoIP gateway is
implemented.
1.4.4.1. VLAN Tagging

The ASWipLL system provides VLAN tagging and traffic engineering in MTU
applications in networks that connect to MPLS, ATM, or Frame Relay backbones.
The ASWipLL hardware responsible for providing these MTU solutions is the SDA-
4S/VLtag Ethernet switch serving up to four tenants, or an external integrated LAN
switch (connected to the SDA-4S/VLtag) serving more than four tenants (e.g., 24
ports).
ASWipLL's SDA-4S/VLtag assigns a different VLAN ID (fixed) to traffic from
each of its four ports. ASWipLL’s SPR converts these four VLAN IDs, tagged by
SDA-4S/VLtag, to four VLAN IDs configured by ASWipLL’s NMS (WipManage).
SPR performs this tag conversion before sending traffic to the air, and when
receiving traffic from the air. This VLAN conversion is applicable only when SPR is
used as a transparent bridge.

Figure 1-7 shows an example of how MTU works in an ATM environment.
Figure 1-7: Multi-tenant solution (i.e., multiple VLANs) in an ATM environment

1.4.4.2. Without VLAN Tagging

The ASWipLL system also provides regular VLAN support (without VLAN
tagging), providing privacy between tenants in MTU applications. The ASWipLL
hardware responsible for providing these MTU solutions is the SDA-4S/VL Ethernet
switch serving up to four tenants, or an external third-party integrated LAN switch
(connected to the SDA-4S/VL) serving more than four tenants (e.g., 24 ports). The
SDA-4S/VL provides VLANs between its ports and the SPR, ensuring privacy
between users of different ports. For example, all users connected to Port 1 do not
“see” users connected to Port 2.
Figure 1-8: Multi-tenant solution without VLAN tagging, but ensuring privacy
between tenants

1.4.5. Repeater Solution

ASWipLL units can be used to provide repeater functionality. This is implemented
in scenarios where the BSR needs to be “extended” to remote subscriber sites that
are blocked by obstacles such as trees, hills, and other typical line-of-sight
obstructions or that the BSR-SPR (or BSR-IDR) transmission is out-of-range.
Back-to-back Ethernet connectivity of a BSR with an SPR/IDR provides the repeater
capability, as illustrated in Figure 1-9.
Figure 1-9: ASWipLL repeater solution

In Figure 1-9, BSR A is part of an ASWipLL Base Station connected to the service
provider’s backbone. BSR A serves multiple SPRs, marked as SPR Ai. Two SPRs—
SPR B1 and SPR B2—cannot communicate directly with the Base Station.
Therefore, an SPR acts as a repeater by connecting back-to-back with BSR B (SPR
B1 and B2 are served by BSR B).
Notes:
- Careful planning is required to cope with issues such as interferences and
delay that are introduced by the repeater solution. For example, if the system is
used as a frequency hopping system, GPS may be required at each base
station.
- Space and frequency isolation between the “repeater SPR” and BSR B is
required.
- Bandwidth management should be calculated to support the “repeater
bandwidth”.
- IP addressing and routing tables should be configured to support the
repeater solution.


2
Installing ASWipLL
Management Software
This chapter describes the procedures for installing software for configuring and
managing the ASWipLL system. This chapter includes the following sections:
System Requirements
Installing WipConfig
Installing WipManage

I n s t a l l i n g AS W i p L L M a n a g e m e n t S o f tw a r e Commissioning Manual
2.1. System Requirements

Before installing WipManage and WipConfig programs, ensure that the following
system requirements are fulfilled:
Hardware requirements:
CPU 400 MHz minimum (recommended 1,000 MHz or more)
RAM 256 MB (recommended 512 MB or more)
Display adapter memory 8 MB
Graphics 1024 x 768 (recommended 1024 x 768 or more)
Minimum free hard disk space 500 MB (recommended 2 GB or more)
Network adapter 100 Mbps
Software requirements - operating system:
Microsoft™ Windows™ NT 4 work station (English only) SP3.0 or later
Microsoft™ Windows™ 2000 Professional
Microsoft™ Windows™ XP Professional

Commissioning Manual I n s t a l l i n g AS W i p L L M a n a g e m e n t S o f t w a r e
2.2. Installing WipConfig

The WipConfig program is supplied on a CD-ROM, and requires you to install it on
a Windows-based PC. It is recommended to quit all running programs before
installing WipConfig.
To install WipConfig:
1. Insert the WipConfig CD in your CD-ROM drive.
2. On the Windows taskbar, click Start, and then choose Run.
3. Type D:\WIPCONFIG.EXE (where D is the letter of your CD-ROM drive
letter).
4. Click OK.
The windows installation wizard will now take you through the following setup
procedure.

5. Click Next.

6. To accept the default destination folder for installing WipConfig, click Next.

7. Leave “Airspan” as the Program Manager group, and then click Next.

8. Enter your customer key number, if relevant, and then click Next.

9. Click Next to begin the installation.

When WipConfig is successfully installed, the following appears:

10. Click Finish to complete the installation. The WipConfig shortcut icon is
automatically created and placed on your desktop.

2.3. Installing WipManage

The WipManage program is supplied on a CD-ROM, and requires you to install it
on a Windows-based PC. It is recommended to quit all running programs before
installing WipManage.
To install WipManage:
1. Insert the WipManage CD into your CD-ROM drive.
2. On the Window’s taskbar, click Start, and then choose Run.
3. Browse the WipManage CD that is in your CD-ROM drive, and then double-
click the “wipmng.exe” file.
The installation wizard will now take you through the following setup procedure.

5. Click Next to agree to the terms of the license agreement and continue with the
setup.

6. Click Next to install WipManage into the directory C:\WipMng.

7. Click Next to add WipManage to the “Airspan” Program Manager Group.

8. If Microsoft Access is not installed on your workstation, select the Add MS-
Access ODBC Drivers check box.
Select the Add Data Source check box if you are performing a first-time
installation of WipManage, and then click Next.

9. Enter the Customer Key to continue the installation, alternatively, leave the
Customer Key field empty, and click Next to continue.

10. Click Next to begin installing WipManage.

If you selected the Add Data Source check box in Step 8, the ODBC Microsoft
Access Setup dialog box appears, as displayed below.
In the ODBC Microsoft Access Setup dialog box, accept the settings, and then
click OK. The WipManage database WiplldB.mdb file is created in the
directory C:\WipMng\WiplldB.mdb.

A progress bar indicates the status of the WipManage installation process, as

displayed below.
When WipManage installation has completed, the Installation Complete dialog

box appears, as displayed below.

11. Click Finish to complete the installation. The WipManage shortcut icon is
placed on your desktop:
Note: If your network has a firewall, to enable WipManage to manage the

devices, you need to "open" the ports concerned with SNMP traffic. For
example, if WipManage is located inside the firewall and the ASWipLL devices
are located outside the firewall, you need to open the outbound UDP port 161
(for SNMP Get and Set) and the inbound UDP port 161 (for receiving SNMP
traps).

3
Initial Configuration
This chapter describes the procedures for initial configuration of the ASWipLL
devices using WipConfig.
This chapter includes the following sections:
Overview
Initial Serial Configuration
Summary of Tasks
Task 1: Start WipConfig
Task 2: Initialize BSDU
Task 3: Initialize BSR
Task 4: Initialize SPR
Establishing a Network Connection
Summary of Tasks
Task 1: Configure PC’s IP Address
Task 2: Connect WipConfig to the Device
Note: In this chapter, BSR procedures are also applicable for PPR devices
and SPR procedures are also applicable for IDR devices.

Initial Configuration Commissioning Manual
3.1. Overview
Before you can manage the ASWipLL devices (BSR, SPR, and BSDU) using the
ASWipLL network management system (i.e. WipManage), you need to define
certain initial network, management, and radio frequency (RF) parameters. These
initial configuration parameters include the following:
IP address (of BSR, SPR, and BSDU)
Subnet address (of BSR, SPR, and BSDU)
SPR's index number in the BSR
BSR's Air MAC address
Frequency table ID (for BSR-SPR wireless communication)
After you initialize the ASWipLL devices with these configuration parameters, you
can manage them remotely using WipManage or WipConfig through an IP network
connection.
Initial configuration is performed using ASWipLL’s WipConfig program (or the
WipConfig PDA application, which runs on a Personal Digital Assistance device --
refer to the WipConfig PDA User's Guide). The initial configuration is performed
through a serial communication mode by connecting the ASWipLL device to the
serial port (i.e. COM) of the PC running WipConfig.
In general, to successfully establish an air and a network link between the BSR and
SPRs, you must ensure the following:
Correct IP and subnet addresses are configured (according to your network's
addressing scheme)
Same frequency table ID is configured for the BSR and the SPRs
Same maximum transmission rate mode is configured for the BSR and SPRs
Correct BSR's Air MAC address is configured for the BSR
Correct BSR's Air MAC address is assigned to the SPR

Commissioning Manual Initial Configuration
The table below lists the ASWipLL main default settings.
Table 3-1: ASWipLL device default settings

Parameter Default value
IP addresses:
• BSR • 10.0.0.10
• SPR • 10.0.0.20
• BSDU • 10.0.0.5
Subnet mask 255.255.255.240
Get Community Public
Set Community Private
Default gateway 0.0.0.0
Air subnet address According RFC 1918 (i.e. ranging from 192.168.0.0)
Mode (router/bridge) Router
Note: For a detailed description of connecting serial cables between the PC

running WipConfig and the ASWipLL device, refer to the ASWipLL Hardware
Installation Guide.

3.2. Initial Serial Configuration

The following subsections describe the tasks for performing initial configuration on
the ASWipLL devices through a serial communication mode using WipConfig. For
clarity, the procedures described are based on the configuration displayed in the
figure below:
Figure 3-1: Configuration setup example (IP routing mode)

3.2.1. Summary of Tasks

The flowchart in Figure 3-2 displays the tasks for performing initial configuration of
your ASWipLL devices.
Figure 3-2: Flowchart for performing initial ASWipLL device configuration

3.2.2. Task 1: Start WipConfig

Initial configuration is performed using WipConfig. For a detailed explanation on
installing WipConfig, see Chapter 2, "Installing ASWipLL Management Software".
To start WipConfig:
1. From the Windows Start menu, point to Programs, point to Airspan, and then
click WipConfig.
-Or-
On your desktop, double-click the WipConfig shortcut icon.
The Login WipConfig dialog box appears, as displayed below.
Figure 3-3: Login WipConfig dialog box
2. In the Name field, enter the login name (default is "Admin").

3. In the Password field, enter your password (default is "Wipll").
Note: The login values are case sensitive. The default login name and
password can be changed once you have logged into WipConfig (refer to the
ASWipLL WipConfig User’s Guide).

4. Click OK.
WipConfig starts and displays the WipConfig window showing the SPR
Configuration pane, as displayed in the following figure:
Figure 3-4: WipConfig window

3.2.3. Task 2: Initialize BSDU

The following procedure describes BSDU initial configuration.
To perform BSDU initial configuration:
1. Ensure the BSDU is connected through serial cabling to the PC running
WipConfig.
2. In the Communication group, select the Serial option.
3. Click the Connect button.
WipConfig connects to the BSDU device, displaying the BSDU Configuration
pane:

Figure 3-5: WipConfig connected to BSDU (BSDU Configuration pane)

4. Apply factory defaults to the BSDU by performing the following:
a. On the toolbar, click the Set Factory Default button.

A Warning message box appears.
Figure 3-6: Warning message box for setting defaults
b. Click Yes to confirm applying factory defaults to the device.

A Warning message box appears, requesting you to confirm device reset.
Figure 3-7: Warning message box for resetting device
c. Click Yes to reset the device with default settings.

WipConfig applies default settings to the BSDU.
5. In the Network Configuration group, enter the following fields:
Eth IP Address: BSDU’s IP address (e.g. 10.0.0.5)
Eth Subnet Mask: BSDU’s subnet mask address (e.g. 255.255.255.240)
Default Gateway: BSDU’s default gateway’s IP address, if relevant

6. In the RF Configuration group, in the Freq Table Size field, enter the number
of frequencies listed in the frequency table used by the BSR (valid range is 1
through 96), e.g. 23. This is used by the BSDU for synchronizing BSRs and
BSDUs.
7. On the toolbar, click the Write button.
8. On the toolbar, click the Reset button to reset the BSDU.

Figure 3-8: Warning message box for resetting BSDU
9. Click Yes to reset the device.
Notes: The BSR Power Control group contains six BSR check boxes, each
corresponding to the BSDU's rear panel BSR ports for connecting to the SPRs.
In the example configuration, all the ports are connected to BSRs.

3.2.4. Task 3: Initialize BSR

The following procedure describes initial configuration of the BSR.
To perform BSR initial configuration:
1. Ensure the BSR is connected through serial cabling to the PC running
WipConfig.

WipConfig connects to the BSR device, and displays the BSR Configuration
pane:
Figure 3-9: WipConfig connected to BSR (BSR Configuration pane)

4. Apply factory default settings to the BSR by performing the following:



WipConfig applies the default settings to the BSR.
Eth IP Address: BSR’s IP address (e.g. 10.0.0.10)
Eth Subnet Mask: BSR’s subnet address (e.g. 255.255.255.240)
Default Gateway: BSR’s default gateway’s IP address if relevant

6. In the RF Configuration group, enter the following fields:

Air MAC Address: BSR’s Air MAC address (valid ranges is between
0x0000 through 0xFFFF), e.g. 0x1200.
Notes:
1) For the Air MAC address, Airspan recommends using only the most
significant bytes (MSB), i.e. the two left-most bytes, and not the least
significant bytes (LSB), i.e. the right-most bytes. For example, a typical Air
MAC address would be "AB00", where the zeros represent the LSB.
2) To ensure that each BSR has a unique Air MAC address, ensure that the
two left-most significant bytes are different between BSRs, e.g. 1000 and 2000.
In this way, the ASWipLL system can support 256 different BSRs in the same
sector (or area).
Frequency Table ID: frequency table ID used by the BSR (valid range is 0
through 63), e.g. 1.
Note: Frequency table IDs 0 through 31 are read-only (i.e. in ROM);

Frequency table IDs 32 through 63 (i.e. NVRAM). To define NVRAM frequency
tables, refer to the WipManage User’s Guide.
8. On the toolbar, click the Reset button to reset the BSR.


3.2.5. Task 4: Initialize SPR

The SPR is usually configured at the factory or at the customer’s premises before
installation. The following procedure describes SPR initial configuration.
To perform SPR initial configuration:
1. Ensure the SPR is connected through serial cabling to the PC running
WipConfig.

WipConfig connects to the SPR device, and displays the SPR Configuration
pane:
Figure 3-13: WipConfig connected to SPR (SPR Configuration pane)

4. Apply factory default settings to the SPR by performing the following:



WipConfig applies default settings to the SPR.
Eth IP Address: SPR’s IP address (e.g. 10.0.0.20)
Eth Subnet Mask: SPR’s subnet address (e.g. 255.255.255.240)
Default Gateway: SPR’s default gateway’s IP address (if relevant)


Index in BSR: SPR’s index number that is indexed in the BSR, e.g. 2.
BSR Air MAC Address: BSR’s Air MAC address to which the SPR is
associated (valid ranges is between 0x0000 through 0xFFFF), e.g. 0x1200.
Note: For the Air MAC address, Airspan recommends using only the most
significant bytes (MSB), i.e. the two left-most bytes, and not the least significant
bytes (LSB), i.e. the right-most bytes. For example, a typical Air MAC address
would be "AB00", where the zeros represent the LSB.
7. On the toolbar, click the Write button to apply the new settings to the
SPR.
8. On the toolbar, click the Reset button to reset the SPR.

Figure 3-16: Warning message box for resetting SPR

3.3. Establishing a Network Connection

After you have configured the ASWipLL devices with basic network parameters
such as IP addresses through a serial communication mode, you can connect
WipConfig to these devices through an IP network connection. This allows you to
configure various device parameters that are available only through an IP network
connection such as Air subnet addresses and VLAN policy.
You can configure devices locally through an IP network by connecting the PC
running WipConfig to the device’s local port. In addition, you can configure devices
remotely through an IP network by connecting WipConfig to the device from
anywhere that provides IP connectivity to the device.
The following WipConfig fields (parameters) are available only when WipConfig
connects to the ASWipLL device through an IP network connection:
BSDU:
Sync Enabled: enables synchronization of the BSDU.
Sync. Ring Id: up to four BSDUs may be daisy chained together. Each
BSDU can be assigned an identification number for participating in the
synchronization process.
BSR:
Max Rate Mode: maximum transmission rate mode
Sync Enabled: enables BSR synchronization (controlled by BSDU)
Voice Enabled: for the sync. Ring - used to determine the hop time
Phase: represents the frequency (listed in the frequency table) on which the
BSR starts transmitting data when the BSR receives a synchronization pulse
(signal) from the BSDU. The phase value is the frequency's index number as
listed in the frequency table. (Valid range is 1 – 96.)
Air Subnet: Air subnet address and scheme for port of BSR interfacing with
wireless path with SPR

SPR:
Default Gateway: IP address of SPR’s default gateway
Max Rate Mode: maximum transmission rate mode (must be the same as
the BSR)
Air Subnet: Air subnet address and scheme for port of SPR interfacing with
wireless path with BSR
Notes:
1) If the SPR cannot be "reached" via the BSR, a network connection can also
be established with the SPR via the SDA (that connects to the SPR), using the
SDA’s Ethernet port.
2) For detailed description on connecting the cables between the PC running
WipConfig and the ASWipLL device for IP network connections, refer to the
ASWipLL Hardware Installation Guide.


To establish an IP network connection between your PC running WipConfig and the
ASWipLL device, you need to perform the following steps (see also Figure 3-17):
Define PC’s IP address, subnet, and default gateway
Connect WipConfig to the ASWipLL device
Figure 3-17: Flowchart for establishing a network connection between WipConfig

and ASWipLL devices
3.3.2. Task 1: Configure PC’s IP Subnet Address

To establish an IP network connection between your PC running WipConfig (or
WipManage) and the ASWipLL device, you need to configure your PC (i.e. PC’s
10/100 Ethernet card) with the same subnet address as the BSR and BSDU. In
addition, you need to define your PC’s default gateway with the BSR’s IP address,
or a router’s IP address if one exists behind the BSR.

Note: The procedure described here for changing your PC’s IP address is for
Windows 2000.
To change your PC’s subnet mask address:

1. If connecting through BSDU’s 100 Base-T Port 1, ensure the BSDU’s 10Base-T
Ports 1 & 2 are looped and your PC has the correct hardware (e.g. Intel 8255x-
based PCI Ethernet Adapter 10/100BaseT).
2. On your desktop, right-click My Network Places , and then from the

shortcut menu, choose Properties, as displayed below.
Figure 3-18: Choosing Properties from My Network Places icon

The Network and Dial-up Connections folder appears, as displayed below:
Figure 3-19: Network and Dial-up Connections folder
3. Right-click the desired connection, and then from the shortcut menu, choose
Properties.

The Local Area Connection Properties dialog box appears, as displayed below:
Figure 3-20: Local Area Connection Properties dialog box
4. In the Components list, select Internet Protocol (TCP/IP), and then click
Properties.

The Internet Protocol (TCP/IP) Properties dialog box appears:
Figure 3-21: Internet Protocol (TCP/IP) Properties dialog box
5. Select the Use the Following IP Address option, and then enter the following
fields:
IP Address: PC’s IP address, e.g. 10.0.0.2
Subnet Mask: PC’s subnet mask address. This must be identical to the
BSR/BSDU (i.e. 255.255.255.240) so that the PC is on the same subnet as
the BSR/BSDU)
Default Gateway: PC’s default gateway. This must be the BSR (i.e. IP
address 10.0.0.10), or if a router exists behind the BSR, then the router’s IP
address

6. Click OK.
Check that your PC’s IP settings have been correctly applied by performing the
following:
1. From Windows Start menu, choose Run, and then in the Open field, type
"cmd".
2. At the MS-DOS prompt, type ipconfig, as shown below.
Figure 3-22: Verifying IP settings using the ipconfig command
As displayed in Figure 3-22, the PC’s IP settings connections have been successfully
applied:
IP Address: 10.0.0.2
Subnet Mask: 255.255.255.240
Default Gateway: 10.0.0.10 (i.e. BSR’s IP address)

3.3.3. Task 2: Connect WipConfig to the Device

Once you have configured the PC’s IP address, you can connect WipConfig to the
ASWipLL devices through an IP network communication mode.
To connect WipConfig to the ASWipLL device through an IP connection:
1. Start WipConfig.
2. From the Tools menu, choose Select Communication Protocol.
The Select Communication Protocol dialog box appears.
Figure 3-23: Select Communication Protocol dialog box
3. Select the IP icon, and then click OK.

On the toolbar, in the Communication group, the Network option is selected, as
displayed in the figure below.

Network option SNMP remote Set Community

selected agent’s IP address rights
Figure 3-24: Entering IP network parameters

4. Enter the following SNMP fields:

Remote Agent: device's IP address, which is acting as a remote SNMP agent
Set Community: SNMP write community rights (e.g. private or public)
5. From the Tools menu, point to Communication, and then choose Network.
The SNMP Protocol Preferences dialog box appears, as displayed below.
Figure 3-25: SNMP Protocol Preferences dialog box
6. To define the SNMP parameter preferences, enter the following fields:

Timeout: time (in seconds) WipConfig waits for a response from the device
after sending a request to the device. Each time the timeout value is reached
and no response is received, WipConfig retransmits its request. The number
of times WipConfig retransmits requests is according to the value defined in
the Number of Retransmits field.
Number of Retransmits: number of times WipConfig retransmits requests
to the ASWipLL device after the timeout value is reached with no response
from the ASWipLL device.
7. Click OK.
8. On the toolbar, click the Connect icon.

WipConfig connects to the ASWipLL device (e.g. SPR) through the IP network
communication mode, as displayed below:
Figure 3-26: WipConfig connected to device (e.g. SPR) through IP network


4
Establishing BSR-SPR Link
in Router Mode
This chapter describes basic procedures for establishing a BSR-SPR link in an IP
routing mode.
Summary of Tasks
Task 1: Configure BSR for IP Routing
Task 2: Configure SPR for IP Routing
Task 3: Start WipManage
Task 4: Add a BS Group
Task 5: Add a Base Station
Task 6: Add a BSDU
Task 7: Add a BSR
Task 8: Add an SPR
Task 9: Test the BSR-SPR Link
Color-Coding of SPR Icons
and SPR procedures are also applicable for IDR devices. In other words, this
chapter is also relevant for establishing a BSR-IDR link and a PPR-SPR/IDR
link in an IP routing mode.

Establishing BSR-SPR Link in Router Mode Commissioning Manual
4.1. Summary of Tasks

The flowchart in Figure 4-1 displays a summary of tasks for establishing a BSR-
SPR link in an IP routing mode.
Figure 4-1: Flowchart for establishing BSR-SPR IP routing link

Commissioning Manual Establishing BSR-SPR Link in Router Mode
For the purpose of this chapter, the example configuration shown below is used.
Figure 4-2: Configuration example for establishing BSR-SPR link in IP router mode
Note: The BSR and SPRs must be on different networks from each other. In
addition, SPRs must be on different networks (i.e. subnets) from one another.

4.2. Task 1: Configure BSR for IP Routing

The first step is to configure the BSR for IP routing. This is performed using
WipConfig.
Warning: In this procedure, you need to reset BSR to factory default settings.
This results in the deletion of the NVRAM frequency tables. Therefore, it is
recommended to save the NVRAM frequency tables before performing this
procedure (refer to the WipManage User's Guide for saving frequency tables).
Note: It is recommended to configure the BSR through a serial connection.
To configure BSR for IP routing (WipConfig):

1. Connect the PC running WipConfig to the BSR.
2. Start WipConfig.
3. In the Communication group, select Serial.
4. On the toolbar, click the Connect button.

WipConfig connects to the BSR (i.e. IP address 10.0.0.10).
Mode field
Figure 4-3: WipConfig connected to BSR

5. Apply factory default settings by performing the following:



6. From the Mode drop-down list, select Router (i.e. IP router mode).
Note: If in the BSR’s ROM, the BSR is defined as an IP router, the Mode field
displays Router; If the BSR is defined for transparent bridging, then the Mode
field displays Bridge.
7. In the Eth IP Address field, enter the BSR’s IP address (e.g. 10.0.0.10).
8. In the Eth Subnet Mask field, enter the BSR’s subnet mask address (e.g.
255.255.255.240).

9. In the RF Configuration group, in the BSR Air MAC Address, enter the
BSR’s Air MAC (e.g. 0x1200). Valid ranges are between 0x0000 through
0xFFFF).
12. Click Yes to reset the device with default settings.

Ensure that the Mode field displays Router (i.e. BSR in IP routing mode), as
displayed below.
BSR in
router mode
Figure 4-7: BSR configured in IP router mode

4.3. Task 2: Configure SPR for IP Routing

The next step is to configure the SPR for IP routing. This is performed using
WipConfig.
Warning: In this procedure, you need to reset the SPR to factory default
settings. This results in the deletion of the NVRAM frequency tables. Therefore,
it is recommended to save the NVRAM frequency tables before performing this
procedure.
Note: It is recommended to configure the SPRs through a serial connection.
To configure SPR for IP routing (WipConfig):

1. Connect the PC running WipConfig to the SPR device.
2. Start WipConfig.

5. WipConfig connects to the SPR (i.e. 10.0.0.20).
Mode field
Figure 4-8: WipConfig displaying the SPR Configuration pane




7. From the Mode drop-down list, select Router (i.e. IP router mode).
Note: If in the SPR’s ROM, the SPR is defined as an IP router, then the Mode
field displays Router; If the SPR’s ROM is defined for transparent bridging,
then the Mode field displays Bridge.
8. In the Eth IP Address field, enter the SPR’s IP address (e.g. 10.0.0.20).
9. In the Eth Subnet Mask field, enter the SPR’s subnet mask address (e.g.
255.255.255.240).

BSR’s Air MAC address to which the SPR is associated, e.g. 0x1200. Valid
ranges are between 0x0000 through 0xFFFF.

Ensure that the Mode field displays Router (i.e. in IP routing mode), as
displayed below.
SPR in router
mode
Figure 4-12: SPR configured for IP routing

4.4. Task 3: Start WipManage

Once you have configured the BSR and SPR for IP routing using WipConfig, you
need to define the following ASWipLL elements using WipManage, in order to
establish the BSR-SPR link:
BS Group (Base Station group)
BS (Base Station)
BSDU
BSR
SPR
To start WipManage:
1. From the Windows Start menu, point to Programs, point to Airspan, and then
click WipManage. The WipManage Main window is displayed below:
Figure 4-13: WipManage Main window

4.5. Task 4: Add a BS Group

A BS Group is the first element you need to define in WipManage. To this BS
Group you can then later add a BS. In our example, the BS Group is named
"Manhattan_1".
Note: WipManage displays two default BS Groups that you can use: Default
and Default1. These default groups can be renamed or deleted.
To add a BS Group:
1. In the Database Tree, right-click , and then from the shortcut menu,
choose Add BS Group. The BS Group Add dialog box appears, as displayed
below.
Figure 4-14: Adding a BS Group
2. In the Group Name field, enter a name for the BS Group, e.g. "Manhattan_1".

3. Click OK.
BS Group
added
Figure 4-15: BS Group "Manhattan_1" added to Database Tree
4.6. Task 5: Add a Base Station

The next step is to add a BS to the BS Group. In our example, the BS is named
"Times Square".
To add a BS:
1. In the Database Tree, click the "Manahattan_1" branch, to which you
want to add the BS.
2. In the BSs Map view (i.e. right pane), right-click an empty area, and then from
the shortcut menu, choose Add BS.

The BS Add dialog box appears, as displayed below.
Figure 4-16: Adding a BS
3. In the BS Name field, enter a name for the BS, e.g. "Times Square".
4. Click OK.
Added BS
Figure 4-17: BS "Times Square" added to BS Group "Manahattan_1"

4.7. Task 6: Add a BSDU

You can now add a BSDU to the BS that you added in the previous section. In our
example, a BSDU with IP address 10.0.0.5 is added.
To add a BSDU:
1. In the Database Tree, double-click the "Times Square" branch, or in the
BSs Map view, double-click the "Times Square" icon. The BS view is
displayed.
2. Right-click one of the BSDU index boxes (1 to 4), and then from the shortcut
menu, choose Add BSDU.
The BSDU-Add dialog box appears, as displayed below.
Figure 4-18: Adding a BSDU
3. In the Manage IP field, enter the BSDU’s IP address, e.g. 10.0.0.5.

4. In the Get Community and Set Community fields, enter the SNMP community
rights.

5. From the Index in BS drop-down list, select the BSDU index number (1 through
4). The index number that appears by default when you open BSDU Add dialog
box, is the index number of the BSDU box in which you right-clicked.
6. Click OK.
Added BSDU
Figure 4-19: BSDU (10.0.0.5) added to BS "Times Square"

4.8. Task 7: Add a BSR

You can add up to six BSRs to each BSDU. Therefore, you can add a maximum of
24 BSRs (6 x 4 BSDUs) at a BS. In our example, we need to add a BSR with IP
address 10.0.0.10.
To add a BSR:
1. In the Database Tree, double-click "Times Square" icon.
2. Right-click one of the six blue rectangles in the same row as the BSDU to which
you want to add the BSR, and then from the shortcut menu, choose Add BSR.
The BSR-Add dialog box appears.
Figure 4-20: Adding a BSR
3. In the Manage IP field, enter the BSR’s IP address, e.g. 10.0.0.10.

4. In the Get Community and Set Community fields, enter the BSR's SNMP
community rights.
5. To define advanced identifying parameters, select the Advanced check box. The
Advanced fields appear, as displayed in Figure 4-21.

Figure 4-21: Adding advanced BSR parameters
Enter the following Advanced group fields, as desired:

BSDU Index in BS: BSDU (1 through 4) to which you want to add the BSR.
By default, the displayed BSDU index number corresponds to the BSDU that
appears in the same the row in which you right-clicked.
Index in BSDU: Up to six BSRs can be added to a BSDU. The index
number (1 through 6) represents a unique BSR number within the BSDU. By
default, the displayed index number is that which corresponds to the BSR
box in which you right-clicked.
6. Click OK.

Added BSR
Figure 4-22: BSR (10.0.0.10) added to BS "Times Square"
To manage the BSR, double-click the BSR icon.
BSR in router
mode
Figure 4-23: BSR Zoom window displaying BSR (10.0.0.10) in IP Router mode

4.9. Task 8: Add an SPR

Once you have added the BSR, you can add SPRs to this BSR. You can add up to
126 SPRs per BSR device and assign any one of the index numbers (2 through 127)
to the SPR.
In our example, we need to add one SPR (10.0.0.20) to the SPR index #2 icon (as
defined in WipConfig in Chapter 3, "Initial Configuration").
To add an SPR:
1. Double-click the BSR icon. The BSR Zoom window appears.

2. Right-click SPR index #2 icon, and then from the shortcut menu, choose Add,
as shown below.
Figure 4-24: Choosing the Add command from the shortcut menu

The Permitted SPRs-Add dialog box appears.
Figure 4-25: Permitted SPRs Add dialog box
3. In the IP Address field, enter the SPR’s IP address (e.g. 10.0.0.20).

4. To add a static route from the BSR to the SPR, click Route. The Static Routing
Table per SPR dialog box appears.

Figure 4-26: Static Routing Table per SPR dialog box
5. Click Add. The following dialog box appears:
Figure 4-27: Static Route Table Add dialog box

6. Fill in the following fields:

Destination: enter the IP address of the SPR (e.g. 10.0.0.20)
Route Mask: enter the subnet mask of the SPR (e.g. 255.255.255.240)
To allow WipManage to help you calculate the subnet mask, click the Calc
button. The Calculate Subnet dialog box appears, as shown below.
Figure 4-28: Calculate Subnet dialog box
Once you have calculated the subnet mask, click the OK button, and the Static
Route Table – Add dialog box reappears.

7. Click OK. The static route from the BSR to the SPR appears in the Static
Routing Table, as shown below.
Figure 4-29: Added SPR static route
8. Click Close to close the Static Routing Table per SPR dialog box.
9. In the Permitted SPRs Add dialog box, click OK.
After a few seconds, the SPR index #2 icon appears green, as shown in Figure
4-30, indicating that an air and network link exists with the SPR. You can now
manage the SPR.

SPR
successfully
linked to BSR
Figure 4-30: Added SPR (index 2) displayed in BSR Zoom window
Double-click the SPR icon to open the SPR Zoom window, displayed below.
SPR in router
mode
Figure 4-31: SPR Zoom window of SPR (10.0.0.20)

4.10. Task 9: Test the BSR-SPR Network Link

You can test the network link between the BSR and SPR by pinging the SPR from a
PC located behind the BSR.
To test the link by pinging:
From the PC/Laptop (e.g. IP address 10.0.0.2) behind the BSR, open an MS-
DOS prompt and use the ping – t command to ping the SPR (IP address
10.0.0.20), as shown below:
Figure 4-32: Pinging SPR using the MS-DOS ping-t command

4.11. Color-Coding of SPR Icons

In the BSR Zoom window, 126 SPR indexes are represented as icons composed of a
circle, an index number (2 through 127), and a rectangle surrounding the index
number. The color of the SPR icon and rectangle surrounding the index number
indicates the status of the connection as follows:
Circle: indicates status of the low-level (Air MAC) connection between BSR
and SPR
Rectangle surrounding index number: indicates status of IP network
connection between PC management station and the SPR
BSR-SPR air link status (circle)

WipManage-SPR IP network
SPR index number link status (rectangle)
Figure 4-33: Areas of the SPR icon
For configuration to succeed, the SPR icon’s circle and rectangle surrounding the
index number must both be green (i.e. an air and network link must exist).

Table 4-1: Description of color-coding possibilities of SPR icon

SPR Air link Network link Description
icon (color of (color of
circle) rectangle)
Grey Grey Undefined SPR
Green Green SPR has air link with BSR, and IP routing link with
PC running WipManage
Yellow Red Defined SPR, but without air link with BSR, and
without IP routing link with PC running
WipManage
Green Red Defined SPR has air link with BSR, but no IP
routing link with PC running WipManage
Green Yellow SPR has air link with BSR, and is currently being
polled by PC running WipManage
Grey with Red Defined SPR, but currently disabled
"X"
Grey with Grey Previously defined SPR that has been deleted from
check mark the BSR. This SPR index number is not deleted
from the ASWipLL database.


5
in Bridge Mode
This chapter describes basic procedures for establishing a BSR-SPR link in a
transparent bridging mode. This chapter includes the following sections:
Summary of Tasks
Task 1: Configure BSR for Transparent Bridging
Task 2: Configure SPR for Transparent Bridging
Task 3: Start WipManage
Task 4: Add a BS Group
Task 5: Add a Base Station
Task 6: Add a BSDU
Task 7: Add a BSR
Task 8: Add an SPR
Advanced Tasks
and SPR procedures are also applicable for IDR devices. In other words, this
chapter is also relevant for establishing a BSR-IDR link and a PPR-SPR/IDR
link in transparent bridging mode.

Establishing BSR-SPR Link in Bridge Mode Commissioning Manual

The flowchart in Figure 5-1 displays the tasks for establishing a BSR-SPR link in
transparent bridging mode.
Figure 5-1: Flowchart for establishing BSR-SPR link in transparent bridging mode

Commissioning Manual Establishing BSR-SPR Link in Bridge Mode
For the purpose of this chapter, the example configuration shown below is used.
Figure 5-2: Configuration example for establishing BSR-SPR link in bridge mode

5.2. Task 1: Configure BSR for Transparent

Bridging
The first step is to configure the BSR for transparent bridging. This is performed
using WipConfig.
Warning: In this procedure, you need to reset the BSR to factory default
procedure.
To configure BSR for transparent bridging (WipConfig):

2. Start WipConfig.

Changed to
router mode
Figure 5-3: WipConfig connected to BSR (in router mode)




6. From the Mode drop-down list, select Bridge (i.e. transparent bridging).
Note: If in the BSR’s ROM, the BSR is defined as an IP router, then the Mode
field displays Router; If the BSR is defined for transparent bridging, then the
Mode field displays Bridge.
255.255.255.240).

BSR’s Air MAC, e.g. 0x1200. Valid ranges are from 0x0000 through 0xFFFF.

Ensure that the Mode field displays Bridge (i.e. BSR in transparent bridge
mode), as displayed below.
Bridge mode
Figure 5-7: BSR configured for transparent bridging

5.3. Task 2: Configure SPR for Transparent

Bridging
The next step is to configure the SPR for transparent bridging. This is also
performed using WipConfig.
procedure.
Note: It is recommended to configure the SPR through a serial connection.
To configure SPR for transparent bridging (WipConfig):

2. Start WipConfig.

WipConfig connects to the SPR (i.e. IP address 10.0.0.20).
SPR in router
mode
Figure 5-8: WipConfig connected to SPR (in router mode)




6. From the Mode drop-down list, select Bridge.
field displays Router; If the SPR is defined for transparent bridging, then the
7. In the Eth IP Address field, change the SPR’s IP address (e.g. 10.0.0.11).
255.255.255.240).

BSR’s Air MAC address to which the SPR is associated, e.g. 0x1200. Valid
ranges are from 0x0000 through 0xFFFF.

Ensure that the Mode field displays Bridge (i.e. SPR in transparent bridge
SPR changed
to bridge
mode
Figure 5-12: SPR configured for transparent bridging

5.4. Task 3: Start WipManage

Once you have configured the BSR and SPR for transparent bridging using
WipConfig, you need to define the following ASWipLL elements using WipManage
in order to establish a BSR-SPR link:
BS Group (Base Station group)
BS (Base Station)
BSDU
BSR
SPR
To start WipManage:
From the Windows Start menu, point to Programs, point to Airspan, and then
click WipManage.
Figure 5-13: WipManage Main window

5.5. Task 4: Add a BS Group

A BS Group is the first element you need to define in WipManage. To this BS
Group you can then later add a BS. In our example, the BS Group is named
"Manhattan_1".
Note: WipManage displays two default BS Groups that you can use: Default
and Default1. These default groups can be renamed or deleted.
To add a BS Group:
1. In the Database Tree, right-click , and then from the shortcut menu,
choose Add BS Group. The BS Group Add dialog box appears, as displayed
below.
Figure 5-14: Adding BS Group
2. In the Group Name field, enter a name for the BS Group, e.g. "Manhattan_1".

3. Click OK.
The figure below displays the added BS Group "Manhattan_1" in the Database
Tree.
BS Group
added
Figure 5-15: BS Group "Manhattan_1" added to Database Tree
5.6. Task 5: Add a Base Station

The next step is to add a BS to the BS Group. In our example, the BS is named
"Times Square".
To add a BS:
1. In the Database Tree, click the "Manahattan_1" branch, to which you
want to add the BS.

2. In the BSs Map view (i.e. right pane), right-click an empty area, and then from
the shortcut menu, choose Add BS. The BS Add dialog box appears, as
displayed below.
Figure 5-16: Adding a BS
3. In the BS Name field, enter a name for the BS, e.g. "Times Square".
4. Click OK.
Added BS
Figure 5-17: BS "Times Square" added to BS Group "Manahattan_1"

5.7. Task 6: Add a BSDU

You can now add a BSDU to the BS that you added in the previous section. In our
example, a BSDU with IP address 10.0.0.5 is added.
To add a BSDU:
1. In the Database Tree, double-click the "Times Square" branch "Times
Square", or in the BSs Map view double-click the "Times Square" icon.
The BS view is displayed.
2. Right-click in one of the BSDU index boxes (1 to 4), and then from the shortcut
menu, choose Add BSDU.
The BSDU-Add dialog box appears, as displayed below.
Figure 5-18: Adding a BSDU
3. In the Manage IP field, enter the BSDU’s IP address, e.g. 10.0.0.5.

rights.

5. From the Index in BS drop-down list, select the BSDU index number (1 through
4). The index number that appears by default when you open BSDU Add dialog
box, is the index number of the BSDU box in which you right-clicked.
6. Click OK.
Added BSDU
Figure 5-19: BSDU (10.0.0.5) added to BS "Times Square"

5.8. Task 7: Add a BSR

You can add up to six BSRs to each BSDU. Therefore, you can add a maximum of
24 BSRs (6 x 4 BSDUs) at a BS. In our example, we need to add a BSR with IP
address 10.0.0.10.
To add a BSR:
1. In the Database Tree, double-click "Times Square" icon.
2. Right-click one of the six blue rectangles in the same row as the BSDU to which
you want to add the BSR, and then from the shortcut menu, choose Add BSR.
The BSR-Add dialog box appears.
Figure 5-20: Adding a BSR
3. In the Manage IP field, enter the BSR’s IP address, e.g. 10.0.0.10.

rights.
5. To define advanced identifying parameters, select the Advanced check box. The
Advanced fields appear, as displayed in Figure 5-21.

Figure 5-21: Adding advanced BSR parameters
Enter the following Advanced group fields, as desired:

BSDU Index in BS: BSDU (1 through 4) to which you want to add the BSR.
By default, the displayed BSDU index number corresponds to the BSDU that
appears in the same the row in which you right-clicked.
Index in BSDU: Up to six BSRs can be added to a BSDU. The index
number (1 through 6) represents a unique BSR number within the BSDU. By
default, the displayed index number is that which corresponds to the BSR
box in which you right-clicked.
6. Click OK.

Added BSR
Figure 5-22: BSR (10.0.0.10) added to BS "Times Square"
To manage the BSR, double-click the BSR icon. The BSR Zoom window appears:
BSR in
bridge mode
Figure 5-23: BSR Zoom window displaying BSR (10.0.0.10) in bridge mode


Once you have added the BSR, you can add SPRs to this BSR. You can add up to
126 SPRs per BSR device and assign any one of the index numbers (2 through 127)
to the SPR.
In our example, we need to add one SPR (10.0.0.11) to the SPR index #2 icon (as
defined previously in WipConfig).
To add an SPR:
1. Double-click the BSR icon. The BSR Zoom window appears, as displayed
below.
2. Right-click the SPR index #2 icon, and then from the shortcut menu, choose
Add, as shown below.


4. Click OK.
Note: No static routes are added in transparent bridge mode.

The SPR index #2 icon appears green, indicating a viable BSR-SPR link.
SPR
successfully
linked to BSR
Double-click the SPR icon to open the SPR Zoom window, as displayed below.
SPR in bridge
mode
Figure 5-27: SPR Zoom window of SPR (10.0.0.11) in bridge mode


You can test the link between the BSR and SPR by pinging the SPR from a PC
located behind the BSR.
From the PC/Laptop (IP address 10.0.0.2) behind the BSR, open an MS-DOS
prompt and use the ping – t command to ping the SPR (IP address
Figure 5-28: Pinging the ASWipLL device using the MS-DOS ping-t command
Note: To ping devices in the transparent bridging mode, all devices (including
hosts) must be in the same subnet.

5.11. Advanced Tasks

Once you have configured the BSR and SPR for transparent bridging, you can
perform the following tasks:
View MAC addresses
Define MAC address aging time
Enable forwarding of various packets
5.11.1. Task 1: View MAC Addresses

When a ping is performed between the SPR and BSR, and between the SPR’s hosts
and BSR, the BSR enters the SPR’s and the SPR host’s MAC addresses in
WipManage's BSR’s MAC Table.

To view the MAC addresses (WipManage):

In the BSR Zoom window, from the Configuration menu, point to Bridge, and
then choose MAC Table.
Figure 5-29: MAC Table dialog box displaying the MAC addresses
MAC addresses that begin with 00a00a indicate ASWipLL devices (SPR or
BSR). All other MAC addresses represent hosts connected to the SPRs.

5.11.2. Task 2: Define MAC Address Aging Time

WipManage allows you to define the time after which unused MAC addresses are
deleted from the MAC table. In other words, if the BSR does not receive any SPR
packets within this configured time, then the SPR’s MAC address is deleted from
the BSR’s MAC table.
To define aging time for MAC addresses (WipManage):
1. From the Configuration menu, point to Bridge, and then choose MAC Table.
The MAC Table dialog box appears, as displayed in Figure 5-29.
2. In the Aging Time field, enter the time (in minutes) after which you want an
unused MAC address to be automatically deleted from the MAC Table.
3. Click Set, and then click Close.

5.11.3. Task 3: Enable Forwarding of Various Packets

WipManage allows you to enable and disable the forwarding of various packets in
transparent bridge mode.
To enable forwarding of packets in bridge mode:
1. In the BSR Zoom window, point to Bridge, and then choose Bridge
Configuration. The Bridge Configuration dialog box appears, as displayed
below.
Figure 5-30: Bridge Configuration dialog box
2. To enable the sending of unknown destination packets from the subscriber’s

LAN, select the Forward Unknown Destination Packets check box.

3. To enable the sending of broadcast/multicast packets from the BSR to the

SPR/IDR, select the Forward Broadcast/Multicast Packets check box.
4. To enable bridging between SPRs, select the Enable Bridging Between SPRs
check box.
5. To enable passing through of various applications, select the desired check
boxes:
ARP: if selected, no Address Resolution Protocol (ARP) request packets are
received.
DHCP: if selected, no dynamic IP addressing (Dynamic Host Configuration
Protocol) is performed to devices
PPPoE: if selected, no Point-to-Point Protocol over Ethernet packets are
transmitted
NetBIOS over IP: if selected, no Network Basic Input Output System
messages are transmitted. This is usually for Microsoft for network
neighborhood – peer sharing.
Other: other applications and services


6
Changing Link from Router
to Bridge
This chapter describes the procedures for changing the BSR-SPR network from an
IP routing mode to a transparent bridge mode.
Overview
Summary of Tasks
Task 1: Install WipManage that Supports Transparent Bridging
Task 2: Upgrade SPR to Support Transparent Bridging
Task 3: Upgrade BSR to Support Transparent Bridging
Task 4: Configure BSR for Transparent Bridging
Task 5: Configure SPR for Transparent Bridging
Task 6: Add SPR

Changing Link from Router to Bridge Commissioning Manual
6.1. Overview
The following figures display the configuration setup of the ASWipLL system in an
IP router mode (see Figure 6-1), and then changed to a transparent bridge mode (see
Figure 6-2).
Figure 6-1: ASWipLL in an IP router mode

Commissioning Manual Changing Link from Router to Bridge
Figure 6-2: ASWipLL changed to transparent bridge mode


The flowchart in Figure 6-3 displays a summary of tasks for changing BSR-SPR
network from an IP routing network to a transparent bridging network.
Figure 6-3: Flowchart for changing ASWipLL from IP routing to transparent bridging

6.3. Task 1: Install WipManage that Supports

Transparent Bridging
Before you can configure your BSR-SPR network for transparent bridging, you need
to ensure that the currently installed WipManage supports transparent bridging. If
the current WipManage supports only IP routing (and PPPoE), you need to install
the latest WipManage that supports also transparent bridging.
For installing WipManage, see Chapter 2 "Installing ASWipLL Management
Software".
Note: WipManage software version 4.49 and later, support both transparent
bridging and IP routing/PPPoE.
6.4. Task 2: Upgrade SPR to Support

If the SPR’s software version supports only IP routing, you need to download a later
software version that supports also transparency bridging. You can download a later
software version to the SPR by using WipManage or WipConfig. If you use
WipManage, you need to run a TFTP server.
For a detailed description on upgrading SPRs, see Chapter 27, "Upgrading
ASWipLL Devices".
Notes:
1) You can download only up to two earlier or later software versions than the
current version. For example, if the current SPR’s software version is 2.58.0.4
(i.e. ASWipLL Release 4.1), you can download either the next version, e.g.
2.69.0.1 (i.e. ASWipLL Release 4.2A), or the one after that, e.g. 2.78.0.5 (i.e.
ASWipLL Release 4.2B).
2) Always upgrade the devices furthest form the PC running the TFTP server.
In other words, upgrade the SPR before the BSR.

6.5. Task 3: Upgrade BSR to Support

If the BSR’s software version supports only IP routing, you need to download a later
software version that supports also transparency bridging. You can download a later
software version to the BSR, by using WipManage or WipConfig. If you use
WipManage, you need to run a TFTP server.
For a detailed description on upgrading BSRs, see Chapter 27, "Upgrading
ASWipLL Devices".
Notes:
1) You can download only up to two earlier or later software versions than the
current version. For example, if the current BSR’s software version is 2.58.0.4
ASWipLL Release 4.2B). For an explanation on the upgrading rules, see
Chapter 20, "Upgrading ASWipLL Database and SW Versions".
2) Always upgrade the devices furthest form the PC running the TFTP server.
In other words, upgrade the SPR before the BSR
6.6. Task 4: Configure BSR for Transparent

Bridging
Once you have successfully downloaded a later software version supporting
transparent bridging to the BSR, you need to configure BSR for transparent
bridging. This configuration is performed using WipConfig.
procedure.

To configure the BSR for transparent bridging (WipConfig):

2. Start WipConfig.
BSR in router
mode
Figure 6-4: BSR Configuration pane (BSR in IP router mode)




Note: If in the BSR’s ROM, the BSR is defined as an IP router, then the Mode
field displays Router; If the BSR is defined for transparent bridging, then the
255.255.255.240).

BSR’s Air MAC, e.g. 0x1200. Valid ranges are from 0x0000 through 0xFFFF).


Ensure that the Mode field displays Bridge (i.e. BSR in transparent bridge
BSR changed
to bridge
mode
Figure 6-8: BSR changed to transparent bridge mode

6.7. Task 5: Configure SPR for Transparent

Bridging
Once you have downloaded to the SPR a software version supporting transparent
bridging, you need to configure the SPR for transparent bridging. To perform this,
you need to use WipConfig to change the Mode field from Router (i.e. IP router
mode) to Bridge (i.e. bridge mode).
procedure.
Note: It is recommended to configure the SPR through a serial connection.
To configure SPR for transparent bridging (WipConfig):

1. Connect the PC running WipConfig to the SPR device using a serial cable
connection.
2. Start WipConfig.

WipConfig connects to the SPR (i.e. IP address 10.0.0.20) and displays the SPR
Configuration pane.
SPR in router
mode
Figure 6-9: SPR Configuration pane (SPR in IP router mode)




field displays Router; If the SPR is defined for transparent bridging, then the
7. In the Eth IP Address field, enter the SPR’s IP address (e.g. 10.0.0.11) so that it
is in the same subnet as the BSR.
255.255.255.240).


Index in BSR: unique identity of the SPR within the BSR
(valid ranges is between 2 through 127), e.g. 2.
BSR Air MAC Address: BSR Air MAC address to which the SPR is
associated, e.g. 0x1200. Valid ranges are from 0x0000 through 0xFFFF.

Ensure that the Mode field displays Bridge (i.e. SPR in transparent bridge
SPR in bridge
mode
Figure 6-13: SPR changed to transparent bridge mode

6.8. Task 6: Add SPR in WipManage

When you change the SPR and BSR from the IP router mode to the transparent
bridge mode using WipConfig, WipManage deletes the SPR associated with the
BSR. Therefore, you need to add the SPR again in WipManage.
Before you add the SPR in the BSR Zoom window, you can verify, in this window,
whether BSR is configured for transparent bridging. The figure below displays the
BSR Zoom window, which displays the BSR’s mode as "Bridge". In addition, the
SPR icon contains a check mark (√) indicating that the SPR has been deleted.
SPR deleted
from BSR
BSR in bridge
mode
Figure 6-14: Verifying BSR is in bridge mode
In our example configuration, we need to add SPR (10.0.0.11) to SPR index #2.

To add an SPR:
1. In the BSR Zoom window, right-click the SPR index #2 icon, and then from the
shortcut menu, choose Add, as shown below.

2. In the IP Address field, enter the IP address of the SPR (e.g. 10.0.0.11).
3. In the Name field, enter the name of the SPR.
Note: In transparent bridging, you do not enter static routes (i.e. Route button
is not used).

4. Click OK.
The SPR index #2 icon appears green, as shown below, indicating that a viable
air and network link exists with the BSR. You can now manage the SPR.
SPR
successfully
linked to BSR

Double-click the SPR to display the SPR Zoom window.
SPR in bridge
mode
Figure 6-18: SPR Zoom window of SPR 10.0.0.11 in bridge mode
You can verify that the SPR is in bridge mode by the "Bridge Mode" display in the
SPR Zoom window, as shown above


connected behind the BSR device.


7
Changing Link from Bridge
to Router
This chapter describes basic procedures for changing the BSR-SPR network from a
transparent bridge mode to an IP router mode.
Overview
Summary of Tasks
Task 1: Configure BSR for IP Routing
Task 2: Configure SPR for IP Routing
Task 3: Add an SPR

Changing Link from Bridge to Router Commissioning Manual
7.1. Overview
The following figures display the configuration setup of the ASWipLL system in a
transparent bridge mode (see Figure 7-1), and then changed to an IP router mode
(see Figure 7-2).
Figure 7-1: ASWipLL in transparent bridge mode

Commissioning Manual Changing Link from Bridge to Router
Figure 7-2: ASWipLL changed to IP router mode


The flowchart in Figure 7-3 displays a summary of tasks for changing ASWipLL
from a transparent bridging network to an IP routing network.
Figure 7-3: Flowchart for changing ASWipLL from transparent bridging to IP routing

7.3. Task 1: Configure BSR for IP Routing

The first step is to change BSR's operating mode from bridge to router mode, using
WipConfig.
procedure.
To configure BSR for IP routing (using WipConfig):

2. Start WipConfig.


Bridge mode
Figure 7-4: BSR in transparent bridge mode



Note: If in the BSR’s ROM, the BSR is defined as an IP router, the Mode field
displays Router; If the BSR is defined for transparent bridging, then the Mode
field displays Bridge.
6. From the Mode drop-down list, select Router.

8. In the Eth Subnet Mask field, change the BSR’s subnet mask address (e.g.
255.255.255.240).
9. In the Air MAC Address field, enter the BSR’s Air MAC address, e.g. 0x1200.
Valid ranges are from 0x0000 through 0xFFFF.
10. In the Frequency Table ID field, enter frequency table ID used by the BSR
(valid range = 0 through 63), e.g. 1.



Ensure that the Mode field displays Router (i.e. BSR in IP routing mode).
Changed to
router mode
Figure 7-8: BSR changed to IP router mode

7.4. Task 2: Configure SPR for IP Routing

The next step is to change the SPR's operating mode from bridge to router mode,
using WipConfig.
Warning: In this procedure, you first need to reset the SPR to factory default
procedure.
Note: It is recommended to configure the SPRs through a serial connection.
To configure SPR for IP routing (using WipConfig):

1. Connect the PC running WipConfig to the SPR device through a serial cable
connection.
2. Start WipConfig.

WipConfig connects to the SPR (i.e. 10.0.0.11).
SPR in bridge
mode
Figure 7-9: SPR in transparent bridge mode




6. From the Mode drop-down list, select Router (i.e. IP routing).
field displays Router; If the SPR’s ROM is defined for transparent bridging,
then the Mode field displays Bridge.
7. In the Eth IP Address field, change the SPR’s IP address (e.g. 10.0.0.20).
8. In the Eth Subnet Mask field, change the SPR’s subnet mask address (e.g.
255.255.255.240).


Index in BSR: unique identity of the SPR within the BSR
(valid ranges is between 2 through 127), e.g. 2.
BSR Air MAC Address: BSR Air MAC address to which the SPR is
associated, e.g. 0x1200. Valid ranges are from 0x0000 through 0xFFFF.


Ensure that the Mode field displays Router (i.e. SPR in IP routing mode).
SPR in router
mode
Figure 7-13: SPR changed to IP router mode


When you change the SPR and BSR from the transparent bridge mode to IP router
mode using WipConfig, WipManage deletes the SPR associated with the BSR.
Therefore, you need to add the SPR again in WipManage. In addition, you need to
add a static route from the BSR to the SPR and define a default gateway (if relevant)
for the SPR.
Before you add the SPR in the BSR Zoom window, you can verify, in this window,
that BSR is configured for IP routing. The figure below displays the BSR Zoom
window, which displays the BSR’s mode as "Router". In addition, the SPR icon
contains a check mark (√) indicating that the SPR has been deleted.
SPR deleted
from BSR
BSR in router
mode
Figure 7-14: Verifying that BSR is in IP router mode

In our example, we need to add SPR (10.0.0.20) to the SPR index #2 icon.
To add the SPR:
1. In the BSR Zoom window, right-click the SPR #2 icon, and then from the
shortcut menu, choose Add.
Figure 7-15: Choosing the Add command for adding the SPR


2. To add a static route from the BSR to the SPR, click Route. The Static Routing
Table per SPR dialog box appears.

3. Click Add. The following dialog box appears:
Figure 7-18: Static Route Table Add dialog box

4. Fill in the following fields:

Destination: enter the SPR’s IP address (e.g. 10.0.0.20)
Route Mask: enter the SPR’s subnet mask (e.g. 255.255.255.240)
To allow WipManage to help you calculate the Subnet Mask, click the Calc
button. The Calculate Subnet dialog box appears, as shown below.
Figure 7-19: Calculate Subnet dialog box
Once you have calculated the Subnet Mask, click the OK button, and the Static
Route Table – Add dialog box reappears.

5. Click OK. The static route from the BSR to the SPR appears in the Static
Routing Table, as shown below.
Figure 7-20: Added SPR static route
6. Click Close to close the Static Routing Table per SPR dialog box.
7. In the Permitted SPRs Add dialog box, click OK.

After a few seconds, the SPR index #2 icon appears green, as shown below,
indicating that a viable air and network link exists with the BSR. You can now
manage the SPR.
SPR
successfully
linked to BSR

Double-click the SPR icon to open the SPR Zoom window, as displayed below.
SPR in router
mode
Figure 7-22: SPR Zoom window of SPR (10.0.0.20) in IP router mode
You can verify that the SPR is in router mode by the "Router Mode" display in the
SPR Zoom window, as shown above.


located behind the BSR.
Figure 7-23: MS-DOS prompt using the ping – t command


8
with AutoConnect
This chapter describes procedures for establishing a link between BSRs and SPRs
using the ASWipLL AutoConnect feature.
Overview
Configuring Repeating AutoConnect
Configuring AutoConnect with Redirection
Redirecting Previously Redirected SPRs
Color-Coding of AutoConnect SPR Icons
AutoConnect Trap Messages
Notes:
1) AutoConnect is a licensed feature.
2) In this chapter, BSR procedures are also applicable for PPR devices and
SPR procedures are also applicable for IDR devices.

E s t a b l i s h i n g B S R - S P R L i n k w i t h Au t o C o n n e c t Commissioning Manual
8.1. Overview
ASWipLL’s AutoConnect feature is a license-dependant feature that automatically
connects initially powered-on, unconfigured SPRs to BSRs. These SPRs
automatically connect to BSRs with the strongest RF signal. In addition, these SPRs
can then be redirected to different BSRs. The AutoConnect feature assigns newly
connected SPRs with temporary configuration parameters such as IP address, and, if
relevant, the BSR’s air MAC address to which the SPRs must connect (i.e.
redirection of the SPRs to a different BSR).
You can configure the following AutoConnect features:
Repeating AutoConnect: each time the SPR is reset or powered on, it connects
to a BSR with which it has the strongest RF signal.
AutoConnect with redirection: SPR undergoes AutoConnect only once. This
occurs when it is first powered on or reset, whereby it connects to a BSR having
the strongest RF signal. However, once connected to this BSR, the SPR is then
redirected to connect to a specific BSR. Even if the SPR is later cold started or
reset, the SPR always connects to the specific BSR (i.e. does not undergo
AutoConnect again).
Redirecting previously redirected AutoConnect SPR: SPR that was
redirected to a specific BSR after undergoing AutoConnect, is redirected again
to a different BSR. The SPR always remains connected to this new BSR.

Commissioning Manual E s t a b l i s h i n g B S R - S P R L i n k w i t h Au t o C o n n e c t
Notes:
1) When implementing AutoConnect, ensure that all BSRs are either operating
as IP routers (and PPPoE bridges), or that all BSRs are operating as
transparent bridges.
2) When implementing AutoConnect, all ASWipLL devices must share the
same Management VLAN, Air Subnet address, management station, and
Get/Set Community string.
3) If you are implementing AutoConnect on existing ASWipLL devices, first
change the Air Subnet addresses on each SPR (using WipManage or
WipConfig). This will cause IP disconnection until you finally change the Air
Subnet of the BSR.
4) ASWipLL devices are generally supplied to the customer configured for
AutoConnect in their ROM. However, if this is not the case, you need to define
AutoConnect for each device using WipConfig.
5) When resetting devices to default, the NVRAM frequency tables are
deleted.
6) For the BSR to establish a link with the SPR, ensure that the BSR and SPR
have identical ROM frequency tables.

8.1.1. Automatically Connecting SPRs to BSRs

Unconfigured and newly installed SPRs that do not appear in the ASWipLL
management database remain connected to the BSR with the strongest RF signals.
Figure 8-1 displays the AutoConnect process without redirecting the SPR to a
different BSR.
Figure 8-1: AutoConnect without Redirecting to a different BSR]
The following lists the chronological process of the AutoConnect feature with no
redirecting to a different BSR:
1. Once an unconfigured SPR is installed at the subscriber’s site, and then turned
on, it automatically establishes a link to a BSR with which it has the strongest
RF reception.
2. The BSR provides the SPR with a temporary IP address (for communication and
configuration).
3. The SPR sends an SNMP trap to the ASWipLL management station (i.e.
WipManage) notifying WipManage that the SPR has performed AutoConnect.

4. WipManage searches in the ASWipLL database for the BSR to which the SPR is
assigned. However, because the SPR is not listed in the database, the
management system allows the SPR to continue its link with the BSR.
5. The SPR continuously sends Config Request traps (up to 10) to the management
station until the management station acknowledges these traps. Once the
management station acknowledges these traps, the AutoConnect process ends.
The BSR-SPR link is sustained until the SPR is turned off.
When the SPR is turned on again, the SPR undergoes the AutoConnect process
once again, connecting to the BSR with the strongest RF signal.
8.1.2. Redirecting SPRs to Specific BSRs

Unconfigured and newly installed SPRs that appear in the ASWipLL management
database are redirected to a BSR as defined in the database. Figure 8-2 and Figure
8-3 display the AutoConnect process where the SPR is redirected to a different BSR
(BSR #2).
Figure 8-2: AutoConnect before Redirecting SPR to a different BSR

Figure 8-3: AutoConnect after Redirecting SPR to a different BSR
The following lists the chronological process of the AutoConnect feature with
redirecting SPRs to a different BSR:
1. Once an unconfigured SPR is installed at the subscriber’s site, and then turned
on, it automatically establishes a link with the BSR (BSR #1) with the strongest
reception.
2. The BSR (BSR #1) provides the SPR with a temporary IP address (for
communication and configuration).
3. The SPR sends an SNMP trap to the ASWipLL management station (i.e.
WipManage) notifying WipManage that the SPR has performed an
AutoConnect.
4. WipManage identifies the BSR (BSR #2) in the ASWipLL database to which the
SPR must be connected.

5. WipManage request and receives from this correct BSR (BSR #2), the following
parameters:
BSR (BSR #2) Air MAC address
SPR subnet mask
BSR (BSR #2) transmission rate (3 or 4 Mbps)
6. WipManage sends the configuration parameters to the SPR. These parameters
include:
BSR (BSR #2) Air MAC address
SPR Air MAC address
BSR (BSR #2) IP address
SPR IP and subnet mask address
SPR transmission rate ((3 or 4 Mbps)
SNMP and TFTP QoS class
7. The SPR disconnects from the original BSR (BSR #1), and then connects to the
appropriate BSR (BSR #2) according to the received parameters.
The SPR continuously sends Config Request traps (up to 10) to the management
station until the management station acknowledges these traps. Once the
management station acknowledges these traps, the AutoConnect process ends.
The SPR does not undergo AutoConnect in the future, even if switched off and
then powered on again. From now on, the SPR will always establish a link with
the changed BSR (BSR #2).

8.2. Configuring Repeating AutoConnect

You can configure newly installed, unconfigured SPRs for AutoConnect. Each time
these devices are reset or powered on, they undergo AutoConnect (i.e. repeating
AutoConnect) by connecting to the BSR with the best RF signal.
You can configure repeating AutoConnect for newly installed SPRs, and for regular
SPRs that are currently connected to a BSR.

The figure below displays a flowchart for configuring repeating AutoConnect.
Figure 8-4: Flowchart for configuring repeating AutoConnect

8.2.2. Task 1: Add AutoConnect SPRs

Before powering on the SPR devices, you need to add SPR indexes defined for
AutoConnect, for the BSR in WipManage’s BSR Zoom window. When you add
these SPR indexes, you assign temporary IP addresses, which the BSR temporarily
assigns the connected SPR for communication and configuration.
The SPR devices should only AutoConnect to BSRs that are in the same network
and that provide SPR indexes configured for AutoConnect.
For clarity, in our example, we will define AutoConnect SPR icons for BSR with IP
address 10.0.0.10.
Note: Ensure the WipManage PC IP address is defined in WipManage’s BSR

Managers Table.

To add a range of SPRs for AutoConnect:

1. In the BSR Zoom window, right-click an available undefined (i.e. grayed) SPR
index icon, and then from the shortcut menu, choose Add Range Permitted
SPRs, as displayed in Figure 8-5.
Figure 8-5: Choosing Add Range Permitted SPRs command

The Add Range Permitted SPRs dialog box appears.
Figure 8-6: Add Range Permitted SPRs dialog box
2. In the First SPR Index field, enter the index number of the first SPR
(e.g. 2)
3. In the Last SPR Index field, enter the index number of the last SPR
(e.g. 3).
4. In the First SPR IP Address field, enter the IP address of the first SPR (e.g.
10.0.0.12).
5. From the Status drop-down list, select AutoConnect.
6. From the Auto Disconnect drop-down list, select On to enable this feature.

7. Select the Add to Static Route Table check box, and then in the Subnet Mask
field, enter Subnet Mask address. The subnets should be defined by mask. A
calculator is provided to determine optimal efficiency.
Figure 8-7: Subnet Address Calculator
Note: If the SPRs are in transparent bridge mode, clear the Add to Static
Route Table check box.
8. Click OK.

The added AutoConnect SPR icons (e.g. SPR indexes 2 and 3) are displayed
below.
Figure 8-8: Added AutoConnect SPR indexes (2 and 3) in BSR Zoom window
For a description on color-coding of AutoConnect SPR icons, see Section 8.5,

"Color-Coding of AutoConnect SPR Icons".
Note: The added AutoConnect SPR icons are only added to the ASWipLL
database when you edit them or when an SPR device connects to them.

8.2.3. Task 2: Define AutoDisconnect Interval

The AutoDisconnect interval is the time that an SPR index configured for
AutoConnect, becomes available for accepting an SPR device using AutoConnect
after an SPR losses connection with the BSR (i.e. with the SPR index). The interval
between losing the connection and becoming available again for accepting another
SPR through AutoConnect is called the AutoDisconnect interval. This interval is
user-configurable.
SPR device SPR device
connects to BSR disconnects and
SPR icon ready for Auto Disconnect
connection to return time (in min.)
Available SPR icon SPR icon

configured for available for
AutoConnect and accepting SPR
AutoDisconnect device through
AutoConnect
Figure 8-9: AutoDisconnect process

To define the interval for AutoDisconnect:

1. In the BSR Zoom window, from the Configuration menu, choose AutoConnect.
The AutoConnect dialog box appears, as displayed below:
Figure 8-10: AutoConnect dialog box
2. In the Minutes to AutoDisconnect field, enter the interval for returning the
status of the SPR index to AutoConnect after an SPR disconnects from the BSR
(i.e. index available for accepting an SPR with AutoConnect).
3. Click OK.
Note: The Number of Pings and Pings Interval fields are not applicable for
this ASWipLL release.

8.2.4. Task 3: Configure AutoConnect for SPR

For SPRs to connect to a BSR using AutoConnect, you need to enable the
AutoConnect feature for the SPRs.
You can enable AutoConnect for the following SPR types:
Pre-installed SPR: has no link with any BSR. Can be configured using
WipConfig through a serial connection, i.e. no IP connectivity with the SPR is
required.
SPR currently linked to a BSR: regular SPR that is currently connected to a
BSR. You can enable AutoConnect for this SPR using WipManage. As soon as
you enable AutoConnect and then reset the SPR, the SPR disconnects from the
BSR, and then connects to a BSR using AutoConnect.
8.2.4.1. Using WipConfig

The following procedure describes how to configure AutoConnect for an SPR using
WipConfig.
Warning: In this procedure, you need to reset the SPR to factory defaults.
This results in the deletion of the NVRAM frequency tables. Therefore, it is
recommended to save the NVRAM frequency tables before performing this
procedure.
To enable AutoConnect using WipConfig:

1. Connect the PC running WipConfig to the SPR using a serial connection.
2. Start WipConfig, and then connect to the SPR by clicking .

3. On the toolbar, click the Set Factory Default button.

4. Click Yes to confirm applying factory defaults to the device.


WipConfig applies factory default settings to the SPR.

6. Under the RF Configuration group, select the AutoConnect check box, as

displayed below:
AutoConnect
check box
selected
Figure 8-13: Selecting the AutoConnect check box


Notes:
1) You do not need to configure other parameters such as the BSR’s Air MAC
address, etc. This is because the SPR’s configuration parameters are later set
(by the BSR) when the SPR connects to the BSR through AutoConnect.
2) WipConfig displays the AutoConnect check box only if the SPR device
supports the AutoConnect feature.

8.2.4.2. Using WipManage

The following procedure describes how to configure AutoConnect for SPRs
currently connected to a BSR. This is performed using WipManage. In our example,
the SPRs disconnect from BSR (10.0.0.10) and then reconnect with AutoConnect to
the BSR (also 10.0.0.10) with the strongest RF signal.
To enable AutoConnect using WipManage:
1. In the BSR Zoom window, from the MultiDevices menu, choose AutoConnect.
Note: You can also redefine individual SPRs for AutoConnect in the SPR
Zoom window, by simply choosing the AutoConnect command from the
Configuration menu.

The Multi AutoConnect Configuration dialog box appears.
AutoConnect
check box
Figure 8-15: Enabling AutoConnect for currently connected SPRs
2. Select the AutoConnect check box.

3. Select the SPRs (e.g. 10.0.0.20 and 10.0.0.36) for which you want to enable
AutoConnect, and then click Apply.
The Multi Apply confirmation box appears, as displayed below.
Figure 8-16: Multi Apply confirmation box
4. Select the Apply Changes check box, and then click Apply.

The SPR is configured for AutoConnect (i.e. YES appears in the AutoConnect
column, as displayed below).
Figure 8-17: YES displayed for AutoConnect
5. Reset the SPR: from the MultiDevices menu, choose Reset.

6. Select the SPRs that you want to reset, and then click Apply.

Figure 8-19: Confirming SPR selection
7. Click Apply.
Figure 8-20: Confirming reset
8. Click Yes.

8.2.5. Task 4: Verify BSR-SPR Link

Once you have enabled AutoConnect for the SPRs and reset them, the SPRs
disconnect from the BSR and then using AutoConnect, connect to the BSR with
which it has the strongest RF signal. In WipManage, the BSR Zoom window
displays the SPR AutoConnect icons in green color, as displayed below:
Figure 8-21: SPRs connected to BSR using AutoConnect

8.3. Configuring AutoConnect with Redirection

You can configure an SPR to undergo AutoConnect only once. The SPR initially
(i.e. after reset or powered on) connects to a BSR with which it has the strongest RF
signal, but then disconnects and reconnects (i.e. redirected) to a specific BSR,
selected by the user. Even if the SPR is later reset or powered off and then on again,
the SPR always connects to the specific BSR (i.e. does not undergo AutoConnect).
The following subsections describe the procedures for configuring AutoConnect
with Redirection for SPR devices.
Notes:
1) If WipManage fails to redirect the SPR to the redirected BSR (due to some
problem), SPR remains connected to the BSR with which it connected initially
though AutoConnect.
2) SPR redirection can occur to the same BSR with which the SPR initially
connects through AutoConnect. In such a scenario, the SPR associates with
the same BSR, but with a different index number.
3) For redirection, all BSRs in the network must have the same Management
VLAN ID, Air Subnet, Managers Table, and Get/Set Community settings.


The steps for configuring AutoConnect with Redirection using WipManage are
described in the flowchart below.
Figure 8-22: Flow diagram of configuring AutoConnect (and Redirection)

8.3.2. Task 1: Enable WipManage to Receive

Redirection Traps
Before you start configuring AutoConnect with Redirection in WipManage, it is
recommended to enable WipManage to receive redirection traps.
To enable WipManage to receive AutoConnect traps:
1. In WipManage's Main window, from the Tools menu, choose Environment
Settings. The Environment Settings dialog box appears, as displayed below.
Selected check
box for receiving
Redirection traps
Figure 8-23: Environment Settings dialog box - Traps Settings tab
2. Select the SPRs Redirection After AutoConnect check box.

3. Click OK.

8.3.3. Task 2: Add "Fixed" SPRs

The first step in configuring AutoConnect in the ASWipLL system is to define a
range of "fixed" SPRs. These SPR indexes will be used later to accept SPRs
redirected to them that initially connected to a BSR through AutoConnect. These
fixed SPRs must be added in the BSR to which you want the SPRs to be redirected.
In our example, the SPRs will be redirected to BSR 10.0.0.10.
To add "fixed" SPRs:
SPRs.
(e.g. 2).
(e.g. 43).

4. In the First SPR IP Address field, enter the IP address of the first SPR, e.g.
30.0.0.1.
5. From the Status drop-down list, select Enabled.
6. In the Auto Disconnect drop-down list, select Off.
7. In the Subnet Mask field, enter Subnet Mask address (e.g. 255.255.255.248).
The subnets should be defined by mask. A calculator is provided to determine
optimal efficiency.
8. If required, select the Add to Static Route Table check box.
Note: For transparent bridging, clear the Add to Static Route Table check
box.

9. Click OK.
The defined fixed SPR indexes (e.g. SPR indexes 2 to 43) are displayed below:
Figure 8-26: Added "fixed" SPR index icons (2 to 43) displayed in BSR Zoom window
Note: The newly added SPRs are only added to the ASWipLL database when
you edit them (i.e. when you define the SPRs for Redirection).
8.3.4. Task 3: Add AutoConnect SPRs

Once you have defined "fixed" SPRs, you need to add a range of AutoConnect SPR
icons for accepting newly installed, powered-on SPRs. The SPR icons are defined
with temporary IP addresses, which the BSR temporarily assigns the SPR devices
for communication and reconfiguration. The SPR devices should only AutoConnect
to BSRs that are in the same network.

You can define AutoConnect SPR index icons for all your BSRs. For clarity, in our
example, we will define AutoConnect SPRs for BSR 10.0.0.10 (i.e. the same BSR
for which we defined fixed SPRs).
Notes:
1) Ensure the WipManage PC IP address is defined in WipManage’s BSR
Managers Table.
2) BSR associated configuration traps should be checked in the WipManage
main window (i.e. the SPRs Redirection after AutoConnect check box)

SPRs.
(e.g. 65)
(e.g. 127).

20.0.0.1).
6. In the Auto Disconnect drop-down list, select On to enable this feature.
7. In the Subnet Mask field, enter Subnet Mask address. The subnets should be
defined by mask. A calculator is provided to determine optimal efficiency.
8. If required, select the Add to Static Route Table check box.

9. Click OK.
The added AutoConnect SPR icons (e.g. SPR indexes 65 to 127) are displayed
in Figure 8-29.
Figure 8-29: Added AutoConnect SPRs (65 to 127) in BSR Zoom window
The AutoConnect SPR icons are highlighted yellow (i.e. no communication link
between the SPR and BSR), and display the letter "A" (i.e. indicating that the
SPR icon is available for accepting an SPR through AutoConnect)/
Note: The added AutoConnect SPR icons are only added to the ASWipLL
database when you edit them or when an SPR device connects to them.

8.3.5. Task 4: Define AutoDisconnect Interval

The AutoDisconnect interval is the time that an SPR index configured for
AutoConnect, and after an SPR losses connection with the BSR, becomes available
for accepting another SPR using AutoConnect. The interval between losing the
connection and becoming available again for accepting an SPR through
AutoConnect is called the AutoDisconnect interval.
To define the interval for AutoDisconnect:
1. In the BSR Zoom window, from the Configuration menu, choose AutoConnect.
The AutoConnect dialog box appears, as displayed below:
Figure 8-30: AutoConnect dialog box
2. In the Minutes to AutoDisconnect field, enter the interval for returning the
status of the SPR index to AutoConnect after an SPR disconnects from the BSR
(i.e. index available for accepting an SPR with AutoConnect).
3. Click OK.
Note: The Pings Interval and Number of Pings fields are only applicable for
previous ASWipLL releases.

8.3.6. Task 5: Configure "Fixed" SPRs for Redirection

Once you have added a range of fixed SPR icons, you need to define for these SPR
indexes the SPR device's Ethernet MAC address of the SPR device that you want
connected to these indexes.
This SPR’s Ethernet MAC address for the SPR index icon, corresponding to the
associated BSR, is stored in the ASWipLL database. After an SPR initially connects
to a BSR using AutoConnect, WipManage searches the ASWipLL database for the
SPR’s Ethernet MAC address. If it locates this address defined for an SPR index,
WipManage then redirects the SPR to the BSR with which this SPR index is
associated.
To define redirection for an SPR:
1. In the BSR Zoom window, from the Configuration menu, point to SPRs, and
then choose Permitted SPRs.
The Permitted SPRs Table dialog box appears, as displayed below:
Figure 8-31: Permitted SPRs Table dialog box

2. Select the fixed SPR for which you want to configure redirection, and then click
Edit.
The Permitted SPRs Edit dialog box appears.
Figure 8-32: Permitted SPRs Edit dialog box
3. To define redirection for the SPR, perform the following:

Select the AutoConnect Redirection check box.
In the Redirection Eth. MAC Address field, enter the SPR’s Ethernet MAC
address (e.g. 2001F0). This is the SPR device that you want redirected to this
BSR (10.0.0.10) after the SPR has performed AutoConnect.

Notes:
1) The SPR’s Ethernet MAC address appears on the SPR’s front chassis.
2) Enter only the last six digits of the SPR’s Ethernet MAC address.
4. Click OK to close the Permitted Add dialog box.

The Permitted SPRs Table dialog box displays the SPR’s Ethernet MAC address
in the Redirection Eth. MAC column.
SPR’s Ethernet MAC address for redirection
Figure 8-33: SPR’s Ethernet MAC address defined
5. To define the Ethernet MAC addresses of additional fixed SPRs, see Step 2.

8.3.7. Task 6: Power on or Reset SPR Device

Once you have added AutoConnect SPR indexes and fixed SPR indexes for
Redirection, you can install and power on the unconfigured SPR device.
The following figures display the AutoConnect-Redirection process in WipManage
when the SPR device is powered on:
The powered on SPR device first connects to the BSR (e.g. 10.0.0.10) using
AutoConnect. The figure below displays the AutoConnect SPR index 65 icon to
which the SPR device connects in the BSR using AutoConnect.
Figure 8-34: SPR connected to BSR using AutoConnect (AutoConnect SPR index 65)

When WipManage locates the SPR’s Ethernet MAC address in the database, the
SPR device disconnects from BSR 10.0.0.10 (i.e. the AutoConnect SPR index 65
loses connection), and then the SPR device reconnects to the BSR (e.g. 10.0.0.10)
with the defined fixed SPR (i.e. SPR index 2) containing the SPR’s Ethernet MAC
address. The figure below displays the fixed Redirection SPR index 2 icon to which
the redirected SPR device connects in the BSR.
Figure 8-35: SPR redirected to BSR (fixed SPR index 2)

8.4. Redirecting Previously Redirected SPRs

WipManage allows you to redirect, once again, an SPR that was previously
redirected to a BSR after initially undergoing AutoConnect.
Notes:
1) Although redirection can be performed to a different BSR than the BSR to
which the SPR device originally connects using AutoConnect, for clarity, our
example uses the same BSR (i.e. 10.0.0.10) for AutoConnect and Redirection.
2) When the SPR is redirected, the previous SPR’s entry (i.e. index # 2) in the
ASWipLL database is deleted, and the new SPR (i.e. index # 6) defined by its
new Ethernet MAC address, is entered in the database with its associated
BSR.


Figure 8-36 displays a flow chart describing the steps for redirecting a previously
redirected SPR, to another BSR (or SPR index).
Figure 8-36: Flow chart for redirecting a previously redirected SPR

8.4.2. Task 1: Add a "Fixed" SPR for Redirection

You first need to define redirection in a "fixed" SPR icon that is associated with a
BSR to which you want the SPR device to reconnect.
To define redirection for an SPR:
1. In the BSR Zoom window of the BSR to where you want the SPR device to be
redirected, right-click a fixed SPR (e.g. SPR index 6), and then from the
shortcut menu, choose Edit.
Figure 8-37: Permitted SPRs Edit dialog box for defining redirection
2. Select the AutoConnect Redirection check box.

3. In the Redirection Eth. MAC Address field, enter the SPR’s Ethernet MAC
address (e.g. 2001F0).
4. Click OK.
The Ethernet MAC Address Exists confirmation box appears, informing you that
this SPR device has already undergone redirection to a BSR.
Figure 8-38: Ethernet MAC Address Exists confirmation box
5. Click Yes to change SPR’s original redirection location.

8.4.3. Task 2: Add an AutoConnect SPR

Before you can reconfigure AutoConnect for the SPR, you need to add SPR indexes
for AutoConnect. The SPR devices should only AutoConnect to BSRs that are in the
same network.
For clarity, in our example, we will define AutoConnect SPR icons for BSR with IP
address 10.0.0.10.
Note: Ensure the WipManage PC IP address is defined in WipManage’s BSR

Managers Table.

SPRs, as displayed below.
Figure 8-39: Choosing the Add Range Permitted SPRs command

The Add Range Permitted SPRs dialog box appears.
(e.g. 2)
(e.g. 3).
10.0.0.12).
6. From the Auto Disconnect drop-down list, select On to enable this feature.
7. Select the Add to Static Route Table check box, and then in the Subnet Mask
field, enter Subnet Mask address.
Note: If the SPRs are in transparent bridge mode, clear the Add to Static
Route Table check box.

8. Click OK.
The added AutoConnect SPR icons (e.g. SPR indexes 2 and 3) are displayed in
Figure 8-29.
Figure 8-41: Added AutoConnect SPRs (2 and 3) in BSR Zoom window
8.4.4. Task 3: Redefine AutoConnect for Currently

Redirected SPR
You now need to return the currently connected SPR (that connected to the BSR by
redirection), to AutoConnect.
To redefine a redirected SPR for AutoConnect:
1. In the BSR Zoom window, from the MultiDevices menu, choose AutoConnect.

Note: You can also redefine individual SPRs for AutoConnect in the SPR
Zoom window, by simply choosing the AutoConnect command from the
Configuration menu.
The Multi AutoConnect Configuration dialog box appears.
Figure 8-42: Defining AutoConnect for currently connected and redirected SPRs

2. Select the AutoConnect check box.

3. Select the permitted SPR (e.g. 30.0.0.1) that you want to redirect to a different
BSR, and then click Apply.
The Multi Apply confirmation box appears, as displayed below.

The SPR is configured for AutoConnect (i.e. YES appears in the AutoConnect
column, as displayed below).
5. Click Close.

8.4.5. Task 4: Reset the SPR Device

Resetting the SPR disconnects the SPR from the BSR. The SPR device then
connects to a BSR using AutoConnect, and thereafter undergoes redirection to
connect to the BSR to which it is associated (as defined in Section 8.4.2, "Task 1:
Add a "Fixed" SPR for Redirection").
To reset the SPR device:
1. In the BSR Zoom window, from the MultiDevices menu, choose Reset.
The Multi Reset dialog box appears, as displayed below.
Figure 8-45: Multi Reset dialog box

2. Select the SPR (i.e. 30.0.0.1 – index #2) that you want to reset, and then click
Apply.
The Multi Apply confirmation box appears.
The Reset confirmation box appears.
Figure 8-47: Reset confirmation box
4. Click Yes to confirm SPR device reset.

The SPR resets, disconnects from the current BSR (i.e. SPR index 2 icon
disconnects), automatically reconnects to the BSR with the strongest RF signal
using AutoConnect), and then is redirected to the BSR containing the SPR’s
Ethernet MAC address.
Note: The previous SPR’s entry (i.e. index # 2) in the ASWipLL database is
deleted, and the new SPR (i.e. index # 6) defined by its new Ethernet MAC
address is entered in the database, with its associated BSR.

The following figures display the process in WipManage’s BSR Zoom window
when redirecting a previously redirected SPR device.
Figure 8-48: Connected SPR (index #2) that was previously redirected
Figure 8-49: Disconnected SPR (index #2) due to reset to AutoConnect

Figure 8-50: Connected SPR (index #65) using AutoConnect
Figure 8-51: SPR (index #65) redirected to BSR (i.e. SPR index #6)

8.5. Color-Coding of AutoConnect SPR Icons

The format of the AutoConnect SPR icon depends on whether the SPR is defined
with AutoDisconnect. When the SPR icon is defined as AutoConnect with
AutoDisconnect, a black-colored triangle appears in addition to the AutoConnect
symbol (i.e. "A"), as displayed below.
Triangle indicating AutoConnect
with AutoDisconnect
Figure 8-52: SPR icon defined as AutoConnect with AutoDisconnect
When the SPR icon is defined as AutoConnect, but without AutoDisconnect, the
SPR icon displays only the AutoConnect symbol (i.e. "A"), as displayed below.
Figure 8-53: SPR icon defined only as AutoConnect
Note: When an SPR device disconnects from the SPR icon defined for
AutoConnect with AutoDisconnect, the SPR icon returns to the AutoConnect
state, ready to accept another SPR device. In contrast, when an SPR device
disconnects from the SPR icon defined only with AutoConnect, the SPR icon
loses its AutoConnect configuration and changes to a fixed SPR icon.
When an SPR device connects to a BSR using the SPR icon configured for
AutoConnect without AutoDisconnect, the SPR icon changes to a normally
connected SPR icon. When the SPR device losses connection with the BSR, the
SPR icon changes to a normal fixed SPR icon without air link or IP routing link.
Figure 8-54 depicts this process of an SPR icon configured for AutoConnect
(without Auto Disconnect).

Figure 8-54: Connected and disconnected SPR icon configured for AutoConnect
Table 8-1 provides a summary of the color-coding of the AutoConnect SPR icons.
Table 8-1: Description of status of AutoConnect SPR icons

SPR Air link Network link Description
icon (color of (color of
circle) rectangle)
Yellow with Red SPR icon defined for AutoConnect (without
"A" Disconnect) and available for accepting an SPR
device connecting to BSR via AutoConnect.
Yellow with Red SPR icon defined for AutoConnect with
"A" and AutoDisconnect is available for accepting an SPR by
triangle AutoConnect.
Green with Green SPR icon defined for AutoConnect with
triangle AutoDisconnect, has an SPR device connected to it
with air link with BSR, and IP routing link with PC
running WipManage. The SPR that is connected to
this icon may be connected by AutoConnect or
regular means.
Yellow with Red SPR icon defined for AutoConnect with
triangle AutoDisconnect in the BSR has lost connection with
SPR device and is undergoing AutoDisconnect (see
Section 8.3.5, "Task 4: Define AutoDisconnect
Interval").

8.6. AutoConnect Trap Messages

You can check whether AutoConnect and AutoConnect Redirection processes have
occurred successfully by viewing WipManage’s trap messages. These trap messages
can be viewed in the Traps pane of the WipManage main window, as displayed
below.
Traps pane
displaying
AutoConnect
trap
Figure 8-55: Main window displaying AutoConnect traps

The description of the AutoConnect trap messages are described in Table 8-2
Table 8-2: Description of AutoConnect trap messages

Trap Message Meaning
AutoConnect: On: <SPR index The SPR index number is in AutoConnect
number> mode (after an SPR device disconnected from it
and AutoDisconnect interval has ended),
available for accepting an SPR device
connecting to BSR using the AutoConnect
feature.
AutoConnect: Off: <SPR index The SPR index (for AutoConnect) has an SPR
number> device connected to it using AutoConnect and
is therefore, not in available for receiving
another SPR through AutoConnect.
AutoConnect to <BSR IP address>- SPR device was connected to the BSR using
<SPR index icon>, <SPR’s AutoConnect feature.
Ethernet MAC address>-<connected
to BSR at certain decibels
(dBm)>. Ver: <SPR device’s
software version>
<SPR’s Ethernet MAC Address> was The SPR was automatically connected to the
AutoConnected more than once BSR using AutoConnect more than once. This
indicates that the SPR Ethernet MAC address
already exists in WipManage’s database, and
thus, the SPR was not successfully redirected.
<SPR’s Ethernet MAC address> The SPR was redirected.
after redirect
<SPR’s Ethernet MAC address> is The SPR is configured for redirection, but
not set for redirection WipManage cannot locate the SPR’s Ethernet
MAC address in the database.


9
Configuring a Point-to-Point
Radio Link
This chapter describes basic procedures for configuring a point-to-point wireless
link using ASWipLL’s PPR device.
Overview
Summary of Tasks
Task 1:Configure the PPR
Task 2: Configure the SPR
Task 3: Test the PPR-SPR Link
Note: This chapter mentions the SPR device. However, all SPR procedures
described in this chapter are also applicable for IDR devices. In other words,
this chapter is also relevant for establishing a PPR-IDR link.

Configuring a Point-to-Point Radio Link Commissioning Manual
9.1. Overview
ASWipLL’s Point-to-Point Radio (PPR) device is implemented in point-to-point
radio links operating in the 2.4 GHz, 3.4 GHz to 3.8 GHz, and 5.8 GHz bands. The
PPR provides a secure and reliable point-to-point wireless link with a single remote
ASWipLL device (i.e. SPR).
PPR provides real-time adaptive modulation (2-, 4-, 8-level FSK) and Auto
Retransmission Request (ARQ): features that offer high quality connectivity whilst
maximizing spectrum utilization.
The PPR can deliver up to 4 Mbps using a 1.33 MHz channel, and is fully packet-
based. If more than 4 Mbps bandwidth is required between two end points, two or
more links can be installed in parallel. For two links, ASWipLL uses IP routing: one
link routes IP traffic in the uplink; and another link, routes IP traffic in the downlink.
A third link can be added to bridge mainly PPPoE traffic in uplink and downlink.
The PPR device is similar to the BSR in that it performs IP routing and PPPoE
bridging, transparent bridging, as well as all the other BSR software features. The
only difference between the PPR’s and BSR’s software features is that the PPR is
part of a point-to-point link, in other words, only a single SPR can be associated
with the PPR.
The PPR typically communicates with an SPR providing a high-antenna gain. The
PPR at the near end, and the SPR at the far end, both connect to the local network
through ASWipLL’s SDA devices.

Commissioning Manual Configuring a Point-to-Point Radio Link
In WipManage, the configuration of the PPR device is performed in a modified BSR

Zoom window. This window is similar to the regular BSR Zoom window, except
that it allows PPR communication with only one SPR device by providing only one
available SPR index number, as displayed in the following figure:
Figure 9-1: BSR Zoom window displaying a single SPR index for PPR
In the figure, only one SPR index is available for adding an SPR. This available SPR
index is calculated using the suffix of the PPR’s Air Mac address.

The following describes the procedure for calculating the SPR's index number:
If S = PPR’s Air MAC address suffix
If N = S mod 126
If N<2
N = N + 126
The following table lists examples of SPR indexes calculated from the PPR’s Air
MAC address suffix:
Table 9-1: SPR index calculated from PPR's Air MAC address
PPR Air Mac address suffix SPR index
Hexadecimal Decimal
XX:00 0 126
XX:01 1 127
XX:02 2 2
… … …
XX:7D 125 125
XX:7E 126 126
XX:7F 127 127
128 2
… … …
XX:FD 253 127
XX:FE 254 2
XX:FF 255 3

For clarity, the procedures described in this chapter are based on the following
configuration example:
Figure 9-2: Configuration example for PPR setup


The flowchart in Figure 9-3 displays a summary of tasks for configuring a point-to-
point wireless link between a PPR and an SPR.
Figure 9-3: Flowchart for configuring PPR in ASWipLL
9.3. Task 1:Configure the PPR

You need to use WipConfig to configure the PPR. This includes defining an SPR
(by IP address) with which the PPR will form a point-to-point radio link. It is
recommended to configure the PPR through a serial connection.

To configure a PPR (WipConfig):

1. Connect the PC running WipConfig to the PPR.
2. Start WipConfig.
WipConfig connects to the PPR (i.e. IP address 10.0.0.10).
PPR
Configuration
button
Figure 9-4: WipConfig connected to PPR device




6. From the Mode drop-down list, select one of the following options:
Bridge: transparent bridge mode
Router: IP router mode
Note: If in the PPR’s ROM, the PPR is defined as an IP router, then the Mode
field displays Router; If the PPR is defined for transparent bridging, then the
7. In the Eth IP Address field, enter the PPR's IP address (e.g. 10.0.0.10).

8. In the Eth Subnet Mask field, enter the PPR's subnet mask address (e.g.
255.255.255.240).
9. In the RF Configuration group, in the BSR Air MAC Address, enter the PPR's
Air MAC, e.g. 0x1200. Valid ranges are from 0x0000 to 0xFFFF.
10. To define a point-to-point radio link with an SPR, click the PPR Configuration
button. The PPR Configuration dialog box appears, as displayed below.
Figure 9-7: PPR Configuration dialog box
Notes:
1) The PPR Configuration button only appears in WipConfig if the device to
which WipConfig connects is a PPR.
2) The SPR Index field is read-only. WipConfig automatically calculates the
SPR index number by using an algorithm based on PPR's Air MAC address
(e.g. 0x1200 results in SPR index #126).
a. In the IP Address field, enter the SPR's IP address (e.g. 10.0.0.20) with
which the PPR will create a point-to-point radio link.
b. In the Subnet Mask field, enter the subnet mask address of the SPR (e.g.
255.255.255.240) with which the PPR will create a point-to-point radio link.
c. Click Accept.

12. On the toolbar, click the Reset button to reset the PPR.
9.4. Task 2: Configure the SPR

After you have configured the PPR (e.g. with an Air MAC address) in Section 9.3,
"Task 1:Configure the PPR", you need to configure the SPR with which the PPR
will communicate in a point-to-point radio link. This SPR configuration is
performed using WipConfig.
If you want to configure the SPR for transparent bridging, you need to define the
SPR's IP and subnet addresses so that the SPR is in the same subnet as the PPR.
It is recommended to configure the SPR through a serial connection.
To configure the SPR (WipConfig):
2. Start WipConfig.


WipConfig connects to the SPR (i.e. IP address 10.0.0.20).
PPR button
Figure 9-9: SPR Configuration pane

5. Apply factory default settings to the BSR by performing the following:



6. From the Mode drop-down list, select one of the following options:
Bridge: transparent bridge mode
Router: IP router mode
Note: If in the SPR's ROM, the SPR is defined as an IP router, then the Mode
field displays Bridge; If the SPR is defined for transparent bridging, then the
Mode field displays Router.
7. In the Eth IP Address field, enter the SPR's IP address (e.g. 10.0.0.20).

8. In the Eth Subnet Mask field, enter the SPR's subnet mask address (e.g.
255.255.255.240) so that it is in the same subnet as the PPR.
PPR’s Air MAC address to which the SPR is associated, e.g. 0x1200. Valid
ranges are from 0x0000 to 0xFFFF.
significant bytes (MSB), e.g. the two left-most bytes, and not the least
significant bytes (LSB), e.g. the right-most bytes. For example, a typical Air
MAC address would be "AB00", where the zeros represent the LSB.
10. Click the PPR button.

The Index in BSR field displays the SPR's index number associated with the
PPR. This index number is calculated using an algorithm based on the PPR's Air
MAC address that you entered in the BSR Air MAC Address field (e.g. Air
MAC address is 0x1200, therefore, the SPR’s index is 126).

The SPR device is configured for PPR, with an index number based on PPR’s
Air MAC address, as displayed below.
SPR index
automatically
entered after
clicking PPR
button
Figure 9-13: SPR configured for PPR (e.g. SPR index according to PPR’s Air MAC)
Note: If WipManage contains a BSR with the same IP address as the PPR,
before you can add the PPR in WipManage, you need to first delete this BSR.

9.5. Task 3: Test the PPR-SPR Link

You can test the link between the PPR and SPR by pinging the SPR from a PC
located behind the PPR.
From the PC/Laptop (IP address 10.0.0.2) behind the PPR, open an MS-DOS


10
Configuring a Repeater
Solution
This chapter describes the procedures for configuring a back-to-back (i.e. BSR-to-
SPR) repeater solution in the ASWipLL network using a BSR and SPR.
Overview
Summary of Tasks
Task 1: Add BS-1 and BS-2
Task 2: Add BSR-1 and BSR-2
Task 3: Define BSR-1’s Default Gateway
Task 4: Define BSR-2’s Default Gateway
Task 5: Add SPR-1 and SPR-2
Task 6: Add Routes for SPRs behind BSR-2 toward SPR-1
Task 7: Define SPR-1’s Default Gateway
Task 8: Add Routes for SPRs behind BSR-2 toward BSR-2
Task 9: Define SPR-2’s Default Gateway
Note: This chapter mentions the SPR device. However, all SPR procedures
described in this chapter are also applicable for IDR devices. In other words,
this chapter is also relevant for establishing a repeater solution using BSR-IDR
back-to-back link.

Configuring a Repeater Solution Commissioning Manual
10.1. Overview
ASWipLL devices can be used to provide repeater functionality. This is
implemented in scenarios in which the BSR needs to be "extended" to remote
subscriber sites that are blocked by obstacles (such as trees, hills, and other typical
line-of-sight obstructions) or that the BSR-SPR transmission is out-of-range.
Back-to-back Ethernet connectivity of a BSR with an SPR provides the repeater
capability, as displayed in the figure below.
Figure 10-1: ASWipLL back-to-back (SPR-to-BSR) repeater solution

Commissioning Manual Configuring a Repeater Solution
In Figure 10-1, BSR A is part of an ASWipLL Base Station that is connected to the
service provider’s backbone. BSR A serves multiple SPRs, marked as SPR A1,
SPRAi and so on. Two SPRs—SPR B1 and SPR B2—cannot communicate directly
with the ASWipLL Base Station due to non-line-of-site factors. Therefore, an SPR
acts as a repeater by connecting back-to-back with a BSR
(BSR B), which serves SPR-B1 and SPR-B2.
Notes:
1) Careful RF planning is required to cope with issues such as interferences
and delay that are introduced by the repeater solution. For example, if the
system is used as a frequency hopping system, GPS may be required at each
Base Station.
2) Space and frequency isolation between the "repeater SPR" and BSR B is
required.
3) To avoid radio interferences between the neighboring BSR-B and SPR,
either orthogonal tables or totally different frequencies range should be
assigned to the two.
4) Bandwidth management should be calculated to support the "repeater
bandwidth".
5) As the configuration functions as two separated cells, managed by BSR-A
and BSR-B, additional configuration related to RF operation is required.
6) IP addressing and routing tables should be configured to support the
repeater solution.
7) In the IP Router mode, only the SPR and BSR at the repeater site must be
in the same subnet. In the Bridge mode, all the devices must be in the same
subnet.


The flowchart in Figure 10-2 displays a summary of tasks for configuring a back-to-
back (SPR-to-BSR) repeater solution.
Figure 10-2: Flowchart for configuring a back-to-back ASWipLL repeater solution

For clarity, the back-to-back repeater procedures described in this chapter are based
on the following basic configuration:
Figure 10-3: Configuration example for configuring a back-to-back ASWipLL repeater

solution

10.3. Task 1: Add BS-1 and BS-2

The first task that you need to perform is to add Base Stations BS-1 and BS-2. These
Base Stations are located in different geographical areas. BS-1 represents the
ASWipLL Base Station consisting of BSR-1 (associated with SPR-1); BS-2
represents the repeater Base Station consisting of BSR-2 (associated with SPR-2,
and connected to SPR-1 via Ethernet hub SDA).
To add Base Stations BS-1 and BS-2:
1. In WipManage’s Main window, right-click in the workspace area, and then from
the shortcut menu, choose Add BS, as shown below.
Choosing Add
BS from
shortcut menu
Figure 10-4: Choosing the Add BS command from the shortcut menu

The WipManage-BS-Add dialog box appears:
Figure 10-5: WipManage-BS-Add dialog box
2. In the BS Name field, enter the BS name (i.e. BS-1 or BS-2), and then click OK.

The newly added Base Stations appear in the WipManage Main window, as
shown below.
Figure 10-6: WipManage Main window displaying added Base Stations
10.4. Task 2: Add BSR-1 and BSR-2

The next task is to add BSR-1 and BSR-2 to Base Station BS-1 and BS-2,
respectively. The following procedure only relates to adding BSR-1 to BS-1.
However, this procedure is similar for adding BSR-2 to BS-2.
To add BSR-1 to BS-1:
1. Double-click the BS-1 icon.

2. Right-click one of the blue rectangles, and then from the shortcut menu, choose
Add BSR, as shown below.
Choosing Add
BSR from
shortcut menu
Figure 10-7: Choosing the Add BSR command from the shortcut menu
The WipManage-BSR-Add dialog box appears.
Figure 10-8: Adding BSR-1

3. In the Manage IP field, enter 10.1.1.1 for the IP address of BSR-1. (10.1.2.2 for
BSR-2).
4. In the Name field, enter a Name.
5. Click OK.
The BSR-1 and BSR-2 are added, as shown below (e.g. BSR-1 added to BS-1).
Figure 10-9: Added BSR-1 to BS-1

Double-click BSR-1 to open the BSR Zoom window, shown below.
Figure 10-10: BSR Zoom window of BSR-1

10.5. Task 3: Define BSR-1’s Default Gateway

You need to define BSR-1’s default gateway, which is the router that is connected to
the Internet Network. To define the default gateway you need to enter the router’s IP
address.
To define BSR-1's default gateway:
1. In the BSR Zoom window for BSR-1, from the Configuration menu, point to
Network, and then choose Static Routing Table. The Static Routing Table
dialog box appears.
Figure 10-11: Static Routing Table dialog box

2. Select the Enable Default Gateway check box, and then enter the following:
IP address of the router connected to the Internet network (i.e. IP world)
In the Metric field, enter "1"
Figure 10-12 displays the defined default gateway to the Internet network.
Figure 10-12: Defining default GW

10.6. Task 4: Define BSR-2’s Default Gateway

You need to define BSR-2’s default gateway as SPR-1 (i.e. IP address 10.1.2.1).
This is performed in the BSR Zoom window of BSR-2.
To define the BSR-2’s default gateway:
dialog box appears.
2. Select the Enable Default Gateway check box, and then enter the following:
IP address of SPR-1 (e.g. 10.1.2.1)
In the Metric field, enter "1"
The figure below displays BSR-2’s default gateway (i.e. SPR-1).
Figure 10-13: Defining BSR-2’s default gateway

10.7. Task 5: Add SPR-1 and SPR-2

Once you have added the BSRs, you can add the SPRs associated with these BSRs.
When you add the SPR, you need to add the SPR’s IP address as well as the route
for the BSR to reach the SPR.
The following procedure describes how to add SPR-1 to BSR-1. This procedure is
similar to adding SPR-2 to BSR-2.
To add SPR-1 to BSR-1:
1. Double-click the BSR-1 icon. The BSR Zoom window appears.

2. Right-click the available SPR index (SPR index 2 in this example), and then
from the shortcut menu, choose Add, as shown below.


3. In the IP Address field, enter the IP address of the SPR-1 (10.1.2.1).
4. In the Name field, enter the name of the SPR-1.
Figure 10-15 displays an example of the Permitted SPRs – Add dialog box.
IP address of SPR-1

5. Add a route for the BSR-1 to reach SPR-1 by performing the following:
a. Click Route. The Static Routing Table per SPR dialog box appears.
b. Click Add.
Figure 10-17: Adding static route

c. In the Destination field, enter the IP address of SPR-1 (i.e. 10.1.2.1).

d. In the Route Mask field, enter SPR-1 subnet mask (i.e. 255.255.255.0).
e. Click OK.
6. Click Close, and then OK.
The SPR-1 icon is added to BSR-1 (10.0.0.10), as shown below.
Figure 10-18: Added SPR-1 to BSR-1

10.8. Task 6: Add Routes for SPRs behind BSR-

2 toward SPR-1
You need to define routing entries to all SPRs behind BSR-2, toward SPR-1. This
enables BSR-1 to know the route to SPR #2, located behind the repeater site (i.e.
behind BSR #2).
To add routes for SPRs behind BSR-2 toward SPR-1:
dialog box appears.

2. In the Static Routing Table dialog box, click Add. The Static Route Table – Add
dialog box appears.
Figure 10-20: Defining routing entry
a. In the Destination field, enter the IP address of SPR #2 (i.e. 10.1.3.1).

WipManage automatically calculates the correct destination route.
b. In the Route Mask field, enter the subnet mask of the SPR #2.
c. For the Next Hop, select the SPR check box, and then select the SPR index
number (i.e. 2) for which SPR #1 is defined. This indicates that for BSR #1
to reach SPR #2, it must route through SPR #1.

3. Click OK.
Added static route shown below.
Figure 10-21: Added route from SPR-2 (behind BSR-2) toward SPR-1

10.9. Task 7: Define SPR-1’s Default Gateway

You need to define SPR-1’s default gateway as BSR-1. You define this is the SPR
Zoom window of SPR-1.
To define SPR-1’s default gateway:
1. In the SPR Zoom window for SPR-1, from the Configuration menu, point to
dialog box appears.
2. Select the Enable Default Gateway check box, and then click the BSR check
box to define BSR-1 as the SPR-1’s default gateway.
Figure 10-22: Defining SPR-1’s default gateway as BSR-1

10.10. Task 8: Add Routes for SPRs behind

BSR-2 toward BSR-2
You now need to add static routing entries to allow SPR-1 to send traffic to SPR-2,
located behind BSR-2. Therefore, the static route is defined by the IP address and
subnet of SPR-2 as well as the hop to reach this destination, which is via BSR-2.
This is a static route of SPRs behind BSR-2 toward the IP address of BSR-2 (which
is on the same subnet as SPR-1). Therefore, these definitions are defined in SPR-1
(i.e. 10.1.2.1), in the SPR Zoom window.
To add routes for SPRs behind BSR-2 toward BSR-2:
dialog box appears.

2. In the Static Routing Table, click Add. The Static Route Table – Add dialog box
appears.
Figure 10-24: Adding routes for SPRs behind BSR-2 toward BSR-2
3. Add static routing entries:

a. In the Destination field, enter the IP address of SPR #2 (i.e. 10.1.3.1).
WipManage automatically calculates the correct destination route.
b. In the Route Mask field, enter the subnet mask of SPR #2.
c. For the Next Hop, enter the IP address of BSR-2 through which SPR-1 has
to route traffic in order to reach SPR-2.

4. Click OK.
The added route is displayed in the Static Routing Table dialog box, as displayed
below.
Figure 10-25: Added route for SPR-1 to SPR-2

10.11. Task 9: Define SPR-2’s Default Gateway

You need to define SPR-2’s default gateway as BSR-2. This is performed in the
SPR Zoom window of SPR-2.
To define SPR-2’s default gateway:
dialog box appears.
2. Select the Enable Default Gateway check box, and then click the BSR check
box to define BSR-2 as the SPR-2’s default gateway.
All other SPRs associated with BSR-2 must be configured in the same way as
described above.

11
Managing Bandwidth
This chapter describes the procedures for managing the bandwidth in the ASWipLL
system, and includes the following sections:
Overview
Configuring Asymmetric Bandwidth
Summary of Tasks
Task 1: Enable Asymmetric Bandwidth Policy
Task 2: Define Downlink and Uplink CIR and MIR Values
Note: This chapter mentions the BSR and SPR devices. However, the BSR
procedures are also applicable for PPR devices; and the SPR procedures are
also applicable for IDR devices.

M a n a g i n g B a n dw i d t h Commissioning Manual
11.1. Overview
The ASWipLL system allows operators and service providers to manage the
bandwidth policy allocated to their subscribers, assuring optimal network
performance. The bandwidth policy is per BSR, and thus, applies to all SPRs
associated with the BSR.
ASWipLL allows operators to define a maximum bandwidth for each subscriber,
referred as maximum information rate (MIR). In addition, ASWipLL allows
operators to provide a guaranteed bandwidth, referred as committed information rate
(CIR), to a subscriber even when the network is loaded. Typically, subscribers pay
different rates for the levels of desired bandwidth commitment. Different levels of
CIR and MIR can be sold as different services (e.g. Platinum, Gold, Silver, and
Bronze) at different prices.
ASWipLL allows the operator to implement the following bandwidth policies:
Asymmetric CIR/MIR: different downlink and uplink values for CIR and MIR.
In other words, you need to define CIR and MIR values for downlink, as well as
define CIR and MIR values for uplink. Downlink refers to traffic from Base
Station to subscriber; uplink refers to traffic from subscriber to Base Station.
This is useful in applications such as cable TV (CATV), where a higher
downlink bandwidth is needed than in uplink.
Aggregated CIR/MIR: CIR and MIR values defined for the sum of the
downlink and uplink traffic. In other words, you need to define one CIR value
that applies to both downlink and uplink, and define one MIR value that applies
to both downlink and uplink. This is useful when there exists varying bandwidth
demands on the network, different applications, or different user types. For
example:
MIR (downlink and uplink): 1500 bps
CIR (downlink and uplink): 256 bps
No bandwidth policy: subscriber receives MIR, but if the network is unable to
maintain this bandwidth, the subscriber receives less. This is an unpredictable
bandwidth policy, whereby the subscriber may receive no bandwidth at all. In
addition, no proportional degradation is implemented in this policy.

Commissioning Manual Managing Bandwidth
When the total CIR of active SPRs is greater than the available bandwidth for data
(CIR overbooking), ASWipLL implements its CIR Proportional Degradation
feature. CIR overbooking can derive from the following:
Large number of active SPRs (running data)
Large number of VoIP calls
Modem rate decreases to an unexpected value
Poor RF conditions (may be relevant even in a, e.g. fixed modem rate)
In the event of CIR overbooking, the CIR decreases in proportion to the configured
CIR of the SPRs. In other words, each SPR receives bandwidth that equals to
k*configured CIR, where 0<k<1 (k is referred to as the proportion factor).
Therefore, the proportion between CIR bandwidth values of all SPRs is maintained.
11.2. Configuring Asymmetric Bandwidth

The subsections below describe procedures for configuring Asymmetric CIR and
MIR bandwidth for multiple SPRs. In our example, the SPRs are configured with
the following CIR and MIR values:
For downlink (i.e. BSR to SPR):
MIR: 1500 bps
CIR: 256 bps
For uplink (i.e. SPR to BSR):
MIR: 128 bps
CIR: 64 bps


The flowchart in Figure 11-1 displays a summary of tasks for defining Asymmetric
CIR and MIR bandwidth for multiple SPRs.
Figure 11-1: Flowchart for defining aggregated bandwidth
11.2.2. Task 1: Enable Asymmetric Bandwidth Policy

The first task that you need to perform for configuring asymmetric bandwidth is to
enable Asymmetric CIR/MIR bandwidth policy at the BSR. Once you choose this
bandwidth policy at the BSR, the Asymmetric CIR/MIR bandwidth policy applies to
all SPRs associated with the BSR.
To enable Asymmetric bandwidth policy:
then choose Bandwidth Limitation. The Bandwidth Limitation dialog box
appears.

Asymmetric bandwidth
policy selected
Figure 11-2: Selecting Asymmetric CIR/MIR option
2. Select the Asymmetric CIR/MIR option.

3. Click OK.

11.2.3. Task 2: Define Downlink and Uplink CIR and

MIR Values
After you have enabled the Asymmetric CIR/MIR bandwidth policy, you need to
define MIR and CIR values for downlink and uplink for the SPRs.
To define Asymmetric CIR and MIR values for multiple SPRs:
then choose Multi Edit/Delete Permitted SPRs. The Multi Edit-Delete
Permitted SPRs dialog box appears.
Figure 11-3: Multi Edit-Delete Permitted SPRs dialog box

2. Select the SPRs by clicking their corresponding check box, for which you want
to define MIR and CIR,
-Or-
Click the Select Range button, and then enter the range of SPR indexes that you
want to select, and then click OK.
Figure 11-4: Selecting a range of SPRs

3. Click Edit. The Edit Permitted SPRs dialog box appears.
Downlink MIR and CIR
Uplink MIR and CIR
Figure 11-5: Editing downlink and uplink MIR and CIR values

Note: The fields displayed for defining bandwidth depends on the type of
bandwidth policy selected. If the No Bandwidth Limitation policy is selected,
the Permitted SPRs-Edit dialog box does not display any fields for CIR and
MIR.
4. For the downlink (i.e. BSR to SPR) values, fill in the following fields:
Downlink MIR: maximum information rate, e.g. 1500 bps
Downlink CIR: committed information rate, e.g. 256 bps
5. For the uplink (i.e. SPR to BSR) values, fill in the following fields:
Uplink MIR: maximum information rate, e.g. 128 bps
Uplink CIR: committed information rate, e.g. 64 bps
Notes:
1) To define CIR MIR values for an individual SPR, you can right-click an SPR,
and then choose Edit.
1) Bandwidth values are in bits per second (bps).
2) The default MIR value is 4096 bps.
3) The default CIR value is zero (0).
4) When the total CIR of active SPRs and IDRs is greater than the available
bandwidth for data, ASWipLL implements its CIR Proportional Degradation
feature whereby the CIR decreases in proportion for all the SPRs. Therefore,
the proportion between CIR bandwidth of all SPRs is maintained.


12
Defining Static Routes
This chapter describes procedures for adding static routes in the ASWipLL network,
and includes the following sections:
Overview
Adding Static Routes to a BSR
Summary of Tasks
Task 1: Add Static Route to BSR
Task 2: Add Default Gateway to BSR
12.1. Overview
Static routes are paths that a packet takes from an ASWipLL device (i.e. BSR and
SPR/IDR) to a specific destination (i.e. BSR, SPR/IDR, or third-party router). The
route destination is defined by IP address and subnet mask. Static routes also include
default gateways and air subnet addresses (for defining air subnet addresses, see
Chapter 15, "Defining Air Subnets").
You can also define the device/router through which the traffic is routed to the
defined destination. This is referred to as the “next hop” and can be defined as any
third-party device (i.e. router) by IP address, or as an SPR that is associated with the
BSR, by the SPR’s index number.
In addition, static route configuration also includes defining default gateways. These
are default gateways that you can define for each ASWipLL device. In the case of a
BSR, the default gateway can be a third-party router or any SPR that is associated
with the BSR. In the case of an SPR, the default router can be the BSR with which
the SPR is associated, or any other third-party device.

Defining Static Routes Commissioning Manual
Notes:
1) The procedures described in this chapter relate to the BSR. However, the
procedures for adding static routes for SPRs are similar
2) When ASWipLL is configured for transparent bridging, static routing is not
applicable. However, the Static Routing Table command allows you to define
a default gateway, which is applicable for transparent bridging.
3) For detailed description on defining gateways per SPR, see Chapter 23,
"Defining Security", and for defining gateways per VLAN, see Chapter 14,
"Defining VLANs".
12.2. Adding Static Routes to a BSR

The sections below describe the procedure for adding a static route to BSR #1
(10.0.0.10) for routing traffic to BSR #2 (10.0.0.48). This destination is reached via
a third-party router (10.0.0.2), referred to as next hop. In addition, a default gateway
is also defined for the BSR #1. The static route configuration is illustrated in the
figure below:
Figure 12-1: Configuration example for adding static routes

Commissioning Manual Defining Static Routes

The flowchart in the figure below displays the tasks for adding a static route and
default gateway to a BSR.
Figure 12-2: Flowchart for adding static routes

12.2.2. Task 1: Add Static Route to BSR

The following procedure describes adding a static route to BSR #1 (10.0.0.10) for
routing traffic to BSR #2 (10.0.0.48). This destination is reached via a third-party
router (10.0.0.2), referred to as next hop.
To add a static route (for BSR #1):
1. From the Configuration menu, point to Network, and then choose Static
Routing Table. The Static Routing Table dialog box is displayed in Figure 12-3.

Commissioning Manual Defining Static Routes
2. Click Add. The Static Routing Table - Add dialog box appears, as displayed
below.
Figure 12-4: Adding static route
3. Enter the following fields (as displayed in the figure above):

Destination: IP address of the destination network, e.g. 10.0.0.48 (i.e. IP
address of BSR to where you want to route the traffic.
Route Mask: subnet mask of the destination network. This can be calculated
using the Calc. button.
Next Hop: IP address of the router, e.g. 10.0.0.2 (i.e. IP address of third-
party router) through which the packet passes to reach its destination (i.e.
BSR). (When the next hop is one of the SPRs/IDRs in the cell, you can select
the SPR check box, and then enter the SPR’s index number as defined in the
BSR.)
Primary Metric: number of hops between the BSR and the SPR/IDR or the
next router.
4. Click OK.

12.2.3. Task 2: Add Default Gateway to BSR

The following procedure describes how to add a default gateway (e.g. 10.0.0.1) for
the BSR #1 (10.0.0.10).
To add a default gateway (for BSR #1):
1. From the Configuration menu, point to Network, and then choose Static
Routing Table. The Static Routing Table dialog box is displayed below.
GW's IP
address
Default GW
enabled
Figure 12-5: Adding a default gateway
2. Select the Enable Default Gateway check box, and then perform the following:
a. In the text box, enter the BSR's default gateway's IP address, e.g. 10.0.0.1.
b. In the Metric field, enter hops between the BSR and the default gateway.
3. Click Apply.

13
Defining Virtual Ports
You can define up to 16 virtual ports (i.e. network interfaces) per BSR and SPR/IDR
when operating in the routing mode. The virtual ports are defined by IP address and
subnet mask. This is useful when using third-party external routers (see IntraCom
Gateways in Chapter 23, "Defining Security") that are on different subnets to the
BSR or SPR.
The procedure described in this chapter is based on the configuration displayed in
the figure below.
Figure 13-1: Configuration example for defining BSR's virtual ports
In the above configuration, the BSR provides two virtual (i.e. logical) IP network
interfaces with a third-party router. For example, BSR's logical ports 10.0.0.2 and
10.0.1.2 interfaces with the router's 10.0.0.1 and 10.0.1.1 port interfaces
respectively. VLANs can be assigned to each of these virtual port interfaces. This is
useful when implementing a gateway per VLAN application where SPR VLAN
traffic is routed to these interfaces (i.e. gateways).
Note: For a detailed description on defining gateways per VLAN, see Chapter
14, "Defining VLANs".

Defining Virtual Ports Commissioning Manual
To define two virtual network interfaces (e.g. for a BSR):

1. In the BSR Zoom window, from the Configuration menu, point to Network, and
then choose Addresses Table / 802.1Q. The Addresses Table/802.1Q dialog box
appears, as displayed below.
Figure 13-2: Addresses Table/802.1Q dialog box

Commissioning Manual Defining Virtual Ports
Note: The first IP address (i.e. Index #1) that appears in the Addresses
Table/802.1Q is defined in WipConfig when you define the BSR's IP address,
subnet mask, and default gateway. These can only be edited or deleted using
WipConfig (refer to the WipConfig User’s Guide).
2. Click Add. The Device Addresses Table dialog box appears, as shown below.
Figure 13-3: Defining a virtual port 10.0.0.2
3. Fill in the following fields, as shown in the figure above:

IP Address: IP address of the BSR's logical network interface (e.g.
10.0.0.2).
Interface: defines the type of connection (e.g. Ethernet) used for the
interface between the BSR and the other component. If there is only one
interface protocol, this selection remains grayed. Otherwise, from the drop-
down list, select an interface.
Subnet Mask: subnet address of the BSR's logical network interface (e.g.
255.255.255.0).

Admin: If there is only one option available, this remains grayed, otherwise
clicking this button provides a list of possible administration options.
Gateway: IP address of the third-party router (or gateway) that interfaces
with this virtual port.
4. If you want to implement Gateway per VLAN application (see Chapter 14,
"Defining VLANs"), select the VLAN ID check box, and then enter the VLAN
number (e.g. 100).
5. Click OK.
6. Perform steps 2 through 5 for adding the BSR's virtual port 10.0.1.2 with
gateway 10.0.1.1 (with VLAN ID 200), as configured below.
Figure 13-4: Defining a virtual port 10.0.1.2

Commissioning Manual Defining Virtual Ports
The figure below displays the virtual ports defined in the procedure above.
BSR's virtual
ports
Figure 13-5: Addresses Table / 802.1Q listing virtual ports


14
Defining VLANs
This chapter describes the procedures for defining VLAN policy and management
for the ASWipLL system, and includes the following sections:
Overview
Transparent Mode
Tagging Mode
Defining VLANs for IP Routing
Defining Gateways per VLAN
− Summary of Tasks
− Task 1: Enable Gateway per VLAN Mode
− Task 2: Reset the BSR
− Task 3: Define Gateway Addresses per VLAN
− Task 4: Define SPR VLAN ID(s)
Defining BSR VLAN Policy and Management
Defining SPR VLAN Policy and Management
Defining VLANs for Transparent Bridging
Defining BSR VLAN Policy and Management
Defining SPR VLAN Policy and Management

D e f i n i n g V L AN s Commissioning Manual
Note: This chapter mentions the BSR and SPR devices. However, all BSR
procedures are also applicable for PPR devices; and all SPR procedures are
14.1. Overview
The SPR can have several IP addresses on its LAN port, allowing for multiple IP
subnets on the same LAN. This is useful when there is a need for groups of users on
the same physical LAN or, for example, when using a second layer LAN switch that
supports virtual LANs (VLANs). In this setup, each VLAN may have its own IP
subnet. In such scenarios, SPR provides "one-leg routing" on its LAN port.
There are three types of VLANs:
Static port based: most common type of VLAN belonging to Layer 1, as
VLAN membership is based on the physical ports
Dynamic MAC-based: Layer 2 VLAN - the station's MAC address determines
the VLAN
Dynamic IP-based: Layer 3 VLAN - Common IP or IPX network numbers are
automatically entered into common VLANs
When the ports of a switch are grouped into the same broadcast domain under
management control, the grouped ports are called a VLAN.
Two stations in the same VLAN communicate directly using MAC-level frames
(Layer 2), whereas stations in different VLANs need to use Layer 3 connections to
communicate (i.e. IP routing protocol).
ASWipLL uses two types of VLAN modes:
Transparent
Tagging

Commissioning Manual D e f i n i n g V L AN s
14.1.1. Transparent Mode

In transparent mode, VLAN traffic is passed intact between the BSR and SPR. This
is VLAN traffic destined to the WAN (i.e. interfacing with the BSR) and to the
subscriber (i.e. interfacing with the SPR).
The SPR passes all VLAN (i.e. 802.1Q) traffic. In other words, the SPR passes all
VLAN traffic received from the SPR's LAN interface with the subscriber (through
the SDA) to the BSR. The BSR then sends this VLAN traffic to the WAN. This is
also the case in the opposite direction, i.e. traffic from the WAN to the subscriber.
Therefore, in transparent mode, VLAN traffic is passed uninterrupted through the
ASWipLL network, preserving the VLAN formats.
Figure 14-1: Transparent mode
Transparent mode is configured in WipManage, by selecting the Pass Any option in

the Addresses Table / 802.1Q dialog box for BSRs (in the BSR Zoom window), or
in the 802.1Q (VLAN) Configuration dialog box for SPRs/IDRs (in the SPR Zoom
window).

14.1.2. Tagging Mode

In the Tagging mode, although the 802.1Q frames are recognized, the SPR accepts
only one specific VLAN from the BSR, which it untags and passes onto the
subscriber's LAN. All other traffic from the BSR is discarded. Traffic received by
the SPR from the SDA is tagged with a specific VLAN and sent to the BSR. If the
SPR is connected to an SDA-4S/VLtag device, the SPR assigns VLANs to traffic
from each of the four SDA-4S/VLtag ports, before sending the VLAN traffic to the
BSR. In the opposite direction, the SPR accepts only traffic from these VLANs.
Figure 14-2: Tagging mode
14.2. Defining VLANs for IP Routing

This section describes how to define VLANs when ASWipLL is configured in the
IP router / PPPoE mode.

configuration, the BSR sends VLAN packets (received from the SPR) to its
appropriate default gateway (router) according to VLAN ID. Therefore, the BSR
does not perform the main routing, rather the gateway.
The figure below illustrates the implementation of the Gateway per VLAN feature.
Figure 14-3: ASWipLL’s gateway per VLAN mode
In the figure, VLAN 60 traffic is routed by Gateway #1, and VLAN 70 and VLAN
80 traffic is routed by Gateway #2. Therefore, the gateway routes the traffic
according to VLAN, and not according to SPR device.

14.2.1.1. Summary of Tasks

The flowchart in the figure below displays a summary of tasks for defining gateways
per VLAN for the ASWipLL network.
Figure 14-4: Flowchart for defining gateways per VLAN
14.2.1.2. Task 1: Enable Gateway per VLAN Mode

Before you can define gateways for each VLAN, you need to enable the Gateway
per VLAN mode, by selecting the Gateway per VLAN Mode option using
WipManage.

To enable the Gateway per VLAN mode:

1. In the WipManage main window, double-click the desired BSR. The BSR Zoom
window appears.
2. From the Configuration menu, point to Network, and then click Multiple
Gateway Mode. The IntraCom dialog box appears.
Figure 14-5: IntraCom dialog box
3. Select the Gateway Per VLAN Mode option, and then click OK. The following
Notice message box appears.
Figure 14-6: Notice message box
4. Click OK.

14.2.1.3. Task 2: Reset the BSR

After you have selected the Gateway per VLAN Mode option, you need to reset the
device for the mode to take effect.
1. In the BSR Zoom window, from the Configuration menu, choose Reset. The
Reset confirmation box appears.
2. Click Yes to confirm reset. The Device Reset message box appears.
Figure 14-8: Device Reset message box
3. Click OK.
14.2.1.4. Task 3: Define Gateway Addresses per VLAN

Now that you have configured the BSR device for Gateway per VLAN mode, you
need to define the BSR's virtual IP address and assign the virtual port a gateway
with a specific VLAN ID. This is performed using WipManage.

then choose Addresses Table/802.1Q. The Addresses Table/802.1Q dialog box
appears.
2. Click Add. The Device Addresses Table dialog box appears.

Figure 14-10: Device Addresses Table dialog box
3. In the IP Address field, enter the BSR’s virtual IP address for this gateway.
4. In the Subnet Mask field, enter the BSR's virtual subnet mask for this gateway.
5. In the Gateway field, enter the gateway’s (router’s) IP address.
6. Select the VLAN ID check box, and then in the spin box, enter the VLAN ID to
be routed to this gateway.
7. Click OK. The defined gateway VLAN appears in the Addresses Table/802.1Q
dialog box.
8. Click Apply, and then Close.
14.2.1.5. Task 4: Define SPR VLAN ID(s)

Each SPR can support only one VLAN ID, except for SPRs that are attached to the
ASWipLL SDA-4S/VLtag switch, which provides up to four VLAN IDs, each
corresponding to a port (1 to 4).
To define a VLAN ID for an SPR:
1. In the SPR Zoom window, from the Configuration menu, point to Network, and
then choose 802.1Q (VLAN).

Figure 14-11: 802.1Q (VLAN) Configuration dialog box

2. For IP traffic, in the IP Routing / Transparent Bridging group, select the

Tag/Untag check box, and then enter the following fields:
VLAN ID: VLAN ID of the SPR. The SPR tags all IP or PPPoE packets
received from the subscriber's network with this VLAN ID, and then
forwards the packets to the BSR. In addition, SPR accepts only IP or PPPoE
packets from the BSR with this VLAN ID, untags them, and then passes
them to the subscriber's network.
Priority: select the priority level (0 to 7, where zero is the lowest priority) of
traffic for this VLAN
3. For SPR PPPoE traffic, fill in the fields in the PPPoE Bridging group, as
described in Step 4.
4. If an SDA-4S-VLtag switch is connected to the SPR, then in the VLAN Tagging
(SDA-4S/VLtag) group, select Enable/Disable VLAN Tagging check box, and
then for each port (1 to 4 ports), define the VLAN ID and its corresponding
priority level.
Note: SDA-4S/VLtag VLAN tagging is only applicable when ASWipLL is

configured for transparent bridging.
5. Click OK.
14.2.2. Defining BSR VLAN Policy and Management

WipManage allows you to define whether the BSR passes all traffic or passes all
traffic except VLAN traffic in an IP router / PPPoE environment. WipManage also
allows you to define a VLAN ID for BSR SNMP traffic.
To define BSR VLAN policy and management:
1. In the WipManage main window, double-click the desired BSR icon. The
BSR Zoom window appears.
2. From the Configuration menu, point to Network, and then click Addresses
Table / 802.1Q (VLAN). The Addresses Table / 802.1Q dialog box appears.

3. To define the policy for VLAN traffic, in the IP Routing / Transparent

Bridging group or PPPoE Bridging group (depending on the environment),
perform the following:
Pass Any: passes all traffic
Drop 802.1Q: discards traffic that has a VLAN tag

4. To enable management through a specific VLAN, perform the following:

a. Click the SNMP Virtual Port button, and then from the list, select All to
allow any port to be configured for management SNMP traffic.
b. Select the Management VLAN Enabled check box, and then fill in the
following fields:
− VLAN ID: VLAN ID for management SNMP packets
− Priority: priority level (0 to 7, where zero is the lowest priority)
Note: The Management VLAN Enabled check box is available only if you
have selected the Pass Any option.
5. Click Apply, and then OK.
14.2.3. Defining SPR VLAN Policy and Management

WipManage allows you to define whether the SPR passes or discards VLAN traffic,
or whether the SPR tags/untags traffic from a specific VLAN. In addition, you can
define a VLAN ID for SNMP management of the SPR.
To define VLAN policy for SPRs:
2. In the BSR Zoom window, double-click the SPR icon. The SPR Zoom window
appears.
3. From the Configuration menu, point to Network, and then click 802.1Q
(VLAN). The 802.1Q (VLAN) Configuration dialog box appears.


4. For IP traffic, in the IP Routing / Transparent Bridging group, perform one of

the following:
Select one of the following options:
− Pass Any: passes all IP traffic
− Drop 802.1Q: discards IP traffic that has a VLAN tag
To enable VLAN tagging/untagging for IP traffic, select the Tag/Untag
check box, and then enter the following fields:
− VLAN ID: VLAN ID of the SPR (to the BSR)
− Priority: select the priority level (0 to 7, where zero is the lowest
priority) of traffic for this VLAN
5. For SPR PPPoE traffic, fill in the fields in the PPPoE Bridging group, as
described in Step 4.
6. To enable SPR SNMP management through a VLAN, select the Management
VLAN Enabled check box, and then fill in the following fields:
VLAN ID: VLAN ID to which the WipManage station belongs
Priority: select the priority level (0 to 7, where zero is the lowest priority)
Notes:
1) The SDA-4S/VL – VLAN Tagging group is relevant only when ASWipLL is
configured in Bridge mode.
2) If you select the Management VLAN Enabled check box, only those
WipManage stations belonging to the defined VLAN can manage the SPR.

14.3. Defining VLANs for Transparent Bridging

When the ASWipLL network is operating in the transparent bridge mode, you can
define only one VLAN per SPR. In addition, WipManage allows you to define a
VLAN ID for SPR SNMP management.
14.3.1. Defining BSR VLAN Policy and Management

WipManage allows you to define whether the BSR passes or discards VLAN traffic
in transparent bridging environment. In addition, you can define the VLAN ID for
BSR SNMP management.
To define BSR VLAN policy and management:
2. From the Configuration menu, point to Network, and then click Addresses
Table / 802.1Q (VLAN).
The Bridge Mode message box appears informing you that PPPoE
configurations are not relevant for transparency bridging.
Figure 14-14: Bridge Mode message box
3. Click OK.

The Addresses Table / 802.1Q dialog box appears.
Figure 14-15: Addresses Table / 802.1Q dialog box
4. To define the policy for VLAN traffic in transparency bridging networks,

perform the following:
In the IP Routing / Transparent Bridging group, select one of the
following options:
− Pass Any: passes all transparent bridging traffic
− Drop 802.1Q: discards transparent bridging traffic that has a VLAN tag

5. To enable management through a VLAN, perform the following:

a. Click the SNMP Virtual Port button, and then from the list, select All to
allow any port to be configured for management traffic.
b. Select the Management VLAN Enabled check box, and then fill in the
following fields:
− VLAN ID: VLAN ID for management packets
priority)
Note: The Management VLAN Enabled check box is available only if you
have selected the Pass Any option, in the Transparent Bridging group.

14.3.2. Defining SPR VLAN Policy and Management

WipManage allows you to define whether the SPR passes or discards VLAN traffic
in a transparent bridge network. In addition, you can define the SNMP management
VLAN ID for the specific SPR.
To define VLANs for SPRs/IDRs:
2. In the BSR Zoom window, double-click the SPR icon. The SPR Zoom window
appears.
3. From the Configuration menu, point to Network, and then click 802.1Q
(VLAN).
The Bridge Mode message box appears informing you that PPPoE
configurations are not relevant for transparency bridging.
Figure 14-16: Bridge Mode message box
4. Click OK.

The 802.1Q (VLAN) Configuration dialog box appears.

5. For transparent bridging traffic, in the IP Routing / Transparent Bridging

group, perform the following:
Select one of the following options:
− Pass Any: passes all transparent bridging traffic
− Drop 802.1Q: discards transparent bridging traffic that has a VLAN tag
− To enable VLAN tagging/untagging for transparent bridging traffic,
select the Tag/Untag check box, and then enter the following fields:
− VLAN ID: VLAN ID of the SPR (to the BSR)
priority) of traffic for this VLAN
6. If an SDA-4S/VLtag device is connected to the SPR, select the SDA-4S/VL –
VLAN Tagging check box, and then enter the VLAN IDs and priority levels for
each port (ports 1 to 4).
7. To enable SPR SNMP management through a VLAN, select the Management
VLAN Enabled check box, and then fill in the following fields:
VLAN ID: VLAN ID to which the WipManage station belongs
Priority: select the priority level (0 to 7, where zero is the lowest priority)
Note: If you select the Management VLAN Enabled check box, only those
management stations belonging to the defined VLAN can manage the SPR.

15
Defining Air Subnets
This chapter describes the procedures for defining subnet addresses for the BSR and
SPR/IDR ports that interface with the wireless (i.e. air) path, and includes the
following sections:
Overview
Configuring Air Subnet Addresses for Private Networks
Summary of Tasks
Task 1: Define BSR's Air Subnet using WipConfig
Task 2: Verify BSR's Air Subnet Address
Task 3: Define SPR's Air Subnet using WipConfig
Task 4: Verify SPR's Air Subnet Address
Task 5: Return PC's IP Settings for Connectivity with BSR
Task 6: Add BSR and SPR in WipManage
Task 7: View Air Subnets in WipManage

D e f i n i n g Ai r S u b n e t s Commissioning Manual
Notes:
1) Air Subnet addressing is relevant only when ASWipLL is operating in the IP
router mode.
2) If using WipManage, change the SPR's Air Subnet address before changing
the BSR’s Air Subnet address.
3) Ensure that the SPRs and the BSR with which the SPRs are associated,
have identical Air Subnet addressing scheme (i.e. Not Economical or
Economical).
4) This chapter mentions the BSR and SPR devices. However, all BSR
procedures are also applicable for PPR devices; and all SPR procedures are
15.1. Overview
The air subnet addresses of the ports that interface with the BSR-SPR wireless
communication path (i.e. air) are typically configured during installation using
WipConfig. The configuration is performed through a local IP network
communication mode. The figure below displays a typical local network cable setup
between the PC running WipConfig and the SPR.
Figure 15-1: Local network setup (e.g. SPR)

Commissioning Manual D e f i n i n g Ai r S u b n e t s
ASWipLL can operate in one of the following Air Subnet addressing schemes:
Economical: IP addresses of the air subnet ports are user-defined. This mode is
applicable for all networks with private Internet addresses according to RFC
1918:
10.0.0.0 to 10.255.255.255 (Class A)
172.16.0.0 to 172.31.255.255 (Class B)
192.168.0.0 to 192.168.255.255 (Class C)
The Economical mode increases the flexibility of ASWipLL. It permits more
efficient use of IP addresses in the user’s network and often avoids a need of
changing IP addresses in a pre-existing network. For example, an operator with
private IP addresses from the range of 192.168.0.0 does not have to change IP
addresses in the network when installing ASWipLL.
The Economical mode provides the subnet address 255.255.255.252, thereby,
providing a total of four IP addresses, where only two of the addresses can be
used for ASWipLL devices: one for the BSR and one for the SPR.
Not Economical: only for networks using RFC's 192.168.0.0 range. IP
addresses of the Air subnet ports are fixed ranging from 192.168.0.0 to
192.168.255.255 (see RFC 1918). Therefore, the Not Economical mode
provides Class C subnetting for all the BSRs. This means that 254 addresses are
available to choose for one BSR. Thus, many addresses are "wasted" (not used).
The addressing is as follows:
BSR side SPR side
192.168.x.1 192.168.x.2
where x is the SPR index number in the ASWipLL database.
For example, for SPR index #2, the air subnet address of the SPR virtual port
interfacing with the BSR is 192.168.2.2; the air subnet address of the BSR virtual
port interfacing with the SPR is 192.168.2.1 (see Figure 15-2).

Figure 15-2: Not Economical Air subnet addressing scheme
Notes:
1) Networks using 192.168.0.0. range can be configured for Economical or
Not Economical air subnetting address schemes. All other ranges can only
use Economical air subnetting address schemes.
2) By default, ASWipLL uses air subnet addressing is according to RFC 1918
(i.e. IP addresses ranging from 192.168.0.0.) – Not Economical.
3) Airspan recommends using WipConfig to configure air subnet addressing
scheme. The WipConfig should be connected to the device through a local
network connection for the BSR and the SPR.
4) The BSR and SPR must be configured with the same air subnet-addressing
scheme.

15.2. Configuring Air Subnet Addresses for

Private Networks
The following subsections describes the procedures for configuring air subnet
addressing scheme in private networks using IP addresses other than 192.168.0.0.
The configuration example describes configuring the BSR and SPR from default
settings to user-defined settings. The configuration setup example is illustrated in the
figure below:
Figure 15-3: Configuration setup example for Economical air subnet addressing
scheme


The flowchart in the figure below displays the tasks for defining air subnet addresses
for the BSR and SPR.
Figure 15-4: flowchart for defining air subnet addresses
15.2.2. Task 1: Define BSR's Air Subnet using

WipConfig
The first step is to define the BSR's air subnet scheme as Economical and in the
172.16.0.0 address range. The BSR is accessed using the BSR's default parameters
(i.e. IP address 10.0.0.10). Thus, ensure that the PC 's IP addressing scheme provides

IP connectivity to the device (i.e. IP address is 10.0.0.2; subnet mask is

255.255.255.240; and default gateway is 10.0.0.10).
To define BSR's air subnet address using WipConfig:
1. Ensure that WipConfig is connected to the BSR by a local network connection.
2. Start WipConfig, and then in the Communication group, select Network.
3. In the Remote Agent field, enter the BSR's default IP address, i.e. 10.0.0.10.
4. On the toolbar, click the Connect button. WipConfig connects to the BSR, as
displayed below.
Air Subnet
group
Figure 15-5: WipConfig connected to BSR (using Not Economical mode)

5. In the Air Subnet group, perform the following to define the Air subnet
addressing scheme as Economical:
a. From the New Scheme drop-down list, select Economical.
b. In the New Base field, enter only the network ID address, e.g. 172.16.0.0.
Eth IP Address: change the BSR’s IP address to 192.168.1.1
Eth Subnet Mask: change the BSR’s subnet address to 255.255.255.0
Air MAC Address: BSR’s Air MAC address (valid ranges is between
0x0000 through 0xFFFF), e.g. 0x1200.
Frequency Table ID: frequency table ID used by the BSR (valid range is 0
through 63), e.g. 1.
device.
WipConfig applies the new settings to the BSR.
9. On the toolbar, click the Reset button to reset the device.

Figure 15-6: Warning message box for resetting BSR

WipConfig losses connection with the BSR due to the BSR's new IP address.

15.2.3. Task 2: Verify BSR's Air Subnet Address

To verify that the BSR's air subnet address has successfully being applied, you need
to connect WipConfig once again to the BSR through a network connection. Before
you can do this, you need to ensure that the PC has IP connectivity to the BSR by
changing the PC's IP settings:
PC's IP address: 10.0.0.2 changed to 192.168.2.1 (i.e. same subnet as BSR)
PC's subnet mask: 255.255.255.240 changed to 255.255.255.0
PC's default gateway: 10.0.0.10 changed to 192.168.1.1 (i.e. the BSR)
For a detailed description on changing a PC's IP settings, see Chapter 3, "Initial
Configuration".
To verify that the BSR's air subnet address has been applied successfully:
2. Start WipConfig.
3. In the Communication group, select Network.
4. In the Remote Agent field, enter the BSR's IP address, e.g. 192.168.1.1.
WipConfig connects to the BSR and shows the BSR's air subnet address
configured for Economical mode and in the 172.16.0.0 range, as displayed
below.

Network ID of
air subnet
Economical
scheme
selected
Figure 15-7: BSR configured for Economical mode in 172.16.0.0 range
15.2.4. Task 3: Define SPR's Air Subnet using

WipConfig
After you have defined the BSR's air subnet address, you need to define the SPR's
air subnet address with the same air subnet parameters as the BSR, i.e. Economical
and in the 172.16.0.0 range.
The SPR is accessed using the SPR's default parameters (i.e. IP address 10.0.0.20)
and by connecting the PC's LAN directly to the SPR (i.e. not via the BSR). Thus,
you need to change the PC's Ethernet interface IP address so that it's in the same

subnet as the SPR (for a detailed description on changing a PC's IP settings, see
Chapter 3, "Initial Configuration").
PC's IP address: changed to 10.0.0.17 (i.e. same subnet as SPR)
PC's subnet mask: 255.255.255.240
PC's default gateway: 10.0.0.20 (i.e. the SPR)
To define SPR's air subnet address using WipConfig:
1. Ensure that WipConfig is connected to the SPR through a local network
connection.
2. Start WipConfig.
4. In the Remote Agent field, enter the SPR's default IP address, i.e. 10.0.0.20.
WipConfig connects to the SPR and displays the Configuration parameters.

Air Subnet
group
Figure 15-8: WipConfig connected to SPR (using Not Economical mode)
6. In the Air Subnet group, perform the following to define the Air subnet
addressing scheme as Economical:
a. From the New Scheme drop-down list, select Economical.
b. In the New Base field, enter only the network ID address, e.g. 172.16.0.0.
Eth IP Address: SPR’s IP address, e.g. 192.168.2.1
Eth Subnet Mask: SPR’s subnet address, e.g. 255.255.255.0


Index in BSR: SPR’s index number that is indexed in the BSR, e.g. 2.
BSR Air MAC Address: BSR’s Air MAC address to which the SPR is
associated (valid ranges is between 0x0000 through 0xFFFF), e.g. 0x1200.
device.
10. On the toolbar, click the Reset button to reset the device.
Figure 15-9: Warning message box for resetting BSR

WipConfig losses network connection with the SPR due to the SPR's new IP
address.

15.2.5. Task 4: Verify SPR's Air Subnet Address

To verify that the SPR's air subnet address has successfully being applied, you need
to connect WipConfig to the SPR through a network connection. Before you can do
this, you need to ensure that the PC has IP connectivity to the SPR by changing the
PC's IP settings:
PC's IP address: 10.0.0.17 changed to 192.168.2.2 (i.e. same subnet as SPR)
PC's subnet mask: 255.255.255.240 changed to 255.255.255.0
PC's default gateway: 10.0.0.20 changed to 192.168.2.1 (i.e. the SPR)
To verify that the SPR's air subnet address has been applied successfully:
2. Start WipConfig.
4. In the Remote Agent field, enter the BSR's IP address, e.g. 192.168.1.1.

WipConfig connects to the SPR and shows the SPR's air subnet address
configured for Economical mode and in the 172.16.0.0 range, as displayed
below.
Network ID of
air subnet
Economical
scheme
selected
Figure 15-10: SPR configured for Economical mode in 172.16.0.0 range

15.2.6. Task 5: Return PC's IP Settings for

Connectivity with BSR
Once you have successfully configured the SPR, you need to define the PC's IP
settings so that it has IP connectivity with the BSR. This is vital for management of
the BSR and SPR through WipManage.
The PC's IP settings for this interface is as follows:
IP address: 192.168.1.2
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1 (i.e. the BSR)
For a detailed description on changing a PC's IP settings, see Chapter 3, "Initial
Configuration".
15.2.7. Task 6: Add BSR and SPR in WipManage

Once you have defined the BSR's and SPR's air subnet addresses using WipConfig,
you need to add the BSR and SPR in WipManage. For a detailed description of
adding BSR and SPR to WipManage, see Chapter 4, "Establishing BSR-SPR Link in
Router Mode".
15.2.8. Task 7: View Air Subnets in WipManage

Once you have added the BSR and SPR in WipManage, you can view the actual air
subnet addresses assigned to the BSR and SPR. The air subnet addresses are listed
per BSR-SPR link, from the first SPR index to the last.
To view air subnet addresses:
1. In the WipManage main window, double-click the BSR icon. The BSR Zoom
window appears.
2. In the BSR Zoom window, from the Configuration menu, point to Network,
and then choose Static Routing Table.

The Static Routing Table dialog box appears.
3. Click Advanced. The Air Subnet Configuration dialog box appears, displaying
the configured air subnet address scheme (i.e. Economical) and the network ID
(i.e. 172.16.0.0) on which the scheme is based.

Network ID on
which air subnet
is based
Economical mode
selected
Figure 15-12: Air Subnet Configuration dialog box
4. Click Air Addresses. The Air Subnet Addresses window appears, listing the air
subnet addresses of each consecutive SPR and the BSR.

Air subnet address of SPR

(index #2)
Air subnet address of BSR

associated with SPR (index #2)
Figure 15-13: Air Subnet addresses (Economical) of SPRs associated with a BSR
Note: The Economical Air subnet addresses listed in the Air Subnet
Addresses window are incremented by four (e.g. SPR #2 is 172.16.0.9 and
SPR #3 is 172.16.0.10). This is because the Economical mode provides the
subnet address 255.255.255.252, thereby, providing a total of four IP
addresses (only two of the addresses can be used for ASWipLL devices: one
for the BSR and one for the SPR).


16
Defining ASWipLL as a DHCP
Relay Agent
This chapter describes the procedures for configuring ASWipLL as a Dynamic Host
Configuration Protocol (DHCP) relay agent, and includes the following sections:
Overview
Defining ASWipLL as a DHCP Relay Agent
Note: DHCP Relay Agent configuration is relevant only when the ASWipLL
system is configured for IP routing (i.e. not applicable for transparent bridging).
16.1. Overview
ASWipLL devices and WipManage software support DHCP. You need to allow
transfer of Dynamic Host Configuration Protocol (DHCP) packets over the network
for dynamic address assignments. DHCP protocol allows dynamic allocation of IP
addresses and other IP host parameters to users such as Windows-based PCs. With
dynamic addressing, a device can have a different IP address every time it connects
to the network. In some systems, the device's IP address can even change while it is
still connected.

D e f i n i n g AS W i p L L a s a D H C P R e l a y Ag e n t Commissioning Manual
Dynamic addressing simplifies network administration because the software keeps

track of IP addresses rather than requiring an administrator to manage the task. This
means that a new computer can be added to a network without the hassle of
manually assigning it a unique IP address. In order to do so within an IP routing
environment, the IP routers have to support DHCP relay agent functionality.
ASWipLL as an IP router is also a DHCP relay agent/server.
16.2. Defining ASWipLL as a DHCP Relay Agent

You define a DHCP relay agent for BSRs. The DHCP server is defined by an IP
address.
To define a DHCP server:
1. In the BSR Zoom window, from the Configuration menu, point to Network,
and then choose DHCP, as shown below:
Figure 16-1: Choosing the DHCP command from the Configuration menu

Commissioning Manual D e f i n i n g AS W i p L L a s a D H C P R e l a y Ag e n t
The DHCP Relay dialog box appears, as shown below:
Figure 16-2: DHCP Relay dialog box
2. In the DHCP Server IP field, enter the IP address of the DHCP server, and then
click OK. The following Notice message box appears:
3. Click OK. The DHCP requests will now be forwarded to the designated DHCP
server.

D e f i n i n g AS W i p L L a s a D H C P R e l a y Ag e n t Commissioning Manual

17
Defining PPPoE
This chapter describes procedures for enabling point-to-point protocol over Ethernet
(PPPoE) in the ASWipLL system.
Overview
Enabling PPPoE for BSR and Associated SPRs
Summary of Tasks
Task 1: Select PPPoE Enabled Option for BSR
Task 2: Reset the BSR
Task 3: Verify BSR in PPPoE Mode
Task 4: Select PPPoE Enabled Option for SPRs
Task 5: Reset the SPRs
Task 5: Verify SPRs in PPPoE Mode
Notes:
1) PPPoE configuration is relevant only when the ASWipLL system is
configured for IP routing (i.e. not applicable for transparent bridging).
2) This chapter mentions the BSR and SPR devices. However, the BSR

Defining PPPoE Commissioning Manual
17.1. Overview
It is desirable to connect multiple hosts at a remote site through the same customer
premise access device. It is also a goal to provide access control and billing
functionality in a manner similar to dial-up services using Point-to-Point Protocol
(PPP). In many access technologies, the most cost-effective method to attach
multiple hosts to the customer premise access device is through Ethernet. In
addition, it is desirable to keep the cost of this device as low as possible while
requiring little or no configuration.
PPPoE provides the ability to connect a network of hosts over a simple bridging
access device to a remote Access Concentrator. With this model, each host utilizes
it’s own PPP stack and the user is presented with a familiar user interface. Access
control, billing and type of service can be done on a per-user, rather than a per-site
basis.
PPPoE has two distinct stages: a "discovery stage" and a "PPP session stage". When
a host wishes to initiate a PPPoE session, it must first perform discovery to identify
the Ethernet MAC address of the peer and establish a PPPoE session ID. While PPP
session stage defines a peer-to-peer relationship, discovery is inherently a client-
server relationship. In the discovery process, a host (the client) discovers an access
concentrator that the host can communicate with. The discovery stage allows the
host to discover all access concentrators and then select one. When discovery
completes successfully, both the host and the selected access concentrator have the
information they will use to build their point-to-point connection over Ethernet.
The discovery stage remains stateless until a PPP session is established. Once a PPP
session is established, both the host and the access concentrator MUST allocate the
resources for a PPP virtual interface.
The PPPoE method in ASWipLL is described below:
1. The Data Terminal Equipment (DTE) client requests PPPoE service with a
broadcast message to the SPR.
2. The SPR then sends the request to the BSR.
3. The BSR contains a MAC address table of all LAN side DTEs.
4. If valid, the BSR sets up a transparent PPPoE bridge to the server.

Commissioning Manual Defining PPPoE
5. The BSR then responds to the user with an authorization unicast via the SPR.
6. A PPPoE data link tunnel is set up between the LAN client and the WAN server
through the SPR and BSR air link.
Figure 17-1: PPPoE process in the ASWipLL system
Note: When you configure PPPoE for the BSR, you can configure some
SPRs for PPPoE and some SPRs for IP filtering

17.2. Enabling PPPoE for BSR and Associated

SPRs
The following subsections describe the procedures for enabling PPPoE of a BSR
(10.0.0.10) and two associated SPRs (SPR 10.0.0.20 and SPR 10.0.0.36).

The flowchart in the figure below displays a summary of tasks for enabling Point-to-
Point over Ethernet for BSR and SPRs.
Figure 17-2: Flowchart for enabling PPPoE
17.2.2. Task 1: Select PPPoE Enabled Option for BSR

The first task that you need to perform is to select the PPPoE Enable option
(instead of the IP Filters Active option) to enable point-to-point over Ethernet in the
BSR.

To enable the PPPoE mode:

then choose PPPoE/IP Filtering, as shown below.
Figure 17-3: Choosing the PPPoE / IP Filtering command
The PPPoE / IP Filters dialog box appears:
Figure 17-4: PPPoE/IP Filtering dialog box showing device in IP Filters Active mode

2. Select the PPPoE Enabled option.

3. Click OK.
17.2.3. Task 2: Reset the BSR

After you have selected the PPPoE Enabled option, you need to reset the BSR for
the PPPoE mode to take effect.
To reset the BSR:
1. In the BSR Zoom window, from the Configuration menu, choose Reset.
The Reset confirmation box appears, as displayed below.
2. Click Yes to confirm resetting the device.

The Device Reset message box appears, as displayed below.
3. Click OK to reset the device.

17.2.4. Task 3: Verify BSR in PPPoE Mode

After you have reset the BSR, it is recommended that you check that the new
settings have taken effect.
To verify that the BSR is in PPPoE mode:
In the BSR Zoom window, from the Configuration menu, point to Network, and
then choose PPPoE/IP Filtering.
The PPPoE / IP Filters dialog box appears, displaying "PPPoE Enabled" in the
Current Device Mode field, as shown below.
PPPoE
enabled
Figure 17-7: Current Device Mode field displaying "PPPoE Enabled"

17.2.5. Task 4: Select PPPoE Enabled Option for

SPRs
Once you have enabled PPPoE for the BSR, you can enable PPPoE for the SPRs.
Note: You can configure some SPRs for PPPoE and some SPRs for IP
filtering, even though they are all associated with the same BSR that is
configured for PPPoE.
To enable PPPoE for SPRs:

1. In the BSR Zoom window, from the MultiDevices menu, point to Network, and
then choose PPPoE/IP. The Multi SPRs PPPoE / IP Window dialog box
appears:

Select PPPoE
Enabled
IP filtering
currently active
Figure 17-8: PPPoE/IP Filtering dialog box showing device in IP Filters Active mode
2. Select the SPRs that you want to configure for PPPoE with the BSR.
3. Select the PPPoE Enabled option.
4. Click Apply.

Figure 17-9: Confirming applying of PPPoE to SPRs
5. Click Apply.
17.2.6. Task 5: Reset the SPRs

After you have selected the PPPoE Enabled option for the SPRs in the previous task,
you need to reset the SPRs for the configuration to take effect.

To reset the SPRs:

The Multi Reset Window dialog box appears, as displayed below.

2. Select the SPRs that you want to reset, and then click Apply.
Figure 17-11: Multi Apply Confirmation message box
3. Click Apply. The Reset message box appears, as displayed below.

17.2.7. Task 6: Verify SPRs in PPPoE Mode

After you have reset the SPR, it is recommended that you check that the new
To check that the SPRs are in PPPoE mode:
In the BSR Zoom window, from the MultiDevices menu, point to Network, and
then choose PPPoE/IP. The Multi SPR PPPoE / IP Filters Window dialog box
appears.
"PPPoE Enabled" displayed
Figure 17-13: Current Device Mode field displaying "PPPoE Enabled"


18
Configuring BSR Antenna
You can configure antenna diversity for BSR models with either two internal
antennas or two third-party external antennas. The main antenna transmits and
receives RF signals. However, the secondary antenna can be enabled for dual
antenna diversity, whereby the incoming RF signal is received by the antenna (i.e.
main/primary or secondary antenna) with the best RF signal.
Notes:
1) The current ASWipLL release allows antenna configuration only in
the Rx Mode.
2) Only the main antenna transmits.
3) Although this chapter mentions the BSR, it also applies to the PPR device.

C o n f i g u r i n g B S R An t e n n a Commissioning Manual
You can either allow only the main antenna to receive, or you can enable antenna
diversity whereby the antenna with the best RF reception receives the RF signal.
To configure the BSR antenna:
1. In the BSR Zoom window, in the workspace area, click the Antenna
Configuration icon,
-Or-
From the Configuration menu, point to RF, and then choose Antenna
Configuration, as shown below.
Figure 18-1: Choosing the Antenna Configuration command

Commissioning Manual C o n f i g u r i n g B S R An t e n n a
The BSR Antenna Configuration dialog box appears:
Figure 18-2: Antenna Configuration dialog box
2. Select one of the antenna configuration options: Main or Diversity. When the
Diversity option is selected, the antenna with the best RF reception is used to
receive the signal.
Note: The Diversity option is available only when the BSR uses two internal
antennas or two external antennas for dual-antenna diversity.

C o n f i g u r i n g B S R An t e n n a Commissioning Manual

19
Configuring Radio Transmit
Power
This chapter provides procedures for configuring ASWipLL radio transmit power,
and includes the following sections:
Overview
Defining BSR Transmit Power
Summary of Tasks
Task 1: Define the BSR Power Level
Configuring BSR Control over SPR Transmit Power
Summary of Tasks
Task 1: Enable BSR Power Management for SPRs
Task 2: Reset the SPRs
Task 3: Verify BSR Power Control is Enabled

C o n f i g u r i n g R a d i o T r a n s m i t P ow er Commissioning Manual
19.1. Overview
WipManage allows you to configure maximum radio transmit (Tx) power levels for
each ASWipLL radio (i.e. BSR and SPR). In addition, you can allow the BSR to
control the SPR's transmit power levels to ensure viable BSR-SPR wireless
communication at minimum SPR transmit power levels. The BSR adjusts the SPR's
transmit power by ensuring that a user-defined minimum received signal strength
(RSS) level is maintained at the BSR with the SPR.
Airspan’s ASWipLL radios provide transmit power compensation for power
attenuation caused by cable loss (cable connecting to external antenna). The
ASWipLL radios are designed to compensate for this power loss. Cable loss
(typically measured in dB per 100 feet) is the loss of radio transmit (Tx) power as
heat, and directly proportional to cable length and quality, and operating frequency.
The table below lists examples of cable loss per cable length.
Table 19-1: Example of cable loss per cable length
Note: Airspan does not supply external antenna cables. It is the responsibility
of the installer to provide the cable and ensure cable characteristics (e.g.
length and cable loss) enables adherence to the regulations (e.g. maximum
EIRP) of the regulatory domain in which the device is operating. For example,
in accordance with FCC regulations, when operating in unlicensed bands, the
external antennas must provide an EIRP of equal to or less than 36 dBm to
prevent interference with other radios.

Commissioning Manual Configuring Radio Transmit Power
19.2. Defining BSR Transmit (Tx) Power

The following procedure describes how to configure (using WipManage) BSR
transmit power to 27 dBm using a 40-feet cable with cable loss of 6 dB. The
procedure described is similar to SPR/IDR transmit power configuration, but
performed in the SPR Zoom window.

The figure below displays a flowchart for configuring transmit power level for a
BSR.
Figure 19-1: Flowchart for configuring BSR's transmit power level

19.2.2. Task 1: Define the BSR Power Level

The procedure below describes setting the power level to 21 dBm with loss
compensation (from cable loss) of 6 dBm. Thus, an overall power level of 27 dBm is
configured for the BSR transmit power.
To define BSR transmit power accounting for cable loss:
1. In the BSR Zoom window, from the Configuration menu, point to RF, and then
choose Power Settings.
Figure 19-2: BSR Power Settings dialog box
Regularity Domain: (read from the device’s ROM and are read-only)
displays the regularity domain that the ASWipLL unit supports (e.g. FCC).
A flag of the country is displayed where the regularity domain is associated.
The following regularity domains can occur.
− 1 = FCC (USA)
− 2 = ETSI
− 3 = Telec (Japan)
− 6 = non specific

Antenna Gain (read-only): antenna gain of the BSR’s internal antenna. If

the BSR model uses an external antenna(s), this field displays 0.
2. Ensure the Power Management Mode Active check box is cleared.
3. On the Power Level slide ruler, define the BSR’s maximum power level by
moving the slider to the desired level, e.g. 21 dBm.
4. In the Loss Compensation field, enter the power to compensate for power
attenuation due to cable length (i.e. cable loss compensation), e.g. 6 dB.
5. Click Apply
6. Click Ok, and then reset the BSR to apply the new power settings.
Therefore, taking into consideration cable loss, the total power level of 27 dBm (21
+ 6) is achieved.
Notes:
1) ASWipLL 900 MHz is capable of transmitting up to 30 dBm.
2) In accordance with FCC regulations, ASWipLL 900 transmit power is limited
to 23 dBm in the 4 Mbps mode, and 18 dBm in the 3 Mbps mode.


Once you have defined the BSR's power level, you need to reset the BSR.
To reset the BSR:
2. Click Yes.
Figure 19-5: Device Reset information box
3. Click Ok.

19.3. Configuring BSR Control over SPR

Transmit Power
The following subsections describe how to configure BSR (10.0.0.10) power control
of the SPRs (SPR 10.0.0.20 and SPR 10.0.0.36).
Note: Power control is not supported by some hardware revisions in the

3.x GHz BSRs/SPRs.

The figure below displays a flowchart for configuring BSR power control over the
SPR.
Figure 19-6: Flowchart for configuring BSR power control of SPR

19.3.2. Task 1: Enable BSR Power Management for

SPRs
For BSR to control the SPR's transmit power level, you need to enable BSR power
management. In addition, at the same time, you need to define the minimum
required RSS level of the SPR measured at the BSR. The BSR adjusts the SPR's
transmit power level according to the RSS level. In other words, if the RSS falls
below the user-defined level, BSR increases the SPR's power level, and vice versa.
To enable BSR power management of SPRs:
1. In the BSR Zoom window, from the MultiDevices menu, point to RF, and then
Check boxes
selected for
SPR
Desired SPR
RSS level
Check box
selected for
BSR
Figure 19-7: MultiDevice Power Settings dialog box
2. Click Select All to select all the SPRs.

3. In the SPR group:

a. Select the Permit Power Management Mode check box.
b. Select the Power Management Mode Active check box.
c. On the BSR Receive Power ruler, move the slide ruler to the desired
received signal strength (e.g. –68 dBm) that you want the BSR to obtain for
the SPRs (i.e. this is measured at the BSR).
4. In the BSR group, select the Power Management Mode Active check box.
5. Click Apply.
6. Select the Apply Changes to All SPRs and Apply Also BSR Device options,
and then click Apply.
7. Click Ok.

19.3.3. Task 2: Reset the SPRs

Once you have configured BSR power control of the SPRs, you need to reset the
SPRs.
To reset the SPRs:

2. Click Select All, and then Apply.
3. Click Apply.
4. Click Yes.

19.3.4. Task 3: Verify BSR Power Control is Enabled

The following procedure describes how to verify that BSR power management is
enabled.
To verify that BSR power management of SPRs' transmit power:
In the BSR Zoom window, from the MultiDevices menu, point to RF, and then
Management
modes
enabled
("YES")
Figure 19-13: Verifying BSR power management is enabled
As can be seen in the figure above, the BSR power management is enabled, which
indicated by the following fields:
Per Power Mng Mode: displays YES
Power Mng Mode: displays YES

20
Managing Frequency Tables
This chapter describes the procedures for managing the ASWipLL system’s
frequencies, and includes the following sections:
Overview
Considerations for Frequency Allocation
ROM Frequency Tables
Defining NVRAM Frequency Table for BSR-SPRs Wireless Communication
Summary of Tasks
Task 1: Add Normal Frequency Table for BSR
Task 2: Add Normal Frequency Table for SPR
Task 3: Assign Identical Frequency Table to Multiple SPRs
Task 4: Specify Operating Frequency Table ID
Note: To establish a viable link between the BSR and SPRs, the BSR and all
the SPRs must use the same frequency table. This frequency table is defined
by its index number and the frequencies comprising it.

Managing Frequency Tables Commissioning Manual
20.1. Overview
The ASWipLL system provides up to 64 frequency tables, each table consisting of
up to 97 frequencies. The first 32 (0 to 31) frequency tables are stored in the
ASWipLL device's read-only memory (ROM); the next 32 (31 to 63) frequency
tables are stored in the ASWipLL device's non-volatile random access memory
(NVRAM). NVRAM is a type of memory that retains its contents even when the
device’s power is turned off.
The frequency table is used for wireless communication between the BSR/PPR and
SPRs/IDRs. When using frequency tables consisting of multiple frequencies for
frequency hopping, synchronization can also be implemented (see Chapter 21,
"Defining Synchronization").
ASWipLL allows you to define the following types of frequency tables:
Multiple frequencies: frequency table consisting of multiple frequencies for
frequency hopping. These frequency tables are used for wireless communication
based on frequency hopping. The frequency on which the packet is transmitted
changes (i.e. "hops") every 50 ms. These multiple frequency tables can be
defined in one of the following methods:
Normal: frequencies entered manually
Gap Algorithm: frequencies entered automatically based on the following
user-defined parameters:
− First frequency in the frequency table
− Size of frequency table (i.e. amount of frequencies – number of "hops")
− Steps ("hops") between consecutive frequencies
Single frequencies: frequency table consists of only one frequency (i.e. no
frequency hopping implemented)

Commissioning Manual Managing Frequency Tables
For Normal frequency tables, the NVRAM frequency tables support a maximum of
up to 388 bytes. Each frequency in an NVRAM frequency table takes up 1 byte. In
addition, each frequency table takes up an additional 1 byte.
The following table shows an example of the number of frequency tables possible,
based on byte limitations:
Table 20-1: NVRAM frequency tables and used bytes
Frequency Table Bytes

64 65 (i.e. 64 x 1 byte for each frequency, plus 1 byte for the table)
32 33
Single (i.e. frequency entered 9 10 (i.e. 9 x 1 byte, plus 1 byte for the table)
times)
Therefore, the maximum 388 bytes is sufficient for:

Two tables of 126 frequencies each, and two tables of 66 frequencies each, or
Five tables of 64 frequencies each, and one table of 62 frequencies
Notes:
1) Gap frequency tables are unlimited with regards to bytes.
2) For a frequency table consisting of a single frequency, you need to enter
the frequency nine times in the table.
3) For normal frequency tables, at least 9 frequencies must be entered.
Therefore, if less than 9 frequencies are used, the frequencies must be entered
repetitively (and in the same order) until at least 9 frequencies are entered and
the series is complete. For example, if only five frequencies are used (e.g. F1,
F2, F3, F4, and F5), the frequencies would be entered as such: F1, F2, F3, F4,
F5, F1, F2, F3, F4, F5 (i.e. at least 9 entries -- in this case 10 entries to
complete the series).
4) For BSDU synchronization of BSRs, you need to enter at least 11 frequency
hops.

20.1.1. Considerations for Frequency Allocations

Certain considerations should be adhered to for frequency allocations for multiple
BSRs whose RF sectors may be adjacent, overlapping, or when using omni-
directional antennas. The considerations mentioned below are to prevent more than
one BSR transmitting on the same frequency at any given time, which may result in
radio interference that may cause loss of communication between BSR and its SPRs.
The considerations of frequency allocations for communication depends on the
operating frequency band type (i.e. licensed or unlicensed) and type of transmission
(i.e. FDD or TDD):
Licensed bands (only one frequency is used, i.e. no hopping):
FDD: ensure minimum separation of 2 MHz, for example:
− BSR #1 transmits on 3725 MHz
TDD: ensure minimum separation of 4 MHz, for example:
Unlicensed bands (multiple orthogonal frequencies used for frequency
hopping):
FDD: ensure minimum separation of 2 MHz
TDD: ensure minimum separation of 4 MHz

For example, when using Gap (algorithms) frequency tables, one BSR can be
configured to hop frequencies by 2, while the other BSR can be configured to
hop frequencies by 6:
Table 20-2: Example of different hopping sizes for adjacent BSRs

Frequency Frequency
index BSR #1 BSR #2
(hops by 2) (hops by 6)
1 1 1
2 3 7
3 5 13
4 … …
In this way, at any given time, the two BSRs transmit on a different frequency
from the other (except for frequency 1 due to orthogonal method).
In summary, Airspan recommends increasing frequency allocations as much as
possible between BSRs with adjacent and overlapping sectors.
Note: In all ASWipLL bands, the frequency spacing is 1 MHz. However, in

ASWipLL 3.x GHz the frequency spacing can be 1 MHz or 1.75 MHz (the
spacing, which is factory set, is determined by Airspan).

20.1.2. ROM Frequency Tables

The ROM Frequency Table command allows you to view frequency-hopping
tables 0 through 31, which are stored in the device's ROM.
Note: The procedure for viewing ROM frequency tables is similar for the BSR
and SPR. The only difference is that for the BSR the BSR Zoom window is
used; for the SPR, the SPR Zoom window is used.
To view the ROM frequency tables:

From the Configuration menu, point to RF, and then choose ROM Frequency
Table. The ROM Frequency Tables window appears, as displayed in
Figure 20-1.
Figure 20-1: ROM Frequency Tables window

The ROM Frequency Tables window displays columns of frequency tables. Each
column is consecutively numbered (i.e. Table 0, Table 1, Table 2, and so on).
The RF Type field (read-only) displays the frequency band in which the
ASWipLL system is operating.
The Frequency Table ID field (read-only) displays the frequency table that the
BSR is using.

20.2. Defining NVRAM Frequency Table for

BSR-to-SPRs Wireless Communication
The sections below describe the procedure for adding an NVRAM frequency table
using the Normal method (as opposed to Gap) for wireless communication between
a BSR and multiple SPRs. The configuration example describes adding an NVRAM
frequency table consisting of 23 frequencies, starting from 2,402 MHz and ending at
2,468 MHz, with 3 MHz gap between each consecutive frequency.

The figure below displays a flowchart for configuring a frequency table for BSR-to-
SPRs wireless communication.
Figure 20-2: Flowchart for adding an NVRAM frequency table to BSR and SPRs

20.2.2. Task 1: Add Frequency Table for BSR

The first task you need to perform is to add an NVRAM frequency table for the
BSR. The following procedure describes adding an NVRAM frequency table using
the Normal method (i.e. frequencies entered manually). In our example, you need to
add a frequency table consisting of 23 frequencies, starting from 2402 MHz and
ending at 2468 MHz, with 3 MHz gap between each consecutive frequency.
To manually add a Normal frequency table:
1. In the BSR Zoom window (of BSR 10.0.0.10), from the Configuration menu,
point to RF, and then click NVRAM Frequency Tables.
2. In the NVRAM Frequency Tables dialog box, click Add. The Frequency Tables
Add dialog box appears, as displayed in Figure 20-3.

Figure 20-3: Adding frequencies using Normal method
3. Click the Normal Table tab.

4. In the Insert New Table To field, enter the frequency table’s index number (32
to 63). If you do not enter a number, WipManage automatically assigns it the
next available consecutive Frequency Table number.
5. In the Valid Frequencies pane (i.e. right pane), select the desired frequency, and
then click the left-pointing arrow button to add the frequency to the
Frequency Table pane (i.e. left pane). For example, 2402, 2405, 2408, 2411,
2414, 1417, 2420, 2423, 2426, 2429, and 2432.

6. Click OK. The Frequency Tables Add dialog box closes, and the added Normal
Frequency table appears in the Frequency Tables dialog box, as displayed below.
Added
frequency
table ID 32
Frequencies
(total of 23)
Frequency
table ID (0)
currently used
Figure 20-4: Added NVRAM frequency table (ID 32)

20.2.3. Task 2: Add Frequency Table for SPR

Once you have added the Normal frequency table for the BSR, you need to add an
identical frequency table for the SPR. This procedure is similar to adding a
frequency table for the BSR, but performed in the SPR Zoom window. The
frequency table must have the same frequency table ID number and contain the same
frequencies.
To manually add a Normal frequency table:
1. In the SPR Zoom window (of SPR 10.0.0.20), from the Configuration menu,
point to RF, and then click NVRAM Frequency Tables; The NVRAM
Frequency Tables dialog box appears.
2. In the NVRAM Frequency Tables dialog box, click Add. The Frequency Tables
Add dialog box appears, as displayed in Figure 20-3.

Figure 20-5: Adding frequencies using Normal method
3. Ensure the Normal Table tab is selected.

4. In the Insert New Table To field, enter the frequency table’s index number (32
to 63), e.g. 32. (If you do not enter a number, WipManage automatically assigns
it the next available consecutive Frequency Table number.)

5. In the Valid Frequencies pane (i.e. right pane), select the desired frequency, and
then click the left-pointing arrow button to add the frequency to the
Frequency Table pane (i.e. left pane). For example, 2402, 2405, 2408, 2411,
2414, 1417, 2420, 2423, 2426, 2429, 2432, and so on.
6. Click OK. The Frequency Tables Add dialog box closes, and the new Frequency
table appears in the Frequency Tables dialog box, as displayed below.
Added
frequency
table ID 32
Frequencies
(total of 23)
Frequency
table ID (0)
currently used
Figure 20-6: Added NVRAM frequency table (ID 32)

20.2.4. Task 3: Assign Identical Frequency Table to

Multiple SPRs
The BSR and the SPRs (with which the BSR is to establish a wireless connection)
must use the same frequency table. This means that for the BSR and the SPRs, the
frequency table has the same frequency table index number and is comprised of the
same frequencies.
Note: Assigning a new and identical frequency table for the BSR and multiple
SPRs can only be performed when you already have an air and network link
between the BSR and SPRs. The frequency table used to establish the initial
link is defined when installing the SPRs, by assigning the same ROM
frequency table index number to the BSR and SPRs, using WipConfig.
You need to assign the frequency table that you defined for the SPR (in the section
above) to the remaining SPRs. This assures that all SPRs have the same frequency
table as the BSR.
To assign the same NVRAM Frequency table to associated SPRs:
1. In the BSR Zoom window, from the MultiDevices menu, point to RF, and then
choose Frequency Tables.
The Multi SPRs Frequency Tables dialog box appears, listing all the SPRs
associated with the BSR, and the frequency tables of a selected SPR, as
displayed in Figure 20-7.

Frequency
table (ID 32)
of selected
SPR
Selected SPR
(i.e. 10.0.0.20)
with unique
Hashed Table
value
Figure 20-7: Multi SPRs Frequency Tables dialog box
2. Select the all the SPRs (with which you want to communicate with the BSR), by
clicking the Select All button.
3. Select the SPR (i.e. 10.0.0.20) for which you defined the NVRAM Frequency
table (in Section 20.2.3, "Task 2: Add Frequency Table for SPR"). Note that in
our example, the Hashed Table value of SPR 10.0.0.20 is 159710956, and of
SPR 10.0.0.36 is 0.
The selected SPR’s NVRAM Frequency table appears in the Frequency Tables
list, located in the upper pane.
4. Click Apply. The Multi-Apply Confirmation box appears, as displayed below.

Figure 20-8: Confirming assigning SPR’s Frequency table to multiple SPRs
5. Click Apply.
The NVRAM Frequency table of SPR 10.0.0.20 is copied to the other SPRs.
This is indicated by all SPRs having identical Hashed Table values. In our
example, all SPRs now have the Hashed Value of 159710956 (inherited from
SPR 10.0.0.20). If you click on any SPR in the list, the same frequency table will
appear in the upper pane, i.e. Frequency Table index 32.
Identical
Hashed Table
values
Figure 20-9: SPRs assigned identical NVRAM Frequency tables

20.2.5. Task 4: Specify Operating Frequency Table ID

After you add the frequency table to BSR and SPRs/IDRs, you need to instruct the
devices to use this specific frequency table. This is performed at the BSR.
To specify the operating frequency table ID:
1. In the BSR Zoom window, from the Configuration menu, point to RF, and then
choose Hopping Configuration. The Hopping Configuration dialog box
appears.
Figure 20-10: Entering frequency table ID number
2. In the Frequency Table ID field, enter (as shown in the figure above) the
frequency table ID that you added to the BSR and SPRs (i.e. ID #32).
3. Click Apply. The following message box appears.
Figure 20-11: Message box informing to reset device for changes to take affect
4. Click OK, and then click Close to close the Hopping Configuration dialog box.


Once you have specified the frequency table for BSR-SPRs wireless
communication, you need to reset the BSR.
To reset the BSR:
2. Click Yes.
Figure 20-13: Device Reset confirmation box
3. Click Ok.


21
Defining Synchronization
This chapter describes procedures for synchronizing an ASWipLL Base Station and
includes the following section:
Overview
Synchronizing a Base Station
Summary of Tasks
Task 1: Enable GPS
Task 2: Reset BSDU
Task 3: Verify GPS Synchronization
Task 4: Define Synchronization for BSDUs
Task 5: Reset the BSDUs
Task 6: Verify BSDU Synchronization
Task 7: Enable BSR Synchronization
Task 8: Reset BSRs
Task 9: Verify BSRs Synchronization

Defining Synchronization Commissioning Manual
21.1. Overview
WipManage allows you to synchronize the ASWipLL system when implementing
frequency hopping for BSR-SPR wireless communication (i.e. in the unlicensed
bands). Synchronization ensures that ASWipLL devices transmit on different
frequencies at any given time from one another, thereby, avoiding traffic collisions.
The following ASWipLL system components can be synchronized:
Daisy-chained BSDUs at a Base Station.
Multiple BSRs at a Base Station connected to a BSDU(s).
Multiple Base Stations: synchronized by using a GPS (connected to a BSDU) at
every Base Station. Synchronization ensures that all Base Stations operate with
the same GPS clock signal (i.e. BSDUs at all Base Stations send a
synchronization pulse at the same time to the BSRs). Similar to BSR and BSDU
synchronization at a single Base Station, all Base Stations must use the same
frequency table for multiple Base Station synchronization.
Warning: Accurate frequency planning must be performed for multiple Base

Station synchronization to prevent adjacent channel interference between Base
Stations.
Synchronization in the ASWipLL system is controlled by the BSDU and is based on

frequency hopping that is used in BSR-SPR wireless communication. The same
frequency table used for BSR-SPR communication is used for this synchronization.
Synchronization by the BSDUs is based on frequency table size. This is the number
of frequencies composing the frequency table that the BSRs and SPRs use for
communication. The BSDU sends a synchronization pulse to the BSRs at intervals
calculated by frequency table size multiplied by 50 msec (time between "hopping"
from one frequency to the next). This synchronization pulse instructs the BSRs to
"hop" the transmitted data onto a specific frequency (in the frequency table) referred
to as phase. This occurs even if the BSR has not completed a cycle of transmitting
the data on all the frequencies in the frequency table.

Commissioning Manual Defining Synchronization
For example, assume the frequency phase for BSR #1 is F1 (e.g. 2,402 MHz). If the
BSR is transmitting on F5 (e.g. 2,414 MHz) when the BSDU sends a
synchronization pulse, the BSR "hops" this transmitted data back to F1.
The table below displays an example of multiple BSRs using the same frequency
table, but each having a different frequency phase.
Table 21-1: BSR synchronization and phase frequencies
BSR Frequency table (phase per BSR)

1 2 3 4 5 6 7 8 9 10
#1 2402 2405 2408 2411 2414 2417 2420 2423 2426 2429
(phase 1)
#2 2402 2405 2408 2411 2414 2417 2420 2423 2426 2429
(phase 4)
#3 2402 2405 2408 2411 2414 2417 2420 2423 2426 2429
(phase 7)
#4 2402 2405 2408 2411 2414 2417 2420 2423 2426 2429
(phase 5)
In the table above, at any given moment, the BSRs transmit on a different frequency
to one another. For example, when the BSRs receive a synchronization pulse from
the BSDUs, the BSRs transmit on the following frequencies: 2402 for BSR #1; 2411
for BSR #2; 2420 for BSR #3; and 2414 for BSR #4.
Notes:
1) Synchronization is applicable only when ASWipLL implements frequency
hopping for wireless communication.
2) Synchronization is available depending on the regularity domain in which
the ASWipLL devices are operating.

21.2. Synchronizing a Base Station

The following subsections describe the procedures for synchronizing a Base Station
consisting of two BSRs, two BSDUs, and a GPS connected to one of the BSDUs, as
Figure 21-1: Configuration example for synchronizing a Base Station


The flowchart below displays a summary of tasks for configuring synchronization at
a Base Station.
Figure 21-2: Flowchart for synchronizing a Base Station

21.2.2. Task 1: Enable GPS

A GPS can be used for synchronizing BSDUs (and thereby BSRs) at a single Base
Station. For synchronizing between Base Stations, a GPS is mandatory.
The GPS is connected to one of the BSDUs and is activated in WipManage's BSDU
Zoom window. The BSDU to which the GPS is connected is automatically assigned
as Master BSDU.
In our example, the GPS is connected to BSDU 10.0.0.5.
To activate the GPS:
1. In the WipManage main window, in the Database tree, double-click the BSDU
branch (i.e. 10.0.0.5) to which the GPS is connected. The BSDU Zoom
window appears.
2. From the Configuration menu, choose GPS. The GPS dialog box appears, as
displayed below.
Figure 21-3: Enabling GPS
3. Select the Enable GPS check box to enable the GPS.

4. Click OK.
5. Reset the BSDU.

21.2.3. Task 2: Reset BSDU

Once you have selected the Enable GPS check box, you need to reset the BSDU to
activate the GPS.
To reset the BSDU:
1. In the BSDU Zoom window (of BSDU 10.0.0.5), from the Configuration menu,
choose Reset. The GPS dialog box appears, as displayed below:
2. Click Yes.
Figure 21-5: Device Reset confirmation box
3. Click OK.

21.2.4. Task 3: Verify GPS Synchronization

Once you have enabled the GPS and reset the BSDU to which the GPS is connected,
you can verify that the GPS is working.
To verify GPS operation:
In the BSDU Zoom window (of BSDU 10.0.0.5), from the Configuration menu,
choose GPS. The GPS dialog box appears, as displayed below:
Figure 21-6: Verifying GPS is enabled
The GPS dialog box indicates that the GPS is synchronizing the ASWipLL system
by the following indications:
Enable GPS: selected
GPS Powered On: displays "YES" (i.e. GPS receiving power)
GPS Synchronized: displays "YES" (i.e. GPS synchronized by a satellite
signal)
Time: GPS clock time

In addition, the BSDU Zoom window provides Status LEDs that indicate the status
of the GPS, as described in the table below:
Table 21-2: Status LED description for GPS

LED Color Status Meaning
GPS Green On GPS is connected to the BSDU
Blinking Receiving a satellite signal
21.2.5. Task 4: Define Synchronization for BSDUs

You can enable synchronization among daisy-chained BSDUs at a Base Station. The
BSDU that controls the synchronization (referred to as Master BSDU), depends on
whether a GPS is implemented:
GPS implemented: BSDU to which the GPS is physically connected receives
satellite time signals from the GPS, and therefore, controls the synchronization
between the BSDUs. This BSDU is referred to as the Master BSDU.
Without GPS: one of the BSDUs (1 to 4) can be defined to control
synchronization (i.e. Master BSDU). If no BSDU is defined, then the first
powered-on BSDU automatically controls synchronization.
Notes:
1) Ensure BSDU synchronization ports are connected between BSDUs. For a
detailed description on cabling these ports, refer to the ASWipLL Hardware
Installation Guide.
2) Ensure identical frequency table size is configured for all BSDUs.
You need to define the number of frequencies composing the frequency table used
for BSR-SPR wireless communication. This is later used for enabling
synchronization of multiple BSRs by the BSDU. In addition, you need to define a
unique synchronization ring ID number for the BSDUs.
In the configuration example, the GPS is connected to BSDU 10.0.0.5, and
therefore, this BSDU will automatically be assigned as the Master (and BSDU
10.0.0.6 as the slave). In the following procedure, you need to assign BSDU 10.0.0.5
ring ID 8, and BSDU 10.0.0.6 ring ID 5.

To configure BSDU synchronization:

1. Ensure that you have connected the SYNC ports between BSDUs.
2. In the WipManage main window, in the Database tree, double-click the BSDU
branch (e.g. 10.0.0.5). The BSDU Zoom window appears.
3. From the Configuration menu, choose Hopping Configuration (or on the
toolbar, click ). The Hopping Configuration BSDU dialog box appears, as
displayed below.
Figure 21-7: Synchronization defined for BSDU 10.0.0.5 (ring ID 8)
4. In the Freq. Table Size field, enter the number of frequencies that compose the
frequency table that is used for BSR-SPR communication (e.g. 23).
5. Select the Synchronization Ring Mode On check box.
6. In the Synchronization Ring ID field, enter an arbitrary identification number
(0 through 15) for this BSDU in the daisy chain (e.g. 8).

7. From the Hop Length drop-down list, select the hopping time between
frequencies:
Regular Hop Length: ± 50 msec
Short Hop Length: 25 msec.
8. Click Apply.
9. Perform Steps 1 through 8 for BSDU 10.0.0.6. The Hopping Configuration
BSDU dialog box for BSDU 10.0.0.6 is displayed below, showing its Ring ID
defined as 5:
Figure 21-8: Synchronization defined for BSDU 10.0.0.6 (ring ID 5)

21.2.6. Task 5: Reset the BSDUs

After you have configured the BSDUs' synchronization parameters, you need to
reset the BSDUs.
To reset the BSDUs:
1. In the WipManage Main window, from the MultiDevices menu, point to
BSDUs, and then choose Reset.
Figure 21-9: Multi BSDU Reset dialog box

2. Click Select All, and then click Apply.
3. Click Yes.

21.2.7. Task 6: Verify BSDU Synchronization

Once you have configured BSDU synchronization, you can verify that these
synchronization settings have been applied.
To verify BSDU synchronization:
In the WipManage Main window, from the MultiDevices menu, point to
BSDUs, then to RF, and then choose Hopping Configuration.
Figure 21-11: Verifying BSDU synchronization

The following parameters verify that the correct BSDU synchronization has been
applied:
Freq Table Size: identical for all BSDUs (this is crucial for BSR
synchronization by the BSDUs), i.e. "23".
Sync. Mode: synchronization working (i.e. "YES")
Sync. Status: indicates synchronization working - BSDU 10.0.0.5 is master
(Master) and BSDU 10.0.0.6 is slave ("Synchronized")
Synchronization Ring ID: unique identifying number assigned to each BSDU.
In our example, BSDU 10.0.0.5 is ID "8"; BSDU 10.0.0.6 is ID "5".
Sync to Master ID: indicates all BSDUs are synchronized to a specific Master
BSDU (i.e. BSDU 10.0.0.5 or ID "8")
In addition, you can verify synchronization by viewing the Status LEDs in the
BSDU Zoom window. The table below describes the synchronization LEDs:
Table 21-3: Status LEDs in the BSDU Zoom window

LED Color Status Meaning
HSP (hop Green On BSDU synchronization process is active
synchronization
process)
State Green Only right LED on Synchronization process is starting
(two LEDs) Both LEDs on BSDU is the master unit
Only left LED on BSDU is a slave unit
Both LEDs off BSDU sync pulse lost
Blinking Receiving a satellite signal
HSP P (hop Green On Change state for the HSP pulse
synchronization
process pulse)

21.2.8. Task 7: Enable BSR Synchronization

The synchronization of BSRs at a Base Station is performed by the BSDU. All the
BSRs must be configured to use the same frequency table ID (used for BSR-to-SPR
wireless communication). In addition, each BSR must be configured to start
transmitting on a different frequency listed in the frequency table (referred to as
phase). This prevents more than one BSR or SPR using the same frequency at any
given time, thereby preventing collisions and loss of communication.
The following procedure enables BSR synchronization for BSRs 10.0.0.10 and BSR
10.0.0.14. For each of these BSRs, a unique phase frequency index is defined: 1 for
BSR 10.0.0.10 and 4 for BSR 10.0.0.14.
To configure BSR synchronization:
1. In the BSR Zoom window (i.e. BSR 10.0.0.10), from the Configuration menu,
point to RF, and then choose Hopping Configuration. The Hopping
Configuration dialog box appears.
2. Select the Synchronization Ring Mode On check box. The following appears:
Figure 21-12: Enabling synchronization for BSR 10.0.0.10 (phase = 1)

3. Ensure that the correct frequency table ID appears in the Frequency Table ID
field. This must be identical for all BSRs at the Base Station.
4. In the Synchronization Ring Phase field, enter the index of the frequency on
which the BSR starts transmitting when a synchronization pulse is received from
the BSDU. This must be unique for each BSR that is connected to the BSDU(s).
5. From the Hop Length drop-down list, select the time data is "hopped" from one
frequency to the next:
Regular Hop Length: ± 50 msec
Short Hop Length: 25 msec.
6. Click Apply.
7. Perform Steps 1 through 6 for BSR 10.0.0.14. The Hopping Configuration
dialog box for BSR 10.0.0.14 is displayed below, showing its Synchronization
Ring Phase field value defined as 4:
Figure 21-13: Enabling synchronization for BSR 10.0.0.14 (phase = 4)

21.2.9. Task 8: Reset BSRs

To apply the BSR synchronization settings, you need to reset the BSRs.
To reset the BSRs:
1. In the WipManage Main window, from the MultiDevices menu, point to BSRs,
and then choose Reset.
Figure 21-14: Multi BSR Reset dialog box

2. Click Select All, and then Click Apply.
3. Click Yes.

21.2.10. Task 9: Verify BSRs Synchronization

Once you have enabled BSRs synchronization, you can verify that the BSRs are
synchronized by the BSDU.
To verify BSRs synchronization:
In the WipManage Main window, from the MultiDevices menu, point to BSRs,
then to RF, and then choose Hopping Configuration.
Figure 21-16: Verifying BSR synchronization

The Multi BSR Hopping Configuration window displays the BSRs synchronization
indicated by the following:
Sync Mode: synchronization is enabled (i.e. "YES")
Sync. Status: BSR is synchronized (i.e. "Synchronized") by BSDU
Sync. Ring Phase: index of frequency (in the frequency table) for transmitting
at every synchronization pulse received from the BSDU. For BSR 10.0.0.10 this
is "1"; for BSR 10.0.0.14 this is "4".
Sync. To Master ID: BSDU controlling synchronization (i.e. Master BSDU ID
"8")


22
Defining Transmission Rate
This chapter describes the procedures for defining transmission rate in the
ASWipLL system.
Overview
Defining Maximum Rate Mode
Summary of Tasks
Task 1: Define Maximum Rate Mode
Task 2: Reset the SPRs/IDRs
Defining Transmission Rate Options

Defining Transmission Rate Commissioning Manual
22.1. Overview
WipManage allows you to modify the transmission rate mode (initially configured
by WipConfig during initialization) of your ASWipLL system. This rate must be
identical for the BSR and its associated SPRs/IDRs for a viable air and network link
to exist.
WipManage also allows you to define various rate options, which includes the
following:
Allowing the ASWipLL system to operate either at a fixed rate regardless of
radio conditions, or at an adjustable rate according to radio conditions of each
SPR and IDR.
Reducing the maximum rate to a rate lower than the configured maximum rate
mode. This may be useful when, for example, a poor link exists between BSR
and SPRs/IDRs, and instead of transmitting at the maximum rate, you can reduce
the rate to overcome poor link conditions and sustain a viable link.
Selecting transmission rate for broadcast packets that are sent from the BSR to
SPRs/IDRs.

Commissioning Manual Defining Transmission Rate
22.2. Defining Maximum Rate Mode

The following subsections describe the procedures for changing the maximum rate
mode of a BSR and its associated SPRs from 3 Mbps to 4 Mbps. Any modification
to maximum rate mode requires resetting the BSR and SPR/IDR devices.
Figure 22-1: Configuration example for defining maximum rate mode


The flowchart in the figure below displays a summary of tasks for changing the
maximum rate mode for the BSR and its associated SPRs.
Figure 22-2: Flowchart for defining maximum rate mode

22.2.2. Task 1: Define Maximum Rate Mode

To change the maximum transmission rate mode for the BSR and SPRs, you can use
the MultiDevices menu in the BSR Zoom window. This method is recommended to
ensure that the BSR and its associated SPRs have identical maximum rate mode
settings.
To define maximum rate mode for BSR and SPRs:
1. In the BSR Zoom window, from the MultiDevices menu, choose Rate; The
Multi Rate Window dialog box appears, as displayed below:
Max Mode
list for BSR
Max Mode
list for SPR
Figure 22-3: Selecting a different maximum rate mode

2. In the SPR group, from the Max Mode drop-down list, select 4 Mbps.
3. In the BSR group, from the Max Mode drop-down list, select 4 Mbps.
4. In the BSR group, click Apply.
22.2.3. Task 2: Reset the SPRs/IDRs

After changing the SPR/IDR maximum rate mode, you need to reset the SPRs/IDRs.
Note: Reset the SPRs/IDRs before resetting the BSR to ensure that the BSR-
SPRs/IDRs network communication link is retained.

To reset the SPRs/IDRs:

1. In the BSR Zoom window, from the MultiDevices menu, choose Reset; The
Multi Reset Window dialog box appears, as displayed below:
2. Select all the SPRs/IDRs, and then click Apply.

The Multi Apply Confirmation Window confirmation box appears, as displayed

below:
3. Click Apply; The Reset confirmation box appears, as displayed below:
4. Click Yes.


After resetting the SPR/IDR max, you need to reset the BSR for maximum rate
mode changes to take effect.
To reset the BSR:
1. In the BSR Zoom window, from the Configuration menu, choose Reset; The
Reset confirmation box appears, as displayed below.
2. Click Yes to confirm resetting the device; The Device Reset message box

22.3. Defining Transmission Rate Options

Once you have configured the maximum rate mode of your ASWipLL system,
WipManage enables you to select various transmission rate parameters controlled by
and configured at your BSR.
To define transmission rate parameters:
1. In the BSR Zoom window, from the Configuration menu, choose Rate; The Rate
dialog box appears, as displayed below:
Figure 22-9: Rate dialog box
2. In the Rate Mode group, select one of the following options:

Automatic Rate Adjustment: system operates at the maximum rate
depending on RF conditions of each SPR and IDR. It allows changes in
transmission rate when conditions are poor, thus, avoiding excessive BER
and possible dropout.

Fix Mode (Max): system always operates at the maximum rate irrespective
of RF conditions. Thus, if conditions are poor, a loss of link may occur at
this maximum rate.
3. In the Max Rate group, select a lower transmission rate than the configured
maximum rate mode (i.e. defined in the Max Mode drop-down list) or select the
same rate. This may be useful when, for example, a poor link exists between
BSR and SPRs/IDRs. For example, if your Max Mode is 4 Mbps, instead of
transmitting at 4 Mbps, you can reduce transmit rate to 1.33 Mbps to overcome
poor link conditions. The maximum rate options vary depending on the Max
Mode settings: for 4 Mbps mode, the Max Rate options include 1.33 and 4
Mbps; for 3 Mbps mode, the Max Rate options include 1, 2, and 3 Mbps).
4. In the Broadcast Rate group, select the transmission rate for broadcast packets
that are sent from the BSR to SPRs/IDRs. By default, the lowest rate is selected
to ensure that all SPRs/IDRs (even those with lower transmission rates) receive
the broadcast packets. If all the SPRs/IDRs are configured for identical
maximum rates e.g. 4 Mbps, then you can set the broadcast rate to 4 Mbps. The
broadcast rate options vary depending on the Max Mode settings: for 4 Mbps
mode, the broadcast rate options include 1.33 and 4 Mbps; for 3 Mbps mode, the
broadcast rate options include 1, 2, and 3 Mbps.
5. Click OK.
Note: The Broadcast Rate group is available only when the ASWipLL device
is configured in the bridge mode and the Automatic Rate Adjustment option
is selected in the Rate Mode group.


23
Defining Security
This chapter describes the procedures for defining ASWipLL security settings, and
includes the following sections:
Overview
Defining Management Stations
Defining SNMP Read/Write Community Strings
Defining Public-Key Encryptions
Adding IP Filters
Defining IntraComm Gateways

Defining Security Commissioning Manual
23.1. Overview
WipManage allows you to define the following basic security settings:
Management stations: based on IP address to receive device-generated traps
(and to manage the device if the Manager Mode feature is set to "On"). These
stations are listed in the Managers Table.
WipManage station rights: WipManage station rights for managing the
ASWipLL device, i.e. read (Get) and write (Set) SNMP community strings.
Public-key encryptions: defines public and private encryption keys for the BSR
and SPR respectively. The encryption settings are defined for a BSR and its
associated SPRs for encryption/decryption.
IP Filters: allows you to add IP filters based on protocol type, port number, and
source IP address for the BSR and SPR devices.
IntraComm Gateways: enables IP filtering for communication among SPRs,
using third-party external routers (or gateways). The third-party router is
connected to the BSR. The BSR receives packets from SPRs destined for other
SPRs, and forwards the packets to a third-party router. The router checks if the
IP address of the destined SPR appears in its table. If it doesn’t appear, the router
discards the packet; if it does appear, the router sends the packet to the BSR,
which sends it to the destined SPR.

Commissioning Manual Defining Security
23.2. Defining Management Stations

WipManage allows you define management stations for receiving device-generated
traps. The management station is typically WipManage, but it can also be a third-
party management station such as HP OpenView.
Up to five management stations can be defined for each device (i.e. BSR, BSDU,
and SPR). The management stations are defined by IP address.
Note: For internally generated traps (i.e. traps generated by WipManage), no

management station needs to be defined.
The following describes the procedure for adding a management station (manager)
to a BSR. This procedure is similar to adding management stations for the other
devices.
To add management stations (e.g. for a BSR):
1. In the BSR Zoom window, from the Configuration menu, choose Managers
Table. The Managers Table dialog box appears.
Figure 23-1: Managers Table dialog box

2. Click the Add button. The Manager Entry – Add dialog box appears.
Figure 23-2: Managers Entry Add dialog box
3. In the IP Address field, enter the station’s IP address.

4. Click OK.
23.3. Defining SNMP Read/Write Community

Strings
WipManage allows you to configure a device's read/write SNMP agent community
rights. These rights are used by WipManage (or a third-party management station
such as HP OpenView) to access and manage the device by SNMP MIB traps. The
read community is for WipManage to retrieve configuration settings from the
device. The write community string is for WipManage to apply configuration
settings to the device.
The procedures for defining the BSR, SPR, and BSDU SNMP read/write
community strings are similar, but performed in their respective Zoom windows (i.e.
BSR Zoom, SPR Zoom, and BSDU Zoom window respectively).
The following subsections describe the procedures for defining SNMP read/write
community strings for a BSR.


The figure below displays a flowchart for configuring SNMP read/write community
rights for managing a BSR.
Figure 23-3: Flowchart for defining SNMP read/write community strings
23.3.2. Task 1: Define BSR's SNMP Read/Write

Community Strings
You first need to access the BSR (using the default community strings), and then
modify the BSR's SNMP read/write community strings. By default, WipManage
assigns public and private to read and write community strings respectively.

To define BSR's SNMP read/write community strings:

1. In the BSR Zoom window, from the Configuration menu, point to Security, and
then choose Agent Security. The Agent Security dialog box appears.
Figure 23-4: Agent Security dialog box
2. In the Read Community field, enter the BSR's read privilege password (e.g.
"wipll_admin").
3. In the Write Community field, enter the BSR's write privilege password (e.g.
"jlkpff").
4. In the Trap Community field, define the SNMP community string of the BSR
traps. This is relevant only for third-party SNMP external management stations
(e.g. HP OpenView); WipManage management stations receive traps regardless
of community string.

5. To increase access security by allowing only management stations (e.g.

WipManage) whose IP addresses appear in the Managers table (see Section 23.2,
"Defining Management Stations") to manage the BSR, perform the following:
a. Select the Advanced check box.
b. From the Manager Mode drop-down list, select "On". ("Off" allows any
station to manage the WipManage, although this depends on Read and Write
community settings).
6. Click OK.
Figure 23-5: Defined SNMP strings
Warning: If you have enabled ("On") the Manager Mode, before closing the
BSR Zoom window, ensure that you have defined a management station (see
Section 23.2, "Defining Management Stations".

23.3.3. Task 2: Verify BSR's SNMP Read/Write Strings

Once you have defined the BSR's SNMP read/write community strings, you can
verify these settings.
To verify BSR's read/write community strings:
1. Close the BSR Zoom window.
2. In the WipManage Main window, in the BS view, right-click the BSR.
Get/Set community
strings displaying
configured settings
Figure 23-6: Verifying new SNMP settings in BSR Properties dialog box
3. Verify that the Get Community (i.e. read) displays "wipll_admin".

4. Verify that the Set Community (i.e. write) displays "jlkpff".
Notes:
1) To access and manage the BSR, the Get and Set community strings in the
BSR Properties dialog box must be correct.
2) To verify the SPR's read/write community settings, in the BSR Zoom
window, right-click the SPR index icon, and then from the shortcut menu
choose Edit. Verify the settings in the Get and Set Community fields.

23.4. Defining Public-Key Encryptions

WipManage allows you define private/public key encryption-based security between
the BSR and SPR. The transmitted data is encrypted using private and public keys.
The encryption feature is enabled at the BSR. The encryption key (i.e. Public and
Private) must be identical for the BSR and SPR.

The figure below displays a flowchart for configuring key encryption-based security
for a BSR and its associated SPR.
Figure 23-7: Flowchart for defining public-key encryption

23.4.2. Task 1: Enable Encryption-Based Security

You first need to enable key encryption-based security at the BSR. In addition, at the
same time, you need to define the BSR's public key value.
To enable encryption-based security and define BSR's public key value:
1. In the BSR Zoom window, from the Configuration menu, point to Security, and
then choose Air Protocol Security. The Security Configuration dialog box
appears.
Figure 23-8: Security Configuration dialog box
2. From the Encryption Mode drop-down list, enable encryption by selecting

Enable.
3. In the Public Key field, enter the BSR's public key.
4. Click Apply.


For the key encryption settings in Task 1 to take effect, you need to reset the BSR.
To reset the BSR:

Note: Verify that key-encryption is enabled, by ensuring that the Encryption

Mode field in the Security Configuration dialog box displays Enabled.

23.4.4. Task 3: Define SPR's Private Key

Once you have configured key encryption for the BSR, you can configure the SPR's
private key. The private key value must be identical to the BSR's public key value.
To define the SPR's private key:
1. In the SPR Zoom window, from the Configuration menu, point to Security, and
then choose Air Protocol Security. The Security Configuration dialog box
appears.
Figure 23-11: Security Configuration dialog box
2. In the Private Key field, enter the private key value (e.g. 170).
3. Click Apply.

23.4.5. Task 4: Reset the SPR

Once you have defined the SPR's private key, you need to reset the SPR.
To reset the SPR:
1. In the SPR Zoom window, from the Configuration menu, choose Reset.
2. Click Yes to confirm reset.

23.5. Adding IP Filters

You can assign IP filters according to protocol type (i.e. TCP and UDP), and source
and destination IP addresses. You can define a range of addresses and ports to
permit and deny traffic for passing through the ASWipLL system. A BSR can use
up to 28 different filtering rules.
Notes:
1) IP filtering is relevant only when the ASWipLL system is configured for IP
routing (i.e. not applicable for transparent bridging).
2) IP filtering cannot operate with PPPoE bridging.

The flowchart below displays a summary of tasks for defining IP filtering.
Figure 23-13: Flowchart for defining IP filtering in the ASWipLL system

23.5.2. Task 1: Enable IP Filtering

The first task you need to perform is to enable IP filtering by selecting the IP Filters
Active option, using WipManage.
To enable IP filtering:
1. In the WipManage main window, double-click the BSR icon. The BSR
Zoom window appears.
2. From the Configuration menu, point to Network, and then choose PPPoE / IP
Filtering. The PPPoE / IP Filters dialog box appears.
Figure 23-14: PPPoE / IP Filtering dialog box
3. Select the IP Filters Active option as displayed in the figure above, and then
click OK.


After you have selected the IP Filters Active option, you need to reset the BSR for
the mode to take effect.
To reset the BSR:


23.5.4. Task 3: Verify BSR in IP Filtering Mode

After you have reset the BSR, it is recommended that you check that the new
To check that the BSR is in IP filtering mode:
In the BSR Zoom window, from the Configuration menu, point to Network, and
then choose PPPoE/IP Filtering.
The PPPoE / IP Filters dialog box appears, as displayed below.
Figure 23-17: Current Device Mode field displaying "IP Filters Active"

23.5.5. Task 4: Add BSR IP Filtering Rules

Now that you have configured the BSR for IP filtering, you need to define the IP
filtering rules (or parameters).
The following procedure describes how to add an IP filter for blocking FTP packets
from any source and to any destination, through port 21.
To add an IP filter for blocking FTP packets:
then choose IP Filtering. The IP Filtering dialog box appears.
Figure 23-18: IP Filtering dialog box

2. Click Add. The IP Filtering Table – Add dialog box appears.
Figure 23-19: IP Filtering Table Add dialog box
3. Add the IP filter as shown in the figure above:

a. From the Protocol Type drop-down list, select TCP (i.e. for FTP).
b. From the Port Number drop-down list, select Specific, and then in the field
that appears, enter the port number 21 (i.e. port for FTP).

c. Apply IP filter to all sources and all destinations by performing the

following:
− In the Source Address field, enter the source IP address to which you
want to apply the IP filter (e.g. 255.255.255.255, i.e. all sources).
− In the Source Mask field, enter the source IP subnet mask address to
which you want to apply the IP filter (e.g. 255.255.255.255, i.e. all
sources).
− In the Destination Address field, enter the destination IP address to
which you want to apply the IP filter (e.g. 255.255.255.255, i.e. all
destinations).
− In the Destination Mask field, enter the destination IP subnet mask
address to which you want to apply the IP filter (e.g. 255.255.255.255,
i.e. all destinations).
Note: Source and destination refers to packets that are received by the BSR
(from WAN side or SPR side) and sent by the BSR (to WAN side or SPR side),
respectively.
d. Select the Deny option to discard all packets defined in the above steps.

4. Click Apply.
The IP filter appears in the IP Filtering table, as displayed below.
Figure 23-20: Added IP filter appearing in the IP Filtering table blocking FTP traffic

23.5.6. Task 5: Enable IP Filtering for SPR

Once you have defined IP filtering for the BSR, you need to select an SPR
(associated with this BSR), to enable IP filtering for the SPR.
To enable IP filtering for SPR:
1. In the BSR Zoom window, double-click the SPR for which you want to apply IP
filtering.
The SPR Zoom window appears.
2. From the Configuration menu, point to Network, and then choose PPPoE / IP.
The PPPoE/IP dialog box appears.
Figure 23-21: PPPoE/IP dialog box
3. Select the IP Filters Active option, and then click OK.

23.5.7. Task 6: Reset the SPR

Once you have enabled IP filtering for the SPR, you need to reset the SPR to apply
the IP Filters settings performed in the previous section.
To reset the SPR:
1. In the SPR Zoom window, from the Configuration menu, choose Reset.
23.5.8. Task 7: Add SPR IP Filter Rule

Now that you have configured the SPR for IP filtering, you need to define the IP
filtering rule.
To add IP filter to block FTP traffic:
1. In the SPR Zoom window, from the Configuration menu, point to Network, and
then choose IP Filtering. The IP Filtering dialog box appears.
2. Click Add. The IP Filtering Table – Add dialog box appears.
3. See Section 23.5.5, "Task 4: Add BSR IP Filtering " for defining the SPR IP
filtering parameters.

23.6. Defining IntraComm Gateways

WipManage allows you to assign IP filtering for communication among SPRs using
third-party external routers. The figure below illustrates gateways per SPR (referred
to in WipManage as IntraComm Gateway).
Figure 23-23: Example of IntraComm Gateway feature (gateways per SPR)
In this setup, the BSR relays traffic to the appropriate gateway according to the SPR
index number, regardless of the VLAN to which the traffic belongs. For example, in
the figure above, SPR #1 is routed to Gateway #1, and SPR #2 is routed to
Gateway #2, despite the fact that both SPR #1 and SPR #2 belong to the same
VLAN (i.e. VLAN 60).

Note: If the IntraComm gateway (i.e. external router) is in a different subnet

address to the BSR, you need to define this subnet interface for the BSR. See
Chapter 13, "Defining Virtual Ports".

The flowchart in the figure below displays a summary of tasks for assigning IP
filtering among SPRs using third-party external routers (i.e. IntraComm gateways).
Figure 23-24: Flowchart for assigning IP filtering among SPRs using third-party
external routers (i.e. IntraComm gateways

23.6.2. Task 1: Select IntraComm Gateway Option

The first task you need to perform is to select the IntraComm Gateway Mode
option, using WipManage.
To select the IntraComm Gateway Mode option:
1. In the WipManage main window, double-click the BSR icon. The BSR
Zoom window appears.
2. From the Configuration menu, point to Network, and then choose Multiple
Gateway Mode. The IntraComm dialog box appears.
Figure 23-25: IntraComm dialog box
3. Select the IntraComm Gateway Mode option.

4. Click Apply, and then click OK.


Once you have selected the IntraComm Gateway Mode option, you need to reset
the BSR to apply the setting.
To reset the BSR:

23.6.4. Task 3: Define Gateway IP Address per SPR

Now that IntraComm Gateway mode is configured for the BSR, you need to define
the gateway’s IP address for each SPR.
To define the gateway’s IP address per SPR:
1. In the BSR Zoom window, right-click the SPR to which you want to apply
IntraComm Gateway filtering, and then from the shortcut menu, choose Edit.
The Permitted SPRs – Edit dialog box appears.
Figure 23-27: Permitted SPRs – Edit dialog box
2. In the Intra Comm. GW field, enter the IP address of the third-party external
router/gateway that the SPR uses to communicate with other SPRs.
3. Click OK.

24
Defining Quality of Service
This chapter describes procedures for defining Quality of Service (QoS) for the
ASWipLL system.
Overview
Defining QoS for Data
Defining QoS for VoIP
Summary of Tasks
Task 1: Define QoS for IP Addresses of SIP Server and Softswitch
Task 2: Configure DiffServ Tagging for RGW
Task 3: Map DiffServ Tags to ASWipLL Prioritization at BSR and SPR

D e f i n i n g Q u a l i t y o f S e r vi c e Commissioning Manual
24.1. Overview
ASWipLL provides end-to-end Quality of Service (QoS) for the ASWipLL network.
This proprietary QoS relates to internal traffic between the BSR and SPR. Once
traffic exits to the WAN, the original QoS settings of the packet are used (except for
QoS for IP addresses).
Configuring QoS for SPRs and BSRs are similar. The only difference is that QoS for
BSR is pertinent to downlinks (i.e. traffic from BSR to SPRs associated with the
BSR); QoS for SPR is pertinent to uplinks (i.e. traffic from the SPR to the BSR).
Thus, in most cases, you need to configure QoS for both the BSR and SPR. A
scenario where QoS is configured only at one end is for trivial file transfer protocol
(TFTP) traffic, which is configured only at the BSR (i.e. downlink traffic from BSR
to SPR.) This allows you to ensure high priority for traffic (i.e. TFTP traffic)
concerned with downloading software versions to ASWipLL devices.
The figure below illustrates an example of QoS settings between a BSR and an SPR,
where VoIP traffic is assigned highest priority.
Figure 24-1: ASWipLL internal QoS
Note: When setting QoS for a specific IP address, QoS for BSR is according
to source (i.e. from WAN); QoS for SPR is according to destination (i.e. to
WAN).

Commissioning Manual D e f i n i n g Q u a l i t y o f S e r vi c e
ASWipLL allows you to apply QoS to the following traffic parameters:

Network type:
IP: all IP packets
PPPoE Discovery: broadcast packets concerned with PPPoE
PPPoE Session: PPPoE data packets
Others: all packets except the above
Transport protocols:
TCP
UDP
ICMP
Applications: based on transport protocol (e.g. TCP) and port number. For
example, FTP (Transport = TCP; port = 21).
IP addresses: packets originating from or destined to specific IP addresses.
802.1p and DiffServ/TOS bits: ASWipLL allows you to cross-map (i.e.
customize) packets with 802.1p and DiffServ/TOS prioritization levels and
assign them to ASWipLL's internal QoS priority levels. For example, you can
define that for DiffServ/TOS priority level 1, ASWipLL will assign its own
priority level of 2.

ASWipLL assigns QoS to this traffic based on the following two parameters:
Class (traffic priority): Range 0 through 6. Class determines the relevant
importance of a packet: the higher the class, the higher the importance. Highest
class is typically assigned to VoIP and video packets.
Stamp: Stamp refers to the Time-To-Live (TTL) assigned to the packet. The
lower the TTL, the higher the priority. After expiration, the packet is discarded.
When a packet arrives from the Ethernet network the system recognizes the type
of packet and assigns it with an ASWipLL Time-To-Live (TTL) value. TTL
determines which packets go first, where packets share the same priority. Higher
priority packets always go first regardless of the TTL of lower priority packets.
The stamp range is from 3 through 4,000 milliseconds.
The following sections provide examples for QoS configuration of the BSR. These
configurations are similar for the SPR.

24.2. Defining QoS for Data

This section describes the procedure for defining QoS for TFTP applications. This
application is based on the UDP transport protocol and uses port 69. Assigning a
higher QoS priority to TFTP packets over standard data packets is important for
remote download of software files by TFTP to ASWipLL devices. This provides
TFTP packets a reliable and unobstructed flow to ASWipLL devices.
For TFTP QoS, you only need to configure the QoS at the BSR, i.e. QoS for TFTP
traffic toward the SPR. For most applications, such as FTP, you need to configure
the identical QoS settings for both the BSR and SPR (i.e. downlink and uplink
traffic).
To define QoS for TFTP applications (at BSR):
1. In the BSR Zoom window, from the Configuration menu, choose QoS, as
shown below.
Figure 24-2: Choosing the QoS command from the Configuration menu

The following dialog box appears:
Figure 24-3: Quality of Service window
2. Click the Applications tab.

Left-pointing
arrow
TFTP
application
Figure 24-4: Quality of Service window – Applications tab
3. From the list of applications located in the right pane, select the TFTP
application (i.e. defined as UDP transport protocol using port 69), as displayed in
the figure above.
4. Click the left pointing arrow button to add the TFTP application to the QoS
Application tab.
The QoS Applications Policy – Add dialog box appears with the Transport
Protocol and Port fields displaying the TFTP definitions, as shown below.
Figure 24-5: QoS Applications Policy Add dialog box

5. Define the TFTP application's QoS settings by performing the following:

a. In the Stamp field, enter a time stamp value (e.g. 1,000 ms).
b. From the Class drop-down list, select a priority level (e.g. 2).
6. Click OK.
TFTP
application
added to
BSR's QoS
configuration
Figure 24-6: QoS defined for TFTP applications

24.3. Defining QoS for VoIP

In a typical VoIP setup based on H.323 protocol, the BSR connects to a Gatekeeper
(GK) and a Gateway (GW). The GK handles the voice signaling while the GW
handles the PSTN voice data. In addition, the SPR connects to a Residential
Gateway (RGW) through the SDA. The RGW handles the voice signaling and data
from the subscriber’s telephone to the BSR.
You can configure QoS for VoIP based on the following parameters:
DiffServ/TOS:
WipManage provides you with a QoS feature for converting TOS to an
internally customized priority class. You can assign DiffServ/TOS to the voice
signaling and voice data (i.e. RTP) for VoIP access products: Gatekeeper (GK),
Gateway (GW), and Residential Gateway (RGW). The first three bits in the IP
header is allocated for TOS.
This feature provides QoS for SPRs communicating with each other.
WipManage allows you to tag voice signaling and data packets.
IP Addresses:
You can assign different QoS to voice signaling and voice data for residential
gateways that do not support DiffServ tagging. Typically, voice signaling is
assigned a higher priority level than voice data. The priority is defined according
to source IP address at the BSR, i.e. IP address of the GW and GK; and
according to destination IP address at the SPR (i.e. IP address of the GW and
GK). For VoIP QoS based on IP addresses, you need to add the IP addresses of
the GK and GW for both the BSR and the SPR. The IP addresses of the GK and
GW are identical at the BSR and SPR side.
802.1p:
WipManage allows you to convert standard QoS priority levels into an
ASWipLL customized priority class. This ASWipLL priority is based on
VLANs. Therefore, the RGW at the subscriber’s premises must support VLAN
and perform 802.1p tagging. The incoming VLAN tagged packet has a field
called User Priority containing 3 bits that indicate priority level

Note: When setting priority for a specific IP address, QoS for BSR is
according to source; QoS for SPR is according to destination.

This section describes the procedures for configuring QoS for VoIP based on
DiffServ/TOS tagging to ensure the ASWipLL system assigns the highest QoS for
VoIP packets. This QoS configuration is based on the following network scenario:
SIP server (e.g. 10.0.0.1) and softswitch (e.g. 10.0.0.2) is located behind BSR
Residential gateway (located at the subscriber's site behind the SPR), configured
with a DiffServ tag for voice data (i.e. RTP) and voice signaling
The procedure for configuring QoS for VoIP is based on the configuration setup
Figure 24-7: Configuration example for defining QoS for VoIP based on DiffServ/TOS
tagging

Figure 24-8: Flowchart for defining QoS for VoIP based on DiffServ/TOS tagging
24.3.2. Task 1: Define QoS for IP Addresses of SIP

Server and Softswitch
The VoIP packets in our example scenario either originate from or are destined to
two IP addresses, namely, the SIP server (for signaling packets) and the softswitch
(for voice data destined for and originating from the PSTN). Thus, to configure QoS
for VoIP for these devices, you need to assign these IP addresses QoS settings (i.e.
stamp and class).
You must configure these QoS settings at both the BSR and SPR to ensure QoS in
both the downlink and uplink. This procedure is similar for the BSR and SPR. The
main difference is that QoS for the BSR refers to the source IP address (i.e. traffic
from SPR) while the QoS for the SPR refers to the destination IP address (i.e. traffic
destined to BSR). Therefore, the procedure below describes the QoS setting for the
SPR. Simply perform the same at the BSR.

To configure QoS (e.g. for SPR) for SIP server and softswitch IP addresses:
1. In the SPR Zoom window, from the Configuration menu, choose QoS. The
Quality of Service dialog box appears.
Figure 24-9: Choosing the QoS command
2. Select the IP Addresses tab.

3. Click Add.
Figure 24-10: Adding QoS for IP address 10.0.0.1 (i.e. SIP server)

4. Configure QoS for the SIP server (i.e. signaling packets) by performing the
following:
a. In the IP address, enter the SIP server's IP address (e.g. 10.0.0.1).
b. In the Mask field, enter the SIP server's mask address to use this specific IP
address (e.g. 255.255.255.255).
c. In the Stamp field, enter 250.
d. In the Class field, select (5) Signaling.
5. Click OK.
6. Repeat steps 1 through 7 for configuring QoS for the softswitch's IP address (i.e.
10.0.0.2), but enter a stamp of 200 ms and class of (4) Media, as displayed
below.
Figure 24-11: Adding QoS for IP address 10.0.0.2 (i.e. softswitch)

The figure below displays the QoS configured for the SIP server (i.e. 10.0.0.1) for
signaling packets and softswitch (i.e. 10.0.0.2) for voice data packets at the SPR.
QoS for SIP

server and
softswitch IP
address
Figure 24-12: QoS defined for SIP server and softswitch IP addresses
Note: Configure the same QoS configurations for the BSR (i.e. in the BSR
Zoom window: Configuration menu > QoS command > IP Addresses tab).
24.3.3. Task 2: Configure DiffServ Tagging for RGW

Configure your third-party residential gateway (RGW) so that it assigns a different
DiffServ tag for voice data and for signaling.

24.3.4. Task 3: Map DiffServ Tags to ASWipLL

Prioritization Scheme
You need to enable ASWipLL to recognize and assign appropriate QoS to the
DiffServ tagging that you configured for the RGW for voice data and for voice
signaling. You need to configure this for both the BSR and the SPR, thereby,
ensuring QoS in both the downlink and uplink.
This procedure is similar for the BSR and SPR, except performed in the BSR Zoom
window and SPR Zoom window respectively. Therefore, the procedure below only
describes this QoS setting for the SPR. Perform the same QoS settings for the BSR.
To enable ASWipLL QoS (e.g. SPR) to support DiffServ tagging by RGW:
1. In the SPR Zoom window, from the Configuration menu, choose QoS.
2. Select the DiffServ / TOS tab.
3. Select the Enable/Disable Priority check box, and then perform the following:
a. For priority 4, assign class (4) Media and 200 ms stamp.
b. For priority 5, assign class (5) Signaling and 250 ms stamp.

QoS for DiffServ tagging for voice signaling

QoS for DiffServ tagging for voice data
Figure 24-13: Mapping of DiffServ tagging to ASWipLL prioritization
4. Click Set.
Note: Configure the same QoS configurations for the BSR (i.e. in the BSR
Zoom window: Configuration menu > QoS command > DiffServ / TOS tab).

25
Managing Traps
This chapter describes the procedures for working with traps in WipManage, and
Overview
Defining Management Stations
Enabling Trap Display in WipManage
Viewing the Traps Pane
Viewing the Alarms Table
Enabling Pop-up Notifications and Execution of Batch Files on Trap Receipt
Enabling/Disabling Receipt of Specific Traps
25.1. Overview
As a Simple Network Management Protocol (SNMP)-based application,
WipManage can receive traps generated internally by WipManage and generated by
ASWipLL devices. Each ASWipLL device contains an SNMP agent (residing on the
device) that collects and stores the device's data (e.g. configuration parameter
settings) in a management database type called Management Information Base
(MIBs). This information can be retrieved or modified by WipManage using SNMP
commands (i.e. read and write). The SNMP trap command allows the device to
automatically report events by sending traps to WipManage.

Managing Traps Commissioning Manual
To allow WipManage to receive traps, you need to perform the following:

Define management stations (e.g. WipManage) for receiving device-generated
traps
Enable WipManage to receive and display traps
Note: For internally generated traps (i.e. generated by WipManage), no

management station needs to be defined
25.2. Defining Management Stations

Up to five management stations can be defined for receiving traps. These stations
need to be defined per ASWipLL device type (i.e. BSR, BSDU, and SPR/IDR).
Management stations are defined by IP address.
You can also define the trap SNMP community string per device that you want the
management station to receive. This is relevant only for third-party SNMP external
management stations (e.g. HP OpenView); WipManage management stations
receive traps regardless of community string. (Community strings are defined in the
Agent Security dialog box: Configuration menu > Security > Agent Security).

Commissioning Manual Managing Traps
To define a management station for receiving traps (e.g. for BSR):

1. In the BSR Zoom window, from the Configuration menu, choose Managers
Table. The Managers Table dialog box appears, as displayed below.
Figure 25-1: Managers Table dialog box
2. Click Add. The Manager Entry - Add dialog box appears, as displayed below.
Figure 25-2: Adding a manager
3. In the IP Address field, enter the IP address of the WipManage interface

configured for the computer on which WipManage is running.
4. Click OK.

25.3. Enabling Trap Display in WipManage

WipManage can display up to the last 1,000 received traps. These traps can be
displayed in the Traps pane of the WipManage main window, or in the Alarms table
located in all the configuration windows pertaining to each device (i.e. BSR Zoom,
SPR Zoom, and BSDU Zoom windows). The Alarms table displays only traps that
are saved in the database, while the traps pane displays saved and unsaved traps.
To enable WipManage to display traps:
1. In the WipManage main window, from the Tools menu, choose Environment
Settings.
2. Click the Trap Settings tab.
For viewing traps in

Alarms tables (i.e.
saving traps to
database)
For viewing traps in

Traps pane
Figure 25-3: Enabling trap display in WipManage

3. For viewing traps in the Alarms tables, select the Add Traps to DB check box
(this also saves traps to the database).
4. For viewing traps in the Traps pane, select the Add Traps to List check box.
5. Click OK.
Notes:
1) Traps are displayed with a specific severity level: Normal , Warning ,
Major , and Critical .
2) To receive traps, ensure the Stop Listening button is displayed
(default) on the WipManage main window's toolbar. If the Start Listening
button is displayed, click this button.

25.4. Showing the Traps Pane

The Traps pane displays traps that are saved and not saved in the database.
To view the Traps pane:
In the WipManage main window, from the View menu, choose Traps Pane.
Traps pane
Figure 25-4: Traps pane displaying traps
The Traps pane displays traps in the following format:

Traps that are saved in the DB appear with an index number, e.g. "2"
Traps not saved in the DB appear with a number sign (#) alongside the index
number, e.g. "#2"
Traps from a previous WipManage session and not saved in the DB appear
with "Old" alongside the index number, e.g. "Old 2"

25.5. Viewing the Alarms Table

Traps saved in the database (DB) can be viewed in the Alarms table, which is
located in all the device-specific windows (i.e. BSR Zoom, SPR Zoom, and BSDU
Zoom windows). The Alarms table also allows you to filter trap display according to
device.
To view traps saved in the DB in device-specific windows (e.g. BSR Zoom
window):
In the BSR Zoom window, from the Alarms menu, choose Alarms Log.
The Alarms Table window appears, as displayed below.
Figure 25-5: Alarms table displaying traps saved in DB

25.6. Enabling Pop-up Notifications and

Execution of Batch Files on Trap Receipt
WipManage allows you to enable displays of pop-up windows to notify you of
receipt of specific traps from specific ASWipLL devices. In addition, WipManage
allows you to select any batch or executable file (i.e. *.bat or *.exe files) that
automatically runs when a specific trap is received. This is useful, for example, if
you have a batch file that sounds an alarm on your PC when a trap is received.
To enable pop-up notifications and/or file executions on trap receipt:
1. In the WipManage main window, from the Tool menu, choose Alarm
Management. The Alarm Management Configuration dialog box appears.
Figure 25-6: Alarm Management Configuration dialog box
2. In the IP List field corresponding to the desired trap name, enter the IP address
of the ASWipLL device, and then press the <Enter> key.
3. To enable a pop-up window to notify that the trap was generated by the
ASWipLL device, select the PopUp check box that corresponds to the trap
name.

4. To enable an execution of a file (*.bat or *.exe file) at the generation of the trap,
select the Enable check box corresponding to the trap name, and then browse to
the required file by clicking the Browse button.
5. Click OK.
To delete an IP address or a file, simply right-click the lower dividing line of the row
in which the IP address or file is entered, and then from the shortcut menu, choose
Delete.

25.7. Enabling/Disabling Receipt of Specific

Traps
WipManage allows you to enable or disable WipManage to receive certain traps per
device type (i.e. BSR, SPR, and BSDU). The configuration of these traps is
performed in the device-specific windows (i.e. BSR Zoom, SPR Zoom, and BSDU
Zoom windows).
To enable/disable WipManage receiving specific traps (e.g. from BSR):
1. In the BSR Zoom window, from the Alarms menu, choose Config Traps. The
Configure Traps dialog box appears, as displayed in Figure 25-7.
Figure 25-7: Configuring traps

2. To ensure that the received signals are from a valid community, select the
Authentication Trap check box. Any attempt of an unauthorized user to access
the BSR, a trap will be sent indicating this.
3. To receive E2 traps, select the E2 Trap check box. The E2 traps are generated
when the database memory is corrupted. The RF has a separate memory, and if
this memory cannot be accessed, an RF E2 alarm is generated approximately
every 30 seconds.
4. To acknowledge that synchronization of BSR was lost and prevent its
continuous generation, click the Acknowledge Sync Lost Trap button.
5. To receive and define temperature traps from the BSR, perform the following:
a. Select the Temperature Trap check box
b. On the High Temperature Threshold slide ruler, move the ruler to the
temperature above which you want a temperature trap to be generated.
c. On the Low Temperature Threshold slide ruler, move the ruler to the
temperature below which you want a temperature trap to be generated.
6. To receive traps indicating that SPR/IDR devices have been associated
(connected) with the BSR, select the Association Connect Trap check box.
7. To receive traps indicating that an SPR/IDR has connected to the BSR through
AutoConnect, select the AutoConnect Trap from BSR check box.

8. To receive traps indicating that the AutoDisconnect interval of an SPR index of a

BSR has ended (i.e. SPR index available for receiving an SPR through
AutoConnect), select the AutoDisconnect Trap from BSR check box.
9. To receive traps indicating that the MAC table has reached its maximum of
entries (i.e. 128 MAC addresses), select the MAC Table Overflow Trap check
box.
Notes:
1) The Acknowledge RF E2 Trap button is not applicable. Latest ASWipLL
releases perform this automatically.
2) Some alarm types are not configurable (for example, Cold Start).
3) The AutoConnect Trap from BSR and the AutoDisconnect Trap from
BSR check boxes are available only if the AutoConnect feature is licensed.

26
Upgrading ASWipLL
Database
This chapter describes the procedures for upgrading the ASWipLL database, and
Overview
Summary of Tasks
Task 1: Install WipLL DB Upgrade
Task 2: Start WipLL DB Upgrade
Task 3: Upgrade the ASWipLL Database
Task 4: Compact the ASWipLL Database
26.1. Overview
The ASWipLL system provides a database that contains data of the entire ASWipLL
system. Sometimes a new ASWipLL release employs a new version of the
ASWipLL database. Airspan's WipLL DB Upgrade utility tool, generally supplied
on a CD with your ASWipLL system, provides you with the means for upgrading
the ASWipLL database.
WipLL DB Upgrade allows you to perform the following:
Upgrade the database version
Compact the database

U p g r a d i n g AS W i p L L D a t a b a s e Commissioning Manual

The flowchart in the figure below displays a summary of tasks for upgrading the
ASWipLL database.
Figure 26-1: Flowchart for upgrading the ASWipLL database

Commissioning Manual U p g r a d i n g AS W i p L L D a t a b a s e
26.3. Task 1: Install WipLL DB Upgrade

WipLL DB Upgrade is supplied on a CD. The CD's installation wizard guides you
through the installation steps. You need to install WipLL DB Upgrade on the same
PC on which the ASWipLL database resides.
To install WipLL DB Upgrade:
1. Insert the WipLL DB Upgrade CD in your CD-ROM drive.
2. On the Windows taskbar, click Start, and then choose Run.
3. Type D:\ DBUPGRADE.EXE (where D is the letter of your CD-ROM drive
letter)
4. Click OK
The Welcome window appears, as displayed below.
Figure 26-2: Welcome window

5. Click Next.
Figure 26-3: Choose Destination Location window
6. To accept the default destination folder for installing WipLL DB Upgrade, click
Next, or to install WipLL DB Upgrade to a different folder, click Browse, and
then select the desired folder.

Figure 26-4: Select Program Manager Group window
7. Accept the default Program Manager group ("WipLL"), and then click Next.

Figure 26-5: Start Installation window

The Installing window appears, displaying the installation progress.
Figure 26-6: Installing window
When the WipLL DB Upgrade has been copied to the selected folder, the
Desktop Shortcut window appears.

Figure 26-7: Desktop Shortcut window
9. Select the Add Shortcut to Desktop check box to add the WipLL DB Upgrade
shortcut icon to your desktop, and then click Next.

Figure 26-8: Installation Complete window
10. To close the installation wizard, click Finish.

The WipLL DB Upgrade shortcut icon appears on the desktop:
Figure 26-9: WipLL DB Upgrade shortcut icon

26.4. Task 2: Start WipLL DB Upgrade

Once you have installed WipLL DB Upgrade on your PC, you can start the
application.
To start WipLL DB Upgrade:
From the Start menu, point to Programs, point to Airspan, and then choose
WipLL DB Upgrade,
-Or-
On your desktop, double-click the WipLL DB Upgrade shortcut icon.
The WipLL DB Upgrade starts and the WipLL DB Upgrade main window
Figure 26-10: WipLL DB Upgrade main window

26.5. Task 3: Upgrade the ASWipLL Database

The following describes the procedure for upgrading the ASWipLL database,
wiplldb.mdb.
To upgrade an ASWipLL database version:
1. In the WipLL DB Upgrade main window, from the Tools menu, choose
Upgrade Database. The WipLL DB Upgrade dialog box appears, as displayed
below.
Figure 26-11: WipLL DB Upgrade dialog box
2. In the Current Database field, select the current database that you want to
upgrade, by clicking the Browse button, and then selecting the file.
The Open dialog box appears, as displayed in Figure 26-12.

Figure 26-12: Selecting a database
If the selected database file (with the *.mdb file extension), does not conform to
ASWipLL standards for upgrading a database, an error message box appears, as
displayed in Figure 26-13.
Figure 26-13: Incorrect database or version
3. In the Upgrade To drop-down list, select the new database version number to
which you want to upgrade the old version.
4. In the New Database Location field, select the new database for which you
want to upgrade the ASWipLL database, by clicking the Browse button, and
then selecting the file.

Note: If you use the Browse button, all you need to enter is the file name. By
default, the upgraded database will be generated in the same folder as the
original.
Figure 26-14: Naming the new database
Figure 26-15: Selected database

5. Click Next.
The upgrade details that you selected above, are displayed in the following
window:
Figure 26-16: Upgrade details confirmation
6. Click Finish.
When WipLL DB Upgrade successfully completes the upgrading process, the
Congratulations message box appears, as displayed below.
Figure 26-17: Congratulations message box

26.6. Task 4: Compact the ASWipLL Database

After you have upgraded the ASWipLL database, WipLL DB Upgrade allows you to
free disk space on your PC by compacting your database file. This frees unused disk
space by removing references no longer in use.
1. In the WipLL DB Upgrade main window, from the Upgrade Tools menu, choose
Compact Database.
Figure 26-18: Compacting a database
2. In the Path field, type the path and file name of the database that you want to
compact, or click the Browse button, and then select the database file from the
desired folder.
3. Click Compact.


27
Upgrading ASWipLL Devices
This chapter describes the procedures for upgrading ASWipLL devices, and includes
the following sections:
Overview
Remote Upgrade using WipManage
Upgrading Multiple SPRs
Upgrading a Single BSR
Local Serial Upgrade using WipConfig
Troubleshooting

U p g r a d i n g AS W i p L L D e vi c e s Commissioning Manual
27.1. Overview
You can upgrade ASWipLL devices by downloading a later software (SW) version
file, using WipConfig or WipManage. The table below compares the WipConfig and
WipManage tools regarding upgrade capabilities.
Table 27-1: Comparison of SW tools for upgrading ASWipLL devices

Program Communication mode Number of devices
WipConfig Serial and Network (i.e. local and remote) Single device
WipManage Network (i.e. remote upgrade via TFTP Single and multiple
server) devices
WipConfig can perform local upgrades when connected to an ASWipLL device

through an RS-232 serial cable. For remote upgrades, WipManage and WipConfig
can communicate with the device from anywhere with IP connectivity to the
ASWipLL device. With regards to WipManage, the SW download is performed
using a Trivial File Transfer Protocol (TFTP) server on which the SW file is located.
ASWipLL devices contain two banks for storing the SW version files: a standby
bank and an active bank. The active bank contains the currently active SW version
file while the standby bank contains an inactive previous SW version file.
When you upgrade an ASWipLL device, the SW version file is first downloaded to
the device's standby SW bank. To enable the device to use the file, you need to
transfer the file to the device's active SW bank. In so doing, the previously active
SW version file is transferred back into the standby bank and becomes inactive.

Commissioning Manual U p g r a d i n g AS W i p L L D e vi c e s
The figure below illustrates the upgrade process (using a TFTP server).
Figure 27-1: Remote downloading of SW version files
You can upgrade devices by up to two earlier or later software versions than the
current version residing on the ASWipLL device. The table below lists examples of
permissible upgrades from one ASWipLL release to another (starting from the
earliest release 2.6 to the latest release 4.4). The ASWipLL release depicts the SW
version pertaining to the specific release.
Table 27-2: Permissible download paths from one ASWipLL release to another
Release Release Release Release Release
2.6 3.0B 4.1 4.2B 4.4
3.0A 3.0B 4.1 4.2B 4.4
3.0B 4.1 4.2B 4.4
4.0 4.1 4.2B 4.4
4.1 4.2B 4.4
4.2A 4.4
4.2B 4.4
4.2C 4.4

The table below lists the SW version file names for the ASWipLL devices that are
downloaded to the relevant ASWipLL device.
Table 27-3: SW version file names per ASWipLL device

ASWipLL device SW version file
WipConfig WipManage
(HEX file format) (BIN file format)
BSR BSR.hex BSR.bin
PPR PPR.hex PPR.bin
SPR SPR.hex SPR.bin
IDR IDR.hex IDR.bin
BSDU BSDU.hex BSDU.bin
Notes:
1) You can download up to two earlier or later software versions than the
current version. For example, if the current BSR’s software version is 2.58.0.4
ASWipLL Release 4.2B).
2) Always upgrade ASWipLL devices farthest away from the PC running the
TFTP server. In other words, upgrade first SPRs, then BSRs, and then BSDUs.
This ensures that if a failure occurs with an SPR, the BSR remains in link with
the other SPRs.
3) The ASWipLL configuration tools (i.e. WipConfig and WipManage) allow you
to simply select the path to the folder in which SW version files are located,
instead of selecting the specific file.

27.2. Remote Upgrade using WipManage

You can perform SW version upgrade with WipManage (and a TFTP server) from
any remote location with IP connectivity to the ASWipLL devices (i.e. BSR, BSDU,
and SPR/SDA). The remote upgrade for SPR/SDA is via the BSR, which provides
the wireless link with the SPR/SDA.
Before you can upgrade the SW version using WipManage, you need to ensure that
a TFTP server is running, and that the TFTP’s outbound path to the folder in which
the SW version files are located is defined.
The table below describes the commands for downloading SW version files to single
and multiple ASWipLL devices.
Table 27-4: Location of command for upgrading single or multiple devices

Device Upgrade Window Menu Command
BSR Single BSR Zoom Configuration Download
Multiple WipManage main MultiDevices BSRs > Download Manager
BSDU Single BSDU Zoom Configuration Download
Multiple WipManage main MultiDevices BSDUs > Download Manager
SPR Single SPR Zoom Configuration Download
Multiple BSR Zoom MultiDevices Download Manager
The following subsections provide examples of how to upgrade a single BSR and
multiple SPRs. The procedures for upgrading single and multiple devices are similar
between the devices, the only difference being the location of the command for
performing upgrades:

27.2.1. Upgrading Multiple SPRs
Using WipManage, you can upgrade multiple SPR devices. This is performed in the
BSR Zoom window. The following procedure upgrades the SPRs’ SW version from
2.96.000.001 to 2.97.000.002 using the PC on which WipManage is running as the
TFTP sever (i.e. 10.0.0.2).
To upgrade multiple active SPRs:
1. Ensure that the TFTP server is running and the following is configured:
TFTP’s Outbound path to the folder in which the software version file (i.e.
SW version 2.97.000.002) is located
TFTP allows maximum simultaneous clients
2. In the BSR Zoom window, from the MultiDevices menu, choose Download
Manager, as displayed below.
Figure 27-2: Choosing the Download Manager command

The Download Manager dialog box appears.
Figure 27-3: Download Manager dialog box
3. In the TFTP Server IP field, enter the TFTP server's IP address (e.g. 10.0.0.2).
4. Select the SPRs that you want to upgrade, by clicking the check boxes
corresponding to the SPRs.

5. Click Download.
A blue progress bar indicates the progress of the downloading process for each
SPR, as displayed below.
Progress bar
Figure 27-4: Downloading SW version file 2.78.000.005 to multiple SPRs

When the download is complete, the Download Manager dialog box displays the
following, as displayed below:
Progress bar: "Download Success"
Standby Bank field: "2.97.000.002"
Downloaded
SW file in
Standby bank
"Download
Success"
message
Figure 27-5: Download complete (SW version file in Standby bank)

6. Click Swap Banks to transfer the downloaded file from the SPRs’ Standby
software bank to the Active software bank.
The Swap dialog box appears, as displayed below.
Figure 27-6: Swap dialog box
7. Select the Match Data check box, and then click Yes to swap software banks
and reset the SPRs.

The downloaded file is transferred to the Active banks of the SPRs and the
previous version is transferred to the Standby bank. This is indicated in the
Download Manager dialog box by the display of "Swap!" alongside the Active
bank, as displayed in Figure 27-7.
Downloaded
file transferred
("swapped")
to Active bank
Figure 27-7: SW version file transferred to Active bank
8. Click Lock Active to ensure that the downloaded SW version file in the Active
bank becomes default, and to prevent the file swapping with the file in the
Standby bank.

The file is locked in the Active bank. The Download Manager dialog box
removes the "Swap!" display, as displayed in Figure 27-8.
Downloaded
file locked in
Active bank
Figure 27-8: SW version file (2.97.000.002) locked in Active bank
9. Click Close, to close the Download Manager dialog box.

10. Continue to upgrade the BSR and BSDU from their respective windows until all
the devices are upgraded.

27.2.2. Upgrading a Single BSR

WipManage allows you to download a software version file to a single BSR or to
multiple BSRs. Upgrading multiple BSRs is similar to upgrading multiple SPRs, but
performed in the WipManage Main window.
Upgrading a single BSR is performed in the BSR Zoom window. The following
procedure upgrades the BSR SW version from 2.96.000.001 to 2.97.000.002 using
the PC on which WipManage is running as the TFTP sever (i.e. 10.0.0.2).
To upgrade a single BSR:
1. Ensure that the TFTP server is running and that its outbound path to the folder in
which the software version file (i.e. for SW version 2.97.000.002) is located is
defined.
2. In the BSR Zoom window, from the Configuration menu, choose Download, as
displayed below.
Figure 27-9: Choosing the Download command

The Download dialog box appears, as displayed below.
Figure 27-10: Download dialog box displaying current active SW version 2.69.000.001
3. In the TFTP Server IP field, enter the TFTP server’s IP address (e.g. 10.0.0.2,
i.e. IP address of PC, on which the TFTP server is running).
4. Click Start Download to begin downloading the new software to the BSR.

A blue progress bar indicates the progress of the downloading process.
Progress bar
Figure 27-11: Downloading SW version file

When the download is complete, the Download dialog box displays the
following, as displayed in Figure 27-12:
Progress bar: "100%"
Download Status field: "Download Success"
Downloaded file
in Standby bank
"Download
Success"
message
Progress bar
displaying 100%
Figure 27-12: Download complete (SW version file in Standby bank)

5. Click Swap Banks to transfer the downloaded file from the SPR’s Standby
The Reset dialog box appears, as displayed in Figure 27-13.
Figure 27-13: Reset dialog box
6. Select the Match Data check box, and then click Yes to swap banks and reset
the SPR.

7. Click OK.
After a few seconds, the SW version file is transferred to the Active bank and the
previous SW version file is transferred to the Standby bank, as displayed in
Figure 27-15.
Downloaded file
transferred to
Active bank
Figure 27-15: Download dialog box displaying SW version file in Active bank

Standby bank.
The Status field of the Active bank displays "Locked", as displayed below.
SW file
locked in
Active bank
Figure 27-16: Download dialog box displaying locked Active bank
9. Click Close to complete the software version upgrade.

27.3. Local Serial Upgrade using WipConfig

You can perform local serial software version upgrades by connecting a PC running
WipConfig to the ASWipLL device. Upgrades through a serial configuration are
required when installing the devices and before a BSR-SPR air link is established.
For a detailed explanation on the serial cable setup, refer to the ASWipLL Hardware
Installation Guide.
The following procedure provides an example of upgrading an SPR (10.0.0.20) from
SW version 2.96.000.001 to 2.97.000.002 using WipConfig.
To upgrade a device’s SW version (e.g. SPR):
1. Connect the PC (i.e. serial port) running WipConfig to the ASWipLL device, and
ensure that the ASWipLL device remains connected to the ASWipLL Ethernet
switch/hub (i.e. SDA or BSDU).
2. Start WipConfig, and then connect WipConfig to the ASWipLL device by
selecting Serial, and then clicking the Connect button.

The Configuration pane (e.g. SPR) appears, displaying the device’s basic
configuration settings, as displayed below.
Download
/Upload
button
Figure 27-17: WipConfig connected to SPR through serial mode
3. In the Outlook bar, click the Download/Upload button.

The Download/Upload pane appears, as displayed below.
Figure 27-18: Download/Upload pane with SW version 02.96.000.01 in Active bank
4. In the File field, click the double-arrow button.

The Select Directory dialog box appears, as displayed below.
Figure 27-19: Browsing to the software version file to download
5. Browse to the folder that contains the software version file, and then click OK.
The File field displays the path and SW file name relevant to the device type.

6. Click Download.
WipConfig starts downloading the SW version file to the device’s Standby bank,
and displays the following:
Current Action field: "Software Download"
Current Status field: "Erasing" and then "Download in Progress"
Progress bar: indicates progress of download in percentage
"Software
Download"
message
"Download in
Progress"
message
Progress bar
Figure 27-20: Progress bar indicating download in progress

When the download is complete, the following is displayed:

Current Status field: "Download Finished"
Downloaded
file in Standby
bank
"Download
Finished"
message
Figure 27-21: Download complete and SW version file in Standby bank

7. Click Swap Banks to transfer the downloaded file from the SPR’s Standby
The Ask User confirmation box appears, as displayed in Figure 27-22.
Figure 27-22: Confirming swap (and reset) action from Standby to Active bank
8. Click Yes.
The Information box appears, as displayed below.
Figure 27-23: Information box

9. Click OK.
After a few seconds, the SW version file is transferred from the Standby bank to
the Active bank, and the previous SW version file is transferred to the Standby
bank, as displayed below.
Downloaded
file transferred
to Active bank
Figure 27-24: Downloaded SW version file moved from Standby to Active bank

Standby bank.
The Status field of the Active bank displays "locked", as displayed below.
Downloaded
file locked in
Active bank
Figure 27-25: Downloaded SW version file locked in Active bank

27.4. Troubleshooting
The following table lists troubleshooting that may occur during software downloads:
Table 27-5: Download troubleshooting

Problem Solution
Download fails during • Decrease timeout (default is 30 sec) at the TFTP server and
download (for WipManage) at the SPR
• Increase retry transmissions (default is 5)
Unable to download • WipManage: verify TFTP server is running and that its
outbound path is correctly pointing to the folder in which the
software version is located.
• WipConfig: verify path is correctly pointing to the folder in
which the software version is located


28
Evaluating Link Quality
This chapter explains the methods for evaluating link quality between a BSR and an
SPR.
28.1. Overview
Once you have established your wireless link between a BSR and an SPR/IDR, it is
recommended that you test the quality of the link. This includes measuring the
following parameters:
RSSI (received signal strength indication)
C/I
BER
Throughput (i.e. bandwidth)
Note: Link quality must be tested for a single link, i.e. between a BSR and an
SPR.

E va l u a t i n g L i n k Q u a l i t y Commissioning Manual
28.2. RSSI Levels

It is crucial to measure received signal strength (RSSI) levels at both the BSR and
SPR to ensure that a sufficient wireless link exists for communication. The RSSI
measurements indicate the signal strength between these two devices.
The desired RSSI levels for ensuring a quality link depends on the maximum
transmission rate mode in which the BSR-SPR link is configured.
Table 28-1: Desire RSSI levels per rate

Rate mode Total rate Desired RSSI
4 Mbps 4 Mbps ≥ -78 dBm
1.33 Mbps ≥ -90 dBm
3 Mbps 3 Mbps ≥ -75 dBm
2 Mbps ≥ -83 dBm
1 Mbps ≥ -90 dBm
Notes:
1) Ensure that the RSSI measured at the BSR and at the SPR do not differ
more than 5 dBm. A difference of 5 dBm and greater may be caused by
different radio Tx power levels between BSR and SPR or poor antenna
orientation. Different Tx levels may be due to the BSR controlling SPR's power
(i.e. Power Management mode is set to On).
2) For RSSI measurement at SPR, no traffic generation is required; for RSSI
measurement at BSR, traffic generation is required (see Section 28.5,
"Generating Traffic to Measure Throughput").
Typically, the RSSI is measured at the BSR using WipManage, and the RSSI is
measured at the SPR using WipConfig.

Commissioning Manual E va l u a t i n g L i n k Q u a l i t y
28.2.1. Measuring RSSI at SPR using WipConfig

RSSI measurements at the SPR are typically performed using WipConfig.
To measure RSSI at SPR using WipConfig:
1. Start WipConfig.
2. In the outlook bar, click the WipConfig tab.
3. Click the Statistics button. The Statistic pane appears, as displayed below.
RSSI graph
Figure 28-1: Statistics pane displaying RSSI graph

28.2.2. Measuring RSSI at BSR using WipManage

The RSSI measurements at the BSR are typically performed using WipManage.
Note: For RSSI measurement at the BSR, traffic flow needs to exists between
the BSR and SPR. For generating traffic, see Section 28.5, "Generating Traffic
to Measure Throughput".
To measure RSSI at BSR using WipManage:

1. Open the BSR Zoom window pertaining to the BSR whose RSSI you want to
measure.
2. From the Performance menu, point to Air, point to Cell, and then choose RSSI
per SPR. The RSSI Per SPR dialog box is displayed below.
Figure 28-2: RSSI per SPR graph

28.3. Carrier-to-Interference Ratio

A common performance measure of radio communication systems for unlicensed
bands is the carrier-to-interference ratio (C/I). The C/I is important to determine the
maximum allowed interference level for which the system will still work. C/I is the
ratio of the power in the carrier to the power of the interference signal. CIR is
normally expressed in dB. The C/I is a very useful measure in communications
because it is not sufficient to simply have a strong signal (i.e. RSSI), since a weak
signal in the presence of weak noise may well be as useful as a strong signal in the
presence of strong noise.
To calculate the desired RSSI level, you need to measure the interference level at
the BSR using the Spectrum Analyzer. When the Spectrum Analyzer graph displays
“spikes”, this generally indicates interference. Note that normal “noise” level is
approximately –112 dBm (referred to as thermal noise).
Airspan recommends using frequencies that are approximately 28, 20, and 12 dB
above interference levels to effectively operate in 8-, 4-, and 2-level FSK (4 Mbps/3
Mbps, 2 Mbps, and 1.33 Mbps/1 Mbps), respectively, as listed in the table below.
Table 28-2: ASWipLL minimum C/I requirements per FSK mode

FSK Rate mode C/I
8-level FSK 4 Mbps and 3 Mbps 28 dBm
4-level FSK 2 Mbps 20 dBm
2-level FSK 1.33 Mbps and 1 Mbps 12 dBm
Note: ASWipLL can operate in 2-, 4-, and 8-level FSK with signal strengths greater
than -90, -83, and -75 dBm, respectively.
For example, if the noise level measured by the spectrum analyzer is -70 dBm (see
Figure 28-3), the RSSI level at the SPR should be as follows to ensure a good link
with the BSR:
8-level FSK: RSSI > -42 dBm (28 dBm minus –70 dBm)

28.3.1. Spectrum Analysis using WipConfig

The following subsections provide a brief description on using WipConfig's
Spectrum Analyzer for analyzing the spectrum for identifying noisy frequencies.
Notes:
1) Airspan’s Spectrum Analyzer feature, which plugs into WipConfig, is license-
dependant.
2) Ensure all other ASWipLL devices are powered off, except the device whose
spectrum you are analyzing.
3) Mount the ASWipLL device prior to commencing the spectrum analysis.
4) The spectrum analysis should be performed in continuous mode for at least 20
times. The longer you perform the sweep, the more reliable results are obtained as
interference in the ISM band can change throughout the day or change rapidly
(e.g. in frequency hopping systems).
5) To ensure locating clear frequencies, continually narrow down the sweep
frequency range. For example, first sweep a large frequency range. Once you have
selected a clear area from this initial sweep, run another batch of sweeps
concentrating on these selected frequencies. The fewer frequencies the more
reliable the analysis for capturing bursty, intermittent transmitters (e.g. pagers).
6) When using external antenna, ensure correct Antenna Gain is defined with
consideration to RF cable loss.
7) As interference depends on geographical locations, it is recommended to
perform spectrum analysis at the CPE location when installing the ASWipLL IDR
device.
8) For a detailed description on using the Spectrum Analyzer, refer to the
WipConfig User's Guide.

28.3.1.1. Accessing the Spectrum Analyzer

You can access the Spectrum Analyzer through either a serial or an IP network
communication mode.
To access the Spectrum Analyzer:
1. Start WipConfig and then connect WipConfig to the BSR by performing one of
the following:
Serial mode: on the toolbar, select the Serial option, and then click
Connect.
IP mode: on the toolbar, select the Network option, and then in the Remote
Agent field, enter the ASWipLL device's IP address, and then click
Connect.
2. In the Outlook bar, click the Spectrum Analyzer button; A message box
appears informing you that the device will lose connection with all other devices.
3. Click OK.
28.3.1.2. Setting up the Spectrum Analyzer

Before you can start analyzing the spectrum, you need to define various parameters
in the Spectrum Analyzer.
To set up the Spectrum Analyzer:
1. Ensure the Setup tab (located in the top-right pane) is selected.
2. In the Refresh Rate field, enter the rate (in seconds) for polling the BSR/PPR.
(The default is 3 sec; maximum is 3600 sec.)

3. In the Number of Sweeps group, select the option for scanning the frequency
range:
Single: scans the spectrum only once
Continuous: cyclically scans the spectrum (i.e. repetitively)
Custom: you can define the number of sweeps (range is 0 through 1,000
sweeps)
4. To change the antenna gain, in the Antenna Gain field, enter the antenna gain.
If you want to restore the BSR’s default antenna gain, click the True Antenna
Gain Value button.
5. To define the frequency range for which you want to analyze, define the
following fields:
Start Freq: frequency from where you want to scan (i.e. lower frequency)
Stop Freq: frequency to where you want to scan (i.e. upper frequency)
28.3.1.3. Starting the Spectrum Analyzer
To start and stop the Spectrum Analyzer, click the Start and Stop
buttons (located below the graph), respectively.

28.3.1.4. Viewing Results

The Spectrum Analyzer results are plotted on the graph as well as displayed in the
Results table (to access the Results table simply click the Results tab). The
following measurements are displayed:
Average received signal strength (RSSI) per frequency (plotted white line on the
graph)
Maximum hold received signal strength (RSSI) per frequency (plotted yellow
line on the graph)
Distance (in spectrum RF) that the BSR/PPR can establish a viable communication
link with another transmitter. This is displayed in the TxRxOffset field.
Interference of
–70 dBm at
2,445 MHz
Figure 28-3: WipConfig's spectrum analyzer showing peak interference of -70 dBm

28.4. Bit Error Rate (BER)

It is important to measure bit error rate (BER) levels between the BSR and SPR to
ensure that a high quality link exists. Bit error rate is the percentage of bits with
errors divided by the total number of bits that have been transmitted, received or
processed over a given period. The rate is typically expressed as 10 to the negative
power. For example, four erroneous bits out of 100,000 bits transmitted would be
expressed as 4 x 10-5 (or 4E-5).
The more bits transmitted, the more accurate the BER measurement. Thus, it is
important to use a third-party tool such as Iperf that generates a flood of UDP
packets.
Note: To measure BER, ensure that a flood of packets between the BSR and
SPR are generated (see Section 28.5, "Generating Traffic to Measure
Throughput").
The BER can be measured locally at the SPR using WipConfig, or it can be
measured remotely using WipManage.

28.4.1. Measuring BER Using WipConfig

You can measure BER using WipConfig only at the SPR.
To measure BER at the SPR using WipConfig:
1. Start WipConfig, and then connect it to the SPR.
2. In the outlook bar, click the Statistics button.

The Statistic pane appears, as displayed below.
BER graph
measuring
BER between
BSR and SPR
Figure 28-4: Statistics pane

28.4.2. Measuring BER Using WipManage

You can measure BER using WipManage.
To measure BER using WipManage:
1. Open the BSR Zoom window pertaining to the BSR whose BER you want to
measure.
2. From the Performance menu, point to Air, point to Cell, and then choose BER
per SPR.
The BER per SPR window is displayed below.
Figure 28-5: BER per SPR graph

28.5. Generating Traffic to Measure Throughput

For measuring BER, RSSI (at the BSR), and throughput, you need to generate a
flood of traffic between the BSR and SPR. The following methods can be
implemented to generate traffic:
Iperf program:
You can use a third-party free firmware program such as Iperf (free download at
http://dast.nlanr.net/Projects/Iperf/), which generates a flood of UDP packets to
measure throughput. Using this program, a simple batch file can be made for the
client side (behind the SPR) and for the Base Station side (behind the BSR) to
ease the throughput measurement procedure.
FTP:
An FTP session can be used to generate TCP packets to measure throughput.
Connect a PC to the SPR/IDR and run three to four simultaneous FTP sessions
to an FTP server that is physically connected to the BSR’s LAN port (e.g.
Microsoft IIS, and Linux FTP built-in servers). The few concurrent sessions
eliminate the Slow Start phenomenon (succinct explanation can be found in RFC
#2001). During the test, record the RSSI and BER levels for the BSR and
SPR/IDR. This information is useful to Airspan’s technical support team for
future diagnosis.


29
Troubleshooting
This chapter explains how to solve the following problems that you might encounter
when using WipManage:
No PC-BSR Network Link
No BSR-SPR Air Link
No PC-SPR Network Link

Troubleshooting Commissioning Manual
29.1. No PC-BSR Network Link

When no network link exists between the BSR and PC running WipManage, the
BSR icon is displayed in red ( ) in the WipManage main window.
Table 29-1: Solution for no BSR-PC network link

Solution
• Ensure the BSR is receiving power (from the BSDU or SDA).
• Check IP connectivity with BSR by pinging the BSR (MS-DOS command: ping –t
<BSR’s IP address>).
• Check the PC’s network IP addressing configurations (i.e. IP address, subnet mask, and default
gateway).
29.2. No BSR-SPR/IDR Air Link

When no air link exists between BSR and SPR/IDR, in the BSR Zoom window, the
SPR icon is displayed with a yellow circle and red rectangle ( ).
Table 29-2: Solutions for no BSR-SPR/IDR air link

Solution
• Ensure that power is received by the SPR/IDR.
• Ensure that the version disk file/ROM (VDF) for the BSR and SPR/IDR are identical. If not,
this may result in different frequencies used by the BSR and SPR/IDR (even if the frequency
table ID is the same). These frequencies are ROM Frequency tables (0-31). If the VDFs differ,
then define an NVRAM frequency table (32-63) that is the same for the BSR and SPR/IDR.
• Ensure BSR and SPR/IDR transmission rates (i.e. 3 Mbps or 4 Mbps) are identical
• Ensure BSR's Air MAC address is defined correctly in the SPR/IDR.
• Ensure SPR/IDR index number in the SPR/IDR is defined correctly (i.e. if the index is defined
as 2 in WipConfig, then in WipManage, add the SPR to index icon #2).
• Ensure that the external antenna is connected (if an external antenna exists).
• Ensure that the distance between the BSR and SPR/IDR is in range for RF communication.
• Ensure no obstacles in LOS between BSR and SPR/IDR that may interfere with transmission.

Commissioning Manual Troubleshooting
29.3. No PC-SPR Network Link

When no network link exists between the PC running WipManage and the
SPR/IDR, the SPR icon is displayed as a green circle and red rectangle ( ) in the
BSR Zoom window. (Note that an air link can exist in such a scenario between the
BSR and SPR/IDR.)
Table 29-3: Solution for no SPR-PC network link

Solution
• Ensure WipManage management’s IP address is correct.
• For AS WipLL in the IP router mode, check that the routing table is correctly defined.
• For AS WipLL in the transparent bridge mode, delete the ARP table (MS-DOS command: ARP
–d)
• Ensure that the SPR/IDR and BSR are configured for the same modes (i.e. IP Router or
Transparent Bridge)
• Check PC’s routing table for correct routes from BSR to SPR/IDR (MS-DOS command:
route print):
• For AS WipLL in the transparent bridge mode, check PC’s routing table for correct routes from
BSR to SPR/IDR (MS-DOS command: tracert <SPR’s IP address>:

Troubleshooting Commissioning Manual
Solution
• If all the above routing verifications are correct, and still no network link to the SPR/IDR, using
WipConfig, reset the SPR/IDR to factory defaults, and then reconfigure the SPR/IDR. This
ensures that your configuration settings are correct.

Commissioning Manual v06-460 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Commissioning Manual v06-460 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

ASWipLL and

Leading the World in Wireless DSL

Revision Record: ASWipLL Commissioning Manual

Publication No. 01040311-06

1. Introduction .............................................................................................. 1-1

01040311-06 Airspan Networks Inc. v

2. Installing ASWipLL Management Software ........................................... 2-1

3. Initial Configuration ................................................................................. 3-1

4. Establishing BSR-SPR Link in Router Mode ......................................... 4-1

vi Airspan Networks Inc. 01040311-06

5. Establishing BSR-SPR Link in Bridge Mode ......................................... 5-1

6. Changing Link from Router to Bridge .................................................... 6-1

7. Changing Link from Bridge to Router .................................................... 7-1

01040311-06 Airspan Networks Inc. vii

7.5. Task 3: Add an SPR.......................................................................... 7-15

8. Establishing BSR-SPR Link with AutoConnect..................................... 8-1

viii Airspan Networks Inc. 01040311-06

9. Configuring a Point-to-Point Radio Link................................................ 9-1

10. Configuring a Repeater Solution .......................................................... 10-1

11. Managing Bandwidth ............................................................................. 11-1

12. Defining Static Routes ........................................................................... 12-1

01040311-06 Airspan Networks Inc. ix

12.2.2. Task 1: Add Static Route to BSR ..................................... 12-4

13. Defining Virtual Ports............................................................................. 13-1

14. Defining VLANs ...................................................................................... 14-1

15. Defining Air Subnets.............................................................................. 15-1

x Airspan Networks Inc. 01040311-06

15.2.7. Task 6: Add BSR and SPR in WipManage..................... 15-16

16. Defining ASWipLL as a DHCP Relay Agent ......................................... 16-1

17. Defining PPPoE ...................................................................................... 17-1

18. Configuring BSR Antenna ..................................................................... 18-1

19. Configuring Radio Transmit Power ...................................................... 19-1

01040311-06 Airspan Networks Inc. xi

20. Managing Frequency Tables ................................................................. 20-1

21. Defining Synchronization ...................................................................... 21-1

xii Airspan Networks Inc. 01040311-06

22. Defining Transmission Rate.................................................................. 22-1

23. Defining Security.................................................................................... 23-1

01040311-06 Airspan Networks Inc. xiii

23.5.7. Task 6: Reset the SPR ................................................... 23-23

24. Defining Quality of Service.................................................................... 24-1

25. Managing Traps...................................................................................... 25-1

26. Upgrading ASWipLL Database ............................................................. 26-1

xiv Airspan Networks Inc. 01040311-06

26.4. Task 2: Start WipLL DB Upgrade .................................................. 26-10

27. Upgrading ASWipLL Devices................................................................ 27-1

28. Evaluating Link Quality.......................................................................... 28-1

29. Troubleshooting ..................................................................................... 29-1

01040311-06 Airspan Networks Inc. xv

This page is intentionally left blank.

xvi Airspan Networks Inc. 01040311-06

01040311-06 Airspan Networks Inc. xvii

Organization of this Manual

xviii Airspan Networks Inc. 01040311-06

Chapter 6, "Changing Link from Router to Bridge Mode": provides step-by-

01040311-06 Airspan Networks Inc. xix

Chapter 17, "Defining PPPoE": provides step-by-step instructions for defining

xx Airspan Networks Inc. 01040311-06

Bold Command and menu names, Click the Next button.

01040311-06 Airspan Networks Inc. xxi

This page is intentionally left blank.

xxii Airspan Networks Inc. 01040311-06

01040311-06 Airspan Networks Inc. 1-1