Home > Trapeze Networks Evaluation Checklist

Trapeze Networks Evaluation Checklist

Tags:  

Trapeze Networks Evaluation Checklist

This document is intended to provide a checklist for setting up a basic Trapeze Networks lab environment for testing and evaluation.
DirSec recommends reviewing the relevant Trapeze documentation before deploying, in particular:
  • Trapeze Networks Mobility System Software (MSS) Quick Start Guide
  • Trapeze Networks RingMaster Quick Start Guide

Assumptions

The following equipment will be used for the evaluation:
  1. Trapeze MX-8 controller
  2. RingMaster management software (on a customer-provided server)
  3. 4-6 Mobility Point APs (MP-422 or MP-8)

Prerequisites

Before starting the deployment, please verify the following:
  1. You have a valid login for the Trapeze SafetyNet support portal, and also has a RingMaster evaluation key. If access needs to be set up, please contact DirSec for assistance.
  2. If needed, download the following components from Trapeze SafetyNet:
    1. Current product documentation for Mobility System Software (MSS) and RingMaster.
    2. Current RingMaster software release for selected platform (Windows, Linux, Mac OS X).
    3. Current Mobility Exchange (MX) firmware image
    4. For assistance in determining correct software releases, please contact DirSec.
  3. A server is available to host the RingMaster management software
    1. RingMaster server is supported on the following operating systems:
      1. Microsoft Windows Server 2003, Microsoft Windows XP with Service Pack 1 or higher, Microsoft Windows 2000 with Service Pack 4, or Microsoft Vista Enterprise.
      2. SUSE Linux 10.2 and Red Hat WS ES5
      3. Apple MacOS Version 10.4.x. with Java 1.5.
    2. Trapeze Networks specifies the following minimum server hardware requirements:
      1. Windows/Linux: Intel/AMD x86-compatible Dual Core processor, 2.0 GHz, 2 GB RAM, 50 GB Available Disk Space
      2. Mac OS X: Mac Pro, two 2.0 GHz, 2 GB RAM, 50 GB HD
    3. TODO: Verify if VMware instances are supported
  4. IP addresses and other network settings are established for RingMaster server and MX-8 controller.
  5. Have available a system with a serial port or USB-to-serial adapter and appropriate terminal software. While the Mobility Exchange controller can be configured via a web-based Quick Start, serial access to the unit may be required in some situations.

Pre-deployment Questions

  1. Will access points be deployed as directly-connected to MX or in distributed mode?
    1. If distributed mode, discuss requirements for DHCP Option 53 or DNS hostname for location of MX controller.
    2. PoE power support?
      1. Does customer have PoE switch and/or power injectors?
  2. Authentication services
    1. Does customer have IAS or similar AD/LDAP to RADIUS bridge?
    2. Authentication options of interest?
      1. 802.1x?
      2. Web-based portal?
      3. Guest access via SmartPass?

Deployment Steps

  1. Installation of RingMaster software and initial setup
  2. Initial setup of MX controller
    1. Connection to unit (serial or via Ethernet crossover cable)
    2. Reset to factory defaults
    3. Quick Start configuration of unit
      1. Hostname
      2. Country of Operation (United States)
      3. IP address
      4. Netmask
      5. Default Gateway
      6. Authentication credentials
  3. Establish RingMaster communication with MX
  4. Check MSS software version on MX, and upload new firmware image if needed.
  5. Define mobility points in RingMaster
  6. Set up of radio profiles.

 RSS of this page