pves installation and management guide v2.5

ProximVision ESInstallation and Management Guide

Copyright© 2011 Proxim Wireless. All rights reserved. Covered by one or more of the following U.S. patents: 5,231,634; 5,875,179; 6,006,090; 5,809,060;6,075,812; 5,077,753. This Installation and Management Guide, and the software described in it are copyrighted with all rights reserved. No part ofthis publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any meanswithout the written permission of Proxim Wireless.

TrademarkProxim is a registered trademark, and ProximVision ES and the Proxim logo are trademarks of Proxim Wireless. All other trademarks mentionedherein are the property of their respective owners.

DisclaimerProxim reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Proxim toprovide notification of such revision or change. Proxim may make improvements or changes in the product(s) described in this Installation andManagement guide at any time.

ProximVision ES - Installation and Management GuideSoftware Version: 2.5

Documentation Version: 2.5P/N 76907, June 2011

ProximVision ES Installation and Management Guide 2

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

ProximVision ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Integrating ProximVision ES into the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

License Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Re-Install ProximVision ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

ProximVision ES Standalone Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Initialization of ProximVision ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Launch ProximVision ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 ProximVision ES Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Startup Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About ProximVision ES Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Discover Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configure Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Mode Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4 Discovery of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configure Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Filter Type: Include Address Range - Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Filter Type: Include Address Range - IP Address Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Filter Type: Exclude Address Range - Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Filter Type: Exclude Address Range - IP Address Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Restart Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Manage Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Manual Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Discover TDM IDU Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Prerequisites for GX800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Operational Features of the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Ping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Web Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Generate Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Commit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Add SU/EP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Enable SNMP and Disable SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5 Creating Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Creating New Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63User Subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Deleting Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Renaming Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Discover Devices under a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Add Devices to a User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Delete Devices from Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6 Configuring Individual Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7 Monitoring Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Performance Monitoring through Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81SNR Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Current Statistics Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Graph Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

AP-700 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

AP-4000 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

AP-800, AP-8000 and AP-8000MR Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

MP.11 and QB.11 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

MP.16 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

MP.11 HS 5054 Series and MP.11 HS 4454 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

GX800 Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

MP-8100 Series and QB-8100 Series Device Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88


8 Configuring Devices in Bulk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Bulk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91An Example for Bulk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Bulk Configurable Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

9 Network Mapping of the Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Map Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Dynamic Map Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Configure a Location in Dynamic Map Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Change Dynamic Map Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Static Map Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Configure a Location in Static Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Map Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Locate a Device on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Device Placement on Dynamic Map at configured GPS Co-ordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

10 Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Trap Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

SysLog Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Custom Inventory Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

ScanTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Locate a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Show ProximVision ES Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Connectivity Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Device Does Not Boot - No LED Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Serial Link Does Not Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

RADIUS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Windows Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

SNMPv1/v2c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Invalid Subnet Mask or IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Unable to Discover GX800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136


Management Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

SNMPv3 Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Third Party Server Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Unknown Host/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Invalid Entry while Configuring SSID/VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Unable to create Syslog, Trap Host and VLAN Entries for MP.16 device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Screen Resolution Related Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Miscellaneous Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

A ProximVision ES Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

B Technical Services and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145


ProximVision ES Installation and Management Guide

1
Introduction
This chapter contains information on the following:

• ProximVision ES• Integrating ProximVision ES into the Network

7

Introduction

1.1 ProximVision ESProximVision ES (commonly known as PVES) is Proxim’s network management system that helps to manage and administerwireless networks effectively and efficiently. ProximVision ES combines industry-leading functionality with an intuitive userinterface, enabling Network Administrators and Help Desk staff to support and control a wireless network from a centralizedlocation. ProximVision ES supports only Proxim devices. For Proxim devices, refer to ProximVision ES Supported Devices.

Its features are as follows:

• Rapid Network Deployment: Automates configuration processes for faster, more efficient deployment of ProximWireless networks.

• Mobile Configuration Capabilities: Helps Network Managers with mobile options for exhaustive deviceconfigurations.

• Geographical Network View and Statistical Plots: Provides a map overlay of the entire network with real-time,visual network status indicators.

• Greater Ease of Use and Upgradability: Allows to manage entire network from a single console.

1.2 Integrating ProximVision ES into the NetworkProximVision ES generally resides in the Microsoft Windows machine and communicates with various components of yourWLAN infrastructure. In any deployment, ProximVision ES seamlessly integrates and communicates with Access Points,Point-to-multipoint devices, Point-to-point devices, Mesh devices and Time Division Multiplexing (TDM) devices. From acentral location, you can manage your network; real-time monitoring allows you to monitor the health and status of thedevices on the network. With the help of ProximVision ES, you can plan your network usage and ensure optimum utilization.ProximVision ES communicates over-the-air or over-the-wire utilizing a variety of protocols.

IMPORTANT!

This Installation and Management Guide provides instructions for the installation, configuration, and operation of the Proxim devices by using ProximVision ES. For any queries, please contact Proxim’s Technical

Services and Support team.



2
Installation

• System Requirements• License Policy• Software Installation• Re-Install ProximVision ES• ProximVision ES Standalone Backup Utility• Initialization of ProximVision ES• Software Updates

9

Installation

2.1 System RequirementsBefore installing ProximVision ES, check the following system requirements for best results.

• Windows 2003/ XP/ Windows 7

• Minimum dual core processor with 3 Ghz speed

• Use minimum 2 GB RAM for Windows XP and 4 GB RAM for Windows 7. If the manageable devices are more than100, please use 4 GB RAM for Windows XP and minimum 6 GB RAM for Windows 7.

• An additional of 250 MB Hard Disk space

NOTES:• Please upgrade the system configuration settings, incase, ProximVision ES is used along with other applications on

the same machine. For example, any sniffers or any other Network Management System running on the samemachine.

• These system configuration settings are applicable only for ProximVision ES.

• User’s can experience a slowdown in the ProximVision ES performance, if the system configurations are not doneproperly.

• You cannot install ProximVision ES on a Virtual Machine.

2.2 License PolicyThe following is a brief summary of the ProximVision ES license policy.

• By default and without additional licenses, ProximVision ES allows you to configure and monitor up to four devices. Toconfigure and monitor more devices, you will have to purchase additional licenses from Proxim Wireless.

• When you install ProximVision ES for the first time, a LicenseData.lic file is generated in the lic subdirectory ofProximVision ES install directory (C:\Program Files\Proxim Wireless\ProximVision ES2.0\lic). You have to share thisLicenseData.lic file with the Proxim Wireless Customer Support team who will generate another License.lic file andshare it with you. Use the upload utility that comes with ProximVision ES to upload the License.lic file. To upload theLicense.lic file, refer to Upload License.

2.3 Software InstallationTo install the software, follow the following steps.

NOTE: Proxim recommends you to set the display settings at 96 dpi that is compatible for working with ProximVisionES.

1. Double-click the ProximVision ES executable file. The ProximVision ES - InstallShield Wizard window appears.


Installation

Figure 2-1 InstallShield Wizard

2. Click Next to proceed with the installation. The InstallShield Wizard extracts the files needed to install ProximVision ES onyour computer as shown in the following screen.

Figure 2-2 Extracting Files

3. After the files are extracted, the ProximVision ES Setup page appears.


Installation

Figure 2-3 Setup

4. Click ProximVision ES link to install ProximVision ES.

a. Scenario 1 - If you are upgrading ProximVision ES from 2.x to a higher version, then the following upgrade windowappears.

Figure 2-4 Upgrade Window

1. Click Yes to proceed with the version upgrade of ProximVision ES else click No.

NOTES:• Before upgrading the version, it is recommended to take a back up of the ProximVision ES application.

– If you are upgrading the version from 2.1 to 2.x, use the Export Data which comes as part of theProximVision ES application, to take a backup of the data.

– If you are upgrading the version from 2.0 to 2.x, use the ProximVision ES Standalone Backup Utilitywhich is available at http://support.proxim.com, to take a backup of the data.

• After upgrading the version, you can use the Import Data utility which comes as part of the ProximVision ESapplication to restore the settings.

2. When you click Yes in the upgrade window, the ProximVision ES InstallShield Wizard window appears.


Installation

Figure 2-5 Upgrade - InstallShield Wizard

3. Click Next to proceed with the installation. The Setup Status window appears.

Figure 2-6 Upgrade - Setup Status

4. Once the InstallShield Wizard successfully installs ProximVision ES on your system, the ProximVision ESInstallation Complete window appears.


Installation

Figure 2-7 Upgrade Installation Confirmation

5. Click Finish to exit the InstallShield Wizard window.

b. Scenario 2 - If you are installing ProximVision ES for the first time or upgrading the version from 1.x to 2.x, then thefollowing ProximVision ES - InstallShield Wizard window appears.

NOTE: Uninstall any previous version of ProximVision ES 1.x before you proceed with the installation of ProximVision ES2.x. Otherwise, the installation files will get corrupted.

Figure 2-8 Install ProximVision ES


Installation

1. Click Next. The License Agreement window appears. Read the license Agreement and then select “I accept the terms of the license agreement” and click Next.

Figure 2-9 License Agreement

2. The Customer Information window appears. Enter User Name and Company Name, and then click Next.

Figure 2-10 Customer Information

3. The Setup Type window appears. Select the Setup Type as either Complete or Custom, and then click Next.


Installation

Figure 2-11 Setup Type

4. Selecting Complete as the setup type leads you to a default pathway of installation; whereas, selecting Customprompts you to customize the installation pathway.

a. If you select Custom in the Setup Type window, the following window appears.

Figure 2-12 Choose Destination Location

— Click Change and select a folder where you want to install the files. Click OK.

— Click Next. The Select Features window appears.


Installation

Figure 2-13 Select Features

— Select DefaultFeature and click Next. The Ready to Install ProximVision ES window appears asshown in Figure 2-14.

b. If you select Complete in the Setup Type window, the following window appears.

Figure 2-14 Ready to Install ProximVision ES

5. Click Install to install ProximVision ES. The Setup Status window appears.


Installation

Figure 2-15 Setup Status

6. Click Finish to complete installation.

Figure 2-16 Setup Complete Confirmation

2.4 Re-Install ProximVision ESIf ProximVision ES fails to install, follow the following steps to re-install the software.

1. Take a backup of the files. If you are upgrading ProximVision ES from 2.0 to 2.x, refer to ProximVision ES StandaloneBackup Utility for backup method, else refer to Export Data.

2. Uninstall ProximVision ES

3. Re-Install ProximVision ES


Installation

4. Restore the backup files by navigating to Start > Programs > Proxim Wireless > ProximVision ES2.0 > ImportData.

2.5 ProximVision ES Standalone Backup UtilityWhen you upgrade ProximVision ES from 2.0 to 2.x, it is recommended to take a back up of the ProximVision ES files by usingthe ProximVision ES Standalone Backup Utility file, which is available at http://support.proxim.com.

Follow the following steps to take a back up of the ProximVision ES files.

1. Download the ProximVision ES Standalone Backup Utility file, which is available at http://support.proxim.com.

2. Double-click the ProximVision ES Backup Utility executable file.

3. The ProximVision ES 2.0 BackUp Utility window appears.

Figure 2-17 ProximVision ES 2.0 BackUp Utility

4. Click Browse to select a folder (C:\Program Files\Proxim Wireless\ProximVision ES2.0) to install ProximVision ESBackup executable file.

5. After selecting the destination folder, click Install.

6. The Backup Files window appears.

Figure 2-18 Backup Files Window

7. Click Browse to select a folder to back up the files.

8. Finally, click Back up. A window appears which displays the path where the backup files are stored.


Installation

Figure 2-19 Backup Files Path Message

2.6 Initialization of ProximVision ESNavigate to Start > Programs > Proxim Wireless > ProximVision ES2.0.

Figure 2-20 Startup ProximVision ES

ProximVision ES contains the following menu options.

• Auto Discovery Defaults: Click this option to set all auto discovery configurations to factory.

• Delete All Devices: Click this option to delete all the devices that are discovered.

NOTE: You have to close ProximVision ES before using Delete All Devices option. Never use Delete All Devicesoption while ProximVision ES is running.

• Export Data

Click this option to back up ProximVision ES files (such as Discovered Device Data, Map Data, Device information and soon) to the desired folder on your Personal Computer. It is advisable to back up all the necessary data at frequent intervalsso that the user can restore the settings of ProximVision ES in the event of unexpected failures in the Operating System,Database Corruption, Upgrading to a newer version and so on.


Installation

To export data,

a. Navigate to Start > Programs > Proxim Wireless > ProximVision ES2.0 > ExportData.

b. The Backup Files window appears.

Figure 2-21 Export Data - Backup Files

c. Click Browse to select a folder to export files. The following window appears. Select a folder to export data andclick Open.

Figure 2-22 Export Data - Choose Folder

d. In Figure 2-21, click Back up to export data to the above selected folder. On successful backup, a message isdisplayed which shows the path where the backup files are saved.

Figure 2-23 Backup Confirmation Message

e. Click Ok to close the window.

• GenerateLicData: Click this option to regenerate license information.

• Import Data

Click this option to restore the exported data, back to ProximVision ES.


Installation

To import data,

a. Navigate to Start > Programs > Proxim Wireless > ProximVision ES2.0 > ImportData. The following windowappears.

Figure 2-24 Import Data

b. Click Browse. The Open window appears. Select the backup files (only zip files) that you want to restore toProximVision ES and click Open.

Figure 2-25 Choose Files to Restore

c. In Figure 2-24, click Restore to restore the selected files to ProximVision ES. On successfully restoring the backup file,the following screen appears.

Figure 2-26 Restore Success Message

• ProximVision ES: Click this option to launch ProximVision ES. To launch ProximVision ES, refer to Launch ProximVisionES.

• ScanTool: Click this option to invoke Proxim’s ScanTool to scan all the devices available on the network.


Installation

• Upload License

Click this option to upload the license file (license.lic) obtained from Proxim’s Customer Support team.

To upload the license file, navigate to Start > Programs > Proxim Wireless > ProximVision ES2.0 > Upload License.The Upload License window appears. Click Browse to select the license file and click Upload.

Figure 2-27 Upload License

NOTE: If the user does not upload the valid license.lic file or works with default license then the maximum number ofdevices supported by ProximVision ES is four.

Figure 2-28 License Information

2.6.1 Launch ProximVision ES

To launch ProximVision ES, navigate to Start > Programs > Proxim Wireless > ProximVision ES2.0 > ProximVision ES.Alternatively, you can also click ProximVision ES icon on the desktop.


Installation

You are now directed to ProximVision ES login window. Login credentials authenticate a valid user to log on to ProximVisionES.

Figure 2-29 User Login Window

There are two types of users:

1. Administrator User - The Administrator user administers the entire ProximVision ES application. This user type hasthe write access to all the features of ProximVision ES and also has the privilege to change his or her own passwordand that of the Monitor user (the other user type). To change the password, refer to Change Password.

2. Monitor User - The Monitor user has only view access to all the features of ProximVision ES. However, the Monitoruser can,

• Enable Station Statistics in AP-700, AP-4000, AP-4000MR and AP-4000MR-LR devices

• Enable Sys Log, Event Log and SNTP in AP-800, AP-8000 and AP-8000MR devices

• Enable Event Log, SNTP and Temperature in MP-81XX and QB-81XX devices

• Monitor and view the performance statistics of the configured devices

• Access Map functionality feature to view devices installed at specified locations

• Change his or her own password

Follow the following steps to log on to ProximVision ES.

In the ProximVision ES login window,

1. Type a valid user name in the User Name box. The user name is admin for the Administrator user and monitor forthe Monitor user.

2. Type the password in the Password box. By default, the password is public for both the Administrator user and theMonitor user.

NOTE: By default the password is public. For security reasons, it is recommended to change the password after yourfirst logon to ProximVision ES. To change the password, refer to Change Password. A password can have spaces butit should not start or end with a space.

3. Click Ok to log on to ProximVision ES.

On successful logon, ProximVision ES is launched.


Installation

Figure 2-30 Launching ProximVision ES

NOTE: If you are launching ProximVision ES in Windows 7, the windows will temporarily change the color scheme towindows 7 basic.

2.7 Software Updates Proxim releases new versions of ProximVision ES software from time to time. So it is recommended to check the Proxim Website for latest updates. To download and install the latest software, follow these steps.

1. In your web browser, open the link http://support.proxim.com.

2. Log on to the support page with your username and password. If you have not created an account, create an accountto gain access.

3. At the upper-left of the home page, click Product Downloads Page

4. You are directed to the Product Downloads and Documentation page. Click ProximVision ES2 under NetworkManagement / Tool.

5. You are now directed to another page, wherein, you can download the latest release of the ProximVision ES softwarealong with the documentation, to the desired location on your personal computer.

6. Run the.exe to install the software.

7. If you are facing any problem while installing the software, please contact Proxim’s Technical Services and Supportteam.



3
ProximVision ES Overview

• User Interface• Toolbar Icons• TFTP Server• Telnet

26


3.1 User InterfaceAfter the successful launch, the ProximVision ES home page along with the Proxim’s Product portfolio window appears.

Figure 3-1 Home Page and Startup Information Window

3.1.1 Startup Information Window

The Startup Information window gives you information about the ProximVision ES version and its license.

It also gives you an insight on all the Proxim wireless products. You can view the data sheet of each product by just clickingthe respective product link.

If you do not want the product window to open while ProximVision ES is launched then select the check box Do not showthis message at startup at the lower-left of the window.



3.1.2 About ProximVision ES Home Page

The title bar contains the ProximVision ES application name.

The left panel is termed as Device Tree of ProximVision ES, whereas the right panel is the Configuration Table.

The Device Tree represents a tree structure of all the Proxim devices that are available on the network.

If you are launching ProximVision ES application for the first time, the devices will not be shown in the Device Tree as they areyet to be auto discovered. To auto discover the devices, refer to Configure Auto Discovery.

NOTE: Ensure that your system is connected to the network on which all the devices are configured.

Figure 3-2 Home Page with Devices Discovered

Once the devices are auto discovered, they will be displayed in a tree structure format in the Device Tree. These devices aregrouped under the following respective groups,

• Default groups (AP [Access Point], TMP [Tsunami™ Multipoint])

• User-defined Links which contains the following devices

– Tsunami 8000 TDM IDU (Central Office (CO) and Customer Premises Equipment (CPE))

– Tsunami QB 81XX End Point A and B



• User-created groups

ProximVision supports BSU-SU, AP-clients and TDM IDU-QB tree structure.

If you select a device in the Device Tree, the information about that device is displayed in the lower-left pane of the DeviceTree.

The Configuration table provides you the platform to configure the device parameters.

NOTE: When you start ProximVision ES application next time, the devices that were discovered earlier will beautomatically queried for device status (either online or offline) and are displayed in the Device Tree. A status barindicates the progress made while querying the devices on the network as shown in Figure 3-3. The status bardisplays 100% when the device status check is complete. On reaching 100%, the status bar automatically getsclosed.

Figure 3-3 Status Bar

NOTE: If a device is down and cannot be configured or monitored, then that specific device is highlighted in Red.

The status bar contains the following information.

• Total Devices - Indicates the total number of devices discovered on the network.

• Up - Indicates the total number of devices that are currently up on the network.

• Down - Indicates the total number of devices that are currently down on the network.



• Undiscovered - Indicates the total number of devices that are shown in ProximVision ES but cannot be managed.

• Licensed Information - Indicates the total number of nodes for which the user is licensed to configure devices.

• Logged in as - Indicates the type of user logged into ProximVision ES. The user can either be an Administrator user ora Monitor user.

ProximVision ES home page contains the following menu items:

• Discover Menu• Configure Menu• Tools Menu• Mode Menu• Help Menu



3.1.3 Discover Menu

The Discover menu enables you to discover devices that are available on the network. It contains the following submenus.

Figure 3-4 Discover Menu

3.1.3.1 Configure Auto Discovery

By using the Configure Auto Discovery submenu, you can discover all devices available in the specified IP range and subnetrange that ProximVision ES manages. You must specify the IP address and the subnet for auto discovery process. To autodiscover the devices, refer to Configure Auto Discovery.

3.1.3.2 Restart Auto Discovery

By using the Restart Auto Discovery submenu, you can restart the auto discovery process. To restart auto discovery process,refer to Restart Auto Discovery.

3.1.3.3 Manage Auto Discovery

By using the Manage Auto Discovery submenu, you can manage the auto discovery process. To manage auto discoveryprocess, refer to Manage Auto Discovery.

3.1.3.4 Manual Discovery

By using the Manual Discovery submenu, you can discover the devices manually. You must specify the IP address to discovera device. To manually discover a device on the network, refer to Manual Discovery.

3.1.3.5 Discover TDM IDU Link

By using the Discover TDM IDU Link submenu, you can discover the link which contains the devices - Tsunami 8000 TDMIDU (Central Office (CO) and Customer Premises Equipment (CPE)), Tsunami QB 81XX End Point A and Tsunami QB 81XX EndPoint B. To discover a link, refer to Discover TDM IDU Link.



3.1.4 Configure Menu

The Configure menu enables you to configure devices in bulk, organize devices under the respective user groups and changemap locations. It contains the following submenus.

Figure 3-5 Configure Menu

3.1.4.1 Bulk Operations

By using the Bulk Operations submenu, you can configure devices in bulk. To configure devices in bulk, refer to BulkOperations.

3.1.4.2 Organize Devices

By using the Organize Devices submenu, you can organize devices under the respective user-defined groups. To organizedevices under the user groups, refer to Add Devices to a User Group.

3.1.4.3 Change Map Locations

By using Change Map Locations submenu, you can change map locations in either Dynamic Map Mode or Static MapMode. To change map locations, refer to Network Mapping of the Devices.

3.1.5 Tools Menu

The Tools menu enables you to monitor the health of the devices and their performance status with the help of Log Files andreports. It also enables you to scan the devices available on the entire network and also locate devices available in the devicetree of ProximVision ES. It also provides the platform for the Administrator user and the Monitor user, to change thepassword. The Tools menu contains the following submenus.



Figure 3-6 Tools Menu

3.1.5.1 Preferences

The Preferences submenu contains the following menu items.

1. Polling Interval

By using the Polling Interval feature, you can set the polling interval to monitor the up/down status of the device.

To set the polling interval,

a. Navigate to Tools > Preferences > Polling Interval. The Polling Interval window appears.

Figure 3-7 Polling Interval

b. Type a value (in minutes) in the Interval box and click Set. Set the polling interval as minimum as possible to getaccurate status of the network. This will increase the bandwidth usage on the network.

NOTE: By default, the polling interval is 10 minutes. You can set the minimum polling interval as 3 minutes andmaximum as 1440 minutes.

2. Periodic Performance

By using Periodic Performance feature, you can generate SNR plots for the devices, in the duration of the set pollinginterval.

To set the polling interval,

a. Navigate to Tools > Preferences > Periodic Performance.



Figure 3-8 Performance Collection

b. Type the polling interval in minutes in the Polling Interval (in Minutes) box.

c. Click Start Polling to start polling the performance of the devices on the network.

d. To stop polling, click Stop Polling. While polling, you can also change the polling interval time. To do so, change thetime in the Polling Interval (in Minutes) box and click Change Poll Interval.

3. Change Password

By using the Change Password submenu, the user can change his or her own password. Note that this password is used tolog on to ProximVision ES.

To change the password, navigate to Tools > Preferences > Change Password. The Change Password window appears.

Figure 3-9 Change Password

In the Change Password window,

1. Select the user name from the User Name box. If you are changing Administrator user password then the user nameis admin and if you are changing Monitor user password then the user name is monitor.

2. Type the password, which is by default public for both the Administrator user and the Monitor user, in the CurrentPassword box.



3. Type the new password in the New Password(6-10) box. The password should be minimum of six characters andmaximum of ten characters.

NOTE: A password can have spaces but it should not start or end with a space.

4. Confirm the new password by re-entering it in the Confirm Password(6-10) box.

5. Click Change to change the password.

NOTE: The Administrator user has the privilege to change his or her own password and that of the Monitor user.

3.1.5.2 Settings

By using the Settings submenu, you can edit the static map images that are uploaded onto the ProximVision ES, by usingImage Editors like Microsoft Paint, Adobe Photoshop or any other image editing applications. To edit static map images, referto Edit an Image using Image Editor.

3.1.5.3 Trap Viewer

By using the Trap Viewer submenu, you can view information about the traps that a device encounters. To view Trap logs,refer to Trap Viewer.

3.1.5.4 Syslog Viewer

By using the SysLog Viewer submenu, you can view logs that a device sends periodically about its status. To view Syslogs,refer to SysLog Viewer.

3.1.5.5 Inventory Report

By using the Inventory Report submenu, you can generate reports for the devices connected on the network. To generateInventory reports, refer to Inventory Report.

3.1.5.6 Custom Inventory Report

By using the Custom Inventory Report submenu, you can customize the inventory reports for the devices connected on thenetwork. To generate Custom Inventory reports, refer to Custom Inventory Report.

3.1.5.7 ScanTool

By using the ScanTool submenu, you can scan all the devices available on the network. For more information on ScanTool,refer to ScanTool.

3.1.5.8 Locate a Device

By using the Locate a Device submenu, you can locate a device in the Device Tree. You can also use this feature to locate adevice on the map. You must specify the IP address of the device for it to be discovered. Refer to Locate a Device.

3.1.5.9 Show ProximVision ES Log

By using the Show ProximVision ES Log, submenu, you can view the logs encountered while using ProximVision ES. Fordetails on Show ProximVision ES Log, refer to Show ProximVision ES Log.



3.1.6 Mode Menu

By using the Mode menu, you can toggle between Configure Mode, Dynamic Map Mode and Static Map Mode. For detailson these modes, refer to Configuring Individual Device Settings, Dynamic Map Mode and Static Map Mode respectively.

Figure 3-10 Mode Menu

3.1.7 Help Menu

The Help menu helps you to view details about ProximVision ES version, its license information and the Proxim products. Italso helps you to view the ProximVision ES Installation and Management guide.

Figure 3-11 Help Menu

3.1.7.1 About ProximVision ES

To view information on ProximVision ES wireless products and its datasheet, navigate to Help > About ProximVision ES.

For more information, refer to Startup Information Window.



3.1.7.2 ProximVision ES Help

To view ProximVision ES Installation and Management Guide, navigate to Help > ProximVision ES Help. Alternatively, clickF1.

3.2 Toolbar IconsProximVision ES provides icons that enable you to perform certain tasks directly from the tool bar:

Figure 3-12 Toolbar Icons

• Click Configure Auto Discovery icon to discover devices for a certain IP range/subnet range.

• Click Discover New Device icon to discover a device manually.

• Click Bulk Operations icon to configure devices in bulk.

• Click Refresh icon to refresh all the devices available on the network.

• Click Periodic Polling icon to set the polling interval.

• Click Trap Messages icon to view Trap Log messages.

• Click SysLog Messages icon to view SysLog messages of all the devices available on the network.

• Click Inventory Report icon to view the inventory report of all the devices available on the network.

• Click Telnet icon to manage a device through CLI commands.

• Click Configure Mode icon to switch to Configure mode.

• Click Map Mode icon to toggle between Map Modes (Dynamic and Static).

• Click ProximVision ES Help icon to view ProximVision ES Installation and Management Guide.

3.3 TFTP ServerThe “Trivial File Transfer Protocol” (TFTP) server allows you to transfer files on a network. You can upload configuration filesfrom the device to the Personal Computer for backup or copying, and you can download configuration files or new softwareimages to the devices. The TFTP software is located on the installation CD. If a TFTP server is not configured and is running,you will not be able to download and upload images, and configure files to/from the device. Remember that the TFTP serverdoes not have to reside on the same server as ProximVision ES, it can reside on any Windows Personal Computer or Serverthat is network accessible from ProximVision ES and Proxim devices. Note that you do not need a TFTP server running unlessyou want to transfer files to/from the device.

• Check to see that TFTP is configured, to point to the directory containing the device image.

• Ensure that the proper TFTP server device address, the proper device Image file name, and that the TFTP server isconnected.

• Ensure that the TFTP server is configured to both transmit and receive files (on the TFTP server’s Security tab), with noautomatic shutdown or time-out (on the Auto Close tab).



3.4 TelnetTelnet allows you to access, configure and manage devices by using CLI commands.

Follow the following steps to access, configure and manage devices by using CLI Commands.

1. Make sure that your computer is reachable to the devices on the network.

NOTE: If you have not previously configured the device IP address and do not have a DHCP server on the network, thedevice will revert to its default IP address. AP devices, MP-81XX and QB-81XX devices will default to169.254.128.132; MP.11, MP.11HS and QB.11 devices will default to 10.0.0.1; MP.16 Base Station defaults to192.168.10.1; MP.16 Subscriber Station defaults to 192.168.10.2; GX800 (A-side) will default to 10.0.0.1 andGX800 (B-side) will default to 10.0.0.2

2. Click the Telnet icon available in the tool bar. The Telnet window appears. Alternatively, Telnet is also available onthe right-click of a device.

3. Type the CLI user name and password. The default password is public. Please note that the CLI username is requiredonly for MP-81XX, QB-81XX, AP-800, AP-8000, AP-8000MR and GX800 devices. For all other devices, only CLIpassword is required.

• CLI password for Tsunami 8000 TDM IDU is admin.

• In GX800, the CLI user name and password for Administrator user is admin and secret respectively; and forUser is user and test respectively.

NOTE: • By default, the Telnet Client is disabled in Windows 7. To enable the Telnet Client, follow these steps:

1. Open Control Panel.

2. Navigate to Programs.

3. In Programs, click Turn Windows Features On or Off, and then on the list that appears, select the boxbeside Telnet Client. Finally, click Ok.



4
Discovery of Devices

• Configure Auto Discovery• Restart Auto Discovery• Manage Auto Discovery• Manual Discovery• Discover TDM IDU Link• Prerequisites for GX800• Operational Features of the Device

39


4.1 OverviewOnce you have configured ProximVision ES on the network, the next step is to discover the existing AP, TMP and Time DivisionMultiplexing (TDM) devices connected on your network and assign them to a Group to manage them by using ProximVisionES.

Tabulated below are the Proxim products along with the icons to represent these devices in ProximVision ES.

Devices IconsOrinoco® AP-700 Orinoco® AP-4000Orinoco® AP-4000MOrinoco® AP-4900MTsunami™ MP.11 5012 SUIOrinoco® AP-4000MROrinoco® AP-4000MR-LROrinoco® AP-4900MR-LROrinoco® AP-800

Orinoco® AP-8000

Orinoco® AP-8000MR

Tsunami™ MP.11 5012 SURTsunami™ MP.11 5012 CPE

Tsunami™ MP.11 5054 BSU Tsunami™ MP.11 5054 SUI

Tsunami™ MP.11-5054-R BSUTsunami™ MP.11 5054-R SUTsunami™ MP.11-5054-R-LR BSUTsunami™ MP.11-5054-R-LR SUTsunami™ QB.11-5054-RTsunami™ QB.11 5054-R-LRTsunami™ MP-8100-BSU

Tsunami™ MP-8100-SUATsunami™ MP-8150-SURTsunami™ MP-8160-BSU

Tsunami™ MP-8150-CPE-100aTsunami™ MP-8150-CPE-A100Tsunami™ MP-8150-CPE-100i

Tsunami™ MP-8160-CPE

Tsunami™ MP-8160-SUA

Tsunami™ QB-8100-EPATsunami™ QB-8150-EPRTsunami™ QB-8150-LNK-12Tsunami™ QB-8150-LNK-50



NOTE: The MeshMAX 5054W and MeshMAX 5054WM are discovered as either AP or TMP device.

Tsunami™ 8000 TDM IDU (E1)

Tsunami™ 8000 TDM IDU (T1) \

Tsunami™ MP.16 Series

Tsunami™ MP.11 HS 5054 Series• MP.11 HS 245054-BSU-R (Outdoor)• MP.11 HS 245054-SU-R• MP.11 HS 245054-SUA• MP.11 HS 245054-BSU-S (Indoor)• MP.11 HS 245054-SU-S

Tsunami™ MP.11 HS 4454Tsunami™ GX800

Undiscovered Devices



4.2 Configure Auto DiscoveryThe Configure Auto Discovery feature discovers all the Proxim devices available on the network that ProximVision ESmanages.

NOTES:• You cannot discover Tsunami 8000 TDM IDU by using Configure Auto Discovery feature. To discover the

IDU, refer to Discover TDM IDU Link.

• Before discovering GX800 device, please see Prerequisites for GX800.

To start Auto Discovery process,

1. Navigate to Discover > Configure Auto Discovery or click icon on the toolbar.

Figure 4-1 Configure Auto Discovery Submenu

2. The Auto Discovery window appears.



Figure 4-2 Auto Discovery Window

3. You can auto discover the devices by using four Filter Type options. Click the following links to auto discover devicesby using the different filter types.

a. Filter Type: Include Address Range - Subnetb. Filter Type: Include Address Range - IP Address Rangec. Filter Type: Exclude Address Range - Subnetd. Filter Type: Exclude Address Range - IP Address Range

4. Specify the required parameters, and click Discover.



4.2.1 Filter Type: Include Address Range - Subnet

Figure 4-3 Auto Discovery - SNMPv1/v2c (Include Address Range - Subnet)

5. Type the subnet range (or the first address on the network) to be scanned in the Subnet box (example, 169.0.0.0).

NOTE: Specify an IP address for the device. You must be able to ping that IP Address from your system whereProximVision ES is installed.

6. Type the Subnet Mask for the network to be scanned (example, 255.255.255.0) in the Subnet Mask box.

7. Type the port number in the Port box. ProximVision ES uses this port to communicate with the device.

NOTE: By default, ProximVision ES displays Port number as 161. Ensure that you specify the port number in which thedevice SNMP agent is listening to SNMP requests.

8. Type a value in the Timeout box. This timeout (in seconds) is the period for which ProximVision ES will wait for aresponse from a device after sending an SNMP request.

9. Type a value in the Retries box. This value represents the number of times ProximVision ES will try to poll a devicewhen it does not receive a response within the SNMP Timeout period. If ProximVision ES does not receive an SNMPresponse from the device after the specified number of retries, ProximVision ES will classify the device as “Down”.

10. Select the appropriate SNMP User Version to discover the devices.

• If you select SNMPv1/v2c, then by default the Read/Write Community boxes are set to “public”. CommunityString is used for communication between the devices.

NOTE: For GX800, the Read Community (parameter in web interface RO community) is “public” and WriteCommunity (parameter in web interface RW community) is “private”. Since, by default the applicationsets the default read/write passwords to “public”, care should be taken to change the Write password to“private”.



• If you select SNMPv3, do the following:

— Type user name in the User Name box. The user name is either admin or administrator.

— Select Auth Protocol as “SHA” from the Auth Protocol box.

— Type Auth Password in the Auth Password.

— The factory Auth Password for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XX Series devicesis public123. It is advisable to change this password and it should contain minimum of eight characters.

— The factory Auth Password for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR, AP-4900M,AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454 devices is public.It is advisable to change this password and it should contain minimum of six characters.

— Select Privacy Protocol in the Privacy Protocol box.

— Select Privacy Protocol as “AES-128” for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XXSeries devices.

— Select Privacy Protocol as “DES” for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR,AP-4900M, AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454devices.

— Type Privacy Password in the Privacy Password box.

— The factory Privacy Password for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XX Seriesdevices is public123. It is advisable to change this password and it should contain minimum of eightcharacters.

— The factory Privacy Password for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR, AP-4900M,AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454 devices is public.It is advisable to change this password and it should contain minimum of six characters.

NOTE: GX800 does not support SNMP v3.

Figure 4-4 Auto Discovery - SNMPv3 (Include Address Range - Subnet)



NOTE: SNMPv3 supports three security levels: (1) No authentication and no encryption; (2) authentication and noencryption; and (3) authentication and encryption. Currently, ProximVision ES supports only “authentication andencryption”.

4.2.2 Filter Type: Include Address Range - IP Address Range

Figure 4-5 Auto Discovery - SNMPv1/v2c (Include Address Range - IP Address Range)

1. Type the IP address range in the From (example, 169.254.128.66) and To (example, 169.254.128.200) boxes to bescanned.

NOTE: Specify a static IP address for the device. You must assign the unit a unique address that is valid on your IPsubnet. Contact your network administrator if you need assistance in selecting the IP address for the unit.

2. Type the Port number. ProximVision ES uses this port to communicate with the device.


3. Type a value in the Timeout box. This timeout (in seconds) is the period for which ProximVision ES will wait for aresponse from a device after sending an SNMP request.

4. Type a value in the Retries box. This represents the number of times ProximVision ES will try to poll a device when itdoes not receive a response within the SNMP Timeout period. If ProximVision ES does not receive an SNMP responsefrom the device after the specified number of retries, ProximVision ES will classify the device as “Down”.

5. Select the appropriate SNMP User Version to discover the devices.

• If you select SNMPv1/v2c, then by default the Read/Write Community boxes are set to “public”. CommunityString is used for communication between the devices.



NOTE: For GX800, the Read Community (parameter in web interface RO community) is “public” and WriteCommunity (parameter in web interface RW community) is “private”. Since, by default the applicationsets the default read/write passwords to “public”, care should be taken to change the Write password to“private”.

• If you select SNMPv3, do the following:


— Select Auth Protocol as “SHA” from the Auth Protocol box.

— Type Auth Password in the Auth Password.

— The factory Auth Password for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XX Series devicesis public123. It is advisable to change this password and it should contain minimum of eight characters.

— The factory Auth Password for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR, AP-4900M,AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454 devices is public.It is advisable to change this password and it should contain minimum of six characters.

— Select Privacy Protocol in the Privacy Protocol box.

— Select Privacy Protocol as “AES-128” for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XXSeries devices.

— Select Privacy Protocol as “DES” for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR,AP-4900M, AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454devices.

— Type Privacy Password in the Privacy Password box.

— The factory Privacy Password for AP800, AP8000, AP8000MR, MP 81XX Series and QB 81XX Seriesdevices is public123. It is advisable to change this password and it should contain minimum of eightcharacters.

— The factory Privacy Password for AP-700, AP4000, AP-4000M, AP-4000MR, AP-4000MR-LR, AP-4900M,AP-4900MR-LR, MP.11 Series, QB.11 Series, MP.11 HS 5054 Series and MP.11 HS 4454 devices is public.It is advisable to change this password and it should contain minimum of six characters.

NOTE: GX800 does not support SNMP v3.

Figure 4-6 Auto Discovery - SNMPv3 (Include Address Range - IP Address Range)



4.2.3 Filter Type: Exclude Address Range - Subnet1. Type the subnet range (or the first address on the network) that is to be excluded from being scanned in the Subnet

field (example, 160.0.0.0).


2. Type the Subnet Mask for the network to be excluded from being scanned (example, 255.255.255.0). The largestsubnet accepted by ProximVision ES is 255.255.0.0



Figure 4-7 Auto Discovery - (Exclude Address Range - Subnet)

4.2.4 Filter Type: Exclude Address Range - IP Address Range1. Type the IP address range in the From (example, 169.254.128.66) and To (example, 169.254.128.200) boxes that

needs to be excluded from being scanned.





NOTE: By default, ProximVision ES displays Port number as 161. Ensure that you specify the port number in which thedevice SNMP agent is listening for SNMP requests.

Figure 4-8 Auto Discovery - (Exclude Address Range - IP Address Range)

CAUTION: If you have excluded any IP address/subnet range, then that particular range will be excluded for all the AutoDiscovery process thereafter.



4.3 Restart Auto DiscoveryThe Restart Auto Discovery feature allows you to restart the Auto Discovery process.with the previously used network or IPrange.

1. Navigate to Discover > Restart Auto Discovery.

Figure 4-9 Restart Auto Discovery Submenu

2. The Auto Discovery Service window appears. Click Yes, if you want to restart the Auto Discovery process;Otherwise, click No.

Figure 4-10 Auto Discovery Service

4.4 Manage Auto DiscoveryThe Manage Auto Discovery feature allows you to manage Auto Discovery process. This feature stores all the IP Addressesand Subnets that are used to auto discover the devices available on your network. If you have excluded any IP Addresses orSubnets during the Auto Discovery process, then you need to manually rediscover those IP Addresses or Subnet to beincluded in the list.

1. Navigate to the Discover > Manage Auto Discovery.



Figure 4-11 Manage Auto Discovery Submenu

2. The Manage Auto Discovery window appears.

Figure 4-12 Manage Auto Discovery Window

The Manage Auto Discovery window captures all the auto discoveries done by the user. Each auto discovery done by theuser is displayed as a row in the Manage Auto Discovery window. Each row includes the type of auto discovery performedby the user (For example, Include Address), the start IP address (For example 169.254.128.66), and the End IP address (Forexample 169.254.128.160) for auto discovering the devices.

To delete a row, select the row that you want to delete and click Delete.

4.5 Manual DiscoveryAlthough ProximVision ES has very robust discovery capabilities, there are deployment situations which dictate manuallyadding the devices to ProximVision ES.

NOTES:• You cannot discover Tsunami 8000 TDM IDU by using Manual Discovery feature. To discover the IDU, refer to

Discover TDM IDU Link.

• Before discovering GX800 device, please see Prerequisites for GX800.



1. Navigate to Discover > Manual Discovery, or click in the toolbar, or right-click Root group in the Device Treeand then click Discover.

Figure 4-13 Manual Discovery Submenu

2. The Discover window appears.

Figure 4-14 Manual Discovery

3. Type the IP address (example, 169.254.128.66) of the device that you want to manually discover, in the DeviceAddress box.

4. Follow the same method as explained in Configure Auto Discovery to discover the device.

5. Click Discover. Note that the device is discovered and highlighted in the Device Tree.

When the devices are manually discovered, they are discovered under AP or TMP group in the Device Tree. The user has torefresh the Device Tree for devices to move to their respective groups.

To refresh the Device Tree, right-click the default group Root in the Device Tree and click Refresh Device Tree as shown inthe following screen.



Figure 4-15 Refresh Device Tree

4.6 Discover TDM IDU LinkDiscovering Tsunami 8000 TDM IDU involves discovering a link which contains the devices - Central Office (CO), Tsunami QB81XX End Point A, Customer Premises Equipment (CPE) and Tsunami QB 81XX End Point B.

To discover the link, perform the following:

1. Navigate to Discover > Discover TDM IDU Link.

Figure 4-16 Discover TDM IDU Link Submenu

2. The following Discover screen appears.



Figure 4-17 Discover the Link

3. Type a name for the link in the Link Name box.

4. Step1: The step1 includes discovering CO (IDU) and Tsunami QB 81XX End Point A (ODU). Click CO to discover thesetwo devices.

a. Click IDU to discover CO (IDU) and provide the following information.

— Enter the device IP address in the Device Address box.

— Provide the port number that ProximVision ES uses to communicate with the device in the Port box.

— Select the user version as SNMPv1/v2c.

NOTE: Tsunami 8000 TDM IDU does not support SNMP v3.

— Enter the Read Community and Write Community password in the SNMPv1/v2c box. The ReadCommunity password is “public” and the Write Community password is “gcimsap”.

NOTE: You cannot change the default SNMP v1/v2c Read and Write passwords of Tsunami 8000 TDM IDU.

b. Click ODU to discover Tsunami QB 81XX End Point A (ODU) and provide the following information.

— Enter the device IP address in the Device Address box.

— Provide the port number that ProximVision ES uses to communicate with the device in the Port box.

— Select the user version as SNMPv1/v2c or SNMP v3.

— If you select user version as SNMPv1/v2c then enter the Read Community and Write Communitypassword in the SNMPv1/v2c box. The Read Community and Write Community password is “public”.

— If you select user version as SNMP v3 then do the following:


— Select Auth Protocol as SHA from the Auth Protocol box.



— Type Auth Password in the Auth Password box. By default, the password is public123.

— Select Privacy Protocol as DES from the Privacy Protocol box.

— Type Privacy Password in the Privacy Password box. By default, the password is public123.

NOTE: It is advisable to change the Auth Password and Privacy Password. The password can contain aminimum of eight characters.

5. Step2: The step2 includes discovering CPE (IDU) and Tsunami QB 81XX End Point B (ODU). Click CPE to discover thesetwo devices. Follow the same method as explained in step 1 to discover these 2 devices.

6. Finally, click Discover Link to discover the link. The link is discovered and added to the Device Tree as shown in thefollowing screen.

Figure 4-18 Link Discovered

You can also discover an IDU by right-clicking on a CO or CPE in the Device Tree.

1. Right-click CO/CPE.



Figure 4-19 Right-Click on CO/CPE

2. Click Discover.

3. The Manual Discovery window appears. For manually discovering the device, refer to Manual Discovery.

NOTE: While discovering, the user should provide a valid IDU IP address as ProximVision ES does not validate the IPaddress of the IDU.

4.7 Prerequisites for GX800 To manage and monitor GX-800 with ProximVision ES, the following setting have to be done on the device by using webinterface:

1. Navigate to SNMP tab.

2. Select Enable SNMP parameter.

3. Set the read and read/write IP addresses that will be used to manage the device. You can set up to three readpasswords (RO Net/Mask1; RO Net/Mask2; RO Net/Mask3) and three read/write passwords (RW Net/Mask1; RWNet/Mask2; RW Net/Mask3).

For example, if ProximVision ES is installed in a system with IP address 10.0.0.100 then this IP range needs to be set in the device under the parameter RO Net/Mask as 10.0.0.0/24 and RW Net/Mask also needs to be set to 10.0.0.0/24.

For more information, please refer to the GX800 User Guide on the support site at http://support.proxim.com



4.8 Operational Features of the DeviceProximVision ES provides certain features that you can use on a particular device. Right-click a device in the Device Tree toview its features.

Figure 4-20 Operational Features of the Device

Listed below are the operational features of the device. Please note that based on the device type, these features may vary.

4.8.1 Edit

The Edit feature enables you to edit the SNMP version, Read and Write community strings, and Port of the already discovereddevice. Please note that if the credential differ, the device status may be down.

4.8.2 Ping

The Ping feature enables you to ping a particular device. It provides information, such as time delay in relay and so on.

4.8.3 Telnet

Refer to Telnet.

4.8.4 Refresh

The Refresh feature enables you to refresh a particular device.

4.8.5 Delete

The Delete feature enables you to delete a particular device.



4.8.6 Reboot

The Reboot feature enables you to reboot a particular device.

4.8.7 Web Configure

The Web Configure feature enables you to configure a device by using web interface.

NOTE: Please note that this feature is not applicable to Tsunami 8000 TDM IDU device.

4.8.8 Reset

The Reset feature enables you to reset a device configuration parameters to factory defaults.

NOTES:• ProximVision ES cannot manage the device that is reset. You need to configure the settings of the device to

manage them.

• When you reset Tsunami 8000 TDM IDU, all the configured parameters are reset except for the device IPaddress.

• Not applicable for GX800.

4.8.9 Generate Diagnostics

The Generate Diagnostics feature enables you to generate diagnostics report of a device detailing its performance andother characteristic statistics. This report serves as a means to carry out an on the spot analysis of a device in the event of itsperformance failure.



Figure 4-21 Device Diagnostic Report

Click Export, to export the diagnostic report of a device to a desired location and in the desired format (xls, txt and so on).

Click Close, to close the Diagnostics Report screen.

NOTE: This feature is not applicable to Tsunami 8000 TDM IDU device.

4.8.10 Commit

The Commit feature enables you to apply the changed device configuration parameters on a device. This feature is availableto MP-81XX, QB-81XX, AP-800, AP-8000 and AP-8000MR devices.

NOTE: In case of Tsunami 8000 TDM IDU device, the feature to commit the configured parameters on the device isApply.

4.8.11 Add SU/EP

The Add SU/EP feature enables you to add SU to a BSU or an End Point B to End Point A. To add either SU or End Point B,right-click the BSU/End Point A in the Device Tree and click Add SU/EP.

ProximVision ES prompts you to manually discover the SU/End Point B device on the network.



Figure 4-22 Discover the SU Device

Refer to Manual Discovery to manually discover a device available on the network.

Once discovered, the SU is added to the BSU or End Point B is added to End Point A in the respective group in the Device Tree.

NOTES:• Since Add SU/EP feature manually adds SU device to a BSU, and End Point B to a End Point A, you need to

refresh the Device Tree to align the devices in the respective groups.

4.8.12 SaveThe Save feature enables you to save the configured parameters of the Tsunami 8000 TDM IDU.

NOTE: This feature is applicable only to Proxim’s Tsunami 8000 TDM IDU device.

4.8.13 Enable SNMP and Disable SNMP

When SNMP Write access is enabled, you cannot access GX800 through Web Interface and Telnet.

To access GX800 through Web Interface and Telnet, click Disable SNMP.



Figure 4-23 Operational Features of GX800



5
Creating Groups

• Creating New Groups• Deleting Groups• Renaming Groups• Discover Devices under a Group• Add Devices to a User Group• Delete Devices from Groups

62

Creating Groups

5.1 OverviewDevices need to be configured to achieve optimal performance and network security. Individual configuration of each deviceis a time consuming process and prone to errors. To address this issue, ProximVision ES allows group creation andconfiguration of devices under that group. This enables to configure all the devices of a particular group at one time. Thedevices of a particular group share certain common configuration settings.

5.2 Creating New GroupsProximVision ES enables you to create a new user group under the default group - Root. Root group is the pre-defined groupunder which all the devices on the network are discovered. You can also create subgroups under the user-defined groups.

NOTE: With ProximVision ES, you can create as many different groups as desired but the hierarchy or the subgroupsunder each group is restricted up to 3 levels.

To create a new user group,

1. Browse to the default group Root in the Device Tree, right-click and select Create User Group.

Figure 5-1 Create a new User Group

2. The Create User Group window appears.

Figure 5-2 Create User Group Window

3. Type a name for the user group that you want to create, in the User Group box.


Creating Groups

4. Select the image that represents the new user group from the Select Icon box. To add an icon of your choice to theexisting list of icons, click More. The Upload Group Icon window appears.

Figure 5-3 Upload Group Icon Window

5. In the Upload Group Icon window, click Browse to select an icon of your choice from the desired location. After youselect the image icon, click Upload. On successfully uploading the image icon, a success confirmation Messagewindow appears.

NOTE: You can upload image icons of type JPG, GIF and PNG of size 16*16 pixels only.

Figure 5-4 Upload Confirmation

6. Click Create in the Create User Group window. The newly created user group can be viewed in the Device Tree.

5.2.1 User Subgroups

ProximVision ES allows you to create group hierarchy up to three levels. For example, you can create a main group, asubgroup, and a sub-subgroup as shown in the following screen.

Figure 5-5 Multi-Level User Groups


Creating Groups

5.3 Deleting GroupsTo delete an existing user group,

1. Select the user group that you want to delete from the Device Tree.

2. Right-click and click Delete.

Figure 5-6 Delete a User Group

NOTE: ProximVision ES does not allow you to delete a user group with devices grouped under it. To delete a usergroup, you have to first delete all the devices grouped under it.

To delete devices belonging to a user group, refer to Delete Devices from Groups.

5.4 Renaming GroupsTo rename an existing user group,

1. Select the user group that you want to rename from the Device Tree.

2. Right-click and click Rename.


Creating Groups

Figure 5-7 Rename a User Group

3. The Rename window appears. In the Rename window, enter the new name in the User Group box, change theimage icon to the desired one from the Select Icon box and click Rename.

Figure 5-8 Rename Window

4. You can view the changed user group name in the Device Tree.

Figure 5-9 Renamed User Group


Creating Groups

5.5 Discover Devices under a GroupProximVision ES allows you to discover a device available under the user group.

Select the user group to discover a device under it. Right-click and click Discover. For more information on how to discover adevice, refer to Manual Discovery.

Figure 5-10 Discover a Device

NOTE: With this feature, in addition to discovering devices available under the respective user groups, you can alsodiscover devices available on the network.

5.6 Add Devices to a User GroupProximVision ES enables you to add devices to a user group.

To add devices to a user group,

1. Right-click the user group to which you want to add new devices and select Add Devices to Group.

Figure 5-11 Add Devices to Group


Creating Groups

2. The Organize Devices in user groups window appears.

Figure 5-12 Organize Devices

The left pane of the Organize Devices in user groups window contains AP, TMP, Link and user-created groups.

Note that for the user subgroups, the entire path of the user group hierarchy is displayed. For example,UG1-UG2-UG3-New where UG1 represents the first level user group, UG2 represents the second level user group andUG3-New represents the third level user group (last level as grouping is limited to 3 levels only).

When you click the AP group, the corresponding AP devices are displayed; When you click the TMP group, thecorresponding TMP devices along with their SUs are displayed; When you click a Link, the corresponding CO, QB 81XXEnd Point A, CPE and QB 81XX End Point B devices are displayed.

Figure 5-13 Organize Devices (Link)

3. Select the device(s) that you want to move to the desired user group from either AP group, TMP group, Link orUser-Created groups.

a. When you select AP device, all the connected AP-Clients will also move to the desired user group.


Creating Groups

b. When you select a BSU device, all the associated SU devices are also displayed. Select the SUs that you want tomove along with the BSU to the desired user group.

c. The SU devices that are not selected, will also move to the desired user group but does not exist as part of theBSU. To move SU devices back to their respective BSU, right-click the Root group in the Device Tree and clickRefresh Device Tree.

Figure 5-14 Refresh Device Tree

d. When you select a link, all the devices belonging to that link will move to the desired user group.

4. In the Select Group box, select the user group to move the device(s) that you have selected.

5. Next, click Move.

NOTES:• A link can be moved only to the first level of the user group.

• Devices available in AP, TMP and Link can be moved to user groups but vice versa is not possible.

• While discovering a link, if Tsunami QB 81XX devices are already discovered, they will be rediscovered andadded to the link.

• You cannot move individual devices of a link to the desired User Groups.

• When you discover a BSU device, all the corresponding SU devices are also discovered. If a SU device is alreadydiscovered and placed under a different group then it moves under the respective BSU device, and isrepresented with its IP address. The SU device not discovered earlier is represented with its MAC address andonce discovered, its representation changes from MAC address to IP address.

5.7 Delete Devices from GroupsTo delete a device from the user group, right-click the device that you want to delete from the user group and click Delete.

NOTE: When you delete a device, it gets deleted from the respective user group. When the deleted device isdiscovered again, it is discovered under the respective default group.



6
Configuring Individual Device Settings
6.1 OverviewWhile most device configuration settings are managed by ProximVision ES at a group level to enable efficient changemanagement, certain settings must be managed at an individual device level. For example, devices within a group are oftencontiguous with one another and have overlapping coverage area; it would not make sense to configure RF channel settingsat a group level. Instead, channel settings are managed at an individual device level to avoid interference.

NOTE: Any changes made at individual device level will automatically override group level device settings. Ensure thatyour system is configured on the network on which all the devices are configured.

By using ProximVision ES, you can configure the following devices:

• ORiNOCO® Access Points and Mesh Series

• AP-700

• AP-4000, AP-4000M, AP-4000MR and AP-4000MR-LR

• AP-4900M and AP-4900MR-LR

• ORiNOCO® 802.11n Access Points and Mesh Series

• AP-800

• AP-8000

• AP-8000MR

• TsunamiTM MP 8100 Series

• MP-8100-BSU

• MP-8100-SUA

• MP-8150-SUR

• MP-8160-BSU

• MP-8160-SUA

• MP-8150-CPE

• MP-8150-CPE-100i

• MP-8160-CPE

• TsunamiTM QB 8100 Series

• QB-8100-EPA

• QB-8150-EPR

• QB-8150-LNK

• QB-8150-LNK-12 and QB-8150-LNK-50

• TsunamiTM MP.11 Series

• MP.11 5012 SUI, SUR and CPE

• MP.11 5054 BSU and SUI

• MP.11 5054-R BSU and SU

• MP.11 5054-R-LR BSU and SU

• TsunamiTM QB.11 Series

• QB.11 5054-R

70


• QB.11 5054-R-LR

• Tsunami™ MP.16 Series

• MP.16 3500

• Tsunami™ MP.11 HS 5054 Series

• MP.11 HS 245054-BSU-R (Outdoor)

• MP.11 HS 245054-SU-R

• MP.11 HS 245054-SUA

• MP.11 HS 245054-BSU-S (Indoor)

• MP.11 HS 245054-SU-S

• Tsunami™ MP.11 HS 4454

• MeshMAX 5054 Series

• MeshMAX 5054W and 5054WM

• Tsunami™ 8000 TDM IDU

• QB-IDU-4E-LNK

• QB-IDU-4T-LNK

• Tsunami™ GX800

The following table lists the devices and their features that can be configured by using ProximVision ES.

# Device (s) Configurable Features1. AP-700

AP-4000• General

• Download

• Upload

• IP Configuration

• DHCP Server

• VLAN

• Op Mode (For AP-700 only)

• Basic Mesh (For AP-4000 only)

• Management Services

• Transmit Power Back-Off (For AP-4000 only)

• Wireless A

• Wireless B (For AP-4000 only)

• RADIUS Profile

• MAC Access

• SSID/VLAN Configuration – Wireless A

• SSID/VLAN Configuration – Wireless B (For AP-4000 only)

• Security Profile

• Trap Groups

• Mgmt Passwords



2. AP-800/AP-8000/AP-8000MR

• System Information

• Download

• Upload

• Network IP Configuration

• Ethernet Interface Properties

• VLAN

• VLAN Ethernet1 Configuration

• VLAN Ethernet2 Configuration (For AP-8000MR only)


• SNMP

• Syslog

• Management Access Control Table

• Interface -1 VAP (For AP Mode Only)

• Wireless Interface 1 - MESH (For Mesh Portal and Mesh Point Only)

• Interface 1 - Basic Properties

• Interface 1 - Properties

• Interface 1 - 11n Properties

• Interface 2 - VAP (For AP-8000 and AP-8000MR Only)

• Interface 2 - Basic Properties (For AP-8000 and AP-8000MR Only)

• Interface-2 Properties (For AP-8000 and AP-8000MR Only)

• Interface-2 11n Properties (For AP-8000 and AP-8000MR Only)

• RADIUS Server Profile

• MAC Access Control

• Wireless Security Configuration

• QoS STA EDCA Table

• QoS AP EDCA Table

• 802.1 D to IP DSCP Mapping Table

• 802.1 D to 802.1p Mapping Table

• QoS Profile

• QoS Policy

• Global Filtering

• Protocol Filter

• Static MAC Address Filter

• Advanced Filtering

• TCP/UDP Port Filter

• Storm Threshold Filter

• DHCP Server Interface

• DHCP Pool

# Device (s) Configurable Features



3. MP.11QB.11

• General

• Download

• Upload

• Downgrade

• DHCP Server

• IP configuration


• Wireless

• Security Encryption

• Security RADIUS Auth (For BSU/End Point A only)

• Security Mac Auth (For BSU/End Point A only)

• Trap Groups

• Mgmt Passwords

• DNS Client

• SNTP

• Syslog

• VLAN BSU (For BSU only)

• VLAN SU4. MP.11 HS 5054 Series

MP.11 HS 4454• General

• Download

• Upload

• Downgrade

• DHCP Server

• IP Configuration


• Wireless


• Easy Setup

• Trap Groups

• Mgmt Passwords

• DNS Client

• Security RADIUS Auth (For BSU Only)

• Security MAC Auth (For BSU Only)

• VLAN BSU (For BSU Only)

• VLAN SU5. Tsunami 8000 TDM IDU • System Information

• Device Software Upgrade

• Channel Configuration




6. MP-8100-BSUMP-8160-BSU


• Download

• Upgrade Configuration

• Upload


• VLAN

• VLAN Ethernet1 and Ethernet2 Configuration


• SNMP

• Syslog


• Licensed Features

• WORP

• Interface-1 Properties

• MIMO Properties

• DFS (Not applicable to MP-8160-BSU)

• Basic and Advanced DDRS

• RADIUS Server Profile




• Protocol Filter



• TCP/UDP Port filter


• WORP Intra Cell Blocking

• WORP Intra Cell Group

• WORP Intra Cell MAC

• QoS SU Entries

• QoS Class Details

• QoS Service Flow Entries

• QoS PIR Entries

• QoS PIR MAC Entries

• QoS PIR IP Entries

• QoS PIR Port Entries

• Network Configuration

• Ethernet IP Configuration

• Wireless IP Configuration (In Routing mode only)

• Static Route Table (In Routing mode only)

• RIP (In Routing mode only)





• DHCP Pool

• DHCP Relay Server (In Routing mode only)

• IGMP Snooping




7. QB-8100-EPA (EndPoint A)QB-8100-EPA (EndPoint B)QB-8150-EPR (EndPoint A)QB-8150-EPR (EndPoint B)QB-8150-LNK-12/50 Endpoint AQB-8150-LNK-12/50 Endpoint B


• Download


• Upload


• Advanced Ethernet Interface Properties

• VLAN

• VLAN Ethernet1 and Ethernet2 Configuration (Ethernet2 not applicable to QB-8150-LNK-12/50)


• SNMP

• Syslog



• WORP


• MIMO Properties

• DFS


• RADIUS Server Profile (Not Applicable to EndPoint B)

• MAC Access Control (Not Applicable to EndPoint B)



• Protocol Filter





• WORP Intra Cell Blocking (Not Applicable to EndPoint B)

• WORP Intra Cell Group (Not Applicable to EndPoint B)

• WORP Intra Cell MAC (Not Applicable to EndPoint B)

• QoS End Point B Entries (Not Applicable to EndPoint B)

• QoS Class Details (Not Applicable to EndPoint B)

• QoS Service Flow Entries (Not Applicable to EndPoint B)

• QoS PIR Entries (Not Applicable to EndPoint B)

• QoS PIR MAC Entries (Not Applicable to EndPoint B)

• QoS PIR IP Entries (Not Applicable to EndPoint B)

• QoS PIR Port Entries (Not Applicable to EndPoint B)









• NAT (In Routing mode only; Not applicable to EndPoint A)


• DHCP Pool


• IGMP Snooping8. MP-8100-SUA

MP-8150-SURMP-8160-SUA


• Download


• Upload


• VLAN

• VLAN Ethernet1 and Ethernet2 Configuration


• SNMP

• Syslog



• WORP


• MIMO Properties

• DFS

• Basic DDRS

• Advanced DDRS



• Protocol Filter










• NAT (In Routing mode only)


• DHCP Pool


• IGMP Snooping




9. MP-8150-CPEMP-8150-CPE-100iMP-8160-CPE


• Download


• Upload


• VLAN



• SNMP

• Syslog



• WORP


• MIMO Properties

• DFS




• Protocol Filter










• NAT (In Routing mode only)


• DHCP Pool


• IGMP Snooping




For information on how to configure these devices, refer to the respective Installation and Management Guide available athttp://support.proxim.com.

10. GX800 • General

• Revision

• Description

• Maintenance

• Radio

• Alarm

• Ports

• ODU Details

• IDU Details

• IP Settings11. MP.16 • General

• Download

• Upload

• Mgmt Passwords (For BS only)

• Syslog

• Basic MAC (For BS only)

• Advanced MAC (For BS only)

• Radio

• Downlink Burst Profile (For BS only)

• Uplink Burst Profile (For BS only)

• SS List (For BS only)

• Basic

• VLAN (For BS only)

• Bridging (For BS only)




7
Monitoring Devices

• Overview• Performance Monitoring through Graphs• Graph Properties• AP-700 Device Monitoring• AP-4000 Device Monitoring• AP-800, AP-8000 and AP-8000MR Device Monitoring• MP.11 and QB.11 Device Monitoring• MP.16 Device Monitoring• MP.11 HS 5054 Series and MP.11 HS 4454 Device Monitoring• GX800 Device Monitoring• MP-8100 Series and QB-8100 Series Device Monitoring

80

Monitoring Devices

7.1 OverviewProximVision ES provides the platform to monitor and administer the health of Proxim devices on the network.

ProximVision ES supports two types of graphs to monitor device performance:

1. SNR Graphs: SNR data will be stored for 24 hours for the selected device. After every 24 hours, the graph getsrefreshed.

2. Current Statistics Graphs: Current Statistics data will be stored for one hour only. After every one hour, the graphgets refreshed.

7.2 Performance Monitoring through GraphsTo view the performance graph of a device:

1. Select the device by navigating through the Device Tree, and click Plot Stats as shown in the following figure.

Figure 7-1 Plot Stats

2. The window as shown in Figure 7-2 appears. This window contains two menu items: SNR Plot and Current StatisticsPlot.


Monitoring Devices

7.2.1 SNR Graphs

To generate SNR graphs, click SNR Plot tab.

Figure 7-2 SNR Plot

In the SNR Plot Graph window,

a. Select the device(s) to generate the performance graph.

NOTES:• If you are monitoring the performance of a BSU device then all its SU devices are displayed.

• If you are monitoring the performance of a SU device then its BSU device is displayed.

• If you are monitoring the performance of a QB device then either End Point A or End Point B is displayed.

b. Set the polling interval for the graph. To set the polling interval, refer to Periodic Performance.

c. Click Generate Plot to generate the graph. The graph for the selected device(s) is plotted as shown in Figure 7-3.

d. Click Stop Plot to stop plotting the performance graph.


Monitoring Devices

Figure 7-3 SNR Stop Plot

To refresh the graph, click Refresh Graph.

To delete the graph data, click Delete Graph Data.

To clear the graph data, click Clear.

7.2.2 Current Statistics Graph

To generate Current Statistics graph, click the Current Statistics Plot tab.


Monitoring Devices

Figure 7-4 Current Statistics Plot

In the Current Statistics Plot Graph window,

a. Select the device(s) to generate the performance graph.

NOTES:• If you are monitoring the performance of a BSU device then all its SU devices are displayed.

• If you are monitoring the performance of a SU device then its BSU device is displayed.

• If you are monitoring the performance of a QB device then either End Point A or End Point B is displayed.

b. Select parameters for the device from the Variable Name drop-down box.

c. Specify the polling interval (say 5 seconds) in the Interval (In Seconds) box. The performance of a device ismonitored in the duration of the set Polling interval.

d. Click Generate Graph. The graph for the selected device(s) is plotted as shown in Figure 7-5.

e. Click Stop Plot to stop plotting the performance graph for the device(s).


Monitoring Devices

Figure 7-5 Current Statistics Stop Plot

To clear the graph data, click Clear.

7.3 Graph PropertiesWhen you right-click on the graph, a window with the following menus appears. These options can be used to change thelook and feel of the graph.

a. Properties - Allows you to set the graph properties such as graph title along with its font style, size and color; plot axis and so on.

b. Save as - Allows you to save the graph to a desired location.

c. Print - Allows you to take a printout of the graph.

d. Zoom In & Zoom Out - Allows you to zoom in and zoom out the graphs.

e. Auto Range - Allows you to select the suitable range for X and Y axis for the graph.


Monitoring Devices

Figure 7-6 Graph Right-click Menu

NOTE: The performance graphs are supported only by AP-800/8000/8000MR, MP-81X and QB-81XX devices.

7.4 AP-700 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the AP-700 device.

• ICMP Received

• ICMP Transmitted

• Ethernet Interface Statistics

• Wireless Statistics

• Station Statistics

For more information on how to monitor this device, refer to the respective Installation and Management Guide athttp://support.proxim.com.

7.5 AP-4000 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the AP-4000 device.

• ICMP Received



• Wireless-Slot A Statistics

• Wireless-Slot B Statistics



Monitoring Devices

For more information on how to monitor this device, refer to the respective Installation and Management Guide athttp://support.proxim.com.

7.6 AP-800, AP-8000 and AP-8000MR Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the AP-800, AP-8000 and AP-8000MR devices.

• Wireless Interface-1 Statistics

• Wireless Interface-2 Statistics (For AP-8000 and AP-8000MR devices only)


• ICMP Statistics

• IP ARP Table

• RADIUS Client Authentication Status

• RADIUS Client Accounting Statistics

• Mesh Neighbour Statistics

• Sys Log

• System Inventory Management Table

• Event Log

• SNTP

• Ethernet 1 Statistics

• Ethernet 2 Statistics (For AP-8000MR only)

• Bridge Statistics

For more information on how to monitor these devices, refer to their respective Installation and Management Guide at http://support.proxim.com

7.7 MP.11 and QB.11 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the MP.11and QB.11devices.

• ICMP Received





• Spectrum Analyser

For more information on how to monitor these devices, refer to their respective Installation and Management Guide at http://support.proxim.com.

7.8 MP.16 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the MP.16 device.


• MAC Statistics

• SF Statistics List (For BS only)

For more information on how to monitor this device, refer to the respective Installation and Management Guide at http://support.proxim.com.


Monitoring Devices

7.9 MP.11 HS 5054 Series and MP.11 HS 4454 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the MP.11 HS devices.

• ICMP Received




• Station Stations

For more information on how to monitor these devices, refer to their respective Installation and Management Guide at http://support.proxim.com.

7.10 GX800 Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the GX800 device.


• Mux

• LAN Counters

• Ber

• LAN Details

For more information on how to monitor this device, refer to the respective Installation and Management Guide at http://support.proxim.com.

7.11 MP-8100 Series and QB-8100 Series Device MonitoringBy using ProximVision ES, you can monitor the following statistics of the devices

a. MP-8100-BSU; MP-8160-BSU; QB-8100-EPA (Endpoint A); QB-8150-EPR (Endpoint A); QB-8150-LNK-12/50 (Endpoint A)

• RADIUS Client Authentication Status

• SU Link Statistics (For MP devices only)

• End Point B Link Statistics (For QB devices only)

• IGMP Ethernet1 Statistics

• IGMP Ethernet2 Statistics (Not applicable to QB-8150-LNK-12/50 devices)

• IGMP Wireless1 Statistics

• IGMP Router Port

• WORP General Statistics

• Temperature


• Event Log

• SNTP

• Ethernet1 Statistics

• Ethernet2 Statistics (Not applicable to QB-8150-LNK-12/50 devices)

• Bridge Statistics (In Bridge mode only)

• QoS Summary



Monitoring Devices

• ICMP Statistics

• IP ARP Table

b. MP-8100-SUA; MP-8150-SUR; MP-8160-SUA; QB-8100-EPA (Endpoint B); QB-8150-EPR (Endpoint B); QB-8150-LNK-12/50 (Endpoint B)


• IGMP Ethernet2 Statistics (Not applicable to QB-8150-LNK-12/50)




• BSU Link Statistics (For MP devices only)

• End Point A Link Statistics (For QB devices only)

• WORP Site Survey

• Temperature


• Event Log

• SNTP


• Ethernet2 Statistics (Not applicable to QB-8150-LNK-12/50)



• ICMP Statistics

• IP ARP Table

c. MP-8150-CPE, MP-8150-CPE-100i; MP-8160-CPE devices





• BSU Link Statistics

• WORP Site Survey


• Event Log

• SNTP




• ICMP Statistics

• IP ARP Table

For more information on how to monitor these devices, refer to their respective Installation and Management Guides athttp://support.proxim.com.



8
Configuring Devices in Bulk

• Overview• Bulk Operations• Bulk Configurable Features

90


8.1 OverviewConfiguring the devices to achieve optimal performance and network security is a complex, time-consuming process and isprone to errors. ProximVision ES addresses this problem by automating the process of device configuration and complianceauditing.

ProximVision ES allows certain settings to be managed efficiently at a “Group Level” while others are managed at an“Individual Device Level”. ProximVision ES defines a Group with similar devices on the wireless LAN, ranging from one deviceto hundreds of devices, that share certain common configuration settings.

Typical Group Configuration variables include basic settings (SSID, SNMP, Polling Interval and so on), security settings (VLANs,WEP, 802.1x and so on), and some radio settings (Data Settings, Data Rates, Fragmentation Threshold, RTS Threshold, DTIM,Preamble and so on).

8.2 Bulk OperationsBulk Operations feature enables you to configure devices in bulk rather than individually. While configuring devices in bulk,you need to ensure that all the devices are of same type. For example, you cannot perform Bulk Operations on an AP and ona TMP device.

To configure devices in Bulk,

1. Click Configure > Bulk Operations or click in the tool bar.

Figure 8-1 Bulk Operations Submenu

2. Alternatively, you can also access Bulk Operations feature by right-clicking default Root group in the Device Tree.



Figure 8-2 Bulk Operations - Root Group

3. The Group Device Configurations window appears.

Figure 8-3 Bulk Operations Window

4. Select all the devices whose parameters you wish to configure in bulk from the Device Tree. Remember that you needto select devices of same type, that is either AP or TMP devices. If you select devices of different type, ProximVisiondisplays an error message saying Selected devices are not of the same type.

NOTE: To select multiple devices, press Ctrl and select devices in the Device Tree.



5. The bulk device parameters under a particular tab are displayed in the right-pane of the Bulk Operations window.Under the respective tabs, update the device parameters as desired. Note that the parameters that are updated arehighlighted in bold.

NOTE: By default, the Set button is disabled. It gets enabled only when you update the device parameters.

6. Configuring this way, allows the user to configure/apply only the updated device parameters under a tab to thedevices that are selected in bulk. To configure/apply all the parameters (that is both updated and non-updatedparameters) under a tab to the devices selected in bulk, click Operations menu> Apply All Parameters in the BulkOperations window. The Apply Configuration window appears.

Figure 8-4 Apply All Parameters

7. Select Apply Configuration checkbox in the Apply Configuration window and click Ok.

NOTE: The Apply All Parameters feature is not applicable to the RADIUS and Security Profile tabs.

8. After updating the device parameters under the respective tabs, click Set to apply the updated parameters to theselected devices.

9. If you wish to restore the device parameters, click Clear.

10. For the changes to take effect, perform a commit and reboot operation on AP-800, AP-8000, AP-8000MR, MP-81XXand QB-81XX devices.

The Operations menu in the Bulk Operations window contains two more menu items:

1. Refresh Switches: This feature refreshes all the devices that are available in the Device Tree of the Bulk Operationswindow.

2. Exit: This submenu allows you to close the Bulk Operations window. Select Yes if you want to close Bulk Operationswindow, otherwise click No.

Figure 8-5 Bulk Operations - Exit Window



8.2.1 An Example for Bulk Operations

Consider a case where you want to change the WORP properties of two similar devices (with IP addresses 169.254.128.178and 169.254.128.132 respectively) by using Bulk Operations. To commit the changes and for the changes to take effect, youalso want to commit and reboot the device by using bulk operations. Note that individually changing the WORP propertiesand then performing a commit and reboot operation on each device is a time consuming process.

Consider the following steps to perform the bulk operations.

1. Select the devices (with IP addresses 169.254.128.178 and 169.254.128.132 respectively), from the left pane of theBulk Operations window. To select multiple devices, use Ctrl key.

2. Click the WORP tab in the right pane of the Bulk Operations window. The WORP parameters are displayed as shownin the following screen.

Figure 8-6 Select Similar Devices in Bulk

3. Lets say you want to change the Network Name of the devices selected in bulk. Type in the new network name (saypublic 123) in the Network Name box.



Figure 8-7 Change Network Name

4. Lets say you want to apply the unchanged parameters (that is Input Bandwidth Limit, Output Bandwidth Limitand Data Streams) also to be applied to the devices selected in bulk. To do so, navigate to Operations menu andselect Apply All Parameters. In the Apply Configuration window, select the Apply Configuration parameter andclick ok. Doing so will apply the changes as well as unchanged parameters to all the selected devices.

Figure 8-8 Select Apply Configuration Parameter

5. To save the changes, click Set in the Bulk Operations window. A Status Dialog window displays the status of yourlast operation. Click Exit, to close the window.



Figure 8-9 Status Dialog

6. In the Bulk Operations window, click Commit and Reboot for the changes to take effect on all the selected devices.

NOTE: The Bulk Operations feature is not applicable to Tsunami 8000 TDM IDU, GX800 and MP.16 devices.



8.3 Bulk Configurable FeaturesThe following table lists the devices and their features that can be configured by using Bulk Operations.

# Device(s) Bulk Configurable Features1. AP-700

AP-4000• Download/Upgrade

• Upload



• Wireless - A

• Network Name (SSID)

• Enable Auto Channel Select

• Frequency Channel

• Transmit Rate

• Wireless - B (For AP-4000 only)


• Enable Auto Channel Select


• Transmit Rate

• Management VLAN

• SSID / VLAN Configuration - Wireless A

• SSID / VLAN Configuration - Wireless B (For AP-4000 only)

• RADIUS Profile


• MAC Access

• Reboot2. MP.11 Series

QB.11 Series• Download/Upgrade

• Upload

• Downgrade

• General

• SystemCountryCode

• SystemMode

• Wireless

• Interface type



• Scanning Across Bandwidth

• Channel Bandwidth

• Network Secret


• Reboot



3. AP-800AP-8000AP-8000MR


• Download/Upgrade

• Upload



• Interface -1 VAP (For AP only)

• Wireless Interface -1 Mesh (For Mesh Portal and Mesh Point only)

• Interface -1 Basic Properties

• Interface - 1 Properties

• Interface - 1 11n Properties

• Interface -2 VAP (For AP-8000 and AP-8000MR only)

• Interface -2 Basic Properties (For AP-8000 and AP-8000MR only)

• Interface - 2 Properties (For AP-8000 and AP-8000MR only)

• Interface - 2 11n Properties (For AP-8000 and AP-8000MR only)

• VLAN


• VLAN Ethernet2 Configuration (For AP-8000MR only)

• RADIUS Profile



• SNMP Trap Host Configuration

• Commit

• Reboot4. MP.11 Series

QB.11 Series• Download/Upgrade

• Upload

• Downgrade

• General

• SystemCountryCode

• SystemMode

• Wireless

• Interface type



• Scanning Across Bandwidth

• Channel Bandwidth

• Network Secret


• Reboot

# Device(s) Bulk Configurable Features



5. MP-8100-BSUMP-8160-BSUQB-8100-EPA (Endpoint A)QB-8150-EPR (Endpoint A)QB-8150-LNK-12/50 (Endpoint A)


• Upload




• WORP

• Basic DDRS

• VLAN


• VLAN Ethernet2 Configuration (Not applicable to QB-8150-LNK-12/50)

• RADIUS Profile




• Commit

• Reboot6. MP-8100-SUA

MP-8150-SURMP-8160-SUAQB-8100-EPA (Endpoint B)QB-8150-EPR (Endpoint B)QB-8150-LNK-12/50 (Endpoint B)


• Upload




• WORP

• Basic DDRS

• VLAN


• VLAN Ethernet2 Configuration (Not applicable to QB-8150-LNK-12/50)



• Commit

• Reboot




7. MP-8150-CPEMP-8150-CPE-100iMP-8160-CPE


• Upload




• WORP

• Basic DDRS

• VLAN




• Commit

• Reboot8. MP.11 HS 5054 Series

MP.11 HS 4454• Download/Upgrade

• Upload



• Downgrade

• General

• Wireless


• Reboot




9
Network Mapping of the Devices
This chapter contains the following information:

• Overview• Map Modes• Dynamic Map Mode• Static Map Mode• Map Data• Device Data• Device Placement on Dynamic Map at configured GPS Co-ordinates

101


9.1 OverviewIt is important to survey the site before initializing the process for the deployment of wireless devices in that region. Needlessto say, going to the physical site for feasibility of device installation may cost the installers. To avoid this, network mapping ofthe devices stands as a strong supportive pillar to contemplate the feasibility of installation for different locations.

You can contemplate and survey the device installation by using the maps. This feature gives immense support and ease forthe installers to survey the installation sites sitting at a remote single location by using ProximVision ES map modes.

9.1.1 Scope

You can plan your Proxim devices for installation by using this map functionality from any location in the world. An importantadvantage is that at the street level of a location, the devices can be mapped with ease. You can locate with the longitudeand latitude of the respective places.

9.2 Map ModesProximVision ES supports two types of Map Modes, namely,

1. Dynamic Map Mode - This Map Mode enables the user to connect to the real-time maps (that is Google maps) andview the Proxim devices on the map, which are already discovered by using ProximVision ES.

2. Static Map Mode - This Map Mode allows the user to load static maps and view the Proxim devices on the map,which are already discovered by using ProximVision ES.

9.3 Dynamic Map ModeTo access Dynamic Map Mode, navigate to Mode > Dynamic Map Mode.

Figure 9-1 Dynamic Map Mode Submenu

Or click icon on the toolbar. The Map Mode Selection window appears.



Figure 9-2 Dynamic Map Mode Selection Window

Select Dynamic Map Mode from the Map Mode Selection window and click OK.

NOTE: If you want to use the Dynamic Map mode functionality in ProximVision ES, Internet facility should be available.

9.3.1 Configure a Location in Dynamic Map Mode

The following Dynamic Map Locations window appears. This window enables you to add, edit or delete a map location. Italso allows the user to view the map for the desired location along with the discovered devices.

Figure 9-3 Add Location in Dynamic Mode

9.3.1.1 Add a Location

To add a location,

1. In the Add Location pane of the Dynamic Map Locations window,

a. Enter a name for the location in the Location field.

b. Enter the latitude and longitude values in the Latitude and longitude boxes manually, or click Locate from Mapicon to select the latitude and longitude automatically from the map. A new window appears as shown below.



.

Figure 9-4 Longitude and Latitude Selection

c. Point the cursor to the desired location and double click on it. The longitude and latitudes of that location areautomatically loaded.

NOTE: To view and work with the devices on the map, provide correct latitude and longitude values.

d. Select Set as Current Location checkbox to set this location as default. By using this option, you can set a defaultlocation so that you need not select a location every time you start the Dynamic Map Mode.

NOTE: When you set a location as the current location, the map for that location will be automatically displayed along with the devices when you access Dynamic Map Mode for the next time.

e. Click Save Location to save the location.

2. Click Close to close the Dynamic Map Locations window.

9.3.1.2 Edit a Location

To edit a location,

1. Select a location from the Location drop-down box of the Dynamic Map Locations window and click Edit.

2. In the Edit Location pane of the Dynamic Map Locations window,

a. Change the Latitude and Longitude values either manually, or click Locate from Map icon to select the latitudeand longitude automatically from the map.

b. Either select or clear the Set as current location checkbox.

c. Click Save Location to save the changes done to a location.



Figure 9-5 Dynamic - Edit Location

9.3.1.3 Delete a Location

To delete a location,

1. Select a location from the Location drop-down box of the Dynamic Map Locations window and click Delete.

Figure 9-6 Dynamic - Delete a Location

2. A confirmation window to delete a location is displayed as shown below.



Figure 9-7 Dynamic Delete Location - Confirmation Window

3. Click Yes to delete a location else click No.

NOTE: We recommend you to delete a dynamic map location only when multiple dynamic map locations are saved inProximVision ES.

9.3.1.4 View a Dynamic Location Map

To view a dynamic location map,

1. Select a location from the Location drop-down box of the Dynamic Map Locations window and click Show onMap.

2. A location map with all the Proxim devices are displayed with their link quality as shown in the following screen. Thedevices displayed can be dragged from one place to another for installation.

Figure 9-8 Dynamic - Location Map



Click Refresh to refresh the map data.

NOTE: The mesh topology gets refreshed depending on the set polling interval.

9.3.2 Change Dynamic Map Location

When you are currently in the Dynamic Map Mode, you cannot add, edit, delete or connect to a dynamic map location fromMode > Dynamic Map Mode, or from the icon.

To add, edit, delete or connect to a dynamic map location, navigate to Configure > Change Map Locations > DynamicMap. Follow the same method to add, edit, delete or view a dynamic map location as explained earlier.

NOTE: To change Dynamic Map Location, the ProximVision ES application should be set in Dynamic Map Mode. To setthe Dynamic Map Mode, select Dynamic Map Mode by navigating to Mode > Dynamic Map Mode or from the

icon. If not an error message is displayed as shown in the following screen.

Figure 9-9 Change Dynamic Map Location - Error Message

9.4 Static Map ModeTo access Static Map Mode, navigate to Mode > Static Map Mode.

Figure 9-10 Static Map Mode Submenu

Or Click icon on the toolbar. The Map Mode Selection window appears.



Figure 9-11 Static Map Mode Selection Window

Select Static Map Mode from the Map Mode Selection window and click OK.

9.4.1 Configure a Location in Static Mode

This window enables you to add, edit and delete a static map location. It also allows the user to connect and view the Proximdevices already discovered on the static maps.

Figure 9-12 Add Location in Static Mode

9.4.1.1 Add a Location

To add a location,

1. In the Add Location pane of the Static Map Locations window,

a. Enter a name for the location in the Name box.

b. Click Browse to upload a static map for the location. The following window is displayed.



Figure 9-13 Browse Static Maps

Select a map image for the desired location and click Open. You can only upload map images of jpg type.

NOTE: If you are trying to upload a map of size less than 1024*768 dimension, an error message is displayed as shownin the following screen.

Figure 9-14 Static Map - Upload Error Message

c. Click Upload.

d. Select Set as Current Location checkbox to set this location as default. By using this option, you can set a defaultlocation so that you need not select a location every time you start the Static Map Mode.

NOTE: When you set a location as the current location, the map for that location will be automatically displayed whenyou access Static Map Mode for the next time.

e. Click Save Location to save the location.

2. Click Close to close the Static Map Locations window.



9.4.1.2 Change an existing Location Image

Figure 9-15 Static - Edit Location

To change an existing location image,

1. Select a location from the Name drop-down box of the Static Map Locations window and click Edit.

2. In the Edit Location pane of the Static Map Locations window,

a. Click Browse to upload a new map image for the location. After selecting the map image, click Upload.

b. Either select or clear the Set as current location checkbox.

c. Click Save Location to save the changes. A window appears which confirms whether to overwrite the new mapimage with the existing one. Click Yes to overwrite the map image else click No.

Figure 9-16 Static Maps - Edit Confirmation

9.4.1.3 Delete a Location

To delete a location,

1. Select a location from the Name drop-down box of the Static Map Locations window and click Delete.



Figure 9-17 Static - Delete a Location

2. A confirmation window to delete a location is displayed as shown in the following screen.

Figure 9-18 Static Delete Location - Confirmation Window

3. Click Yes to delete a location else click No.

NOTES:• You cannot delete a static map which is in use.

• You can delete a static map only when you have stored multiple static maps in ProximVision ES.

9.4.1.4 Edit an Image using Image Editor

The Static Map functionality of ProximVision ES, provides you the option to edit an uploaded static image by using ImageEditor programs like Microsoft Paint, Adobe Photoshop or any other image editing applications.

Before editing the static image, you will have to set the Image Editor. Follow these steps to set the Image Editor.



Figure 9-19 Image Editor

1. Navigate to Tools > Settings > Image Editor. The Configure Image Editor screen appears.

Figure 9-20 Set Image Editor

2. Click Browse to select the path for the desired Image Editor. On selecting the path, a message is displayed, whichconfirms that the Image Editor is configured.

Figure 9-21 Configured Message

After setting the Image Editor, follow these steps to edit the static image.

1. Click Edit under Preview in the Static Map Locations screen.

2. The selected Image Editor opens with the static image for editing. Edit and save the image in the Image Editor.

3. To view the updated preview image, click .



Figure 9-22 Image Editor with Static Image for Editing

9.4.1.5 Connect to a Static Location Map

To connect to a static location map,

1. Select a location name from the Name drop-down box of the Static Map Locations window and click Connect.

2. A static location map with all the Proxim devices are displayed with their link quality as shown in the following screen.The devices displayed can be dragged from one place to another for installation.



Figure 9-23 Static Location Map

Click Refresh to refresh the map data.

NOTE: The mesh topology gets refreshed depending on the set polling interval.

9.4.1.6 Change Static Map Location

When you are currently in static map mode, you cannot add, edit, delete or connect to a static map location from Modemenu > Static Map Mode, or from the icon.

To add, edit, delete or connect to a static map location, navigate to Configure > Change Map Location > Static Map.Follow the same method to add, edit, delete or connect to a static map location as explained earlier.

NOTE: To change the Static Map Location, ProximVision ES application should be set in Static Map Mode. To set theStatic Map Mode, select Static Map Mode by navigating to Mode > Static Map Mode or from the icon. Ifnot an error message is displayed as shown in the following screen.



Figure 9-24 Change Static Map Location

9.5 Map DataFollowing are the map specific parameters displayed on the right-click of a map.

Figure 9-25 Map Parameters

• Map Legend: This parameter displays the link quality (Signal Strength) in different color grids as shown in Figure 9-26.Each color maps to an SNR value of the device and displays the specific limit of values on the map. The SNR value decidesthe quality of the wireless link of the devices.

Figure 9-26 Link Quality of the Devices

• Map Label: This parameter displays the following details of the devices on the map.

– IP address: This displays the IP Address of a device.

– Name: This displays the name of a device.

– MAC Address: This displays the MAC Address of a device.

• Lock Nodes:

– Lock All: This parameters locks all the devices on the map. When enabled, you cannot drag and drop a device toanother location on the map.

This parameter is not device specific. To lock a device individually, right-click the device and click Lock.

– Unlock All: This parameter unlocks all the devices and you can move the devices easily on the map. To unlock a deviceindividually, right-click the device and click Locked.

• Show Group:

– All: Displays all the group devices.



– Existing Groups: Displays devices specific to the selected group.

• Channel Map: This parameter maps the channel number of the devices based on the link colors. Same channel devicesare linked up by using the same color.

Figure 9-27 Channel Map

Figure 9-28 Channel Map

To customize the channel colors, right-click the channel link and select the required color from the Pick a Channel Colorwindow.



Figure 9-29 Pick a Channel Color

NOTE: The undiscovered devices will not show any link with the devices on the map.

• Map Caching: Click Map Caching to download the maps into the ProximVision ES application, which is used to view themap when internet is DOWN. Map Caching can be enabled or disabled by clicking Map Caching > Enable/Disable. Toclean all the downloaded maps in the Map Cache, click Clean.

NOTES:• Cached content is deleted after every 30 days or when the cache folder size exceeds 100 Mbps

• Map Caching feature is not applicable in Static Maps

• Save Map Data: Click this parameter to save the geological positions of all the devices located on the map.

Consider a case where you have saved the device positions on the map. After saving the device positions on the map, youhave applied few more changes to the device positions on the map. Lets say, without saving the newly applied devicepositions, you switch to another map mode. In such a scenario, the ProximVision ES application before switching toanother map mode checks if the recently changed device positions are to be saved or not. Click Yes, if you wish to savethe changes else click No.

• Clear Map Data: Click this parameter to move all the devices that are saved on the map, from Static Map to DynamicMap and vice versa.

Follow the following steps to move all devices from one map mode to another. Let us say that you want to move all thedevices from Dynamic Map to Static Map.

1. Right-click on the Dynamic Map. A map menu is displayed as shown in the following screen.



Figure 9-30 Right-Click on the Dynamic Map

2. If you have not saved the device locations in the Dynamic Map, select Save Map Data to save the device positions.

3. Next, select Clear Map Data from the map menu.

4. Select Static Map Mode by navigating to Mode > Static Map Mode, or from the icon.

Figure 9-31 Select Static Map Mode

5. The following screen appears. Click No, to clear the device positions on the Dynamic Map.

NOTE: If you select Yes, the devices will be saved in the Dynamic Map and will not move to Static Map.

Figure 9-32 Save Device Positions



6. The devices will move from Dynamic Map to Static Map, and the Static Map appears with devices displayed as shownin the following screen. Save the locations on the map as desired.

Figure 9-33 Move Devices - Save Device Positions

NOTE: The Administrator user has access to all the map specific parameters as discussed above. Except for MapCaching, Save Map Data and Clear Map Data, the Monitor user has access to all the other map specific parameters.

9.6 Device DataFollowing are the device specific parameters that you can access on the right-click of the device.

Figure 9-34 Device Data

• Manage Device: Click this parameter to switch to the Configuration mode to manage/configure the device.

• Lock: Click this parameter to lock a device on the map.

– To enable, right-click the device and select Lock.

– To disable, right-click the device and select/uncheck Locked.

• Delete Device: Click this parameter to delete a device on the map.



– To delete, right-click the device and select Delete Device. Note that you can also right-click the device IP address youwant to delete in the Device Tree and click Delete.

• Save/Clear Device Position:

– Save Device Position: Click this parameter to save a device position on the map.

Consider a case where you have saved a device position on the map. After saving the device position on the map, youhave applied few more changes to the device position on the map. Lets say, without saving the newly applied deviceposition, you switch to another map mode. In such a scenario, the ProximVision ES application before switching toanother map mode checks if the recently changed device position has to be saved or not. Click Yes, if you wish tosave the changes else click No.

– Save Device Position & Commit: Refer to Device Placement on Dynamic Map at configured GPS Co-ordinates– Clear Device Position: Click this parameter to clear a saved device position on the map. The device can be moved

from Dynamic Map to Static Map and vice versa only when its device position is cleared on a map.

To move a particular device, follow the following steps:

1. Select the device on the map that you desire to move.

2. Right-click the device and select Clear Device Position.

NOTE: The Clear Device Position is enabled only when the device is saved on the map.

3. Repeat step 1 and 2 for each additional device that you want to move.

4. Change the map mode from Dynamic to Static and vice versa.

5. Select No, when asked to save the device positions on the map.

NOTE: If you select Yes, all the devices will be saved on the current map and cannot be moved to the desired map location.

6. The selected devices will appear on the map, place them and save their locations as desired.

• Change Device Location: Click this parameter to change the position of the device if latitudes/longitude are known. Thisis enabled only when the device is not saved on the map.

• CLI: Click this parameter to configure a device by using Telnet.

• HTTP: Click this parameter to configure a device by using web interface.

NOTES:• When the device is down, you can only access IP Address, Lock, Delete Device and Clear Device position

parameters of a device.

• The Monitor user has access to only IP and Lock parameters of a device.

• This feature is not applicable to Tsunami 8000 TDM IDU devices.

To view the device and link details, point the cursor on the device. The device related information is displayed at the bottomof the Device Tree as shown in Figure 9-36 and remains there as long as you keep the cursor on the device.

You can link the device manually also, but limited only to two devices at a time.

1. Select the two devices to link by holding the Ctrl key and right-click.

2. To add a link, right-click and select Link Devices to link two devices.

3. To delete a link, right-click and select Delete Link.



Figure 9-35 Calculate Distance

NOTES:• You can connect CO with Tsunami QB 81XX End Point A, and CPE with Tsunami QB 81XX End Point B only

through manual links.

• Only Manual links can be deleted. Manual links are highlighted in black.

4. To calculate distance between the devices, click Calculate Distance.

NOTES:• Calculate Distance calculates the straight line distance between the two devices without taking the road map

into consideration.

• Calculate Distance feature is not applicable in Static Maps.

Figure 9-36 Device Details



9.6.1 Locate a Device on the Map

To locate a particular device on the map, click Tools > Locate a Device. The Locate a Device window appears.

Figure 9-37 Locate a Device on the Map

Enter the IP address of the device that has to be located on the map, in the IP Address box and click Find.

The located device icon on the map is highlighted in green.

Figure 9-38 Located Device Highlighted in Green

9.7 Device Placement on Dynamic Map at configured GPS Co-ordinatesThis feature enables a Network Administrator to place the devices on the Dynamic Map (Google map) at the configured GPSCo-ordinates (Longitude and Latitude). It also provides the flexibility for the Network Administrator to change the devicepositions by using Dynamic Map feature of ProximVision ES. To change the device location, the Network Administrator has tojust drag and drop the devices on the Dynamic Map at the desired location, and then save and commit for the changes totake effect.

Given below is an example which helps you to understand this feature along with the process to change device location byusing Dynamic Map functionality.



Figure 9-39 Device GPS Co-ordinates

As seen in Figure 9-39, the GPS Longitude and Latitude values for a TMP (169.254.128.132) device are 79.10 and 22.91respectively.

ProximVision ES places the device on the Dynamic Map at the specified GPS co-ordinates as shown in Figure 9-40.



Figure 9-40 Device Located on the Dynamic Map at configured GPS Co-ordinates

Let say, you want to change the Latitude and Longitude values of the TMP device to 27.99 and 78.4 respectively. To do so,drag and drop the device at the desired Latitude and Longitude values on the dynamic map. Next, right-click on the deviceand select Save Device Position & Commit.

NOTES:• The GPS co-ordinates feature is applicable only to AP-800/AP-8000/AP-8000MR, AP-700, AP-4000x, AP-4900x,

MP-81XX and QB-81XX devices.

• The Save Device Position & Commit option is applicable only to MP-81XX, QB-81XX andAP800/8000/AP-8000MR devices. For all other devices, the save option is Save Device Position.



Figure 9-41 Change in the Device Location

On performing a save operation, the changed GPS Co-ordinates are applied on the device.

Figure 9-42 Changed GPS Co-ordinates applied on the Device

NOTE: After discovering the devices, if you have changed the latitude and longitude values of the device by usingeither HTTP, SNMP or CLI then refresh the Dynamic Map for the changes to reflect in ProximVision ES.



10
Tools

• Trap Viewer• SysLog Viewer• Inventory Report• ScanTool• Locate a Device• Show ProximVision ES Log

126

Tools

10.1 OverviewProximVision ES provides you a comprehensive trap detection and the inventory report thus enabling your organization toleverage existing network infrastructure without requiring any separate trap viewer devices.

CAUTION: If you have closed and restarted ProximVision ES, then all the previous trap messages and syslog messages will not be available. You can save the logs in Tools menu before closing ProximVision ES, if required.

10.2 Trap ViewerTrap Viewer is a messaging system that enables you to view the traplog messages sent from the devices. The TrapLog server inthe device should be configured to send messages to ProximVision ES. To view TrapLog, navigate to Tools > Trap Viewer.

Figure 10-1 Trap Viewer Submenu

The ProximVision ES - TrapLog Viewer window appears which provides the following information:

• Device Address

• Description of the modification

• Time

• Severity

Figure 10-2 Trap Viewer Screen

Click Export to save the Trap Viewer information to a desired location on your Personal Computer. A window appears whichprompts you to browse to the desired location to export TrapLog information.


Tools

Figure 10-3 Export TrapLog information

NOTE: You can view trap messages sent by Tsunami 8000 TDM IDU device only when it is configured.

10.3 SysLog ViewerThe SysLog Viewer is a messaging system that enables you to view syslog event messages sent from the devices. The syslogserver in the device should be configured to send messages to ProximVision ES.

Figure 10-4 SysLog Viewer Submenu

The ProximVision ES - SysLog Viewer window appears which provides the following information:

• Device Address

• Comment

• Status


Tools

Figure 10-5 SysLog Viewer Screen

To save the syslog report to a desired location on your Personal Computer, click Export.

NOTE: SysLog messages are not supported by Tsunami 8000 TDM IDU device.

10.4 Inventory ReportInventory Report submenu provides information about all the devices available on the network. To generate inventory report,navigate to Tools > Inventory Report.

Figure 10-6 Inventory Report Submenu


Tools

Figure 10-7 Collecting Inventory Information

The ProximVision ES - Inventory Report window appears which provides the following information:

• IP Address

• Status

• System Description

• Location

• Serial Number

• Software Version

• Hardware Version

• MAC Address

• Security ID

Figure 10-8 Inventory Report Screen

To save the Inventory Report at a desired location on your Personal Computer, click Export.

10.4.1 Custom Inventory Report

The Custom Inventory Report allows the user to customize the inventory reports based on their specific requirements.

To customize Inventory Reports,

1. Click Tools > Custom Inventory Report. The Inventory Options window appears.


Tools

Figure 10-9 Custom Inventory Options

2. From the Inventory Options list, select the inventory details that you want to be displayed in the Inventory Report.

3. Click OK to generate a customized Inventory Report.

10.5 ScanToolProxim’s ScanTool is a software utility that runs on Microsoft's Windows machine. By using ScanTool, the IP address assignedto the device can be obtained and, if required, can be changed to the IP address that is appropriate on the network. TheScanTool automatically detects the devices installed on the network segment, regardless of IP address, and enables theconfiguration of each device’s IP settings.

By using ScanTool, you can

• Launch the Web interface

• Scan devices

• Modify the assigned IP address

• Switch between the network adapters, if there are multiple network adapters in the system

To launch ScanTool, navigate to:

– Tools > ScanTool, or

– Start > Programs > Proxim Wireless > ProximVision ES2.0 > ScanTool

NOTES:• ScanTool cannot detect devices that are on different LANs

• ScanTool works only for Proxim’s products

• ScanTool does not detect Tsunami 8000 TDM IDU, MP.16 and MP.11 HS (in SNMP v3 mode) devices

For more information on ScanTool, refer to the latest User Manuals at http://support.proxim.com.


Tools

10.6 Locate a DeviceTo locate a particular device (already discovered) on the network,

1. Navigate to Tools > Locate a Device.

Figure 10-10 Locate a Device Submenu

2. The ProximVision ES - Locate a Device window appears.

Figure 10-11 Specify IP Address to Locate a Device

3. Specify the IP address of the device that you want to locate and click Find. On doing so, the specified device isselected in the Device Tree.

NOTE: Specify an already discovered IP address.

10.7 Show ProximVision ES Log Show ProximVision ES Log contains ProximVision ES application log details.

To access Show ProximVision ES Log, navigate to Tools > Show ProximVision ES Log.


Tools

Figure 10-12 Show ProximVision ES Log Submenu

When you select Show ProximVision ES Log, the log information window appears.

Figure 10-13 Show ProximVision ES Log Information



11
Troubleshooting
This chapter helps you to isolate and troubleshoot problems faced while working with ProximVision ES. If this chapter doesnot provide a solution, or the solution does not solve your problem, contact Proxim’s Customer Support team athttp://support.proxim.com.

See the following:

• Connectivity Issues• RADIUS Profile• Windows Firewall• SNMPv1/v2c• Invalid Subnet Mask or IP address• Unable to Discover GX800• Management Passwords• SNMPv3 Error• Third Party Server Error• Unknown Host/Port• Invalid Entry while Configuring SSID/VLAN• Unable to create Syslog, Trap Host and VLAN Entries for MP.16 device• Screen Resolution Related Issues• Miscellaneous Errors

134

Troubleshooting

11.1 Connectivity IssuesConnectivity issues include problems that prevent you from powering and connecting to the device(s).

11.1.1 Device Does Not Boot - No LED Activity• Make sure your power source is ON.

• Make sure all the cables to the device are connected properly.

11.1.2 Serial Link Does Not Work• Double-check the physical network connections.

• Make sure your Personal Computer terminal program (such as HyperTerminal) is active and configured to the followingvalues:

– Com Port: (COM1, COM2 and so on depending on your computer);

– Baud rate: 115200; Data bits: 8; Stop bits: 1; Flow Control: None; Parity: None;

– Line Feeds with Carriage Returns

(In HyperTerminal select: File > Properties > Settings > ASCII Setup > Send Line Ends with Line Feeds)

11.2 RADIUS ProfileWhile editing the RADIUS Profile, if you do not enter the value for Shared Secret parameter, then ProximVision ES displaysthe following error.

Figure 11-1 Shared Secret Error for RADIUS Profile

To rectify the error, enter a value for the Shared Secret parameter.


Troubleshooting

11.3 Windows FirewallWindows Firewall protects the system from unsolicited users and application. If the Windows Firewall is turned on, then theProximVision ES application will not be able to launch itself. In such a case, you need to turn off the Windows Firewall andrelaunch the ProximVision ES application.

11.4 SNMPv1/v2cProximVision ES will not be able to manage the Access Point devices that are discovered in SNMPv1/v2c mode, but changedto SNMPv3 mode in the Secure Management status. You need to rediscover the Access Points in the SNMPv3 mode andmanage them by using the ProximVision ES application.

11.5 Invalid Subnet Mask or IP addressWhen you provide an invalid IP address or Subnet Mask, proximVision ES displays the following error.

Figure 11-2 Invalid Subnet and/or Mask

Enter the valid IP address or Subnet Mask to rectify the error.

11.6 Unable to Discover GX800If ProximVision fails to discover GX800, see Prerequisites for GX800.

You can also refer to the GX800 Installation and Management Guide at http://support.proxim.com.


Troubleshooting

11.7 Management PasswordsYou cannot make any changes in the Mgmt Passwords page, if the secure manage option is enabled. If Secure Manage isenabled, then you need to rediscover the device manually in the SNMPv3 mode. Once you rediscover the device, you canmodify/edit changes to the Mgmt Passwords page.

Figure 11-3 Management Passwords

11.8 SNMPv3 ErrorWhile trying to discover the devices in SNMPv3 version, you need to enter the password of minimum eight characters. If thepassword is less than eight characters, the ProximVision ES application will display the following error:

Figure 11-4 SNMPv3 Error during the Discovery of Devices


Troubleshooting

Please note that for AP-700, AP-4900M, AP-4000MR, AP-4000MR-LR, AP-4900MR-LR and MP.11 HS Series devices, thepassword should be of minimum six characters.

11.9 Third Party Server ErrorWhen any third party server (SysLog and TRAP server) is running, then ProximVision ES displays the following error.

Figure 11-5 SysLog Error

You need to deactivate the external server and run the ProximVision ES application again to ensure that the error does notoccur.

11.10 Unknown Host/PortWhile trying to discover the device that is not available on the network, ProximVision ES displays the following error.

Figure 11-6 Unknown Host/Port

To ensure that “Unknown Host/Port” is not displayed again, you need to enter a valid device IP address.

11.11 Invalid Entry while Configuring SSID/VLANEnsure that you have entered values for all the parameters while configuring SSID/VLAN information. If any of the parametersare left empty, ProximVision ES will display the following error.


Troubleshooting

Figure 11-7 Invalid Entry while Configuring SSID/VLAN


Troubleshooting

11.12 Unable to create Syslog, Trap Host and VLAN Entries for MP.16 devicea) Syslog Entries

While creating Syslog entries for MP.16 device, ensure that you select the SysLog Status as Create.

Figure 11-8 Creation of SysLog Entries

b) Trap Host Entries

While creating Trap Host entries for MP.16 device, ensure that you select the Trap Host Entry Status as Create.

Figure 11-9 Creation of Trap Host Entries

c) VLAN Entries

While creating VLAN entries for MP.16 device, ensure that you select the VLAN Status as Create.


Troubleshooting

Figure 11-10 Creation of VLAN Entries

11.13 Screen Resolution Related IssuesIf you set the system DPI to 120 dpi, you may come across screen resolution problems as shown in the following figure.

Figure 11-11 Screen Resolution Related Issues

To avoid such problems, Proxim recommends you to set the system DPI setting to 96 dpi, which is compatible to work withProximVision ES.

11.14 Miscellaneous Errors• If any specific IP Address range is excluded while using the Auto Discovery process, then this IP Address range will be

excluded from all the future Auto Discovery processes that would take place. If you want to include the excluded IPAddress range, then you need to manually rediscover the devices.

• When there are about 8-10 subnets configured in Auto Discovery, then there are chances that the ProximVision ES mayhang. If ProximVision ES does not respond, restart the application.

• In Windows 7, if you are not able to browse a Static Map for the Static Map Location, then close the ProximVision ESapplication and start it without any compatibility mode.

• In MP.11 HS device, when you update the operational mode of the wireless interface from 2.4 GHz to 5 GHz, the devicereboots automatically.

• In MP.16 device, the index (MAC Address) generated on the device is as shown in the following figure:


Troubleshooting

Figure 11-12 MP.16 Index Format

• In Windows 7, if you are not able to work with ProximVision ES Command Line Utilities as listed below, then run themwith admin privileges.

– Auto Discovery Defaults

– Delete All Devices

– Export Data

– GenerateLicData

– Import Data

– ProximVision ES

– ScanTool

– Upload License



A
ProximVision ES Supported Devices
ProximVision ES supports the following devices:

• ORiNOCO® Access Points and Mesh Series

• AP-700

• AP-4000, AP-4000M, AP-4000MR and AP-4000MR-LR

• AP-4900M and AP-4900MR-LR

• ORiNOCO® 802.11n Access Points and Mesh Series

• AP-800

• AP-8000

• AP-8000MR

• TsunamiTM MP 8100 Series

• MP-8100-BSU

• MP-8100-SUA

• MP-8150-SUR

• MP-8160-BSU

• MP-8160-SUA

• MP-8150-CPE

• MP-8150-CPE-100i

• MP-8160-CPE

• TsunamiTM QB 8100 Series

• QB-8100-EPA

• QB-8150-EPR

• QB-8150-LNK

• QB-8150-LNK-12 and QB-8150-LNK-50

• TsunamiTM MP.11 Series

• MP.11 5012 SUI, SUR and CPE

• MP.11 5054 BSU and SUI

• MP.11 5054-R BSU and SU

• MP.11 5054-R-LR BSU and SU

• TsunamiTM QB.11 Series

• QB.11 5054-R

• QB.11 5054-R-LR

• Tsunami™ MP.16 Series

• MP.16 3500

• Tsunami™ MP.11 HS 5054 Series

• MP.11 HS 245054-BSU-R (Outdoor)

• MP.11 HS 245054-SU-R

• MP.11 HS 245054-SUA

• MP.11 HS 245054-BSU-S (Indoor)

• MP.11 HS 245054-SU-S

143

• Tsunami™ MP.11 HS 4454

• MeshMAX 5054 Series

• MeshMAX 5054W and 5054WM

• Tsunami™ 8000 TDM IDU

• QB-IDU-4E-LNK

• QB-IDU-4T-LNK

• Tsunami™ GX800



B
Technical Services and Support
Obtaining Technical Service and SupportIf you are facing any problem(s) while using Proxim products, please read the manual and the other documents that areprovided along with the product to find a solution. If the problem still exist or if you require additional support to resolve yourissue, please contact Proxim’s Technical Service team and provide them with the following information:

• Product information

– Part number and serial number of the faulty unit

• Trouble/error information

– Trouble/symptom being experienced

– Activities completed to confirm fault

– Network information (What kind of network you are using?)

– Circumstances that preceded or led to the error

– Message(s) or alarm(s) viewed

– Steps taken to reproduce the problem

• ServPak information (if a Servpak customer)

– ServPak account number

NOTE: Technical Support is free for the first 90 days from the date of purchase. If you would like to register yourproduct now, please visit Proxim eService Web site at http://support.proxim.com and click New ProductRegistration.

Support Options

Proxim eService Web Site SupportProxim’s eService Web site (http://support.proxim.com) is available 7x24x365.

You can access the following services on the support Web site:

• New Product Registration: Register your product to gain access to technical updates, software downloads, and freetechnical support for the first 90 days from receipt of hardware purchase.

• Open a Ticket or RMA

• Search Knowledgebase: Locate white papers, software upgrades, and technical information.

• ServPak Support: Learn more about Proxim’s ServPak global support service options.

• Your Stuff: Track status of your tickets or RMAs and receive product update notifications.

• Provide Feedback: Submit suggestion(s)/feedback on the support Web site.

• Customer Survey: Submit the Customer Survey response on the support Web site.

145

Telephone SupportGiven below are the Proxim’s technical support contact details along with the time for making support calls.

USA and Canada Customers

Phone: 408-383-7700

Toll Free: 866-674-6626

Hours: 6:00 AM to 6:00 P.M. Monday - Friday, Pacific Time

APAC Customers

Phone: +91 40 23115490

Hours: 9:00 AM to 6:00 P.M. Monday - Friday, IST (UTC/GMT +5:30 hrs)

International Customers

Phone: 408-383-7700

Hours: 6:00 AM to 6:00 P.M. Monday - Friday, Pacific Time

ServPak SupportTo provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak.ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meetyour specific needs. Whether your requirement is round the clock technical support or advance replacement service, we areconfident that the level of support provided in every service in our portfolio will exceed your expectations.

• Advanced Replacement of Hardware: Can you afford to be down in the event of a hardware failure? Ourguaranteed turnaround time for return to factory repair is 30 days or less. Those customers who purchase this serviceare entitled to advance replacement of refurbished or new hardware guaranteed to be shipped out by the nextBusiness Day. Hardware is shipped Monday – Friday, 8:00 AM – 2:00 PM (PST).

• Extended Warranty: Extend the life of your networking investment by adding 1, 2, or 3 years to your productsstandard warranty. This service coverage provides unlimited repair of your Proxim hardware for the life of the servicecontract. The cost of an extended warranty is far less than the cost of a repair providing a sensible return on yourinvestment.

• 7x24x365 Technical Support: This service provides unlimited, direct access to Proxim’s world-class Tier 3 technicalsupport engineers 24 hours a day, 7 days a week, 365 days a year including holidays. Customers who purchase thisservice can rest assured that their call for technical assistance will be answered and a case opened immediately todocument the problem, troubleshoot, identify the solution and resolve the incident in a timely manner or refer to anescalation manager for closure.

• 8x5 Technical Support: This service provides unlimited, direct access to Proxim’s world-class technical support 8hours a day, 5 days a week from 8:00 AM - 5:00 PM (PST(US)). Technical Support is available at no charge for the first90 days from the purchase date. Beyond this period, a ServPak support agreement will be required for technicalsupport. Self-help will be made available by accessing Proxim’s extensive eService knowledgebase.

• Software Maintenance: It is important to maintain and enhance security and performance of wireless equipmentand Proxim makes this easy by providing a Software Maintenance program that enables customers to access newfeatures and functionality, rich software upgrades and updates. Customers will also have full access to Proxim's vastknowledgebase of technical bulletins, white papers and troubleshooting documents.

• Priority Queuing Phone Support: This service provides customers with a one hour response time for technicalphone support. There is no waiting in line for those urgent calls for technical support.


To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or forquestions on any of the available ServPak support options, call Proxim Support at 408-383-7700 or send an email message [email protected].


pves installation and management guide v2.5

Documents