motorola canopy prizm release 3.3 release notes… · 2013-08-07 · license agreement the use of...

Motorola Canopy® Prizm Release 3.3 Release Notes Issue 4

July 2010

LICENSE AGREEMENT

The use of Release 3.3 of the Prizm product is only under the terms and conditions that are quoted in the section titled "License Agreement" of the Motorola Canopy® Prizm Release 3.3 User Guide and in the click-wrap version of the same.

TRADEMARKS

MOTOROLA and the stylized M Logo are registered in the U.S. Patent & Trademark Office. All other product or service names are the property of their respective owners. Java and all other Java-based marks are trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation; and Windows XP is a trademark of Microsoft Corporation. Netscape is a registered trademark of Netscape Communication Corporation. Canopy is a registered trademark of Motorola, Inc.

Motorola, Inc Canopy Wireless Broadband 1299 East Algonquin Road Schaumburg, IL 60196 USA

http://motorola.wirelessbroadbandsupport.com/support/

© Motorola, Inc. 2010

http://motorola.wirelessbroadbandsupport.com/support/

TABLE OF CONTENTS

1 Introduction............................................................................................................. 11 1.1 New in This Issue........................................................................................... 11 1.2 Feedback About Documentation .................................................................... 13

2 Features................................................................................................................... 15 2.1 New Features................................................................................................. 15

2.1.1 Slimmer Aggregation of Element Performance Data ....................................15 2.1.2 Reinstated Bandwidth Reports and Charts ...................................................16 2.1.3 New Prestructured Configuration Templates for Authentication ...................16 2.1.4 HPAP Channel Bandwidth Tab Added to Configuration for Update Device

Firmware Task...............................................................................................17 2.1.5 Failed to Poll Alert Made Configurable..........................................................17 2.1.6 LM Link From Initial Web Page .....................................................................17 2.1.7 New Command to Re-assign SM Public IP Addresses.................................17

2.2 New Attributes and Statistics.......................................................................... 18 2.3 New Support for Elements ............................................................................. 26

3 Compatibility ........................................................................................................... 27 3.1 Software Compatibility.................................................................................... 27 3.2 Supported Platforms and Requirements ........................................................ 28

3.2.1 OS Platforms for the Prizm Server ................................................................28 3.2.2 OS Platforms for the Prizm Client Application...............................................28 3.2.3 OS Platforms for Canopy License Manager..................................................28 3.2.4 Functions Module Required for the Prizm Server on Windows ....................28 3.2.5 Framework for the Prizm Server on Windows...............................................28 3.2.6 Visual C++ Package for the Prizm Server on Windows................................29 3.2.7 Upgrades to Release 3.3...............................................................................29 3.2.8 Dependencies for the Prizm Client Application .............................................29 3.2.9 Databases .....................................................................................................30 3.2.10 Web Browsers ...............................................................................................31

3.3 Module Firewall Configuration........................................................................ 32 3.4 VLAN ID Length ............................................................................................. 32

4 Installation Tool ...................................................................................................... 33

5 Documentation........................................................................................................ 41 5.1 Documents That Support Release 3.3 ........................................................... 41 5.2 Installing the Latest Documents ..................................................................... 41

5.2.1 Overwriting Documents in Windows..............................................................42 5.2.2 Overwriting Documents in Linux....................................................................42

6 Issues Resolved with This Software Release ...................................................... 43 Cold Start Trap from AP Not Triggering Prizm to Note an IP Address Change ..........43 Defect That May Require Periodic Prizm Server Restart ............................................43 History Tab Displaying Simultaneous Null Values for All Attributes............................43 Discovery Messages Thrown to Element Configuration History .................................43 Modify Element IP and MAC Not an Alternative Way to Suspend ..............................43 SM Details Temporarily Partial After Move from Provisioned to Managed .................44 Exception Error Thrown for Deactivating Alerts...........................................................44 Java Exception When Filtering Alerts..........................................................................44 Element Type Null in Subscriber Report for SMs in Ignored, Discovered, or Provisioned States.......................................................................................................44 Platform Versions for Some Discovered Elements Incorrectly Expressed..................44 NAT RF Public IP Not Configurable via Prizm Template ............................................44 SNMP Proxy SMs That Register in New AP Not Being Polled ...................................45 CNUT Options Being Available in BAM-only Server ...................................................45 Bandwidth Tab Absent From Details for BAM-managed SM ......................................45 Dollar Sign in Site Field Affecting Element Details ......................................................45 Incorrect Option Cited by Email That Provides Temporary Password ........................45 Two Predefined Configurable Reports Removed........................................................45 Standard Schedule Creation Time Showing Server Startup Time ..............................45 Type List Sometimes Not Including All Task Types ....................................................46 Import Causing Prizm to Identify Generic Device as Generic Group ..........................46 Two Identical Options for Source in Event Filter Dialog ..............................................46 Scroll Bar Not Included in Report View Panel .............................................................46 Alerts by Element Type Dashboard Module Displaying Improperly ............................46 Web Server Not Starting After Installation on Linux ....................................................46 Configurable Values Out of Range for Two VLAN Attributes ......................................46 Login ID Entries in Improper Case Accepted ..............................................................46 Authentication for Valid PMP 430 SMs Rejected ........................................................46 Missing Decimal Point in Element Details for PTP 600...............................................47 Configuration Parameter Selection Tree Missing Some RF Max Modulation Mode Attributes......................................................................................................................47 Subscriber Report Request Generates Error If No SMs in Network ...........................47 RF Antenna Polarization Null in Browser Column.......................................................47

Element Details Misleading for SMs............................................................................47 Wrong Availability for Authentication Tabs of SMs......................................................47 Java Errors for PostgreSQL Updates of Customer Information ..................................48 Element Count in Browser for Search Results Always Showing Zero ........................48 Print Preview Truncating Report Data .........................................................................48 Polling Threads Seizing for Large Networks ...............................................................48 Maximum Supported Number of Characters for User Passwords ..............................48 Refresh Required for Network Inventory Report After Prizm Upgrade .......................48 Unregistered SMs Automatically Being Moved From Activate to Suspend.................49 Refresh Operation Losing the Expanded/Collapsed Settings for Elements................49 Installation Tool Detecting Uninstalled Release ..........................................................49 Nonfunctioning Help Button in Installer Wizard ...........................................................49 History Tab Null for SM................................................................................................49 Inability to Select All Elements Displayed....................................................................49 Define Notification Dialog Accepting Address Lists Too Lengthy for PostgreSQL......49 Delete Selected Files Function Inconsistent in Secure NBI to Prizm..........................50 System Losing Status of an Element...........................................................................50 Channel Change Traps Not Being Processed for PTP 500 Ethernet Bridges ............50 License Manager Setup via Server Administrator Tool Not Synced Out to License Manager Administrator Tool ........................................................................................51 Server With Microsoft SQL Server 2000 Failing to Start .............................................52 Accept and Manage Operation Put DHCP Server Address for NAT SMs into the Management Subnet ...................................................................................................52 Upgraded Server on RHEL OS Crashing ....................................................................52 Prizm Disregarding Non-default Port Configuration for Licensing Server ...................53 InstallAnywhere Tool Freezing When Legal Password was Configured for PostgreSQL .................................................................................................................53

7 Issues Acknowledged with This Software Release ............................................. 55 7.1 Issues in the Installation and Upgrade Processes ......................................... 55

Ports Not Being Released by the <Upgrade From> Software Release ......................55 Installation Tool Unable to Remove Prizm Release 3.1 From Non-standard Path .....55 Full Prizm Server Installation on Standalone License Server Keeping LM Login and Password .....................................................................................................................55

7.2 Issues in Core Prizm Functions...................................................................... 56 .NET Framework Required for Prizm on Windows......................................................56 Inability to Clear Release 8.x Passwords from Elements............................................56 Data Export from Print Preview Not Guaranteed.........................................................56 Only One SM Listed in Remote Subscribers Tab via Web Proxy ...............................56 Authentication Occurred Not Updated to False...........................................................57 Increments for Task Scheduling and Implementing Vary............................................57 RF Airlink Security Attribute Not Supported ................................................................58

Configuration Functions Not Working in Accepting State............................................59 Uncertain Behavior Toward Quarantined Elements During Switch to RADIUS..........59 Web Proxy Failing if Prizm Launched in HTTP ...........................................................59 Web Proxy Cannot Download Certain Configuration Files..........................................59 Count of Failed Logins Reaching Lockout Threshold..................................................59 Speed of Reporting to Prizm Affected by License Manager Server Outage ...............60 Long Pauses in the Network Discovery Process with MySQL ....................................60 Individual Parameters Not Reset When Template Application Appears Successful...61 Prizm Sending DFS Update Requests to Non-DFS Radios........................................61 Relationship Lost When Accept and Manage Interrupted ...........................................61 MySQL on Windows Sometimes Requiring Restart ....................................................61 SMs Provisioned by MAC Address Remaining in Accepting State .............................62 Authentication Server Requiring Unusually Long Time to Recover from Restart .......62 Configuration History Tab Reflecting Changes Not Made By the Prizm Operator......62 Configurable Parameters Assuming Alternate Values Without Operator Action.........63 Profiles Automatically Adopting New Names ..............................................................63 Elements Locked in Unprovisioned State....................................................................63 Disabled Default Tasks Automatically Re-enabled After Reboot ................................64 VLAN Profiles Unable to Set SM Management VID Pass-Through ............................64 Bandwidth Service Plans Unable to Set MIR and CIR Parameters ............................64 Inability to Change Geolocation Attributes ..................................................................64

7.3 Issues in the Prizm Client Interface................................................................ 65 No License Checkout Error Logged in Applying Configuration Window .....................65 Database and Prizm GUI Supporting Longer VLAN Entries Than BAM Subsystem Does..........................................................................................................65 Status Indicator Color Not Red for Unrecognized Trap Alert ......................................65 Prizm Reporting Incorrect Distance for 900-MHz SM .................................................65 Moved Elements Appearing in New and Old Positions ...............................................66 Licensing Information Window Sometimes Showing 0 for Available Licenses ...........66 Erroneous Numeric Values in Details Graphics ..........................................................66 Color Key Overlaying Key Text....................................................................................67 Prizm Console Window Opening Off-screen...............................................................68 SM Not Reflecting New VLAN Membership Until Reboot ...........................................68 Nonexistent Elements Being Discovered ....................................................................68 Column Selections Discarded If Search Dialog is Not Cleared...................................69 Deleted Service Plan or VLAN Profile Can Be Applied ...............................................69 Client Lockup First License Manager Server Goes Down...........................................69 Slow Reaction to Show Licensing Option....................................................................70 Authentication Account State Not Updated for SM Removed from RADIUS..............70 Possible SNMP Failure Reaching a CMM4.................................................................70 No Indication When an Element Is Read Only ............................................................70 HTML Session Dropped After Configuration Push......................................................71

Various Treatments of Number and Type of Characters in Site Names .....................71 Clarification Needed for Source of Bandwidth Values.................................................72 Unexpected Behaviors in Dashboard ..........................................................................72 Tabs Not Closing .........................................................................................................74 Some Elements Not Moving to Ignored Elements List ................................................75 Bandwidth Usage Chart Displays in Byte Units After Conversion to Bit Charts..........75 Changed IP Address Associated With NAT Private IP in Configuration History .........76 Button for Information About the Application Not Functional.......................................76 Scroll Horizontally Option for Dashboard Ignored .......................................................76 Persistent End Time Selection List for Event Filter in Linux........................................77 Elements from Previous Window Appearing in New Window for a Split Second........77 Search Category Listed Twice.....................................................................................77 Tooltip for Some Elements Being Out of the Console Window...................................77 Sessions Tab Displaying Incomplete and/or Inaccurate Information ..........................78 Updates to EMS Primary Status of SNMPAccounts Not Enforceable ........................78 Duplicate Elements Tree in Home Configuration ........................................................79 Error Thrown for Selection of All Devices Types in PostgreSQL Deployment With Prizm Upgrade.............................................................................................................79

LIST OF FIGURES

Figure 1: License Web Server link in Prizm startup page ..................................................... 17 Figure 2: IP Access Filtering area of Security tab in module GUI ......................................... 32 Figure 3: Process for fresh installation.................................................................................. 35 Figure 4: Process for Prizm upgrade .................................................................................... 36 Figure 5: Process for License Manager upgrade .................................................................. 37 Figure 6: Process for Prizm and License Manager upgrade................................................. 38 Figure 7: License Manager configuration options from Linux console .................................. 51 Figure 8: History tab of Configuration side tab, example ...................................................... 62 Figure 9: Example erroneous label on graph ........................................................................ 66 Figure 10: Example color key covering key text.................................................................... 67 Figure 11: Question mark shown as element type for HTTP-discovered elements .............. 68 Figure 12: Dashboard with added (seventh) module ............................................................ 73 Figure 13: Dashboard after click or hover on tab .................................................................. 74 Figure 14: Dashboard Module Settings Window................................................................... 76

LIST OF TABLES

Table 1: New or changed attributes ...................................................................................... 18 Table 2: Eliminated attributes................................................................................................ 22 Table 3: New or changed statistics ....................................................................................... 23 Table 4: Eliminated statistics................................................................................................. 24 Table 5: Unsupported SNMP objects.................................................................................... 25 Table 6: Devices types newly supported............................................................................... 26 Table 7: Installer options....................................................................................................... 33 Table 8: Prizm source for bandwidth values ......................................................................... 72

Prizm Release 3.3 Release Notes July 2010

Issue 4 11

1 INTRODUCTION

1.1 NEW IN THIS ISSUE Issue 4 of these release notes is published to support the new (3.3.9) iteration of Prizm Release 3.3 and communicate its resolution of the following issues:

◦ Server With Microsoft SQL Server 2000 Failing to Start on Page 52 ◦ Accept and Manage Operation Put DHCP Server Address for NAT SMs into the

Management Subnet on Page 52 ◦ Upgraded Server on RHEL OS Crashing on Page 52. ◦ Prizm Disregarding Non-default Port Configuration for Licensing Server on

Page 53 ◦ InstallAnywhere Tool Freezing When Legal Password was Configured for

PostgreSQL on Page 53

At the same time, Issue 3 of the user guide is published to

◦ add information about VLAN attributes that FSK radio Release 10.3 introduced but that cannot be configured via VLAN profile.

◦ update the Device Region Code attribute description to add two newly supported regions.

◦ announce a New Command to Re-assign SM Public IP Addresses on Page 17.

This update is not intended to catch up with and redeliver information that the patch notes that support Release 3.3 have published. Both Issue 4 of these release notes and Issue 3 of the user guide are complemented by the patch notes. If your system is always current with the latest patch, then the set of documents to use for reference is as follows:

◦ To see all currently supported features, refer to both − Issue 3 of the user guide − all patch notes.

◦ To see all currently supported device types or firmware versions, refer to both − this issue of the release notes − all patch notes.

◦ To see all acknowledged (unfixed) issues, refer to both − this issue of the release notes − the most recently published patch note.

◦ To see all fixed issues, refer to both − this issue of the release notes − all patch notes.

This reference scheme is graphically depicted below.

12 Issue 4

represents all of the new.

represents some of the old issues, carried forward unfixed. In the case of the release notes, these were carried forward from the previous release(s).

represents some of the old issues, now fixed. In the case of a patch note, these were carried forward from one or more previous patches.

To find certain types of information, you will a simultaneous search of multiple documents. For example, to see whether an acknowledged issue has been fixed, you will want to open both the release notes and all published patch notes, then use the Adobe Reader feature that searches all of the open documents. In Adobe Reader 9, you would

1. move all of the documents into the same directory. 2. open one of them. 3. enter the Item ID into the Find text box. 4. select Open Full Reader Search from the drop-down list of options. 5. select All PDF Document in. 6. use the drop-down list to select the directory.


Issue 4 13

1.2 FEEDBACK ABOUT DOCUMENTATION We welcome your feedback on Canopy® system documentation. This includes feedback on the structure, content, accuracy, or completeness of our documents, and any other comments you have. Send your comments to [email protected].

mailto:[email protected]


Issue 4 15

2 FEATURES

2.1 NEW FEATURES Release 3.3 introduces the following features. The use of some of these features is restricted based on permission level that the operator sets in the User Manager under Tools Administrator.

2.1.1 Slimmer Aggregation of Element Performance Data Release 3.3 narrows the scope of element performance data that the system aggregates in its RRD files, collecting and keeping the useful data in the perfchartdatafile.rrd file while only collecting the remainder of the available data.1 The specific data and status values that Prizm will no longer aggregate are

◦ port status ◦ Ethernet status ◦ number of network interface ports ◦ the following PPPoE data:

− current session ID, MTU override, MTU override, MTU override, timer type, timeout

− control bytes sent and received − data bytes sent and received − whether PPPoE is enabled − whether TCP MSS clamping is enabled − uptime and idle time of current session

◦ the following bridge control block data: − FEC stats: bin, bout, btoss, btosscap, uin, uout, utoss, utosscap − RF stats: bin, bout, btoss, btosscap, uin, uout, utoss, utosscap

◦ maximum registered SM count in the AP.

Canopy tracked this feature request under Item ID 0011318.

1 This area of Prizm is discussed in the section titled "Archiving and Removing Event History and

Bridge and ARP Tables" in the server administration guide.

July 2010 Prizm Release 3.3 Release Notes

16 Issue 4

2.1.2 Reinstated Bandwidth Reports and Charts The predefined reports Bandwidth Usage and Top Bandwidth Users, which were removed in Release 3.2, are reinstated with accurate data as follows:

◦ Bandwidth Usage provides daily or monthly transmitted, received, and total byte sums for selected PMP elements.

◦ Top Bandwidth Users provides daily or monthly transmitted, received, and total byte sums for the subscribers who use the most data resources in their traffic toward and from the public network.

The following default, customizable charts and their data view and data export options are also reinstated as the Bandwidth Usage tab of the Statistics side tab in element details panels:

◦ Bytes Transmitted (Tx) ◦ Bytes Received (Rx)

Canopy tracked this feature request under Item ID 0010015 and 0006094.

2.1.3 New Prestructured Configuration Templates for Authentication Release 3.3 introduces two new options available through the Edit Configure Authentication Settings command menu path:

◦ Master Device Authentication (No BAM) ◦ Slave Device Authentication (No BAM)

Either of these new options opens a Task Attributes dialog. To properly use these configuration tasks for PTP slave authentication, first execute the slave task without encryption, configuring the value of the Authentication General Key attribute; then execute the master task, configuring the same value into the attribute of the same name and select Enable for the Authentication Mode attribute. Finally, enable encryption if desired.

For SM authentication where the AP (instead of BAM) will be the authentication server, execute the configuration tasks as sequenced above, but select Use Pre-Shared Key for Authentication Mode of the AP.

For SM authentication where BAM will be the authentication server, set up the configuration task as in Release 3.2.

Canopy tracked this feature request under Item ID 0012648 and 0012709.


Issue 4 17

2.1.4 HPAP Channel Bandwidth Tab Added to Configuration for Update Device Firmware Task The Configuration tab of the Task Attributes dialog for an Update Device Firmware task now includes an HPAP Channel Bandwidth tab, in which the operator has the options to

◦ select, per operating (Current) channel bandwidth of SMs in a PMP 430 Series High-Performance AP sector, a different (Target) channel bandwidth to which Prizm should switch the SMs.

◦ set Prizm to proceed with or abandon the channel bandwidth switch if any SM is registered to the HPAP when CNUT is ready to perform the switch operation.

2.1.5 Failed to Poll Alert Made Configurable The prizmconfig.xml file on the Prizm server now provides adjustable severity for the Failed to Poll alert. See the server administration guide section titled "Configuring the Failed to Poll Alert." Canopy tracked the development of this feature under Item ID 0012442.

2.1.6 LM Link From Initial Web Page The startup web page from Prizm now includes a link to the License administration web server. This link is shown in Figure 1 below.

Figure 1: License Web Server link in Prizm startup page

Canopy tracked the development of this feature under Item ID 0006493.

2.1.7 New Command to Re-assign SM Public IP Addresses The Prizm Release 3.3.9 installation adds to the Edit menu the command option to Re-Assign IP to Subscriber Module(s). When you execute this, Prizm overwrites the public IP address of the SM with an address from the management subnet configuration.


18 Issue 4

2.2 NEW ATTRIBUTES AND STATISTICS As Canopy system software progressively adds devices and module management capabilities, and as Prizm upgrades the set of management and monitoring features, the number of attributes and statistics in Prizm continues to grow. The growth is reflected in the Columns list, from which you can select them for a network view, and in the Configuration Parameter Selection windows, from which you can select the configurable attributes to manage in a custom template that you are creating or updating.

Release 3.3

◦ supports Canopy system releases through 10.3 for FSK and OFDM radios. ◦ introduces the following new or changed attributes to support features of the

elements and element management.

Table 1: New or changed attributes

Prizm Attribute Name Description

All IPv4 Filters If enabled, this sets all IPv4 packet filters in the SM when NAT is disabled, automatically enabling all of the known IP filters (SMB, SNMP, Bootp, IPv4 Mcast, User Defined Ports, and All Other IPv4).

Authentication Account Expires Time configured in the SM for when the SM will no longer be able to authenticate to the network.

Authentication AP Preshared Key For PMP APs in which 2 is set as Authentication Mode, or for PTP masters, this key is implemented, but only if configured to a 32-character string.

Authentication Key Selection If Authentication Mode in the PMP AP is set to Authentication AP Preshared Key: 0 - Use default key. 1 - Use set key.

Authentication Mode Variable to enable/disable authentication. The authentication optional mode is for APs only. This variable can only be set when authentication feature is enabled. 1 - Use a BAM server to authenticate SMs. 2 - Use the Authentication AP Preshared Key in the AP to authenticate SMs.

Authentication Server 4 The IP address of Authentication Sever 4.

Authentication Server 5 The IP address of Authentication Sever 5.

Device Bandwidth Variant Bandwidth variant of the PTP 300, 500, or 600 bridge. Values: bw30MHz, bw15MHz, bw10MHz, bw5MHz, bw20MHz.

Device Channel A Cable Length The length of the cable connected to the telecoms Channel A interface in a PTP 600 bridge, measured in feet. Values: 133 feet, 266 feet, 399 feet, 533 feet, 655 feet.

Device Channel A Loop Back The loopback status of telecoms channel A in a PTP 600 bridge. Values: None, Copper, Wireless.

Device Channel B Cable Length The length of the cable connected to the telecoms Channel B interface in a PTP 600 bridge, measured in feet. Values: 133 feet, 266 feet, 399 feet, 533 feet, 655 feet.


Issue 4 19


Device Channel B Loop Back The loopback status of telecoms channel B in a PTP 600 bridge. Values: None, Copper, Wireless.

Device Channel Bandwidth This control sets the bandwidth of the transmit and receive radio channels in a PTP 600 bridge.

Device Ethernet Link State Current status of the Ethernet link in a PTP 600 bridge. Values: Down, CopperLinkUp, FiberLinkUp.

Device Ethernet Link Type The current speed and duplex of the Ethernet link in a PTP 300, 500, or 600 bridge. Values: Speed1000MbpsFullDuplex, Speed100MbpsFullDuplex, Speed100MbpsHalfDuplex, Speed10MbpsFullDuplex, Speed10MbpsHalfDuplex, SpeedUnknown6.

Device GPS Checksum Enable Enables or disables verification of GPS message checksums.

Device Height Height in meters for a radio relative to its surrounding terrain (not altitude). This release substitutes Device for GPS in the name of this pre-existing attribute. Min Value:-2147483647, Max Value:2147483647.

Device Install Arm State Indicates whether the PTP 300, 500, and 600 bridge is being installed. Values: Disarmed, Armed.

Device Install State Installation alarms and status in PTP 300, 500, and 600 bridges. Values: Ok, WrongMaster, WrongSlave, InvalidSource, RetriesExhausted.

Device Latitude Latitude in decimal degrees. This release substitutes Device for GPS in the name of this pre-existing attribute.

Device Longitude Longitude in decimal degrees. This release substitutes Device for GPS in the name of this pre-existing attribute.

Device OB Management Enable Out-of-band Management control for PTP 600 bridges.

Device OB Management Link State Current status of the out-of-band management link for PTP 600 bridges. Values: Down, CopperLinkUp, FiberLinkUp.

Device OB Management Link Type The current speed and duplex of the out-of-band management link for PTP 600 bridges. Values: Speed1000MbpsFullDuplex, Speed100MbpsFullDuplex, Speed100MbpsHalfDuplex, Speed10MbpsFullDuplex, Speed10MbpsHalfDuplex, SpeedUnknown6.

Device Ping Relay Enable Enables or disables Ping replies from SM WAN interface.

Device Receive Color Code Receive Color Code for a PTP 600 device.

Device Regulatory State The current status of the regulatory check on the PMP master.

Device Telecoms Channel A State Current status of telecoms channel A in PTP 600. Values: Disabled, NoSignalLocal, NoSignalRemote, NoSignalLocalandRemote, Up, RemoteTiming, NoSignalLocalandRemoteTiming

Device Telecoms Channel B State Current status of telecoms channel B in PTP 600. Values: Disabled, NoSignalLocal, NoSignalRemote, NoSignalLocalandRemote, Up, RemoteTiming, NoSignalLocalandRemoteTiming


20 Issue 4


Device Telecoms Channel Selection Indicates which telecoms channels have been enabled in PTP 600. Values: Channel A Only, Channels A and B

Device Telecoms Interface Type Current status of telecoms channel for PTP 300 or PTP 500. Values: Disabled, NoSignalLocal, NoSignalRemote, NoSignalLocalandRemote, Up, RemoteTiming, NoSignalLocalandRemoteTiming

Device Transmit Color Code Transmit Color Code for only PTP 600 devices.

Mirror Capture Port The CMM Port that is set as the Capture port for Mirroring in CMMmicro. Values: Port 1, Port 2, Port 3, Port 4, Port 5, Port 6, Port 7, Port 8.

NAT Connection Type Sets the SM NAT connection type configuration Values: Static IP, DHCP, PPPoE.

NAT Public Gateway Address Sets the NAPT Public Interface Gateway IP on SMs.

NAT Public IP Address Sets the NAPT Public Interface IP on SMs.

NAT RF Public Gateway Address Sets the RF Public Interface Gateway IP on SMs.

NAT RF Public IP Address Sets the NAPT RF Public Interface IP on SMs.

Network DHCP Relay Agent Enable Enables or disables the PMP master acting as DHCP Relay Agent for all SMs and Clients underneath it. 0 - Relay Agent disabled - SM/CPE devices will perform DHCP normally. 1 - Relay Agent enabled - AP will intercept DHCP DISCOVER message from SM and CPE, insert Option 82 containing SM's MAC address, and forward request to specified DHCP server.

Network DHCP Server IP Address DHCP Server IP that will forward DHCP messages from the DHCP Relay Agent in the PMP master. Default is 255.255.255.255 (broadcast).

Network HTTP Access Filter Enables or disables HTTP access filtering in PTP 300, 500, or 600.

Network NTP Sync State SNTP sync state in PTP 600. Values: No Sync, In Sync.

Network Telnet Access Filter Enables or disables Telnet access filtering in PTP 300, 500, or 600.

Packet Filter Direction When NAT is disabled, this attribute in the SM specifies the packet filter To direction. Values: None, Upstream, Downstream, Both. Default is upstream.

Peer IP IP Address of the peer wireless unit for the PTP 600 bridge.

Platform Version Canopy Device Platform Version. Not used for PTP 300, 500, or 600 bridges.

Port 1 to 8 Management Status Allows configuration of the Port as a Management Port in CMMmicro. Values: Off, On.

Port 1 to 9 Mirror Source Rx Enable Enables or disables the Port as Mirror Source Port for Rx in CMMmicro.


Issue 4 21


Port 1 to 9 Mirror Source Tx Enable Enables or disables the Port as Mirror Source Port for Tx in CMMmicro.

Port Mirror Enable Enables or disables Port Mirroring in CMMmicro.

RF Color Code 2 to 10 Additional color codes for PMP radios.

RF Color Code 2 to 10 Priority Priority settings for the additional color codes for PMP radios.

RF Color Code Rescan Idle Timer Time in minutes, configured in the AP, when no unicast RF traffic has occurred before the SM with a non-primary color code rescans. 0 - Rescan without waiting.

RF Color Code Rescan Timer Time in minutes, configured in the AP, for the SM to start the idle timer after a session is started with a non-primary color code. 0 - Disable this timer.

RF DHCP State Sets the SM NAT RF public connection type configuration. Values: Static IP, DHCP.

RF Large VCQ Enable Enables or disables Large VC Qs for SM or PTP slave. Where the uplink is used for camera video feed, enable this attribute.

RF Link Mode Optimization Optimizes the wireless link behavior for the type of traffic to be carried on PTP 300, 500, and 600 links. Values: IP Traffic, TDM Traffic.

RF Peer Max Transmit Power Maximum transmit power that the remote PTP 600 bridge is permitted to use when establishing and maintaining the wireless link.

RF Power Spectral Density Constant power spectral density mode control in PTP 300, 500, and 600 bridges. Values: Constant, FullPower.

RF PTP Link State Current status of the PTP 300, 500, or 600 wireless link. Values: Up, Registering, Searching, Acquiring, Radar CAC, Initializing.

RF Rate Adaptation Sets the RF Rate Adaptation as follows: 0 - No rate adaptation. 1 - 1x and 2x rate adaptation. 2 - 1x, 2x, and 3x rate adaptation (only OFDM). For PMP430 radios, this applies to only Downlink Rate Adapt.

Site Info View Enable Enable non-login users the ability to view Site Information.

SNMP Sync Status Trap Enable Enables or disables the GPS sync/out-sync traps from the CMMmicro agent.

SNMP Trap Port Destination port for SNMP Traps in PTP 300, 500, and 600 bridges.

SNMP Trap Version The SNMP protocol version to use for SNMP Traps in PTP 300, 500, and 600 bridges. Values: SNMP Version 2c, SNMP Version 1.

VLAN Local Setting Enable When enabled, the AP retains its VLAN settings when it is transformed into an SM (for spectrum analysis).

VLAN Setting Sets the VLAN tag type in PTP 300, 500, or 600 bridges. Values: No VLAN Tagging, iEEE8021Q Tagged C TagType 8100, iEEE8021ad Tagged S Tag or B TagType 88a8.


22 Issue 4


VLAN SM Management VID Pass-through

Allows or blocks all MVID traffic ingress at the wired interface to the SM.

VLAN VIDMAC Map MAC1 to 10 MAC address of Port VID Mac Address Mapping table entry of that number for SMs. Syntax: xx-xx-xx-xx-xx-xx.

VLAN VIDMAC Map VID1 to 10 Port VID of VID Mac Address Mapping table entry of that number for SMs. Min Value: 1, Max Value: 4094.

Release 3.3 eliminates the following Prizm attributes that were present in previous releases.

Table 2: Eliminated attributes

Prizm Attribute Name

Bandwidth Actual Uplink Index

Bandwidth DAcks Reserved High

Bandwidth High-Priority Uplink Percentage

Bandwidth Max Uplink Index

Bandwidth Total NumCtlSlots Reserved High

Bandwidth Total NumDAckSlots

Bandwidth Total NumUAckSlots

Bandwidth UAcks Reserved High

Device Ethernet Link Negotiation Speeds

NAT DHCP Client Enabled

Port 9 Description

RF 6.0 Compatibility

RF Antenna Type

RF Background BER Mode

RF Rate

RF Region Code

Signal Strength Ratio

Trap Community 1 to 10

VLAN Allow Only Untagged Frames


Issue 4 23

You cannot configure statistics. However, you can view the values of any of them, except when their values are null or their columns are not selectable because the feature they support is not being used.

Prizm Release 3.3 introduces the following new or changed statistics.

Table 3: New or changed statistics

Prizm Statistic Name Description

Average Radio Power Level Average Receive Power of the radio in dBm for OFDM slave elements.

Bridge FEC bin Bridge CB FEC stats bin.

Bridge FEC bout Bridge CB FEC stats bout.

Bridge FEC btoss Bridge CB FEC stats btoss.

Bridge FEC btosscap Bridge CB FEC stats btosscap.

Bridge FEC uin Bridge CB FEC stats uin.

Bridge FEC uout Bridge CB FEC stats uout.

Bridge FEC utoss Bridge CB FEC stats utoss.

Bridge FEC utosscap Bridge CB FEC stats utosscap.

Bridge RF bin Bridge CB RF stats bin.

Bridge RF bout Bridge CB RF stats bout.

Bridge RF btoss Bridge CB RF stats btoss.

Bridge RF btosscap Bridge CB RF stats btosscap.

Bridge RF uin Bridge CB RF stats uin.

Bridge RF uout Bridge CB RF stats uout.

Bridge RF utoss Bridge CB RF stats utoss.

Bridge RF utosscap Bridge CB RF stats utosscap.

Current Channel Frequency Channel frequency of the AP when the SM is in session.

Current Color Code Color code of the AP in which the SM is registered. If it is not registered, the SM returns the value -1.

Current Color Code Priority Color code priority of the AP in which the SM that returns this value is registered.

DHCP Replies Discarded Number of DHCP replies discarded by the DHCP relay.

DHCP Replies Received Number of DHCP replies received by the DHCP relay.

DHCP Replies Relayed Number of DHCP replies relayed by the DHCP relay.

DHCP Requests Discarded Number of DHCP requests discarded by the DHCP relay.

DHCP Requests Received Number of DHCP requests received by the DHCP relay.

DHCP Requests Relayed Number of DHCP requests relayed by the DHCP relay.


24 Issue 4

In addition, a new management statistic is added: Security Profile Name.

Release 3.3 eliminates the following previously included Prizm statistics.

Table 4: Eliminated statistics

Prizm Statistic Name

BER Bits Received

BER Level

Clear BERStats

Ethernet Rx NUcast

Ethernet Rx Ucast

Ethernet Tx NUcast

Ethernet Tx Ucast

Maximum Jitter

Maximum RSSI

Minimum Jitter

Minimum RSSI

Port 1 to 8 Status

Primary Bit Errors

Radio Signal Strength Index

Radio Sliding Value

Receive Power Maximum

Receive Power Minimum

Secondary Bit Errors

Slave Session Timer


Issue 4 25

Release 3.3 does not support the following SNMP objects that managed devices support.

Table 5: Unsupported SNMP objects

MIB Object Name Object Type

Object Access

Object Description

airDelay Table R/O Round trip air delay in 100-ns increments.

airDelayns Table R/O Round trip air delay in ns increments.

dVLANAcceptDVLANPackets Boolean R/W Allow or disallow packets already doubly-tagged (QinQ) to ingress the FEC of PTP master or slave, or in the SM (not configurable in the AP).

dVLANEnable Boolean R/W Enable or disable DVLAN (QinQ) in the PTP master or slave, or in the SM (not configurable in the AP).

hiPriority Boolean R/W Enable Hi Priority Data Queue in PTP radio.

linkAirDelay Table R/O Round trip air delay between AP and SM, in bits.

linkAirDelayns Table R/O Round trip air delay between AP and SM, in ns.

linkQualityAPData Table R/O Link quality of data that the SM currently is receiving from the AP, relative to the current modulation rate (2X, for example).

linkQualityAPDataMax Table R/O Highest link quality of data that the SM has received from the AP, relative to the current modulation rate (2X, for example).

ntpLogSNMP String R/O NTP Log.

regFailESN String R/O The ESN of the SM that failed to register.

regFailReasonText String R/O Textual description in the AP for the failure of an SM to register in it.1

regFailSeqNum Integer R/O The sequential position of the registration attempt failure.

regFailTime Integer R/O The number of ticks that occurred when the ESN failed to register.

regGrantReason List R/O The registration failure reason.

spectrumAnalysisDisplay List R/W Display for Spectrum Analyzer: 0 - Average over entire period. 1 – Instantaneous, showing the last.

whispFailedRegEntry Table R/O List of Failed ESNs.

whispFailedRegTable Table R/O List of link test results.


26 Issue 4

MIB Object Name Object Type

Object Access

Object Description

whispSmTranslationTable Table R/O SM translation table.

whispSmTranslationTableEntry Table R/O SM translation table entry.

whispTranslationTableAge Integer R/O Age of the registered entity.

whispTranslationTableIndex Integer R/O Index into translation table.

whispTranslationTableIpAddr String R/O IP Address of the registered entity.

whispTranslationTableMacAddr String R/O MAC Address of the registered entity.

NOTES: 1. This object is added to the Registration Failed trap, but not added to Prizm as a statistic.

Attribute names in the Prizm GUI are not necessarily identical to those of corresponding parameters in the module GUIs.

2.3 NEW SUPPORT FOR ELEMENTS Release 3.3 enhances support for pre-existing FSK and OFDM elements and introduces support for the following device types:

Table 6: Devices types newly supported

Product Device Type in Prizm GUI Device Template in Prizm

PTP 110 Master PTP 100 Master (Canopy Backhaul Master Module)

PTP 110 Slave PTP 100 Slave (Canopy Backhaul Slave Module) Canopy_BH.xml

PMP 430 AP PMP 430 AP (Canopy High Performance OFDM Access Point) Canopy_OFDM_AP.xml

PMP 430 SM PMP 430 SM (Canopy Zoltar OFDM Subscriber Module) Canopy_OFDM_SM.xml


Issue 4 27

3 COMPATIBILITY

3.1 SOFTWARE COMPATIBILITY Prizm Release 3.3 has been tested with and supports the following other Canopy products/software releases:

◦ CMMmicro on Release 3.0 ◦ CMM4 on Release 3.0 ◦ PTP 100 Series Ethernet bridges (Canopy BHM and BHS modules) on Canopy

System Release 7.x through 10.3 ◦ PTP 200 Series Ethernet bridges (Canopy BHM and BHS modules) on Canopy

System Release 9.4.3 through 10.3, including in the 5.4-GHz frequency band range

◦ PTP 300 Series Ethernet bridges (25-Mbps High-Speed Backhaul Module, for links up to 155 mi [250 km]) in 5.4- and 5.8-GHz frequency band ranges on V03-02

◦ PTP 400 Series Ethernet bridges (30/60-Mbps High-Speed Backhaul Module) on Release 5845-07-00

◦ PTP 500 Series Ethernet bridges (105-Mbps High-Speed Backhaul Module, for links up to 155 mi [250 km], 99.999% availability) in 5.4- and 5.8-GHz frequency band ranges on V03-02

◦ PTP 600 Series Ethernet bridges (150/300-Mbps High-Speed Backhaul Module) on V08-03

◦ Canopy PMP 100 devices on Canopy System Releases 7.x through 10.3 ◦ Canopy PMP 400 devices (5.4-GHz unlicensed OFDM AP and SM) on

Canopy System Release 9.4.3 through 10.3 ◦ Canopy PMP 430 devices (5.7-GHz unlicensed OFDM High-Performance AP

and Zoltar SM) on Canopy System Release 10.0 through 10.3 ◦ Canopy PMP 500 devices (3.5-GHz licensed OFDM AP and SM) on

Canopy System Release 9.4.3 through 10.3 Prizm Release 3.3 is designed to work properly with Canopy System Release 7.x and later. Basic monitoring, configuration, and authentication functions should work with Release 7.2.9 and later. However, these older system releases were not designed to support some of the Prizm features and element attributes that Prizm Release 3.3 introduces.

The API/SDK that Prizm Release 3.3 accesses through its northbound interface is not part of the Prizm software distribution, but rather must be separately downloaded. The API/SDK bundle must be Version 3.3.


28 Issue 4

3.2 SUPPORTED PLATFORMS AND REQUIREMENTS

3.2.1 OS Platforms for the Prizm Server The server in Prizm Release 3.3 is supported with the following operating systems:

◦ Red Hat Enterprise Linux Version 4.7 or 5.3 ES for 32-bit processors ◦ MS-Windows 2003 Server for 32-bit processors ◦ MS-Windows XP Professional for 32-bit processors

3.2.2 OS Platforms for the Prizm Client Application The Prizm client application in Release 3.3 is supported on only the 32-bit versions of any of the following operating systems:

◦ Red Hat Enterprise Linux Version 4.7 or 5.3 ◦ MS-Windows XP Professional ◦ MS-Windows Vista Business

3.2.3 OS Platforms for Canopy License Manager Licensing servers are supported on any of the following operating systems:

◦ Red Hat Enterprise Linux Version 4.7 or 5.3 ES for 32-bit processors ◦ MS-Windows 2003 Server for 32-bit processors ◦ MS-Windows XP Professional for 32-bit processors

3.2.4 Functions Module Required for the Prizm Server on Windows The Tomcat web server in Prizm Release 3.3 requires that the following functions file is present in Windows: C:\Windows-or-WINNT\system32\msvcr71.dll. The Microsoft C Runtime Library depends on it. Check to ensure that this file is present there. If it is not, then install Prizm Release 3.3 and then copy the file msvcr71.dll from the C:\Canopy\Prizm\_jvm\bin folder in the C:\Windows-or-WINNT\system32 folder. Canopy tracks this issue under Item ID 0012706.

3.2.5 Framework for the Prizm Server on Windows Prizm Release 3.3 requires Microsoft .NET Framework. If .NET is not installed on the local machine, then

◦ Prizm server will not start. ◦ an unsatisfied link error occurs when you try to start Prizm.

To obtain .NET Framework

1. visit http://www.microsoft.com/downloads. 2. click on the link labeled

.NET Framework Version 2.0 Redistributable Package (x86). NOTE: Version 3.0 will work as well.

See also .NET Framework Required for Prizm on Windows on Page 56.

http://www.microsoft.com/downloads


Issue 4 29

3.2.6 Visual C++ Package for the Prizm Server on Windows Prizm Release 3.3 requires Microsoft Visual C++ 2005 SP1 Redistributable Package. This package should be downloaded from the following web site and installed before the Prizm upgrade or fresh installation:

http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en

3.2.7 Upgrades to Release 3.3 Upgrades to Release 3.3 are supported from Releases 2.2 through 3.2. Operators who are using an earlier release should uninstall the earlier release and then perform a fresh installation of Release 3.3.

3.2.8 Dependencies for the Prizm Client Application Although a client computer requires no proprietary code for access to the Prizm server, the following dependencies exist for successful operation of the Prizm client application:

◦ Java must be loaded and enabled on the computer and in the browser that is used to access the main Prizm web page. If an appropriate version of Java is not found on the client computer, Prizm admonishes the user to download and install Java. The Release 3.3 setup tool automatically installs Java.

◦ The browser must support JNLP mime types for Java Web Start. By default for most browsers, this is automatically set in the Java installation.

◦ For all clients (in and outside the U.S.), Java Virtual Machine (JVM) Version 1.6.0 is recommended. The implementation for daylight saving time in this version is compliant.

◦ The Prizm client computer must have port-level communication with Prizm server. If the user is accessing Prizm from a corporate intranet, or is behind another firewall, proxy, or NAT based device, then port access may be problematic. The ports that are required for communication with the Prizm server include − the general communication ports (80 and 12800, by default) − the HTTPS port for Proxy support (8489, by default) − the RMI command ports (12801 to 12900, by default).

◦ If you launch the Release 3.3 client application on a Linux device using Firefox as your web browser, Java Web Start may throw an Unexpected Error similar to the following:

Unable to launch Prizm@localhost.

If this occurs, perform the following steps to point Firefox toward the proper version of Java Virtual Machine (JVM):

1. Install JVM Version 1.6 on the local client device. 2. Launch the Firefox browser. 3. In the menu system of Firefox, select Edit Preferences. 4. Click on Java Web Start.




30 Issue 4

5. In the Action column pull-down menu, select Use other… 6. Browse to and select the Java 1.6 version of javaws.bin.

EXAMPLE: The path to the appropriate file may be java/jre1.6.0_19/bin/javaws.bin.

3.2.9 Databases Prizm accesses the customer databases through Java Database Connectivity (JDBC) application programming interfaces. Each database has a specified XML file for database configuration.

For operator convenience, Canopy suggests some database configuration steps that you can take. However, Canopy does not provide direct support for any database. You should refer any problems that you encounter with the database to the vendor of the database.

The databases that Prizm Release 3.3 has successfully been tested with are as follows.

Database Software JDBC Driver Database

Provided by Installed by Provided by Installed by

Microsoft® SQL Server Enterprise Edition Version 2000on Windows

operator operator operator operator

MySQL Database Server Version 4.1.201 or 5.0 on Linux Linux operator operator operator

MySQL Database Server Version 4.1.201 or 5.0 on Windows

operator operator operator operator

PostgreSQL Version 7.4 on RHEL Linux v4 or Version 8.1 on RHEL Linux v5.3

Linux or Prizm

operator or Prizm Canopy Prizm

PostgreSQL Version 8.2 on Windows

operator or Prizm

operator or Prizm Canopy Prizm

NOTES: 1. No problem with newer builds of Version 4.1 is anticipated.

If you choose to deploy another database that is not part of the list above, then the database may work only if it provides adequate support of SQL, ODBC, and JDBC. This requires some configuration changes and an XML file that correctly maps the field type names and index syntax that Prizm uses to those that the database uses. For specific information on these configuration changes and the database mapping XML file, see the Prizm™ Software Development Kit (SDK).

As database vendors publish later versions of databases that work today with Prizm, Canopy expects that these will also work. However, this depends on continued adequate support of SQL, ODBC, and JDBC.


Issue 4 31

You can maintain SM authentication and bandwidth configuration on a Remote Authentication Dial-in User Service (RADIUS) server. In this case, Prizm acts as the proxy or network access server (NAS) between the AP and the RADIUS server. This release is certified to support either

◦ FreeRADIUS 1.1.3 or 1.1.72 (see TUhttp://www.freeradius.org/UT) ◦ Steel-Belted RadiusP

®P (see

http://www.juniper.net/us/en/products-services/software/ipc/)TP

3PT

Regardless of the RADIUS server vendor, RADIUS should be configured such that no additional delay occurs between when a RADIUS reject occurs and when the RADIUS server responds to the next request.

Prizm and Canopy system software

◦ do not introduce any new MIB objects for monitoring or managing data on the RADIUS server.

◦ do not support the RADIUS Authentication Client MIB, RFC 2618. ◦ do not support the RADIUS Authentication Server MIB, RFC 2619.

3.2.10 Web Browsers The following web browsers have been tested and approved for use with Prizm:

◦ MS-Internet Explorer Version 6.0 or greater ◦ Netscape® Version 7.n or greater ◦ Firefox Version 3.5 or greater

Most other browsers that recognize and support the following can partially or fully work with the Prizm interface:

◦ Java Applets with Java Plug-in 1.4.x, where x is 2 or greater, and Plug-in 1.5 ◦ Java Web Start (JNLP), mime type: application/x-java-jnlp-file

If you experience a nuance with one of these other browsers, please send a description to [email protected].

2 FreeRADIUS 2.x is expressly not supported.

TP

3PT Steel-Belted Radius is a registered trademark of Juniper Networks, Inc.

http://www.freeradius.org/

http://www.juniper.net/us/en/products-services/software/ipc/

mailto:[email protected]


32 Issue 4

3.3 MODULE FIREWALL CONFIGURATION In Release 8.x and later, the Security tab of the Configuration web page in the AP, SM, and BH includes the IP Access Control parameter, as shown in Figure 2.

Figure 2: IP Access Filtering area of Security tab in module GUI

This parameter provides an optional high-level firewall in the module as follows:

◦ When IP Access Filtering Disabled is selected, Prizm can manage the module without being inhibited by the firewall.

◦ When IP Access Filtering Enabled is selected, the IP address of the Prizm server must be entered into one of the Allowed Source IP parameters. Otherwise, the firewall prevents Prizm from managing the module.

3.4 VLAN ID LENGTH The database schema accepts VLAN ID entries of 1,500 or fewer characters. Although Prizm is capable of displaying 1,500 characters and accepts them without indicating an error, the BAM subsystem truncates the entry at 255. Larger entries can result in the BAM subsystem applying incorrect VLAN IDs.


Issue 4 33

4 INSTALLATION TOOL The task or set of tasks that the installation tool for Prizm Release 3.3 offers to perform is based on what the tool detects on your device and what you indicate as you use the tool. The tool detects Prizm and License Manager, and relies on your response about the presence of a database, then offers to perform the tasks described in Table 7.

Table 7: Installer options

What is Currently Installed

Prizm 2.2 thru 3.2

License Manager

PostgreSQLDatabase

Other Database

What the Tool Does at Your Option

●

● ●

● ●

Upgrades License Manager.

Installs Prizm 3.3. Installs License Manager. Installs PostgreSQL 8.2 in Windows or 7.4 in RHEL Linux v4 or 8.1 in RHEL Linux v5.3.

●

● Installs Prizm 3.3. Installs License Manager.

● ●

Upgrades Prizm to 3.3. Upgrades License Manager. Installs License Manager. Installs PostgreSQL 8.2 in Windows or 7.4 in RHEL Linux v4 or 8.1 in RHEL Linux v5.3.

● ● ●

● ● ● Upgrades Prizm to 3.3. Upgrades License Manager.

● ●

● ● Upgrades Prizm to 3.3.

●

Upgrades Prizm to 3.3. Installs License Manager. Installs License Manager. Installs PostgreSQL 8.2 in Windows or 7.4 in RHEL Linux v4 or 8.1 in RHEL Linux v5.3.

The kind of information that the tool will prompt for depends on what is being installed or upgraded. For example, where License Manager is being installed or upgraded, the tool will ask for a Login, Password, LM Port, and Admin Port.

One user account is stored for each Licensing Server. Prizm uses these accounts to authenticate itself on the licensing server. These accounts are required for the case of a redundant licensing server configuration. The Login and Password that the installation tool will ask for in its License Manager Options dialog window are those for authenticating Prizm on the licensing server.


34 Issue 4

The LM Port, with the default number 27000, is the port referred to as

◦ Licensing Port in the License Manager Administrator Tool. ◦ Server Port in the License Manager area of the Prizm Administrator Tool.

This is the port to which Prizm will send its license requests and notifications of licenses forfeited.

The Admin Port, with default number 27443, is the port referred to as Webserver Port in both of those other tools. This is the port for web access to the License Manager Administrator tool.

The installation tool will upgrade License Manager to Release 2.0 where it detects local Release 1.0. However, the tool will not upgrade remote License Manager. In this case, Prizm Release 3.3 will work properly with License Manager Release 1.0, but operator tasks on this License Manager must be done according to procedures in Issue 1 or the Release 3 setup guides (without a GUI into License Manager).

In the case of any Prizm server installation or upgrade, the tool prompts you at the end for whether to open the Prizm Server Administration Tool, in which you should specify important information about the server and the database.

The tool does not install only a database. For a remote database, follow the database installation instructions in the Prizm setup guide. To allow Prizm to update the structure of an existing database, select

1. Use an Existing Database at the Please select Prizm installation options prompt.

2. the option to open the Prizm Server Administrator Tool after the installation tool has finished installing Prizm.

In that administrator tool, provide the information that configures Prizm to use the remote database. With that information, Prizm initializes the databases and migrates its structure to compatible with Release 3.3 when the Prizm server starts. This is a function of the Prizm server, not of the installation tool.

The installation processes are illustrated in the following flowcharts.


Issue 4 35

Detected: no Prizm and no License Manager.

Install ComponentsInstall Components

Install Prizm Server

Install License Manager

InstallPrizm

Prizm OptionsPrizm Options

Install a Database(PostGreSQL)

Use an Existing Database

InstallDB

No

License Manager OptionsLicense Manager Options

Enter TextLogin

Enter TextPassword

27000LM Port

27443Admin Port

InstallLM

YesDatabase OptionsDatabase Options

Refer to Prizm 3.00 Quick InstallScreen For DB Options

Yes

PerformInstallation

SummarizeInstallation

No

No

ItemsSelected

Yes

Prompt/ExitInstallation

No

InstallationCompleted*

Yes

Installed: Prizm if selected, License Manager if selected, PostgreSQL if selected.

Figure 3: Process for fresh installation


36 Issue 4

Detected: Prizm (Release 2.2 through 3.2) and no License Manager

Uninstall PreviousPrizm Version

Install NewPrizm Version

Migrate PrizmSettings

InstallationCompleted

Upgraded: Prizm

Figure 4: Process for Prizm upgrade


Issue 4 37

Detected: License Manager and no Prizm

SummarizeUpgrade

Uninstall PreviousLM Version

Install NewLM Version

Migrate LicenseFiles


License Manager OptionsLicense Manager Options

Enter TextLogin

Enter TextPassword

27000LM Port

27443Admin Port

Upgraded: License Manager

Figure 5: Process for License Manager upgrade


38 Issue 4

Detected: Prizm (Release 2.2 through 3.2) and License Manager

Upgrade Prizm.Don’t Launch Prizm

Admin Tool Yet.

UpgradeLicenseManager


Upgraded: Prizm and License Manager

Figure 6: Process for Prizm and License Manager upgrade

Before you launch the installation tool for a Prizm upgrade, perform the following steps:

1. To preserve log files, device templates, configurations, performance data, and other information from being irretrievably overwritten by the installation, and to safeguard the data in your database (even though new releases use different database schemas), back up the following current data to elsewhere on the computer or onto alternative media: ◦ the Prizm database, according to the administrative guide from your

database vendor ◦ performance statistics files from

InstallationFolder\modules\performance\data ◦ modified configuration files from InstallationFolder\config ◦ custom or modified device templates from

InstallationFolder\modules\devicetemplates 2. Back up the installer tool from your existing release into a safe folder so that you

can reinstall this release if you later want to do so for any reason.


Issue 4 39

3. Ensure that Canopy License Manager has the Release 3.3 Prizm server license mounted.

4. Install .NET Framework and Visual C++ on the server device. (See Framework for the Prizm Server on Page 28 and Visual C++ Package for the Prizm Server on Page 29.)

The defaults in a fresh installation are as follows:

Panel Field Default Setting

License Agreement Installation and Use of Prizm Requires Acceptance of the Following License Agreement

I do NOT accept the terms of the License Agreement

Select Components To Install

Please select the components to install depends on what is detected

Select Prizm Options Please select Prizm Installation Options Install a Default Database (PostgreSQL)

Choose Install Folder Where Would You Like to Install? C:\Canopy\Prizm (Windows) or /usr/local/Canopy/Prizm (Linux)

Login lmadmin

Password lmpassword

LM Port 27000 License Manager Options

Admin Port 27443

Postgres Database Service Account Password PrizmExpress123 (only Windows)

Database Superuser Account Password PrizmExpress123 (only Windows)

PostgreSQL Database Passwords

Password for Database User 'prizm' PrizmExpress123

Prizm Server Admin Tool Would you like to run Prizm Server Admin Tool on installation complete?

Yes for fresh installation No for upgrade

After the installation(s), the installer tool places in the same directory as itself a file named installer.properties. If you ever need to rerun the installation tool and select a different set of options in the tool GUI, you must first delete this file. Otherwise, the new installation will be corrupted.


Issue 4 41

5 DOCUMENTATION

5.1 DOCUMENTS THAT SUPPORT RELEASE 3.3 The following documents support Release 3.3:

◦ Motorola Canopy® Prizm Release 3.3 Server Setup Guide for Linux Platforms, Issue 1, April 2010

◦ Motorola Canopy® Prizm Release 3.3 Server Setup Guide for Windows Platforms, Issue 1, April 2010

◦ Motorola Canopy® Prizm Release 3.3 Server Administration Guide, Issue 1, April 2010

◦ Motorola Canopy® Prizm Release 3.3 User Guide, Issue 3, July 2010 ◦ Motorola Canopy® Prizm Release 3.3 Release Notes, Issue 4, July 2010

(this document)

5.2 INSTALLING THE LATEST DOCUMENTS

IMPORTANT! Read this section carefully and copy any later files as instructed. If you do not, then you may be using Prizm documentation that has been superseded.

The installation tool deposits

◦ iterations of the administration guide and the user guide into the InstallationFolder\bin\tomcat\webapps\prizm\helpfiles folder in Windows or the /usr/local/Canopy/Prizm/bin/tomcat/webapps/prizm/helpfiles directory in Linux on the Prizm server. These books are required for the system response to the Help Help and Help User Guide functions in the client application.

◦ iterations of the administration guide, the user guide, the setup guide specific to your operating system, and these release notes into the InstallationFolder on Windows or the /usr/local/Canopy/Prizm directory on Linux. Since these files sit at the Prizm installation directory level, they are easy for your Prizm server administrator to view for reference at any time and they provide faster access than downloading.

Before the general availability date of the Prizm software release, Canopy performs final testing on it. During and following that testing interval, no changes can be made to the these documents, even changes that arise from final testing, since the installation tool (which will not be modified) already includes these documents.


42 Issue 4

If later iterations are available, then file by file, you need to

1. copy the PDF files that are placed on your computer in the destination directory of your unpack (unzip or untar) operation.

2. paste them into the directories that are cited above (overwrite the PDF files that the installation tool automatically deposited into the Prizm and helpfiles directories).

The result will be that the latest and best information will be available to you as you administer the Prizm server or use Prizm from the application GUI.

5.2.1 Overwriting Documents in Windows The following is a graphical depiction of the overwrite process. For the user guide, you must keep the file name of the new file consistent with the name of the file that you are replacing. The help system depends on that file name (PrizmUserGuide.pdf).

UnzipDestinationFolder\ InstallationFolder\bin\tomcat\webapps \prizm\helpfiles

PrizmAdministrationGuide.pdf PrizmUserGuide.pdf PrizmAdministrationGuide.pdf

PrizmUserGuide.pdf

UnzipDestinationFolder\ InstallationFolder

Prizm_Release_3.3_Release_Notes.pdf PrizmAdministrationGuide.pdf PrizmSetupGuideForWindows.pdf PrizmUserGuide.pdf

Prizm_Release_3.3_Release_Notes.pdf PrizmAdministrationGuide.pdf PrizmSetupGuideForWindows.pdf PrizmUserGuide.pdf

5.2.2 Overwriting Documents in Linux The following is a graphical depiction of the overwrite process. For the user guide, you must keep the file name of the new file consistent with the name of the file that you are replacing. The help system depends on that file name (PrizmUserGuide.pdf).

UntarDestinationDirectory/ /usr/local/Canopy/Prizm//bin/tomcat/webapps/prizm/helpfiles

PrizmAdministrationGuide.pdf PrizmUserGuide.pdf PrizmAdministrationGuide.pdf

PrizmUserGuide.pdf

UntarDestinationDirectory/ /usr/local/Canopy/Prizm

PrizmReleaseNotes_3_30.pdf PrizmAdministrationGuide.pdf PrizmSetupGuideForLinux.pdf PrizmUserGuide.pdf

PrizmReleaseNotes_3_30.pdf PrizmAdministrationGuide.pdf PrizmSetupGuideForLinux.pdf PrizmUserGuide.pdf


Issue 4 43

6 ISSUES RESOLVED WITH THIS SOFTWARE RELEASE

The following issues are fixed in Prizm Release 3.3.

Cold Start Trap from AP Not Triggering Prizm to Note an IP Address Change When an IP address change is made to an AP, the reboot that enforces the change triggers the expected cold start trap to be sent to Prizm. However, when Prizm received this trap, it did not note the change in IP address and was thus not able to configure the element or ascribe new statistical data to it. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0006067.

Defect That May Require Periodic Prizm Server Restart In Prizm Release 3.1 and continuing into 3.2, the Prizm server may have crashed, with the following error thrown to a logs/serviceout_id_xxxxx.txt file:

Exception java.lang.OutOfMemoryError...Out of swap space

Where this issue occurred, it was caused by inadequate swapping capability in JVM Version 1.5 for memory-swapped RRD files related to element performance data. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0012854, 0010901 and 0010639.

History Tab Displaying Simultaneous Null Values for All Attributes The History tab of the Configuration side tab in an element Details view sometimes displayed the values of several configurable attributes as null. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0010230.

Discovery Messages Thrown to Element Configuration History Messages related to element discovery sometimes displayed in the Configuration side tab of the History tab in the element Details pane. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0010815.

Modify Element IP and MAC Not an Alternative Way to Suspend In the user guide section titled "Account State," the advisory has been revised as follows:

IMPORTANT! The Edit menu of the Define Networks tab includes the command option Modify Element IP and MAC, which may be helpful in some equipment replacement scenarios. If your goal is to suspend an SM, this is not a good alternative to suspending customers from a network view. Although a change in the IP address requires the SM to re-register, a change in only the MAC address requires the SM to reauthorize in BAM through the AP. However, the SM retains its MAC address, which the BAM function in Prizm examines for its reauthorization decision. BAM will read the unchanged MAC address and reauthorize the SM, and Prizm will allow it to remain registered.

Canopy tracked this issue under Item ID 0009924.


44 Issue 4

SM Details Temporarily Partial After Move from Provisioned to Managed When the state of an SM was changed from provisioned to full management, the set of element Details available for it may have been partial during the first 30 seconds (or fewer) afterward. During that lapse, a click of the Refresh button causes the full set of Details to display. Canopy tracked this issue under Item ID 0010146 and 0010418.

Exception Error Thrown for Deactivating Alerts Where PostgreSQL is the relational database deployed, Java threw a remote exception error when a defined alert is deactivated in the client. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0009722.

Java Exception When Filtering Alerts The Define Alerts tab failed to post the filtered list of alerts when any Source other than Configuration Manager was selected and threw the Java error unmarshalling return. Similarly, when the User All or PUBLIC was selected after a Source had been selected (and the Java error, if one was thrown, was dismissed), the tab failed to post the applicable alerts and threw a similar unmarshalling return error. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0005981 and 0010813.

Element Type Null in Subscriber Report for SMs in Ignored, Discovered, or Provisioned States Tabular subscriber reports include an Element Type column, whose entries are blank for SMs that are in the Ignored, Discovered, or Provisioned management state. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012923.

Platform Versions for Some Discovered Elements Incorrectly Expressed Tabular network inventory reports include a Platform Version column, whose purpose is to relay P number where the radio sends it to Prizm, else FPGA/HW version. In either case, radios identify their versions to Prizm only when they are fully managed. No version numbers can be displayed for SMs that discovered through their AP link or for SMs that are under BAM-only licensing. This is expected behavior for the Prizm interface. However, Release 3.3 modifies the column title to "Platform/FPGA Version" so that the first case is more readily understood. Canopy tracked this issue under Item ID 0012820 and 0012822.

NAT RF Public IP Not Configurable via Prizm Template In the tree for Prizm attribute selection for inclusion in a custom configuration template, Prizm provided a NAT RF Public Gateway Address attribute that was selectable under the Canopy NAT Configuration NAT Public Interface Configuration branch. However, it did not also provide a corresponding IP address. The raw template will now include a NAT RF Public IP selectable attribute. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0011668.


Issue 4 45

SNMP Proxy SMs That Register in New AP Not Being Polled SMs for which Prizm can detect no routable IP address maintain their communications with Prizm via SNMP proxy, where Prizm has been configured to enable this feature and to use AP Port 61002 to send SNMP proxy messages to the AP. However, if an SM in this scenario registered into an AP other than the one by which it was discovered, and DHCP provided an IP address to the SM (other than the one originally assigned when the SM first registered), Prizm lost its ability to poll the SM. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012093.

CNUT Options Being Available in BAM-only Server CNUT-related functionality is not available in the BAM-only server. However, some CNUT options were present in the interface of this mode. For example, the Manage Packages option was present when the File Settings Edit Settings command option was selected from the main menu. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012202 and 0006191.

Bandwidth Tab Absent From Details for BAM-managed SM The Details pane for an SM in the Provisioned state omitted the Bandwidth tab. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012811.

Dollar Sign in Site Field Affecting Element Details The following advisory is now removed from the IMPORTANT admonishment in the user guide section titled "Using Canopy Element Configuration Templates":

For the Site Name, Site Location, and Site Contact text fields, do not include the $ character in the entry that you type. This can result in Prizm later failing to display some of the details of the element.


Incorrect Option Cited by Email That Provides Temporary Password If you ever forget your password, you can type in your Login ID and select the Forgot Password? link. If more than one email address is associated in Prizm with your account, Prizm prompts you to select the account to which Prizm will send your password. In this case, the system resets your password and sends the new password to the specified email account. This email now properly instructs you to change the password (after you log in via temporary password) by selecting the File Change Password option. Canopy tracked this issue under Item ID 0010616.

Two Predefined Configurable Reports Removed The Bandwidth Usage and Top Bandwidth Users reports were made available because they were providing inaccurate data. These reports are restored to the system. Canopy tracked this issue under Item ID 0010268.

Standard Schedule Creation Time Showing Server Startup Time If you used the Standard Schedule option rather than Occurs once or Occurs multiple times in creating a task, the Creation Time column entry for the task showed the last server startup time instead of the true creation time of the task. Release 3.3 resolves this issue. Canopy tracked it under Item ID 0009760.


46 Issue 4

Type List Sometimes Not Including All Task Types A Refresh operation in the Define Tasks tab sometimes resulted in some task types being not represented in the Type drop-down list. Release 3.3 resolves this issue. Canopy tracked it under Item ID 0010124.

Import Causing Prizm to Identify Generic Device as Generic Group When Prizm imported a .net file, it represented generic elements from the imported network as if they were generic groups. Release 3.3 resolves this issue. Canopy tracked it under Item ID 0009951.

Two Identical Options for Source in Event Filter Dialog If you selected a Source in the Event Filter dialog and clicked OK, Prizm placed two instances of that source into the drop-down list of options for Source the next time you opened the Event Filter dialog. Release 3.3 resolves this issue. Canopy tracked it under Item ID 0010244.

Scroll Bar Not Included in Report View Panel If you shortened the console window when a report was present in the Report Manager tab, and one or more rows of data became no longer viewable as a result, the Prizm interface failed to include a vertical scroll bar that would allow those rows to be viewed. Release 3.3 resolves this issue. Canopy tracked it under Item ID 0010299.

Alerts by Element Type Dashboard Module Displaying Improperly Since the Alerts by Element Type module is a table, expected behavior is to allow position swapping for the columns of the table. Also, expected behavior is that if you set a refresh interval for this module (as a number of minutes that you type into the Refresh Frequency field of the Common tab in the Dashboard Module Settings window), then the module refreshes upon that interval. Release 3.3 resolves this issue. System behavior is now as a user would expect. Canopy tracked it under Item ID 0010617.

Web Server Not Starting After Installation on Linux In an isolated instance, the installation script failed to properly format web server files for use in a Linux platform. Release 3.3 resolves this issue. Canopy tracked this previously unreported issue under Item ID 0012414.

Configurable Values Out of Range for Two VLAN Attributes Prizm allowed users to configure the values 0 and 4095 for the VLAN Management VID and VLAN Untagged Ingress VID attributes, despite that the legal range for each of these attributes is 1 to 4094. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012977.

Login ID Entries in Improper Case Accepted Prizm authentication for the Login ID of users was case insensitive. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0006021 and 0008490.

Authentication for Valid PMP 430 SMs Rejected Registration attempts into PMP 430 APs failed. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0012000.


Issue 4 47

Missing Decimal Point in Element Details for PTP 600 The Information side tab of the General tab in the element details panel for PTP 600 omitted a decimal point for link information, showing 100% link availability as 1000000 instead of 100.0000. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012868.

Configuration Parameter Selection Tree Missing Some RF Max Modulation Mode Attributes Certain BPSK, QPSK, and QAM attributes were not present (not selectable) in the working copy of a custom configuration template for device types PTP 300, 400, 500, and 600. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012834.

Subscriber Report Request Generates Error If No SMs in Network When a Subscriber Report was requested for a network that contained no accepted SMs at the moment, the system threw an error (Report generation failed due to Error retrieving data) instead of generating a report that would show zero SMs. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012819.

RF Antenna Polarization Null in Browser Column When the Configuration side tab of the RF tab in element Details included a value for RF Antenna Polarization, the RF Antenna Polarization column (if selected) in the network browser did not. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012824.

Element Details Misleading for SMs The element Details panel included a blank Filter tab for SMs

◦ that were under BAM-only management. ◦ where NAT was enabled.

Release 3.3 resolves this issue. For the first case, the Filter tab is now hidden. For the second, this tab now displays the message Disabled When NAT Enabled. Canopy tracked this previously undetected issue under Item ID 0012823.

Wrong Availability for Authentication Tabs of SMs The Information side tab of the element Details panel

◦ for a BAM-only provisioned SM under BAM-only management included two Authentication tabs.

◦ for an EMS-managed SM whose AP has authentication enabled had no Authentication tab.

Release 3.3 resolves this issue. In each case, a single Authentication tab is now present in the element Details. Canopy tracked this previously undetected issue under Item ID 0012644.


48 Issue 4

Java Errors for PostgreSQL Updates of Customer Information Where a PostgreSQL relational database is deployed, updates of customer contact information and customer element association were failing with Java errors. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0012686.

Element Count in Browser for Search Results Always Showing Zero When the Search function at the bottom of the client console window was launched, the bar at the top of the resulting network browser showed a total of [0-0]/0, implying that the browser was showing elements arbitrarily numbered zero through zero out of a total of zero elements, even when the browser did properly show listed elements that had met the search criteria.

These number did not update until the user specified a different number of rows to be shown. Release 3.3 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0010637.

Print Preview Truncating Report Data Depending on the length of the data in a report field, the Print Preview and the Saving Report into a PDF-File functions may have truncated the field contents. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0009971.

Polling Threads Seizing for Large Networks Operators of large networks may have experienced RRD reporting issues if a polling task did not complete before the next polling interval began. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0011055.

Maximum Supported Number of Characters for User Passwords If you used the Restrict Minimum Length option while defining a Security Policy, the system did not prevent you from configuring the Minimum Length field to greater than 32 characters, which is the maximum number of characters that Prizm supports in its user Password field. This would have allowed a user to specify as password too long to permit logging into the system.

Release 3.3 checks the Minimum Length field and enforces that its value is not greater than 31. Canopy tracked this issue under Item ID 0009845.

Refresh Required for Network Inventory Report After Prizm Upgrade The Prizm database did not become updated with attributes that were added by a Prizm software upgrade until the first Refresh operation occurred, so the Report Manager could not produce a Network Inventory Report until Refresh had been done. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0006422.


Issue 4 49

Unregistered SMs Automatically Being Moved From Activate to Suspend In random cases, Prizm would briefly display a green, linked icon for an unregistered SM that had been moved to the Suspend and then back to the Activate account state. Shortly after that, Prizm would automatically move that unregistered SM back to Suspend and not allow the operator to move it again to the Activate state. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0012805.

Refresh Operation Losing the Expanded/Collapsed Settings for Elements A refresh of the console may not have resulted in the identical expand/collapse view for each element. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0011000.

Installation Tool Detecting Uninstalled Release The installation tool for at least Release 3.2 reported that it detected Prizm, even though the earlier release on the server device had been uninstalled and the folder for that earlier release had been deleted. The installation tool for Release 3.3 will not detect an uninstalled release of Prizm. Canopy tracked this issue under Item ID 0010624.

Nonfunctioning Help Button in Installer Wizard The wizard of the installation tool for Release 3.2 included a Help button that failed to launch help. In the wizard for Release 3.3, this button is removed. Canopy tracked this issue under Item ID 0011003.

History Tab Null for SM The History tab of the Information side tab in the element details view for an SM that is under either Full Prizm management or BAM management was sometimes blank. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0012812.

Inability to Select All Elements Displayed In a network browser view that includes a large number of elements, an operator may have found that the interface from some point would no longer allow the selection of additional currently displayed elements. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0012833.

Define Notification Dialog Accepting Address Lists Too Lengthy for PostgreSQL Prizm threw an error when a recipient address string (multiple addresses delimited by semicolons) exceeded 128 characters for operators who deploy PostgreSQL as their relational database. The error reflected the fact that the database would not store a string as lengthy as the one entered in the Address(s) field of the Define Notification dialog window, but Prizm allowed the lengthy entry, anyway, since MySQL databases do not impose this limit.

Release 3.3 resolves this issue by disallowing any entry that is longer than 128 characters. MySQL operators do not need to revisit their notifications to shorten strings that are already stored in their databases. Canopy tracked this issue under Item ID 0010257.


50 Issue 4

Delete Selected Files Function Inconsistent in Secure NBI to Prizm Where the server is on a Linux platform and access to the NBI for the Access Web Files option from the startup page is from a device on a Windows platform, the Delete Selected Files button failed to delete any of the checked (selected) files whose names contained a space. To avoid this issue, rename files to remove spaces before uploading them. Release 3.3 resolves this issue.

To remove files that have already been uploaded with spaces in their file names, perform the following steps:

1. Navigate to the /usr/local/Canopy/Prizm/bin/tomcat/webapps/prizm/uploads directory on the Prizm server and delete them.

2. Open the file /usr/local/Canopy/Prizm/bin/tomcat/webapps/prizm/uploaded_files.xml for editing.

3. Delete the uploaded-file tag for any file that you deleted. 4. Save and close this file.


System Losing Status of an Element Following a successful execution of the Find IP/MAC Address command option from the Tools menu, the status indicators for elements that are both returned by the search operation and present under a collapsed node in the network browser view turned white, the color whose purpose is to indicate either BAM-only provisioning of the element or that the element is on the other end of a link with an element for which BAM provisioning or Prizm management is suspended. If no network view is open when the search is conducted, then all elements are collapsed for the purpose of this description.

Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0009893.

Channel Change Traps Not Being Processed for PTP 500 Ethernet Bridges When a channel change occurred in a PTP 500 Series Ethernet bridge and the bridge properly sent the associated trap, Prizm received the trap but could only provide the generic caution Received Unknown Trap. Release 3.3 resolves this issue. Canopy tracked this issue under Item ID 0013064.


Issue 4 51

License Manager Setup via Server Administrator Tool Not Synced Out to License Manager Administrator Tool To avoid authentication errors for failure to retrieve available licenses, any change in the License Manager configuration needed to be identically made in both the server Administrator Tool and the License Manager Administrator Tool at https://hostname:27443. Although this remains the case for syncing the setup out to a remote License Manager (LM) web server, Release 3.3 automatically syncs the setup to a local LM web server, except in Linux via the console script, where the following workaround is required for updating the local LM server:

1. From the initial set of options under Configure Server, enter 5 for Configure Licensing.

2. As you normally would, enter 1 for Server Type in the subsequent set of options under Configure Server and then specify the server (redundancy) type.

Figure 7: License Manager configuration options from Linux console

https://hostname:27443/


52 Issue 4

3. As you normally would under Option 2, configure

◦ Host

◦ Port

◦ Login

◦ Password

◦ Web Server Port

4. Enter 5 for Save given server data for Prizm and local License Web Server. (This option is new in Release 3.3.

Canopy tracked this issue under Item ID 0011282 and 0012708.

Server With Microsoft SQL Server 2000 Failing to Start The Prizm installation tool for Windows improperly set up the Microsoft SQL Server 2000 database for the Alert Manager, which caused Prizm to fail to start wherever this database brand was deployed. For this failure, Prizm threw errors, including SEVERE SYSTEM Start Server failed: java.sql.SQLException: Failed to open table alert_manager_01_10_00.

The installation tool for Prizm Release 3.3.9 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0013549.

Accept and Manage Operation Put DHCP Server Address for NAT SMs into the Management Subnet While configuring the subnet for Prizm to apply to NAT-enabled slave elements, if you selected Enable IP Address Assignment (activating the Auto IP Address Assignment (SM/BHS Configured when Accepted) block, then Prizm would overwrite the LAN IP address and the IP address of the DHCP server, putting them into the subnet from which Prizm will manage the element.

The Prizm Release 3.3.9 installation modifies the Subnet Configuration panel such that the Auto IP Address Assignment (SM/BHS Configured when Accepted) block includes a check box for Assign NAT LAN IP With Management IP (Recommended). If you leave this box unchecked, then

◦ Prizm will not re-assign IP addresses for the LAN access and DHCP server ◦ but if you later disable NAT, then Prizm may lose its management access, since

the management IP address known to Prizm may differ at that time from the management IP address in the SM.

Canopy tracked this previously undetected issue under Item ID 0013818.

Upgraded Server on RHEL OS Crashing The Prizm installation tool for Linux failed to update the file that specifies how Prizm collects and reports on performance data, which may cause the server to crash. The installation tool for Prizm Release 3.3.9 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0013671.


Issue 4 53

Prizm Disregarding Non-default Port Configuration for Licensing Server If the server Administrator Tool properly configured a port other than 27000 for License Manager, the original Prizm Release 3.3 on startup failed to check whether an alternative port was configured, but instead

1. attempted traffic with License Manager at Port 27000. 2. failed to start when License Manager did not respond on that port.

The installation tool for Prizm Release 3.3.9 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0014070.

InstallAnywhere Tool Freezing When Legal Password was Configured for PostgreSQL With a proper configuration in each of the four text boxes of the PostgreSQL Database Passwords panel, a click of the Next button resulted in the tool stalling. The installation tool for Prizm Release 3.3.9 resolves this issue. Canopy tracked this previously undetected issue under Item ID 0014101.


Issue 4 55

7 ISSUES ACKNOWLEDGED WITH THIS SOFTWARE RELEASE

The following issues that may occur during the use of Prizm Release 3.3 are acknowledged.

7.1 ISSUES IN THE INSTALLATION AND UPGRADE PROCESSES You may encounter the following issues during setup operations.

Ports Not Being Released by the <Upgrade From> Software Release The following advisory has been added to the administration guide section on upgrading the Prizm server software:

IMPORTANT! Before you begin the upgrade procedure, stop all services that are running. This will free up the required ports. If the installation tool throws an error about a port not having been released, abort the operation and attempt it again after a short delay. (Some ports may not have been immediately released when the associated service was stopped.)

Canopy tracks this issue under Item ID 0009858.

Installation Tool Unable to Remove Prizm Release 3.1 From Non-standard Path During an upgrade, the Prizm installation tool removes the previous release, except in the case of that release being 3.1 and having been installed on Windows at a path other than C:\Canopy\Prizm. In the exception case, the tool properly throws an error that instructs the operator to uninstall Release 3.1 from its non-standard location and then perform a fresh installation of 3.2. Canopy tracks this issue under Item ID 0010390.

Full Prizm Server Installation on Standalone License Server Keeping LM Login and Password When the full Prizm server is installed on a device that has only a previously installed License Manager server, the installation tool should overwrite the login and password in the License Manager server to the default values lmadmin and lmpassword, respectively. However, the installation tool leaves intact the previously configured login and password. This breaks the relationship between License Manager server and Prizm server, which is installed with the default values for lmadmin and lmpassword.

The workaround is to follow up the installation by reconfiguring the login and password on the Prizm server to match those that were carried forward in the License Manager server. Until this issue is resolved, Canopy will continue to track it under Item ID 0010820.


56 Issue 4

7.2 ISSUES IN CORE Prizm FUNCTIONS You may encounter the following issues as you use the core functions in Prizm.

.NET Framework Required for Prizm on Windows If Microsoft .NET Framework is not installed on the local machine, then

◦ Prizm server will not start. ◦ an unsatisfied link error occurs when you try to start Prizm.

Moreover, if Prizm determines that a critical .NET Framework patch is absent, then it returns an error that advises you to re-install the application (.NET). This is not the correct advice. You must load patches from the Microsoft update page, which does not tag the .NET Framework patches as critical. Thus, even if you have the Microsoft AutoUpdate feature enabled on your Prizm server device, the patches are not automatically downloaded.

The only way to ensure that you have all of the needed patches is to periodically check them against what is available on the update page. Also, be advised that a device reboot is required to put .NET Framework and/or its patches into effect. Canopy will continue to track this under Item ID 0005791.

Inability to Clear Release 8.x Passwords from Elements For elements that run a Canopy system release earlier than 8.x, a Prizm user is able to send a space (for the Management Password attribute) to clear a previously set password. Release 8.x does not support this. For a workaround, use proxy to the element and clear the password in the element GUI. Until this issue is resolved, Canopy will continue to track it under Item ID 0002940.

Data Export from Print Preview Not Guaranteed When print preview is active, the export to text, csv, and xml do not work with the current version of JFreeReport. Until this issue is resolved, Canopy will continue to track it under Item ID 0002990.

Only One SM Listed in Remote Subscribers Tab via Web Proxy With the Web Proxy feature in Prizm enabled in the server, but the Double Proxy feature disabled, the Remote Subscribers tab of the Canopy Access Point should list all SMs registered to that element when you view its Home page, having used the Edit Open Status Page of the Element command option. Each registered SM should be listed on a separate line that contains a disabled link including the element name, MAC address, and LUID number of the SM.

However, this tab is currently displaying with only a single SM listed, regardless of whether Prizm manages the SMs are directly or through SNMP proxy. Until this issue is resolved, Canopy will continue to track it under Item ID 0005197.


Issue 4 57

Authentication Occurred Not Updated to False When authentication is disabled in an AP, Prizm continues to show the value True for the Authentication Occurred attribute for SMs that had authenticated, because it does not receive the authentication disabled traps (even though it consistently receives registration traps). Only if you delete and rediscover those SMs will Prizm show their value as False. Until this issue is resolved, Canopy will continue to track it under Item ID 0005296.

Increments for Task Scheduling and Implementing Vary Task Manager allows you to precisely select when a task that you are defining should be launched. However, Prizm launches tasks on the hour, at 5 minutes after the hour, and on 5-minutes increments after that.

When you schedule the task, if you select the Occurs once option and then click the Not Defined button, then the Choose Start Date dialog allows you to specify the launch time to the minute.

If you select instead the Occurs multiple times option and click Not Defined, then the resulting Schedule Configuration dialog allows you to specify the offset (after the hour) to the second.


58 Issue 4

From this precision, you could assume that the task will launch as specified, but it will launch on the 5-minute increment. Until this issue is resolved, Canopy will continue to track it under Item ID 0005232.

RF Airlink Security Attribute Not Supported In response to the Canopy System Release 8.2 deprecation of the MIB object for air link encryption, Prizm Release 3.0 dropped the RF Airlink Security attribute. Because it did, customers who run one of the earlier system releases can no longer configure that parameter by using this Prizm release. Proper treatment would have been for Prizm to continue to support the attribute so that those customer could use it. Until this issue is resolved, Canopy will continue to track it under Item ID 0005436.


Issue 4 59

Configuration Functions Not Working in Accepting State On elements that are in the Accepting management state, you can impose a set of BAM attribute values by using the Configure command option in a network browser tab, but you cannot update those elements by using any of the following other means:

◦ addProvisionedElement function in the northbound interface ◦ Add Element(s) for BAM Provision or Update Element(s) for BAM Provision

command option in the Define Networks tab of the Prizm GUI. If this worked properly, you could configure the BAM settings in the resulting Provision Network Elements window.

You can use any of these three functions to configure elements that are in the Provisioned state, but none of these to configure elements that are in the Accepting state. Until this issue is resolved, Canopy will continue to track it under Item ID 0005485.

Uncertain Behavior Toward Quarantined Elements During Switch to RADIUS It is not known whether and how Prizm will display elements that were quarantined at the time of a switch from normal database mode to RADIUS mode. For this reason, Canopy recommends that you first delete all quarantined elements before switching. Another alternative would be to add them to RADIUS so that they can authenticate. Until this issue is resolved, Canopy will continue to track it under Item ID 0005915.

Web Proxy Failing if Prizm Launched in HTTP Where Java Version 1.6 is deployed, if you launch Prizm in HTTP (http://PrizmServerIPAddress) and then attempt to use the web proxy feature to access the status page of a network element, an error message indicates that the browser is unable to launch the requested URL. This issue owes to the jnlp BasicService class.

The workaround for this issue is to launch Prizm from in the secure protocol (https://PrizmServerIPAddress:8443). Until this issue is resolved, Canopy will continue to track it under Item ID 0005754, 0007591, and 0010288.

Web Proxy Cannot Download Certain Configuration Files For PTP elements, the web proxy feature in Prizm does not download certain configuration files, and for this reason, Prizm cannot operate the following features in those elements:

◦ Save Configuration File button on the Save and Restore web page ◦ Generate Diagnostics button on the CSV Download web page

Until this issue is resolved, Canopy will continue to track it under Item ID 0005756.

Count of Failed Logins Reaching Lockout Threshold It is possible for so many failed login attempts are made that Prizm will lock out all administrator level accounts. If this occurs, the Prizm server becomes unmanageable unless you directly access the database to reactivate an administrator account. Canopy will continue to track this issue under Item ID 0005034.

http://prizmserveripaddress/

https://prizmserveripaddress:8443/


60 Issue 4

Speed of Reporting to Prizm Affected by License Manager Server Outage The following paragraph has been added to the administration guide to clarify the effect of a License Manager server outage on the speed of reporting license information to Prizm:

If only the server that reports as the master server to Prizm goes down, then reporting to Prizm noticeably slows. If only one of the other servers goes down, then reporting to Prizm noticeably quickens.


Long Pauses in the Network Discovery Process with MySQL While discovering a large network (for example, more than 3,000 elements), the discovery process may unexpectedly and even repeatedly pause for exactly 8 hours or may stall altogether. This occurs because of a timeout that is configured by default for MySQL. The workaround is to reconfigure the timeout to a faster value.

If you encounter this issue

1. find the file my.cnf. NOTE: In Windows, this may be in the Windows folder (for example, C:\WINDOWS or C:\WINNT)4, directly under C:\, or in your MySQL folder (for example, C:\MySQL Server 5.0). In Linux, this should be in the directory /etc.

2. open the file /my.cnf for editing. 3. search for wait_timeout=28800. 4. change 28800 to 1000. 5. write and close the file. 6. restart MySQL so that it read the configuration options in the file.

Canopy will continue to track this issue under Item ID 0009204, 0012851, 0012867, and 0010416.

4 If you are in doubt about what folder this is, select Start Run. In the Open field of the Run

dialog, type in cmd. Click OK. In the resulting DOS window, enter echo %WINDIR%. The system returns the name and path of the Windows folder on your device.


Issue 4 61

Individual Parameters Not Reset When Template Application Appears Successful This can occur when one or more of the attributes or values in a configuration template that is being applied to an element is inappropriate and should simply be ignored by the element. When Prizm sends an invalid value, the following may be observed:

◦ Prizm generates the Warning Failed to set All Parameters for the Element. The associated error details from Source Configuration Manager lists the attribute under Failed Parameters and lists all appropriate attributes that were sent with valid values under Set Parameters. This would be the correct behavior if in fact all others were set.

◦ The element details pane in a network browser indicates in the following areas that all of the appropriate attributes have been reset to the valid values that Prizm sent: − the History tab (of the Configuration side tab) − the General tab (of the Information side tab)

◦ The management web interface of the element itself displays unchanged values for some of the parameters for which Prizm sent appropriate attributes with valid values.


Prizm Sending DFS Update Requests to Non-DFS Radios Prizm may send SNMP update requests for Dynamic Frequency Selection (DFS) to radios that do not support the DFS feature. In this case, the source SYSTEM generates the error Access dfsCount failed. Until this issue is resolved, Canopy will continue to track it under Item ID 0009945.

Relationship Lost When Accept and Manage Interrupted When an Accept and Manage Network Element(s) operation is cancelled before its completion, some of the elements that had been selected for accept and manage may lose their parent-child relationships. Until this issue is resolved, Canopy will continue to track it under Item ID 0010141.

MySQL on Windows Sometimes Requiring Restart Occasionally, the MySQL database will reject the JDBC/ODBC connection. When this occurs, you may see a message like Internal Error on Win 2003 Prizm Server, and Prizm

◦ if already started, keeps trying to re-establish connection to the database and cannot.

◦ if not already started, will not start.

In either case, restart the MySQL database first, and then restart the Prizm server. Until this issue is resolved, Canopy will continue to track it under Item ID 0010323 and 0010417.


62 Issue 4

SMs Provisioned by MAC Address Remaining in Accepting State The user guide procedure titled "Accepting an uninstalled element for BAM-only operations" describes how to provision elements that are not yet installed. However, any element that is provisioned by means of this procedure may stick in the Accepting state instead of automatically moving into the Managed state when the SM next registers. The workaround for this issue is to watch the state after adding the MAC address and, if it does not move beyond Accepting, perform an Accept and Manage operation on the SM. Until this issue is resolved, Canopy will continue to track it under Item ID 0010303 and 0010419.

Authentication Server Requiring Unusually Long Time to Recover from Restart When the Prizm processes are stopped by the Prizm server Administrator Tool, the authentication server can take many minutes, after writing the …bam_engine.txt file, to become available again to APs for BAM-licensed services.

This is observed in Prizm Release 3.2, unlike in previous releases. Until this issue is resolved, Canopy will continue to track it under Item ID 0010392 and 10623. See also the user guide section titled "AP Authentication Setup."

Configuration History Tab Reflecting Changes Not Made By the Prizm Operator In a network where multiple SMs, one of which is not being managed by Prizm, have the same IP address for element management, the Configuration side tab for the History tab in the Details pane for an element (example shown below) may display changes that the Prizm operator did not induce.

Figure 8: History tab of Configuration side tab, example

These changes enter the log in Prizm when the managed SM goes out of service and the non-managed SM responds to messages that Prizm sends to the IP address of the intended (managed) SM.

The workaround for this issue is for the operator to ensure that no IP addresses are used in both the managed and the non-managed subsets of the network. Until this issue is resolved, Canopy will continue to track it under Item ID 0010816 and 0010229.


Issue 4 63

Configurable Parameters Assuming Alternate Values Without Operator Action In rare and unpredictable cases, the values of certain configurable parameters may change back and forth without any operator action. This may be seen in the following parameters:

◦ VLAN Profile and the following associated parameters: − VLAN Untagged Ingress VID − VLAN Membership

◦ Software Version ◦ FPGA/HW Version ◦ RF Frequency List


Profiles Automatically Adopting New Names Without any action by the operator to cause this, the names of bandwidth service plans and VLAN profiles in Prizm may change. When this occurs, it seems to be without pattern as well. Until this issue is resolved, Canopy will continue to track it under Item ID 0010814.

Elements Locked in Unprovisioned State In rare instances, some elements become locked in the database as Unprovisioned. When this occurs

◦ the elements are visible in a browser view of their network, where by design no command option is available for deleting the elements so that they can be rediscovered.

◦ the elements are not visible in the Network Elements list in the Define Networks tab, where the command option Delete Network Element(s) does exist.

So, such elements cannot be deleted by using the Prizm client application interface. However, they can be deleted by exercising the following eight SQL CLI command lines directly upon the Prizm database:

delete from nodemgr_element_performance where element_id=xxxx; delete from nodemgr_element_attribute where element_id=xxxx; delete from nodemgr_element_link where element_id=xxxx; delete from nodemgr_element_link where link_element_id=xxxx; delete from nodemgr_element_tag where element_id=xxxx; delete from nodemgr_network_element where element_id=xxxx; delete from bam_sm where element_id=xxxx; delete from bam_bad_sm where element_id=xxxx;

It would be both unnecessary and unwise to ever use these commands to removed a Managed element, but these commands do provide the workaround for removing any stuck Unprovisioned elements. Until this issue is resolved, Canopy will continue to track it under Item ID 0010905.


64 Issue 4

Disabled Default Tasks Automatically Re-enabled After Reboot Through the Edit Deactivate Task command option in the Define Tasks tab, you can disable any task, which will remain in that state until you optionally undo the action through the Edit Activate Task command. This is the expected behavior for all tasks, but the actual behavior for only operator-defined tasks. The following tasks are defined and activated by the Prizm installation tool and are automatically re-activated whenever Prizm reboots:

◦ Access Point – Unregistered Unit ◦ Backhaul – Unpaired Master ◦ Backhaul – Unpaired Slave ◦ Element – Ethernet Down ◦ Element – Invalid Software Version ◦ Element – Poll Failed ◦ Element – Recently Rebooted ◦ Element – SNMP Management Disabled ◦ RF – dBm Threshold Monitor

If you prepare to keep any of these deactivated, remember to deactivate them whenever the Prizm server has rebooted. Until this issue is resolved, Canopy will continue to track it under Item ID 0010909.

VLAN Profiles Unable to Set SM Management VID Pass-Through Although the protocol that BAM uses to push VLAN profiles to SMs supports most VLAN attributes, it does not support the Management VID Pass-Through attribute. The workaround for this issue is to set this attribute via SNMP (configuration template). Until this issue is resolved, Canopy will continue to track it under Item ID 0010079 and 0009717.

Bandwidth Service Plans Unable to Set MIR and CIR Parameters Although the protocol that BAM uses to push bandwidth service plans to SMs supports most bandwidth attributes, it does not support the MIR and CIR attributes. The workaround for this issue is to set these attributes via SNMP (configuration template). Until this issue is resolved, Canopy will continue to track it under Item ID 0010037 and 0009536.

Inability to Change Geolocation Attributes When you use a custom template to push new geolocation attribute values to an element, you may find that these values are unchanged in the element itself, despite that a success message is logged. If you encounter this intermittent issue, the workaround is to use the web proxy feature to populate the geolocation parameters directly in the management interface of the element. Until this issue is resolved, Canopy will continue to track it under Item ID 0012716.


Issue 4 65

7.3 ISSUES IN THE Prizm CLIENT INTERFACE You may encounter the following issues as you use the Prizm GUI.

No License Checkout Error Logged in Applying Configuration Window If you attempt to apply a bandwidth configuration that requires a floating license, and Prizm requests but cannot obtain a floating license for any of the elements selected for the Configure operation, no error appears in the Applying Configuration window, where events associated with the Configure operation are logged. A workaround for this issue is to open and monitor an Event Viewer, looking for BAM alerts that are Critical, or to monitor the element(s) in a Network Browser view, looking for the Critical indication in the status icon(s). Until this issue is resolved, Canopy will continue to track it under Item ID 0003089.

Database and Prizm GUI Supporting Longer VLAN Entries Than BAM Subsystem Does The database schema accepts VLAN ID entries of 1,500 or fewer characters. Although Prizm is capable of displaying 1,500 characters and accepts them without indicating an error, the BAM subsystem truncates the entry at 255. Larger entries can result in the BAM subsystem applying incorrect VLAN IDs.

Status Indicator Color Not Red for Unrecognized Trap Alert When Prizm receives a trap from a device whose custom template either does not define the trap or defines it, but the trap is not automatically acknowledged, Prizm generates the alert Unknown SNMP Trap Error. This severity of this alert is Critical. An alert of this severity should cause the element status indicator for this device to be red, but instead is not affecting the color. Until this issue is resolved, Canopy will continue to track it under Item ID 0004234.

Prizm Reporting Incorrect Distance for 900-MHz SM For only the 900-MHz modules, the following distance amounts are exactly half of the correct value:

◦ Distance shown in the Details pane for the SM ◦ Max Distance and Average Distance shown in the Details pane for the AP ◦ distances shown in the following columns:

− RF Link Distance Km − RF Link Distance Mi − RF Link Avg. Distance Km − RF Link Avg. Distance Mi

Until this issue is resolved, Canopy will continue to track it under Item ID 0004108. Prizm reports correct distances for all other SMs.


66 Issue 4

Moved Elements Appearing in New and Old Positions After a move operation to reposition elements in the hierarchy, the system deselects the moved elements, but may display them in their original places as well as in their new places in the hierarchy. If it does, this is not an indication that the move operation failed or that Prizm continues to associate them with their former location.

To work around this issue, you can click Ignored Elements in the left-hand pane, then Network Elements in the left-hand pane, and see the refreshed display that has the elements in only their new location. Until this issue is resolved, Canopy will continue to track it under Item ID 0001303.

Licensing Information Window Sometimes Showing 0 for Available Licenses Occasionally and regardless of Prizm release, the Licensing Information window may indicate that no licenses other than the default element licenses are available when some are. This results from the interaction between the licensing software and some file contents that are not present in every license file. When this occurs, both the total license count and the checked out license count are wrong.

The workaround for this issue is to execute lmutil lmstat –a on the License Manager server. This command always returns the accurate numbers of Canopy licenses and checkouts. Until this issue is resolved, Canopy will continue to track it under Item ID 0004347.

Erroneous Numeric Values in Details Graphics In some instances, labels on an axis of a graph in the details pane for an element may display values that are both incorrect and peculiar. For example, an AP slicing value of 474 has been displayed as 9999999998175. The licensing agreement for the matheval third-party library prevents Canopy from modifying the library to prevent such errors. An example of the erroneous display is shown in Figure 9.

Figure 9: Example erroneous label on graph


In another example, the axis labels for a receive or transmit errors graph or for a link loss graph may display incorrect and peculiar values. Until this issue is resolved, Canopy will continue to track it under Item ID 0010781.


Issue 4 67

Color Key Overlaying Key Text In some graphical content tabs5 of the details pane for an element, the color box in the key for the graph covers the text of the key. This issue also results from characteristics of the matheval third-party library. An example of the erroneous display is shown in Figure 10.

Figure 10: Example color key covering key text


5 The Ethernet Traffic, Link Information, or RF Traffic tabs.


68 Issue 4

Prizm Console Window Opening Off-screen If you switch from a multiple-monitor to a single-monitor setup, the Prizm console may open outside the limits of your current screen. In a Windows platform, the workaround is to right click on the Start menu, select Move, and use the arrow keys to move the window back to the primary screen; then exit and launch the Prizm client application again. Until this issue is resolved, Canopy will continue to track it under Item ID 0004685.

SM Not Reflecting New VLAN Membership Until Reboot If you use a VLAN profile in Prizm to change the VLAN membership for a Canopy Subscriber Module, the change will not be reflected in the GUI of the SM until the SM has been rebooted. This is an anomaly of the SM. Until this issue is resolved, Canopy will continue to track it under Item ID 0003241.

Nonexistent Elements Being Discovered Element discovery by HTTP can result in

◦ nonexistent elements being included in the discovered elements list ◦ the following error message, posted to the Discovering Network Elements

window: Discovered new Element via HTTP, requires a password that is not in the Default Password List

When this occurs, Prizm marks the elements with a ? in place of an element type icon in the discovered list and in network browser windows, as shown in Figure 11.

Figure 11: Question mark shown as element type for HTTP-discovered elements

These elements are IP addresses that are within the discovery range and valid for the defined subnet but not associated with any discovered or discoverable devices. The workaround is to not check the HTTP Scan (Canopy Elements Only) option in the Discover Network Elements window, except to discover a known device that both has a known IP address and fails to respond to SNMP requests. Until this issue is resolved, Canopy will continue to track it under Item ID 0005087.


Issue 4 69

Column Selections Discarded If Search Dialog is Not Cleared If you make any selections in the Select Columns window (either from the full list or from the short list returned by the search feature) and/or any were already selected when you clicked the button, and then you do a new search and select more, afterward be sure to clear the contents of the Search dialog before you click the OK button. Otherwise, only the columns selected in the current short list are displayed after you click OK.

Proper behavior would be for all selected columns to remain selected, except for any whose checkbox you uncheck. Until this issue is resolved, Canopy will continue to track it under Item ID 0000005259.

Deleted Service Plan or VLAN Profile Can Be Applied If you begin to provision an element for BAM, and then the bandwidth service plan or VLAN profile that you have selected is deleted (for example, by another user account who is simultaneously logged in) before you finish, Prizm allows you to apply the deleted service plan or profile. Preferable behavior would be to disallow the provisioning and provide an informative error message about the deletion. Until this issue is resolved, Canopy will continue to track it under Item ID 0005832.

Client Lockup First License Manager Server Goes Down When the first server listed in the License Manager panel of the PrizmEMS Administrator Tool goes down, the Prizm client application interface may lock up for about ten minutes. If it is not feasible to bring that server back up, perform the following steps as a workaround:

1. Navigate to the …Canopy/Prizm/bin directory. 2. Launch the script ServerAdminTool.bat or ServerAdminTool.sh. 3. Select Action PrizmEMS Server Stop. 4. In the left panel of the tool interface, click License Manager. 5. After the License File Data options open in the right panel

a. switch the first listed server with either of the others. b. click the Save Configuration button.

6. If your Prizm server is on a Windows boot device a. select Start Run. b. in the Open field of the Run dialog, type regedit. c. click OK. d. in the left panel of the Registry Editor, click to highlight

My Computer HKEY_LOCAL_MACHINE SOFTWARE FLEXlm License Manager.

e. in the right panel, click to highlight MOTOCNPY_LICENSE_FILE.


70 Issue 4

f. select Edit Modify. g. In the Value data field, reorder the servers so that the failed server is no

longer listed (for example, 27000@lm2,27000@lm3,27000@lm1;). If your Prizm server is on Linux, edit the file /root/.flexlmrc so that the failed server order is no longer listed.

7. Select Action PrizmEMS Server Start. Until this issue is resolved, Canopy will continue to track it under Item ID 0010109.

Slow Reaction to Show Licensing Option If the client application users complain of the Prizm GUI seeming to hang, rather than promptly displaying the Licensing Information window (more than a minute passes after they select Help Show Licensing from the main menu), you can modify one of the following files on the Prizm server, so that the file points to only the current license locations:

◦ My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager in the Windows registry

◦ the file /root/.flexlmrc on Linux.

Then ask a Prizm client user to retry Help Show Licensing. This workaround is not successful in every case. Until this issue is resolved, Canopy will continue to track it under Item ID 0001225.

Authentication Account State Not Updated for SM Removed from RADIUS If you remove the record of an SM from the RADIUS server, then Prizm will properly deny future authentication attempts from that element. However, Prizm will fail to update the Authentication Account State attribute and fail to mark the element with the Suspend icon in network views. The workaround for this issue is to delete the element from Prizm. Until the issue is resolved, Canopy will continue to track it under Item ID 0005914.

Possible SNMP Failure Reaching a CMM4 A CMM4 supports a Community String value that contains one or more spaces, and Prizm does not. Thus, if a CMM4 in your network has its Community String value configured with at least one space, Prizm SNMP messages to that CMM4 will fail. The workaround is to use the proxy feature in Prizm to open the direct web interface to the CMM4, reconfigure the string without any spaces, and ensure that Prizm is using the same string syntax for this element. Canopy will continue to track this potential issue under Item ID 0004614.

No Indication When an Element Is Read Only If you attempt to use Prizm to write to an element that is set up for read only (discovered and accepted from a subnet for which Enable Element for Monitoring (Read Only) had been configured), the Prizm interface does not inform you that the element is read only. Canopy will continue to track this potential issue under Item ID 0001616.


Issue 4 71

HTML Session Dropped After Configuration Push As with CNUT, although the support tool creates a file with links that you can click through to access the interfaces of Canopy devices that are operating, if you make any configuration changes to an element in this way, the element may drop its session with your browser. If this occurs, it has no effect on whether Prizm can open a subsequent browser session to its management interface. Until the issue is resolved, Canopy will continue to track it under Item ID 0008211.

Various Treatments of Number and Type of Characters in Site Names Among Prizm Releases 2.x and 3.x and PostgreSQL and MySQL databases, each handles the number of characters in site names differently. PostgreSQL limits, and Prizm Release 2.x did limit, site names to 50 characters. MySQL does not impose a limit but truncates the contents. The management web interfaces on Canopy radios accept only 32 or fewer characters, but Prizm Release 3.x accepts up to 128 characters in its Site Name attribute. However, the InterNiche TCP/IP stack supports only 64. Canopy does not track these various treatments as a problem, but advises operators accordingly.

Special characters in site names can also appear to be incompatible with the Prizm interface. This owes to the fact that SNMP messages carry the site name contents as octet strings. Prizm can accept elements that have special (non-ASCII) characters in their site name parameters, but may display their Site Name attributes as colon-separated octet strings (for example, 52:54:2d:4e:44:20:41:50:20:23:20:31…).

Operators who want to altogether avoid difficulties in site name storage and translation can limit the configuration of each Site Name attribute to 64 or fewer ASCII characters in Prizm Release 3.2 and remember that proxy visits to element interfaces may not reflect the same contents in the Site Name parameter.



72 Issue 4

Clarification Needed for Source of Bandwidth Values The following content is added to the "Managing Bandwidth by Service Plans" section of the user guide.

The following table indicates the conditions under which Prizm applies to an SM values from either a bandwidth service plan or a custom configuration template.

Table 8: Prizm source for bandwidth values

Prizm Applies to the Device Configuration

Source Parameter in AP Auth Occurred Field for SM

Auth Enabled Parameter in AP

database SM2

enabled BSP1 BSP true

disabled CCT BSP

enabled CCT CCT any (SM, BAM, or BAM+SM)

false disabled CCT CCT

NOTES: 1. BSP represents bandwidth service plan. CCT represents custom configuration template. 2. The following exception exists: if both the bandwidth service plan and the configuration

template push a value for the Bandwidth Broadcast MIR attribute, then the value in the template is applied in the SM.


Unexpected Behaviors in Dashboard Prizm allows you to add modules to or subtract modules from your custom dashboard. Any change that you make may result in the whole dashboard being vertically scrollable because a portion of it is hidden by the vertical constraints of your console window size. This behavior is contrary to the purpose of having a dashboard, which is to have all of the summary information that you preselected as important available at a glance. When the dashboard is in this condition, you can restore it to its original appearance by clicking on, or even hovering the mouse cursor over, the Dashboard tab.

However, this causes the dashboard to immediately display a maximum of six modules. This action is helpful only when you want the original dashboard restored. For example, if you added modules and they are currently displayed (more than six total in the dashboard), you will lose that configuration from the immediate display if you run the mouse cursor to the tab and be able to see it only if you scroll downward. See the next two figures.


Issue 4 73

Figure 12: Dashboard with added (seventh) module


74 Issue 4

Figure 13: Dashboard after click or hover on tab

The highlighted vertical scroll bar in Figure 13 indicates that the seventh module is accessible via scrolling.


Tabs Not Closing Tabs become not closable after they have been moved by the or button. These buttons function properly to scroll tabs into or out of visibility when the horizontal size of the console window is so small as to not allow all of the open tabs to be viewed at the same time.


Issue 4 75

However, tabs that have been moved persist, even after the associated button has been clicked. If the window can be resized larger such that all open tabs are in view, then any of these tabs can be closed.


Some Elements Not Moving to Ignored Elements List The user guide procedure titled "moving an element to the Ignored Elements list" should work in all cases, but some of the checked (selected) elements may not move, while others do. The workaround is to

1. identify remaining elements that should have been moved 2. ensure that they are checked 3. invoke the Edit Move Element(s) to Ignore List. command option again until

all elements that should be moved have successfully been moved.


Bandwidth Usage Chart Displays in Byte Units After Conversion to Bit Charts The administration guide procedure titled "Changing chart units from bytes to bits" should result in all of the following chart types being converted:

◦ RF Traffic ◦ Ethernet Traffic ◦ Bandwidth Usage

However, the Bandwidth Usage chart does not convert from bytes. This is consistent with how Prizm displays column data for bandwidth statistics in a network browser, even after conversion of the other two charts to bits, but perhaps not as intended by the operator who performs the conversion.



76 Issue 4

Changed IP Address Associated With NAT Private IP in Configuration History Prizm puts the management IP address of a discovered SM appropriately into the Management IP Address attribute, except when it rediscovers the SM and finds that its IP address has changed. In this case, Prizm puts the new IP address into the NAT Private IP Address attribute and keeps the original address in the Management IP Address attribute. These can be seen in the History tab of the Information side tab in the element details view and in the columns of the two attributes, when these are selected for a network browser view. This treatment lasts until the SM reboots.

At that point, WM discovers the SM at its new IP address and puts that address into the Management IP Address attribute. Canopy tracks this issue under Item ID 0009733.

Button for Information About the Application Not Functional For most views in Prizm, the Print Preview option opens a faithful presentation of what would result from the Print operation. This presentation includes several icons above the formatted content, much as an ordinary window does. However, the information icon does not function:

This button promises, but does not open to, "information about the application."


Scroll Horizontally Option for Dashboard Ignored The Common tab of Dashboard Module Settings window includes options to Scroll Horizontally and Scroll Vertically.

Figure 14: Dashboard Module Settings Window

Scroll Vertically works as expected in only the Licensing Information module. For example, if you uncheck Scroll Vertically for the Recently Accepted Elements module, the vertical scroll bar is still present if the number of elements exceeds the number that can be simultaneously displayed in the available space.


Issue 4 77

The Scroll Horizontally option does not work in any of the modules. You can check and uncheck it, click OK, and finish the dashboard configuration with apparent success, but the check mark for this top option will have no effect on your dashboard.


Persistent End Time Selection List for Event Filter in Linux An operator whose server and client application are both on a Linux platform may find that the drop-down list for End Time in the Event Filter dialog persists after the calendar (Set End Time dialog) opens for the Custom option. The workaround is to drag the calendar dialog away from the persistent list. Until this issue is resolved, Canopy will continue to track it under Item ID 0010259.

Elements from Previous Window Appearing in New Window for a Split Second In the Define Networks tab, an empty Network Elements or Discovered Elements window may be seen for a fraction of a second as having elements that were present in the last previous window. After that split second, those elements disappear and the empty window properly displays as empty. Until this issue is resolved, Canopy will continue to track it under Item ID 0010190.

Search Category Listed Twice Sometimes a search performed from the Status bar of the main Prizm console results in a duplicate of the search category being added to the drop-down list of categories.


Tooltip for Some Elements Being Out of the Console Window For some elements, the pop-up tooltip may be outside the scope of the current console window, depending on how quickly you are moving the mouse cursor in a network view. Until this issue is resolved, Canopy will continue to track it under Item ID 0010600.


78 Issue 4

Sessions Tab Displaying Incomplete and/or Inaccurate Information The Sessions side tab of the User Manager tab may show void cells in the user table

or may contain inaccurate information about the users and their sessions. This is particularly the case with the LoginID, Established, Duration, and Type fields of the table. Until this issue is resolved, Canopy will continue to track it under Item ID 0010603.

Updates to EMS Primary Status of SNMPAccounts Not Enforceable The OK button in the SNMPAccounts tab of the Update Profile window is greyed out (unavailable to commit changes to the EMS Primary field of accounts).

The workaround for this issue is to

1. highlight to select the account. 2. click the Remove Account button. 3. click the Add Account button. 4. select the account name to add to the profile. 5. click the OK button. 6. select the desired (checked or unchecked) status for EMS Primary. 7. click the OK button.



Issue 4 79

Duplicate Elements Tree in Home Configuration Operators whose Home configuration includes both a network elements tree in the Define Networks tab and either a Define Tasks or a Define Alerts tab may see two instances of the tree in response to the selection of the File Settings Go To Home Configuration command option. Java Swing is not properly repainting the screen.

The workaround is to click on the alternative tab (Define Tasks or Define Alerts) and then click on the Define Networks tab. This removes the duplicate copy of the tree. Until this issue is resolved, Canopy will continue to track it under Item ID 0010312.

Error Thrown for Selection of All Devices Types in PostgreSQL Deployment With Prizm Upgrade For an operator whose relational database is PostgreSQL and who upgraded to Prizm Release 3.3, the Prizm GUI may throw an error when an attempt is made to select all device types in the definition of an alert by advanced criteria. If you experience this issue, contact Technical Support, who will provide assistance in the following workaround:

◦ If user defined alerts are present, Technical Support will help you save the data associated with those alerts.

◦ If either no user defined alerts are present or the data from existing alerts has been saved − Technical Support will help you remove the database table named

alert_manager_01_10_00. − Technical Support will ask you to restart your Prizm server.
