You are on page 1of 7

WM Release 3.

0 Release Notes

Issue 4 March 2011


Device and Software Requirements
Network Management Capacity
Where the requirements that are listed in this section are met or exceeded, the WM Release 3.0 server can concurrently monitor and manage as many as 5,000 network elements, with the following upper limits for each supported network element type: � � � � � � � � 2,000 total RFMS/ADSP managed sites 1,000 RFMS servers/ADSP folders 1,000 PMP APs 4,000 PMP SMs 1,000 PTP links (2,000 PTP elements) 5,000 Mesh nodes (1,750 Quattro nodes)

This release supports as many as 1,000 traps per second. 20 concurrent client connections.


Hardware Requirements
Requirements for the server and client devices are distinguished as follows. Devices that are used for both must meet both sets of requirements.


Server Device Hardware Requirements
The following specifications are recommended as minimum hardware requirements for the WM Release 3.0 server: � � � � a server-class CPU, as distinguished from a desktop computer 4 GB RAM a dual-core processor, 2 GHz+ RAID storage (all collected data is stored in the MySQL database on the server)


Client Device Hardware Requirements
Any modern desktop or laptop that meets the following minimum standards can run the WM Release 3.0 client application: � � � 15 MB storage space a high-speed link of at least 1 Mbps. (Slower connection speed causes slow startup and the possibility of other problems after startup.) screen resolution setting of 1024 x 768


...2 with Patch (Service Pack) 8. To allow a reliable interval for broad testing on networks that include Mesh elements...0. is limited to support for networks that are entirely composed of PMP and/or PTP elements (networks that exclude deployment of Mesh elements and Mesh management products from the Motorola One Point Wireless Suite).0. see the Wireless Manager 3.5 ES.19: � � � Release 3. which was published for general availability in November 2010 Future Release 3.15.2 Supported Upgrade Paths The software upgrade paths to this release are strictly limited as are those of successive service packs when they are made available: � Only two previously releases support an upgrade to Release 3.. which was published for limited availability in December 2010 Release 2. For OS-specific installation instructions..0.1 Software Platforms. and Requirements Types of Networks Supported by Release 3. Motorola technical support cannot help a user customize an OS to meet the requirements. Wireless Manager requires specific versions of libraries to be located in certain places.0. networks that contain any Mesh elements must continue to use only Release 2.. 4.0. Even later versions of Red Hat Enterprise Linux fail to satisfy these library requirements. Compatibility. note . 4. A server on a Linux or CentOS operating system requires the installation of a GUI windowing environment..2 of WM with Patch 8 applied.0 Quick Start Guide.3.19. 32-bit.0 service packs will be supported for only Release 3.3 Operating Systems OS Platforms for the Server The following are supported for the Release 3.Issue 4 March 2011 WM Release 3. 18 . No later version of Red Hat Enterprise Linux or of Linux from a different vendor is supported. Meanwhile. which these release notes support.5. 32-bit Red Hat Enterprise Linux 5.0 Release Notes 4.3 The scope of Issue 3 of these release notes and Release 3.3.. a WM upgrade that will support them is deferred until a future service pack provides that.0 server: � � � Windows Server 2008 R2 Enterprise CentOS 5...

..5 ES. 32-bit..6. Red Hat Enterprise Linux Version 5.) You must assign the old server IP address to the server on the new device. one that runs an OS version that Release 3.5. OS Platforms for the Client The WM Release 3. One problem that this will avoid is a plotted display of data from both servers being rendered in the "WM Monitoring" Collected statistics window when you launch Help�Diagnostics�Server Health Diagnostics. 4.WM Release 3. 19 . VMware on the Server VMware vSphere is supported on the Release 3.4 Other Dependencies Java in the Server The server requires Java 1. but you can restore data according to procedure titled "To migrate operator data in upgrade of WM plus the OS" in that guide.0 server device. The following other OSs are expected to work but were not tested with the client application: other 32-bit Windows versions CentOS 5.3. (As stated in the server administration guide. the Restore System command option is not supported for restoring the data onto a different server device.0 Release Notes Issue 4 March 2011 important ... This is an advisory to an operator who has backed up the server data from the previous release in order to manually restore it on a different server device.0 supports. 32.0 client application supports any of the following operating systems: � � � � � Windows 7 Professional.5 ES..bit. Java Runtime Environment in the Client The WM client application supports the 32-bit platform of either of the following operating systems: � � Windows 7 Professional. 32-bit Windows Server 2008 R2 Enterprise Red Hat Enterprise Linux Version 5..

6: � � � If security applications and setting on the client device allow the installation. Every subsequent time the client connects to the same server. you must install Java 6 and then launch the client. which is satisfied as follows: � Where Java 1.2 or later is not present. The client requires Java 1. The port assignments that Wireless Manager components use must be open in the firewall. where a firewall is implemented. which will then use Java Web Start to install itself.4. Instructions for how to configure server-client communications after installation are documented in both the quick start guide and the server administration guide. WM automatically attempts to install Java 1. if the client is on a Linux device MS-Internet Explorer 7. Where 1. WM verifies these downloaded files for updates. 20 .6. then proceed as described in the following bullet.0 Release Notes The client is launched using the Java Web Start Application Manager. if the client is on a Windows device Port Availability and Assignments Communications between the server and client require that two port assignments (for NMSSocketPort and NMS_FE_SECONDARY_PORT) are made in the server file system after WM installation or upgrade.4. no further action is required of the client device administrator. If they do not allow it. The client-related jar files are downloaded when the client connects to the server for the first time.2 or later is present in the client device. Browsers The client device requires one of the following HTTP browsers: � � Mozilla Firefox 3.Issue 4 March 2011 WM Release 3.

Inbound UDP for APs to request authentications from BAM.2 Inbound data from the BAM server. Outbound UDP for SNMP response over the northbound interface (NBI). Network management back-end server. Socket server. 21 . Inbound UDP for the northbound interface (NBI). Inbound TCP for the web server. TCP connections by Tomcat and web server for access to device management web pages. NMS Socket for TCP communication between the WM server and WM client.1 Outbound connection to BAM server to launch its interface. Inbound TCP for TFTP connections in the firmware upgrade process.0 Release Notes Issue 4 March 2011 Table 1: Ports that must be open Server Port 25 80 161 161 162 1234 1476 1482 2000 2501 WM 3306 6900 8001 8003 8009 8090 9090 32900 33100 61001 Usage Outbound connection to SMTP server for email configuration. Inbound UDP for SNMP traps from devices. Outbound UDP for SNMP interface with ADSP/RFMS elements.3 NMS FE Secondary for TCP communication between the WM server and WM client.4 Outbound UDP from BAM to APs. Configuration server. To turn the SM Autoupdate feature on or off in APs. Outbound UDP for device SNMP queries and configurations. Queries to the MySQL database.WM Release 3.

/server/conf/licensing.1 database whose service name is WMSMySQL. Communications between WM and the web administration interface of GeoServer.. 4. 4. Port number is reconfigurable in . 22 . 3.5 Optional Oracle Java Naming and Directory Interface (JNDI) connection pool via Tomcat.xml. the tool prompts you to input the root password for MySQL Server and the username and password for the WMSDB database. Port number is reconfigurable in . Must be configured in .conf with WM server stopped after WM installation. 5....5 Database The installation tool for WM Release 3.0 installs a MySQL Server Version 5. Although the tool installs this database on the WM server device.5 Usage WM Release 3.. During the installation.0 supports on a device remote to the server. 2./server/conf/WibbWMSConfiguration... Must be configured in .xml.0 Release Notes Secure communications between WM and the web server of License Manager.xml./server/Apache/Tomcat/conf/server./server/conf/serverparameters...3.conf with WM server stopped after WM installation. WM to request licenses..Issue 4 March 2011 Server Port 27000 License Manager 27443 1521 GeoServer 8080 NOTES: 1. Port number is reconfigurable in ./server/conf/transportProvider. Release 3.

the database. the initial versions of the software product documentation. This tool supports both � � fresh installation. the scripts to configure connections to License Manager. and the optional system to be accessed via the northbound interface from WM. where BAM is deployed. See the Wireless Manager Release 3. software application that is required for � � � � � � � � � � � � � validating the WM server license. allocating WM management licenses to devices against the total available license count. validating the physical maps license.0 Quick Start Guide. where BAM is deployed. the script to install the MySQL database for fresh installations or to migrate it (make it adaptable to new field definitions and field sizes and to all new queries) for upgrades. See the Wireless Manager 3.0 Release Notes Issue 4 March 2011 5 Installation Tool Motorola provides the installation tool for this release as an available download during the license procurement process. upgrades either from Release 2. see the Prizm to WM Migration Guide. For information on licensing the software products see the Wireless Manager 3. For information about migrating data from Prizm to WM. see the Wireless Manager Release 3. contact your Motorola representatives. validating the BAM server license.0 Quick Start Guide.0 or from Release 2. See Documentation on Page 25.2 only with Patch 4. 23 . the option to install Network Updater Tool (CNUT).0 Server Administration Guide. for the upgrade case. The distribution from this tool includes � License Manager. an MD5 checksum to verify that the tool did not experience corruption during its download. allocating licenses for authentication and for pushes of bandwidth service plans and VLAN profiles to PMP slave devices.WM Release 3.0 Server Administration Guide. optional BAM.