Wm4 0 userguideissue3
0 likes1,094 views
This document provides a user guide for Cambium Wireless Manager (WM) System Release 4.0. It describes launching and using the WM client application, including supported device types, configuring proxies and passwords, using the client window and toolbar, alarm views, applications tree, search utility, and performing operations in table views. The guide also covers help menu options, managing multiple client windows, and references other important WM documents.
![WM Release 4.0 User Guide Issue 3
May 2012
added support for
− PTP 250 Master and Slave as read‐only elements
− PTP 300, PTP 500, and PTP 800 Master and Slave as Version 05‐00. See the caveat in
Clarifications on Page 46.
− PTP 400 Master and Slave as Version 09‐01.
− more attributes of the Extreme Switch.
− PMP 320 Release e2.3. For the AP, this includes
Network Configuration attributes for SNMP version (v1/2c or v3), web access
security (HTTPS or HTTP), and serial interface (CLI or uGPS).
read‐only attributes for GPS location, the active service flow count, and the
frequency range and restriction mode of the AP.
performance tables for UL and DL MCS counters of registered CPE's MCS and HARQ
stats.
a frame utilization table used by the native Frame Utilization tool in WM but hidden
from user configuration templates.
updates to the Upload AAA Certificate utility, tables for user management and trap
destinations, and the Slots Measurement, MAC Version, backoff values (for DL, UL,
and ECINER), Sync Source, Selected DL/UL Ratio, and Sync Status attributes.
commands that Save Configuration Command, Reboot Device, Clear [service flow]
Counters, and Clear [MCS] Statistics.
introduction of performance statistics for the following data:
‐ received/transmit data rate
‐ received IP packets with and without VLAN tag
‐ received non‐IP packets with and without VLAN tag
‐ received packets classified and unclassified
‐ DL and UL MCS state of each registered CPE
‐ antenna method of each registered CPE.
elimination of the need for operators to have their own physical map licenses. This is
reflected in About License Tab on Page 80.
a means to terminate a rogue or runaway client session while other concurrent sessions
continue. See Terminating a Client Session on Page 683.
changes in the integrated software upgrade utility. See
− Upgrading Devices On Demand on Page 287.
− Setting the General Configuration on Page 289.
− Setting the SM Autoupdate Configuration on Page 290.
synchronization functions (buttons) added to the WM Server panel of the WM Administrator
Tool to launch removal of all events, alarms, and traps in process, while leaving all elements'
statistics untouched. See Using the WM Server Panel on Page 684.
removal of trap port configurability and trap parser interfaces.
removal of the System Administration web interface.
45](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-45-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
6.4 Operations on a Device
The Inventory view panel supports right‐click menu options. Right click on an entry in the table to
display the drop‐down list of options that are available at that time or for the currently selected
(highlighted) network elements.
The top‐level selections in these right‐click menus are an identical list of options for all of the various
devices. Beneath the top level, some braches are device specific as follows:
For only PMP AP and SM devices (including OFDM but not PMP 320), the Launch branch
includes a link that opens a client session in BAM, the server that processes authentication
attempts from SMs and manages their bandwidth service plans and VLAN profiles.
For only high‐speed PTP backhaul master and slave devices that support it, the Launch
branch includes a link that launches the PTP LinkPlanner tool.
For only child WMs, the Launch branch includes
− a link to Client, which opens a WM client session into the child WM.
− no link to [the device] WebPage like every other element has.
For generic elements (see Generic Elements (Non‐Cambium Devices) on Page 51 for the
definition of this device type), the Launch branch is absent.
The options that are available for all elements through their right‐click menu are as shown
in Figure 90.
Figure 90: Right-click options common for all elements
137](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-137-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
The meanings of these fields are as follows.
Table 21: Event filter custom view criteria fields
Field Description
Specify name for the custom view you are creating or modifying. If no value is specified in
Filter View
this field, the custom views are created with default values, such as Network Events0,
Name
Network Events1, Network Events2.
Choose the parent tree node under which your custom view has to be placed in the tree
from the drop‐down box.
ParentName
The criteria set for the parent custom view will be automatically used for child custom
view. Hence, it is enough to specify only additional criteria for the child custom view.
Choose the severity of the event based on which you need to filter events in your custom
view from the editable drop‐down box.
Severity
For multiple severities, type the severity as comma separated values. For example,
Major,Info.
Specify all or part of a message associated with the events you want to view.
Message Example: If the message is specified as Interface failure. Status poll failed., then only
events with this message are displayed in the custom view.
Category Specify the category of the events you want to view. For example, Topology.
Specify the domain name of the events to be displayed in this view. The domain‐specific
Domain information is based on physical location, or functional categorization, or logical
categorization of the source of the event.
Network Specify the network to which the source of the event belongs.
Node Specify the name of the node based on which the events are to be filtered.
Specify the name of the failed entity (that is primarily responsible for the event) based on
Failed Object
which the events are to be filtered.
Source Specify the source of the event based on which the events are to be filtered.
From The events occurred after the time specified in this field [Month, Date, Year, Hour, Min,
Date/Time Sec, AM/PM] are displayed in the custom view.
To The events occurred up to the time specified in this field [Month, Date, Year, Hour, Min,
Date/Time Sec, AM/PM] are displayed in the custom view.
357](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-357-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
The meanings of these fields are as follows.
Table 25: Alarm filter custom view criteria fields
Field Description
Specify name for the custom view you are creating or modifying. If no value is
Filter View Name
specified in this field, default values, such as Alarms0, Alarms1, Alarms2 are created.
Choose the parent tree node under which your custom view has to be placed in the
tree from the drop‐down box.
ParentName The criteria set for the parent custom view will be automatically used for child
custom view. Hence, it is enough to specify only additional criteria for the child
custom view.
Choose the severity of the alarm based on which you need to filter alarms in your
custom view from the editable drop‐down box.
Severity
tip…………………For multiple severities, type the severity as comma
separated values. For example, Major,Minor.
In the drop‐down list, choose the previous severity of the alarms you want to view
from the editable drop‐down box. For example, if you want to view alarms that
Previous severity were previously minor and then became critical, select Minor is this field.
tip…………………For multiple severities, type the severity as comma
separated values. For example, Major,Minor.
Specify the name of the owner with whom the alarm is associated.
tip…………………To create a custom view for alarms that are un-owned
by any user, set the value as null. For multiple
Owner owners, specify owner names as comma separated
values.
Example: If the value is set as "Ed", then only the alarms owned by "Ed" are
displayed in the custom view.
Category Specify the category of the alarms you want to view. For example, Topology.
Specify the group based on which the alarms are to be filtered.
Group Example: If the group is specified as it‐test, then only alarms forming a part of this
group id are displayed in custom view.
Specify all or part of a message associated with the alarms you want to view in the
created custom view.
Message
Example: If the message is specified as Node Clear., then only alarms with this
message are displayed in the custom view.
Specify the name of the failed entity (that is primarily responsible for the alarm)
Failure Object
based on which the alarms are to be filtered.
Source Specify the source of the alarm based on which the alarms are to be filtered.
From Date/Time The alarms modified after the time specified in this field [Month, Date, Year, Hour,
(modified) Min, Sec, AM/PM] are displayed in the custom view.
373](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-373-320.jpg)
![Issue 3 WM Release 4.0 User Guide
May 2012
Field Description
To Date/Time The alarms modified up to the time specified in this field [Month, Date, Year, Hour,
(modified) Min, Sec, AM/PM] are displayed in the custom view.
From Date/Time The alarms generated after the time specified in this field [Month, Date, Year, Hour,
(created) Min, Sec, AM/PM] are displayed in the custom view.
To Date/Time The alarms generated up to the time specified in this field [Month, Date, Year, Hour,
(created) Min, Sec, AM/PM] are displayed in the custom view.
Choose the mode in which you need to group the alarms in a custom view from the
drop‐down box.
max – the alarms of maximum severity are grouped and displayed at the
GroupViewMode beginning of the list.
latest – the newest alarms are grouped and displayed at the beginning of
the list.
none – the alarms are not grouped.
Specify age of the alarm based on which the alarms are to be filtered. Age of an
alarm denotes the time lapsed since the last modification of the alarm in the Web
NMS system.
By default, the value specified is Any, whereby alarms of all age is displayed.
Other options are: minutes, hours, days, today, and, yesterday.
Alarm age
Example: Age in hrs > 1 displays all the alarms that are less than an hour old. After
(modified time)
this custom view is created, the alarms are dynamically added to the view as they
satisfy the criteria of being less than an hour old. In this case, the old alarms remain
in the view. If you require to delete the old alarms and need to view only those
currently satisfying the criteria, set the minutes in which the custom view should be
refreshed in Refresh period in minutes (by default, it is set as 1 minute). On setting
this, the server sends data automatically at the time interval specified.
Event and Alarm filter criteria dialogs include an Additional Criteria button. If you click this button,
WM opens an additional criteria dialog. See Figure 254 on Page 359. The More button in this window
adds a single Property Name/Match Criteria correlated pair of fields each time you click it. To add
three pairs, for example, click the More button three times. The Fewer button removes a pair.
To specify what columns your new custom view should include, click the Select Props To View
button.
374](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-374-320.jpg)
![Issue 3 WM Release 4.0 User Guide
May 2012
note ............. If the graph displays only a zero value for a count type of statistic, this is because a
constant value was received from the agent as a result of the first two observations. The
difference is zero, and this is shown. This scenario can happen as the saveAbsolutes
property value of a statistic is set to false by default, causing the displayed value to be
the difference between successively collected values. If the saveAbsolutes value was set
to true, then the absolute value would be plotted and a zero value would not occur often.
The following messages are possible when you launch the Current statistics window.
Table 29: Possible messages in a current performance data graph
Message Reason
Fetching Data.... The data is being collected from the device.
No Response from agent This is no response from the agent running in the device. This
could indicate that the element is down.
Cannot plot [Data is String type] The collected data from the device is of string type and the
graph can not be plotted.
The table view of the collected statistic can be remarkably useful, since it calls out each historical
value in a table where you can read individual numbers. The table view is also the only way to view
non‐numeric values.
When you dismiss this window, WM will discard the values that it collected and will not save them in
the database.
13.3.2 Viewing a Collected Performance Statistic
The collected view of a performance statistic shows historical data collected in the past and is useful
for identifying trends or focusing on time frames, such as blocks of time during which problems tend
to arise. To launch the collected graph viewer, right‐click on the target statistic in the Configured
Collection view and select PlotCollected Statistic from the drop‐down list of options.
The Collected statistics graph opens in a separate window. This window provides not only the graph
style options that are summarized in Table 28 on Page 384, but also data options in the right panel,
headed Data Range Settings. The default range is the last previous 24 hours. If you switch the setting
to another, click the Plot Chart button at the bottom of the panel to effect the change.
386](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-386-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
Figure 271: Collected statistics window, line graph
The following messages are possible when you launch the Collected statistics window.
Table 30: Possible messages for a Collected statistics window
Message Reason
No data available By default, automatic data collection starts 5 minutes after the WM Server is started
and any devices are discovered. In addition, data collection for a newly added statistic
also starts after 5 minutes. However, the delay is configurable and can be set according
to your network requirements.
note………………For Counter type OIDs, the initial data collected is not
stored. When data is collected for the second time, the
difference between the two values is calculated and
stored. Depending on the polling interval set, the data will
be collected a second time. Therefore, it is possible that
there will be more delay in plotting the graph data when
working with Counter type OIDs.
Cannot plot [Data is The collected data from the device is of string type, therefore a graph will not be
String type] plotted.
Date Range Setting The From date and To date that you set in Custom Date Range Settings are incorrect.
incorrect Check for the date/time values set and click Plot Chart again.
[From‐Date is greater
than To‐Date]
The graph options for this view are summarized in Table 28 on Page 384. This view supports zooming,
auto‐ranging, printing, and saving as a PNG file. These options are available through a right‐click
anywhere in the graph area.
387](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-387-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
Table 31: AP performance reports
System Report Name Statistic Values Reported
AP Bridge Table [per Device Name (Device ID)]
Summary SM MAC, ocal UID, Age, Extension [timeout extension flag] , Hash
L
Device ID, Device Name
AP Ethernet Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards , Rx Errors , Tx Bytes Tx Broadcast, x
, , , T
Multicast , Tx Discards Tx Errors
,
Device ID, Device Name
Type, ite Contact , Site Location, Software Version Platform Version, FPGA Version ,
S ,
AP General Status
Uptime, Regulatory, hannel Bandwidth , Cyclic Prefix, egistered SM Count , Color
C R
Code Region Code, Temperature
,
Device ID, Device Name
AP QOS Summary Uplink Sustained Rate, Downlink Sustained Rate, Uplink Burst Allocation, Downlink
Burst Allocation, Downlink Rate, Broadcast Downlink CIR
Device ID, Device Name
AP Radio Statistics Rx Bytes Rx Broadcast Rx Multicast, Rx Discards Rx Errors , Tx Bytes Tx Broadcast, x
, , , , T
Multicast , Tx Discards Tx Errors
,
[per Device Name (Device ID)]
AP Session Table
MAC, Session Uptime, Session State, Reg Count, Re‐reg Count, Average Jitter,
Summary
RSSI (dBm), Air Delay (nsec)
[25 highest with total bytes]
AP Top 25 Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated
Errors
Device ID, Device Name
AP VLAN Configuration
Enabled, Local Setting Enabled, Allow Only Tagged Frames, Dynamic Learning, Ageing
Summary
Timeout, Management VID
PMP AP Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab]
Summary Report Graphs and/or tables [optionally specified in Input Data tab]
Table 32: PMP 320 AP performance reports
System Report Name Statistic Values Reported
PMP 320 AP Ethernet Device ID, Device Name
Statistics Rx Bytes , Rx Discards , Rx Errors , Tx Bytes Tx Discards Tx Errors
, ,
Device ID, Device Name
PMP 320 AP General
Type , Site Name, Site Contact , Site Location, Software Version Device Version Uptime ,
, ,
Status
Center Frequency , Base Station ID
PMP 320 AP Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab]
Summary Report Graphs and/or tables [optionally specified in Input Data tab]
389](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-389-320.jpg)
![Issue 3 WM Release 4.0 User Guide
May 2012
System Report Name Statistic Values Reported
Index, Service Class Name
PMP 320 AP QOS
MIR, Min Reserved Rate, Max Latency, Data Delivery Type, Unsolicited Grant Interval,
Summary
Unsolicited Poll Interval
Device ID, Device Name
PMP 320 AP Radio
Uplink CINR (0), plink RSSI (0), ownlink CINR (0) , Downlink RSSI (0) , Uplink CINR (1) ,
U D
Statistics
Uplink RSSI (1) , Downlink CINR (1), ownlink RSSI (1)
D
PMP 320 AP Service SM MAC, SF Index
Flow Summary Direction, QoS Profile ID, Classification Rule ID
[25 highest with total bytes]
PMP 320 AP Top 25
Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated
Report
Errors
Table 33: SM performance reports
System Report Name Statistic Values Reported
PMP FSK SM Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab]
Summary Report Graphs and/or tables [optionally specified in Input Data tab]
PMP OFDM SM
[for number of days back specified in Input Data tab, devices specified in Devices tab]
Graphical Summary
Graphs and/or tables [optionally specified in Input Data tab]
Report
SM Bridge Table [per Device Name (Device ID)]
Summary Device MAC, ocal UID, Age, Extension [timeout extension flag], Hash
L
Device ID, Device Name
SM Ethernet Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards , Rx Errors , Tx Bytes Tx Broadcast, x
, , , T
Multicast , Tx Discards Tx Errors
,
Device ID, Device Name
Type , Site Contact Site Location , Software Version , Platform Version, FPGA Version ,
,
SM General Status
Uptime, Channel Bandwidth , Cyclic Prefix , Registered To , Color Code, Channel
Frequency Transmit Power Level, Region Code Temperature , Air Delay, itter
, , J
Device ID, Device Name
Uplink Sustained Rate, Downlink Sustained Rate, Uplink Burst Allocation, Downlink
SM QOS Summary
Burst Allocation, Broadcast MIR, High Priority Channel Enabled, High Priority Uplink CIR,
High Priority Downlink CIR, Low Priority Uplink CIR, Low Priority Downlink CIR
Device ID, Device Name
SM Radio Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards Rx Errors , Tx Bytes Tx Broadcast, x
, , , , T
Multicast , Tx Discards Tx Errors
,
390](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-390-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
System Report Name Statistic Values Reported
[25 lowest with value]
Receive power
[25 highest with value]
SM Top 25 Report Jitter
[25 highest with total bytes]
Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated
Errors
Device ID, Device Name
SM VLAN Configuration
Allow Only Tagged Frames, Dynamic Learning, Ageing Timeout, Management VID, SM
Summary
Management Pass‐through VID, Untagged Ingress VID
Table 34: PMP 320 CPE performance reports
System Report Name Statistic Values Reported
PMP 320 CPE Ethernet Device ID, Device Name
Statistics LAN Rx Bytes, LAN Tx Bytes WAN Rx Bytes , WAN Tx Bytes
,
Device ID, Device Name
PMP 320 CPE General Type , Site Name, Site Contact , Site Location , Software Version , Hardware Model,
Status Center Frequency (kHz), evice Bandwidth (kHz), p Link Data Rate (Kbps) ,
D U
Up Link Modulation Type Down Link Data Rate (Kbps), Down Link Modulation Type
,
PMP 320 CPE Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab]
Summary Report Graphs and/or tables [optionally specified in Input Data tab]
PMP 320 CPE Radio Device ID, Device Name
Statistics Rx Bytes Rx Discards Rx Errors , Tx Bytes Tx Discards Tx Errors
, , , ,
Device ID, Device Name
PMP 320 CPE Service
SFID, CID, BCID, Type, State, Direction, Enabled, Scheduling, Max Rate (bps), ARQ
Flow Summary
Enable, HARQ Enable, Rules
[25 lowest with value]
RSSI
[25 highest with value]
PMP 320 CPE Top 25
CINR
Report
[25 highest with total bytes]
Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated
Errors
391](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-391-320.jpg)
![Issue 3 WM Release 4.0 User Guide
May 2012
Table 35: PMP Backhaul performance reports
System Report Name Statistic Values Reported
PMP Backhaul Bridge [per Device Name (Device ID)]
Table Summary SM MAC, ocal UID, Age, Extension [timeout extension flag] , Hash
L
Device ID, Device Name
PMP Backhaul Ethernet Rx Rate(bytes/sec) , Rx Broadcast Rate(packets/sec), x Multicast Rate(packets/sec),
R
Statistics Rx Discards, x Errors , Tx Rate(bytes/sec), x Broadcast Rate(packets/sec) , Tx Multicast
R T
Rate(packets/sec) Tx Discards, Tx Errors
,
Device ID, Device Name
PMP Backhaul General Type, ite Contact , Site Location, Software Version Platform Version, FPGA Version ,
S ,
Status Uptime, Channel Bandwidth , Color Code Region Code, Registered SM Count,
,
Temperature
PMP Backhaul Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab]
Summary Report Graphs and/or tables [optionally specified in Input Data tab]
Device ID , Device Name
PMP Backhaul Radio Rx Rate(bytes/sec), x Broadcast Rate(packets/sec), x Multicast Rate(packets/sec),
R R
Statistics Rx Discards, x Errors , Tx Rate(bytes/sec) , Tx Broadcast Rate(packets/sec) , Tx Multicast
R
Rate(packets/sec) Tx Discards Tx Errors
, ,
PMP Backhaul Top 25 [25 highest with total bytes]
Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Errors
Device ID, Device Name
PMP Backhaul VLAN
Enabled, Local Setting Enabled, Allow Only Tagged Frames, Dynamic Learning, Ageing
Configuration Summary
Timeout, Management VID
Table 36: PTP performance reports
System Report Name Statistic Values Reported
PTP VLAN Configuration Device ID, Device Name
Summary Enabled, Management Priority, Allow Only Tagged Frames, Management VID
Device ID, Device Name
PTP Ethernet Statistics Rx Bytes, x Non Unicast Rx Unicast , Rx Discards Rx Errors, x Bytes , Tx Non Unicast
R , , T ,
Tx Unicast , Tx Discards Tx Errors
,
Device ID, Device Name
Type, ite Contact , Site Location, Software Version PGA Version , Uptime, Region
S ,F
PTP General Status Code Bandwidth RF Receive Channel RF Receive Frequency, RF Receive Modulation
, , ,
Mode , RF Receive Power , RF Transmit Channel , RF Transmit Frequency RF Transmit
,
Modulation Mode , RF Transmit Power
PTP Graphical Summary [for number of days back specified in Input Data tab, devices specified in Devices tab]
Report Graphs and/or tables [optionally specified in Input Data tab]
Device ID, Device Name
PTP Radio Statistics
Rx Bytes, Rx Discards, Rx Errors, Tx Bytes, Tx Discards, Tx Errors
392](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-392-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
System Report Name Statistic Values Reported
[25 highest with total bytes]
PTP Top 25 Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated
Errors
PTP VLAN Configuration Device ID, Device Name
Summary Enabled, Management Priority, Allow Only Tagged Frames, Management VID
WM also provides preconfigured reports of
Inventory Summary (see Figure 273)
Device Uptime (see Figure 274 on Page 394)
Figure 273: Inventory Summary report
393](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-393-320.jpg)
![Issue 3 WM Release 4.0 User Guide
May 2012
note ............. If the Rediscovery Interval is set using Regular Interval option, then the values set for
Specific Dates and Days of Week options will not take effect.
Procedure 80: To set rediscovery on specific dates
1. Click General tab in the Discovery Configurator.
2. Click the Rediscovery button.
The Rediscovery Scheduler dialog is displayed.
3. Click the Specific Dates option.
Figure 279: Rediscovery Scheduler, Specific Dates
4. To choose a specific date on which the rediscovery occurs, click the appropriate date option:
◦ All: Selects all the dates of a month and indicates rediscovery occurs every day.
◦ Specific: Constitutes a range of days. For example, if you select 5 and 15, then the
rediscovery will take place from the 5th to 15th of every month.
When a particular month does not have the specified date, the rediscovery will occur
based on the “number of days” difference between the current month and the next
month. For example, if the specified date is 31 and the current month is October. As per
this configuration, the rediscovery should occur after a range of 31 days. But the next
month, November, does not have 31. In this case, rediscovery will be scheduled for
December 1st (i.e., current month date 31 + specified date [31]). This is because all
these calculations are in terms of milliseconds. Similarly if the date is specified as 31 and
the current month is February (28 days), then the rediscovery will be scheduled for
March 3.
408](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-408-320.jpg)
![WM Release 4.0 User Guide Issue 3
May 2012
14.5 Viewing the Discovery Log
The Discovery Configurator includes a Discovery Log tab, where important events in the discovery
process are captured with their results.
Figure 294: Discovery Log
These are success examples. The following are examples of discovery failure events that the log
calls out.
Figure 295: Failure events in the Discovery Log
[02 Aug 2010 13:25:43:774] DISCOVERY(10.60.2.43:254): Unable to write to device
while testing Write Community. Device is currently not writeable. Device's Write
Community must be set manually.
[02 Aug 2010 13:27:55:562] PING: [THREAD:: Thread-138] SNMP Ping failed for device
10.60.2.15.Snmp Properties:: ,RemotePort=161,SnmpRetries=0,TimeOut=1
[07 Aug 2010 24:22:45:483] PING: [THREAD:: statuspoll-2] SnmpPing failed for device
10.50.7.253.SnmpPing Properties::
Community=public,RemotePort=0,SnmpRetries=3,TimeOut=1 Version=v2
[06 Aug 2010 20:04:56:015] PING: [THREAD:: pool-5-thread-3] ICMP Ping failed for
device 192.168.101.1
433](https://image.slidesharecdn.com/wm40userguideissue3-120727051552-phpapp01/85/Wm4-0-userguideissue3-433-320.jpg)
Wm4 0 userguideissue3
- 1. Cambium Wireless Manager User Guide System Release 4.0 Issue 3 May 2012 © 2012 Cambium Networks. All Rights Reserved.
- 3. Table of Contents Accuracy...................................................................................................................................... 2 Copyrights ................................................................................................................................... 2 Restrictions ................................................................................................................................. 2 License Agreements.................................................................................................................... 2 1 About This User Guide ..................................................................................43 1.1 Continuing Features...................................................................................................... 43 1.2 Features New in Release 4.0......................................................................................... 44 1.3 Clarifications ................................................................................................................. 46 1.4 References to Other WM Documents .......................................................................... 46 1.5 Links to Other Important Documents........................................................................... 47 1.6 Feedback on This Guide ................................................................................................ 48 2 Supported Device Types ................................................................................49 2.1 Cambium Networks Device Types ................................................................................ 49 2.2 Generic Elements (Non‐Cambium Devices).................................................................. 51 2.3 Subordinate WM Servers.............................................................................................. 53 3 Launching the Client ......................................................................................61 3.1 Dependencies ............................................................................................................... 61 3.2 Corporate Networks ..................................................................................................... 61 3.3 Launch Procedures........................................................................................................ 62 3.4 Configuring the Proxy on the WM Client...................................................................... 65 3.4.1 Setting Proxy Information in the Java Control Panel ............................................................ 66 3.4.2 Setting Proxy Information in the Web Browser .................................................................... 68 3.4.3 Troubleshooting an "Unable to launch the application" Error ............................................. 69 3.5 Configuring Your Password........................................................................................... 72 3.6 Troubleshooting an Unsuccessful Login ....................................................................... 73 4 Using the Client Window................................................................................75 4.1 Using the Toolbar.......................................................................................................... 75 4.2 Using the Alarm Summary Views.................................................................................. 77 4.3 Using the Status Bar...................................................................................................... 78 4.4 Using the Display Panel................................................................................................. 78 4.5 Using the Menu Bar ...................................................................................................... 79 4.6 Using the Help Menu .................................................................................................... 80
- 4. 4.6.1 About Wireless Manager....................................................................................................... 80 4.6.2 Help Contents........................................................................................................................ 85 4.6.3 Diagnostics ............................................................................................................................ 86 4.7 Managing Client Windows............................................................................................ 86 4.7.1 Navigating through Active Windows..................................................................................... 86 4.7.2 Detaching a Window from the Client.................................................................................... 86 4.7.3 Saving Location and Size of Windows ................................................................................... 87 4.7.4 Closing All Open Windows .................................................................................................... 87 4.8 Using the Applications Tree .......................................................................................... 87 4.8.1 Custom Views ........................................................................................................................ 90 4.8.2 Frame Operations.................................................................................................................. 92 4.8.3 Administration Tools ............................................................................................................. 92 4.9 Using the Search Utility................................................................................................. 92 4.10 Performing Table View Operations ............................................................................ 102 4.10.1 Navigating Through a Table ............................................................................................ 103 4.10.2 Setting the Page Length for a Table................................................................................ 104 4.10.3 Refreshing the Page View ............................................................................................... 104 4.10.4 Viewing a Range of Table Details.................................................................................... 104 4.10.5 Sorting Table Details ....................................................................................................... 104 4.10.6 Rearranging and Resizing Columns in a Table ................................................................ 105 4.10.7 Viewing Row Details ....................................................................................................... 105 4.11 Importing Data Files Into WM .................................................................................... 105 4.12 Exporting Data Files From WM................................................................................... 108 4.12.1 Exporting Device Discovery Information ........................................................................ 109 4.12.2 Exporting User Account Information .............................................................................. 111 4.12.3 Exporting Network Hierarchy Information ..................................................................... 113 4.13 Recovering from a Lost Connection to the Server...................................................... 114 5 Monitoring the System Dashboard.................................................................115 5.1 Dashboard Refreshes.................................................................................................. 115 5.2 Dashboard Display Options ........................................................................................ 116 5.3 Strategic Use of the Dashboard .................................................................................. 118 5.3.1 Click‐throughs From the Dashboard ................................................................................... 119 5.3.2 Sortable Table Displays ....................................................................................................... 120 6 Using an Inventory View ...............................................................................121 6.1 Inventory View Edit Menu Options ............................................................................ 123 6.1.1 Delete Object and Traces .................................................................................................... 123 6.1.2 Clear Alarms ........................................................................................................................ 123
- 5. 6.1.3 Delete Alarms ...................................................................................................................... 123 6.1.4 Search.................................................................................................................................. 123 6.2 Inventory Custom Views............................................................................................. 126 6.3 Topology Data Exports................................................................................................ 136 6.4 Operations on a Device............................................................................................... 137 6.5 Operations on a Network ........................................................................................... 142 6.5.1 Start/Stop Discovery ........................................................................................................... 142 6.5.2 Status Update for the Network ........................................................................................... 143 6.5.3 Delete Object and Traces of the Network........................................................................... 143 6.5.4 Credential Manager for the Network.................................................................................. 143 7 Using the Physical Map ................................................................................145 7.1 Importing the Geo‐locations....................................................................................... 145 7.2 Importing Addresses................................................................................................... 148 7.3 Displaying the Physical Map ....................................................................................... 150 7.3.1 Available Formats for Online Maps..................................................................................... 151 7.3.2 Format of Offline Maps ....................................................................................................... 151 7.4 Generating a Physical Map View of an Element Selected in the Inventory View ...... 154 7.5 Viewing Collocated and Proximal Elements ............................................................... 155 7.6 Panning ....................................................................................................................... 159 7.7 Jumping to a Different Position in a Physical Map ..................................................... 160 7.8 Refreshing a Physical Map .......................................................................................... 160 7.9 Setting Physical Map Options ..................................................................................... 161 7.9.1 Selecting Links, Coverage, and Standards Types to Display on a Map Type ....................... 161 7.9.2 Using the RSSI Auto‐Threshold Feature .............................................................................. 169 7.9.3 Filtering the Icons to Display by Current Alarm Level ......................................................... 169 7.9.4 Setting Whether Elements Appear Based on Zoom............................................................ 170 7.9.5 Using or Hiding Other Physical Map Overlays..................................................................... 171 7.10 Viewing Details in the Physical Map ........................................................................... 174 7.10.1 Accessing Data for a Device in the Physical Map............................................................ 174 7.10.2 Accessing the Geolocation of a Selected Point or Device in the Physical Map .............. 179 7.10.3 Accessing the Street View of a Selected Point or Device in the Physical Map ............... 180 7.10.4 Accessing a Physical Map Device in Other Management Views..................................... 181 7.11 Importing a BroadbandPlanner Prediction................................................................. 182 7.12 Changing the Geolocation for a Device ...................................................................... 182 7.13 Checking the Log of a Physical Map............................................................................ 184 7.14 Exporting a Map.......................................................................................................... 184
- 6. 7.15 Exporting Devices to BroadbandPlanner .................................................................... 190 7.16 Exporting the Network into XML ................................................................................ 191 7.17 Exporting Locations for Use in a Child WM ................................................................ 192 7.18 Notices Regarding Physical Maps ............................................................................... 192 8 Viewing Information About a Specific Device ..................................................195 8.1 Updating the Status of a Device or a Network ........................................................... 195 8.1.1 Updating Status on Demand ............................................................................................... 195 8.1.2 Adjusting the Status Polling Intervals.................................................................................. 195 8.2 Viewing Basic Properties............................................................................................. 198 8.3 Viewing Component Properties.................................................................................. 200 8.4 Viewing Events for a Device........................................................................................ 201 8.5 Viewing Alarms for a Device ....................................................................................... 202 8.6 Viewing Performance Data for a Device..................................................................... 203 8.7 Viewing the Dashboard for a Device .......................................................................... 204 8.7.1 Examples of Network Element Dashboards ........................................................................ 204 8.7.2 Features of Network Element Dashboards ......................................................................... 219 8.7.3 Interactive Components of Network Element Dashboards ................................................ 221 8.8 Viewing a Device Summary Report............................................................................. 223 8.8.1 Running a Device Summary Report on Demand ................................................................. 223 8.8.2 Running a Device Summary Report on a Schedule ............................................................. 226 8.8.3 Saving a Device Summary Report........................................................................................ 226 8.8.4 Deleting a Device Summary Report .................................................................................... 227 8.9 Finding the Customer Assigned to the Device............................................................ 227 9 Performing Other Operations on Devices .......................................................229 9.1 Keeping Device Identifiers Unique ............................................................................. 229 9.2 Managing or Unmanaging a Device............................................................................ 229 9.3 Pinging a Device .......................................................................................................... 230 9.4 Dropping a Subscriber Session.................................................................................... 232 9.5 Checking Relationships Presumed Based On Geo‐locations ...................................... 232 9.6 Removing a Relationship ............................................................................................ 233 9.7 Adding Relationships Among Devices......................................................................... 234 9.7.1 Defining a Larger Extended Family...................................................................................... 234 9.7.2 Adding a Single Relationship ............................................................................................... 235 9.8 Importing a Customer Contact Database ................................................................... 238 9.8.1 Preparing the Customer Contact Data for Import .............................................................. 238
- 7. 9.8.2 Importing Customer Contact Data ...................................................................................... 240 9.9 Assigning a Customer to a Device............................................................................... 242 9.10 Editing or Removing a Customer Record.................................................................... 246 9.11 Sending an Email Notification to a Customer............................................................. 247 9.12 Refreshing Device Data............................................................................................... 248 9.13 Setting WM Credentials for a Group of Selected Devices .......................................... 248 9.14 Configuring a Device ................................................................................................... 250 9.15 Syncing the SNMP String in WM with the SNMP String in a Device........................... 250 9.16 Using the Link Capacity Test Utility ............................................................................ 250 9.16.1 Launching a Link Capacity Test ....................................................................................... 250 9.16.2 Interpreting Link Capacity Test Results........................................................................... 253 9.16.3 Errors in the Link Capacity Test Feature ......................................................................... 254 9.17 Using the Spectrum Analyzer Utility........................................................................... 254 9.17.1 Launching Spectrum Analyzer......................................................................................... 254 9.17.2 Interpreting Spectrum Analyzer Results ......................................................................... 256 9.17.3 Errors in the Spectrum Analyzer Feature........................................................................ 257 9.18 Accessing the Web Interface of a Device ................................................................... 257 9.19 Deleting an Object and Traces.................................................................................... 261 9.20 Using the Bandwidth and Authentication Manager (BAM) Subsystem ..................... 262 9.20.1 Managing Authentication ............................................................................................... 264 9.20.2 Managing Bandwidth...................................................................................................... 266 9.20.3 Managing VLANs ............................................................................................................. 274 9.21 Running a User‐defined Script .................................................................................... 282 9.22 Uploading RADIUS AAA Certificates ........................................................................... 284 9.23 Upgrading Devices On Demand.................................................................................. 287 9.23.1 Launching the Software Upgrade Interface.................................................................... 287 9.23.2 Configuring the PMP/PTP Software Upgrade ................................................................. 288 9.23.3 Launching the On‐Demand Software Upgrade............................................................... 297 9.23.4 Reviewing the Relevant Post‐Upgrade Information About the Device(s) ...................... 297 9.23.5 Resetting Location Attributes for PTP 300 and PTP 500 Devices ................................... 297 10 Creating and Using Device Groups.............................................................299 10.1 Creating a Dynamic Device Group .............................................................................. 305 10.2 Modifying a Dynamic Device Group ........................................................................... 308 10.3 Creating a Static Device Group ................................................................................... 309 10.4 Adding Devices to a Static Device Group.................................................................... 314 10.5 Removing Devices from a Static Device Group .......................................................... 315
- 8. 10.6 Adding or Removing Columns in a Device Group Window ........................................ 317 10.7 Using a Device Group.................................................................................................. 318 10.8 Removing a Device Group........................................................................................... 319 11 Obtaining Device Configuration Information ................................................321 11.1 Adjusting Configuration Polling Intervals ................................................................... 321 11.1.1 Disabling Configuration Polling....................................................................................... 321 11.1.2 Setting Intervals for a Small Network ............................................................................. 321 11.2 Creating and Using Device Configuration Reports ..................................................... 323 11.2.1 Importing Configuration Report Templates.................................................................... 324 11.2.2 Accessing a Predefined Report on Configured Values.................................................... 325 11.2.3 Creating a Configuration Report..................................................................................... 326 11.2.4 Running a Configuration Report ..................................................................................... 331 11.2.5 Finding a Configuration Report Template ...................................................................... 334 11.2.6 Editing a Configuration Report Template ....................................................................... 335 11.2.7 Exporting a Configuration Report Template................................................................... 337 11.2.8 Exporting All Configuration Report Templates ............................................................... 337 11.2.9 Deleting a Configuration Report ..................................................................................... 337 11.3 Using Configuration Summary Reports ...................................................................... 339 11.3.1 Using a Configuration Summary Report as Preconfigured ............................................. 342 11.3.2 Customizing a Configuration Summary Report .............................................................. 343 12 Monitoring Faults .....................................................................................345 12.1 Working with Events................................................................................................... 345 12.1.1 Viewing All Events for a Specific Device ......................................................................... 346 12.1.2 Viewing All Events in the System .................................................................................... 347 12.1.3 Interpreting Event Messages .......................................................................................... 348 12.1.4 Viewing Event Details ..................................................................................................... 350 12.1.5 Finding an Event.............................................................................................................. 353 12.1.6 Viewing Related Alarms .................................................................................................. 354 12.1.7 Viewing All Events Related to Discovery......................................................................... 354 12.1.8 Defining an Events Custom View .................................................................................... 356 12.1.9 Exporting Events to a CSV File ........................................................................................ 362 12.1.10 Printing Events ................................................................................................................ 363 12.2 Handling Alarms.......................................................................................................... 364 12.2.1 Viewing All Alarms for a Specific Device ......................................................................... 364 12.2.2 Viewing All Alarms in the System ................................................................................... 365 12.2.3 Viewing Alarm Details ..................................................................................................... 366 12.2.4 Searching Alarms ............................................................................................................ 368
- 9. 12.2.5 Viewing Related Events................................................................................................... 368 12.2.6 Picking Up / Unpicking an Alarm..................................................................................... 368 12.2.7 Adding Comments to an Alarm....................................................................................... 370 12.2.8 Viewing Alarm History .................................................................................................... 371 12.2.9 Viewing Both Annotation and History of an Alarm ........................................................ 371 12.2.10 Defining an Alarms Custom View.................................................................................... 372 12.2.11 Saving Alarms.................................................................................................................. 376 12.2.12 Exporting Alarms............................................................................................................. 377 12.2.13 Printing Alarms................................................................................................................ 377 12.2.14 Clearing an Alarm............................................................................................................ 377 12.2.15 Deleting an Alarm ........................................................................................................... 377 13 Monitoring Performance ...........................................................................379 13.1 Adjusting the Performance Polling Intervals .............................................................. 379 13.2 List of Available Performance Statistics (Configured Collection) ............................... 382 13.3 Performance Data Viewing Alternatives .................................................................... 384 13.3.1 Viewing a Current Performance Statistic........................................................................ 385 13.3.2 Viewing a Collected Performance Statistic ..................................................................... 386 13.4 Using System Reports ................................................................................................. 388 13.4.1 Importing System Reports .............................................................................................. 396 13.4.2 Using a System Report As Preconfigured ....................................................................... 396 13.4.3 Customizing a System Report ......................................................................................... 397 13.5 Launching an Operator‐defined Report...................................................................... 397 14 Administering Discovery ...........................................................................399 14.1 Importing Device Discovery Information.................................................................... 399 14.2 Using the Discovery Configurator............................................................................... 400 14.2.1 Opening the Discovery Configurator .............................................................................. 401 14.2.2 Discovering Mixed Networks .......................................................................................... 402 14.2.3 Configuring General Automatic Discovery...................................................................... 402 14.2.4 Configuring Criteria‐based Automatic Discovery............................................................ 428 14.2.5 Closing the Discovery Configurator ................................................................................ 432 14.3 Configuring Manual Discovery.................................................................................... 432 14.4 Stages of Discovery ..................................................................................................... 432 14.5 Viewing the Discovery Log .......................................................................................... 433 15 Administering Wireless Manager Security ....................................................435 15.1 Importing User Account Information ......................................................................... 437 15.2 Managing Users .......................................................................................................... 438
- 10. 15.2.1 Limiting a User to Read Only .......................................................................................... 438 15.2.2 Adding a User.................................................................................................................. 439 15.2.3 Changing a User Profile................................................................................................... 445 15.2.4 Assigning Groups to a User ............................................................................................. 447 15.2.5 Changing a User Password.............................................................................................. 448 15.2.6 Deleting a User................................................................................................................ 449 15.2.7 Using Audit Trails ............................................................................................................ 450 15.3 Managing Groups........................................................................................................ 455 15.3.1 Adding Groups ................................................................................................................ 456 15.3.2 Assigning Users to Groups .............................................................................................. 458 15.3.3 Deleting Users from Groups ........................................................................................... 459 15.3.4 Using Custom View Scopes ............................................................................................. 459 15.3.5 Deleting a Group............................................................................................................. 466 15.4 Managing Operations ................................................................................................. 467 15.4.1 Default Operations.......................................................................................................... 468 15.4.2 Configuration .................................................................................................................. 469 15.4.3 Events.............................................................................................................................. 470 15.4.4 Policy............................................................................................................................... 470 15.4.5 Poll Filters........................................................................................................................ 471 15.4.6 Polling Object.................................................................................................................. 471 15.4.7 Polling Units .................................................................................................................... 472 15.4.8 Provisioning..................................................................................................................... 472 15.4.9 Administrative Operation ............................................................................................... 473 15.4.10 Reports............................................................................................................................ 477 15.4.11 Threshold Object............................................................................................................. 477 15.4.12 Topology ......................................................................................................................... 478 15.4.13 Trap Parsers and Filters .................................................................................................. 479 15.4.14 Alerts............................................................................................................................... 479 15.4.15 Task Scheduler Operation............................................................................................... 481 15.4.16 Device Tools .................................................................................................................... 481 15.4.17 Ultralight Client Support ................................................................................................. 481 15.5 Assigning Operations .................................................................................................. 482 15.5.1 Assigning Permitted Operations for a Group.................................................................. 482 15.5.2 Assigning Permitted Operations for a User .................................................................... 484 15.6 Adding Operations ...................................................................................................... 484 15.7 Deleting Operations.................................................................................................... 486 16 Administering Fault Management ...............................................................489 16.1 Administering Trap Parsers......................................................................................... 489
- 11. 16.1.1 Opening the Trap Parser Configuration Tool.................................................................. 490 16.1.2 Adding a Trap Parser....................................................................................................... 491 16.1.3 Reordering the Configured Trap Parser List ................................................................... 497 16.1.4 Viewing Trap Parser Details ............................................................................................ 497 16.1.5 Modifying Trap Parsers ................................................................................................... 498 16.1.6 Deleting a Trap Parser..................................................................................................... 499 16.2 Using Event Parsers .................................................................................................... 499 16.2.1 Opening the Event Parser Configuration Tool ................................................................ 500 16.2.2 Adding an Event Parser................................................................................................... 500 16.2.3 Reordering the Configured Event Parser List.................................................................. 505 16.2.4 Loading an Event Parser from a Parser File .................................................................... 506 16.2.5 Modifying an Event Parser.............................................................................................. 506 16.2.6 Saving an Event Parser.................................................................................................... 508 16.2.7 Deleting an Event Parser................................................................................................. 508 16.3 Using Event Filters ...................................................................................................... 509 16.3.1 Opening the Event Filter Configuration Tool .................................................................. 510 16.3.2 Adding an Event Filter..................................................................................................... 510 16.3.3 Reordering the Event Filter Configuration List ............................................................... 522 16.3.4 Loading an Event Filter ................................................................................................... 522 16.3.5 Modifying an Event Filter................................................................................................ 523 16.3.6 Deleting an Event Filter................................................................................................... 524 16.4 Using Alarm Filters...................................................................................................... 524 16.4.1 Opening the Alarm Filter Configuration Tool ................................................................. 525 16.4.2 Adding an Alarm Filter .................................................................................................... 526 16.4.3 Reordering the Alarm Filter Configuration List............................................................... 531 16.4.4 Loading an Alarm Filter................................................................................................... 532 16.4.5 Modifying an Alarm Filter ............................................................................................... 532 16.4.6 Deleting an Alarm Filter .................................................................................................. 533 16.5 Performing Alarm Operations..................................................................................... 534 16.5.1 Deleting an Alarm ........................................................................................................... 534 16.5.2 Grouping Triggered Alarms............................................................................................. 535 16.6 Assigning Fault Management Privileges ..................................................................... 535 17 Administering Performance Management.....................................................543 17.1 Data Collection............................................................................................................ 543 17.1.1 Elements Involved in Data Collection ............................................................................. 544 17.1.2 Data Collection Process .................................................................................................. 545 17.1.3 Creating a Polling Object................................................................................................. 546 17.1.4 Modifying a Polling Object.............................................................................................. 555
- 12. 17.1.5 Deleting a Polling Object................................................................................................. 558 17.2 Administering Individual Statistics.............................................................................. 559 17.2.1 Adding a Statistic ............................................................................................................ 559 17.2.2 Finding a Statistic ............................................................................................................ 565 17.2.3 Modifying a Statistic ....................................................................................................... 566 17.2.4 Deleting a Statistic .......................................................................................................... 567 17.3 Administering Extended PolledData........................................................................... 568 17.3.1 Modifying Extended PolledData ..................................................................................... 568 17.3.2 Factors for Whether a Statistic is Polled......................................................................... 569 17.4 Associating Thresholds With Statistics and Network Elements ................................. 569 17.4.1 Adding a Threshold ......................................................................................................... 571 17.4.2 Preparing to Map a Threshold ........................................................................................ 577 17.4.3 Mapping a Threshold for an Individual Device ............................................................... 578 17.4.4 Associating a Threshold with a Statistic for an Individual Device................................... 580 17.4.5 Mapping a Threshold for a Specific Type Device ............................................................ 582 17.4.6 Mapping a Threshold for a Device Type ......................................................................... 583 17.4.7 Associating One or More Thresholds with a Polling Object for a Device Type............... 584 17.4.8 Modifying a Threshold .................................................................................................... 589 17.4.9 Deleting a Threshold....................................................................................................... 590 17.4.10 Example Strategy for Choosing and Applying Thresholds .............................................. 591 17.4.11 Interpreting Messages on Multiple Thresholds for a Single Statistic ............................. 592 17.5 Defining a Performance Custom View........................................................................ 592 17.6 Optimizing Performance Data Storage ....................................................................... 600 18 Administering a Policy ..............................................................................603 18.1 Adding a Policy............................................................................................................ 606 18.2 Scheduling a Policy...................................................................................................... 607 18.3 Updating a Policy ........................................................................................................ 608 18.4 Refreshing the Policies................................................................................................ 608 18.5 Executing a Policy ....................................................................................................... 608 18.6 Stopping a Policy......................................................................................................... 609 18.7 Deleting a Policy.......................................................................................................... 610 19 Configuring Network Elements...................................................................611 19.1 Using the Configure Device Command....................................................................... 611 19.2 Using Configuration Templates .................................................................................. 618 19.2.1 Importing a Configuration Template .............................................................................. 618 19.2.2 Pushing Values from a Prestructured Configuration Template...................................... 619
- 13. 19.2.3 Creating a Configuration Template................................................................................. 621 19.2.4 Applying a Configuration Template ................................................................................ 626 19.2.5 Finding a Configuration Template .................................................................................. 628 19.2.6 Editing a Configuration Template ................................................................................... 629 19.2.7 Pushing Configuration Values Upon Discovery............................................................... 631 19.2.8 Exporting a Configuration Template............................................................................... 633 19.2.9 Exporting All Configuration Templates ........................................................................... 634 19.2.10 Deleting a Configuration Template................................................................................. 634 19.3 Cloning a Device Configuration................................................................................... 635 19.4 Launching BAM ........................................................................................................... 640 19.5 Using Certain Device Type‐specific Configuration Dialogs ......................................... 641 19.5.1 Configuring an EtherWAN Switch ................................................................................... 641 20 Scheduling a One-Time or Periodic Task.....................................................647 20.1 Schedulable Tasks ....................................................................................................... 647 20.2 Launching the Task Scheduler .................................................................................... 652 20.3 Defining the Task to Perform...................................................................................... 653 20.4 Viewing Configured Tasks ........................................................................................... 673 20.5 Editing the Definition of a Configured Task................................................................ 677 20.6 Rescheduling or Triggering a Scheduled Task............................................................. 677 20.7 Pausing or Resuming a Scheduled Task ...................................................................... 678 20.8 Retaining or Removing a Scheduled Task................................................................... 678 20.9 Stopping a Running Task............................................................................................. 679 21 Broadcasting a Message ............................................................................681 22 Administering Wireless Manager ................................................................683 22.1 Terminating a Client Session....................................................................................... 683 22.2 Using the WM Administrator Tool.............................................................................. 683 22.2.1 Using the WM Server Panel ............................................................................................ 684 22.2.2 Configuring the BAM Panel............................................................................................. 685 22.2.3 Configuring the Database Panel ..................................................................................... 686 22.2.4 Using the Licensing Panel ............................................................................................... 687 22.2.5 Configuring the NBI Panel............................................................................................... 690 22.2.6 Using the Offline Physical Map Panel ............................................................................. 691 22.2.7 Configuring the Email Configuration Panel..................................................................... 693 22.3 Configuring Log Settings ............................................................................................. 694 22.3.1 Opening the Log File Configuration Tool ........................................................................ 694 22.3.2 Adding Log Files .............................................................................................................. 696
- 14. 22.3.3 Viewing Details of Log Files............................................................................................. 696 22.3.4 Modifying Log File Settings ............................................................................................. 697 22.3.5 Using Debug Mode ......................................................................................................... 701 22.3.6 Logging JVM Monitoring Details ..................................................................................... 702 23 Monitoring WM and Its Networks Through Wireless Manager Ultralight..........703 23.1 Accessing Wireless Manager Ultralight ...................................................................... 703 23.2 Using the What's Up Web Page .................................................................................. 704 23.3 Using the Summary View............................................................................................ 708 23.4 Using the Inventory View in Wireless Manager Ultralight ......................................... 711 23.5 Using the Alarms View in Wireless Manager Ultralight ............................................. 712 23.6 Using the Events View in Wireless Manager Ultralight .............................................. 713 23.7 Using the Customer Info View in Wireless Manager Ultralight.................................. 714 23.8 Using the Logs View in Wireless Manager Ultralight.................................................. 714 23.9 Terminating the Wireless Manager Ultralight Session............................................... 714 Legal Notices and License Agreements .................................................................715 CAMBIUM NETWORKS, LTD END USER LICENSE AGREEMENT............................................... 715 CAMBIUM PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 720 Software Included by Cambium.............................................................................................. 721 Packages That Use Apache License Version 2.0 ..................................................................... 725 THIRD PARTY PUBLICLY AVAILABLE SOFTWARE LEGAL NOTICES AND END USER LICENSE AGREEMENTS FOR PUBLICLY AVAILABLE SOFTWARE ............................................................ 729 Software Included by Commercial Third Party Software ....................................................... 730 Packages That Use GNU Lesser General Public License Version 2.1 ...................................... 736 Packages That Use Apache Software License Version 1.1...................................................... 744 Glossary ...........................................................................................................747 Technical Support..............................................................................................749 Running the Customer Support Tool ...................................................................................... 749 Options for Running the Support Tool ............................................................................................. 749 Populating the Fields of the Customer Support Tool Window ........................................................ 751 Viewing and Saving Files That are Useful for Support............................................................ 757 Contacting Support Representatives...................................................................................... 758 Index................................................................................................................761
- 15. List of Figures Figure 1: Server disk free space monitoring window for a child WM element .......................................... 54 Figure 2: Disk usage monitoring window for a child WM element ............................................................ 54 Figure 3: Disk I/O monitoring window for a child WM element................................................................. 55 Figure 4: Database disk usage monitoring window for a child WM element............................................. 55 Figure 5: Memory utilization monitoring window for a child WM element............................................... 56 Figure 6: Database disk free space monitoring window for a child WM element ..................................... 56 Figure 7: CPU utilization monitoring window for a child WM element...................................................... 57 Figure 8: Element Properties for a subordinate WM server, General tab.................................................. 58 Figure 9: Element Properties for a subordinate WM server, SNMP tab..................................................... 58 Figure 10: Element Properties for a subordinate WM server, Monitoring tab .......................................... 59 Figure 11: Element Properties for a subordinate WM server, Relationship tab ........................................ 59 Figure 12: Web page for WM Web Start client invoke (LoginPage.do) ...................................................... 62 Figure 13: WM Authentication dialog......................................................................................................... 63 Figure 14: WM Authentication advanced options...................................................................................... 64 Figure 15: WM application initial view ....................................................................................................... 65 Figure 16: Possible relationships between client and server ..................................................................... 65 Figure 17: Java Control Panel, General tab................................................................................................. 66 Figure 18: Network Settings window in Java Control Panel ....................................................................... 67 Figure 19: Advanced Network Settings window in Java Control Panel ...................................................... 67 Figure 20: Network tab in Firefox Options window.................................................................................... 68 Figure 21: Connection Settings window in Firefox ..................................................................................... 69 Figure 22: General tab of Java Control Panel.............................................................................................. 70 Figure 23: Temporary Files Settings window in Java Control Panel ........................................................... 71 Figure 24: Delete Temporary Files window in Java Control Panel............................................................. 71 Figure 25: Password Confirmation window................................................................................................ 72 Figure 26: PasswordConfigurator dialog..................................................................................................... 73 Figure 27: Client window, example............................................................................................................. 75 Figure 28: Toolbar when Dashboard is displayed ....................................................................................... 76 Figure 29: Toolbar when Network Events are displayed ............................................................................ 76 Figure 30: Toolbar when Alarms are displayed .......................................................................................... 76 Figure 31: Toolbar when Configured Collection is displayed...................................................................... 76
- 16. Figure 32: Toolbar when Templates view is displayed ............................................................................... 76 Figure 33: Toolbar when Inventory view is displayed ................................................................................ 76 Figure 34: Toolbar when Reports are displayed ......................................................................................... 76 Figure 35: Toolbar when Scheduled Tasks are displayed ........................................................................... 76 Figure 36: Toolbar when Policies view is displayed .................................................................................... 76 Figure 37: Alarm summary views................................................................................................................ 77 Figure 38: View of devices under Warning ................................................................................................. 78 Figure 39: Severe alarm counts .................................................................................................................. 78 Figure 40: About window, License tab........................................................................................................ 80 Figure 41: License Manager web interface................................................................................................. 81 Figure 42: Change Password panel, License Manager Administrator Tool ................................................ 82 Figure 43: About window, Device Details tab............................................................................................. 83 Figure 44: About window, Client Details tab .............................................................................................. 84 Figure 45: About window, Supported Device Templates tab ..................................................................... 85 Figure 46: Expanded view of the Applications tree .................................................................................... 89 Figure 47: Example parent custom view with child view............................................................................ 91 Figure 48: Custom view nodes in Applications tree.................................................................................... 91 Figure 49: Search results for input Statistic Name contents ...................................................................... 94 Figure 50: Search results for input Message contents ............................................................................... 95 Figure 51: Search results for input Source contents................................................................................... 96 Figure 52: Search results for input network Name (ID) .............................................................................. 96 Figure 53: Search results for input IP Address contents............................................................................. 97 Figure 54: Search results for input Alarm Message contents ..................................................................... 98 Figure 55: Search results for input Device Name contents ........................................................................ 98 Figure 56: Search results for input Location contents ................................................................................ 99 Figure 57: Search results for input Name (ID) contents ............................................................................. 99 Figure 58: Search results for input Device Group Name contents ........................................................... 100 Figure 59: Search results for input Address1 contents............................................................................. 100 Figure 60: Alarms table view..................................................................................................................... 103 Figure 61: Select operation window ......................................................................................................... 107 Figure 62: Import information windows................................................................................................... 107 Figure 63: Select file window .................................................................................................................... 108 Figure 64: Dashboard Alarms by Severity display..................................................................................... 116
- 17. Figure 65: Dashboard Alarms by Device Type display .............................................................................. 116 Figure 66: Dashboard Recent Alarms display ........................................................................................... 116 Figure 67: Dashboard Alarms by Message display.................................................................................... 117 Figure 68: Dashboard Device Counts display............................................................................................ 117 Figure 69: Dashboard Help display, Useful Links and License tabs........................................................... 117 Figure 70: Dashboard Help display, Device Details and Settings tabs ...................................................... 118 Figure 71: Clear Alarms Included .............................................................................................................. 118 Figure 72: Clear Alarms Hidden ................................................................................................................ 118 Figure 73: Inventory view ......................................................................................................................... 121 Figure 74: Device types list in Applications tree, example ....................................................................... 122 Figure 75: Alarms Search dialog, sort options .......................................................................................... 124 Figure 76: Alarms Search dialog, input options ........................................................................................ 124 Figure 77: Alarms Search dialog, More options........................................................................................ 125 Figure 78: Alarms Search operation, alarms returned, example.............................................................. 125 Figure 79: Properties tab for an inventory custom view, first form ......................................................... 127 Figure 80: Properties tab for an inventory custom view, second form .................................................... 128 Figure 81: Properties tab for an inventory custom view, third form........................................................ 129 Figure 82: Properties tab for an inventory custom view, fourth form ..................................................... 130 Figure 83: Properties tab for an inventory custom view, fifth form......................................................... 131 Figure 84: Additional custom view criteria dialog, Properties tab ........................................................... 132 Figure 85: Criteria dialog with three properties ....................................................................................... 133 Figure 86: Select Table Columns dialog for inventory custom view ......................................................... 134 Figure 87: User defined table columns window for inventory custom view............................................ 134 Figure 88: Tree Node Properties tab for inventory custom view ............................................................. 135 Figure 89: Export Data dialog.................................................................................................................... 136 Figure 90: Right‐click options common for all elements .......................................................................... 137 Figure 91: Configuration Control dialog for PMP 320 AP ......................................................................... 140 Figure 92: Configure Mode dialog for PMP 320 AP, default values.......................................................... 140 Figure 93: Configure Mode dialog for PMP 320 AP, Mode BW selections ............................................... 141 Figure 94: Configure Mode dialog for PMP 320 AP, Mode Ratio selections ............................................ 141 Figure 95: Configure Mode dialog for PMP 320 AP, Mode Map selections ............................................. 141 Figure 96: Networks panel view ............................................................................................................... 142 Figure 97: Geo‐location Import window................................................................................................... 147
- 18. Figure 98: Import CSV File of Geo‐Locations window............................................................................... 147 Figure 99: Location Import from Address CSV.......................................................................................... 149 Figure 100: Offline map, midwestern USA ............................................................................................... 152 Figure 101: Offline map, northeastern Illinois.......................................................................................... 152 Figure 102: Offline map, network at a plus zoom factor .......................................................................... 153 Figure 103: Offline map, network at a minus zoom factor....................................................................... 153 Figure 104: Physical map: collapsed instance of device collocation ........................................................ 155 Figure 105: Physical map: expanded instance of device collocation........................................................ 156 Figure 106: Refresh and centering options for a physical map ................................................................ 161 Figure 107: All reliability links selected for physical map ......................................................................... 164 Figure 108: Good reliability links filtered out ........................................................................................... 165 Figure 109: Good reliability links persistently filtered out from previous physical map setting.............. 166 Figure 110: Physical map: further zooming required for viewing more devices ...................................... 166 Figure 111: Physical map: All Links, No Coverage, All Air Standards, Map............................................... 167 Figure 112: Physical map: All Links, No Coverage, All Air Standards, Hybrid ........................................... 167 Figure 113: Physical map: Logical Links, No Coverage, All Air Standards, Terrain.................................... 168 Figure 114: Device data pop‐up, Main tab ............................................................................................... 175 Figure 115: Device data pop‐up, Radios tab ............................................................................................. 175 Figure 116: Device data pop‐up, Links tab, scrolling required ................................................................. 176 Figure 117: Path Profile............................................................................................................................. 177 Figure 118: Device data pop‐up, Manage tab, scrolling required ............................................................ 178 Figure 119: Device data pop‐up, Manage tab for a PTP device................................................................ 179 Figure 120: Question mark representing device of unknown type .......................................................... 179 Figure 121: Import BroadbandPlanner Prediction dialog......................................................................... 182 Figure 122: Physical map Log window, opened........................................................................................ 184 Figure 123: Exported physical map in Google Earth application, zoomed in ........................................... 186 Figure 124: Exported physical map in Google Earth application, zoomed out......................................... 187 Figure 125: Places box with Network Elements node expanded ............................................................. 188 Figure 126: Radio(s) link to information about the element .................................................................... 188 Figure 127: Information about the element in Google Earth ................................................................... 189 Figure 128: Places box with links node expanded .................................................................................... 189 Figure 129: Link information in Google Earth view .................................................................................. 190 Figure 130: Polling Configuration dialog, Status Polling tab..................................................................... 196
- 19. Figure 131: Configure Specific Type Polling dialog for status polling ....................................................... 197 Figure 132: Element Properties, General tab ........................................................................................... 198 Figure 133: Element Properties, SNMP tab .............................................................................................. 199 Figure 134: Element Properties, Monitoring tab ...................................................................................... 199 Figure 135: Element Properties, Relationship tab .................................................................................... 200 Figure 136: Show Components panel ....................................................................................................... 200 Figure 137: Component Properties window............................................................................................. 201 Figure 138: Network Events view for a single device ............................................................................... 202 Figure 139: Alarms view for a single device.............................................................................................. 202 Figure 140: Performance data Configured Collection view for a single device ........................................ 203 Figure 141: Dashboard format for PMP AP .............................................................................................. 205 Figure 142: Dashboard format for PMP SM.............................................................................................. 206 Figure 143: Dashboard format for PMP 320 AP ....................................................................................... 207 Figure 144: Dashboard format for PMP 320 CPE...................................................................................... 208 Figure 145: Dashboard format for PMP OFDM AP ................................................................................... 209 Figure 146: Dashboard format for PMP OFDM SM .................................................................................. 210 Figure 147: Dashboard format for PMP BHM........................................................................................... 211 Figure 148: Dashboard format for PMP BHS ............................................................................................ 212 Figure 149: Dashboard format for PTP 500 Master.................................................................................. 213 Figure 150: Dashboard format for PTP 800 Slave..................................................................................... 214 Figure 151: Dashboard format for CMM3 ................................................................................................ 215 Figure 152: Dashboard format for CMM4 ................................................................................................ 215 Figure 153: Dashboard format for 14‐Port Switch ................................................................................... 216 Figure 154: Dashboard format for Generic Element ................................................................................ 216 Figure 155: Dashboard format for Extreme Switch .................................................................................. 217 Figure 156: Dashboard format for RAD Switch......................................................................................... 217 Figure 157: Dashboard for a child WM element....................................................................................... 218 Figure 158: Dashboard panels without data............................................................................................. 221 Figure 159: Collected statistics window for GPS Satellites Tracked ......................................................... 222 Figure 160: Device summary report for a PMP 430 SM ........................................................................... 224 Figure 161: Device summary report for a child WM element .................................................................. 225 Figure 162: Report Results window .......................................................................................................... 226 Figure 163: Customer Contact Management window.............................................................................. 227
- 20. Figure 164: Pinging Components window, success .................................................................................. 231 Figure 165: Pinging Components window, skipped for unmanaged component .................................... 231 Figure 166: Drop Subscriber Session window for a PMP AP..................................................................... 232 Figure 167: Drop Subscriber Session for Name (ID).................................................................................. 232 Figure 168: Remove Relationship option in Extended Family window .................................................... 233 Figure 169: Remove relationship pop‐up warning ................................................................................... 234 Figure 170: Add Relationship Between Elements dialog, both devices identified ................................... 235 Figure 171: Add Relationship Between Elements dialog, one device identified ...................................... 236 Figure 172: Logical link displayed ............................................................................................................. 237 Figure 173: Circular reference error ......................................................................................................... 237 Figure 174: Select operation window ....................................................................................................... 240 Figure 175: Import Customer Contact Information window .................................................................... 241 Figure 176: Customer Contact Management window.............................................................................. 242 Figure 177: Customer Information dialog................................................................................................. 243 Figure 178: Credential Manager dialog..................................................................................................... 249 Figure 179: Link Capacity Test results window ......................................................................................... 253 Figure 180: Spectrum Analyzer window for a PMP 320 AP ...................................................................... 255 Figure 181: Spectrum Analyzer window for a PMP SM ............................................................................ 256 Figure 182: Device web page URL............................................................................................................. 257 Figure 183: Enhanced Security Configuration warning............................................................................. 258 Figure 184: Trusted sites window ............................................................................................................. 258 Figure 185: Initial web page of Subscriber Module .................................................................................. 259 Figure 186: Management home web page of a PMP Subscriber Module................................................ 260 Figure 187: Full management interface web page of PMP Subscriber Module ....................................... 261 Figure 188: Confirmation message for Delete Object and Traces operation ........................................... 262 Figure 189: Apply template dialog, imported AP templates .................................................................... 265 Figure 190: Define Configurations tab...................................................................................................... 268 Figure 191: Configuration Parameter Selection dialog for a service plan ................................................ 269 Figure 192: Configurable parameters in a service plan ............................................................................ 269 Figure 193: Confirm Update window for bandwidth service plan............................................................ 270 Figure 194: Updating Configuration window for a new service plan ....................................................... 271 Figure 195: Task Attributes window for a service plan............................................................................. 272 Figure 196: Configure Element(s) window for applying a service plan .................................................... 273
- 21. Figure 197: Configuration Parameter Selection dialog for a VLAN profile ............................................... 276 Figure 198: Configurable parameters in a VLAN profile ........................................................................... 277 Figure 199: Edit VLAN Membership dialog ............................................................................................... 278 Figure 200: Add Entry window.................................................................................................................. 278 Figure 201: Confirm Update window for VLAN profile............................................................................. 279 Figure 202: Updating Configuration window for VLAN profile................................................................. 279 Figure 203: Task Attributes window for applying a VLAN profile ............................................................. 280 Figure 204: Configure Element(s) dialog for applying a VLAN profile ...................................................... 281 Figure 205: Details for a User Script task.................................................................................................. 283 Figure 206: Schedulable Script Results window, example........................................................................ 284 Figure 207: Upload AAA Certificate dialog, initial view ............................................................................ 285 Figure 208: Upload AAA Certificate dialog, Delete Existing Certificate selected...................................... 286 Figure 209: Software Upgrade dialog ....................................................................................................... 288 Figure 210: Selected for upgrade tab ....................................................................................................... 289 Figure 211: SM Autoupdate Configuration tab......................................................................................... 290 Figure 212: HPAP Channel Bandwidth tab................................................................................................ 292 Figure 213: Package Manager dialog, no packages .................................................................................. 296 Figure 214: Package Manager dialog, packages added ............................................................................ 296 Figure 215: Add Device window for Static Selection of a device group ................................................... 299 Figure 216: Create Device Group conditions for basic Dynamic Selection of a device group.................. 300 Figure 217: Name selections for Add Advanced Criteria of a dynamic device group............................... 301 Figure 218: Device Group Details tab of the Create Device Group dialog................................................ 305 Figure 219: Devices tab of the Create Device Group dialog ..................................................................... 306 Figure 220: Devices Preview window ....................................................................................................... 307 Figure 221: Device Groups window .......................................................................................................... 307 Figure 222: Device Group Details tab of Edit Device Group dialog .......................................................... 308 Figure 223: Devices tab of Edit Device Group dialog................................................................................ 309 Figure 224: Add to Device Groups window .............................................................................................. 310 Figure 225: Devices tab of Create Device Group dialog ........................................................................... 311 Figure 226: Add Device window ............................................................................................................... 312 Figure 227: Devices selected to add ......................................................................................................... 312 Figure 228: Devices added to Devices Selected block .............................................................................. 313 Figure 229: Add to Device Groups window .............................................................................................. 314
- 22. Figure 230: Scheduled Tasks window ....................................................................................................... 319 Figure 231: Delete Group option for a device group................................................................................ 319 Figure 232: Polling Configuration dialog, Configuration Polling tab......................................................... 321 Figure 233: Configure Specific Type Polling dialog for configuration polling ........................................... 322 Figure 234: Execute Configuration Report Template panel ..................................................................... 325 Figure 235: Create Configuration Report Template dialog launched from Inventory.............................. 327 Figure 236: Create Configuration Report Template dialog launched from Applications tree.................. 328 Figure 237: Success for a create report .................................................................................................... 329 Figure 238: Select Configuration Report Data window ............................................................................ 329 Figure 239: Configuration Report View window....................................................................................... 329 Figure 240: Execute Report window......................................................................................................... 330 Figure 241: Execute Configuration Report window.................................................................................. 332 Figure 242: Search window for configuration report template criteria ................................................... 335 Figure 243: Edit Configuration Report Template window ........................................................................ 335 Figure 244: Delete Report window ........................................................................................................... 338 Figure 245: Delete Report window, reports contents .............................................................................. 338 Figure 246: System Reports view.............................................................................................................. 342 Figure 247: SM QOS Summary.................................................................................................................. 343 Figure 248: Network Events view, one device (Source) ........................................................................... 346 Figure 249: Network Events view, all Sources .......................................................................................... 347 Figure 250: Event Details window ............................................................................................................ 351 Figure 251: Search window for event criteria........................................................................................... 353 Figure 252: Discovery Events view............................................................................................................ 355 Figure 253: Event filter custom view criteria dialog, Properties tab ........................................................ 356 Figure 254: Additional custom view criteria dialog, Properties tab ......................................................... 359 Figure 255: Criteria dialog with three properties ..................................................................................... 360 Figure 256: Select Table Columns dialog for event filter view ................................................................. 360 Figure 257: User defined table columns window ..................................................................................... 361 Figure 258: Tree Node Properties tab for event filter custom view......................................................... 361 Figure 259: Export Data dialog.................................................................................................................. 363 Figure 260: Alarms view, one device (IPAddress) ..................................................................................... 365 Figure 261: Alarms view, all devices (all IPAddresses).............................................................................. 366 Figure 262: Alarms details window........................................................................................................... 367
- 23. Figure 263: Owner and Annotation in Alarm detail.................................................................................. 369 Figure 264: Alarm filter custom view criteria, Properties tab .................................................................. 372 Figure 265: Select Table Columns dialog for alarm filter view ................................................................. 375 Figure 266: Tree Node Properties tab for alarm filter custom view......................................................... 376 Figure 267: Polling Configuration dialog, Performance Polling tab.......................................................... 379 Figure 268: Configure Specific Type Polling dialog for performance polling............................................ 381 Figure 269: Configured Collection panel................................................................................................... 382 Figure 270: Current statistics window ...................................................................................................... 385 Figure 271: Collected statistics window, line graph ................................................................................. 387 Figure 272: Collected statistics window, bar graph .................................................................................. 388 Figure 273: Inventory Summary report .................................................................................................... 393 Figure 274: Device Uptime report ............................................................................................................ 394 Figure 275: Discovery Configurator, General tab ..................................................................................... 401 Figure 276: Confirmation for deselection of AutoDiscovery .................................................................... 402 Figure 277: Initial Parameters contents from the Discovery Configurator............................................... 405 Figure 278: Rediscovery Scheduler dialog ................................................................................................ 407 Figure 279: Rediscovery Scheduler, Specific Dates................................................................................... 408 Figure 280: Rediscovery Scheduler, Days of Week ................................................................................... 409 Figure 281: Discovery Configurator, Protocol tab .................................................................................... 411 Figure 282: SNMP Properties selected from the Protocol tab ................................................................. 411 Figure 283: Discovery Configurator, Network Discovery tab ................................................................... 415 Figure 284: Snmp Properties window for network discovery .................................................................. 417 Figure 285: SNMP V3 Properties tab ........................................................................................................ 419 Figure 286: Snmp V3 Properties window, General tab............................................................................. 419 Figure 287: Snmp V3 Properties window, Security tab ............................................................................ 420 Figure 288: Discovery Configurator, Node Discovery tab......................................................................... 422 Figure 289: Disabling discovery for a listed device ................................................................................... 426 Figure 290: Criteria tab, disallow discovery for type SUN and name A .................................................... 427 Figure 291: Discovery Configurator, Criteria tab ...................................................................................... 429 Figure 292: Criteria tab, allow discovery for specific name and OID........................................................ 430 Figure 293: Criteria tab, allow discovery for only SNMP nodes ............................................................... 431 Figure 294: Discovery Log ......................................................................................................................... 433 Figure 295: Failure events in the Discovery Log ....................................................................................... 433
- 24. Figure 296: Initial Security Administration Tool Screen............................................................................ 436 Figure 297: User Administration wizard, User Description panel............................................................. 440 Figure 298: User Administration wizard, account and password expiry .................................................. 441 Figure 299: User Administration wizard, permissions .............................................................................. 442 Figure 300: Assign Permissions dialog ...................................................................................................... 444 Figure 301: Security administration tabs .................................................................................................. 446 Figure 302: User Profile tab ...................................................................................................................... 446 Figure 303: User Profile dialog.................................................................................................................. 447 Figure 304: Select Groups window ........................................................................................................... 448 Figure 305: Change Password dialog ........................................................................................................ 449 Figure 306: Warning for user deletion...................................................................................................... 450 Figure 307: Auth Audit screen .................................................................................................................. 452 Figure 308: Search dialog for audit trails .................................................................................................. 454 Figure 309: AlertAudit window, with properties of an audit trail ............................................................ 455 Figure 310: Groups Wizard, Group Description panel .............................................................................. 457 Figure 311: Groups Wizard, Operations Tree ........................................................................................... 457 Figure 312: Select Users window .............................................................................................................. 458 Figure 313: Scope Settings dialog ............................................................................................................. 461 Figure 314: Select AuthorizedScopes window.......................................................................................... 464 Figure 315: AuthorizedScopes for CV panel ............................................................................................. 465 Figure 316: Warning for authorized scope deletion ................................................................................. 466 Figure 317: Warning for group deletion ................................................................................................... 466 Figure 318: Operation Tree nodes showing default user permissions ..................................................... 468 Figure 319: Operations For Group panel .................................................................................................. 482 Figure 320: Assign Permissions dialog ...................................................................................................... 483 Figure 321: Operations dialog................................................................................................................... 485 Figure 322: Warning for operation deletion............................................................................................. 487 Figure 323: Trap Parser Configuration tool .............................................................................................. 490 Figure 324: Trap Parser Configuration window, Add Trap Parser operation ........................................... 491 Figure 325: Trap Parser Configuration dialog, Event User Properties ...................................................... 497 Figure 326: Event User Properties dialog ................................................................................................. 498 Figure 327: Event Parser Configuration tool............................................................................................. 500 Figure 328: Specify User properties and Trap based Criterias dialog....................................................... 505
- 25. Figure 329: Load Event Parsers From File dialog ...................................................................................... 506 Figure 330: Save Event Parser To File dialog ............................................................................................ 508 Figure 331: Event Filters dialog................................................................................................................. 510 Figure 332: Match criteria Properties dialog ............................................................................................ 511 Figure 333: Suppress Action dialog........................................................................................................... 514 Figure 334: Run Command Action dialog ................................................................................................. 515 Figure 335: Send Trap Action dialog ......................................................................................................... 517 Figure 336: Variable Binding List dialog.................................................................................................... 518 Figure 337: Send Email Action dialog........................................................................................................ 519 Figure 338: Authentication Information dialog ........................................................................................ 521 Figure 339: Filter Details dialog ................................................................................................................ 522 Figure 340: Alert Filters dialog .................................................................................................................. 525 Figure 341: Alert Filters dialog, example added ....................................................................................... 528 Figure 342: Match criteria Properties dialog ............................................................................................ 529 Figure 343: More Properties dialog .......................................................................................................... 530 Figure 344: Filter Details dialog ................................................................................................................ 532 Figure 345: Poll Details dialog, General Properties frame........................................................................ 547 Figure 346: Poll Details, Managed Object match criteria ......................................................................... 548 Figure 347: Poll Details, Data Configuration parameters ......................................................................... 550 Figure 348: Polled Details dialog, General Properties frame, active fields............................................... 556 Figure 349: Poll Details dialog, Data Configuration panel ........................................................................ 557 Figure 350: Poll Details dialog for Delete Polling Object operation ......................................................... 558 Figure 351: Confirm Deletion pop‐up ....................................................................................................... 559 Figure 352: DataCollection Detailed Properties dialog, first form............................................................ 560 Figure 353: DataCollection Detailed Properties dialog, second form....................................................... 563 Figure 354: Search window for statistic criteria ....................................................................................... 566 Figure 355: DataCollection Detailed Properties dialog for Modify Statistic operation ............................ 567 Figure 356: Thresholds and Associations dialog ....................................................................................... 572 Figure 357: Thresholds Properties dialog, long tab .................................................................................. 573 Figure 358: Threshold Properties dialog, string tab.................................................................................. 574 Figure 359: Threshold Properties dialog, percentage tab ........................................................................ 575 Figure 360: New association row added to Thresholds and Associations interface ................................ 578 Figure 361: Search Devices dialog............................................................................................................. 578
- 26. Figure 362: DataCollection Detailed Properties dialog, first set of properties......................................... 580 Figure 363: DataCollection Detailed Properties, second set of properties .............................................. 581 Figure 364: Data Collection Detailed Properties, third set of values........................................................ 582 Figure 365:Search specific type dialog, specific type selected ................................................................. 583 Figure 366: Search specific type dialog, device type selected.................................................................. 584 Figure 367: Poll Details dialog................................................................................................................... 585 Figure 368: Poll Details dialog, Data Configuration panel with read‐only fields ...................................... 586 Figure 369: Poll Details dialog, Data Configuration panel with read‐write fields..................................... 588 Figure 370: Poll Details dialog, General Properties panel ........................................................................ 589 Figure 371: Threshold Properties dialog for Modify operation ................................................................ 590 Figure 372: Threshold Properties dialog for Delete operation................................................................. 591 Figure 373: Performance custom view criteria, Properties tab, first form............................................... 593 Figure 374: Performance custom view criteria, Properties tab, second form.......................................... 595 Figure 375: Performance custom view criteria, Properties tab, third form ............................................. 597 Figure 376: Select Table Columns dialog for performance filter view...................................................... 599 Figure 377: Tree Node Properties tab for performance filter custom view ............................................. 600 Figure 378: AlarmClearingPolicy ............................................................................................................... 603 Figure 379: EscalationPolicy...................................................................................................................... 604 Figure 380: Policies panel ......................................................................................................................... 606 Figure 381: AddPolicy Details window...................................................................................................... 606 Figure 382: Policy Scheduler window ....................................................................................................... 607 Figure 383: Object Details window for policy update............................................................................... 608 Figure 384: Execute policy confirmation pop‐up...................................................................................... 609 Figure 385: List background for policies under execution........................................................................ 609 Figure 386: Stop Policy confirmation pop‐up ........................................................................................... 609 Figure 387: Configuration Group, PMP SM device ................................................................................... 612 Figure 388: Configuration Group, PMP BHM device ................................................................................ 613 Figure 389: Configuration Group, PMP 320 CPE....................................................................................... 614 Figure 390: Configuration Group, PTP 800 Slave ...................................................................................... 615 Figure 391: Configuration groups for a child WM .................................................................................... 616 Figure 392: Configuration Group attributes – IP ...................................................................................... 617 Figure 393: Apply Template dialog, 5.4‐GHz OFDM BHM device ............................................................. 619 Figure 394: Select Import Files browser for configuration templates...................................................... 621
- 27. Figure 395: Create Configuration Template example, PMP OFDM SM with RF tooltip ........................... 622 Figure 396: Create Configuration Template dialog, parameter selected via Jump To, but Include not checked.................................................................................................................................. 624 Figure 397: Create Configuration Template dialog, parameter selected and Include checked ............... 625 Figure 398: Apply Template window ........................................................................................................ 626 Figure 399: Modify Values dialog.............................................................................................................. 627 Figure 400: Devices tab............................................................................................................................. 628 Figure 401: Search window for configuration template criteria .............................................................. 629 Figure 402: Edit Template dialog for editing ............................................................................................ 630 Figure 403: Default Configuration Template Mapping dialog .................................................................. 631 Figure 404: Delete Template window....................................................................................................... 634 Figure 405: Warning pop‐up for Delete template operation ................................................................... 634 Figure 406: Clone Device dialog................................................................................................................ 635 Figure 407: Clone Device dialog, table of attributes and values .............................................................. 637 Figure 408: Select Task Type dialog .......................................................................................................... 652 Figure 409: Create Schedule Task dialog for all tasks except Configuration and Reports........................ 653 Figure 410: Create Schedule Task dialog for a Configuration or Reports task, Schedule tab................... 654 Figure 411: Create Schedule Task dialog for a Configuration or Reports task, Devices tab..................... 655 Figure 412: Add Device window ............................................................................................................... 656 Figure 413: Device Groups window .......................................................................................................... 657 Figure 414: Individual devices selected for removal ................................................................................ 658 Figure 415: Specific Type drop‐down list for Basic Dynamic Selection .................................................... 659 Figure 416: Configuration Attribute drop‐down list for Basic Dynamic Selection.................................... 660 Figure 417: Performance Attribute drop‐down list for Basic Dynamic Selection..................................... 661 Figure 418: Add Advanced Criteria window, ready for Device Properties selections .............................. 662 Figure 419: Add Advanced Criteria window, selectable Device Properties.............................................. 663 Figure 420: Add Advanced Criteria window, Configuration Attributes for a subset of Specific Types .... 664 Figure 421: Create Schedule Task window, Details tab listing configuration templates.......................... 665 Figure 422: Create Schedule Task window, Details tab open to a configuration template ..................... 666 Figure 423: Create Schedule Task dialog, Schedule tab for non‐recurring task ....................................... 668 Figure 424: Create Schedule Task dialog, Schedule tab for a minute‐based task .................................... 669 Figure 425: Create Schedule Task dialog, Schedule tab for an hourly task .............................................. 670 Figure 426: Create Schedule Task dialog, Schedule tab for a daily task ................................................... 671
- 28. Figure 427: Create Schedule Task dialog, Schedule tab for a weekly task ............................................... 672 Figure 428: Create Schedule Task dialog, Schedule tab for a monthly task ............................................. 673 Figure 429: Scheduled Tasks view for SYSTEM‐owned tasks.................................................................... 674 Figure 430: Scheduled Tasks view for user‐owned tasks.......................................................................... 675 Figure 431: Edit Scheduled Task dialog..................................................................................................... 675 Figure 432: Results tab for a scheduled task ............................................................................................ 676 Figure 433: Report Result window for report task execution .................................................................. 676 Figure 434: Options for an Active task...................................................................................................... 677 Figure 435: Paused task in Scheduled Task table view ............................................................................. 678 Figure 436: Mark for Clean Up option in Schedule tab for tasks.............................................................. 678 Figure 437: Options for an Inactive task ................................................................................................... 679 Figure 438: Broadcast Message dialog ..................................................................................................... 681 Figure 439: Clients' Details window.......................................................................................................... 683 Figure 440: WM Server panel of WM Administrator Tool........................................................................ 684 Figure 441: BAM panel of WM Administrator Tool .................................................................................. 685 Figure 442: Database panel of WM Administrator Tool........................................................................... 686 Figure 443: Licensing panel of WM Administrator Tool ........................................................................... 687 Figure 444: Upload License File dialog...................................................................................................... 688 Figure 445: License Manager Status display window ............................................................................... 689 Figure 446: NBI panel of WM Administrator Tool, active SNMP V3 settings ........................................... 690 Figure 447: NBI panel of WM Administrator Tool, active SNMP V1/V2 settings ..................................... 691 Figure 448: Offline Physical Map panel of WM Administrator Tool ......................................................... 692 Figure 449: Email Configuration panel of WM Administrator Tool .......................................................... 693 Figure 450: Logging Configuration panel .................................................................................................. 695 Figure 451: Viewing the Log Details dialog ............................................................................................... 697 Figure 452: Logging configuration window, Log Settings, first frame ...................................................... 698 Figure 453: Logging configuration window, Log Settings, second frame ................................................. 700 Figure 454: Collected statistics window with JVM monitoring history plotted........................................ 702 Figure 455: Login web page of Wireless Manager Ultralight.................................................................... 703 Figure 456: What's Up web page .............................................................................................................. 704 Figure 457: SM Device‐specific web page, top ......................................................................................... 706 Figure 458: Device‐specific web page, middle.......................................................................................... 707 Figure 459: Summary View in Wireless Manager Ultralight..................................................................... 708
- 29. Figure 460: Alarms (Major) web page in Wireless Manager Ultralight .................................................... 709 Figure 461: Events (Critical) web page in Wireless Manager Ultralight ................................................... 709 Figure 462: Individual device block in Wireless Manager Ultralight ........................................................ 709 Figure 463: Inventory view in Wireless Manager Ultralight ..................................................................... 711 Figure 464: Alarms (All) view in Wireless Manager Ultralight .................................................................. 712 Figure 465: Events (All) view in Wireless Manager Ultralight................................................................... 713 Figure 466: Logs available from Wireless Manager Ultralight.................................................................. 714 Figure 467: Support Tool Options window ............................................................................................... 750 Figure 468: Customer Support Tool dialog, General Information tab ...................................................... 751 Figure 469: Choose a File window for additional files to send to Customer Support .............................. 754 Figure 470: Customer Support Tool dialog, Devices tab with Add selected............................................. 756 Figure 471: Saved Support Files window .................................................................................................. 758
- 31. List of Tables Table 1: Structured information resources per general device type.......................................................... 49 Table 2: Troubleshooting client login issues ............................................................................................... 73 Table 3: Common toolbar options .............................................................................................................. 77 Table 4: Applications tree nodes ................................................................................................................ 87 Table 5: Input string vs. result types for Search utility ............................................................................... 93 Table 6: Table navigation buttons ............................................................................................................ 103 Table 7: Tree node properties for event filter view.................................................................................. 135 Table 8: References for common command options................................................................................ 138 Table 9: References for special command options................................................................................... 139 Table 10: Command options from a network element dashboard .......................................................... 219 Table 11: When BAM changes for subscribers are effective .................................................................... 264 Table 12: Bandwidth and VLAN element attributes ................................................................................. 266 Table 13: How VLAN settings are applied to an SM.................................................................................. 275 Table 14: Configuration Summary reports ............................................................................................... 339 Table 15: Preconfigured event messages and their severities ................................................................. 348 Table 16: General discovery events .......................................................................................................... 348 Table 17: Multi‐agent discovery events.................................................................................................... 350 Table 18: Single‐agent discovery event .................................................................................................... 350 Table 19: File import event ....................................................................................................................... 350 Table 20: Event details .............................................................................................................................. 351 Table 21: Event filter custom view criteria fields...................................................................................... 357 Table 22: Wild card characters for criteria fields...................................................................................... 358 Table 23: Tree node properties for event filter view................................................................................ 362 Table 24: Alarm details properties............................................................................................................ 367 Table 25: Alarm filter custom view criteria fields ..................................................................................... 373 Table 26: Configured Collection properties .............................................................................................. 383 Table 27: Differentiating Current and Historical Data .............................................................................. 384 Table 28: Alternatives for viewing the values of a statistic ...................................................................... 384 Table 29: Possible messages in a current performance data graph ......................................................... 386 Table 30: Possible messages for a Collected statistics window................................................................ 387 Table 31: AP performance reports............................................................................................................ 389
- 32. Table 32: PMP 320 AP performance reports ............................................................................................ 389 Table 33: SM performance reports........................................................................................................... 390 Table 34: PMP 320 CPE performance reports .......................................................................................... 391 Table 35: PMP Backhaul performance reports ......................................................................................... 392 Table 36: PTP performance reports .......................................................................................................... 392 Table 37: Format for device discovery information import...................................................................... 399 Table 38: Initial discovery parameters...................................................................................................... 406 Table 39: Discovery interval parameters .................................................................................................. 410 Table 40: SNMP configuration parameters............................................................................................... 412 Table 41: User icons .................................................................................................................................. 436 Table 42: Format for user account information import............................................................................ 437 Table 43: Audit entries for user activity events ........................................................................................ 453 Table 44: Authorized Custom View Scopes value operators .................................................................... 462 Table 45: Configuration options ............................................................................................................... 469 Table 46: Events options........................................................................................................................... 470 Table 47: Policy options ............................................................................................................................ 470 Table 48: Poll Filters options..................................................................................................................... 471 Table 49: Polling Object options ............................................................................................................... 471 Table 50: Polling Units options ................................................................................................................. 472 Table 51: Provisioning options.................................................................................................................. 472 Table 52: Administrative Operation, Services options ............................................................................. 473 Table 53: Administrative Operation, Security options.............................................................................. 475 Table 54: Other Administrative Operations options................................................................................. 476 Table 55: Configuration Reports options .................................................................................................. 477 Table 56: Threshold Object options.......................................................................................................... 477 Table 57: Topology options....................................................................................................................... 478 Table 58: Trap Parsers and Filters options................................................................................................ 479 Table 59: Alerts options ............................................................................................................................ 480 Table 60: Task Scheduler Operation options ............................................................................................ 481 Table 61: Device Tools options ................................................................................................................. 481 Table 62: Trap Parser Configuration fields ............................................................................................... 492 Table 63: Trap Protocol Data Unit fields................................................................................................... 494 Table 64: Event Parser fields..................................................................................................................... 501
- 33. Table 65: Event properties........................................................................................................................ 503 Table 66: Match Criteria fields.................................................................................................................. 511 Table 67: Match Criteria fields, Advanced dialog fields............................................................................ 511 Table 68: Suppress Action Details dialog fields ........................................................................................ 514 Table 69: Run Command Notification dialog fields .................................................................................. 515 Table 70: Send Trap Action dialog fields................................................................................................... 517 Table 71: Send Email Action Details dialog fields ..................................................................................... 519 Table 72: Email alert message properties................................................................................................. 526 Table 73: Alarm Match Criteria fields ....................................................................................................... 529 Table 74: Match criteria Properties fields................................................................................................. 529 Table 75: Common parameters ................................................................................................................ 551 Table 76: Common Data Identifier properties.......................................................................................... 552 Table 77: DataCollection Detailed Properties fields, first form ................................................................ 560 Table 78: DataCollection Detailed Properties fields, second form ........................................................... 563 Table 79: How many and what type of threshold to add ......................................................................... 570 Table 80: Ways to associate statistics with thresholds............................................................................. 570 Table 81: Data collection Threshold indicators ........................................................................................ 571 Table 82: Threshold Properties fields ....................................................................................................... 575 Table 83: Performance custom view criteria fields, first form ................................................................. 593 Table 84: Performance custom view criteria fields, second form ............................................................ 595 Table 85: Performance custom view criteria fields, third form................................................................ 597 Table 86: Configurable task prerequisites, requirements, and options ................................................... 648 Table 87: Options for scheduling of tasks................................................................................................. 667 Table 88: Log Settings panel fields, first frame......................................................................................... 699 Table 89: Log Settings panel fields, second frame.................................................................................... 700 Table 90: Support Detail levels ................................................................................................................. 753
- 35. List of Procedures Procedure 1: To launch WM ....................................................................................................................... 62 Procedure 2: To configure your password prior to client connection........................................................ 72 Procedure 3: To reconfigure your password .............................................................................................. 73 Procedure 4: To view a range of details ................................................................................................... 104 Procedure 5: To export device discovery information ............................................................................. 109 Procedure 6: To export user account information ................................................................................... 111 Procedure 7: To export network hierarchy information .......................................................................... 113 Procedure 8: To export topology data...................................................................................................... 136 Procedure 9: To view an Inventory element in the context of a physical map ........................................ 154 Procedure 10: To view an element in a cluster ........................................................................................ 156 Procedure 11: To view linked elements within the same physical map................................................... 157 Procedure 12: To export a physical map .................................................................................................. 185 Procedure 13: To set status polling for a specific device type.................................................................. 196 Procedure 14: To view device details ....................................................................................................... 198 Procedure 15: To view component details ............................................................................................... 200 Procedure 16: To view events generated for a device ............................................................................. 201 Procedure 17: To view alarms generated for a device ............................................................................. 202 Procedure 18: To view performance data of a device.............................................................................. 203 Procedure 19: To import a customer contact database ........................................................................... 240 Procedure 20: To compose a customer‐device(s) record......................................................................... 242 Procedure 21: To edit a customer‐device(s) record ................................................................................. 246 Procedure 22: To set credentials for a selected group of devices............................................................ 249 Procedure 23: To perform a link capacity test in an SM........................................................................... 250 Procedure 24: To use the Spectrum Analyzer feature.............................................................................. 254 Procedure 25: To open a device web interface ........................................................................................ 257 Procedure 26: To delete a device and all information about it ................................................................ 262 Procedure 27: To configure APs for authentication management........................................................... 264 Procedure 28: To define a service plan..................................................................................................... 268 Procedure 29: To apply a service plan ...................................................................................................... 271 Procedure 30: To update a service plan ................................................................................................... 273 Procedure 31: To remove a bandwidth service plan association ............................................................. 274
- 36. Procedure 32: To remove a service plan .................................................................................................. 274 Procedure 33: To define a VLAN profile ................................................................................................... 276 Procedure 34: To apply a VLAN profile ..................................................................................................... 279 Procedure 35: To update a VLAN profile .................................................................................................. 281 Procedure 36: To remove a VLAN profile association .............................................................................. 282 Procedure 37: To remove a VLAN profile ................................................................................................. 282 Procedure 38: To upload a AAA certificate............................................................................................... 285 Procedure 39: To create a dynamic device group .................................................................................... 305 Procedure 40: To modify a dynamic device group ................................................................................... 308 Procedure 41: To create a static device group ......................................................................................... 309 Procedure 42: To add one or more devices to an existing device group ................................................. 314 Procedure 43: To remove a device from a device group.......................................................................... 315 Procedure 44: To remove a device group................................................................................................. 319 Procedure 45: To set configuration polling for a specific device type...................................................... 322 Procedure 46: To import configuration report templates........................................................................ 324 Procedure 47: To access a configuration report template ....................................................................... 325 Procedure 48: To create a configuration report....................................................................................... 326 Procedure 49: To run a configuration report............................................................................................ 332 Procedure 50: To find a configuration report template ........................................................................... 334 Procedure 51: To edit a configuration report........................................................................................... 335 Procedure 52: To export a single configuration report template............................................................. 337 Procedure 53: To export all configuration report templates.................................................................... 337 Procedure 54: To delete a configuration report....................................................................................... 337 Procedure 55: To view event details......................................................................................................... 350 Procedure 56: To find an event ................................................................................................................ 353 Procedure 57: To view other events that have the same Failure Object ................................................. 354 Procedure 58: To export events................................................................................................................ 363 Procedure 59: To print events to the server printer................................................................................. 363 Procedure 60: To view alarm details ........................................................................................................ 366 Procedure 61: To view related events ...................................................................................................... 368 Procedure 62: To pick up an alarm from the Alarms view ....................................................................... 368 Procedure 63: To pick up an alarm from the Alarms details dialog ......................................................... 369 Procedure 64: To unpick an alarm from the Alarms view ........................................................................ 369
- 37. Procedure 65: To unpick an alarm from the Alarm details dialog ............................................................ 369 Procedure 66: To add comments to an alarm .......................................................................................... 370 Procedure 67: To view the history of an alarm......................................................................................... 371 Procedure 68: To view both annotation and history of an alarm............................................................. 371 Procedure 69: To clear a triggered alarm ................................................................................................. 377 Procedure 70: To set performance polling of a specific device type for its extraneous values ............... 380 Procedure 71: To view performance data collection details .................................................................... 382 Procedure 72: To import system reports.................................................................................................. 396 Procedure 73: To invoke the Discovery Configurator............................................................................... 401 Procedure 74: To disable auto‐discovery ................................................................................................. 402 Procedure 75: To rediscover previously discovered nodes ...................................................................... 403 Procedure 76: To prevent local network discovery .................................................................................. 403 Procedure 77: To set the discovery interval ............................................................................................. 404 Procedure 78: To set initial discovery parameters ................................................................................... 405 Procedure 79: To set the rediscovery at Regular Interval ........................................................................ 407 Procedure 80: To set rediscovery on specific dates ................................................................................. 408 Procedure 81: To set rediscovery on specific days ................................................................................... 409 Procedure 82: To configure SNMP Properties .......................................................................................... 411 Procedure 83: To configure discovery for a network of devices set to allow SNMPv1 and v3 access..... 413 Procedure 84: To configure discovery for a network of devices set to allow only SNMPv3 access......... 413 Procedure 85: To enable discovery of remote networks ......................................................................... 415 Procedure 86: To discover only a range of addresses in a network ......................................................... 416 Procedure 87: To enable DHCP support ................................................................................................... 416 Procedure 88: To discover SNMPv1 or v2c devices in a network............................................................. 417 Procedure 89: To discover SNMPv3 devices in a network........................................................................ 418 Procedure 90: To set a network‐specific SNMPv3 configuration for discovery ....................................... 420 Procedure 91: To configure discovery of a specific IP address................................................................. 422 Procedure 92: To discover nodes where LocalNet is disabled ................................................................. 423 Procedure 93: To discover SNMP devices with specific community and port ......................................... 423 Procedure 94: To discover specific SNMPv3 devices................................................................................ 424 Procedure 95: To set a device‐specific SNMPv3 configuration for discovery .......................................... 424 Procedure 96: To prevent the discovery of a specific network ................................................................ 425 Procedure 97: To prevent the discovery of an unlisted device ................................................................ 426
- 38. Procedure 98: To prevent the discovery of a listed device ...................................................................... 426 Procedure 99: To disallow discovery where type is SUN and name is A (example) ................................. 427 Procedure 100: To discover devices with specific properties................................................................... 429 Procedure 101: To discover only SNMP nodes ......................................................................................... 430 Procedure 102: To discover only the object corresponding to a specific IP............................................. 431 Procedure 103: To launch the Security Administration tool .................................................................... 435 Procedure 104: To add a new user ........................................................................................................... 439 Procedure 105: To change a user profile.................................................................................................. 445 Procedure 106: To assign groups to a user............................................................................................... 447 Procedure 107: To change a user password ............................................................................................. 448 Procedure 108: To delete a user............................................................................................................... 450 Procedure 109: To view audit trails of all users........................................................................................ 451 Procedure 110: To view audit trails of a single user................................................................................. 453 Procedure 111: To add a group ................................................................................................................ 456 Procedure 112: To assign a user to a group.............................................................................................. 458 Procedure 113: To delete a user from a group......................................................................................... 459 Procedure 114: To add a custom view scope ........................................................................................... 460 Procedure 115: To assign an authorized custom view scope ................................................................... 463 Procedure 116: To remove an authorized custom view scope ................................................................ 464 Procedure 117: To change the properties of an authorized scope .......................................................... 465 Procedure 118: To delete an authorized custom view scope................................................................... 465 Procedure 119: To delete a group ............................................................................................................ 466 Procedure 120: To assign operations for a group..................................................................................... 482 Procedure 121: To assign permitted operations for a user...................................................................... 484 Procedure 122: To add an operation ........................................................................................................ 485 Procedure 123: To delete an operation.................................................................................................... 486 Procedure 124: To open the Trap Parser Configuration tool ................................................................... 490 Procedure 125: To add a Trap Parser ....................................................................................................... 491 Procedure 126: To reorder the Configured Trap Parser List..................................................................... 497 Procedure 127: To view details of a Trap Parser ...................................................................................... 497 Procedure 128: To modify a Trap Parser .................................................................................................. 498 Procedure 129: To delete a Trap Parser ................................................................................................... 499 Procedure 130: To open the Event Parser Configuration tool.................................................................. 500
- 39. Procedure 131: To add an Event Parser.................................................................................................... 500 Procedure 132: To reorder the Configured Event Parser List................................................................... 505 Procedure 133: To load an Event Parser file............................................................................................. 506 Procedure 134: To modify an Event Parser .............................................................................................. 507 Procedure 135: To save an Event Parser file ............................................................................................ 508 Procedure 136: To delete an Event Parser ............................................................................................... 508 Procedure 137: To open the Event Filters dialog...................................................................................... 510 Procedure 138: To add an Event Filter—Criteria Phase ........................................................................... 510 Procedure 139: To add an Event Filter—Additional Criteria Phase.......................................................... 512 Procedure 140: To add an Event Filter—Notification Phase .................................................................... 513 Procedure 141: To add a varbind.............................................................................................................. 518 Procedure 142: To modify a varbind ........................................................................................................ 518 Procedure 143: To reorder the Event Filter list ........................................................................................ 522 Procedure 144: To load an Event Filter file............................................................................................... 522 Procedure 145: To modify the match criteria of an Event Filter .............................................................. 523 Procedure 146: To modify the notifications in an Event Filter ................................................................. 523 Procedure 147: To delete an event filter.................................................................................................. 524 Procedure 148: To delete a filter notification........................................................................................... 524 Procedure 149: To open the Alarm Filter Configuration Tool .................................................................. 525 Procedure 150: To add an Alarm Filter, example steps............................................................................ 526 Procedure 151: To add an Alarm Filter, criteria phase ............................................................................. 528 Procedure 152: To add an Alarm Filter, additional criteria phase............................................................ 530 Procedure 153: To add an Alarm Filter, notifications phase .................................................................... 531 Procedure 154: To reorder the Alert Filters ............................................................................................. 531 Procedure 155: To load an Alert Filter file................................................................................................ 532 Procedure 156: To modify the match criteria for an Alarm Filter ............................................................ 532 Procedure 157: To modify the notifications for an Alarm Filter............................................................... 533 Procedure 158: To delete an alarm filter.................................................................................................. 533 Procedure 159: To delete a filter notification........................................................................................... 533 Procedure 160: To delete a triggered alarm............................................................................................. 534 Procedure 161: To assign fault management privileges (example case).................................................. 535 Procedure 162: To create a Polling Object ............................................................................................... 546 Procedure 163: To specify a match criteria via Managed Object properties ........................................... 549
- 40. Procedure 164: To modify a Polling Object .............................................................................................. 555 Procedure 165: To delete a Polling Object ............................................................................................... 558 Procedure 166: To add statistics at runtime............................................................................................. 559 Procedure 167: To find a statistic ............................................................................................................. 566 Procedure 168: To modify an existing Statistic......................................................................................... 566 Procedure 169: To delete a Statistic ......................................................................................................... 568 Procedure 170: To modify the properties of Extended PolledData ......................................................... 568 Procedure 171: To add a threshold .......................................................................................................... 571 Procedure 172: To prepare to map a threshold ....................................................................................... 577 Procedure 173: To map a threshold for an individual device................................................................... 578 Procedure 174: To add thresholds to a statistic ....................................................................................... 580 Procedure 175: To map a threshold for a specific type device ................................................................ 582 Procedure 176: To map a threshold for a device type ............................................................................. 583 Procedure 177: To associate thresholds with a Polling Object for a device type..................................... 584 Procedure 178: To modify a threshold ..................................................................................................... 589 Procedure 179: To delete a threshold ...................................................................................................... 590 Procedure 180: To create a threshold for a device .................................................................................. 591 Procedure 181: To schedule a policy ........................................................................................................ 607 Procedure 182: To update a policy ........................................................................................................... 608 Procedure 183: To configure a device ...................................................................................................... 611 Procedure 184: To import a configuration template................................................................................ 619 Procedure 185: To import configuration templates ................................................................................. 620 Procedure 186: To create a configuration template ................................................................................ 621 Procedure 187: To apply an existing configuration template .................................................................. 626 Procedure 188: To find a configuration template .................................................................................... 628 Procedure 189: To edit a configuration template .................................................................................... 629 Procedure 190: To set up automatic configuration upon discovery ........................................................ 631 Procedure 191: To export a configuration template ................................................................................ 633 Procedure 192: To export all configuration templates............................................................................. 634 Procedure 193: To delete a configuration template ................................................................................ 634 Procedure 194: To clone a device configuration ...................................................................................... 635 Procedure 195: Launching a BAM session ................................................................................................ 640 Procedure 196: To launch Task Scheduler................................................................................................ 652
- 41. Procedure 197: To define a Configuration task ........................................................................................ 653 Procedure 198: To view configured tasks................................................................................................. 674 Procedure 199: To view results of last execution of a task ...................................................................... 675 Procedure 200: To edit a task definition................................................................................................... 677 Procedure 201: To reschedule a task execution....................................................................................... 677 Procedure 202: To pause a task................................................................................................................ 678 Procedure 203: To resume a task ............................................................................................................. 678 Procedure 204: To cancel automatic deletion of a task ........................................................................... 679 Procedure 205: To delete a task ............................................................................................................... 679 Procedure 206: To stop a task .................................................................................................................. 679 Procedure 207: To Broadcast a message.................................................................................................. 681 Procedure 208: To reconfigure offline physical map images in WM........................................................ 692 Procedure 209: To configure server and admin email settings ................................................................ 694 Procedure 210: To open the Log File Configuration tool.......................................................................... 694 Procedure 211: To view log file details ..................................................................................................... 696 Procedure 212: To modify log file details ................................................................................................. 697 Procedure 213: To log in to the Wireless Manager Ultralight .................................................................. 703
- 43. WM Release 4.0 User Guide Issue 3 May 2012 1 About This User Guide This Cambium Wireless Manager Release 4.0 User Guide describes and provides procedures for operations in the Wireless Manager (WM) client interface for Release 4.0. If you are a client administrator or user, use the user guide. Only authorized users can log into a WM client and access specific features, based on assigned user privileges. Contact your system administrator for help with your authorized user privileges. Device‐specific information is provided in the documents that support the devices. This includes definitions for configurable attributes. However, this WM user guide describes how to 1. compose a configuration template, assuming that you know what attributes and values you want to configure 2. use WM to push those values to the elements. All information pertaining to operations on the client (those operations that are authorized or disallowed by the Operation Tree) is provided in this user guide, regardless of the permission required to perform them. This construction for this user guide allows client administrators to use the whole book and all of its cross‐references, whether these link to complex and restricted operations or to simple operations that are universally permitted across the operating staff. At the same time, users with relatively low permissions can view procedures that only client administrators can execute. The rich security features of WM make this a practical design for the user guide. As you acquaint yourself with the table of contents of the user guide, you will see section titles transition from having words like using and monitoring to having words like administering and managing. Given the complexity of user and group account provisioning (in the Operation Tree) and the varied tacks that operators may take in their WM security designs, no attempt is made to clearly partition the user guide where everything situated after a partition applies to only client administrators. 1.1 Continuing Features Release 4.0 continues full configuration and ongoing management capabilities for the range of products that are listed under Cambium Networks Device Types on Page 49 and for non‐Cambium devices for which operators create their own valid device definition templates. It also collects and displays events and alarms for the Cambium Point‐to‐Point (PTP) and Point‐to‐Multipoint (PMP) products, thus providing a consolidated view of the status of the Cambium networks in a single screen. WM Release 4.0 continues the capability to overlay network elements onto an embedded Google map. Maps like this allow you to visualize and analyze a wide range of crucial information, including connectivity between nodes, link quality, range, and device and network availability. These graphical representations help you quickly see network status, identify any problems, and assess the severity of impact they will have on the network and its users. This release has also kept stride with changes in device templates for elements that it has supported and with new templates for elements that are introduced since the last release. 43
- 44. Issue 3 WM Release 4.0 User Guide May 2012 This document is intended to support only Release 4.0 of WM. All information pertaining to operations on the client (those operations that are authorized or disallowed by the Operation Tree), are described here in the user guide, regardless of the permission required to perform them. important ........... The installation tool for the WM server deposits an issue of the Cambium Wireless Manager Release 4.0 Server Administration Guide and the Cambium Wireless Manager Release 4.0 User Guide into the ...server/help directory on the WM server. These documents are placeholders. Immediately after your server installation is completed, visit http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=0. If a later iteration of either or both of these documents is present there, download it and delete the superseded book. Throughout the life of Release 4.0, this web site will always contain the latest supporting documents. Whenever the issue number available at this site is greater than what you currently have, you need to download the replacement. 1.2 Features New in Release 4.0 Release 4.0 introduces the following features: a user interface for cloning device configurations with values, from either a selected device or the database, either pushed to destination devices of the same device type or saved to a template you will later push to them, without touching attributes that should be excluded from cloning; for example, without − those that are not readable from the source, such as keys and passwords. − others that could fail the operation, such as Device Region Code and Device Default Reset. − optionally, those that should in most cases remain unique, such as IP, DHCP, NAT, and bridge mode attributes. See Cloning a Device Configuration on Page 635. a system‐configured view of events that are related to discovery. See Viewing All Events Related to Discovery on Page 354. device type graphical summary reports. See − Table 32: PMP 320 AP performance reports on Page 389 − Table 34: PMP 320 CPE performance reports on Page 391 − Table 31: AP performance reports on Page 389 − Table 35: PMP Backhaul performance reports on Page 392 − Table 33: SM performance reports on Page 390 − Table 33: SM performance reports on Page 390 − Table 36: PTP performance reports on Page 392 support for multiple default configuration templates per device type to be applied during discovery. See Pushing Configuration Values Upon Discovery on Page 631. 44
- 45. WM Release 4.0 User Guide Issue 3 May 2012 added support for − PTP 250 Master and Slave as read‐only elements − PTP 300, PTP 500, and PTP 800 Master and Slave as Version 05‐00. See the caveat in Clarifications on Page 46. − PTP 400 Master and Slave as Version 09‐01. − more attributes of the Extreme Switch. − PMP 320 Release e2.3. For the AP, this includes Network Configuration attributes for SNMP version (v1/2c or v3), web access security (HTTPS or HTTP), and serial interface (CLI or uGPS). read‐only attributes for GPS location, the active service flow count, and the frequency range and restriction mode of the AP. performance tables for UL and DL MCS counters of registered CPE's MCS and HARQ stats. a frame utilization table used by the native Frame Utilization tool in WM but hidden from user configuration templates. updates to the Upload AAA Certificate utility, tables for user management and trap destinations, and the Slots Measurement, MAC Version, backoff values (for DL, UL, and ECINER), Sync Source, Selected DL/UL Ratio, and Sync Status attributes. commands that Save Configuration Command, Reboot Device, Clear [service flow] Counters, and Clear [MCS] Statistics. introduction of performance statistics for the following data: ‐ received/transmit data rate ‐ received IP packets with and without VLAN tag ‐ received non‐IP packets with and without VLAN tag ‐ received packets classified and unclassified ‐ DL and UL MCS state of each registered CPE ‐ antenna method of each registered CPE. elimination of the need for operators to have their own physical map licenses. This is reflected in About License Tab on Page 80. a means to terminate a rogue or runaway client session while other concurrent sessions continue. See Terminating a Client Session on Page 683. changes in the integrated software upgrade utility. See − Upgrading Devices On Demand on Page 287. − Setting the General Configuration on Page 289. − Setting the SM Autoupdate Configuration on Page 290. synchronization functions (buttons) added to the WM Server panel of the WM Administrator Tool to launch removal of all events, alarms, and traps in process, while leaving all elements' statistics untouched. See Using the WM Server Panel on Page 684. removal of trap port configurability and trap parser interfaces. removal of the System Administration web interface. 45
- 46. Issue 3 WM Release 4.0 User Guide May 2012 1.3 Clarifications New OIDs are implemented in v05‐00 for PTP 300 and PTP 500 location attributes. See Resetting Location Attributes for PTP 300 and PTP 500 Devices on Page 297. The order in which user permissions are set determine which permissions are allowed and which are disallowed. Also, the system does not warn the administrator who configures multiple group memberships for a user when those groups have differing sets of permissions. An important admonishment has been added to Administering Wireless Manager Security on Page 435, describing these scenarios. 1.4 References to Other WM Documents If you are a client administrator or user, use this user guide. All information pertaining to the WM server file system is presented for the server administrator in Cambium Wireless Manager 4.0 Quick Start Guide, which documents − the system requirements − the procedure for a fresh installation − client device setup − SNMP broadcast toggling − starting and stopping the WM service − launching the client − setting up, monitoring, and troubleshooting initial discovery − licensing WM software and the physical map Cambium Wireless Manager Release 4.0 Server Administration Guide, which documents − port usage − database administration − server‐side adjustments for discovery fault management performance management security management physical map features − server logs − licensing and upgrading WM software − backing up the system − using the MIB browser For high‐level descriptions of new features included in the initial distribution of Release 4.0, or for all disclosures about features that this distribution supports, see the Cambium Wireless Manager Release 4.0 Release Notes. If you are a server administrator, use the Cambium Wireless Manager Release 4.0 Server Administration Guide. 46
- 47. WM Release 4.0 User Guide Issue 3 May 2012 For BAM feature integration, see the following documentation: Cambium Wireless Manager 4.0 Quick Start Guide Cambium Wireless Manager Release 4.0 Server Administration Guide Using the Bandwidth and Authentication Manager (BAM) Subsystem on Page 262 1.5 Links to Other Important Documents For links to important documents about supported network elements, visit the following web pages: PTP device and PTP LINKPlanner user guides and release notes at http://www.cambiumnetworks.com/support/ptp/software/index.php?tag=linkplanner PMP device user guides, release notes, and MIBs at http://www.cambiumnetworks.com/support/pmp/software/index.php a wide range of PMP 320 device documents at http://www.cambiumnetworks.com/support/pmp/software/index.php CMM user guides and release notes at http://www.cambiumnetworks.com/support/pmp/software/index.php For links to important documents about management tools, visit the following web pages: Wireless Manager guides, release notes, and service pack notes at http://www.cambiumnetworks.com/support/planning/index.php?cat=1&type=0 Cambium Network Updater Tool (CNUT) on‐line help file and release notes at http://www.cambiumnetworks.com/support/planning/index.php?cat=3&type=0 Prizm guides, release notes, and its SDK at http://www.cambiumnetworks.com/support/planning/index.php?cat=2&type=0 For links to network element features and specifications, visit the following web pages. Cambium PTP: − the portfolio at http://www.cambiumnetworks.com/solutions/ptp_overview.php − PTP 100 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp100 − PTP 200 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp200 − PTP 300 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp300 − PTP 500 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp500 − PTP 600 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp600 − PTP 800 at http://www.cambiumnetworks.com/solutions/products.php?id=ptp800 − Cambium Networks LINKPlanner at http://www.cambiumnetworks.com/solutions/products.php?id=linkplanner Cambium PMP: − the portfolio at http://www.cambiumnetworks.com/solutions/pmp_overview.php − PMP 100 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp100 − PMP 320 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp320 − PMP 400 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp400 − PMP 430 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp430 − PMP 450 at http://www.cambiumnetworks.com/solutions/products.php?id=pmp450 47
- 48. Issue 3 WM Release 4.0 User Guide May 2012 For declarations of conformity for individual network elements in their various frequency band ranges, see http://www.cambiumnetworks.com/doc.php. 1.6 Feedback on This Guide We encourage feedback on our documentation, including An opinion on the structure or content of the documents. a notification to us about a deficiency in accuracy or completeness. any other comment you have. Please send your feedback to [email protected]. 48
- 49. WM Release 4.0 User Guide Issue 3 May 2012 2 Supported Device Types 2.1 Cambium Networks Device Types The Cambium Wireless Manager Release Notes for Release 4.0 provides the complete list of the device types that this release supports, correlated to their firmware version(s) supported and their device template file names. WM supports each of these device types with a network elements dashboard (see Viewing the Dashboard for a Device on Page 204) and most with structured information resources as indicated in Table 1. Table 1: Structured information resources per general device type General Device Type Predefined Structured Documented In Information Resource PMP PTP Generic Table 31: AP performance reports on AP Bridge Table Summary1 Page 389 Table 31: AP performance reports on AP Ethernet Statistics1 Page 389 Table 31: AP performance reports on AP General Status1 Page 389 Table 14: Configuration Summary reports on AP QoS Summary1 Page 339 Table 31: AP performance reports on AP Radio Statistics1 Page 389 Table 31: AP performance reports on AP Session Table Summary1 Page 389 Table 31: AP performance reports on AP Top 25 Report1 Page 389 AP VLAN Configuration Table 14: Configuration Summary reports on Summary1 Page 339 Configured values report Accessing a Predefined Report on Configured template Values on Page 325 Default configuration values Pushing Values from a Prestructured push template Configuration Template on Page 619 Device definition template Server administration guide PMP 320 AP Ethernet Table 32: PMP 320 AP performance reports Statistics1 on Page 389 49
- 50. Issue 3 WM Release 4.0 User Guide May 2012 General Device Type Predefined Structured Documented In Information Resource PMP PTP Generic Table 32: PMP 320 AP performance reports PMP 320 AP General Status1 on Page 389 PMP 320 AP Graphical Table 32: PMP 320 AP performance reports Summary Report1 on Page 389 Table 14: Configuration Summary reports on PMP 320 AP QoS Summary1 Page 339 PMP 320 AP Radio Table 32: PMP 320 AP performance reports Statistics1 on Page 389 PMP 320 AP Service Flow Table 14: Configuration Summary reports on Summary1 Page 339 Table 32: PMP 320 AP performance reports PMP 320 AP Top 25 Report1 on Page 389 PMP 320 CPE Ethernet Table 34: PMP 320 CPE performance reports Statistics1 on Page 391 PMP 320 CPE General Table 34: PMP 320 CPE performance reports Status1 on Page 391 PMP 320 CPE Graphical Table 34: PMP 320 CPE performance reports Summary Report1 on Page 391 PMP 320 CPE Radio Table 34: PMP 320 CPE performance reports Statistics1 on Page 391 PMP 320 CPE Service Flow Table 14: Configuration Summary reports on Summary1 Page 339 PMP 320 CPE Top 25 Table 34: PMP 320 CPE performance reports Report1 on Page 391 PMP AP Graphical Summary Table 31: AP performance reports on Page Report1 389 PMP Backhaul Bridge Table Table 35: PMP Backhaul performance reports Summary1 on Page 392 PMP Backhaul Ethernet Table 35: PMP Backhaul performance reports Statistics1 on Page 392 PMP Backhaul General Table 35: PMP Backhaul performance reports Status1 on Page 392 PMP Backhaul Graphical Table 35: PMP Backhaul performance reports Summary Report1 on Page 392 PMP Backhaul Radio Table 35: PMP Backhaul performance reports Statistics1 on Page 392 50
- 51. WM Release 4.0 User Guide Issue 3 May 2012 General Device Type Predefined Structured Documented In Information Resource PMP PTP Generic PMP Backhaul Top 25 Table 35: PMP Backhaul performance reports Report1 on Page 392 PMP Backhaul VLAN Table 14: Configuration Summary reports on Configuration Summary1 Page 339 PMP FSK SM Graphical Table 33: SM performance reports on Page Summary Report1 390 PMP OFDM SM Graphical Table 33: SM performance reports on Page Summary Report1 390 PTP 800 Bridge Table 14: Configuration Summary reports on Configuration Summary1 Page 339 Table 36: PTP performance reports on PTP Ethernet Statistics1 Page 392 Table 36: PTP performance reports on PTP General Status1 Page 392 PTP Graphical Summary Table 36: PTP performance reports on Page Report1 392 Table 36: PTP performance reports on PTP Radio Statistics1 Page 392 Table 36: PTP performance reports on PTP Top 25 Report1 Page 392 PTP VLAN Configuration Table 14: Configuration Summary reports on Summary1 Page 339 Table 33: SM performance reports on SM Bridge Table Summary1 Page 390 Table 33: SM performance reports on SM Ethernet Statistics1 Page 390 Table 33: SM performance reports on SM General Status1 Page 390 Table 14: Configuration Summary reports on SM QoS Summary1 Page 339 Table 33: SM performance reports on SM Radio Statistics1 Page 390 51
- 52. Issue 3 WM Release 4.0 User Guide May 2012 General Device Type Predefined Structured Documented In Information Resource PMP PTP Generic Table 33: SM performance reports on SM Top 25 Report1 Page 390 SM VLAN Configuration Table 14: Configuration Summary reports on Summary1 Page 339 NOTES: 1. Optionally loaded into the client application by the network operator. 2.2 Generic Elements (Non-Cambium Devices) WM discovers as a generic element any SNMP‐enabled 1 non‐Cambium device for which no valid device definition template exists. This is distinguished from a Cambium devices, for which a device definition template is part of the WM software distribution, and from any third‐party devices 2 for which the operator has created a valid device definition template. However, generic element discovery depends also on the following workaround. Check to see whether WM has discovered all of the generic devices in the network. For any that WM did not discover, the server administration guide provides a workaround procedure. The result is that WM succeeds in discovering all generic elements in your network. However, WM will use the MAC address as the Name (ID) of any that support and properly implement DHCP. A generic device that WM discovers counts against the node limit in the WMEMSPack license. For a generic device, WM performs the following element management functions: discovery regardless of SNMP version (v1, v2c, or v3) configuration of name, location, contact information, and device description and the following geo‐location attributes: − latitude − longitude − height above the ground collection and display of operational state performance statistics (number of ports, in‐ and out‐octets, and in‐ and out‐errors) collection and processing of cold start, link up, link down, and authentication failure traps representation with the generic device icon ( ) in − the physical map − the Inventory − the Applications tree − viewers for alarms and events 1 Supporting RFC1213‐MIB. 2 Cisco Router and Cisco Switch are third‐party devices for which the WM distribution provides valid device definition templates. 52
- 53. WM Release 4.0 User Guide Issue 3 May 2012 WM also allows them to be members of user‐defined device groups. WM keeps their IP addresses and for each, provides a dashboard (as it does for Cambium device types) to display current alarms and events with some configured attributes and statistics. For WM to manage a device, it must be able to find the MAC address of that device so, during rediscovery, WM 1. probes the ipAddr MIB table for the index to check in the ifTable. 2. queries the ifTable index to get the MAC address. However, if this process fails, then WM fails to discover the device. if the device already exists in database, WM moves it to the Unmanaged state and throws an event to report it. Some generic SNMP devices do not fully support the ifaddr and ipaddr MIB tables. Allowing WM to manage such a device requires the creation of a device template that explicitly supports it. Before you attempt to create a template for it, request assistance from Cambium Networks support by calling the appropriate phone number listed at http://www.cambiumnetworks.com/support/technical.php or submitting your question in the form provided at that web site. Meanwhile, you may leave the device in this state for historical purposes (to preserve statistics, for example) or delete it from the Inventory via the Delete Object and Traces command option (see Deleting an Object and Traces on Page 261). 2.3 Subordinate WM Servers The WM server can act as a Manager of Managers (MoM) when one or more other WM servers are within its network. In this role, it aggregates the information that it receives from subordinate (child) WM servers and facilitates the management of a very large network. Specifically, the MoM server discovers the subordinate server. pushes configurations to it. See Figure 391: Configuration groups for a child WM on Page 616. provides a configuration report about it. See Creating and Using Device Configuration Reports on Page 323. encapsulates its status in a network element dashboard. See Figure 157: Dashboard for a child WM element on Page 218. receives and processes its traps and alarms. provides a device summary report for it. See Figure 161: Device summary report for a child WM element on Page 225. 53
- 54. Issue 3 WM Release 4.0 User Guide May 2012 represents it in the Inventory and Applications tree. represents it by position in the physical map. A client session in the subordinate server provides its own statistics from the set that it sends to the MoM via the properly configured northbound interface (NBI). To see these statistics from the MoM, you can 1. right‐click on the subordinate server in the Inventory and select LaunchClient (or press Ctrl+W). 2. authenticate into the client. 3. from the main menu, select HelpDiagnosticsServer Health Diagnostics. The WM Monitoring window opens and provides time‐based plots for each of the following statistics: server disk free space disk usage disk I/O database disk usage memory utilization database disk free space CPU utilization. 54
- 55. WM Release 4.0 User Guide Issue 3 May 2012 Figure 1: Server disk free space monitoring window for a child WM element Figure 2: Disk usage monitoring window for a child WM element 55
- 56. Issue 3 WM Release 4.0 User Guide May 2012 Figure 3: Disk I/O monitoring window for a child WM element Figure 4: Database disk usage monitoring window for a child WM element 56
- 57. WM Release 4.0 User Guide Issue 3 May 2012 Figure 5: Memory utilization monitoring window for a child WM element Figure 6: Database disk free space monitoring window for a child WM element 57
- 58. Issue 3 WM Release 4.0 User Guide May 2012 Figure 7: CPU utilization monitoring window for a child WM element If you wish, you can keep open an instance of the Collected statistics window for each statistic you want to monitor for as long as the client session remains open. In the MoM client, subordinate server Element Properties are available from a right‐click on that server. See Figure 8, Figure 9, Figure 10, and Figure 11 below. 58
- 59. WM Release 4.0 User Guide Issue 3 May 2012 Figure 8: Element Properties for a subordinate WM server, General tab Figure 9: Element Properties for a subordinate WM server, SNMP tab 59
- 60. Issue 3 WM Release 4.0 User Guide May 2012 Figure 10: Element Properties for a subordinate WM server, Monitoring tab Figure 11: Element Properties for a subordinate WM server, Relationship tab 60
- 61. WM Release 4.0 User Guide Issue 3 May 2012 3 Launching the Client The WM client accesses information from the WM server and displays it graphically. You can browse through the discovered devices in your network, view network and device information, monitor their performance, and identify faults in the network. 3.1 Dependencies The WM client application supports the 32‐bit platform of either of the following operating systems: Windows 7 Professional, 32‐bit. Windows Server 2008 R2 Enterprise Red Hat Enterprise Linux Version 5.5 ES, 32‐bit. The client is launched using the Java Web Start Application Manager. The client requires Java 1.6, which is satisfied as follows: Where Java 1.4.2 or later is present in the client device, WM automatically installs Java 1.6. Where 1.4.2 or later is not present, you must install Java 6 and then launch the client, which will then use Java Web Start to install itself. The client‐related jar files are downloaded when the client connects to the server for the first time. Every subsequent time the client connects to the same server, WM verifies these downloaded files for updates. This client device also requires 15 MB storage space. a high‐speed link of at least 1 Mbps. (Slower connection speed causes slow startup and the possibility of other problems after startup.) screen resolution setting of 1024 x 768. either − Mozilla Firefox 3, if the client is on a Linux or a Windows device − MS‐Internet Explorer 7, if the client is on a Windows device Communications between the server and client require that two port assignments (for NMSSocketPort and NMS_FE_SECONDARY_PORT) are made in the server file system after WM installation or upgrade. These assignments are documented in the quick start guide and the server administration guide. 3.2 Corporate Networks Connections between the client and server are supported across a corporate firewall, presuming that the required ports are configured to be open on the WM server device. a virtual private network (VPN), but with a significant, noticeable reduction in system performance possible. a network address translation (NAT) server. 61
- 62. Issue 3 WM Release 4.0 User Guide May 2012 3.3 Launch Procedures To launch the WM client, perform the following steps. Procedure 1: To launch WM 1. Launch the supported browser. 2. Connect to http://WM_Server_IP_Address:9090. Figure 12: Web page for WM Web Start client invoke (LoginPage.do) 3. Click Launch WM Client. If JNLP is already properly associated with Java Web Start Launcher (javaws), then a pop‐up window suggests the file to open, as shown below. In this case, click OK to let the launch proceed. 62
- 63. WM Release 4.0 User Guide Issue 3 May 2012 If it is not, then the pop‐up window includes a Browse button, as shown below. 4. If the association has not been made with javaws from Java version 1.2.2 or later, create that association wherever it is installed on the client device. 5. If a Warning – Security window pops up, indicating that the digital signature of the application cannot be verified, select the Always trust content from this publisher check box. 6. Click the Run button. 7. On the WM Authentication panel, type in the User ID (possibly root) and Password (possibly public). note ............. The root/public combination is the default administrator account in WM. This account may have been reconfigured during the WM software installation. To find out what account to use for your initial launch of the client, check with the administrator on the WM server device or the technician who installed the software. At the same time, verify that the WM server is using the default port (9090). Figure 13: WM Authentication dialog 8. If you need to change default settings such as port, language, or country, click the Advanced button. 63
- 64. Issue 3 WM Release 4.0 User Guide May 2012 Figure 14: WM Authentication advanced options The default port is 9090. 9. If the port to which the WM Server is listening has been configured as any other port, specify the configured port number in the Port field. 10. Select the language and country of your preference from Language and Country drop‐down boxes respectively. If your client does not support the chosen language, then English is the default language. The Show Console option is selected by default and cannot be deselected. 11. Click Connect. The WM application should now launch successfully. 64
- 65. WM Release 4.0 User Guide Issue 3 May 2012 Figure 15: WM application initial view 3.4 Configuring the Proxy on the WM Client note ............. If the WM client does not currently require a proxy server for access to the Internet, ignore this section. Where a proxy server is used for access to the Internet, some issues must be addressed so that the Physical Map feature and the client/server connection will function properly. The following illustration differentiates the two cases for the relationship between the WM server and client. Figure 16: Possible relationships between client and server 65
- 66. Issue 3 WM Release 4.0 User Guide May 2012 The illustration on the right, where the same device runs both the client and server, is the case where you want to launch the client immediately after installing the WM software. This case requires that all of these instructions are followed. You must enter the information described in this section into both the Java Control Panel and your web browser. 3.4.1 Setting Proxy Information in the Java Control Panel To set the required information in the Java Control panel, perform the following steps on each device where a WM client will be used: 1. Launch the Java Control Panel as follows: ◦ In Windows, select StartSettingsControl PanelJava. ◦ In Linux, enter /usr/local/cambium/wm/jre/bin/jcontrol. Figure 17: Java Control Panel, General tab 2. In the General tab, click the Network Settings button. The Network Settings dialog opens. 66
- 67. WM Release 4.0 User Guide Issue 3 May 2012 Figure 18: Network Settings window in Java Control Panel 3. Select Use proxy server. 4. In the text boxes, type in the address and port of your proxy server. 5. Select Bypass proxy server for local addresses. 6. Click the Advanced button. The Advanced Network Settings window opens. Figure 19: Advanced Network Settings window in Java Control Panel 7. Enter the IP address or subnet mask that matches the address(es) of your server. note ............. For help with this step, contact your network administrator. 67
- 68. Issue 3 WM Release 4.0 User Guide May 2012 3.4.2 Setting Proxy Information in the Web Browser Use the following Firefox Version 3 example procedure as a general primer to configure your browser for proxy information. 1. Launch the browser. 2. Select ToolsOptions. 3. From the icon array at the top, click Advanced. Figure 20: Network tab in Firefox Options window 4. In the Network tab, click the Settings button of the Connection section. The Connection Settings window opens. 68
- 69. WM Release 4.0 User Guide Issue 3 May 2012 Figure 21: Connection Settings window in Firefox note ............. Typically, the next step is not required, because the proxy is already configured. If it were not, then Firefox would not have been previously able to access the Internet. 5. Select Manual proxy configuration and set the HTTP Proxy and Port consistent with the settings in the Java Control Panel. 6. In the No proxy for field, enter the IP address or subnet mask that matches that of the WM server. note.............. This should match what is configured in the Java Control Panel, but may differ in format (for CIDR, for example). In the example shown above, the computer will not look to the proxy for any IP address that matches 10.x.x.x. 3.4.3 Troubleshooting an "Unable to launch the application" Error You may see the following error: 69
- 70. Issue 3 WM Release 4.0 User Guide May 2012 If you see this error 1. ensure that the instructions in the two preceding sections (for configuring the Java Control Panel and your browser) have been properly followed. 2. flush the Java file cache as follows: a. Launch the Java Control Panel as follows: In Windows, select StartSettingsControl PanelJava. In Linux, enter /usr/local/cambium/wm/jre/bin/jcontrol. b. In the General tab, click the Settings button of the Temporary Internet Files section. Figure 22: General tab of Java Control Panel 3. The Temporary Files Settings window opens. 70
- 71. WM Release 4.0 User Guide Issue 3 May 2012 Figure 23: Temporary Files Settings window in Java Control Panel 4. Click the Delete Files button. Figure 24: Delete Temporary Files window in Java Control Panel 5. In the warning window, select both Applications and Applets and Trace and Log Files. 6. Click the OK button. 7. Retry a launch of the WM client. 71
- 72. Issue 3 WM Release 4.0 User Guide May 2012 3.5 Configuring Your Password If a Password Confirmation dialog is displayed as shown in Figure 25 when you log on to the client for the first time, use Procedure 2 to authenticate. Figure 25: Password Confirmation window Procedure 2: To configure your password prior to client connection 1. In the Password Confirmation dialog box, click Configure. 2. In the Type new password field, type in the password that you were assigned to use. 3. In the Confirm new password field, re‐type the same password. 4. In the Password expiry duration field, type the number of days you want your password to be valid. If no value or zero is entered in this field, then the password never expires. 5. Click Connect. The new password is now assigned to you, and you will be connected to the client. Use this new password for future logins. 72
- 73. WM Release 4.0 User Guide Issue 3 May 2012 To change your current WM client password and/or the duration of the period after which your password will expire, use the Password Configurator as follows. Procedure 3: To reconfigure your password 1. After having logged on to the client, select ToolsAdministrationChange Password from the main menu. The Password Configurator dialog box is displayed. Figure 26: PasswordConfigurator dialog 2. Enter the new password in the New Password field. 3. Re‐enter the same password in the Confirm Password field. 4. Enter the number of days you want your password to be valid in Password expiry duration. If no value or zero is entered in this field, then the password never expires. 5. Click OK. The new password will be assigned to you. You need to enter this new password for future logins. 3.6 Troubleshooting an Unsuccessful Login The following table lists the messages that are displayed in certain situations during the login process. Table 2: Troubleshooting client login issues Message Reason Remedy You are logged in for the This pop‐up message is displayed first time, would you when you log on to the client for like to reuse the the first time (only if this has Use Procedure 2 on Page 72. existing password or been enabled by your configure a new password? administrator). 73
- 74. Issue 3 WM Release 4.0 User Guide May 2012 Message Reason Remedy Either set a new password or retain the old password. To keep the same password for the same expiration period, Your password has click Reuse. To enter a new password expired. Would you like and reset the expiration period, click to reuse the old password Your password has expired. Configure and use Procedure 2 on or configure a New Page 72. password? If you do not have the permission to set your password, contact your system administrator. This User account has Your user account has expired. Expired. Please contact Contact your system administrator to The user account is created by the Administrator for renew your user account. further details your system administrator. Your user account has been disabled by your system This User account is administrator. Disabled. Please contact Also, if your consecutive login Contact your system administrator to the Administrator for attempts fail for a certain number enable your user account. further details of retries (number is configured by the administrator), the user account is automatically disabled. 74
- 75. WM Release 4.0 User Guide Issue 3 May 2012 4 Using the Client Window The client window provides the following context‐sensitive components: a main menu at the top of the main window a toolbar composed of icons beneath the main menu an Applications tree that lists in hierarchy the various WM modules in the upper left side of the main window an Alarm Summary View in the lower left side of the main window a view frame that can contain a map or a view on the right side of the main window. Figure 27: Client window, example 4.1 Using the Toolbar The Toolbar displays a collection of actions, commands, and control functions. It is located beneath the menu bar and supports various tools for different modules of WM. The Toolbar is useful for displaying frequently used components. A tool tip identifying supported operations is provided for each tool. The following figures illustrate how the set of toolbar selections varies from one module to another. For example, the Fault Management module has additional toolbar options, such as Add Custom View and Modify Custom View. 75
- 76. Issue 3 WM Release 4.0 User Guide May 2012 Figure 28: Toolbar when Dashboard is displayed Figure 29: Toolbar when Network Events are displayed Figure 30: Toolbar when Alarms are displayed Figure 31: Toolbar when Configured Collection is displayed Figure 32: Toolbar when Templates view is displayed Figure 33: Toolbar when Inventory view is displayed Figure 34: Toolbar when Reports are displayed Figure 35: Toolbar when Scheduled Tasks are displayed Figure 36: Toolbar when Policies view is displayed Some toolbar options are common for all views in the client. Others depend on module functions. The following options are available for all the views in the client. 76
- 77. WM Release 4.0 User Guide Issue 3 May 2012 Table 3: Common toolbar options Go Back to Previous Go Forward to Next Detach Current Window Help To hide or show the toolbar, scroll over the vertical line on the left side of the toolbar to activate the Hide Toolbar tool tip and click to execute the command or toggle the Show Toolbar command from the window menu. 4.2 Using the Alarm Summary Views In addition, the default construction of the client window includes Device Status and Severe Alarms views, displayed in the lower left corner of the WM client window, beneath the Applications tree. These provide a summary of all the alarms tracked by WM. The Device Status panel shows the alarm count of each category from Critical to Clear. This panel is automatically refreshed when events are generated. Use the buttons at the top of the panel to display Severity against number of devices view Severity alone in a pie chart view Figure 37: Alarm summary views This panel is updated automatically and the counts can be seen at all times, not depending on what is in the view frame. You can view all the devices under a specific severity of alarm. In the severity against number of devices view of the Device Status panel, click either the severity or the bar associated with the severity (or click the severity box in the Severe Alarms panel. For example, if you want to view all the Major alarms, click the Major box under Severe Alarms. Regardless of what views or open or what view is on top, WM launches an Inventory view with only those devices that are under an alarm of the selected severity. 77
- 78. Issue 3 WM Release 4.0 User Guide May 2012 Figure 38: View of devices under Warning note ............. To return to a full Inventory view after the slim view of only those devices under a particular alarm severity, click the Show All button. The Severe Alarms panel displays the counts in only the Critical, Major, and Minor severity. When no alarms are present in a severity, WM displays its count against a grey background. When alarms are present, the count displays against the coded color of the severity: red for Critical, orange for Major, and Yellow for Minor. This panel never displays alarms of lesser severity. Figure 39: Severe alarm counts Discovering alarms occur during the discovery process, where nodes are added to the WM inventory of managed objects. The client provides more detailed alarms and device information in its system dashboard, which is described under Monitoring the System Dashboard on Page 115. 4.3 Using the Status Bar The Status Bar at the bottom of the screen indicates the status of the ongoing process. For example it displays Done if all the data is loaded or loading... if the process is still not complete. 4.4 Using the Display Panel The display panel is on the right‐side of client and appears as a window within the main window. This panel is shown when a tree node is selected. For example, if you click Fault ManagementEvents on the tree, then the Events display opens in the right side panel. 78
- 79. WM Release 4.0 User Guide Issue 3 May 2012 4.5 Using the Menu Bar The menu bar is located at the top of the Display area. Select a menu and choose a command to perform a desired function. Certain menu bar drop‐down menus (File, Tools, Window, and Help) are common for all views in the client. The set of active menu bar menus differs as follows for various views. Views of the following types have no Edit menu: − Dashboard − Physical Map − System Reports − Reports Results − Scheduled Tasks no View menu: − Scheduled Tasks no Actions menu: − Dashboard − System Reports − Reports Results all menu bar menus: − Inventory − Network Events − Alarms − Configuration Templates − Configuration Report Templates − Configured Collection − Policies 79
- 80. Issue 3 WM Release 4.0 User Guide May 2012 4.6 Using the Help Menu 4.6.1 About Wireless Manager The main menu selection HelpAbout Wireless Manager displays the About panel, which includes tabs that display details about licenses, SNMP agents, the WM client application, and defined device templates. Figure 40: About window, License tab About License Tab This tab provides current totals of used ( ), available ( ), and used+available ( ) licenses for each license type. Since License Manager is configured as part of WM installation and upgrade procedures, and since the purchased licenses are deployed into the file system in the WM server, the Wireless Manager Release 4.0 Server Administration Guide provides the full details on how the licensing scheme works in this release. However, the WM client application cautions users in the client application when a license deficiency seems to be approaching. A WM server checks out one count of the license specified in the WMEMSPack license whenever a device (other than a PMP Series SM or PTP Series Slave) is discovered and managed by WM. When the number of checked out license counts at the license server reaches 90% of the total license counts, WM opens a modal dialog window to users in current 80
- 81. WM Release 4.0 User Guide Issue 3 May 2012 sessions and to users who users who are launching the client application, warning that more WMEMSPack license capacity will be required. When the number exceeds the total of licenses, no license will be made available for check out until a licensed device is deleted from a network and thereby forfeits the license that had been allocated by License Manager to it. When you click on the Manage Licenses button, WM prompts you to enter the Login Name and Password that WM uses for its own access to the License Manager server (by way of the licensing web server). If you enter these correctly (consistent with how they were saved in the Administrator Tool on the server), then a web browser is spawned, open to the web interface of License Manager. Figure 41: License Manager web interface Changing Your Account Parameters for Tool Access The License Manager Administrator Tool allows you to change how you authenticate to get access through the web server to the tool. You may want to periodically do this for security. To do so, access the tool, then click the Password button in the License Manager panel. An example of the resulting Change Password panel is shown in Figure 42. 81
- 82. Issue 3 WM Release 4.0 User Guide May 2012 Figure 42: Change Password panel, License Manager Administrator Tool note ............. The License Manager area of the Administrator Tool is not capable of prompting for, storing, or implementing account changes for the License Manager Administrator Tool users. Your new user name and password should be ones that are easy for you to recall. Assistance for forgotten user names and passwords is not available. As you type in your old, new, and confirmed new passwords, asterisks represent the characters. When you are satisfied with the new account information, check the Synchronize password and configuration to redundant servers check box and click the Save Changes button. After you have reset the password but before you use the License Manager Administrator Tool web site, you must click the link for Licensing Configuration, then change the password for the local server and click the Save Changes button. Similarly, before you use the server Administrator Tool for license administration, your server administrator must reset the Password field in the License File Data panel of the WM Server Administrator Tool, and then click the Save Configuration button. 82
- 83. WM Release 4.0 User Guide Issue 3 May 2012 About Device Details The count that the device details tab provides represents the total number of agents across all network elements that are currently under WM management. Figure 43: About window, Device Details tab Each agent of a multi‐agent generic device is counted as one instance in the agent count. 83
- 84. Issue 3 WM Release 4.0 User Guide May 2012 About Client Details The information that the Client Details tab displays information that is designed for technical support purposes and not intended for operator use, except when it is requested by a Cambium Networks customer support representative. Figure 44: About window, Client Details tab About Supported Device Templates The Supported Device Templates tab provides the names of all device types that WM supports and of the templates that make some of the operations in support of them possible. These templates should not be confused with either configuration templates, which push values of configurable attributes to managed elements configuration report templates, which retrieve, format, and display attribute values from either the database or the device(s). 84
- 85. WM Release 4.0 User Guide Issue 3 May 2012 Figure 45: About window, Supported Device Templates tab By contrast, the device templates define the devices in such a way that WM is able to distinguish, among other factors the element type from other element types during discovery the firmware version loaded in the element the icon by which to represent the element in the WM user interface the name by which to identify it in various views the performance data statistics to query from it the configuration data that is appropriate to push to it the air standard that applies to it, for radios in the physical map. 4.6.2 Help Contents The main menu selection HelpHelp Contents provides links to the index of on‐line help topics and this user guide, the server administration guide, and the technical support web page. 85
- 86. Issue 3 WM Release 4.0 User Guide May 2012 4.6.3 Diagnostics The main menu selection HelpDiagnostics provides links to the customer support tool (see Running the Customer Support Tool on Page 749) JVM monitoring details (see Logging JVM Monitoring Details on Page 702). 4.7 Managing Client Windows 4.7.1 Navigating through Active Windows When many windows are open in the display panel, you can move forward to the next active screen or move back to the previous one. To move back to the previous window, from the File menu, choose Back or click (Go Back to Previous) on the toolbar, or press Ctrl+Shift+B. To move to the next window, from File menu, choose Forward or click (Go Forward to Next) on the toolbar, or press Ctrl+Shift+F. 4.7.2 Detaching a Window from the Client The following views can be detached from the display panel of the client for viewing as a separate window: system dashboard physical map Inventory view, including custom views and the inventories of a device groups Alarms view Network Events view Configured Collection Scheduled Tasks Policies To detach a window, perform any of the following steps: Right‐click on the node in the Applications tree and select DetachDetach from the drop‐ down list of options. Click (Detach Current Window) on the toolbar. Press Ctrl+Shift+T. To re‐attach a window into the view panel, click the close window button in the upper right corner of the detached window. 86
- 87. WM Release 4.0 User Guide Issue 3 May 2012 tip ................ Position the detached window far enough from its docked position that you can easily distinguish that it is undocked. Otherwise, you might inadvertently close a view that you intended to only reattach. 4.7.3 Saving Location and Size of Windows When you rearrange and resize windows, you need to save them to retain the same location and size. To save location and size after rearranging and resizing windows, select WindowSave Location and Size. You will be able to see the retained location and size when you reopen the client. 4.7.4 Closing All Open Windows To close all the open windows, perform any of the following procedures. Select FileClose All. Press Ctrl+Shift+O. 4.8 Using the Applications Tree The Applications tree pane located on the left side of the client displays a set of hierarchical data representing the current network configuration. At the top of the tree is the physical map. Some nodes of the Applications tree are available permanently (by default) in the client, and others are dynamically added. Each node is selectable, each parent node is expandable and collapsible, and each ultimate child node determines the view that is displayed in the right (opposite panel) of the main client view. The following nodes compose the Applications tree. Table 4: Applications tree nodes Parent Node Default Child Nodes Described Under Monitoring the System Dashboard on Dashboard none Page 115 Physical Map none Using the Physical Map on Page 145 one for each device type present in the network, represented by its icon and its textual string Using an Inventory View on Page 121 Inventory a device type selection for Networks Creating and Using Device Groups on a device type selection for Device Groups Page 299 87
- 88. Issue 3 WM Release 4.0 User Guide May 2012 Parent Node Default Child Nodes Described Under one for Network Events Working with Events on Page 345 Fault Management one for Alarms Handling Alarm on Page 364 Using Configuration Templates on one for Configuration Templates Page 618 Importing Configuration Report Templates on Page 324 Configuration one for Configuration Report Templates Exporting All Configuration Report Templates on Page 337 Table 45: Configuration options on one for Audit Page 469 Using System Reports on Page 388 Viewing a Device Summary Report on none (use parent node for viewing and running the Page 223 available reports) Launching an Operator‐defined Report on Page 397 System Saving a Device Summary Report on Reports Page 226 Deleting a Device Summary Report on Page 227 one for Report Results Using a Configuration Summary Report as Preconfigured on Page 342 Using a System Report As Preconfigured on Page 396 Performance one for Configured Collection Monitoring Performance on Page 379 Scheduling a One‐Time or Periodic Task one for each defined Scheduled Task on Page 647 Administration one for Policies Administering a Policy on Page 603 88
- 89. WM Release 4.0 User Guide Issue 3 May 2012 Figure 46: Expanded view of the Applications tree 89
- 90. Issue 3 WM Release 4.0 User Guide May 2012 The fundamental element in the tree is a node that represents a data item in the given hierarchical set. The root node is the top node of the hierarchical data. Nodes inside the root nodes are called child nodes. Nodes that contain no child nodes are called leaf nodes. When you select a particular node, the corresponding panel is displayed on the right side of the display panel. A series of drop‐down menus is available by selecting nodes in the Applications tree. Select a device, then right click to display the drop‐down menu. The following sections explain the available menu commands. note ............. The deepest branches of the Inventory tree list links as NameID Links under the higher branch of their device type. The longest NameID supported for this list is 100 characters. Any device whose NameID is longer is not listed among the Links list. Table view refers to the display panel on the right side of the client. For instance, clicking on Alarms node under the Fault Management node displays a panel on the right side that shows a table containing details of the generated alarms. Common right‐click menu options are available for several of the Applications Tree nodes. 4.8.1 Custom Views A custom view is a tailored view that can be created for viewing a subset of data that satisfies specific criteria. A search operation can be performed to locate a specific element, but a custom view would be useful to locate a set of elements that satisfy a certain set of criteria. Custom views can be created in an Events, Alarms, Configured Collection, or Inventory view. Network maps can also be created and modified using the Custom Views menu. The option to create a custom view is available based on user privileges. Contact your system administrator to determine your user privileges. You can configure an unlimited number of custom views of events, alarms, and or performance statistics. These views are filters. They are not static, but rather are updated as new events, alarms, or statistic values (respectively) becomes available to the system, even as you are examining the view. Adding a Custom View When any non‐map view is the front window in the view frame, you have the option to add a new custom view of your own definition. From the main menu, select ViewCustom ViewsAdd Custom View. The type of criteria dialog that WM opens for you to configure depends on the type of view that is in front in the view frame: To add a custom events view filter, see Defining an Events Custom View on Page 356. To add a custom alarms view filter, see Defining an Alarms Custom View on Page 372. To add a custom performance view filter, see Defining a Performance Custom View on Page 592. To add a custom inventory view filter, see Inventory Custom Views on Page 126. When you add a custom view, the name of the view (a link to it) is placed into the Applications tree. Each other view that you create in the same module (Network Events, Alarms, or Configured Collection) can be either a direct child of the module link or a child (filter) of another custom view that was user‐created, as Alarms 12 is in the following example. 90
- 91. WM Release 4.0 User Guide Issue 3 May 2012 Figure 47: Example parent custom view with child view Modifying a Custom View You can modify any of your defined custom views as follows. To do so, click on the link to the custom view in the Applications tree as shown below. Figure 48: Custom view nodes in Applications tree WM opens the filter criteria window that you populated when you originally added the view (or that you last modified). Make whatever changes you wish to the values of the various properties. When you are entirely finished reconfiguring the view filter and/or its appearance in the Applications tree, click the Apply Filter button to modify the stored view filter. Renaming a Custom View At any time, you can rename a custom view. To do so, right‐click on the link to the custom view in the Applications tree, then select ViewCustom ViewsRename Custom View from the main menu. In the Applications tree, the name of your custom view is enclosed in an edit box. Change the name as you wish, then press your Enter ( ) key to end the edit session. Resizing Columns in a Custom View Custom view support resizing of their columns (for example, so that you can view all of the data without scrolling). To resize a column, position the mouse cursor over the right border of the column head, left‐click and hold down the button, and drag the border. You can save the resized structure so that when you reopen the view, the columns will be of their current width. To do so, do all of the resizing that you intend to do, then right‐click on the view name in the Applications tree and select Save Custom View State from the drop‐down list of options. If you do not execute this option, the view will reopen with the default column widths next time. 91
- 92. Issue 3 WM Release 4.0 User Guide May 2012 Custom views also support reordering their columns. To do so, position the mouse cursor anywhere in the column head, left click and hold down the button, and drag the entire column. The rearrangement will last as long as the view remains open, even when it has no longer been the front in the view frame. However, the rearrangement will not be saved, even if you execute the Save Custom View State option. The view will revert to the column arrangement that was configured when the view was created. Removing a Custom View To remove a custom view, click on the link to the custom view in the Applications tree, then select ViewCustom ViewsRemove Custom View from the main menu. This does not cause WM to drop elements that were contained in the view, but it does remove the view from both the Applications tree and WM memory. So, if you ever want to re‐establish this view, you must specify all of its criteria over again through the Add Custom View option. important ........... Removing a custom view automatically removes all child custom views, if the one you are removing is a parent view. For example, removing Alarms 1 will automatically remove Alarms 12 in the example branch shown in Figure 47 on Page 91. 4.8.2 Frame Operations Common Frame Operations for Back, Forward, Detach and Close Frame support navigation through the view panels. 4.8.3 Administration Tools The Administration Tools branch of the Applications tree provides access to the area in which a user who has a sufficient level of privilege can administer policies. These operations are described under Administering a Policy on Page 603 Scheduling a One‐Time or Periodic Task on Page 647. 4.9 Using the Search Utility Above the Applications tree in the left panel of the main client window, a Search utility returns matching results from various data fields in WM. 92
- 93. WM Release 4.0 User Guide Issue 3 May 2012 WM looks for matches between the input string and the contents of various data fields in the database. Table 5 lists these fields against the types of results that WM will return for them. Table 5: Input string vs. result types for Search utility Input String Typical Returned Results Example Customer Contact Device Groups Networks Statistics Devices Alarms Data Events View Field Figure Page Configured Statistic Name Figure 49 94 Collection Data Identifier Message Figure 50 95 Network Events Source Figure 51 96 IP Address Name (ID) Networks Figure 52 96 IP Address Source Figure 53 97 Alarms IP Address Alarm Message Figure 54 98 Device Name Figure 55 98 Location Figure 56 99 Inventory Name (ID) Figure 57 99 IP Address Device Groups Device Group Name Figure 58 100 Customer Name Customer Type Address 1 Address 2 City State Customer Zip Contact Figure 59 100 Country Management Email Home Phone Work Phone Mobile Phone Pager Devices 93
- 94. Issue 3 WM Release 4.0 User Guide May 2012 The following example figures are referenced in Table 5 above. Figure 49: Search results for input Statistic Name contents 94
- 95. WM Release 4.0 User Guide Issue 3 May 2012 Figure 50: Search results for input Message contents 95
- 96. Issue 3 WM Release 4.0 User Guide May 2012 Figure 51: Search results for input Source contents Figure 52: Search results for input network Name (ID) 96
- 97. WM Release 4.0 User Guide Issue 3 May 2012 Figure 53: Search results for input IP Address contents 97
- 98. Issue 3 WM Release 4.0 User Guide May 2012 Figure 54: Search results for input Alarm Message contents Figure 55: Search results for input Device Name contents 98
- 99. WM Release 4.0 User Guide Issue 3 May 2012 Figure 56: Search results for input Location contents note ............. In the above example, BOST Lab is part of the configured Location contents and is also coincidentally part of the name of a defined device group. Figure 57: Search results for input Name (ID) contents 99
- 100. Issue 3 WM Release 4.0 User Guide May 2012 Figure 58: Search results for input Device Group Name contents Figure 59: Search results for input Address1 contents Each listed item in a results group provides a mouse hover tooltip that includes preselected detail about the item. The group titles of returned results contain links to further information: Clicking on the plus leaves the group expanded and collapses the other groups. 100
- 101. WM Release 4.0 User Guide Issue 3 May 2012 Clicking on the minus sign expands all of the results groups. Clicking on the number in parentheses opens a view of the results group in the view panel. Clicking on the magnifying glass associated with a results group opens a Search window that accepts multiple criteria and operates as described under Search on Page 123: − If the results group is Devices, then the criteria for a narrower search are − If the results group is Alarms, then the criteria for a narrower search are 101
- 102. Issue 3 WM Release 4.0 User Guide May 2012 − If the results group is Events, then the criteria for a narrower search are − If the results group is Statistics, then the criteria for a narrower search are note ............. The Device Groups and Customer results groups do not contain an icon with which to launch a narrower search (do not support advanced search). 4.10 Performing Table View Operations Table View refers to the display panel that you can view on the right side of the client. For instance, clicking on Alarms node under Fault Management node displays a panel on the right side that shows a table containing details of the generated alarms. 102
- 103. WM Release 4.0 User Guide Issue 3 May 2012 Figure 60: Alarms table view The table views are available in only Fault Management, Network Events, and Configured Collection modules, and they differ from module to module. 4.10.1 Navigating Through a Table The four navigator buttons, First Page, Previous Page, Next Page, and Last Page are located at the top of each table. The purpose of these buttons is detailed in the following table. Table 6: Table navigation buttons Button Purpose To view the first segment, based on current sorting scheme, of the list of entries that are stored First Page in the database. For example, if the table is sorted in the order of most recent items first, then First Page shows the segment of newest items. Previous Page To view the previously viewed segment of the data retrieved from the database. 103
- 104. Issue 3 WM Release 4.0 User Guide May 2012 Button Purpose To view the next segment, based on current sorting scheme, of the data retrieved from the Next Page database. To view the last segment, based on current sorting scheme, of the list of entries that are stored in Last Page the database. For example, if the table is sorted in the order of most recent items first, then Last Page shows the segment of oldest items. 4.10.2 Setting the Page Length for a Table The greater the set page length, the more data is retrieved from the WM server, and thus the slower its response will be. To display only a certain number of rows per page, select the value from the Page Length drop‐down list. Settable increments are 50, 100, 250, 500, 1000, 2500, 5000, 10000, 25000, and 50000. 4.10.3 Refreshing the Page View To refresh the page view, perform any of the following procedures. Right‐click a row and click Refresh. Select ViewRefresh. Press F5. 4.10.4 Viewing a Range of Table Details Procedure 4: To view a range of details 1. In the Displaying field, enter the starting range number. 2. In the to field, enter the ending range number. 3. Press Enter. 4.10.5 Sorting Table Details You can sort the data in a table based on the column type and the details can be viewed either in ascending or descending order. The type of sorting (ascending or descending) is indicated by arrows. A simple click on the column header does the sorting, i.e., the complete data will be sorted. Subsequent click on the same header sorts the data in ascending order (if it were sorted in descending before). There are two types of sorting: Server‐side sorting: Server‐side sorting sorts all data in the WM Server and is not restricted to the data available in the client. For example, if there are 100 events in the WM Server and only 50 are displayed in the Page View of the table, a server‐side sorting sorts the complete 104
- 105. WM Release 4.0 User Guide Issue 3 May 2012 set of 100 events and not just the 50 events. For server‐side sorting, click the column header. Subsequent click on the same column header sorts the data in ascending order (if it were sorted in descending before). The sort indicators for server‐side sorting for ascending and descending are and , respectively. Client‐side sorting: Client‐side sorting sorts data displayed only in the client. For example, if there are 50 alarms in the WM Server and only 25 are displayed in the Page View of the table (25 per page), a client‐side sorting sorts only 25 alarms and not the 50 alarms in the WM Server. For client‐side sorting, press the Ctrl button and click the column header. Subsequent click on the same header sorts the data in ascending order (if it were sorted in descending before). The sort indicator for client‐side sorting for ascending and descending are and , respectively. 4.10.6 Rearranging and Resizing Columns in a Table For easy view of the data, rearrange the columns by just dragging the column header and moving it to the desired place in the table. You may find it helpful to view a some of the data at closer position. To resize the column header, drag the right‐side edge of a column. tip ................ When performing the rearrangement and resizing, the table remains the same only until the client is closed. When it is reopened, the settings would be lost. To retain the same size of columns, you should save the style by selecting the main menu item ViewCustom ViewsSave Custom View State or right-clicking on the node in tree and selecting Custom ViewsSave Custom View State or pressing Ctrl+S. important .......... When saving a custom view, ONLY the resizing is saved, and any rearrangement is not saved, and the custom view is displayed in the default order. 4.10.7 Viewing Row Details To view details or object properties of each row in a table, perform any of the following procedures: Double‐click a row in any view, including a Configured Collection. Press Alt+D in an Events, Alarms, or Inventory view. Right‐click a row in an Events or an Alarms view and click Details. A dialog box is displayed with specific details about the selected row. 4.11 Importing Data Files Into WM WM provides a utility to import CSV files (or, in a lone instance, a text file) that WM will use for device discovery information This operation requires permissions in TopologyAdd Node and Add Network. See Figure 300: Assign Permissions dialog on Page 444. 105
- 106. Issue 3 WM Release 4.0 User Guide May 2012 user account information This operation requires permissions in User AdministrationAdd Users and Assign User To Group. See Figure 300: Assign Permissions dialog on Page 444. customer contact information This operation requires operation permissions in Administrative OperationEmail Configuration. The only supported delimiter in the CSV files is comma. However, for any instance of a literal comma in a data field, the comma must be enclosed in two of a consistently used escape character type. The client refers to such a character as a Text Qualifier. The types allowed are double quote and single quote (apostrophe). Two examples of the supported use of a text qualifier for any of these CSV files are as follows: 12345,Chris Brown","Sean Brown,home,123 Main,Mount,WY,USA,[email protected],4061234567,,,,0a 00 3e 30 2d e4 12345,Chris Brown','Sean Brown,home,123 Main,Mount,WY,USA,[email protected],4061234567,,,,0a 00 3e 30 2d e4 Within a column, the supported delimiter between multiple entries is semicolon. For specific information on preparing each type of file data for import, see the following other sections of this user guide: Importing Device Discovery Information on Page 399 Importing User Account Information on Page 437 Importing a Customer Contact Database on Page 238 All of these options are available from the main menu by selecting ToolsImport and Export. The client responds to this selection by opening the Select operation window. 106
- 107. WM Release 4.0 User Guide Issue 3 May 2012 Figure 61: Select operation window Select the desired import option radio button, then click the Next button. The Import window opens. Figure 62: Import information windows For Text Qualifier, select the escape character that the CSV file you are about to import uses consistently, if any. Then click the button. The Select CSV file window opens. 107
- 108. Issue 3 WM Release 4.0 User Guide May 2012 Figure 63: Select file window Browse to and select the file to import. Back in the previous window, click the Next button. If the import succeeds, then the system responds with a Results window message similar to the following: 4.12 Exporting Data Files From WM note ............. The following operations require permission in TopologyModify Object ExportTopology Data. See Figure 300: Assign Permissions dialog on Page 444. 108
- 109. WM Release 4.0 User Guide Issue 3 May 2012 WM provides a utility to export CSV (comma‐separated values) files that another system or another instance of WM will use for device discovery information (see Exporting Device Discovery Information, next) user account information (see Exporting User Account Information on Page 111) network hierarchy information (see Exporting Network Hierarchy Information on Page 113) 4.12.1 Exporting Device Discovery Information To export a CSV file of device discovery information, perform the following steps. Procedure 5: To export device discovery information 1. From the main menu, select ToolsImport and Export. The Select operation window opens. 2. Select the Export device discovery information radio button. 3. Click the Next button. The Export device discovery information window opens. 109
- 110. Issue 3 WM Release 4.0 User Guide May 2012 4. Check the check box(es) of all of the types of discovery information you want included in the file for export. 5. Click the Next button. The Export device discovery information window changes to include the following fields. 6. Leave the Text Qualifier selection of double quote. 7. Click the button. The Select directory to store exported file window opens. 8. Browse to and select the directory. The path to the selected directory populates the path text field. 9. Click the Next button. The Export device discovery information‐ Results window opens with a confirmation of the export: 110
- 111. WM Release 4.0 User Guide Issue 3 May 2012 10. Click the Finish button. The exported file is formatted according to the rules described in Table 37 on Page 399 and is written to the file name DeviceDiscoveryInformation_UniqueIdentifier.csv in your selected directory. 4.12.2 Exporting User Account Information This operation requires operation permissions in User AdministrationGet List of Users. See Figure 300: Assign Permissions dialog on Page 444. To export a CSV file of user account information, perform the following steps. Procedure 6: To export user account information 1. From the main menu, select ToolsImport and Export. The Select operation window opens. 111
- 112. Issue 3 WM Release 4.0 User Guide May 2012 2. Select the Export user account information radio button. 3. Click the Next button. The Export user account information window opens. 4. Leave the Text Qualifier selection of double quote. 5. Click the button. The Select directory to store exported file window opens. 6. Browse to and select the directory. The path to the selected directory populates the path text field. 7. Click the Next button. The Export user account information‐ Results window opens with a confirmation of the export: 112
- 113. WM Release 4.0 User Guide Issue 3 May 2012 4.12.3 Exporting Network Hierarchy Information To export a CSV file of network hierarchy information, perform the following steps. Procedure 7: To export network hierarchy information 1. From the main menu, select ToolsImport and Export. The Select operation window opens. 2. Select the Export network hierarchy information radio button. 3. Click the Next button. The Export network hierarchy window opens. 4. Leave the Text Qualifier selection of double quote. 5. Click the button. The Select directory to store exported file window opens. 113
- 114. Issue 3 WM Release 4.0 User Guide May 2012 6. Browse to and select the directory. The path to the selected directory populates the path text field. 7. Click the Next button. The Export user account information‐ Results window opens with a confirmation of the export: This exported file consists of only two columns of data: Name, whose value in each row is the Name (ID) of the child element in a parent‐child relationship Parent, whose value in each row is the Name (ID) of the parent element of that child. 4.13 Recovering from a Lost Connection to the Server While you use the client application, if the WM server goes down or you otherwise lose connection to the server, a pop‐up confirmation asks whether you want to exit the client. If you click the Yes button, then the client session closes. If you click the No button, the session remains up. However, some operations in it may indefinitely freeze, including the Discovery Configurator. Any problems of this kind are resolved when you exit and then re‐launch the client. 114
- 115. WM Release 4.0 User Guide Issue 3 May 2012 5 Monitoring the System Dashboard At the top of the list of links in the Applications tree is Dashboard, which puts six contiguous system‐ configured displays on top in the view panel: Alarms by Severity, viewable as a pie chart or bar chart Alarms by Device Type, viewable as a bar chart or table Recent Alarms, viewable as a pie chart, bar chart, or table Alarms by Message, viewable as a bar chart or table Device Counts, viewable as a bar chart or table Help, with the following tabs: − Useful Links. By default, these open the browser to the release‐specific user guide or server administration guide. (The Help Index link opens a page that provides links to these guides.) − License. This tab provides the same summary information that the License tab of the About window provides. See About License Tab on Page 80. − Device Details. This tab provides the same summary information that the Device Details tab of the About window provides. See About Device Details on Page 83. − Settings. This tab provides the option to remove from the dashboard view all alarms of the severity Clear. Thus, for practical purposes, checking the Hide clear alarms check box in the Settings tab transforms the entire dashboard into a troubleshooting panel. Unchecking it returns the dashboard to a display of network health. The dashboard opens by default the first time the client is launched. Each pie chart (click ) provides a complete representation. Each bar chart (click ) whose content is too large to fit in a single page continues across pages that are linked by and buttons. Each table (click ) whose content is too large continues in its vertical dimension by a scroll bar. 5.1 Dashboard Refreshes No action is required to update the data or the graphical representations. The dashboard automatically refreshes when the client is launched, whenever the client receives a notification from the server (except that each alarm is represented only once regardless of repeated instances), and once daily in addition to those occasions. The only exception is that, when the client receives a notification within three seconds of the last, it delays the dashboard update until three seconds have elapsed since its last update. However, you can refresh the entire dashboard at any time by clicking the Settings tab of the Help display and clicking the Refresh Dashboard button. The primary sort order for each of the pie, bar, and table displays is severity. The secondary is count. 115
- 116. Issue 3 WM Release 4.0 User Guide May 2012 5.2 Dashboard Display Options Figure 64: Dashboard Alarms by Severity display Figure 65: Dashboard Alarms by Device Type display Figure 66: Dashboard Recent Alarms display 116
- 117. WM Release 4.0 User Guide Issue 3 May 2012 Figure 67: Dashboard Alarms by Message display Figure 68: Dashboard Device Counts display Figure 69: Dashboard Help display, Useful Links and License tabs 117
- 118. Issue 3 WM Release 4.0 User Guide May 2012 Figure 70: Dashboard Help display, Device Details and Settings tabs Figure 71: Clear Alarms Included Figure 72: Clear Alarms Hidden One of the convenient aspects of the network health preference (clear alarms included) is the ability to monitor the process of successful discovery by tracking the Discovering alarms in the Alarms by Severity display. If you hide clear alarms, then these Discovering alarms are among those that are not shown. You may prefer to display the Clear alarms until discovery has concluded and then hide them. 5.3 Strategic Use of the Dashboard As with most of the more important view panels in WM, you can detach the dashboard from the view panel by clicking in the contextual menu of icons and drag it to somewhere else on the desktop. This allows you to continually monitor its displays while you work in other view panels. While the window is detached, if you click elsewhere in the client interface, the detached dashboard disappears and remains gone (even if you minimize the other view), but reappears in its detached position if you click the Dashboard link in the Applications tree. When you want to return the dashboard to the view panel, click the close window icon in the upper right corner of the dashboard window. A higher‐level alternative to the dashboard is the combination of the Device Status and Severe Alarms display beneath the Applications tree. See Using the Alarm Summary Views on Page 77. This display persists through any succession of views in the view panel to its right. Changes that you see in it may encourage you to view the greater detail that the dashboard presents. 118
- 119. WM Release 4.0 User Guide Issue 3 May 2012 5.3.1 Click-throughs From the Dashboard The data representations in the dashboard are interactive for click‐throughs to other views that then open in the view panel. The view that opens depends as follows on the display component that you click: In this display… if you click this… this view opens… and consists of… pie section, bar, or label Alarms by Severity Alarms alarms of that severity in the network of a severity bar or length of bar, label alarms of that severity in devices of of a severity, or cell in a Alarms that device type Alarms by Device Type severity column alarms of all severities in that device label of a device type Alarms type pie section, bar, label of a alarms of that severity in the network severity, or cell in the Alarms within the last hour Severity column Recent Alarms alarms that occurred in the network at cell in the Date column Alarms that second cell in the Message alarms whose messages match within Alarms column the last hour in the network alarms whose messages match in the bar label or bar Alarms network and/or the trap/error message thrown cell in the Severity Alarms alarms of that severity in the network column Alarms by Message alarms whose message and severity cell in the Alarms column Alarms match the message/severity that this cell tallies cell in the Message alarms whose messages match in the Alarms column network bar or length of bar, or devices that are of the device type and Inventory cell in a severity column are under an alarm of that severity Device Counts label of a device type Inventory devices that are of the device type cell in the Count column Inventory devices that are tallied in that cell The basis of these displays is with one exception the data that the client received in its last refresh. The exception is that the Recent Alarms display retains each alarm for one hour. Mouse‐overs on bars of a bar chart briefly open a tool‐tip that provides the exact number in the category. 119
- 120. Issue 3 WM Release 4.0 User Guide May 2012 5.3.2 Sortable Table Displays The table displays are not sortable for Alarms by Device Type and Device Counts, but are sortable for Recent Alarms and Alarms by Message. One click of the column header sorts all of the table data by the entries in that column. Another click of it sorts by that column, but in reverse order. For example, the default order for Recent Alarms is most‐to‐least recent, based on the entry in the Data column (which includes both date and time). If you want to see all instances of a particular message in contiguous rows, you would sort the Message column and scroll to the set of those messages. 120
- 121. WM Release 4.0 User Guide Issue 3 May 2012 6 Using an Inventory View WM opens to the Inventory view. When any other view is in front in the view frame, you can bring this view to the front by clicking on the Inventory node in the Applications tree. The table in the Inventory panel provides a list of data and status for all devices that WM has successfully discovered. Figure 73: Inventory view For each element, the Status column entry indicates one of the following: the highest severity current alarm against each device, the discovery status 121
- 122. Issue 3 WM Release 4.0 User Guide May 2012 the discovery status (which takes precedence over the alarm severity if a device is being discovered) the management status if a device is unmanaged. Possible values are Critical, Major, Minor, Warning, Discovering, Degraded, and Clear. Devices may show the status Discovering long after the Event viewer includes the event Discovery finished for the device. This is because the Status value in an Inventory view is intended to remain Discovering until deep discovery has concluded for the device. See Stages of Discovery on Page 432. For the Inventory branch, the Applications tree includes, after Networks, a list of selectable device types by which you can access an Inventory view that consists of only devices whose type(s) is selected (highlighted). Figure 74: Device types list in Applications tree, example 122
- 123. WM Release 4.0 User Guide Issue 3 May 2012 The fundamental element in the tree is a node that represents a data item in the given hierarchy. Before the first‐ever discovery is performed in WM, no device types are listed. This is because the list intends to reflect only discovered device types and, therefore, gets the device type names from the Discovery module. After a device type is added to the list, WM never removes it from the list, even in the unlikely event that you are no longer managing any devices of a given type in WM. 6.1 Inventory View Edit Menu Options The Inventory view supports options for the Edit menu on the dynamic menu bar. 6.1.1 Delete Object and Traces This selection, also available via Ctrl+D, removes the selected (highlighted) device from the database as well as from all views in the client. important ........... This command is not undoable and can have unwanted consequences. See Deleting an Object and Traces on Page 261. 6.1.2 Clear Alarms Some of the alarms that are generated in the network are automatically cleared during runtime. You can also clear an alarm manually when it has been resolved or if it is inconsequential. Depending on the alarm settings, the agent sends an alarm notification only when there is a crisis and does not send notifications when that crisis is resolved. In such a scenario, you can manually clear the alarm. 6.1.3 Delete Alarms Use this option to manually delete an alarm when you feel the alarm is not significant or the alarm has been cleared. By default, cleared alarms are automatically deleted after 24 hours. 6.1.4 Search Use the Search dialog box to look for alarms associated with the search criteria you define. 123
- 124. Issue 3 WM Release 4.0 User Guide May 2012 Figure 75: Alarms Search dialog, sort options You can also access this utility by pressing Ctrl+F. Figure 76: Alarms Search dialog, input options The More button allows you to search by two criteria, both of which must be met or either of which must be met in the alarms that the search returns. 124
- 125. WM Release 4.0 User Guide Issue 3 May 2012 Figure 77: Alarms Search dialog, More options Figure 78: Alarms Search operation, alarms returned, example To include the children of matching elements in the Inventory, check the Include Child Agents check box. To add criteria that may narrow the list of matches, click the More button and in the next set of fields, define the additional criteria. Repeat this until all of your criteria are established. Then click the Search button. 125
- 126. Issue 3 WM Release 4.0 User Guide May 2012 6.2 Inventory Custom Views You can configure an unlimited number of inventory custom views. These views are filters. As with the base view that was open when the Add Custom View operation was launched, these are not static, but rather are updated as new information becomes available, even while you are examining the view. For example, when the status of a device changes, the new status is shown in the Status column for that device. Whenever the front view in the frame is an inventory view, WM opens a Show Objects with these Properties dialog in response to selection of ViewCustom ViewsAdd Custom View from the main menu. The properties are initially populated with the values of the base view. In the case of an inventory custom view, the Properties tab consists of two forms, connected by Next and Previous buttons. 126
- 127. WM Release 4.0 User Guide Issue 3 May 2012 Figure 79: Properties tab for an inventory custom view, first form Since this form is a filter, if you do not supply or select a value for a field, the system does not narrow the list of devices that it shows when you open the custom view. Click the Next button to advance to the second form of the Properties tab. 127
- 128. Issue 3 WM Release 4.0 User Guide May 2012 Figure 80: Properties tab for an inventory custom view, second form Click the Next button to advance to the third form of the Properties tab. 128
- 129. WM Release 4.0 User Guide Issue 3 May 2012 Figure 81: Properties tab for an inventory custom view, third form Click the Next button to advance to the fourth form of the Properties tab. 129
- 130. Issue 3 WM Release 4.0 User Guide May 2012 Figure 82: Properties tab for an inventory custom view, fourth form Click the Next button to advance to the fifth form of the Properties tab. 130
- 131. WM Release 4.0 User Guide Issue 3 May 2012 Figure 83: Properties tab for an inventory custom view, fifth form The final form includes an Additional Criteria button. 131
- 132. Issue 3 WM Release 4.0 User Guide May 2012 If you click this button, WM opens an additional criteria dialog. Figure 84: Additional custom view criteria dialog, Properties tab The More button in this window adds a single Property Name/Match Criteria correlated pair of fields each time you click it. To add three pairs, for example, click the More button three times. 132
- 133. WM Release 4.0 User Guide Issue 3 May 2012 Figure 85: Criteria dialog with three properties The Fewer button removes a pair. To specify what columns your new custom view should include, click the Select Props To View button. tip ................ To add vertical scrolling that you can view and check any available property that is not in the view when this dialog opens, resize the dialog window. 133
- 134. Issue 3 WM Release 4.0 User Guide May 2012 Figure 86: Select Table Columns dialog for inventory custom view note ............. These fields are read-write as well as selectable. However, you cannot reorder the columns by overwriting the default contents of their text boxes. Moreover, the system will determine the initial column arrangement regardless of the order that you see here. In the actual view, you will be able to rearrange columns for only the current view session. To specify more columns, click the Additional table columns button. Figure 87: User defined table columns window for inventory custom view 134
- 135. WM Release 4.0 User Guide Issue 3 May 2012 The More, Fewer, and Remove buttons in this window work the same as in the Criteria Dialog window above. The Display Name and Property Name entries add the property to the list of selectable columns in the previous dialog. A check in the associated check box adds the property as a column to the custom Inventory view. When you are satisfied with the construction of your table, click OK in these table columns windows. Back in the Show object with these Properties window, click the Tree Node Properties tab. Figure 88: Tree Node Properties tab for inventory custom view The meanings of these fields are as follows. Table 7: Tree node properties for event filter view Field Description Frame Title Specify the name to be displayed on the title bar of the custom view. Menu File Specify the panel‐specific menu file name. If this field is left blank, the default menu is Name displayed. Specify the icon name (in the WM_ Home/images directory) to use for the custom view. Icon File This icon is visible in the tree as well as in the title bar of the custom view. 135
- 136. Issue 3 WM Release 4.0 User Guide May 2012 Field Description Tree Popup Specify the file name of the menu used to display a contextual menu for the new custom Menu view node in the Navigation tree. Specify the position of the custom view in relation to previously added views. If this field is Node Index left blank, the view will be appended to the end of the current list of custom views. When you are satisfied with the view filter that you have constructed, click the Apply Filter button. See also the following other sections of this guide: Modifying a Custom View on Page 91 Renaming a Custom View on Page 91 Resizing Columns in a Custom View on Page 91 Removing a Custom View on Page 92 6.3 Topology Data Exports WM allows you to export either all of the data from the Inventory only the data of the current scrollable Inventory page. Procedure 8: To export topology data 1. Have the desired Inventory view on top in the view panel. 2. Either ◦ from the main menu, select ActionsExport Topology Data. ◦ press Ctrl+Shift+E. The Export Data dialog box is displayed. Figure 89: Export Data dialog 3. Select the desired option from the radio buttons: Export Entire Custom View Data or Export Displayed Data (only the data that the current Page Length setting of the view frame is allowing into the current display). 4. Enter the file name in File name field. 5. Click Export. A status message is displayed. The exported custom view data file is saved in the WM_ Home/images directory. 136
- 137. WM Release 4.0 User Guide Issue 3 May 2012 6.4 Operations on a Device The Inventory view panel supports right‐click menu options. Right click on an entry in the table to display the drop‐down list of options that are available at that time or for the currently selected (highlighted) network elements. The top‐level selections in these right‐click menus are an identical list of options for all of the various devices. Beneath the top level, some braches are device specific as follows: For only PMP AP and SM devices (including OFDM but not PMP 320), the Launch branch includes a link that opens a client session in BAM, the server that processes authentication attempts from SMs and manages their bandwidth service plans and VLAN profiles. For only high‐speed PTP backhaul master and slave devices that support it, the Launch branch includes a link that launches the PTP LinkPlanner tool. For only child WMs, the Launch branch includes − a link to Client, which opens a WM client session into the child WM. − no link to [the device] WebPage like every other element has. For generic elements (see Generic Elements (Non‐Cambium Devices) on Page 51 for the definition of this device type), the Launch branch is absent. The options that are available for all elements through their right‐click menu are as shown in Figure 90. Figure 90: Right-click options common for all elements 137
- 138. Issue 3 WM Release 4.0 User Guide May 2012 Table 8: References for common command options Command Option See Section Titled Page Add Relationship Adding Relationships Among Devices 234 Add to Device Group Creating a Static Device Group or 309 Adding Devices to a Static Device Group 314 Alarms Viewing Alarms for a Device 202 Apply Template Applying a Configuration Template 626 Children Adding Relationships Among Devices 234 Clone Device Cloning a Device Configuration 635 Components Viewing Component Properties 200 Configure Device Using the Configure Device Command 611 Credential Manager Setting WM Credentials for a Group of Selected Devices 248 Create Report Creating a Configuration Report 326 Create Template Creating a Configuration Template 621 Customer Contact Detail Finding the Customer Assigned to the Device 227 Dashboard Viewing the Dashboard for a Device 204 Delete Object and Traces Deleting an Object and Traces 261 Delete Report Deleting a Configuration Report 337 Delete Template Deleting a Configuration Template 634 Device Group Membership Creating and Using Device Groups 299 Device Summary Report Viewing a Device Summary Report 223 Edit Report Editing a Configuration Report Template 335 Edit Template Editing a Configuration Template 629 Element Properties Viewing Basic Properties 198 Events Viewing Events for a Device 201 Extended Family Adding Relationships Among Devices 234 Install Software Upgrades, For PMP, PTP, or CMM devices: Upgrading Devices On Demand, 287 PMP, PTP, CMM Scheduling a One‐Time or Periodic Task 647 Manage Device Managing or Unmanaging a Device 229 Physical Map Using the Physical Map 145 Ping Device Pinging a Device 230 138
- 139. WM Release 4.0 User Guide Issue 3 May 2012 Command Option See Section Titled Page Reboot Device Using the Configure Device Command 611 Refresh Stored Data Refreshing Device Data 248 Run Report Running a Configuration Report 331 Set Location in Physical Map Changing the Geolocation for a Device 182 Statistics Viewing Performance Data for a Device 203 Unmanage Device Managing or Unmanaging a Device 229 Update Status Updating the Status of a Device or a Network 195 WebPage Accessing the Web Interface of a Device 257 Table 9: References for special command options Command Option See Page BAM Launching BAM 640 Configuration Control PMP 320 device documentation set and Figure 91 140 Configure Mode PMP 320 device documentation set and Figure 92 140 PTP LinkPlanner High‐speed PTP backhaul device documentation set 139
- 140. Issue 3 WM Release 4.0 User Guide May 2012 When the right‐clicked element is a PMP 320 AP, the drop‐down menu includes the following additional options: ToolsSpectrum Analyzer. This option is described under Using the Spectrum Analyzer Utility on Page 254. ToolsConfiguration Control. This option launches the following dialog. Figure 91: Configuration Control dialog for PMP 320 AP ToolsConfigure Mode. This option launches the Configure Mode dialog, with the following mode options. Figure 92: Configure Mode dialog for PMP 320 AP, default values 140
- 141. WM Release 4.0 User Guide Issue 3 May 2012 Figure 93: Configure Mode dialog for PMP 320 AP, Mode BW selections Figure 94: Configure Mode dialog for PMP 320 AP, Mode Ratio selections Figure 95: Configure Mode dialog for PMP 320 AP, Mode Map selections When the right‐clicked element is a PMP 320 CPE, the drop‐down menu includes the option ToolsUpload AAA Certificate to CPE. This option is described under Uploading RADIUS AAA Certificates on Page 284. When the right‐clicked element is a PMP AP, the drop‐down menu includes the following additional options: ToolsDrop Subscriber Session. This option is described under Dropping a Subscriber Session on Page 232. ToolsSpectrum Analyzer. This option, although available in the drop‐down list of commands, is not supported for the PMP AP. Selection of this option spawns the error This operation is not supported for the selected device. ToolsUpload AAA Certificate to SM. This option is described under Uploading RADIUS AAA Certificates on Page 284. When the right‐clicked element is a PMP SM, the drop‐down menu includes the following additional options: ToolsDrop Subscriber Session. This option is described under Dropping a Subscriber Session on Page 232. ToolsLink Capacity Test. This option is described under Using the Link Capacity Test Utility on Page 250. ToolsSpectrum Analyzer. This option is described under Using the Spectrum Analyzer Utility on Page 254. ToolsUpload AAA Certificate to SM. This option is described under Uploading RADIUS AAA Certificates on Page 284. 141
- 142. Issue 3 WM Release 4.0 User Guide May 2012 6.5 Operations on a Network To see a list of all currently managed networks, click on Networks beneath Inventory in the Applications tree. Figure 96: Networks panel view When you right‐click on a network in the list, WM opens a drop‐down list of command options that you can execute upon the selected network. These options are as follows: 6.5.1 Start/Stop Discovery In the Networks panel of the Inventory view, the right‐click menu provides options to Start Discovery and Stop Discovery. When you select Stop Discovery, the discovery process will be halted, but some time may be required for all discovery‐related activities on the selected network to end. This is because WM will continue to try to discover elements that responded to previous messages, even though it ceases sending new discovery‐related messages. For example, preventing discovery of elements that already responded to a broadcast discovery message is not possible. 142
- 143. WM Release 4.0 User Guide Issue 3 May 2012 Stop Discovery also prevents future rediscovery for the selected network, even though rediscovery may be scheduled via the Discovery Configurator (as it is by default every 48 hours). If Stop Discovery is selected, rediscovery is also prevented when WM is stopped and then started, though by default a rediscovery cycle is initiated on WM startup. Select Start Discovery to initiate discovery for the selected network, according to the parameters that are currently set for it in the Discovery Configurator. The results will be displayed in Status column of the Inventory view table. When you select Start Discovery, the chosen network is also eligible for any scheduled rediscovery cycles in the future. A common method for provoking WM into executing a discovery cycle for a network that is not undergoing discovery is to stop and then start discovery for that network. 6.5.2 Status Update for the Network If you select the right‐click Update Status option over a network name, WM performs a status poll on the devices and, if the status poll fails, throws a Major severity alarm indicating that the device is unreachable. 6.5.3 Delete Object and Traces of the Network This selection removes the selected (highlighted) network from the client as well as from the database. important ........... This command is not undoable and can have unwanted consequences. See Deleting an Object and Traces on Page 261. 6.5.4 Credential Manager for the Network If you select the right‐click Update Status option over a network name, WM opens the Credential Manager interface, which allows you to set SNMP and/or Telnet/FTP authentication credentials for the WM to use for its access to each element in that network. See Setting WM Credentials for a Group of Selected Devices on Page 248. 143
- 145. WM Release 4.0 User Guide Issue 3 May 2012 7 Using the Physical Map WM automatically discovers devices and their logical relations in the network and graphically represents them in the physical map, which is a representation of their physical setting. A click on an element in the physical map opens a small summary window of details such as device status, radio information, and link performance. By design, the physical map represents devices whose device type template files were distributed by the installation tool. Additionally, you can represent any other device with a single user‐configurable icon. In this case, the pop‐up window described under Viewing Details on Page 174 contains only device name, its IP address, basic ManagedObject or SnmpNode data, and links to the Inventory view and Fault Management views. It contains no transmitted power level value, operating channel, or other device‐specific information. The map includes parent‐child relationship pointers for these devices based on what type of link they are capable of supporting, but does not include their coverage contours. device type template is stored on the WM server. In the unlikely case that your server administrator deleted a device type template file after installation because your network did not contain any elements of that device type, and you later add them to your network, your server administrator can replace the missing template, and then the physical map will display those new devices. whose location coordinates are known to WM. See the following section, Importing the Geo‐ locations on Page 145. To view the physical map, you can right‐click on a device in the Inventory view and select Physical Map from the drop‐down list. right‐click in a number of contexts to select Physical Map from the drop‐down list. See Displaying the Physical Map on Page 150. 7.1 Importing the Geo-locations The geo‐location import feature allows for the import of a comma‐separated‐value (.csv) geo‐location file. This feature is always available, regardless of the client user interface context, and always has the same effect. It does not depend on or apply to currently displayed view. The most common use of the CSV location import is to initialize network element geo‐locations after full discovery of the network. The location import does not create network element entries in Wireless Manager; it only updates the geo‐location of already‐discovered network elements. Often the location import is the only practical way to update the network element geo‐locations, since most devices do not have GPS data and there are usually too many elements to manually update the geo‐ location of each element. Once each device has a geo‐location, WM will plot it in the physical map. 145
- 146. Issue 3 WM Release 4.0 User Guide May 2012 To access the location import feature, from the main menu, select ToolsPhysical MapGeo‐location Import (CSV). This opens a file selection dialog for browsing to select a comma‐separated‐value plain text file. The file must be in the format specified below, including a header and one line per node, where each device line specifies in four columns 1. the Device Name exactly as displayed in the left column of the Inventory view 2. its latitude in decimal degrees, where negative numbers indicate west latitude 3. its longitude in decimal degrees, where negative numbers indicate west south longitude 4. its height in meters with respect to the ground, as opposed to altitude with respect to sea level The format of the file is as follows: Version: <version> Create Date: <MM/DD/YYYY HH:MM TimeZone> name, Latitude, Longitude, Height_Above_Ground name, Latitude, Longitude, Height_Above_Ground Blank spaces in the CSV file are ignored, except in the name field. The name must be in the exact format and syntax that WM uses. No conversion or normalization is performed, except that a colon‐ segmented MAC address is converted, if necessary, to match a MAC address syntax that is known to WM. For example, where WM uses the MAC address as the name, if the MAC address in the WM name field appears as 00 05 12 0C 09 1B, but the MAC address in the CSV file appears as 00:05:12:0C:09:1B (with colons), then the location import feature converts the imported MAC address to match the known MAC address. CSV files can be saved to CSV directly from Microsoft Excel™ and other spreadsheet programs by selecting Save As and choosing the CSV format, accepting any resulting warnings about loss of full spreadsheet functionality. The following is a typical file for a system that uses the MAC address as the network element name: Version: 1 Create Date: 1/24/2008 04 05 13 0C 09 1B, 25.743199, -84.365451, 20 04 05 13 0F 00 ED, 25.745674, -84.36471, 20 04 05 13 0F 01 3E, 25.748955, -84.363566, 20 04 19 59 B4 94 24, 25.750265, -84.360474, 20 04 00 9E 03 7B 50, 25.746677, -84.35942, 20 04 00 9E 03 7B B5, 25.749446, -84.366381, 20 important ........... The import operation discards the top two lines of the file, even if they contain geo- location record formats. Ensure that your geo-location records begin in the third row of data. When you select ToolsPhysical MapGeo‐location Import (CSV), WM opens the Geo‐location Import window. note ............. The file for import must be accessible to the file system of the client device. 146
- 147. WM Release 4.0 User Guide Issue 3 May 2012 Figure 97: Geo-location Import window Click the ellipsis button and browse to the proper path. Select the file and click the Open button. Then, back in the Geo‐location import window if you want the import operation to occur once and now, click the Run Now button. The GUI includes a progress indicator and buttons that allow you to start, stop, and pause the import operation. Figure 98: Import CSV File of Geo-Locations window ◦ if you prefer instead to delay the import operation or set it up to repeat, click the Run Later button. The Create Schedule Task dialog opens to its Schedule tab. 147
- 148. Issue 3 WM Release 4.0 User Guide May 2012 For information on how to set the fields of the Schedule tab, see Table 87: Options for scheduling of tasks on Page 667. After setting the schedule for the import task, click the Details tab only if you want to browse to change the file to be imported. If you want the task to import the file that you selected from the Geo‐location Import window, click Save in the Create Schedule Task window. If parsing errors are found (for example, a field with improper characters), a note is placed at the top of the Results section. Invalid values or rows with missing fields are noted on a per‐row basis. If a name does not match that of any discovered node in WM, then the geo‐location information is ignored, and a notice for that node appears in the Results report. 7.2 Importing Addresses You can import a properly formatted file that correlates devices to their height values and street addresses. To access the location import feature, from the main menu, select ToolsPhysical MapAddress Import (CSV). This opens a file selection dialog for browsing to select a comma‐separated‐value plain text file. The file must be in the format specified below, including a header and one line per node, where each device line specifies in three columns: 1. the Device Name exactly as displayed in the left column of the Inventory view 2. its height in meters with respect to the ground, as opposed to altitude with respect to sea level 3. its address 148
- 149. WM Release 4.0 User Guide Issue 3 May 2012 The format of the file is as follows: Version:version Create Date: date Device Name, Height, Address Device Name, Height, Address Device Name, Height, Address Blank spaces in the CSV file are ignored, except in the name field. The Device Name must be in the exact format and syntax that WM uses. No conversion or normalization is performed, except that a colon‐segmented MAC address is converted, if necessary, to match a MAC address syntax that is known to WM. For example, where WM uses the MAC address as the Device Name, if the MAC address in the WM name field appears as 00 05 12 0C 09 1B, but the MAC address in the CSV file appears as 00:05:12:0C:09:1B (with colons), then the address import feature converts the imported MAC address to match the known MAC address. To the right of the comma that separates the Height column from the Address column, additional commas (which are typical in addresses) are ignored. Any address format that Google supports is also supported by the address import tool and the physical map. CSV files can be saved to CSV directly from Microsoft Excel™ and other spreadsheet programs by selecting Save As and choosing the CSV format, accepting any resulting warnings about loss of full spreadsheet functionality. The following is a typical file for a system that uses the MAC address as the network element name: Version:1 Create Date: 2/4/2008 0A 0A 0A 0A 0A 0F, 6.0961913,Marysol Trail, Cedar Park, TX 0A 0A 0A 0A 0A 0E,6.1564272,123 Main Street, Linden, TX 0A 0A 0A 0A 0A 0B,6.0859231,46 W. Hwy US 183, Tanner, TX important ........... The import operation discards the top two lines of the file, even if they contain address record formats. Ensure that your address records begin in the third row of data. When you select ToolsPhysical MapAddress Import (CSV), WM opens the Location Import from Address CSV window. note ............. The file for import must be accessible to the file system of the client device. Figure 99: Location Import from Address CSV Click the ellipsis button and browse to the proper path. Select the file and click the Import button. 149
- 150. Issue 3 WM Release 4.0 User Guide May 2012 7.3 Displaying the Physical Map Command options to bring the physical map to the front of the view frame are available throughout the WM user interface: In the following areas, if you right‐click on an element, Go ToPhysical Map is an option in the resulting drop‐down list of options and opens with the target element in its center: − a Network Events view, where the element is identified by the Source by default − an Alarms view, where the element is identified by the Failure Object by default − an Inventory view, where the element is identified by both its MAC Address, Device Name, and IP Address by default, except the Networks view and Reports views In the Applications tree, if you right‐click on the Physical Map branch and select ActionsLoad Online/Offline Map, then the selected map type opens. In the main menu, if you select ToolsPhysical MapLoad Online/Offline Map, then the selected map type opens. note ............. If you ever encounter an AJAX request timed out error displayed on the physical map, this could be the result of network traffic too high, WM server too busy, or inability of the physical map to respond quickly enough to update requests from your client. The physical map displays information that it harvests from core management systems within WM, such as performance data or configuration properties. As a result, the physical map may sometimes noticeably lag behind these core systems. For example, you may view a performance data statistic in the performance data Configured Collection view (an example is shown in Figure 269 on Page 382), and then observe that the value in the physical map is sometime later updated to match what you saw in the Configured Collection. This behavior is designed, so that updates in the physical map do not interfere with WM core data gathering and processing. In typical networks, the delay may be imperceptible but, especially while WM is initially discovering thousands of devices in a very large network, the physical map may display the updated information only after minutes or even hours have elapsed. The physical map can be only online: a Google map, licensed and downloaded upon client demand only offline: tiles loaded into a GeoServer Map Tile Server that is either local or remote to the WM server either online or offline, where both are available. 150
- 151. WM Release 4.0 User Guide Issue 3 May 2012 7.3.1 Available Formats for Online Maps A Google physical map is a representation of physical setting expressed as a satellite view, a geographic map with roadways and other prominent features, or a hybrid of both, or a topographic map of the terrain. In any Google map, a menu of map types is either present or available for display, depending on the setting of the WindowMap Type Control option in the main menu of the physical map. See Map Type Control on Page 172. For differentiation between the Google map and the GeoServer map, this guide and the WM client refer to the Google map as the online map. The online map is launched in any of the ways listed in Displaying the Physical Map on Page 150. However, in the cases where the command option is generic (Physical Map), WM opens the offline map instead, if that was the last map that was previously open. Certain features are unique to the online map. These are listed as unavailable in the next section, Format of Offline Maps. 7.3.2 Format of Offline Maps A GeoServer physical map is a static set of tiles downloaded to and available from the Geoserver, whose access from the client is configured in the administration tool. (See Using the Offline Physical Map Panel on Page 691.) For differentiation between the Google map and the GeoServer map, this guide and the WM client refer to the Geoserver map as the offline map. The user experience in this map is identical to that in the online map, except that the following features are never available in the offline map: Link profile. See Figure 117: Path Profile on Page 177. Google search. See Google Search Bar on Page 171. Show address. See Current Location on Page 173. Street view. See Accessing the Street View of a Selected Point or Device in the Physical Map on Page 180. Device repositioning through drag/drop. See Changing the Geolocation for a Device on Page 182. The predominance of figures in this section that show examples of the physical map are taken from the online map. The following are examples of the offline map, whose features include graphical representations of prominent waterways and densely populated areas. Be aware that your offline maps may vary in appearance from these examples, since your WM server administrator has the flexibility to collect and load into the Geoserver the offline image layers from any of ten different data source types. 151
- 152. Issue 3 WM Release 4.0 User Guide May 2012 Figure 100: Offline map, midwestern USA Figure 101: Offline map, northeastern Illinois 152
- 153. WM Release 4.0 User Guide Issue 3 May 2012 Figure 102: Offline map, network at a plus zoom factor Figure 103: Offline map, network at a minus zoom factor 153
- 154. Issue 3 WM Release 4.0 User Guide May 2012 The offline map is launched in any of the ways listed in Displaying the Physical Map on Page 150. However, in the cases where the command option is generic (Physical Map), WM opens the online map instead, if that was the last map that was previously open. 7.4 Generating a Physical Map View of an Element Selected in the Inventory View This section describes how to proceed from viewing an element in the Inventory view to viewing in the physical map in the context of a cluster of elements (where the zoom level causes proximal elements to be obscured by an element icon) or in the context of links in which the element is involved. Procedure 9: To view an Inventory element in the context of a physical map 1. In the Inventory view, right‐click the element that you want to view in a physical map. 2. From the drop‐down list of options, select Go ToPhysical Map. 154
- 155. WM Release 4.0 User Guide Issue 3 May 2012 note ............. The MapCenter selection from the main physical map menu may zoom out to the most negative level of zoom. 7.5 Viewing Collocated and Proximal Elements In some cases, either the level of zoom hides elements beneath other elements in the downloaded physical map or element representations are partially overlaid by the representations of others. This can particularly occur in the following situations: where a cluster of PMP APs are collocated with a CMM and a PTP slave device where only one tower or otherwise high‐elevation venue is available in the area for effective RF communications Figure 104: Physical map: collapsed instance of device collocation 155
- 156. Issue 3 WM Release 4.0 User Guide May 2012 In the example case above, the PTP master is collocated with a PMP AP that has good links to three PMP SMs. Since the AP is not viewable at any zoom level, the icon pile is represented by a plus sign (). A click on the top icon in the icon pile expands the view to include the cluster that had been represented by the icon with the plus sign. Figure 105: Physical map: expanded instance of device collocation Procedure 10: To view an element in a cluster 1. If the element is part of cluster that cannot be displayed (non‐displayed members of the cluster are represented by +) because of the immediate zoom level, then ◦ to briefly see all other members, either − click on the + − right‐click on the element and select Expand Cluster from the drop‐down list of options. All members of the cluster, but not necessarily all of the elements to which they currently link, are briefly displayed at the current zoom level. The expansion of the cluster is fleeting. For example, the cluster is collapsed upon the next mouse movement. 156
- 157. WM Release 4.0 User Guide Issue 3 May 2012 ◦ to continuously view the other members, from the main Physical Maps menu, select OptionsDisable auto close on clustered elements and then repeat the steps from the first bullet. If this is checked, the user must click in an unused portion of the map to close expanded clusters. If this is unchecked, expanded clusters close when the mouse cursor moves outside the bounds of the cluster. To view all of the elements that are in link with the selected element, perform the following steps. Procedure 11: To view linked elements within the same physical map 1. Use the vertical + / ̶ bar to zoom out. 2. If all linked elements are not displayed yet, zoom out again as many times as necessary to get them into the map. 157
- 158. Issue 3 WM Release 4.0 User Guide May 2012 note ............. The MapCenter selection from the main physical map menu may zoom out to the most negative level of zoom. 158
- 159. WM Release 4.0 User Guide Issue 3 May 2012 note ............. It may be helpful to detach and enlarge the Physical Map, re-center the map, and/or collapse the selections panel to the right of the map. Also, enlarge the confines of the physical map to the extent possible. 7.6 Panning The client keeps data ready for an additional area that surrounds the devices that are currently visible in the physical map. This additional area makes other currently non‐visible elements available to the map as you pan (click and drag to move the focal point). The physical map then displays link lines and coverage contours that are associated with the original devices, even when they link to devices that may be not currently visible in the map. If you pan beyond the edge of the original physical map, then the devices that link to them may become visible, even when the original devices are no longer visible. If a network element is far enough way from the bounds of the original physical map, then its coverage contours are not visible, even if they would actually extend in to the currently visible area. It is also possible that the physical map loses sight of, or is unable to pan widely enough to find, some of the elements that are involved in links with visible elements. This is a limitation of map panning, not of the WM physical map. 159
- 160. Issue 3 WM Release 4.0 User Guide May 2012 7.7 Jumping to a Different Position in a Physical Map From any display of the physical map, you can jump to coordinates that you specify. To do so, right‐ click in the map and select MapShow Address from the drop‐down list of options. When the map repaints, click on the Enter a new lat/long link and modify the coordinates in the resulting Input dialog. Click OK. The map jumps to and renders the address of the coordinates that you specified. 7.8 Refreshing a Physical Map The physical map includes the MapRefresh option from the main menu of the map. If the quality of a link changed since the map was last launched, then the color of the line that represents the link will change when you select this option. Following an idle period that is set in the configuration file, the map will automatically be refreshed. The Map menu also includes the Center option, which both zooms out and positions the center of the map at the geographic center of the network that is being viewed. 160
- 161. WM Release 4.0 User Guide Issue 3 May 2012 Figure 106: Refresh and centering options for a physical map 7.9 Setting Physical Map Options 7.9.1 Selecting Links, Coverage, and Standards Types to Display on a Map Type As a user, you may select one of the following from the link drop‐down list as a type for Link Metric: For Custom Selection, an Edit Custom link appears: If you click on this link, the custom set of options open as a list that overlays the map: 161
- 162. Issue 3 WM Release 4.0 User Guide May 2012 one of the following from the Air Standard drop‐down list as a type of air interface representation: − one of the combined types: − any from a list that WM bases upon the currently managed elements; for example: or 162
- 163. WM Release 4.0 User Guide Issue 3 May 2012 one of the following options for Coverage representation: The RSSI Contours option for Coverage displays the contours according to the following color scheme, which is present for reference in the Legend panel at the bottom of the selection frame to the right of the physical map: one of the following Map options as a type for map background If you choose no filtering (All Links, No Coverage, All Air Standards), then the physical map uses its own generic color scheme and its own generic legend. Otherwise, the physical map may use other colors and the legend is specific to your selections. Links are represented as lines with a white arrow (chevron) pointing away from the parent element and toward the child. The Legend Filter feature allows you to select the desired quality levels (——— for Poor, ——— for Okay, ——— for Good) of links to display—all, some, or none. You can set your map to display only a single type of link representation at a time, if you wish: RSSI, Data Rate, Path Metric, RSSI Auto‐Threshold, Jitter, or Logical Links. For each except Logical Links, the quality assessment that the display represents is a relative statement about the particular measure of link quality. For example, if you select Link Data Rate, then the line color summarizes the effectiveness of the link with respect to only the rate at which data travels in the link. If you select RSSI Auto‐Threshold, then the line color indicates received signal expectations derived from a standard error algorithm, as described under Using the RSSI Auto‐Threshold Feature on Page 169. 163
- 164. Issue 3 WM Release 4.0 User Guide May 2012 If the last poll of either of the devices in a link was unsuccessful, then the color of the link between them is red (until the alert for that poll has been cleared). Otherwise, these link colors are based on performance data that is currently in the database and are not intended to reflect the status of either or both devices. (The icon associated with a device in the Inventory view reflects its status.) If logical links are the only known link data for a pair of nodes, or if only logical links are being displayed, they are by default black, and their colors, like that of any other map element, are user‐configurable. Figure 107: All reliability links selected for physical map 164
- 165. WM Release 4.0 User Guide Issue 3 May 2012 Figure 108: Good reliability links filtered out If a color is filtered out of the view, a link may disappear and reappear as it experiences better or worse link quality. There is no provision to apply this feature to some links and not apply it to others. If you disable the display for one or more link quality level(s) in a physical map, then you must remember to reintroduce the level(s)—check its link type check box—in any subsequent map where you want lines for links of those quality levels to be painted. The persistence of the filter is shown in the following capture, which was taken of a new map launched before any new change was made in the legend filter. 165
- 166. Issue 3 WM Release 4.0 User Guide May 2012 Figure 109: Good reliability links persistently filtered out from previous physical map setting When additional elements that exist within the currently mapped area can be seen only by zooming in, the map includes a magnifying glass symbol: Figure 110: Physical map: further zooming required for viewing more devices 166
- 167. WM Release 4.0 User Guide Issue 3 May 2012 Figure 111: Physical map: All Links, No Coverage, All Air Standards, Map Figure 112: Physical map: All Links, No Coverage, All Air Standards, Hybrid 167
- 168. Issue 3 WM Release 4.0 User Guide May 2012 Figure 113: Physical map: Logical Links, No Coverage, All Air Standards, Terrain The main menu of the physical map frame includes the OptionsAdjust contour transparency selection. When you select this option, WM opens an Input window for configuring a percentage. A higher percentage makes features underneath the contours more visible or legible. 168
- 169. WM Release 4.0 User Guide Issue 3 May 2012 7.9.2 Using the RSSI Auto-Threshold Feature As the first dash list on Page 161 implies, you can set your map to display only a single type of link representation at a time, if you wish: RSSI, Data Rate, Path Metric, RSSI Auto‐Threshold, Jitter, Status Poll State, or Logical Links. RSSI (Radio Signal Strength Indicator) is a relative measure of the strength of a received signal. If you select RSSI Auto‐Threshold from among the specific link type representations, then WM applies a standard error algorithm with current and historical RSSI data (derives recurrence relations) to characterize link reliability into color coding as follows: Poor (———) represents greater than 95% likelihood that the current RSSI of the link significantly differs from historical RSSI values. Okay (———) represents 90 to 95% likelihood that the current RSSI of the link significantly differs from historical RSSI values. Good (———) represents less than 90% likelihood that the current RSSI of the link significantly differs from historical RSSI values. Depending on how long the physical map has been displayed, it may be advisable to refresh the RSSI data that the map uses. Select the option ToolsPhysical MapReset Historical RSSI Data from the main WM menu. 7.9.3 Filtering the Icons to Display by Current Alarm Level Both the physical map menu and the element status bar overlay allow you to exclude from display the icons of elements whose current alarm level(s) you deselect. You can exclude or reintroduce them as follows: To hide all element icons, in the main menu of the physical map frame, select (check) Status FilterHide All Status Levels. To selectively exclude elements of one or more status levels, either − click to uncheck the status level from the Status Filter menu (shown above). For example, to hide the icons of elements whose alarm status is Clear, uncheck Status FilterClear. − click Hide for the status level(s) in the Status menu of the Legend panel in the lower right corner of the map. 169
- 170. Issue 3 WM Release 4.0 User Guide May 2012 Both the Status Filter menu and the Status menu reflect changes made in the other. To reintroduce the icons of elements whose alarm status is currently deselected, use either menu. 7.9.4 Setting Whether Elements Appear Based on Zoom The main menu of the physical map includes the OptionsIcons always respect zoom level selection. If this is checked, equipment is filtered by the zoom level as defined in the configuration file. For example, zooming out to the furthest setting may result in only PTP elements showing. If this in unchecked, the map shows as much equipment as possible, except for equipment that would result in the configured limit being exceeded. For example, if the configured limit is 100, and 1 PTP, 99 PMP devices, and 2 CMM4 devices are present, then the CMM4 devices are not displayed unless the WM server administrator edits the OakleafConfig.xml file to include a zoom level of greater than 100 (in the maxNumDevices tag). 170
- 171. WM Release 4.0 User Guide Issue 3 May 2012 7.9.5 Using or Hiding Other Physical Map Overlays The Window submenu of the main physical map menu contains toggles that keep or hide several other overlays. note ............. Although no device search utility is present in the physical map, you can often use the Search feature in the client to get a physical map link to a particular device. See Using the Search Utility on Page 92. Google Search Bar The Google Search Bar allows you to enter a partial or entire string from an address, zip code, phone number, or comma‐space separated latitude/longitude known to Google Maps and click the associated Search button. The system prints the list of matches above the search box and the map re‐centers onto the location of the top match in the list. 171
- 172. Issue 3 WM Release 4.0 User Guide May 2012 You can then click on any other match to have the map re‐center once again, this time on the location of the target of your click. For any match, the system provides a cloud that contains the name, address, phone number, latitude, and longitude (to the extent that these are known) of matching entity. Map Type Control The WindowMap Type Control option allows you to hide or reinstate the Map drop‐down menu that overlays the physical map in the far upper right corner. This menu controls whether the physical map backdrop for the network portion being viewed is a Google map, a photo taken from a satellite, a topographic representation of altitude differences within the area of the map, or the topographic representation with streets and highways overlaying the area (Hybrid). To see examples of these backdrops, see the figures included in Selecting Links, Coverage, and Standards Types to Display on a Map Type on Page 161. 172
- 173. WM Release 4.0 User Guide Issue 3 May 2012 If you hide (uncheck) these filter menus from overlay in the physical map, you can reinstate them at any time by checking the WindowMap Type Control option. Zoom Control The WindowZoom Control option allows you to hide or reinstate both the zoom control (the vertical, incremented bar) and the re‐center control in the upper left corner of the physical map. These two controls are inseparable. Re‐center control. Clicking on the arrows, clockwise from top, re‐centers the map to the north, east, south or west. Clicking on the hand symbol re‐centers the map on its previous center. This scale zooms the map in (+) or out (‐) by a single increment when you click the plus or minus sign or by single or multiple increments when you click a hash in the scale. If you hide (uncheck) these controls from overlay in the physical map, you can reinstate them at any time by checking the WindowZoom Control option. Alternative means are also provided for re‐centering the map and for zooming: To re‐center the map at a point within the current physical map display, right click on that point and select Center from the resulting drop‐down list of options. To zoom in to the fullest extent on any point within the current physical map display, right click on that point and select Zoom from the resulting drop‐down list of options. This both re‐centers and zooms the map in a single repaint operation. Current Location The WindowCurrent Location option allows you to prevent (unchecked) the Current Location bar from popping up (for example, whenever you click in the physical map or when you right‐click on an element in the map and select MapShow Address) or permit it to pop up (checked). If you prevent it from popping up, you can reinstate it at any time by checking the WindowCurrent Location option. 173
- 174. Issue 3 WM Release 4.0 User Guide May 2012 Map Scale The WindowMap Scale option allows you to hide or reinstate the scale indicator in the far bottom right corner of the physical map. If you hide this indicator, you can reinstate it at any time by checking the WindowMap Scale option. Lat/Long Display If the WindowLat/Long Display option is checked, the map display includes an overlay with the running coordinates above which the mouse cursor travels and hovers. If this is unchecked, the coordinates are not shown. 7.10 Viewing Details in the Physical Map note ............. Many of the options described in this section provide performance statistics for an element. Depending on how long the physical map has been displayed, it may be advisable to refresh the data that the map uses. You can do so by selecting the option ToolsPhysical MapsRefresh Physical Map Data from the main WM menu. When you do, the system may require as much as five minutes to reflect the latest changes. During this wait, selecting MapRefresh from the menu bar of the physical map may shorten the time required to reflect them. 7.10.1 Accessing Data for a Device in the Physical Map In addition to representing a node by a symbol and graphically representing its links and contours, the physical map launches a pop‐up when you click on any node. This pop‐up provides basic information about the node and information about its radios and links. You can also launch this pop‐up through a right‐click on the device icon followed by selection of Open from the resulting drop‐down list of options. 174
- 175. WM Release 4.0 User Guide Issue 3 May 2012 Figure 114: Device data pop-up, Main tab Figure 115: Device data pop-up, Radios tab 175
- 176. Issue 3 WM Release 4.0 User Guide May 2012 Figure 116: Device data pop-up, Links tab, scrolling required 176
- 177. WM Release 4.0 User Guide Issue 3 May 2012 For some data, a Plot link is provided to open the Collected statistics window and graph the collected statistics. (See Viewing a Collected Performance Statistic on Page 386.) The statistics for which this convenience is provided depends on device type as follows: For an AP or SM, the Links tab provides links to plot dBm and Jitter. note ............. Color coding (for example, ) summarizes Jitter by the following arbitrary standards: ≤ 4 is Good (green), >4≤8 is Okay (yellow), >8 is Bad (red). For an SM, the Radios tab provides a link to plot Rx Power. For an AP, the Radios tab provides no link to plot Tx Power. For a PTP device − the Radios tab provides links for plotting Frequency Data Rate Tx Power Rx Power − the Links tab provides links for plotting Mbps dBm The Links tab includes Status Poll State, whose associated box color represents whether the last poll of the devices succeeded ( ) or failed ( ). This item includes an associated Show link, which when clicked opens the Alarms view of the device to display the time stamp of an unsuccessful poll among other events that generated alarms and that thus may suggest reasons why the poll did not succeed. Where topographic information from the United States Geological Survey (USGS) is available, the path Profile link opens a representation of the linear heights plot for the center of the RF beam against the varying heights of the terrain that lies between two linked devices. Figure 117: Path Profile 177
- 178. Issue 3 WM Release 4.0 User Guide May 2012 Where the topographic information is not available, an error indicates so. Where applicable, the tabbed pop‐up also provides click‐through links to launch the management web interface (device settings) of the device. See Figure 182 on Page 257. an Alarms view that lists the alarms, including those of Clear status, generated for only that device. See Figure 139 on Page 202. the network element dashboard for the device. See Viewing the Dashboard for a Device on Page 204. a Network Events view that lists the events generated for only that device. See Figure 138 on Page 202. an Inventory view that lists default Inventory information about that device. the Configured Collection of performance statistics for that device. See Figure 140 on Page 203. Figure 118: Device data pop-up, Manage tab, scrolling required 178
- 179. WM Release 4.0 User Guide Issue 3 May 2012 Figure 119: Device data pop-up, Manage tab for a PTP device The Manage tab for a PTP device includes a link (shown above) that launches the PTP LINKPlanner tool. For any device whose air interface standard is unknown to WM, the physical map represents the device with a question mark. Figure 120: Question mark representing device of unknown type 7.10.2 Accessing the Geolocation of a Selected Point or Device in the Physical Map To find the geolocation for any point in a physical map, right‐click on that point and then select Show Address from the drop‐down list of options. 179
- 180. Issue 3 WM Release 4.0 User Guide May 2012 To find the geolocation for any device in a physical map, right‐click on the device and then select MapShow Address from the drop‐down list of options. 7.10.3 Accessing the Street View of a Selected Point or Device in the Physical Map To open a street‐level view of any point in the physical map, right‐click on that point and then select Street View from the drop‐down list of options. Where a street view is available, Adobe Flash Player will launch the view. To open a street‐level view of any device in the physical map, right‐click on the device and then select MapStreet View from the drop‐down list of options. 180
- 181. WM Release 4.0 User Guide Issue 3 May 2012 Where a street view is available, Adobe Flash Player will launch the view. 7.10.4 Accessing a Physical Map Device in Other Management Views You can quickly jump from viewing a device in a physical map to viewing its records in any of the following other management views. Access is through a right‐click on the device and then selection of the intermediate menu item Manage in the resulting drop‐down list of options. Select Alarms to see all of its current alarms in the Alarms viewer. See Figure 139 on Page 202. Select Events to see all of its current events in the Network Events viewer. See Figure 138 on Page 202. Select Inventory to see the element isolated in a table of Inventory columns. 181
- 182. Issue 3 WM Release 4.0 User Guide May 2012 7.11 Importing a BroadbandPlanner Prediction The ToolsPhysical MapMap Import/ExportImport BroadbandPlanner Prediction option from the main menu allows you to bring into the physical map the CSV‐formatted output from the BroadbandPlanner tool. When you execute this option, WM opens a file browser window. Figure 121: Import BroadbandPlanner Prediction dialog Click the browse button. Browse to and select the CSV file from the tool's export, then click the Import button. 7.12 Changing the Geolocation for a Device To change the geolocation records in WM for any device in a physical map, either click, drag, and drop the device icon. right‐click on the device in the physical map and then select Change Location from the drop‐ down list of options. Select Change Location. A map tack centers on the original location and a pop‐up cloud describes options for changing the records. You can also raise the Change Location cloud options from the Inventory. Right‐click on the device. In the drop‐down list of command options, select Set Location in Physical Map. 182
- 183. WM Release 4.0 User Guide Issue 3 May 2012 Right‐click the element icon and select Set Location. Click at the new location to fix the map tack and then click the Save button. Wait for the records to be updated and Confirm that the map reflects the new location and note the icon to be moved. whether the location configured in the element is updated to match the new location configured in the WM database. 183
- 184. Issue 3 WM Release 4.0 User Guide May 2012 7.13 Checking the Log of a Physical Map The main menu of the physical log includes the OptionsToggle Log Window selection. This alternately opens and closes the Log Window, which contains messages about map activity that can be useful for troubleshooting. Figure 122: Physical map Log window, opened 7.14 Exporting a Map The tools menu allows you to export the physical map as a kml file. store it for viewing in Google Earth. export the devices from the map to the BroadbandPlanner tool. export the network from the map into the XML format. export a location file for use in a child WM. 184
- 185. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 12: To export a physical map 1. To optionally refresh the map before saving it, select MapRefresh from the physical map menu. 2. From the main WM menu, select ToolsPhysical MapMap Import/ExportGenerate KML Export. 3. Select the Save File radio button and click OK. 4. Modify the file name from its default (WM_export.kml). 5. Click the Save button. 6. To optionally view the exported file, select ToolsPhysical MapMap Import/ExportView KML Export. note ............. The response to this option is identical to the response to Generate KML Export. 7. Select the Open with radio button, and click OK. note ............. The web browser handles this request in the manner in which it is configured to handle kml files. It may prompt about whether to open or save the file, open a file browser that prompts for a destination path and file name, or open a view of the map in the Google Earth web site. 8. If necessary, specify Google Earth as the helper application. 185
- 186. Issue 3 WM Release 4.0 User Guide May 2012 Figure 123: Exported physical map in Google Earth application, zoomed in 186
- 187. WM Release 4.0 User Guide Issue 3 May 2012 Figure 124: Exported physical map in Google Earth application, zoomed out 9. In the Places box in the left panel of their site, scroll down to Temporary Places. 10. Under Temporary Places in the hierarchy, right‐click on the file WMS_export.kml that is associated with the latest date and time. 11. From the drop‐down list of options, select Save to My Places. 12. To rename the file a. right‐click the file name and select Rename from the drop‐down list. b. overwrite WMS_export with a unique name for the file. c. click in a blank area to save the new file name and exit the name editing text box. 13. To view information about the mapped elements a. expand the kml file node in the Places box and expand the Network Elements node beneath it. 187
- 188. Issue 3 WM Release 4.0 User Guide May 2012 Figure 125: Places box with Network Elements node expanded b. to see further information about a particular element, click the element node. Figure 126: Radio(s) link to information about the element 188
- 189. WM Release 4.0 User Guide Issue 3 May 2012 Figure 127: Information about the element in Google Earth c. scroll to view information about rest of the elements. 14. To view information about the links a. expand Latest Links and its child nodes. Figure 128: Places box with links node expanded b. click on the node associated with the OTA link. 189
- 190. Issue 3 WM Release 4.0 User Guide May 2012 Figure 129: Link information in Google Earth view 15. To save the map of network elements to a compressed (kmz) file a. right‐click the Network Elements node and select Save As from the drop‐down list. b. browse to and select the folder in which you want to save the map. c. back in the Save file window, click the Save button. 16. To attach a kmz file of the network elements map to new email, right‐click the Network Elements node and select Email from the drop‐down list. 17. To save the map of links a. right‐click the links node and select Save As from the drop‐down list. b. browse to and select the folder in which you want to save the map. c. back in the Save file window, click the Save button. 18. To attach a kmz file of the links to new email, right‐click the links node and select Email from the drop‐down list. 7.15 Exporting Devices to BroadbandPlanner To export devices from the physical map into a text file that Broadband Planner can import and use, select ToolsPhysical MapMap Import/ExportExport Equipment to BroadbandPlanner from the main menu of the WM client application. The Choose file name and location for export dialog opens. (Location in the context of this window title means file system path.) 190
- 191. WM Release 4.0 User Guide Issue 3 May 2012 Browse to and select the repository from which you will want to send/transfer the text file to the tool. 7.16 Exporting the Network into XML To export the network from the physical map into an XML file for use in another system such as a child WM, select ToolsPhysical MapMap Import/ExportExport Network to XML from the main menu of the WM client application. The Choose XML file name and location for export dialog opens. (Location in the context of this window title means file system path.) Browse to and select the repository from which you will want to send/transfer the XML file to the other system. 191
- 192. Issue 3 WM Release 4.0 User Guide May 2012 7.17 Exporting Locations for Use in a Child WM To export the device locations from the physical map into a CSV file for use in a child WM, select ToolsPhysical MapMap Import/ExportExport WM Location Import File from the main menu of the WM client application. The Choose CSV file name and location for export dialog opens. (Location in the context of this window title means file system path.) Browse to and select the repository from which you will want to send/transfer the CSV file to the other system. 7.18 Notices Regarding Physical Maps On rare occasions, WM will returns a warning to the top of the map, and the flag to the far right in the main physical map menu bar, when you try to display a representation that cannot be displayed in a physical map; for example The following are other examples: if WM has no configured location for the device that was selected when you launched the physical map if you select a set of devices that are so far apart that, at the required zoom level, the devices would be invisible 192
- 193. WM Release 4.0 User Guide Issue 3 May 2012 if the zoom level that would be required for the map to include all alarms (the normal approach for WM in ordering the tile from the map server for download) is not possible The physical map may occasionally display the error: AJAX requested time out... This indicates that either network traffic is high or the WM server is especially busy and not responding quickly enough to requests that the client is making for updates in the physical map. 193
- 195. WM Release 4.0 User Guide Issue 3 May 2012 8 Viewing Information About a Specific Device 8.1 Updating the Status of a Device or a Network The status of a device or the network itself is automatically updated on a regular interval via the process of status polling. By default, WM automatically checks and monitors the connection and network status for a device every 15 minutes and displays the current status in the client. The mechanism of status polling can be global or be set to specific for each device type but, in general, it is a request for the device to respond. If the device responds, it is considered reachable and its status is unchanged. If it does not respond, an unreachable alarm is thrown, and the status of the device becomes Major. You can work from default status polling information, force status polling (see Updating Status on Demand below), or reconfigure how WM performs status polling (see Adjusting the Status Polling Intervals on Page 195). 8.1.1 Updating Status on Demand By selecting the Update Status option from the device‐specific menu, you manually update the status. For example, if WM polls the status of a router every 900 seconds, and you want to know the latest status of that router without waiting until the next polling cycle occurs, use this option. This makes the latest status information for the device available to both the client and the database. 8.1.2 Adjusting the Status Polling Intervals Each statistic (for example, the number of bytes that have been received on a wireless interface) represents one characteristic or attribute of the device at a particular time. From the main menu, the ToolsPolling Configuration opens the Polling Configuration dialog to its Performance Polling tab. When this dialog opens, click the Status Polling tab. 195
- 196. Issue 3 WM Release 4.0 User Guide May 2012 Figure 130: Polling Configuration dialog, Status Polling tab WM inherits the single global performance polling configuration for every device type from the value of the GlobalStatusPollingInterval tag in the file .../wm/server/conf/WibbWMSConfiguration.xml in the WM server file system. The initial (installed) value of this tag is 15 minutes. If you wish, you can leave this configuration in force by not using this tab. This tab in the client interface allows you to override those configurations by setting the status polling via SNMP queries to occur (Enable Polling Status checked). not occur (Enable Polling Status unchecked). not occur for device types that you specify, and occur for all other device types. (See Procedure 13 below.) occur at the Global Polling Interval for all devices types. occur at intervals that you set (Polling Interval in Minutes) for each device type that you deliberately Add for status polling interval configuration, and occur at the Global Polling Interval for device types that you do not Add. (See Procedure 13 below.) To set some or all device types that you specify to be polled for status at a rate different from the Global Polling Interval, perform the following steps. Procedure 13: To set status polling for a specific device type 1. Click the Add button associated with the Specific Type Based Polling Configuration block of the Polling Configuration dialog. The Configure Specific Type Polling dialog opens. 196
- 197. WM Release 4.0 User Guide Issue 3 May 2012 Figure 131: Configure Specific Type Polling dialog for status polling 2. In the Specific Type field, use the drop‐down list to select the device type. 3. If you want to disable polling for the device type that you selected, uncheck the Enable Polling check box. 4. If you want polling of your selected device type to occur at an interval that differs from the Global Polling Interval in the previous dialog, type the number of Minutes into the Polling Interval text box or use the drop‐down list to change from Minutes to Hours type the number of hours into the text box. The following rules apply to resetting polling intervals: The smallest accepted polling interval is 1 minute. The largest accepted polling interval is 24 hours (1440 minutes). 5. When you are finished either disabling polling or specially setting the polling interval for the selected device type, click the OK button. The device type with its newly set polling status (disabled or special interval) is displayed in the Specific Device Type Polling Configuration block of the Polling Configuration dialog. note ............. If you attempted to apply an illegal interval, the client throws a pop-up error. for a value too small: for a value too large: note ............. If you attempted to apply an interval identical to the global polling settings, the client asks for confirmation. 197
- 198. Issue 3 WM Release 4.0 User Guide May 2012 6. Back in the Polling Confirmation dialog, you can use ◦ the Remove button to return a highlighted device type to global polling treatment ◦ the Modify button to change the settings (in a dialog like that shown in Figure 268 above, but with the device type preselected and not changeable) that you previously made by the procedure. ◦ the Reset to Defaults button to restore all polling intervals for all device types to the value of the GlobalStatusPollingInterval tag in the file .../WM/server/conf/WibbWMSConfiguration.xml in the WM server file system. 8.2 Viewing Basic Properties Procedure 14: To view device details 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Element Properties. The Element Properties dialog opens with the network/device properties. Figure 132: Element Properties, General tab 3. To view the SNMP properties of the device, click SNMP in the left panel. 198
- 199. WM Release 4.0 User Guide Issue 3 May 2012 Figure 133: Element Properties, SNMP tab 4. To view details of WM monitoring the device, click Monitoring in the left panel. Figure 134: Element Properties, Monitoring tab 199
- 200. Issue 3 WM Release 4.0 User Guide May 2012 5. To view relationships that have been detected for the device, click Relationship in the left panel. Figure 135: Element Properties, Relationship tab 8.3 Viewing Component Properties Use the Components option in the device‐specific menu to display the components for the selected device. For multi‐agent devices, information about both the agent representing the radio and the agent representing the host will be displayed. Procedure 15: To view component details 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Components. Figure 136: Show Components panel 200
- 201. WM Release 4.0 User Guide Issue 3 May 2012 3. To view the properties that WM is currently storing for the device ◦ select a component from the table in the Show Components window. ◦ click the Properties button. To view current properties, click the Update Status button. note ............. This is the way to view the status from multiple SNMP agents. By contrast, using the right- click option and selecting Update Status from the drop-down list of options results in a status update of only the agent for the radio. Figure 137: Component Properties window 4. Change any of the read‐write properties that you want to update. 5. To save the properties that you are viewing, click the Save to database button. 8.4 Viewing Events for a Device Procedure 16: To view events generated for a device 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Go ToEvents. The Network Events Viewer is displayed, which shows all the events for only that device. 201
- 202. Issue 3 WM Release 4.0 User Guide May 2012 Figure 138: Network Events view for a single device For more information on Network Events Viewer, refer to Viewing All Events on Page 347. 8.5 Viewing Alarms for a Device Procedure 17: To view alarms generated for a device 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Go ToAlarms. The Alarms view is displayed, showing all the alarms that are generated for only that device. An example of the Alarms view for a single element in as follows. Figure 139: Alarms view for a single device 202
- 203. WM Release 4.0 User Guide Issue 3 May 2012 8.6 Viewing Performance Data for a Device Procedure 18: To view performance data of a device 1. In the Inventory view, right‐click the device. 2. From the drop‐down list of options, select Go ToStatistics. The performance data Configured Collection view is displayed. The performance data is not intended to reflect the status of the device. The icon associated with a device in the Inventory view reflect its status. Figure 140: Performance data Configured Collection view for a single device For information on the Configured Collection view, refer to List of Available Performance Statistics (Configured Collection) on Page 382. 203
- 204. Issue 3 WM Release 4.0 User Guide May 2012 8.7 Viewing the Dashboard for a Device For each device of a supported device type, the WM client displays upon demand a module of text and graphics that summarizes the status based on retrieved performance data, configuration properties, events, alarms, status, and basic managed object properties. Access to this dashboard is by any of the following means: a double click on the device in the Inventory a right‐click on the device in the Inventory and then selection of Dashboard from the resulting drop‐down list of options a click on the device in the physical map and then a click on the Dashboard link in the Manage tab of the data pop‐up window The dashboards vary in format somewhat, from one device type to another, but only to the extent that the sets of data that they make available to WM differ. The client does not limit the number of network element dashboard windows that you can simultaneously have open (except only one per device) and allows you to independently move or reduce each of them. Immediately beneath the menu bar, each network element dashboard contains a status bar whose color, as well as text, indicates the current status of the element with its Device Name and Name (ID). 8.7.1 Examples of Network Element Dashboards Examples of network element dashboards are shown in Figure 141: Dashboard format for PMP AP on Page 205 Figure 142: Dashboard format for PMP SM on Page 206 Figure 143: Dashboard format for PMP 320 AP on Page 207 Figure 144: Dashboard format for PMP 320 CPE on Page 208 Figure 145: Dashboard format for PMP OFDM AP on Page 209 Figure 146: Dashboard format for PMP OFDM SM on Page 210 Figure 147: Dashboard format for PMP BHM on Page 211 Figure 148: Dashboard format for PMP BHS on Page 212 Figure 149: Dashboard format for PTP 500 Master on Page 213 Figure 150: Dashboard format for PTP 800 Slave on Page 214 Figure 151: Dashboard format for CMM3 on Page 215 Figure 152: Dashboard format for CMM4 on Page 215 Figure 153: Dashboard format for 14‐Port Switch on Page 216 Figure 154: Dashboard format for Generic Element on Page 216 Figure 155: Dashboard format for Extreme Switch on Page 217 Figure 156: Dashboard format for RAD Switch on Page 217 Figure 157: Dashboard for a child WM element on Page 218 204
- 205. WM Release 4.0 User Guide Issue 3 May 2012 Figure 141: Dashboard format for PMP AP 205
- 206. Issue 3 WM Release 4.0 User Guide May 2012 Figure 142: Dashboard format for PMP SM 206
- 207. WM Release 4.0 User Guide Issue 3 May 2012 Figure 143: Dashboard format for PMP 320 AP 207
- 208. Issue 3 WM Release 4.0 User Guide May 2012 Figure 144: Dashboard format for PMP 320 CPE 208
- 209. WM Release 4.0 User Guide Issue 3 May 2012 Figure 145: Dashboard format for PMP OFDM AP 209
- 210. Issue 3 WM Release 4.0 User Guide May 2012 Figure 146: Dashboard format for PMP OFDM SM 210
- 211. WM Release 4.0 User Guide Issue 3 May 2012 Figure 147: Dashboard format for PMP BHM 211
- 212. Issue 3 WM Release 4.0 User Guide May 2012 Figure 148: Dashboard format for PMP BHS 212
- 213. WM Release 4.0 User Guide Issue 3 May 2012 Figure 149: Dashboard format for PTP 500 Master 213
- 214. Issue 3 WM Release 4.0 User Guide May 2012 Figure 150: Dashboard format for PTP 800 Slave 214
- 215. WM Release 4.0 User Guide Issue 3 May 2012 Figure 151: Dashboard format for CMM3 Figure 152: Dashboard format for CMM4 215
- 216. Issue 3 WM Release 4.0 User Guide May 2012 Figure 153: Dashboard format for 14-Port Switch Figure 154: Dashboard format for Generic Element 216
- 217. WM Release 4.0 User Guide Issue 3 May 2012 Figure 155: Dashboard format for Extreme Switch Figure 156: Dashboard format for RAD Switch 217
- 218. Issue 3 WM Release 4.0 User Guide May 2012 Figure 157: Dashboard for a child WM element 218
- 219. WM Release 4.0 User Guide Issue 3 May 2012 8.7.2 Features of Network Element Dashboards Each network element dashboard window includes a series of icons in the upper right corner and a variety of options available from the menu bar in the upper left corner. Clicking on these icons or making a selection from the dashboard menu has the following results. Table 10: Command options from a network element dashboard Icon Menu Item Result opens the physical map and zooms to the device. See Accessing Data ViewPhysical Map for a Device in the Physical Map on Page 174. ViewInventory opens an Inventory viewer that contains only this device. opens an Extended family for Device Name graphical view that includes all members of parent‐child relationships, the set of which includes the device whose dashboard you are viewing. These are ViewLogical logical relationships that either the operator configured (see Adding HierarchyExtended Family Relationships Among Devices on Page 234) or WM inferred, based on their geo‐locations and device types (see Checking Relationships Presumed Based On Geo‐locations on Page 232). opens an Inventory view that includes all devices to which the device whose dashboard you are viewing is configured as the parent. These ViewLogical are logical relationships that either the operator configured (see HierarchyChildren Adding Relationships Among Devices on Page 234) or WM inferred, based on their geo‐locations and device types (see Checking Relationships Presumed Based On Geo‐locations on Page 232). opens a Configured Collection viewer that contains statistics for only ViewStatistics this device. See Figure 140 on Page 203. opens an Alarms viewer that displays only alarms that are associated ViewAlarms with the device whose dashboard you are viewing. See Figure 139 on Page 202. opens a Network Events viewer that displays only events that are ViewEvents associated with this device. See Figure 248 on Page 346. polls the individual device for its latest data and updates the dashboard when it receives that data. If you do not use this option, then the data in a dashboard refreshes in the amount of time required for the server to detect a change and the client to reflect the changed information that it receives from the server. opens a Show Components window that includes the MAC and IP ViewComponents addresses, SNMP version, and up time for each agent in this device. See Figure 136 on Page 200. opens a Web Page URL window with an OK button that provides HTTP LaunchWebPage access to the management web page of this device. See Figure 182 on Page 257. 219
- 220. Issue 3 WM Release 4.0 User Guide May 2012 Icon Menu Item Result opens the Edit Device Name dialog to the Configuration Groups for ConfigurationConfigure Device which WM can push values to the device. See Using the Configure Device Command on Page 611. opens an Apply Template dialog to the names and associated descriptions and versions of all configuration templates that have ConfigurationConfiguration been imported or created and are proper for the device type of the TemplatesApply Template device. See Pushing Values from a Prestructured Configuration Template on Page 619 and Applying a Configuration Template on Page 626. opens a Create Template dialog that displays all of the configurable ConfigurationConfiguration attributes for which WM can push values to the device, and for each TemplatesCreate Template an option to include or exclude it from the template being created. See Creating a Configuration Template on Page 621. opens an Edit Template dialog that displays all of the configurable ConfigurationConfiguration attributes for which WM can push values to the device, and for each TemplatesEdit Template an option to include or exclude it from the template being created. See Editing a Configuration Template on Page 629, opens a Delete Template dialog to the names and associated ConfigurationConfiguration descriptions and device types of all configuration templates that have TemplatesDelete Template been imported or created and are proper for the device type of the device. See Deleting a Configuration Template on Page 634. opens a preconfigured report, formatted in blocks for Current Alarms, ReportsDevice Summary Report Last 10 Events, Configuration Data, and Performance Data of the device. See Viewing a Device Summary Report on Page 223. opens an Execute Configuration Report dialog to the names and ReportsConfiguration associated descriptions and device types of all configuration reports ReportsRun Report that have been imported or created and are proper for the device type of the device. See Running a Configuration Report on Page 331. opens a Create Report dialog that displays all of the configurable ReportsConfiguration attributes for which WM can push values to the device, and for each ReportsCreate Report an option to include or exclude it from the report being created. See Creating a Configuration Report on Page 326. opens an Execute Configuration Report dialog to the names and associated descriptions and device types of all configuration reports ReportsConfiguration that have been imported or created and are proper for the device type ReportsEdit Report of the device. See Editing a Configuration Report Template on Page 335. opens an Delete Report dialog to the names and associated ReportsConfiguration descriptions and device types of all configuration reports that have ReportsDelete Report been imported or created and are proper for the device type of the device. See Deleting a Configuration Report on Page 337. 220
- 221. WM Release 4.0 User Guide Issue 3 May 2012 Icon Menu Item Result opens a network element dashboard view that includes the devices to which the one whose dashboard you are viewing is configured as the child. This is a logical relationship that either the operator configured (see Adding Relationships Among Devices on Page 234) or WM KinParent inferred, based on their geo‐locations and device types (see Checking Relationships Presumed Based On Geo‐locations on Page 232). If a dashboard view of the parent device is already open, then it closes and reopens with current data from the database. opens a network element dashboard view that includes all devices to which the device whose dashboard you are viewing is configured as the parent. These are logical relationships that either the operator configured (see Adding Relationships Among Devices on Page 234) or KinChildrenChild WM inferred, based on their geo‐locations and device types (see Checking Relationships Presumed Based On Geo‐locations on Page 232). If a dashboard view of the child device is already open, then it closes and reopens with current data from the database. If the database contains no value for one or more of the statistics that the dashboard is preset to display for the device type, then the panel displays the message No value to plot. If the specific device type does not support responding to SNMP get queries for the statistic that the panel would otherwise display for the device type, then the panel displays the message Unable to read from device. Examples of these cases are shown in Figure 158. Figure 158: Dashboard panels without data 8.7.3 Interactive Components of Network Element Dashboards The tabular data, graphical representations, and underscored text within a dashboard are links as well. For example, if you double click in a row of the Alarms table, then an Alarms view opens to only that alarm. double click in a row of the Events table, then a Network Events view opens to only that event. double click in a row of the Session Table of a PMP AP or PTP master dashboard, then the dashboard of the in‐session SM that you clicked on opens. click on a line graph (such as Registered SM Count for a PMP AP or PTP master, Radio Power Level for a PMP SM, or Port‐N statistic for a CMM4 Switch) or other statistical representation (such as the thermometer in a Temperature panel, then a Collected statistics for Device Name window opens. Although it opens to a line graph of the same statistic, the Time of Collection in this window is initially 24 hours and adjustable to today, the last one week, or 221
- 222. Issue 3 WM Release 4.0 User Guide May 2012 any custom time frame that you configure in this window. You can also change the graph type to any option listed in Table 28 on Page 384. This view supports zooming, auto‐ranging, printing, and saving as a PNG file. These options are available through a right‐click anywhere in the graph area. (see Viewing a Collected Performance Statistic on Page 386). click on GPS Satellites Tracked or GPS Satellites Visible for a CMM, then a Collected statistics for Device Name window opens. In this case, it contains a line graph that is convertible to a different time frame or different graph type or table, as described immediately above and shown below. Figure 159: Collected statistics window for GPS Satellites Tracked click on Wired Link Status, then a Collected statistics for Device Name window opens. In this case, it contains only a table view that plots the Time of Collection against the Ethernet status (Up or Down) that the device detected at that time. click on Number of Ports for a generic element or any of the following links for a child WM element, then the Collected statistics window is fully convertible, as described for Registered SM Count above: − Number of Managed Objects − Number of Networks − Number of Nodes − Event Count − Alert Count − Free Memory 222
- 223. WM Release 4.0 User Guide Issue 3 May 2012 8.8 Viewing a Device Summary Report WM provides a preconfigured report for any device that you select from the Inventory view. Each is formatted in blocks for Current Alarms Last 10 Events Configuration Data Performance Data By default, device summary reports are accessible to every user. This access continues unless the administrator removes the permission for a specific user. Despite permissions settings, user access to device summary reports may also be limited by custom view scopes to which the user is assigned. WM does not filter out any of the configuration or performance data or process any into summary data, but instead simply delivers the values from the response that the device sends to the query. These reports are available on demand as preconfigured (as described in the next section). They are also available through scheduled tasks. See Scheduling a One‐Time or Periodic Task on Page 647. 8.8.1 Running a Device Summary Report on Demand From any Inventory view, you can launch a report of this type by right‐clicking in the row of the target device and selecting ReportsDevice Summary Report. An HTML window opens to the entire report. 223
- 224. Issue 3 WM Release 4.0 User Guide May 2012 Figure 160: Device summary report for a PMP 430 SM 224
- 225. WM Release 4.0 User Guide Issue 3 May 2012 Figure 161: Device summary report for a child WM element 225
- 226. Issue 3 WM Release 4.0 User Guide May 2012 The report delivers the SNMP data in raw values. For example, the table expresses enabled/disabled flags as integers. 8.8.2 Running a Device Summary Report on a Schedule Running a device summary report is a schedulable task in the WM client. See Scheduling a One‐Time or Periodic Task on Page 647. 8.8.3 Saving a Device Summary Report As soon as you launch a device summary report, WM automatically saves it into a repository that contains in list from all previously launched reports that have not been deleted from the list. You can access this repository by selecting System ReportsReport Results from the Applications Tree. This list is sortable by any of its columns: Result File Name (in the format ReportName_SequentiallyAssignedReportNumber, so that within each alpha sort of report name, the order is chronological) User (who launched the report) Time (date and time) Report Name Report Type Figure 162: Report Results window Since the reports in the list are not searchable, and since the list of stored reports tends to grow over time, sorting is useful. Secondary sorting is achievable by sorting the secondary sort column first, then the primary sort column. To view an individual report in the Report Results view, right click on the target report and select View Report. This opens the report in the exact format and window size that the report opened in when you originally launched it. note ............. When the system assigns the name to a device summary report, the name does not inherit the Name (ID) or Device Name of the subject device, and the Search function in the client does not search the contents of the Report Results repository. So, as you are reviewing a report that you may want to later easily retrieve, you should copy or print the contents as follows. 226
- 227. WM Release 4.0 User Guide Issue 3 May 2012 As with the system reports that WM formats into vertical blocks, the report dialog does not include an export option. However, to dump a portion (such as the contents of a block) of the HTML data that the report returns to a file type that an another application can read or a script can use, you can mark the portion of interest and copy it out. This could be especially useful for portions that are not the subject of any reports that you can launch via System Reports. (See Using Configuration Summary Reports on Page 339.) You can reshape the HTML window, but not manually resize its columns or sort by their content. However, you can export the entire report as CSV for use in another application or Print the entire report on any networked printer. 8.8.4 Deleting a Device Summary Report To permanently remove a device summary report, open the list of available report results by selecting System ReportsReport Results from the Applications Tree. Right‐click on the report that you want to remove, and select Delete Report. 8.9 Finding the Customer Assigned to the Device The Inventory view provides a command option to immediately retrieve the full set of contact data for a customer who is assigned to (associated with) a particular device. The access to this information is through a right‐click on the target device and selection of Customer Contact Detail from the drop‐ down list of options. In the case where no customer has been assigned to the device yet, the system respond with the following message: If you click Yes, then a Customer Contact Management opens and displays a list of all customer‐ device assignments that exist in the database. Figure 163: Customer Contact Management window If no record exists yet, then the Assign To and View Detail buttons are inactive, and the only operation that this window permits is to Close it. If any record already exists, then the Assign To and View Detail buttons in this window are active. If you want to add the device to a listed customer record, click to highlight the row of the customer, then click the Assign To button. The target device is assigned to the selected customer. 227
- 229. WM Release 4.0 User Guide Issue 3 May 2012 9 Performing Other Operations on Devices 9.1 Keeping Device Identifiers Unique To avoid confusion in the client application and problems in device discovery, it is imperative to avoid assigning the same value to certain device attributes of more than one managed device; for example Device Name should be unique, so that records that you view apply to only the device whose records you want to view IP Address must be unique, so that WM internal operations keyed to device IP address, as well as user operations, are not subject to corrupt or mottled data. To keep them unique, ensure − that authorized users avoid redundant IP address assignment − DHCP, where deployed, is configured to avoid it as well. This is also a hazard when you replace one device with another, unless the device being replaced is removed from the network first. If you find more than one managed device that each has the same IP address, set all but one of them to Unmanaged (as described in the following section) until they can be assigned unique addresses of their own. 9.2 Managing or Unmanaging a Device WM manages all network elements that it discovers for which licenses are available, including third‐ party devices for which operators create device definition templates and even generic devices. To free up a node license for a currently unmanaged element, it may be desirable to Unmanage another. The newly unmanaged element continues to be present in the Inventory and physical map, but its color indicator is gray until it is moved back to the Manage state, at which point its color indicator returns to that of its highest current alert. Other differences between managed and unmanaged devices are as follows: for managed devices, WM does status and performance data polling, detects faults, and performs auto rediscovery and therefore detects configuration changes that may have been made from a source other than WM. It also can push configurable attribute values to managed devices and displays the current performance of their links. for unmanaged devices, WM does no status or performance data polling and performs no fault detection or auto rediscovery, during which changes that may have been made from a source other than WM could have been detected. It ignores the unmanaged devices from any scheduled tasks and does not push configurable attribute values to unmanaged devices or display the performance of their links. WM ignores traps sent from the agent(s) of unmanaged devices. However, WM retains performance data that it collected for the device during the time that is was in the managed state in anticipation of its return to that state. 229
- 230. Issue 3 WM Release 4.0 User Guide May 2012 In an Inventory view of devices, select the Manage or Unmanage command option from the right‐ click drop‐down menu to change the management status of a selected device. The client GUI responds as follows to each attempt to change the network element state of a device: When you move a device from Manage to Unmanage A confirmation pop‐up message asks you to confirm the switch. To proceed, click the Yes button. To leave the device in the managed state, click the No button. WM adds an event of Info severity to the Event Viewer. The audit log records the state change against the user account. The color indicator for the device changes to gray. The license that License Manager had allocated to the device will become available for a device that you move into the managed state. When you move a device from Unmanage to Manage A confirmation pop‐up message asks you to confirm the switch. To proceed, click the Yes button. To leave the device in the unmanaged state, click the No button. If License Manager cannot allocate a license to the device, then WM adds to the appropriate logs errors to indicate that the switch failed. WM adds an event of Info severity to the Event Viewer, indicating either the success or the failure of the switch. The color indicator for the device returns to that of the highest current associated alert. The device is among the affected devices for each task that was previously scheduled for it. 9.3 Pinging a Device The Ping Device command is available from all right‐click device menus. This command option causes WM to ping the selected (highlighted) device(s) and to open a Pinging Components window that displays the results of the ping. In this window, a returned message of Request Timed out or Destination Host Unreachable indicates the current IP address of the device was not found. If any of the selected devices is currently configured as unmanaged, then WM displays an Unmanaged Component message. An example of these messages is shown in Figure 164. 230
- 231. WM Release 4.0 User Guide Issue 3 May 2012 Figure 164: Pinging Components window, success Figure 165: Pinging Components window, skipped for unmanaged component For a ping failure, the Pinging Components window indicates in red font Request timed out and 100% loss. If you want to repeat the ping to check for consistent results, click Clear before you click Ping Again. This clears the contents of the window, which are not automatically cleared before the next ping is triggered from the same window. Without clicking Clear again first, you cannot be confident that you are seeing the results of the second ping rather than the results of the first. 231
- 232. Issue 3 WM Release 4.0 User Guide May 2012 9.4 Dropping a Subscriber Session WM allows you to drop the session of (unregister) a PMP SM from the Inventory view. The target device may be either the currently highlighted SM or the one that you select after invoking this feature from its PMP AP. A right‐click on either such device provides the ToolsDrop Subscriber Session command option for this purpose. When the right‐clicked element is a PMP AP, the Drop Subscriber Session for Name (ID) window opens and presents a drop‐down list of the PMP SMs that are currently registered in that AP. Figure 166: Drop Subscriber Session window for a PMP AP When the right‐clicked element is a PMP SM, the Drop Subscriber Session for Name (ID) window opens with the Name(ID) of the target device in gray and unalterable. If the Name (ID) is other than that of the device whose session you want to drop, cancel this window and right‐click the target device to invoke the feature again. Figure 167: Drop Subscriber Session for Name (ID) In either case, if you click the OK button in this window, WM sends the appropriate message to terminate the session of the PMP SM whose Name (ID) is displayed at that time. 9.5 Checking Relationships Presumed Based On Geo-locations Based on comparisons of certain settings in device templates on the server and the geo‐locations defined for devices in your network, the discovery engine in WM presumes logical relationships among devices and displays these. The presumptions are made whenever both the geo‐locations lie within template‐defined positions (tolerances) that establish four corners of a rectangle the devices are of device types that together have a presumable hierarchical relationship (would constitute an extended family). 232
- 233. WM Release 4.0 User Guide Issue 3 May 2012 Per device type, the tolerances can be either the defaults that the device template has defined or new ones that the server administrator has edited into the device template. Users requesting tolerance edits and administrators who edit device templates should keep in mind that the edits apply to all devices of the device type until further edits are made. An example of such a family is provided under Defining a Larger Extended Family on Page 234. Since these automatically established relationships are presumed based on numbers, not on detected communications among them, some may not reflect communications flow among the devices. Do a periodic inspection of logical relationships by right‐clicking on devices and selecting Go ToLogical HierarchyExtended Family from the drop‐down list of options. Then to expand an extended family, see Adding a Single Relationship on Page 235 and Defining a Larger Extended Family on Page 234. to edit devices out of an extended family, see Removing a Relationship (the next section). 9.6 Removing a Relationship Some relationships that WM automatically establishes may be incorrect in the context of data flow in your network or of how you wish to see the hierarchy of your network expressed. Based on device type and geo‐location, WM automatically establishes a relationship with a PTP device as the parent of a proximal CMM device. The example provided under Defining a Larger Extended Family on Page 234 includes a wired link that defies this default treatment. You can remove a relationship by removing an element from it. In an Inventory view, right‐click on the element you want to remove from the relationship and select the drop‐down option Go ToLogical HierarchyExtended Family. Then in the Extended Family for DeviceName logical graphic window, right‐click the link line and select Remove Relationship. Figure 168: Remove Relationship option in Extended Family window The system uses a Warning pop‐up message to ask for confirmation. 233
- 234. Issue 3 WM Release 4.0 User Guide May 2012 Figure 169: Remove relationship pop-up warning When you click OK to accept the proposed action and dismiss this window, WM removes the relationship. returns a success message. 9.7 Adding Relationships Among Devices 9.7.1 Defining a Larger Extended Family WM allows you to add relationships such that a logical connection extends as far as five hops above and five hops beneath an element. All of the related elements constitute an extended family, for the purpose of the user interface and its menu operations. An example of an extended family that is useful to define (in parent‐to‐child order) is 1. a CMM that provides timing to a PTP master at the POP at the top of a double backhaul‐hop configuration (master>slave>slave>master at cluster) 2. a PTP master at the POP in a double backhaul‐hop configuration 3. a PTP slave connected by Ethernet to another slave in a double backhaul‐hop configuration 4. a PTP slave (either as above or at the POP in a more typical configuration) 5. its PTP master 6. the CMM that provides timing to the PTP master and the APs at the cluster 7. an AP connected to the CMM 8. the SMs in the sector of the AP. 9. a Remote AP connected by Ethernet to one of those SMs 10. the SMs in the sector of the Remote AP Hops Notes From To 1 2 For this Ethernet connection, WM may create a juxtaposed parent‐child relationship (in the automatic link that it detects between these devices), which you may wish to correct. 2 3 For this RF connection, WM does not create a parent‐child relationship (automatic link). 234
- 235. WM Release 4.0 User Guide Issue 3 May 2012 Hops Notes From To 3 4 For this Ethernet connection, WM does not create a parent‐child relationship (automatic link). 4 5 For this RF connection, WM does not create a parent‐child relationship. 5 8 For these connections, WM correctly creates the parent‐child relationships in these links, which it automatically detects. 8 9 For this Ethernet connection, WM does not create a parent‐child relationship. 9 10 For these connections, WM correctly creates the parent‐child relationship. 9.7.2 Adding a Single Relationship All right‐click device menus include an Add Relationship option. This command creates a logical relationship (logical link) between two elements, but is not selectable when no elements are selected. If you select this option when there are more than two elements selected, the system displays the following message. when two elements are selected, the system opens an Add Relationship Between Elements window that is already populated with the two devices and includes a Parent of/Child of toggle. Figure 170: Add Relationship Between Elements dialog, both devices identified For convenience, you can use a Find button in this window to identify a different device in either or both positions. 235
- 236. Issue 3 WM Release 4.0 User Guide May 2012 when one element is selected, the system opens an Add Relationship Between Elements window that names the selected device as Device 1 and includes the Find option described above. Figure 171: Add Relationship Between Elements dialog, one device identified The Find option opens a Search Device dialog common throughout the client. The search results are absent of returns that are outside of any custom view scope defined for the user. In the context of the dialog prompt, Name (ID) means MAC address. When you select the other target device for the relationship, it becomes Device 2, as shown in Figure 170. When a device relationship has been created the system returns a confirmation: the Inventory branch of the Applications tree reflects the relationship (Links). The Links view will open in the right panel if you double‐click the Links branch in the Applications tree, and 236
- 237. WM Release 4.0 User Guide Issue 3 May 2012 as in any Inventory view while the relationship remains, the relationship is graphically represented in a pop‐up window if you right‐click the device and select the option Go ToLogical HierarchyExtended Family: Figure 172: Logical link displayed Similarly, the relationship is graphically represented in a pop‐up window if you right‐clicked the parent device and selected the option Go ToLogical HierarchyChildren. If the system returns the following error, this indicates that you attempted to add a relationship that would reverse the parent‐child roles of an already‐defined relationship. Figure 173: Circular reference error If you attempt to add a relationship that already exists, the system throws the following error: 237
- 238. Issue 3 WM Release 4.0 User Guide May 2012 9.8 Importing a Customer Contact Database WM allows the operator to associate customer information with the managed end‐user elements. This facilitates sending email to customers about the service they receive. These can be groups or individuals whom you select in the Customer Contact Detail window or whose assigned elements you select in an Inventory view. The behavior of the email commands is to send to only selected customers in Customer Contact Detail database (window) and send to all customers who are assigned to the selected element(s) in the Inventory view. You can add customer records in either or both of two ways: Import them from an external database. See Preparing the Customer Contact Data for Import (next) and Importing Customer Contact Data on Page 240. Be aware that these operations combined overwrite the entire pre‐existing customer database, including all of its element MAC addresses. Compose the record in WM. See Assigning a Customer to a Device on Page 242. This operation allows the user to essentially edit the individual record and even leave fields null. The customer database in WM also facilitates correlation of data in WM with data in external management, billing, and other operations systems. If you choose to periodically import customer contact information from an authoritative external source, use restrictive permissions for the Email Configuration node of the Administrative Operation branch in the Permissions tree hierarchy. See Assigning Operations on Page 482. 9.8.1 Preparing the Customer Contact Data for Import The WM import operation for customer contact data supports a comma‐separated values (.csv) file in which all of the following headings and some or all of these fields are populated for each customer you want included in the contact database: 1. Unique ID 6. City 11. Home Phone ≤128 characters ≤128 characters ≤20 characters 2. Customer Name 7. State 12. Work Phone ≤128 characters ≤50 characters ≤20 characters 3. Customer Type 8. Zip 13. Mobile Phone ≤128 characters ≤12 characters ≤20 characters 4. Address1 9. Country 14. Pager ≤128 characters ≤50 characters ≤20 characters 5. Address2 10. Email 15. MAC Address ≤128 characters ≤128 characters ≤128 characters The user has the discretion of how to populate these fields. For example, the Customer Type field may be populated by Residential or Commercial, or by any other set of values. Each line stores the data for one device‐customer association. 238
- 239. WM Release 4.0 User Guide Issue 3 May 2012 The population rules are as follows: The headings in the above syntax must occupy the first row of the .csv file. A comma must not be used within a values field (because the comma is the field delimiter), except where every literal‐intended comma in the entire CSV file is surrounded by the same escape character pair (text qualifier): either a pair of " double quotes or a pair of ' single quotes (apostrophe, ASCII char 39 Dec or 27 Hex). Choose only one as the text qualifier and do not use the other for the same purpose. All of the fields are strings. Except for MAC Address (the 15th field), no requirements are placed on the format of the text in a field. The MAC Address entry can be in any of the following standard formats: − 0A:00:3E:30:01:B8 − 0A-00-3E-30-01-B8 − 0A003E3001B8 A Unique ID value cannot be used for more than one customer. For a customer who has more than one radio, repeat the Unique ID value in one row per additional radio (MAC address). You do not need to repeat the other data associated with the customer—Customer Name through Pager. (Blank fields in the successive rows of the same import operation do not cause WM to ignore or erase the populated values of those fields from previous rows that have the same unique id value. However, an import of a customer record overwrites the MAC address associations.) When you trigger an email message, WM avoids sending more than one copy of the message to any customer, regardless of the number of assets that are associated with the Unique ID of the customer. EXAMPLE: Customer ABC has two SMs with MAC Addresses 0A:00:3E:00:00:0A and 0A:00:3E:00:00:0B. Customer DEF has only one SM with MAC Address 0A:00:3E:00:00:0C. Their rows in the import file should look like this. Unique Id,Customer Name,...,MAC Address 1,ABC,...,0A:00:3E:00:00:0A 1,,...,0A:00:3E:00:00:0B 2,DEF,...,0A:00:3E:00:00:0C Thus, the Unique Id value must be unique per customer, not per row. For a radio that is shared by more than one customer, enter each customer on an individual row with a unique ID in the Unique ID field, but with the same MAC address in their MAC Address fields. WM then allows you to trigger an email message to all customers who are associated with that MAC address. WM supports and accepts data from optional fields that you enter as additional columns in your external database. WM adds these fields and their values to only the Customer Contact Management window. 239
- 240. Issue 3 WM Release 4.0 User Guide May 2012 9.8.2 Importing Customer Contact Data The client provides a command option to import a customer contact database that is formatted as described under Preparing the Customer Contact Data for Import on Page 238. To import the database, perform the following steps. Procedure 19: To import a customer contact database 1. Regardless of the type of view that is active in the view panel, select ToolsImport and Export from the main menu. The Select operation window opens Figure 174: Select operation window 2. Click to select the Import Customer Contact Information radio button. 3. Click Next. The Import Customer Contact Information window opens. 240
- 241. WM Release 4.0 User Guide Issue 3 May 2012 Figure 175: Import Customer Contact Information window 4. Click the down arrow associated with Text Qualifier. 5. Select the escape character that your CSV file uses to surround commas that are part of the data (that are not intended as delimiters). note ............. Keep in mind that WM will not print any instances of the selected escape character into any customer record as a literal character. 6. Browse to and select the CSV file that contains the properly formatted data. In any subsequent import of a .csv file into WM, overwriting a record or adding a new record occurs on a whole record‐by‐whole record basis as follows: WM overwrites the contact data for any customer whose unique id identically matches the unique id in a previously stored record. WM accepts the contact data for any customer whose unique id was not previously stored. WM keeps the contact data for any customer whose unique id was previously stored and is not included in the current import. Each MAC address represents a radio device. When you import customer contact data, WM attempts to associate the customer with the devices by MAC Address, but only where WM already manages the device. For any device that WM does not already manage, you must associate the device to its MAC address in the WM GUI. See Assigning a Customer to a Device (below). An import file must exist within file browser range of the client when the import operation is invoked. To perform the import operation, see Importing Data Files Into WM on Page 105. As soon as the operation is executed in the client, user account management under the imported user configuration begins. 241
- 242. Issue 3 WM Release 4.0 User Guide May 2012 9.9 Assigning a Customer to a Device You can add a record for an individual customer in either or both of two ways: import it alone or among other records that you are adding. See the sections that immediately precede this one, beginning on Page 238. This operation overwrites the entire pre‐existing customer record, including all of its associated element MAC addresses. compose the record in the WM GUI. For a new customer, this operation adds the customer with all of the associated elements to the database. To compose a new record, perform the following steps. Procedure 20: To compose a customer-device(s) record 1. Regardless of the view that is active in the view panel, select ToolsCustomer Contact Management from the main menu. The Customer Contact Management window opens. Figure 176: Customer Contact Management window 2. Click the Add button. The Customer Information dialog opens. 242
- 243. WM Release 4.0 User Guide Issue 3 May 2012 Figure 177: Customer Information dialog 3. In the left panel of this dialog, populate the Customer Information text fields. note ............. What you type into the Email text box becomes the addressee of email that WM will set up for you to send to the customer from the sender address specified in your SMTP configuration, whenever you click the Email button with one or more rows selected in the Customer Contact Management window. 243
- 244. Issue 3 WM Release 4.0 User Guide May 2012 4. In the right panel of this dialog, click the Add button. A window opens for specifying one or more devices. 5. In the Devices tab of the window that opens, the device selection process is identical to that process for defining a scheduled task. For reference, see Procedure 197: To define a Configuration task on Page 653. 6. Specify all devices that you want to assign to this customer. 244
- 245. WM Release 4.0 User Guide Issue 3 May 2012 7. Click OK. The Network Elements panel lists the selected device(s). 8. When you are finished specifying the customer‐element association(s), click OK. The record is added to the Customer Contact Management table view. 9. If the actual location of the device(s) is the same as the address you typed in for the customer, optionally check the Update Device Location check box. This feature writes the contents of the customer address into the Site Location field(s) stored in the device. 10. Click OK. The record is added to the Customer Contact Management window. 245
- 246. Issue 3 WM Release 4.0 User Guide May 2012 11. To add another customer, click the Add button and repeat these steps. 12. If you see that a correction needs to be made in a record, either double click the row or click the Edit button for access to the text fields. 13. Click the Close button. 9.10 Editing or Removing a Customer Record For a customer who is already in the database, this operation allows you to edit the record and even leave fields null. To edit an existing record, perform the following steps. Procedure 21: To edit a customer-device(s) record 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Customer Contact Detail. If no existing record is associated with this device, then the system returns a message asking whether you want to add one. If this occurs, use the section Assigning a Customer to a Device (above) to add the proper record. If an existing record matches this device, then a Customer Information window opens, populated with the data that WM stores about its customer. 246
- 247. WM Release 4.0 User Guide Issue 3 May 2012 3. Use the text fields in the left panel or the options via the right panel to adjust or remove the record. 9.11 Sending an Email Notification to a Customer WM sets up email composition for notifications to one or more customers for any purpose, such as marketing higher tiers of service, announcing price changes or anticipated outages, or confirming updates to account information. In the main menu, select ToolsCustomer Contact Management. In the Customer Contact Management window, click to highlight all intended recipients of an email message, then click the Email button. The Compose Email composition window opens, populated with the recipients in the To line the sending address (from you SMTP configuration) in the From line. 247
- 248. Issue 3 WM Release 4.0 User Guide May 2012 Compose the Subject and body of the email, then click the Send button. 9.12 Refreshing Device Data In the Inventory view, the right‐click command option Refresh Stored Data forces WM to perform a rediscovery of the currently selected device(s). As in auto rediscovery WM retains the performance data, alarms, and events that relate to the element and erases only the previous configuration data for it, which WM replaces with the response about the current configuration. the Refresh Stored Data command also rebuilds the automatically determined logical links for the selected device. 9.13 Setting WM Credentials for a Group of Selected Devices WM provides a single, efficient operation to set any, some, or all of the following device credentials that it uses for authenticating itself in each device among a currently selected set: Read Community Write Community Telnet/FTP Login ID Telnet/FTP Password Keep in mind that this operation does not also write new values for these credentials into the target devices, but rather only configures WM to use their new values. The user of this feature must be authorized in the Permissions tree at Device ToolsCredential Manager. As an authorized user, you can access this feature in any of three ways: from the network updater interface (via Install Software Upgrades) from the tools menu (via ToolsCredential Manager from the main menu), where devices currently selected in the Inventory are not inherited as initial target devices. from the Customer Support Tool dialog (via the Credential Manager button in the Devices tab), where devices selected by the Add or the Load From Group operation before clicking the button are inherited as initial target devices. How you raise Credential Manager determines whether the Add/Remove Devices options (Add, Remove, and Load From Group) are included in the Credential Manager dialog. These are not included if you raise Credential Manager from a Software Upgrade or Customer Support Tool dialog. 248
- 249. WM Release 4.0 User Guide Issue 3 May 2012 To use Credential Manager, perform the following steps. Procedure 22: To set credentials for a selected group of devices 1. Launch the feature in any of the three ways noted above. The Credential Manager dialog opens. Figure 178: Credential Manager dialog 2. In the Devices Selected frame, optionally check the check box for Show Password to display in plain text the Telnet/FTP Passwords that WM currently uses to authenticate itself in the listed devices. 3. Use Ctrl+click to highlight all devices whose Credentials you want to identically reset. 4. In the Credentials frame, check the checkbox for each credential that you want to identically reset. 5. In the associated text box(es), type in the new value(s) of the credentials(s). 6. Click the button between the frames of this dialog. The column entries of the Devices Selected frame display the new value(s). 7. To confirm that all the values that the columns of the Devices Selected frame display will succeed in authenticating WM to those devices, click the Verify Credentials button. RESULT: WM returns a success (row painted green) or failure (row painted red) indication for each element that was selected for the verify operation. For any element whose Read Community verify failed, the operation skipped the Write Community verify and indicates failure. 8. To enforce the new value(s), click the Apply button. 249
- 250. Issue 3 WM Release 4.0 User Guide May 2012 9. If you have additional new values to configure for any of the devices in the list a. uncheck the check box of any credential that you do not want to configure in this next operation. b. repeat Steps 4 through 8. 9.14 Configuring a Device This command option is available for a device in the Inventory view. This feature is described under Using the Configure Device Command on Page 611. 9.15 Syncing the SNMP String in WM with the SNMP String in a Device Ensure that the value configured for Write Community in the Managed Object Properties that WM stores (Figure 133 on Page 199) identically matches the SNMP Community Write string in the device, regardless of whether the current value derives from factory configuration of the device, from an edit in the management HTTP interface to the device, or from a configuration push made by a template from WM. 9.16 Using the Link Capacity Test Utility A Link Capacity Test allows you to measure the throughput and efficiency of the RF link between two devices. Many factors, including packet length, affect throughput. WM provides the capability to perform a Link Capacity Test on PMP APs and SMs, when you specify the SM, either as the right‐click device in the Inventory view from which the test is launched or as selected by either its LUID or its Name (ID), if the test interface is launched from a right‐click on an AP in the Inventory view. This feature includes both the launch of the functionality in these devices and GUI features that are similar to how the web‐based management interfaces of these devices provide their options and display their results. The Link Capacity Test dialog contains a settable Packet Length with the range 64 to 1522 bytes. This allows you to compare throughput levels that result from various packet sizes. 9.16.1 Launching a Link Capacity Test To launch a test, perform the following steps. Procedure 23: To perform a link capacity test in an SM 1. In an Inventory view, right‐click either the target SM or the AP to which it is registered. 2. In the resulting drop‐down list of options, select ToolsLink Capacity Test. WM opens a Link Capacity Test dialog whose operation depends on whether the feature was launched from a selected SM or AP. 250
- 251. WM Release 4.0 User Guide Issue 3 May 2012 If the selected device was an SM, then the dialog resembles the following: The Current Subscriber Module value is gray and fixed to Name (ID) and LUID of the SM that you preselected. 251
- 252. Issue 3 WM Release 4.0 User Guide May 2012 If instead you preselected an AP, then the dialog resembles the following: In this case, the dialog allows you to select any of the AP's registered SMs from the drop‐ down list for Current Subscriber Module. 3. If you preselected an AP, select the SM whose link to the AP you want to test. 4. For Duration, either leave 2 or overwrite it with the number of seconds (up to 10) for the test to last. 5. For Packet Length, either leave 1522 or overwrite it with the number of bytes (down to 64) for the packet size to send in the test. 6. Click the Start Test button. After performing the test and assembling the data that the test generated (this could be several seconds longer than the test itself), WM repaints the Link Capacity Test window to deliver the data and present the opportunity to test the link again, this time with a different packet size, for example, if you wish. 252
- 253. WM Release 4.0 User Guide Issue 3 May 2012 Figure 179: Link Capacity Test results window 9.16.2 Interpreting Link Capacity Test Results The key fields in the test results are Downlink Rate and Uplink Rate, expressed in bits per second Downlink Efficiency and Uplink Efficiency, expressed as a percentage. note ............. In the results, interpret Downlink and Uplink as directions from the perspective of the AP, even if the link capacity test was launched with the SM selected. A link is acceptable only if the efficiencies of the link test are greater than 90% in both the uplink and downlink direction, except during 2X or 3X operation (see the PMP user guide for further guidance). Whenever you install a new link, execute a link test to ensure that the efficiencies are within recommended guidelines. The AP downlink data percentage, slot settings, other traffic in the sector, and the quality of the RF environment all affect throughput. However, a Maximum Information Rate (MIR) throttle or cap on the SM does not affect throughput. 253
- 254. Issue 3 WM Release 4.0 User Guide May 2012 9.16.3 Errors in the Link Capacity Test Feature If you launch the feature by the right‐click of an SM that is currently not registered to any AP, then WM returns the error This SM is not registered to an AP. Unable to test. If you launch the feature by the right‐click of an AP that currently has no registered SMs, then WM returns the error No SMs registered to AP. Unable to test. 9.17 Using the Spectrum Analyzer Utility Whether maintaining or growing your network, you may encounter new RF traffic that can interfere with your current or planned equipment. Regularly measuring RF transmissions over a period of time and retrieving records of the RF environment help you to recognize and react to changes. WM provides the capability to launch the Spectrum Analyzer feature in any OFDM or FSK PMP SM or any PMP 320 AP. view the graphic display of the frequency and power level of all detectable signals within, just above, or just below the frequency band range of the target device as soon as the Duration that you specify for the sampling has elapsed. important ........... When you launch the Spectrum Analyzer from a PMP SM, the target SM enters a scan mode and drops any RF connection it had. Good practice is to vary the days and times when you analyze the spectrum in an area, since the RF environment can change throughout the day or throughout the week. note ............. In both an FSK and an OFDM SM, the built-in spectrum analyzer feature measures the detected peak power level. This is consistent with the received Power Level that various tabs in the web-based management interface of an FSK radio reports. However, it is inconsistent with received Power Level indications in the management interface of an OFDM radio, which use the Power Level parameter to report the detected average. Although the spectrum analyzer functionality can be very useful as a tool for troubleshooting and RF planning, but is not intended to replicate the accuracy and programmability of a high‐end spectrum analyzer, which you may sometime need for other purposes. 9.17.1 Launching Spectrum Analyzer To launch this feature, perform the following steps. Procedure 24: To use the Spectrum Analyzer feature 1. In an Inventory view, right‐click on the target device. 2. From the drop‐down list of command options, select ToolsSpectrum Analyzer. The Spectrum Analyzer window opens. 254
- 255. WM Release 4.0 User Guide Issue 3 May 2012 note ............. If this feature was launched from a target PMP SM, the Current Subscriber Module field is grey, and its drop-down selector is not available. If it was launched from a PMP 320 AP, then the drop-down list is similarly inactive and displays in gray the Name (ID) of the target PMP 320 AP. 3. For the Duration field, either leave 10 seconds as the duration or highlight 10 and type in the number of seconds (1000 or fewer) for which you want the analysis performed. 4. Click the Start Remote Spectrum Analysis button. 5. Wait beyond the length of time that you specified for Duration. Figure 180: Spectrum Analyzer window for a PMP 320 AP 255
- 256. Issue 3 WM Release 4.0 User Guide May 2012 Figure 181: Spectrum Analyzer window for a PMP SM note ............. the first painting of results may display bars for fewer than all frequencies, especially in bands with a large number of center channels, like the 5.4-GHz band. 6. Optionally, click the Start Remote Spectrum Analysis button again. It is reasonable to expect that the resulting graph will represent the entire spectrum this time. 9.17.2 Interpreting Spectrum Analyzer Results Colors in the display have the following meanings: Green bars show the most recent measurements. Yellow ticks show the maximum measurements from the current spectrum analysis session. Red ticks show measurements of −40 dBm or stronger. 256
- 257. WM Release 4.0 User Guide Issue 3 May 2012 9.17.3 Errors in the Spectrum Analyzer Feature Although the right‐click menu for OFDM and FSK PMP APs include the ToolsSpectrum Analyzer command option, WM does not support it, and returns the following error when this option is selected: This operation is not supported for the selected device. 9.18 Accessing the Web Interface of a Device This section describes how to access the management interface of a device. The example procedure for the LaunchWebPage command in the following subsection uses a PMP SM as the target device. It is generally advisable to use WM to push configurable values to a device and use the web interface of the device to only occasionally, or when doubt is cast by a message in the log, visit the device to check on the success of configuration attempts from WM. Similarly, it is generally advisable to use WM to push values to PTP devices and visit their interfaces for troubleshooting. Documentation on logging into those devices is provided in the device documentation set. The Inventory view supports the right‐click LaunchWebPage command utility for access to the management web page of a highlighted device. You can use this utility to perform device configuration tasks that are not available in WM because of limitations that the SNMP interface of the device has. verify device configuration against what WM reports about the device. Procedure 25: To open a device web interface 1. In the Inventory view, right‐click the device whose web interface you want to open. 2. From the drop‐down list of options, select LaunchWebPage. The home page of the device web interface opens. Figure 182: Device web page URL note ............. This dialog is populated with a default selection (Device Home Page) and includes a drop-down selection for a blank dialog box into which you can type any other URL. The blank box is provided because a selected device (depending on device type) may have more than one URL and because, in some cases, the computer on which you are running the WM client may not have direct access to the IP address that WM uses to communicate with the device. For this latter case, you may need to type a different IP address (known to you outside of WM) into the blank dialog box. For devices that support access via either http or https, these protocols are separately selectable in the drop-down list. 257
- 258. Issue 3 WM Release 4.0 User Guide May 2012 3. Either leave Device Home Page selected or type an IP address into the blank dialog box. If the site was already listed as trusted, then the management home web page opens. If not, then an Enhanced Security Configuration warning window opens. Figure 183: Enhanced Security Configuration warning 4. To add the web interface of the selected device to the list of trusted sites, click Add. A trusted sites window opens. Figure 184: Trusted sites window 5. Click Add. At this point it may appear that the connection is hanging, when it is not. Proceed to the next step. 6. Click Close. If the IP address being used is correct, a browser window opens to a blank screen with the text Press Here to Continue. 258
- 259. WM Release 4.0 User Guide Issue 3 May 2012 7. Click the word Here. The appearance of the following window depends on the device type. The remainder of this example uses an SM device URL. Figure 185: Initial web page of Subscriber Module 8. If the initial page includes To Proceed, press, click the word here beneath those words. The management home page opens. 259
- 260. Issue 3 WM Release 4.0 User Guide May 2012 Figure 186: Management home web page of a PMP Subscriber Module Browser controls are in effect and determine features such as font size in the web page. Be aware that, if you change any controls, those controls will remain in effect in the browser as you access other sites from your computer. The management interface demands a login using a valid configured user name and password to see any information above the basics displayed in the General tab or to configure any parameters. 9. To authenticate in the device interface, enter the Username and Password of an account that is already authorized for the management interface to the device, then click Login. note ............. If you click the bottom edge of the Username dialog box, the interface present a drop- down list of configured usernames to select from. If the login succeeds, the management interface opens to the full array of left‐panel links and top tabs for access to parameters and statistics. 260
- 261. WM Release 4.0 User Guide Issue 3 May 2012 Figure 187: Full management interface web page of PMP Subscriber Module The management home page opens. Refer to the device documentation set (typically, the device type‐specific user guide) for information about the configurable parameters and read‐only statistics to which you now have access. 10. When you are finished with your session in the interface, click Logoff. This prevents rogue access to the interface. 9.19 Deleting an Object and Traces Network elements that do not need to be managed can be deleted from the client as well as from the database. Based on your user privileges, you may have the option of deleting only a few network elements or a complete network. The primary reason to delete a device is to free up a slot in the node count of your WM license so that another device can be discovered and managed. important ........... The Delete Object and Traces option deletes the symbol and the object associated with that symbol from the database. If you do this, you will permanently lose all historical performance data and other information about the device. If you later want to resume managing the device, you will need to discover it again. 261
- 262. Issue 3 WM Release 4.0 User Guide May 2012 Procedure 26: To delete a device and all information about it 1. In the Inventory view, right‐click the target device. 2. From the drop‐down list of options, select Delete Object and Traces. Since you are asking for data to be removed, a pop‐up asks for confirmation. Figure 188: Confirmation message for Delete Object and Traces operation 3. If you want to proceed with the data removal, click Yes. The device will be deleted from the client as well as from the database. 9.20 Using the Bandwidth and Authentication Manager (BAM) Subsystem The BAM operations include and are limited to managing authentication and defining and applying bandwidth service plans and VLAN profiles for provisioned elements. Unlike configuration templates that you can create in WM to push bandwidth and VLAN values to elements, service plans and VLAN profiles in BAM are long‐term associations with the elements. When a service plan or VLAN profile is modified, the change is automatically applied to all elements that have the association. A further distinction is that SNMP‐applied values for bandwidth and VLAN require a reboot of the element in order to take effect; BAM‐applied plans and profiles immediately take effect. Whether the values that are sent by BAM in its proprietary protocol or by WM in SNMP are adopted for the elements depends on a setting in the AP. The AP contains a Configuration Source parameter, the value of which you could set on an AP‐by‐AP basis in the General tab of the Configuration web page in the direct management interface to AP. However, setting this on an AP‐by‐AP basis allows for possible error in consistency. If you use BAM for authentication, bandwidth, and VLAN settings, then this parameter must be set identically to the value BAM in all of the APs that are under WM management. Best practice is to use a configuration template to push the value BAM to all APs. important ........... If you are not using BAM, then this setting in all of the APs under WM management should be SM. Where BAM is used SMs will derive values for the following parameters 3 from BAM, presuming that you configure them in the user interface of BAM: − all MIR settings: Sustained Uplink Data Rate Uplink Burst Allocation 3 This list of parameters applies to SMs in which hardware scheduling is enabled. Older SMs in which software scheduling is enabled do not accept values for the Hi Priority Channel parameter or any of the CIR parameters. 262
- 263. WM Release 4.0 User Guide Issue 3 May 2012 Sustained Downlink Data Rate Downlink Burst Allocation − all SM VLAN settings: Dynamic Learning Allow Only Tagged Frames VLAN Aging Timeout Untagged Ingress VID Management VID VLAN Membership − the Hi Priority Channel setting − all CIR settings Low Priority Uplink CIR Low Priority Downlink CIR Hi Priority Uplink CIR Hi Priority Downlink CIR APs will ignore, and therefore SMs will not see, any values that WM directly sends via an element configuration template for these parameters, as long as you have Configuration Source in the AP set to BAM. Where the Configuration Source parameter in the AP is set to BAM, the SM stores a value for the Dynamic Learning VLAN parameter that differs from its factory default. When BAM does not send VLAN values (because VLAN Enable is set to No in BAM), the SM uses the stored Disable value for Dynamic Learning. shows the following in the VLAN Configuration web page: − either Enable or Disable as the value of the Dynamic Learning parameter. − Allow Learning : No under Active Configuration. If you use BAM, it is imperative that you use WM 4 to set the following values in your managed PMP elements: Configuration Source in all APs to BAM Authentication Mode in all APs (in whose sectors you want to impose authentication upon the SMs that attempt to register) to Authentication Required SM Management VID Pass‐through in all APs to Disable SM Management VID Pass‐through in all SMs to Disable In its authentication functionality, BAM is unable to distinguish an element as a master or a slave until the slave element attempts to register in the master. If you want to pre‐provision slave elements by entering their MAC addresses before they are deployed, take special care to not enter the MAC address of any AP. Doing so would result in their being misrepresented in network views (although it would not adversely affect how WM handles registration attempts). When BAM is licensed and in place as a subsystem of WM, access to BAM is by right‐clicking on any AP in a WM view and selecting LaunchBAM from the resulting drop‐down list of options. 4 As stated earlier in this section, these are settable in the direct management interface of each element, but to avoid error, push these four values out using element configuration templates in WM. 263
- 264. Issue 3 WM Release 4.0 User Guide May 2012 9.20.1 Managing Authentication You can configure APs in the network to require the SMs in their sectors to authenticate before they register in the APs. AP Authentication Setup Setting up an AP element for authentication includes identifying one to five authentication servers by their IP addresses. The AP ignores any drop session request, or service plan or VLAN profile change, sent from an IP address that is not in its list of authentication servers. For this reason do not insert only some authentication server IP address(es) into some APs and only others into other APs, which you may have been inclined to do for load balancing. ensure that the server in which you execute the operation is in the list of authentication servers in all APs. Whether the server in which you make an SM management change is in the list in the AP determines when that change becomes effective, as described in Table 11. Table 11: When BAM changes for subscribers are effective Effect of the Change Operation Performed in the Server If Server Is If Server Is Not Listed in the AP Listed in the AP Delete a BAM‐managed SM that is Causes the current SM session Session remains up until SM reboots or currently on the network to drop. re‐registers. Change value of any attribute in a service plan or a VLAN profile New attribute values are Old attribute values remain effective Apply a different service plan or VLAN effective immediately. until SM reboots or re‐registers. profile In a single window, you can configure any or all APs in a network to require or cease to require authentication. To do so, perform the following steps. note ............. This procedure presumes that the authentication settings template has been imported into the client application. If it has not, see Procedure 185: To import configuration templates on Page 620. Procedure 27: To configure APs for authentication management 1. In an Inventory view, click to highlight one or more APs. 2. Right‐click one of the highlighted APs and select Configuration TemplatesApply template from the drop‐down list of command options. The Apply template dialog opens. An example is shown in Figure 189. 264
- 265. WM Release 4.0 User Guide Issue 3 May 2012 Figure 189: Apply template dialog, imported AP templates 3. To configure authentication in a PMP 100 AP, click to highlight the Canopy AP;AP/ULAP Authentication Settings template. 4. If the values in this template are known to be as desired, click the Apply Now button. To view, verify, or change the values that this template will push to the AP(s), or to schedule a time and date for the push a. click the Modify Values button. note.............. If any preselected devices are incompatible with the selected template, WM pops up a warning message as follows: ..................... If all are compatible, the it opens the Modify Values dialog directly. 265
- 266. Issue 3 WM Release 4.0 User Guide May 2012 b. Check the check box of Reboot required. note ............. This feature supports the inherent interdependencies among configurable attributes. For example, if you set Network NTP Enable to Enabled, then Get NTP Server From DHCP is automatically set to Disabled; if you set Network IP Access Filter to Disabled, then Network Allowed IP Access 1 to 3 become not configurable. c. For Authentication Mode (Attribute column), select Authentication Enabled (Value column). d. For Device Configuration Source, select BAM. e. For Authentication Server 1, 2, and 3, enter the dotted IP address of each of the BAM servers. important ........... Ensure that these addresses are in the accessible range for the AP(s). For a PMP 100 AP that is running Release 9.5 or later, if one or two more Authentication Servers are to be configured (for a total of four or five), a new template is required. See Creating a Configuration Template on Page 621. f. In the On Failure block, check the check box of Continue with Next Device. g. For the template to retain these values until/unless it is modified again, click the Save button. h. To push this set of values now to the selected AP(s), click the Apply Now button. To schedule a task of pushing these values, click the Apply Later button. note ............. A case where you should later disable authentication is whenever all authentication servers whose IP addresses are listed in this window will be removed from service (for example, for a software update). If you checked Reboot Network Elements after update, then your configuration changes immediately take effect. If you did not, then your changes are delayed until the next reboot of the AP(s). 9.20.2 Managing Bandwidth BAM manages authentication, bandwidth provisioning, and the VLAN profiles of SMs. For each BAM parameter, the corresponding attribute and function in WM are identified Table 12. Table 12: Bandwidth and VLAN element attributes BAM Parameter WM Attribute Function in WM The hexadecimal string stored in both the database and the subscriber radio. This string is 32 or fewer characters, prepended Authentication Key Authentication Key with zeros if needed when the system reads it. The radio interface contains a toggle to Use This Key or Use Default Key. Sustained Uplink Bandwidth Uplink The rate that the subscriber radio(s) are replenished with credits for Data Rate Sustained Rate transmission. This imposes no restriction on the uplink. Sustained The rate at which the AP should be replenished with credits (tokens) Bandwidth Downlink Downlink Data for transmission to the subscriber radio(s). This imposes no Sustained Rate Rate restriction on the uplink. 266
- 267. WM Release 4.0 User Guide Issue 3 May 2012 BAM Parameter WM Attribute Function in WM The maximum amount of data to allow the subscriber radio to Uplink Burst Bandwidth Uplink transmit before being recharged at the Sustained Uplink Data Rate Allocation Burst Allocation with credits to transmit more. The maximum amount of data to allow the AP to transmit to the Downlink Burst Bandwidth Downlink subscriber radio(s) before the AP is replenished at the Sustained Allocation Burst Allocation Downlink Data Rate with transmission credits. Toggles whether BAM should ask License Manager for Cap 2 licenses Allow Higher Bandwidth Allow for the selected subscriber radio(s), to the extent that the licenses Bandwidth License Use are available. Low Priority Uplink Bandwidth Low The committed information rate for transmissions from the selected CIR Priority Uplink CIR subscriber radio(s) on the low‐priority channel. Bandwidth Low Low Priority The committed information rate for AP transmissions to the selected Priority Downlink Downlink CIR subscriber radio(s) on the low‐priority channel. CIR Bandwidth High Is High Priority Toggles whether the high‐priority channel is enabled for all Priority Channel Channel Enabled subscriber radios that are configured to the particular service plan. Enable High Priority Bandwidth High The committed information rate for transmissions from the selected Uplink CIR Priority Uplink CIR subscriber radio(s) on the high‐priority channel. Bandwidth High High Priority The committed information rate for AP transmissions to the selected Priority Downlink Downlink CIR subscriber radio(s) on the high‐priority channel. CIR Is CIR Feature NONE1 Enabled Toggles whether the subscriber radio(s) to which the profile is Is Dynamic VLAN Dynamic applied should (Enabled) or should not (Disabled) add to the VID Learning Allowed Learning table the VLAN IDs of upstream frames, which enter the subscriber radio(s) through the wired Ethernet interface. The type of arriving frames that the subscriber radio(s) to which the Are Tagged Only VLAN Allow Only profile is applied should tag, using the VLAN ID that is stored in the Frames Allowed Tagged Frames Untagged Ingress VID parameter. VLAN Ageing How long the subscriber radio(s) to which the profile is applied VLAN Aging Timeout Timeout should keep dynamically learned VLAN IDs. The VLAN ID that the subscriber radio(s) to which the profile is Untagged Ingress VLAN Untagged applied should use to tag frames that arrive at the subscriber radio(s) VID Ingress VID untagged. VLAN Management The VLAN ID that the subscriber radio(s) to which the profile is Management VID VID applied should share with the AP. Is VLAN Feature Toggles whether BAM sends to the selected subscriber radio(s) the VLAN Enable Enabled VLAN feature values from the particular profile. 267
- 268. Issue 3 WM Release 4.0 User Guide May 2012 BAM Parameter WM Attribute Function in WM All IDs of the VLANs in which the selected subscriber radio(s) should VLAN Ids VLAN Membership be considered a member. NOTES: To have the BAM effect of the Is CIR Feature Enabled parameter set to No, you can set the Bandwidth Low Priority Uplink CIR and Bandwidth Low Priority Downlink CIR attributes to 0 and set the High Priority Channel Enable to Disabled. Managing Bandwidth by Service Plans One important distinction in how BAM and WM send values is the capability in WM to avoid sending/overwriting a value for an attribute while sending values for the others. In BAM by contrast, you needed to send all or none of the values in a set. WM allows you to be entirely selective. To avoid sending an attribute value, leave the contents of the value in WM null (backspace over the default value, if necessary). To overwrite the attribute value to null, type in a forward space as you compose or update the service plan. To configure any of the MIR and CIR attributes, you can configure them as you would any other set of configurable attributes, by defining and applying a configuration template. This approach is good for an adjustment to an individual subscriber radio, for example. set up a service plan to be applied to a group of subscriber radios that you designate. This approach is good for establishing tiered levels of service and − adjusting those tiers over time to have bandwidth automatically added to each. − protecting your set values from being overwritten by values in a configuration template. The following table indicates the conditions under which BAM applies to an SM values from either a bandwidth service plan or a custom configuration template. To define a service plan, perform the following steps. Procedure 28: To define a service plan 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab, shown in Figure 190. Figure 190: Define Configurations tab 268
- 269. WM Release 4.0 User Guide Issue 3 May 2012 2. Select EditAdd a ConfigurationBandwidth Service Plan. BAM opens the Configuration Parameter Selection window, shown in Figure 191. note ............. The menu path that this window displays indicates where you will find this service plan when you want to apply it to selected subscriber radio(s). Figure 191: Configuration Parameter Selection dialog for a service plan 3. For Name, type in a designation that you will associate with the level of service that you will later define. 4. For Category, optionally type in a category in which BAM should show this service plan as being sorted. note ............. The category can be multilevel, in order of higher to lower, with semicolons delimiting between the levels. This is similar to inputting the submenu hierarchy for saved view criteria. 5. When you are satisfied with your entries, click OK. The configurable bandwidth parameters appear with their default values in the Define Configurations tab, shown in Figure 192. Figure 192: Configurable parameters in a service plan 269
- 270. Issue 3 WM Release 4.0 User Guide May 2012 6. For Bandwidth Allow License Use, if you want BAM to ask License Manager for Cap 2 licenses for SMs that are configured to this service plan, select Enabled. 7. For Bandwidth Uplink Sustained Rate, type in the rate at which to replenish the selected subscriber radio(s) with credits for transmission. 8. For Bandwidth Uplink Burst Allocation, type in the maximum amount of data to allow the selected subscriber radio(s) to transmit before being recharged with credits to transmit more at the Bandwidth Uplink Sustained Rate. 9. For Bandwidth Downlink Sustained Rate, type in the rate at which the AP should be replenished with credits (tokens) for transmission to the selected subscriber radio(s). 10. For Bandwidth Downlink Burst Allocation, type in the maximum amount of data to allow the AP to transmit to the selected subscriber radio(s) before the AP is replenished with transmission credits at the Bandwidth Downlink Sustained Rate. 11. For Bandwidth Low Priority Uplink CIR, type in the desired committed information rate for transmissions on the low‐priority channel by the selected subscriber radio(s). 12. For Bandwidth Low Priority Downlink CIR, type in the desired committed information rate for AP transmissions on the low‐priority channel to the selected subscriber radio(s). 13. For Bandwidth High Priority Channel Enable, if you want the high‐priority channel enabled for all subscriber radios that are configured to the particular service plan, select Enabled. 14. For Bandwidth High Priority Uplink CIR, type in the committed information rate for subscriber radio transmissions on the high‐priority channel. 15. For Bandwidth High Priority Downlink CIR, type in the committed information rate for AP transmissions to the subscriber radio(s) on the high‐priority channel. 16. When you are satisfied with the profile, click the Save Changes button. BAM opens the Confirm Update window, shown in Figure 193. Figure 193: Confirm Update window for bandwidth service plan 17. If you want the subscriber radio(s) to immediately reboot after the values in this window are written to them, check Reboot Network Elements after update. important ........... A reboot or re-registration is not required for pushing the bandwidth values for these attributes to an element, only if the server in which you are making these changes is listed as an authentication server in the AP. This is because BAM uses a special protocol, not SNMP, to push these values from either a service plan or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a service plan with an element, no parameter for which the service plan imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 18. Click OK. BAM opens the Updating Configuration window, where it documents the associated events. An example of this window is shown in Figure 194. 270
- 271. WM Release 4.0 User Guide Issue 3 May 2012 Figure 194: Updating Configuration window for a new service plan The service plan is now available to apply to selected elements. You can close this window without consequence. To apply a defined service plan, perform the following steps. Procedure 29: To apply a service plan 1. In a network view, select the subscriber radio(s) in one of the three following ways: ◦ Highlight a single element. ◦ Check the boxes of multiple elements. ◦ Highlight an element under which you want the service plan applied to all subscriber radio(s). 2. From the main menu, select EditConfigureBandwidth Service PlanServicePlanName. BAM opens a Task Attributes window, shown in Figure 195. 271
- 272. Issue 3 WM Release 4.0 User Guide May 2012 Figure 195: Task Attributes window for a service plan 3. Click the Elements tab. 4. If you selected the element(s) for which you want to configure bandwidth settings, check Selected Network Elements. If you selected an element under which you want to configure the bandwidth settings of all subscriber radio(s), check Selected Network Branches. 5. Click the General tab. 6. If you want the element(s) to immediately reboot after the values in this window are written to them, check Reboot Network Elements after update. important ........... Reboot or re-registration is not required for pushing the bandwidth values for the attributes to an element, only if the server in which you are making these changes is listed as an authentication server in the AP. This is because BAM uses a special protocol, not SNMP, to push these values from either a service plan or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a service plan with an element, no parameter for which the service plan imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 7. Click the Run Now button. 272
- 273. WM Release 4.0 User Guide Issue 3 May 2012 If you selected Reboot Network Elements after update, the elements are rebooted, and the changes are activated. If you did not select that option, the changes are not activated until the elements are later rebooted. In either case, BAM opens a Configure Element(s) window, where it documents the associated events. An example of this window is shown in Figure 196. Figure 196: Configure Element(s) window for applying a service plan You can close this window without consequence. 8. If intended licensed upgrades are failing to occur as a result of the service plan being applied, repeat this procedure but, as you do, set the attribute Bandwidth Allow License Use in the General tab to Enabled. To modify the definition of an existing service plan, perform the following steps. Procedure 30: To update a service plan 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab, shown in Figure 190 on Page 268. 2. In the left pane, select (highlight) the service plan that you want to update. BAM opens the service plan in the right pane. 3. Change the values of any attribute(s) as desired. note ............. For the meanings of the various attributes, see Procedure 28 on Page 268. 4. When you are satisfied with the changes, click Save Changes. BAM opens the Confirm Update window. An example of this window is shown in Figure 193 on Page 270. 5. If you want the element(s) to immediately reboot after the values in this window are written to them, check Reboot Network Elements after update. important ........... Reboot or re-registration is not required for pushing the bandwidth values for the attributes shown in Figure 174 to an element, only if the server in which you are making these changes is listed as an authentication server in the AP. This is because BAM uses a special protocol, not SNMP, to push these values from either a service plan or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a service plan with an element, no parameter for which the service plan imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 273
- 274. Issue 3 WM Release 4.0 User Guide May 2012 6. Click OK. BAM opens an Updating Configuration window, where it documents the associated events. You can close this window without consequence. At any time, you can dissociate an element or group of elements from a service plan. To do so, perform the following steps. Procedure 31: To remove a bandwidth service plan association 1. In a Network Browser view, select the elements for which you want to cancel the service plan association. 2. From the main menu, select EditConfigureBandwidth Service PlanRemove Bandwidth Service Plan Association. In the Define Networks tab, this option is available at EditNetwork Element OperationsConfigureBandwidth Service Plan. The element retains the last bandwidth values that were applied by the service plan, but no future changes in the service plan will change the bandwidth values in the element. If you ever want to completely remove a service plan from BAM, perform the following steps. Procedure 32: To remove a service plan 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab, shown in Figure 190 on Page 268. 2. In the left pane, select (highlight) the service plan that you want to delete. BAM opens the service plan in the right pane. 3. From the main menu, select EditDelete the Configuration. 9.20.3 Managing VLANs One important distinction in how BAM and WM send values is the capability in WM to avoid sending/overwriting a value for an attribute while sending values for the others. In BAM by contrast, you send all or none of the values in a set. WM allows you to be entirely selective. To avoid sending an attribute value, leave the contents of the value in WM null (backspace over the default value, if necessary). To overwrite the attribute value to null, type in a forward space as you compose or update the VLAN profile. To configure any of the VLAN attributes, you can configure them as you would any other set of configurable attributes, by defining and applying a configuration template. This approach is good for an adjustment to an individual SM, for example. use BAM to set up a VLAN profile to be applied to a group of SMs that you designate. This approach is good for establishing VLANs and protecting your set values from being overwritten by values in a configuration template. 274
- 275. WM Release 4.0 User Guide Issue 3 May 2012 At any time, you can dissociate an element or group of elements from a VLAN profile. The element retains the last VLAN values that were applied by the profile, but no future changes in the profile will change the VLAN values in the element. Similarly, if you remove a VLAN profile, the elements to which the profile was currently applied retain the values until or unless those are changed by a custom configuration template or another VLAN profile that is applied to them. The following caveats apply to managing VLANs from WM: VLAN must be enabled in the AP. Otherwise, applying a VLAN profile or setting VLAN values from a custom configuration template has no effect. In a VLAN profile, the VLAN Enable attribute is ignored unless the SM authenticated through the BAM subsystem. If VLAN Enable is set to Enabled in a VLAN profile or in a custom configuration template, and you switch this attribute to Disabled, this action does not turn off the VLAN feature in the subscriber radio. To do so, you must reboot the element and allow it to re‐authenticate, at which time BAM ceases to send the VLAN values that are stored in the profile or configuration. When you apply VLAN values, what set of values become effective depends on how the subscriber radio entered the network, as described in Table 13. Table 13: How VLAN settings are applied to an SM Updated VLAN Settings Entry into Corrective the Network Through Requires Action From Immediate Protocol Reboot Entered via BAM BAM VLAN profile Yes Proprietary No Re‐apply the VLAN profile (this time via SNMP). This will Later re‐entered through 2 require a reboot. Configuration 1 AP that does not require Yes SNMP No Source set in new AP authentication Entered without BAM Remember that the original WM VLAN attributes No SNMP Yes authentication values remain in the subscriber radio, even if BAM BAM VLAN profile that later manages it with new Re‐entered via BAM initially matches the Yes Proprietary No values. original settings NOTES: 1. In this case, the PMP SM re‐entered the network by registering in a new AP. 2. If this action is unacceptable for your network, either − initially apply all VLAN profiles to only elements that are behind non‐authenticating APs. This may require that you temporarily disable authentication in some APs, reboot them, apply the profile, re‐enable authentication in them, and reboot them again. Then the subscriber radios will store the values that they received from WM through SNMP. − deploy a sufficient number of BAM packs licenses so that all of your APs hold them. 275
- 276. Issue 3 WM Release 4.0 User Guide May 2012 When you apply a VLAN profile, BAM computes bandwidth based on both the values stored in the relational database and the number of SM bandwidth licenses, and sends the bandwidth service plan along with the VLAN profile to the subscriber radio(s). Operators who use only a relational database (not RADIUS also) find that the bandwidth values applied are as expected. However, operators who use both a relational database and RADIUS can sometimes find unexpected—and far from desired—values applied. This can occur in the following sequence: 1. The relational database is storing the values from the last previous authentication. 2. The operator changes the values in RADIUS, but does not reboot the involved SM. 3. The operator applies a VLAN profile to the element. 4. BAM computes bandwidth for the element, based on the original values (from Step 1), not the new values (from Step 2). 5. BAM sends the desired VLAN profile and bandwidth service plan, which is based on outdated RADIUS input, to the element. WM cannot poll the RADIUS server to detect whether any change has been made since the last authentication. By either of the following means, you can ensure that outdated input is never used in the bandwidth calculation: Discontinue using RADIUS. Reboot the involved element(s) soon after every change in RADIUS. For each BAM parameter, the corresponding attribute and function in WM are identified in Table 12 on Page 266. To define a VLAN profile, perform the following steps. Procedure 33: To define a VLAN profile 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab, shown in Figure 190 on Page 268. 2. Select EditAdd a ConfigurationVLAN Profile. BAM opens the Configuration Parameter Selection window, shown in Figure 197. note ............. The menu path that this window displays indicates where you will find this profile when you want to apply the profile to selected elements. Figure 197: Configuration Parameter Selection dialog for a VLAN profile 3. For Name, type in a designation that you will associate with the VLAN profile that you will later define. 4. For Category, optionally type in a category in which WM should show this VLAN profile as being sorted. 276
- 277. WM Release 4.0 User Guide Issue 3 May 2012 note ............. The category can be multilevel, in order of higher to lower, with semicolons delimiting between the levels. This is similar to inputting the submenu hierarchy for saved view criteria. 5. When you are satisfied with your entries, click OK. The configurable bandwidth parameters appear with their default values in the Define Configurations tab, shown in Figure 198. Figure 198: Configurable parameters in a VLAN profile 6. For VLAN Enable, specify whether BAM should (Enabled) or should not (Disabled) send to the selected subscriber radio(s) the VLAN feature values from the particular profile. 7. For VLAN Dynamic Learning, specify whether the element(s) to which the profile is applied should (Enabled) or should not (Disabled) add to the VID table the VLAN IDs of upstream frames, which enter the subscriber radio through the wired Ethernet interface. 8. For VLAN Allow Only Tagged Frames, select the type of arriving frames that the subscriber radio(s) to which the profile is applied should tag, using the VLAN ID that is stored in the Untagged Ingress VID parameter. 9. For VLAN Aging Timeout, specify how long in minutes the subscriber radio(s) to which the profile is applied should keep dynamically learned VLAN IDs. 10. For VLAN Management VID, type in the VLAN ID that the subscriber radio(s) to which the profile is applied should share with the AP. 11. For VLAN Untagged Ingress VID, type in the VLAN ID that the subscriber radio(s) to which the profile is applied should use to tag frames that arrive at the element(s) untagged. 12. For VLAN Membership, click the … ellipsis button. BAM opens the Edit VLAN Membership window. An example of this window is shown in Figure 199. 277
- 278. Issue 3 WM Release 4.0 User Guide May 2012 Figure 199: Edit VLAN Membership dialog 13. Click the Add Item button. BAM opens the Add Entry window, shown in Figure 200. Figure 200: Add Entry window 14. For each VLAN in which you want the subscriber radio(s) that have this VLAN profile to be member(s), type in the VLAN ID and click OK. The Add Entry window is removed and the Edit VLAN Membership dialog displays all current entries. note ............. Some limitations govern how many VLANs in which BAM can assign membership for the element. The number of digits that WM handles, or the number of characters that the database stores, for this attribute may be limited. However, handling and storage capabilities are sufficient for even the most complex of networks. Entries of 255 or fewer characters are supported. Larger entries can result in the BAM subsystem applying incorrect VLAN IDs. 15. If any ID was mistakenly entered, highlight the entry and click the Remove Item button. 16. When you are finished adding VLAN membership IDs, click OK in the Edit VLAN Membership window. The membership IDs for this profile are listed in the profile pane as display‐only data opposite VLAN Membership. 17. If you need to make further edits to VLAN membership, click the … ellipsis button and repeat the above steps. 18. When you are satisfied with the profile, click the Save Changes button. BAM opens the Confirm Update window, shown in Figure 201. 278
- 279. WM Release 4.0 User Guide Issue 3 May 2012 Figure 201: Confirm Update window for VLAN profile 19. If you want the element(s) to immediately reboot after the values in this window are written to them, check Reboot Network Elements after update. important ........... Reboot or re-registration is not required for pushing the VLAN values for the attributes to an element, only if the server in which you are making these changes is listed as an authentication server in the subscriber radio. This is because BAM uses a special protocol, not SNMP, to push these values from either a VLAN profile or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a VLAN profile with an element, no parameter for which the profile imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 20. Click OK. BAM opens the Updating Configuration window, where it documents the associated events. An example of this window is shown in Figure 202. Figure 202: Updating Configuration window for VLAN profile The profile is now available to apply to selected elements. You can close this window without consequence. To apply a defined VLAN profile, perform the following steps. Procedure 34: To apply a VLAN profile 1. In a network view, select the subscriber radio(s) in one of the three following ways: ◦ Highlight a single element. ◦ Check the boxes of multiple elements. ◦ Highlight an element under which you want the VLAN profile applied to all subscriber radios. 2. From the main menu, select EditConfigureVLAN ProfileVLANProfileName. BAM opens a Task Attributes window, shown in Figure 203. 279
- 280. Issue 3 WM Release 4.0 User Guide May 2012 Figure 203: Task Attributes window for applying a VLAN profile 3. Click the Elements tab. 4. If you selected the element(s) to which you want to apply the VLAN profile, check Selected Network Elements. If you selected an element under which you want the VLAN profile to apply to all subscriber radios, check Selected Network Branches. 5. Click the General tab. 6. If you want the element(s) to immediately reboot after the VLAN profile is associated with them, check Reboot Network Elements after update. important ........... Reboot or re-registration is not required for pushing the VLAN values for the attributes to an element, only if the server in which you are making these changes is listed as an authentication server in the subscriber radio. This is because BAM uses a special protocol, not SNMP, to push these values from either a VLAN profile or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a VLAN profile with an element, no parameter for which the profile imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 7. Click the Run Now button. BAM opens a Configure Element(s) window, shown in Figure 204. 280
- 281. WM Release 4.0 User Guide Issue 3 May 2012 Figure 204: Configure Element(s) dialog for applying a VLAN profile You can close this window without consequence. To modify the definition of an existing VLAN profile, perform the following steps. Procedure 35: To update a VLAN profile 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab. An example of this tab is shown in Figure 190 on Page 268. 2. In the left pane, select (highlight) the VLAN profile that you want to update. BAM opens the Configuration Parameter Selection window, shown in Figure 197 on Page 276. 3. Change the values of any attribute(s) as desired. For the meanings of the various attributes, see Procedure 33: To define a VLAN profile on Page 276. important ........... For the VLAN Membership attribute, if you remove all IDs, BAM does not send this change to the subscriber radio in run time. If you want the radio to immediately be a member of no VLANs, remove all IDs and then directly reboot the element. (Checking Reboot Network Elements after update will not work because BAM does not consider a change in VLAN membership as requiring a reboot.) 4. When you are satisfied with the changes, click Save Changes. BAM opens the Confirm Update window, shown in Figure 201 on Page 279. 5. If you want the element(s) to immediately reboot after the values in this window are written to them, check Reboot Network Elements after update. important ........... Reboot or re-registration is not required for pushing the VLAN values for the attributes to an element, only if the server in which you are making these changes is listed as an authentication server in the subscriber radio. This is because BAM uses a special protocol, not SNMP, to push these values from either a VLAN profile or a custom configuration template. However, you will not see SNMP attribute values change for the element. Once you have associated a VLAN profile with an element, no parameter for which the profile imposes a value can have its value overwritten by a custom configuration template. If you want to reboot at a later time to apply the changes, leave this box unchecked. 6. Click OK. BAM opens the Updating Configuration window, where it documents the associated events. You can close this window without consequence. 281
- 282. Issue 3 WM Release 4.0 User Guide May 2012 At any time, you can dissociate an element or group of elements from a VLAN profile. To do so, perform the following steps. Procedure 36: To remove a VLAN profile association 1. In a Network Browser view, select the elements for which you want to cancel the VLAN profile association. 2. From the main menu, select EditConfigureVLAN ProfileRemove VLAN Profile Association. In the Define Networks tab, this option is available at EditNetwork Element OperationsConfigureVLAN Profile. The element retains the last VLAN values that were applied by the VLAN profile, but no future changes in the VLAN profile will change the VLAN values in the element. If you ever want to completely remove a VLAN profile from BAM, perform the following steps. Procedure 37: To remove a VLAN profile 1. From the main menu, select NetworkDefine Configurations. BAM opens the Define Configurations tab, shown in Figure 190 on Page 268. 2. In the left pane, select (highlight) the VLAN profile that you want to delete. BAM opens the VLAN profile in the right pane. 3. From the main menu, select EditDelete the Configuration. The element retains the last VLAN values that were applied by the profile. 9.21 Running a User-defined Script WM allows users for whom Task Scheduler OperationCreate User Script Task is provisioned in the Permissions tree to point to a locally defined script and launch it, either on demand or as a scheduled task. In either case, this requires configuring the task. See Schedulable Tasks on Page 647. This feature also requires that the script exists on the server and has its mode set to executable. To authorize this feature for a user, see Task Scheduler Operation on Page 481. The Details pane of the Create Schedule Task dialog for this task type allows the user to select the script from a list of the files that are mounted in the UserScripts directory. optionally type arguments into the Enter arguments (optional) text box. launch the script on demand by clicking the Run now button or set the script to run on the specified schedule by clicking the Save button and configuring the Schedule tab. When User Script is the selection from the Select Task Type window, WM opens a Create Schedule Task interface whose Details tab is as follows. 282
- 283. WM Release 4.0 User Guide Issue 3 May 2012 Figure 205: Details for a User Script task When scripts are present under Script Name, you can click to highlight the target script, optionally type in associated arguments for the execution, and then either click the Run now button to launch the execution. click the Save button to set the script to launch as configured in the Schedule tab of this window. If no scripts are present in the directory, then WM returns the following error as a pop‐up message: To view the results of an executed script, use Procedure 199: To view results of last execution of a task on Page 675. 283
- 284. Issue 3 WM Release 4.0 User Guide May 2012 A typical results display for a successful user script execution is as follows. Figure 206: Schedulable Script Results window, example 9.22 Uploading RADIUS AAA Certificates note ............. This operation requires the specific permission Upload AAA Certificate. This is a selectable permission under Configuration in the Permissions tree hierarchy. PMP SMs and PMP 320 CPE devices support RADIUS authentication per RFC1422 by associating a .pem file with the device. This file is the SSL public key of a certificate recognized by a configured AAA (authentication, authorization, and accounting) server. WM provides certificate management with its capability to browse to the target certificate file. remove the existing certificate(s) so that no conflict results from applying the new certificate. pace the rate of certificate updates to control their volume of traffic. The command option to launch this feature is specific to the target device type. If both one or more PMP CPE device(s) and one or more PMP SM(s) are selected, then the Tools submenu is not present upon right‐click. The command options are available in an Inventory view as follows: For the PMP CPE device type, highlight the target device(s), right‐click, and then select ToolsUpload AAA Certificate to CPE from the drop‐down list of options. For the PMP SM device type, highlight the target device(s), right‐click, and then select ToolsUpload AAA Certificate to SM from the drop‐down list of options. The result of either option is the same: WM opens the Upload AAA Certificate dialog. 284
- 285. WM Release 4.0 User Guide Issue 3 May 2012 Figure 207: Upload AAA Certificate dialog, initial view To configure this dialog, perform the following steps. Procedure 38: To upload a AAA certificate 1. Refer to the user guide that documents the device type. 2. Copy the target certificate file to within file browsing reach of the client device. 3. Determine whether all of the currently highlighted devices share the same login and password for management access to the device. 4. Determine whether and how many certificates are currently applied to the highlighted devices. 5. Consider the current traffic load in the network and in the highlighted devices. 6. For Max Concurrent Updates, establish the maximum as a number that is fewer than 21. 7. Click the Browse button. 8. Browse to and select the target certificate file. 285
- 286. Issue 3 WM Release 4.0 User Guide May 2012 9. If any certificates are already applied to any of the highlighted devices, perform the following steps: a. Check to check the check box associated with Delete Existing Certificate. The specific Delete options become active. Figure 208: Upload AAA Certificate dialog, Delete Existing Certificate selected b. Click to select the appropriate radio button for Delete Certificate 1, Delete Certificate 2, or Delete Both. note ............. If certificates are at capacity in the target device, then the device response to the upload attempt depends on the device type. If the target device was a PMP 320 CPE, then the uploaded certificate replaces one of the existing certificates. If it was a PMP SM, then the rejects the upload attempt. 10. For Selected Devices Login ID, type into the text box the management login that is common among all of the highlighted devices. 11. For Selected Devices Password, type into the text box the management password that is common among all of the highlighted devices. 12. Click the Upload button. 13. When the system returns the success message, click the Close button to exit this dialog. important ........... If the target device was a PMP 320 CPE, then the uploaded certificate is immediately effective. If it was a PMP SM, then the certificate will not be effective until the next reboot of the SM. 286
- 287. WM Release 4.0 User Guide Issue 3 May 2012 9.23 Upgrading Devices On Demand note ............. Interpret all references to upgrades in this section to apply to downgrades as well. Since all upgrade packages ultimately outlive their immediate usefulness, when they do they should be stored as potential downgrade packages for instances in which you want to retreat to a previous release. WM supports both on‐demand and scheduled software upgrades, which push software (images), and firmware (logic), and boot file packages to supported Cambium Networks devices. These devices include PMP devices in FSK and OFDM series backhaul devices in PMP and PTP series CMMmicro CMM4, but not its integrated switch The success of each upgrade requires that all of the appropriate upgrade packages have already been downloaded to the client device from − http://www.cambiumnetworks.com/support/pmp/software/index.php for PMP and/or CMM devices − http://www.cambiumnetworks.com/support/ptp/software/index.php for PTP devices. and then uploaded from the client into its application. you have System Administration‐level privileges. your client device has connectivity with the WM server device. the WM server device could successfully ping the IP addresses of the devices that you intend to upgrade. you perform each of the steps that follow within this section. You can and typically will upgrade the devices in your network as a scheduled task instead of an on‐ demand launch. Scheduling allows you to run this operation without immediate staff involvement during periods when network traffic is least intensive. Although this section presumes an on‐demand launch, its instructions and descriptions are essential to orderly and efficient upgrades via schedules tasks and are not reiterated where those tasks are described (Scheduling a One‐Time or Periodic Task on Page 647). So, you will need to refer to this section as well. 9.23.1 Launching the Software Upgrade Interface When you right‐click on a device and select ToolsInstall Software Upgrades, the Software Upgrade dialog opens. important ........... Multiple instances of the Software Upgrade dialog open if you select the Install Software Upgrades option more than once. Be sure to not launch an additional dialog if an instance of it is already open. To configure the upgrade of more than one device, even from disparate specific types, highlight them all in the Inventory view before you select the Install Software Upgrades option. 287
- 288. Issue 3 WM Release 4.0 User Guide May 2012 Figure 209: Software Upgrade dialog Each of these dialog tabs includes several file transfer options and requires authentication that gives WM permission to overwrite the software image, and firmware logic, and/or boot file that currently resides in the target device(s). 9.23.2 Configuring the PMP/PTP Software Upgrade The upgrade configuration consists of five user operations: Reviewing the Relevant Pre‐Upgrade Information About the Device(s), described on Page 289. Setting the General Configuration, described on Page 289. Setting the SM Autoupdate Configuration, described on Page 290. Authenticating WM into the Device(s), described on Page 295. Selecting the Software and Firmware Packages to Apply, described on Page 295. 288
- 289. WM Release 4.0 User Guide Issue 3 May 2012 Reviewing the Relevant Pre-Upgrade Information About the Device(s) The bottom panel includes a tab (Selected for upgrade) that initially displays some relevant information about the pre‐selected device(s): Device Name, Agent, Hops, and Status. To display the remainder of the relevant information as well, click the Probe button. The information is completed for all of the listed devices. Figure 210: Selected for upgrade tab As with other tables in the WM client views, you can click and drag a column border to make the column wider or narrower. To remove a device from the list, highlight it and then click the Remove button. This bottom panel also includes a tab (Upgrade complete) that ultimately displays all of the known relevant information about the device after the upgrade has occurred. If any of the devices that the Selected for upgrade tab is listing are already at their latest versions, then you can move them by highlighting and click the Move to complete button. This can be more practical than the Remove operation, since the former ultimately results in them being displayed among the devices that operate on the latest available versions, whereas Remove leaves them unaccounted for with respect to using the Upgrade complete tab for tracking the current upgrade effort. Setting the General Configuration The Use Passive FTP for Transferring Files to Network Elements option activates passive FTP for all devices. For APs other than the PMP 320 AP, the SM Autoupdate feature causes an AP to examine the software and FPGA versions on each of its SMs command those SMs that require an upgrade to perform one. In this command, the AP directs the SM to a source for the latest software and firmware: either the AP or a TFTP server on the WM server device and within network reach of the WM server. In sectors where SM Autoupdate is not enabled, each SM must have a valid assigned IP address in order for WM to effect the upgrade. Where it is enabled, the AP acts as a virtual proxy for the upgrade. Moreover, SM Autoupdate speeds the process of upgrading a network, while not preventing an administrator from upgrading individual devices through direct IP access to them. WM initiates and terminates the SM Autoupdate mode within APs by using a UDP command. This mode remains active only until either a user with System Administration privileges disables it, manually or in another UDP command) the AP reboots. For security, an AP can accept this command from only one IP address, which is specified in the configuration of the AP. For convenience, WM automatically forces this setting in the APs to the IP address of the WM server. 289
- 290. Issue 3 WM Release 4.0 User Guide May 2012 If the Use https option is checked, then the PMP SM(s) will use a local HTTP server to access the software, boot, and FPGA image files. This works with the Use CNUT HTTP Server as File Server option described under Setting the SM Autoupdate Configuration on Page 290. If the Enable SM Autoupdate When an Access Point is Updated option is checked, then WM automatically enables SM Autoupdate on all selected APs after the direct element updates are completed. Using this option saves the user from having to separately turn on SM Autoupdate. By waiting to enable SM Autoupdate until after all selected network elements (including SMs) have been directly updated, WM avoids problems that can occur when the SM Autoupdate feature is simultaneously enabled at multiple levels of the network hierarchy. Cambium Networks delivers software images in two platform formats (big Endian and little Endian formats) to support two different CPUs running on the radios. At any given time, an AP can push the software images for only one of these platforms. Where an AP must upgrade SMs of both CPU formats, WM automatically monitors the progress of SM Autoupdate within the sector and switches the images and instructions after having pushed the image format of the majority of SMs in the sector. Setting the SM Autoupdate Configuration The SM Autoupdate Configuration block allows you to specify whether the SMs should get their upgrade files from their APs or another server. If the SMs are configured for Public Accessibility, Use TFTP File Server on the WM Server or Use CNUT HTTP Server as File Server can a better option than Use Access Point as File Server for two reasons: Either of these options offloads processing from the APs. This increases the number of simultaneous upgrades. Figure 211: SM Autoupdate Configuration tab When an AP is used as a file server, only 4 SMs associated with a particular AP can perform concurrent upgrades. When another server is used, 20 SMs per AP can perform concurrent upgrades. 290
- 291. WM Release 4.0 User Guide Issue 3 May 2012 Various firmware packages may be required, depending on whether the platform revision is P7/P8/P9, P10, or P11, and an AP can hold only one set of firmware packages at a time. Because of this, WM switches the package on the AP from one to another to ensure that all SMs on the sector get upgraded. The upgrade package attempts to determine which image is best to load onto the AP first during the SM Autoupdate sequence, but if it cannot, then it will use the top‐to‐bottom order of SM types that are listed in the box beneath the Use Access Point as File Server option. To optimize the upgrade performance on a sector, this list includes the option to Move Up or Move Down an SM Type and thereby reorder the updates by SM type. However, if you are upgrading a network of only one SM firmware type, and you see a delay in Autoupdate commencing on your network, you can switch this option setting to try to expedite it. The file server selections compare as follows: to have the APs serve the upgrade files (Use Access Point as File Server). This typically is the least favorable option, since the other options offload processing from the APs and support a greater number of simultaneous SM updates in the network. When an AP is used as a file server, only 4 SMs associated with a particular AP can perform concurrent upgrades. The update process uses the order specified under Auto Update SM Type for all devices that are flagged for updating. Update progress is monitored by FTP messaging. to use the local TFTP server. Devices that are running a release earlier than 12.0 support this option and WM uses this option to push their image files. Unlike in the standalone Network Updater tool, the Use TFTP File Server on the WM server option does not require the operator to configure an IP address for the TFTP server and the root directory where it will store the files for the SMs to pull. WM automatically configures these when this option is selected. Progress of the software upgrades is monitored by FTP messaging. When the TFTP server is used, as many as 20 SMs per AP can perform concurrent upgrades. to allow WM to act as an HTTP/HTTPS server. The Use CNUT HTTP Server as File Server option configures the software upgrade utility to allow devices to pull their image files from the HTTP/HTTPS server and to monitor upgrade status via SNMP messages. It also uses the configured Auto Update SM Type order. Release 12.0 and later devices support this option. For the Use Access Point as File Server and Use CNUT HTTP Server as File Server options, a check box is available for Order By SM Number. If you check this check box, WM counts the number of registered SMs of each Autoupdate SM Type (how many P7/P8/P9, how many P10, and how many P11), and first updates the all of the type with the most, then all of the type with the second‐most, and then all of the type with the least, ignoring the vertical order specified in the Autoupdate SM Type block. If you leave this box unchecked, it uses the order in the block. Using the HPAP Channel Bandwidth Feature note ............. Channel Bandwidth applies to only PMP 430 Series High-performance AP (HPAP) in Release 10.2 or later and the registered SMs in its sector. This feature makes settable a specific channel bandwidth to instruct the HPAP to switch its operation to, based on its current channel bandwidth. whether to proceed with or abandon the channel bandwidth switching operation in the case where the HPAP has at least one currently registered SM. 291
- 292. Issue 3 WM Release 4.0 User Guide May 2012 Figure 212: HPAP Channel Bandwidth tab Improper use of this tab can result in SMs dropping their connections to the HPAP and not being able to reconnect: The PMP 430 Series SM that operates on Release 10.0 or 10.1.1 cannot communicate with an AP that operates on Release 10.2 or later. So, under no circumstances should you upgrade any PMP 430 Series AP to Release 10.2 or later until all of its SMs have first been upgraded to that release. Similarly, a Release 10.2 or later HPAP that is set to a channel bandwidth that differs from that of its SMs cannot communicate with its SMs. So, the desired channel bandwidth should never be set in the HPAP until it is set in all of the SMs in the sector. In the case where you want to downgrade a sector from Release 10.2 or later to Release 10.1 or 10.0, you must first change the sector to the 10‐MHz channel bandwidth (SMs first) and then downgrade all of the SMs before you downgrade the HPAP. However, inherent in a sector of any considerable size is the fact that, at any given time (when you would like to cut over to the new release or later to the new channel bandwidth), some of the SMs are likely to be out of service (powered down by the end user or encountering transient RF problems, for example). To avoid or minimize trouble, you can 1. use WM to identify the out‐of‐service SMs by their red icon color. 2. use WM to display the correlated customer contact information. 3. ask the end customer to attempt to re‐establish the link before you proceed with the operation that has the hazard of stranding SMs. Proper use of this tab is as sequenced in the following example. The goal in this example case is to have an entire PMP 430 HPAP tower linked at 20‐MHz channel bandwidth, and no SMs that are unable to reconnect to the HPAP in case they go out of service for some reason after successful connection at that size of channel: 1. Plan your upgrade session to occur at a date and time when historical data suggests that the fewest SMs are not in service. 2. When the date and time arrive, send a blast to all customers, urging them to keep their sessions up. 292
- 293. WM Release 4.0 User Guide Issue 3 May 2012 3. Use alternative means to ask customers whose SMs are out of session to attempt to reconnect the RF link. 4. In an Inventory view, highlight all APs of the tower. 5. Right‐click among the highlighted APs and select ToolsInstall Software Upgrades. 6. Using Selecting the Software and Firmware Packages to Apply on Page 295 for the Select Packages operation, check only the upgrade package for Release 10.2 or later (in AES or DES) and uncheck any others that are checked in the Package List. 7. In the SM Autoupdate Configuration tab, click the Enable button for Enable/Disable APs for SM Autoupdate. All of the registered SMs in the sector are upgraded to Release 10.2 and then drop their registrations to the AP. 8. When all in‐session SMs have been upgraded, make another attempt to get any that are still running the old release upgraded. important ........... Any that you still cannot upgrade will require a truck roll before they will be able to reconnect to the HPAP. 9. In the SM Autoupdate Configuration tab, click the Disable button for Enable/Disable APs for SM Autoupdate. 10. In the Selected for Upgrade tab, click the Start button. The APs are upgraded to Release 10.2 as HPAPs, and then all of the upgraded SMs re‐register into their HPAPs. 11. Wait until all of the upgraded SMs have re‐registered. 12. Click the HPAP Channel Bandwidth tab. 13. Use this tab to set the Target Bandwidth to 20 MHz for the Current Bandwidth. Click in the Target Bandwidth column at the proper row to expose the drop‐down selection list. 14. In the Channel Bandwidth Switch Mode block of this tab, select Switch Channel Bandwidth Even if SMs are Present. 15. Click the SM Autoupdate Configuration tab. 16. Click the Autoupdate SM Channel Bandwidth button. The channel bandwidth of all connected SMs is changed to 20 MHz, and they drop their connections to their HPAPs. 17. In the SM Autoupdate Configuration tab, click the Disable button for Enable/Disable APs for SM Autoupdate. 18. In the Selected for Upgrade tab, click the Start button. The channel bandwidth of the HPAPs is changed to 20 MHz, and all sectors of the tower are operational when all of the SMs have re‐registered following the reboot, except for those SMs that were not in session during both the upgrade and the channel bandwidth change, and consequently will require a truck roll. In a second example that follows here, the goal is to downgrade an entire PMP 430 HPAP tower from Release 10.2 or later to Release 10.1.1, and have no SMs that are unable to reconnect to the HPAP: 1. Plan your downgrade session to occur at a date and time when historical data suggests that the fewest SMs are not in service. 2. When the date and time arrive, send a blast to all customers, urging them to keep their sessions up. 3. Use alternative means to ask customers whose SMs are out of session to attempt to reconnect the RF link. 293
- 294. Issue 3 WM Release 4.0 User Guide May 2012 4. In an Inventory view, highlight all HPAPs of the tower. 5. Using Selecting the Software and Firmware Packages to Apply on Page 295 for the Select Packages operation, check only the package on which all HPAPs of the tower and all of the SMs in their sectors currently operate and uncheck any others that are checked in the Package List. 6. In the HPAP Channel Bandwidth tab, click in the Target Bandwidth column at the 5.0 (MHz) Current Bandwidth row to expose the drop‐down selection list, and select 10.0 (MHz) for Target Bandwidth. 7. Click in the Target Bandwidth column at the 10.0 (MHz) Current Bandwidth row to expose the drop‐down selection list, and select 10.0 (MHz) for Target Bandwidth. 8. Click in the Target Bandwidth column at the 20.0 (MHz) Current Bandwidth row to expose the drop‐down selection list and select 10.0 (MHz) for Target Bandwidth. 9. Click the SM Autoupdate Configuration tab. 10. Click the Autoupdate SM Channel Bandwidth button. The channel bandwidth is changed to 10.0 MHz in the SMs. note ............. When this occurs, connection between the HPAPs and these SMs is dropped, except where the HPAPs were already operating in 10-MHz channel bandwidth. 11. When all in‐session SMs have been reconfigured to 10‐MHz operation, make another attempt to get any that are still operating in either the 5‐ or the 20‐MHz channel bandwidth reconfigured to 10 MHz. important ........... Any that you still cannot reconfigure to 10 MHz will require a truck roll before they will be able to reconnect to the HPAP. 12. Click the Disable button. 13. Click the Start button. The channel bandwidth is changed to 10.0 MHz in the APs. 14. Allow sufficient time for the SMs whose connections were dropped to re‐register in their APs after the reboot. 15. Using Selecting the Software and Firmware Packages to Apply on Page 295 for the Select Packages operation, check only the CANOPY101_1_Downgrade_OFDM_AESorDES.pkg3 package and uncheck any others that are checked in the Package List. 16. In the SM Autoupdate Configuration tab, click the Enable button for Enable/Disable APs for SM Autoupdate. Only the registered SMs (not the HPAPs also) are downgraded to Release 10.1.1. They will drop their connections to the HPAPs and be unable to re‐register. 17. In the SM Autoupdate Configuration tab, click the Disable button for Enable/Disable APs for SM Autoupdate. 18. In the Selected for Upgrade tab, click the Start button. This time, the HPAPs are downgraded to Release 10.1.1. The SM connections will drop and then be re‐established after the reboot, at which point all sectors of the tower will be operating on Release 10.1.1, except for those SMs that were not in session during both the channel bandwidth change and the downgrade, and consequently will require a truck roll. 294
- 295. WM Release 4.0 User Guide Issue 3 May 2012 Authenticating WM into the Device(s) If no Telnet/FTP Login ID is configured in the Credential Manager (see Setting WM Credentials for a Group of Selected Devices on Page 248), then WM uses root to authenticate into elements for an upgrade via TFTP server. When no Telnet/FTP Password is configured, WM uses a null password. These are also the default user name and password for PMP and PTP elements, with the exception of PMP 320 devices. If either or both of these are configured in the set of elements selected for the upgrade, then their reconfigured values must be configured into these fields of Credential Manager for the elements to allow WM to force the upgrade in them via TFTP. Ensure that device selection is complete in the Selected for upgrade tab. Then click the Apply settings button. If the PMP/PTP tab content is consistent and complete, then WM accepts the authentication strings. Selecting the Software and Firmware Packages to Apply note ............. Use of the upgrades feature requires ConfigurationInstall Software Upgrades allowed in the Permissions tree hierarchy. Click the Select Packages button. WM begins scanning and preparing to load the package files that are in the appropriate directory on the server. opens for the interim the pop‐up message Manually added packages are being added into the database. Please try again later. This pop‐up remains open until you dismiss it. After the scanning and loading process is complete, the Package Manager dialog will not open. Repeat the Select Packages command option (and the pop‐up dismissal, as needed) until the WM opens the Package Manager dialog with packages populated, presuming that there is at least one in that server directory. If none exist there, then the dialog opens with no files initially listed under Package Name. 295
- 296. Issue 3 WM Release 4.0 User Guide May 2012 Figure 213: Package Manager dialog, no packages Regardless of whether packages from the server loaded, you can optionally click the Add button and then browse to and select any package file from anywhere in the client file system. Repeat this as many times as required to upload all the packages from the client to the WM server. Each uploaded package is then available for any client to use for upgrades, until and unless it is removed by a client, as described below. Whenever the Select Packages command option is invoked, any file (in the Tftp directory of the server) that was not previously loaded into Package Manager is loaded into it. Figure 214: Package Manager dialog, packages added 296
- 297. WM Release 4.0 User Guide Issue 3 May 2012 The Package Info panel in the lower portion of this window provides a summary of information about the currently highlighted single package. At any time, you can check the check box of a package and click the Remove button. This both removes the package from the Package List and deletes the package from the server. Before performing the upgrade operation, WM examines each checked package and uses only the top‐most acceptable package. To save some of the time that WM would spend examining packages, you can alter the order of the packages in Package Manager by using the Move Up and Move Down buttons, which move the currently highlighted package. 9.23.3 Launching the On-Demand Software Upgrade Ensure that the information is complete and appropriate in the PMP/PTP tab. Then click the Start button. If no package has been checked in the Package List, then WM throws a specific error to that effect. Otherwise, WM begins the configured upgrade(s). During the process, if you see a need to stop it, click the Abort button. 9.23.4 Reviewing the Relevant Post-Upgrade Information About the Device(s) After performing an upgrade, WM moves the successfully upgraded device to the Upgrade complete tab in the lower panel and updates its Status and version(s) columns. leaves the device whose upgrade failed, so that it is there for further upgrade attempts. 9.23.5 Resetting Location Attributes for PTP 300 and PTP 500 Devices When devices of these types are upgraded to their v05‐00 release, any values previously configured by CSV import of their Latitude, Longitude, and Height above Ground attributes for these devices are lost, because the OIDs associated with these attributes have changed. The workaround is for operators to configure these as fully supported attributes after the upgrades to v05‐00. 297
- 299. WM Release 4.0 User Guide Issue 3 May 2012 10 Creating and Using Device Groups The Device Group feature enables you to define a static or dynamic logical group of two or more devices and assign a group name. Several WM operations may be performed on device groups, such as Apply template and Run report. The Applications tree lists each configured group under the category Device Groups. There is no limit to the number of device groups to which a device can belong. A static group membership will always consist of the same devices, except those that you specifically add to the group or specifically remove from it. Specifically, in this context, means that you mark the Name (ID) of the target device(s) by highlight and then click the buttons (Add or Remove, and then Update) to execute the addition or removal. Figure 215: Add Device window for Static Selection of a device group A dynamic group membership can automatically change as its devices cease to match its criteria or other polled devices now do, but its set of criteria for membership will not change, except if you deliberately alter the set of criteria by selecting other conditions. 299
- 300. Issue 3 WM Release 4.0 User Guide May 2012 After a group has been defined, it cannot be transformed into the other group type. For example, if you think you will need to manually add or manually exclude one or more devices from a group in the future, you should define it using the Static Selection option. If you want the membership of the new group to flex with polling results, then you should define it using the Dynamic Selection option. In a dynamic group definition, you select whether the definition will be Basic, which can apply to only the following criteria: − one required Specific Type—device specific type; for example, PMP.SM(v11.0) − zero or one Configuration Attribute with an associated operator and value to filter devices of the device specific type − zero or one Performance Attribute with an associated operator and value to filter devices of the device specific type. Figure 216: Create Device Group conditions for basic Dynamic Selection of a device group Advanced, which can apply to the following criteria: − one or more values for any or all of the following Device Properties: Device Type—for example, PMP.SM IP Address Managed Name (ID) SNMP Read Community SNMP V3 Context Name 300
- 301. WM Release 4.0 User Guide Issue 3 May 2012 SNMP V3 User Name SNMP Version Write Community Specific Type—device specific type; for example, PMP.SM(v11.0) Status Sys OID − zero or more Configuration Attributes, each with an associated operator and value to filter devices of the Device Type or Specific Type, only if one or more Device Type or Specific Type has been specified under Device Properties − zero or more Performance Attributes, each with an associated operator and value to filter devices of the Device Type, only if a Device Type has been specified under Device Properties. Figure 217: Name selections for Add Advanced Criteria of a dynamic device group 301
- 302. Issue 3 WM Release 4.0 User Guide May 2012 In Device Properties for an Advanced Dynamic Selection the Specific Type is limited to all or fewer of the specific types that fall within the selection(s) made for Device Type. For example, if you select PMP.AP and PMP.SM for Device Type… and then select Specific Type from the drop‐down list of remaining Device Properties, the selectable values include only the specific types within PMP.AP and PMP.SM: Device Type is unavailable among the Device Properties if you specify Specific Type before you attempt to select Device Type. 302
- 303. WM Release 4.0 User Guide Issue 3 May 2012 For Configuration Attributes or Performance Attributes, the Add Advanced Criteria interface allows you to select from either a list of all attributes that the full set of selected Specific Types or Device Types share in common: a list of all attributes that are valid in common for only some of the Device Types or Specific Types that the device group comprises: 303
- 304. Issue 3 WM Release 4.0 User Guide May 2012 This flexibility effectively allows you to define a group that will always be composed of all of certain types of devices and a subset of devices of other types. If you toggle back and forth, trying to decide whether to define a group by Basic or Advanced dynamic criteria, your changes in the dialog are retained until you click the Update button. If this occurs while the Basic criteria are displayed, then the conditions defined by Advanced criteria are discarded and will not apply to the dynamic group membership. Similarly, if you toggle back and forth between Static Selection and Dynamic Selection, your changes are retained until the Update. You can invoke the Device Group feature in any of the following ways: by selecting ToolsManage Device Groups from the main menu. This allows you to create a new device group or edit or delete an existing one. by right‐clicking on the name of an existing device group under InventoryDevice Groups in the Applications tree. This allows you to − monitor an Inventory view of these members in either the view panel or a separate window (Detach). − Apply template or Run report, as stated above. − launch a physical map that comprises the members of the device group. − edit or delete the specific device group. by right‐clicking on a device in an Inventory view and selecting − Add To Device Group. This allows you to add the device to an existing device group or create a new one. − Device Group Membership. If the device already belongs to one or more device groups, this allows you to view the names of the device group(s) to which it belongs. remove it from membership in one, some, or all of them. note ............. If multiple devices are highlighted before the right-click, then the membership list that results is a list of only those device groups in which all of the highlighted devices are members. 304
- 305. WM Release 4.0 User Guide Issue 3 May 2012 10.1 Creating a Dynamic Device Group To create a dynamic device group, perform the following steps. Procedure 39: To create a dynamic device group 1. In the Applications tree, right‐click InventoryDevice Groups. 2. From the drop‐down list of options, select Create Device Groups. Figure 218: Device Group Details tab of the Create Device Group dialog 3. In the Device Group Details tab of the Create Device Group dialog, type a Name for the new group. 4. Type an optional Description that will help you and others remember how this group is constituted. 5. If you want other users to be able to see and use this device group, check the Public check box. 6. Click the Devices tab. 305
- 306. Issue 3 WM Release 4.0 User Guide May 2012 Figure 219: Devices tab of the Create Device Group dialog 7. Using the guidance under Creating and Using Device Groups on Page 299, decide whether you want this group to have a Basic or an Advanced definition. 8. Using the available options, specify the Basic or Advanced criteria for dynamic group membership. 9. Optionally click the Preview button to see the list of devices that would become current members of the new group. 306
- 307. WM Release 4.0 User Guide Issue 3 May 2012 Figure 220: Devices Preview window 10. Inspect the list of devices in the Devices Preview window to ensure that the membership would be as intended. note ............. Although you can click to highlight one or more devices in this window, no options are available to exercise on these previewed devices. 11. Click OK to dismiss the Devices Preview window. 12. If you are satisfied with the criteria, click the Create button. RESULT: The Device Groups window displays all currently defined groups, indicating the user who create the group, the date on which that occurred, and whether the group is Static or Dynamic. Figure 221: Device Groups window For any Dynamic group type, when a new device is polled and matches the dynamic criteria, the new device becomes a member of the device group. When an existing device is polled and no longer matches the criteria, the existing device is dropped from membership in the device group. When a non‐member device is polled and matches the criteria, it is added to the device group. In the Applications tree and elsewhere in the WM client application, the icon is associated with each Dynamic group. 307
- 308. Issue 3 WM Release 4.0 User Guide May 2012 10.2 Modifying a Dynamic Device Group To change the criteria for an existing Dynamic group, perform the following steps. Procedure 40: To modify a dynamic device group 1. In the Applications tree, select InventoryDevice Groups. 2. Right‐click the device group name. 3. Select Device Group OperationsModify Group. Figure 222: Device Group Details tab of Edit Device Group dialog 4. In the Device Group Details tab, change the Name, Description, or Public access as desired. 5. Click the Devices tab. 6. Using the guidance under Creating and Using Device Groups on Page 299, decide whether you want this change to be a Basic or an Advanced definition. 7. Using the available options, modify the Basic or Advanced criteria for dynamic group membership. 308
- 309. WM Release 4.0 User Guide Issue 3 May 2012 Figure 223: Devices tab of Edit Device Group dialog 8. Optionally click the Preview button to see the list of devices that would become current members of the changed group definition. (See Figure 220 on Page 307.) 9. Inspect the list of devices in the Devices Preview window to ensure that the membership would be as intended. 10. Click OK to dismiss the Devices Preview window. 11. If the membership reflects your intent, click the Update button. 10.3 Creating a Static Device Group To create a static device group, perform the following steps. Procedure 41: To create a static device group 1. If all devices of a particular device type are intended members of the new device group, perform the following steps: a. Click the Device Type column in the Inventory view. b. In the Inventory view, click to highlight the target devices. c. Right‐click one of the highlighted devices. d. From the drop‐down list of options, select Add to Device Group. The Add to Device Groups window opens. 309
- 310. Issue 3 WM Release 4.0 User Guide May 2012 Figure 224: Add to Device Groups window e. Click the Create Group button. The Create Device Group dialog opens. 2. If you did not begin this procedure with Step 1, right‐click the Device Groups tree node under Inventory and select Create Device Groups from the drop‐down list of options. The Create Device Group dialog opens. 310
- 311. WM Release 4.0 User Guide Issue 3 May 2012 Figure 225: Devices tab of Create Device Group dialog 3. In the Device Group Details tab, compose a Name for the group and a Description that will help you and others remember what this group represents. 4. To allow other users to access the device group, select the Public check box. 5. Click the Devices tab. 6. Click the Static Selection radio button. 7. If you began this procedure with Step 1, move the Create Device Group window so that you can see the Name (ID) entry of most or all of the devices that you had selected in the Inventory view. 8. Click the Add button. The Add Device window opens. 311
- 312. Issue 3 WM Release 4.0 User Guide May 2012 Figure 226: Add Device window 9. Ctrl+click to highlight the Name (ID) of each device you want in the device group. Figure 227: Devices selected to add 10. Click the Add button. All of those devices are added to the Devices Selected block of the Create Device Group window. 312
- 313. WM Release 4.0 User Guide Issue 3 May 2012 Figure 228: Devices added to Devices Selected block 11. Click the Create button. The device group is added to the Applications tree, and the devices that were selected belong to the device group. (You do not need to add them in a separate operation.) In the Applications tree and elsewhere in the WM client application, the icon is associated with each static group. 313
- 314. Issue 3 WM Release 4.0 User Guide May 2012 10.4 Adding Devices to a Static Device Group Procedure 42: To add one or more devices to an existing device group 1. In the Inventory view, click to highlight the device(s) that you want to add. 2. Right‐click one of the selected devices and select Add To Device Group. The Device Groups window opens, listing all of the existing device groups. Figure 229: Add to Device Groups window 3. Click to highlight the device group. 4. Click the Add To Group button. 314
- 315. WM Release 4.0 User Guide Issue 3 May 2012 10.5 Removing Devices from a Static Device Group Procedure 43: To remove a device from a device group Either perform this set of steps: 1. In the Inventory view, right‐click the specific device group. 2. From the drop‐down list of options, select Device Group OperationsModify Group. The Edit Device Group dialog opens to its Device Group Details tab. 3. Click the Devices tab. 4. In the Devices Selected block, click to highlight the device that you want to remove from the device group. 315
- 316. Issue 3 WM Release 4.0 User Guide May 2012 5. Click the Remove button. An alert asks for confirmation. 6. Confirm the removal by clicking the Yes button. The Devices Selected block of the Edit Device Group dialog displays the list of devices that remain in the device group. or perform this set of steps: 1. In the Inventory view, right‐click the device you want to remove from the device group. 2. From the drop‐down list of command options, select Device Group Membership. 3. In the resulting Device Group Membership For Selected Device(s) window, click to highlight the correct device group in the list. important ........... This window does not expand the device group to display its members. Ensure that the target device is in fact the one that is highlighted in the Inventory view that the Device Group Membership For Selected Device(s) window overlays (shown below). 4. Click the Remove From Group button. An alert asks for confirmation. 5. Confirm the removal by clicking the Yes button. The Devices Selected block of the Edit Device Group dialog displays the list of devices that remain in the device group. 316
- 317. WM Release 4.0 User Guide Issue 3 May 2012 10.6 Adding or Removing Columns in a Device Group Window 317
- 318. Issue 3 WM Release 4.0 User Guide May 2012 10.7 Using a Device Group When you right‐click the name of the device group in the Applications tree, an Inventory view populated with only the members of that device group opens, and so does a drop‐down list that provides the following options: Physical Map. This option displays a new instance of the physical map comprised by the members of this device group. Modify Group. This option allows you to change the name or description of the device group, its access (Public or not), and allows you to add new devices or remove any member devices. Delete Group. This option allows you to delete the entire device group and all of its memberships in a single operation. Columns To View. This option opens the Select Table Columns window. See Figure 86: Select Table Columns dialog for inventory custom view on Page 134. Configuration TemplatesApply template or Delete template. See Using Configuration Templates on Page 618. ReportsConfiguration ReportsRun report or Delete Report. This option allows you to execute any previously created report. See Running a Configuration Report on Page 331 or Deleting a Configuration Report on Page 337. DetachDetach. This option allows you to handle the device group Inventory as a separate window, independent of the view panel in the client. 318
- 319. WM Release 4.0 User Guide Issue 3 May 2012 10.8 Removing a Device Group To delete a device group, perform the following steps. Procedure 44: To remove a device group 1. In the Applications tree, select AdministrationScheduled Tasks. Figure 230: Scheduled Tasks window 2. In the User field at the top of the Scheduled Tasks window, use the drop‐down list to select your user name. 3. Wait until the table contents are refreshed. 4. If any listed task is scheduled against the device group that you intend to delete, edit or delete the task. 5. In the User field at the top of the Scheduled Tasks window, use the drop‐down list to select All. 6. Use a vertical scroll to scan the list for other tasks that are scheduled against the device group that you intend to delete. 7. For any that you find, alert the owner about your intention. 8. In the Applications tree, select InventoryDevice Groups. 9. In the Device Groups window, right‐click the row of the device group that want to delete. Figure 231: Delete Group option for a device group 10. From the drop‐down list of options, select Delete Group. RESULT: The systems asks for confirmation. 319
- 320. Issue 3 WM Release 4.0 User Guide May 2012 11. If you want to proceed with the deletion, click the Yes button. If you have any doubt and want to see the definition of the group first a. click the No button. b. in the Device Groups window, right‐click the row of the device group. c. from the drop‐down list of options, select Modify Group. d. examine the definition of the group. e. if you want to proceed with the deletion 1) click the Cancel button. 2) repeat Steps 9 through 11. 320
- 321. WM Release 4.0 User Guide Issue 3 May 2012 11 Obtaining Device Configuration Information By default, WM collects polled configuration values from managed elements on a regular basis. This basis is operator configurable (see Adjusting Configuration Polling Intervals below). WM also collects this type of information on demand (see Creating and Using Device Configuration Reports on Page 323). 11.1 Adjusting Configuration Polling Intervals 11.1.1 Disabling Configuration Polling Configuration polling consumes significant server resources and burdens the network with arguably unneeded overhead traffic. Rediscovery captures the attribute values. So, separately polling for them is a redundant exercise. Where server resources and network traffic are of little concern, such as in a small network, the information under Setting Intervals for a Small Network provides guidance for adjusting the interval(s) at which WM will poll its devices for their attribute values. However, the general recommendation for most networks and strong recommendation for large networks is to disable configuration polling altogether. To disable it, from the main menu, select ToolsPolling Configuration and uncheck the Enable Configuration Polling check box. A server restart is not needed to enforce this change. 11.1.2 Setting Intervals for a Small Network From the main menu, the ToolsPolling Configuration opens the Polling Configuration dialog to its Performance Polling tab. When this dialog opens, click the Configuration Polling tab. 321
- 322. Issue 3 WM Release 4.0 User Guide May 2012 Figure 232: Polling Configuration dialog, Configuration Polling tab WM inherits the single global configuration polling setup for every device type from the value of the GlobalConfigPollingInterval tag in the file .../WM/server/conf/WibbWMSConfiguration.xml in the WM server file system. The initial (installed) value of this tag is 12 hours. If you wish, you can leave this configuration in force by not using this tab. This tab in the client interface allows you to override those configurations by setting the configuration polling via SNMP queries to occur (Enable Polling Status checked). not occur (Enable Polling Status unchecked). not occur for device types that you specify, and occur for all other device types. (See Procedure 45 below.) occur at the Global Polling Interval for all devices types. occur at intervals that you set (Polling Interval in Hours) for each device type that you deliberately Add for configuration polling interval setup, and occur at the Global Polling Interval for device types that you do not Add. (See Procedure 45 below.) To set some or all device types that you specify to be polled for configuration values at a rate different from the Global Polling Interval, perform the following steps. 322
- 323. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 45: To set configuration polling for a specific device type 1. Click the Add button associated with the Specific Type Based Polling Configuration block of the Polling Configuration dialog. The Configure Specific Type Polling dialog opens. Figure 233: Configure Specific Type Polling dialog for configuration polling 2. In the Specific Type field, use the drop‐down list to select the device type. 3. If you want to disable polling for the device type that you selected, uncheck the Enable Polling check box. 4. If you want polling of your selected device type to occur at an interval that differs from the Global Polling Interval in the previous dialog, type the number of Hours into the Polling Interval text box. The following rules apply to resetting polling intervals: The smallest accepted polling interval is 1 hour. The largest accepted polling interval is 24 hours (1440 minutes). 5. When you are finished either disabling polling or specially setting the polling interval for the selected device type, click the OK button. The device type with its newly set polling status (disabled or special interval) is displayed in the Specific Device Type Polling Configuration block of the Polling Configuration dialog. note ............. If you attempted to apply an illegal interval, the client throws a pop-up error. for a value too small: for a value too large: note ............. If you attempted to apply an interval identical to the global polling settings, the client asks for confirmation. 323
- 324. Issue 3 WM Release 4.0 User Guide May 2012 6. Back in the Polling Confirmation dialog, you can use ◦ the Remove button to return a highlighted device type to global polling treatment ◦ the Modify button to change the settings (in a dialog like that shown in Figure 268 above, but with the device type preselected and not changeable) that you previously made by the procedure. ◦ the Reset to Defaults button to restore all polling intervals for all device types to the value of the GlobalConfigPollingInterval tag in the file .../WM/server/conf/WibbWMSConfiguration.xml in the WM server file system. 11.2 Creating and Using Device Configuration Reports Reports allow you to select and view configuration parameters of discovered devices. These reports are a complement to the configuration features of WM (the Configure Device command and the configuration template features). You can use reports to verify the configuration of a device. Since these reports are about configuration parameters, they differ from performance data reports, which are described elsewhere in this guide. Some configuration parameters are not configurable (are read‐only). These parameters are not visible when you are configuring a device, but are available as part of a configuration parameter report. They are configuration parameters in that, during discovery and rediscovery, WM polls them from the device along with other configuration parameters. They are separate and different from performance data parameters, which WM polls during the more‐frequent performance data polling cycles and which retain historical values. Command options allow you to run any of a set of predefined reports create a custom report edit a configuration report save that report as a template to use for configuring other custom reports run that report upon command ultimately remove reports that no longer serve their original purposes. These command options are available through both the device‐specific menu and a right‐click on the target device in the Inventory view. 324
- 325. WM Release 4.0 User Guide Issue 3 May 2012 11.2.1 Importing Configuration Report Templates To import these configuration report templates, perform the following steps. Procedure 46: To import configuration report templates 1. In the Applications Tree, expand the Configuration node. 2. Right‐click the Configuration Report Templates sub‐node. 3. Select Template OperationsImport Report Template(s). 4. Browse to the target path where the configuration templates exist within reach of the client. (See the path quoted above, if you are browsing in the server file system.) 5. Use ◦ Ctrl+click to individually select a set of templates. ◦ Shift+click to individually select the first and last of a set of templates that are sequentially displayed in the browser, then Ctrl+click to subtract any from in between. ◦ Click to select a single template. 6. After you have highlighted (selected) all of the desired template files, click the Open button. All of the imported files will be available to any user from the Configuration Report Templates dialog upon right‐click of an element and selection of ReportsConfiguration ReportsRun Report from the drop‐down list of command options. 11.2.2 Accessing a Predefined Report on Configured Values For each supported device, WM includes a set of predefined templates that display the current values (on demand) of the configurable parameters in the selected elements. The Inventory view provides access for running these preconfigured reports. Procedure 47: To access a configuration report template 1. Right‐click to select the element from an Inventory view. 2. Select ReportsConfiguration ReportsRun Report from the resulting drop‐down list of options. 325
- 326. Issue 3 WM Release 4.0 User Guide May 2012 The Execute Configuration Report Template panel opens in the right frame, listing all of the imported reports for this device type. Figure 234: Execute Configuration Report Template panel Imported, in this context, means all of those xml templates that were deliberately copied into the user interface by the operator in the utility of the client application. Since the import requires a browse of the file system on the client device, the templates must be accessible to browsing in one of the following ways: The client device is local to the server device. In this case, the templates are available at ...Cambium/WM/server/Default Templates/Report Templates/ (the path is in the server file system). The client device is remote from the server device, but either − a network connection, authenticated where required, exists between the client and the server file system, and the operator uses that connection to browse in it. − the operator has copied the template files from the remote path quoted above to a path in the client file system and browses to this local path. No setting exists for automatically importing the predefined templates that support only the device types present in your network or the larger group that support all possible device types. To import these configuration report templates, see Importing Configuration Report Template on Page 324. 11.2.3 Creating a Configuration Report You can create a custom report by using a template to include the various device configuration parameters whose values you want to be able to view. The report creation process begins with selecting one or more devices. Since you can later run the report against any other device(s), user‐ defined device group, or all devices of a certain device type 5, the individual device that you have selected when you launch the configuration report creation utility is unimportant. 5 This would involve sorting the Inventory view by the Device Type column, and then using Shift+Click on the first and last listed among that particular device group, then right‐clicking on one of the selected devices and selecting Configuration ReportsRun Report. 326
- 327. WM Release 4.0 User Guide Issue 3 May 2012 The device type is important, since the set of parameters that you can choose from in building the report is limited to those that the device type of the selected device supports. For this reason, a report can be run against only devices that have the same device type that the report was created against. Procedure 48: To create a configuration report 1. Invoke the configuration report creation utility in either of the following ways. ◦ From the Inventory as follows: a) In the Inventory, right‐click on a device of the target type. b) From the resulting drop‐down list of options, select ReportsConfiguration ReportsCreate Report. The Create Configuration Report Template dialog opens, listing all of the available device configuration parameters that WM supports for the target device type, each selectable within an expandable and contractible category or as an individual parameter. Figure 235: Create Configuration Report Template dialog launched from Inventory ◦ From the Applications tree as follows: a) In the Inventory, click to highlight a device of the target type. b) In the Applications tree, click to expand the Configuration node. 327
- 328. Issue 3 WM Release 4.0 User Guide May 2012 c) Right‐click the Configuration Report Templates sub‐node. The Configuration Report Templates panel opens, listing all previously imported and all previously created templates. This list is filtered on the basis of agent type. d) From the drop‐down list of options, select Template OperationsCreate Report Template. The Create Configuration Report Template dialog opens with Device Type initially set to the highest alpha‐sort device type. The associated down‐arrow opens a list of all selectable agents (device types). Figure 236: Create Configuration Report Template dialog launched from Applications tree e) Use the down‐arrow to select the target Device Type. The dialog populates with all of the available device configuration parameters that WM supports for the target device type, each selectable within an expandable and contractible category or as an individual parameter. 2. For convenience, optionally use the Jump To drop‐down list to select one configurable parameter. The branch of the configurable attribute hierarchy expands. 3. Expand additional portions as you wish. 328
- 329. WM Release 4.0 User Guide Issue 3 May 2012 4. Compose a Template name that will help you distinguish this report template in the future. 5. Compose a Template description that summarizes the purpose of the report. 6. In the Include column, select (check the check box of) each parameter and/or category of parameters that you want included in the report. note ............. In the example shown in Figure 235 above, all of the parameters in the Maximum Information Rate category are automatically selected because Maximum Information Rate is selected. important ........... Although you can later choose the devices to run the report against and run the report multiple times as you select different sets of devices, you will not be able to change what fields the report includes. To see a different set of fields, you must create a different new report. Thus, it is important to ensure that you have selected all of the desired fields before you click the Create button. 7. Click the Create button. The system confirms that the report has been created. Figure 237: Success for a create report 8. Click Yes. The Select Configuration Report Data window opens. Figure 238: Select Configuration Report Data window 9. If you want WM to query the values from the database, leave Database selected for Source data from. If you want WM to poll the values from the device(s) against which the report runs, select Device. 10. Click the Run Report button. 329
- 330. Issue 3 WM Release 4.0 User Guide May 2012 Figure 239: Configuration Report View window Some delay may occur, during which WM obtains the values, and then the system opens a Configuration Report View window, which includes ◦ the parameters that you selected for the report and the values of those parameters for the device(s) against which you created the report. ◦ options to change the source (to Database or Device for Execute this report from) and/or collect the data for a different set of devices (Add Devices), in case you want to Re‐Run Report. ◦ options to process the data for viewing: − an Export utility to send the current format of the parameters and values from the report to a comma‐separated values (.csv) file. − a Print utility to send only the data through a print driver of your choice. − a Details view, which is especially useful where the report includes many columns, since it formats the data such that information hidden by the constraints of the table view is revealed. 330
- 331. WM Release 4.0 User Guide Issue 3 May 2012 Figure 240: Execute Report window provides an Export utility to send the details format to a CSV file. provides a Print utility to sent the details format through a print driver of your choice. 331
- 332. Issue 3 WM Release 4.0 User Guide May 2012 11.2.4 Running a Configuration Report To run an element configuration report from the latest data available, either polled from the device(s) at the moment when you run the report or queried from the database (updated in the last previous discovery 6 or configuration polling 7), perform the following steps. Procedure 49: To run a configuration report 1. In the Inventory view, select all devices that you want included in the report. note ............. Although more devices of more than one specific type are selectable, and selecting them would return a list of reports that together apply to all of them, the report selection window will allow you to select only one report to execute. To specify more than one device before you launch Run Report, use any of the following means: ◦ select a contiguous set of rows by holding down the Shift key and clicking on the first and last row to be deleted. Shift ◦ select multiple individual rows by holding down the Ctrl key and clicking on each of them. Ctrl ◦ in the Applications tree, expand Device Groups and right‐click on a device group. 2. Right‐click on one of the selected devices. 3. From the drop‐down list of options, select ReportsConfiguration ReportsRun Report. The system opens an Execute Report window, which lists all currently defined reports. 6 Initial discovery (see Configuring Initial Discovery on Page 404) or rediscovery (see Scheduling Rediscovery on Page 406). 7 See Adjusting Configuration Polling Intervals on Page 321. 332
- 333. WM Release 4.0 User Guide Issue 3 May 2012 Figure 241: Execute Configuration Report window 4. In the list, click to highlight the desired type of report. 5. Optionally, switch the source of report data (to query the Database or poll the Device). 6. To optionally change the set of devices for which values will be retrieved, perform the following steps: a. Click the Add Devices button. The Add Devices dialog opens. b. To add the members of a Device Group, perform the following steps: 1) Click the Load From Group button. The Device Groups window opens and lists all of the currently defined Device Groups. 2) Scroll and click, Ctrl+click, or Shift+click to highlight the row(s) of the one or more desired Device Group Names. 333
- 334. Issue 3 WM Release 4.0 User Guide May 2012 3) Click the Load button. The individual devices that are members of the selected Device Groups are loaded into the Devices Selected block of the Add Devices dialog. c. To specify individual devices by their Name (ID)s, perform the following steps: 1) Click the Add button. The Add Device window opens, listing all of the currently managed devices. 2) Scroll and click, Ctrl+click, or Shift+click to highlight the row(s) of the one or more desired individual devices. 3) Click the Add button. The selected devices are added into the Devices Selected block of the Add Devices dialog. 7. Click OK. 8. Back in the Execute Configuration Report window, click the Execute button. WM runs the report and opens the Configuration Report View window. For the meaning and usage of the options in this window, see Procedure 48: To create a configuration report, where these are already described around Figure 239 on Page 329. note ............. If the agent in any device from an Add Devices operation does not support one or more fo the OIDs being polled for the report data, then the client returns the following type of error. 9. When you are finished, dismiss the Execute Report window. 11.2.5 Finding a Configuration Report Template The client includes a utility for quickly finding a configuration report template based on strings that constitute a portion of or the entire template name, template description, or the device type that the template supports. 334
- 335. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 50: To find a configuration report template 1. In the Applications tree, click on ConfigurationConfiguration Report Templates. This opens a Configuration Report Templates view in the right panel, listing all that are currently defined. 2. From the main menu, select EditSearch. A special Search window opens to configure for matches against any of the tabular data that WM is displaying in the Configuration Report Templates window, including that which is viewable only by scrolling. Figure 242: Search window for configuration report template criteria The operation of this window is consistent with how the several other Search windows in the client operate. For an example, see Search on Page 123. Keep in mind that the scope of the search is the contents of the table, not the contents of all configuration report template files (not attributes). 11.2.6 Editing a Configuration Report Template To change the set of parameters for which a configuration report will retrieve values, perform the following steps. Procedure 51: To edit a configuration report 1. In the Inventory, right‐click on a device. 2. From the list of drop‐down options, select ReportsConfiguration ReportsEdit Report. The client opens the Execute Configuration Report window to a table view of the available report templates. 335
- 336. Issue 3 WM Release 4.0 User Guide May 2012 Figure 243: Edit Configuration Report Template window 3. Click to highlight the report that you want to edit. 4. Click OK. The client reopens the Execute Configuration Report window to a table view of the full list of parameters whose values can be retrieved for a device of the type that you right‐clicked. note ............. You cannot change the Template name, but you can change the Template description to better reflect the purpose that you intend for the template after editing it. If you want to make changes that together would render the original name confusing or inappropriate, create a new template instead of editing this one. 5. Check the Include box for each parameter you want to add to the template and uncheck it for each that you want to remove. The Reset button removes all checks from the check boxes in the Include column. 6. When you are satisfied with the set of checked parameters, click the Save button. The client confirms that the changes are saved. 336
- 337. WM Release 4.0 User Guide Issue 3 May 2012 7. To optionally run the edited report, see Running a Configuration Report below. 11.2.7 Exporting a Configuration Report Template It is possible to export a template that you created on this system to another location. You can use this function to either store a backup copy in a safe folder or share with another WM system. Procedure 52: To export a single configuration report template 1. In the Applications tree, click on ConfigurationConfiguration Report Templates. The full list of all existing templates opens in the view panel. 2. In the view panel, right‐click on the template that you want to export and select Export template. The Select Template Export Folder window opens. 3. Browse to and double‐click on the destination folder. 4. Click the Export To Folder button. 11.2.8 Exporting All Configuration Report Templates It is possible to export all templates that you created on this system to another location in a single operation. You can use this function to either store backup copies in a safe folder or share with another WM system. Procedure 53: To export all configuration report templates 1. In the Applications tree, right‐click on ConfigurationConfiguration Report Templates. This open the Reports view in the view frame, where all defined reports are listed. 2. From the drop‐down list of options, select Template OperationsExport All Report Template(s). The Select Template Export Folder window opens. 3. Browse to and double‐click on the folder where you want to store the report templates. 4. Click the Export To Folder button. 337
- 338. Issue 3 WM Release 4.0 User Guide May 2012 11.2.9 Deleting a Configuration Report To remove a report that no longer servers its original purpose, perform the following steps. Procedure 54: To delete a configuration report 1. In the Inventory view, click on a device of the type to which the target report applies. 2. From the drop‐down list of command options, select ReportsConfiguration ReportsDelete Report. The Delete Configuration Report Template window opens, listing all currently defined reports. Figure 244: Delete Report window 3. Select the report template that you want to delete. 4. If you want to review the contents of the report template before deleting it, click View. The Delete Report window displays a view of the report contents. 338
- 339. WM Release 4.0 User Guide Issue 3 May 2012 Figure 245: Delete Report window, reports contents 5. When you have confirmed the target report is the one to be deleted, click Delete. The system returns a warning message: 6. Click Yes to confirm the deletion. 339
- 340. Issue 3 WM Release 4.0 User Guide May 2012 11.3 Using Configuration Summary Reports WM includes various reports that are each preconfigured to deliver current values of important sets of configuration attributes in all devices of a particular category. The types and scopes of these reports are as follows. Table 14: Configuration Summary reports System Report Name Attribute Values Reported Device ID, Device Name AP QOS Summary Uplink Sustained Rate Downlink Sustained Rate , Uplink Burst Allocation , , Downlink Burst Allocation , Downlink Rate, roadcast Downlink CIR B Device ID, Device Name AP VLAN Configuration Enabled Local Setting Enabled , Allow Only Tagged Frames , Dynamic Learning , Ageing , Summary Timeout , Management VID PMP 320 AP QOS Index, Service Class Name, MIR, Min Reserved Rate, Tolerated Jitter, Max Latency, UL Summary Schedule Type, Data Delivery Type, Unsolicited Grant Interval, Unsolicited Poll Interval PMP 320 AP Service Flow SM MAC, SF Index, Direction, QoS Profile ID, Classification Rule ID Summary SFID , CID, BCID PMP 320 CPE Service Type , State, irection , Enabled , Scheduling Max Rate (bps), ARQ Enable , D , Flow Summary HARQ Enable, Rules Device ID, Device Name PMP Backhaul VLAN Enabled, Local Setting Enabled, Allow Only Tagged Frames, Dynamic Learning, Ageing Configuration Summary Timeout , Management VID Device ID, Device Name PTP 800 Bridge Queue Mapping Bridge, Queue Mapping GARP, Queue Mapping Table Entry Count , Configuration Summary Local Packet Filtering PTP VLAN Configuration Device ID , Device Name Summary Enabled Management Priority Allow Only Tagged Frames, anagement VID , , M Device ID, Device Name Uplink Sustained Rate Downlink Sustained Rate, plink Burst Allocation , U , SM QOS Summary Downlink Burst Allocation , Broadcast MIR, High Priority Channel Enabled High Priority , Uplink CIR, High Priority Downlink CIR, Low Priority Uplink CIR, Low Priority Downlink CIR Device ID , Device Name SM VLAN Configuration Allow Only Tagged Frames, Dynamic Learning , Ageing Timeout, Management VID, SM Summary Management Pass‐through VID, Untagged Ingress VID These reports are available on demand as preconfigured (as described in the next section). The preconfigured versions and slimmer versions of them (described under Customizing a Configuration Summary Report on Page 343) are also available through scheduled tasks. See Scheduling a One‐Time or Periodic Task on Page 647. 340
- 341. WM Release 4.0 User Guide Issue 3 May 2012 By default, configuration summary reports are accessible to every user. This access continues unless the administrator removes the permission for a specific user. As shown below in a portion of the Permissions tree hierarchy, permissions for configuration summary reports are individually assignable per report as well as categorically assignable. note ............. Access to these reports require that they are imported into a client that is networked to the WM server file system. 341
- 342. Issue 3 WM Release 4.0 User Guide May 2012 11.3.1 Using a Configuration Summary Report as Preconfigured To access any of these reports, select System Reports from the Applications tree. This opens the System Reports view in the view panel (Figure 246). Figure 246: System Reports view To open the desired report, either double‐click in the row or right‐click in it and select Execute Report. When you do, the report opens as HTML content. 342
- 343. WM Release 4.0 User Guide Issue 3 May 2012 Figure 247: SM QOS Summary You can reshape the HTML window, but not manually resize its columns or sort by their content. However, you can export the entire report as CSV for use in another application or Print the entire report on any networked printer. Running a device summary report is a schedulable task in the WM client. See Scheduling a One‐Time or Periodic Task on Page 647. As soon as you launch a configuration summary report, WM automatically saves it into a repository that contains in list from all previously launched reports that have not been deleted from the list. You can access this repository by selecting System ReportsReport Results from the Applications Tree. This list is sortable by any of its columns: Result File Name (in the format ReportName_SequentiallyAssignedReportNumber, so that within each alpha sort of report name, the order is chronological) User (who launched the report) Time (date and time) Report Name Report Type See Figure 162 on Page 226. Since the reports in the list are not searchable, and since the list of stored reports tends to grow over time, sorting is useful. Secondary sorting is achievable by sorting the secondary sort column first, then the primary sort column. To view an individual report in the Report Results view, right click on the target report and select View Report. This opens the report in the exact format and window size that the report opened in when you originally launched it. 11.3.2 Customizing a Configuration Summary Report As preconfigured, each configuration summary report runs on all devices of a category. You can customize a configuration summary report to run on a subset of those devices if you set the report as a scheduled task and filter that task for devices and optionally for their configuration and performance values. See Table 86: Configurable task prerequisites, requirements, and options on Page 648. 343
- 345. WM Release 4.0 User Guide Issue 3 May 2012 12 Monitoring Faults An event is an occurrence that is generated due to a device trap or internal WM operations and is logged in a historical database. Events can indicate progress of background processes such as discovery or problems that arise in WM or in a managed device. Most events are associated with a particular managed device, which the event refers to as the Failure Object, but some are generic. Events are logged and documented in the historical view titled Network Events. An alarm is generated when an event with Status (severity) of Critical, Major, Minor, or Warning occurs. An alarm has the same severity as the event that generated it. An alarm persists until it is cleared and then subsequently is purged from the database. An alarm that is not cleared remains in the database and continues to be listed in the alarms view unless it is individually deleted by a user. An alarms is cleared when a new event occurs that has both the same failure object as the alarm a status value clear. An alarms can also be cleared manually by the operator. The AlarmClearingPolicy automatically clears a select group of alarms that have an AlarmClear value of 3 after a configurable aging period, whose default is seven days. (See Administering a Policy on Page 603.) By default, cleared alarms are deleted after 24 hours. This is configurable in the server file system. Events are deleted from the database by an event aging policy after a configured period. The deletion period is set using the CLEAN_EVENT_INTERVAL parameter for the EventMgr process, specified in NmsProcessesBE.conf file in the WM server. The default is seven days. Events are deleted regardless of their status after the aging period. Only alarms are kept, due to their status as explained in the previous paragraph. The status of a device matches the severity of its most severe alarm. The Alarms view lists all selectable active (not yet cleared) alarms. Thus, the Alarms view is current, whereas the Network Events view is historical. Both views are dynamic—updated as new events/alarms are generated. Events particular to discovery processes are logged and documented in the historical view titled Discovery Events. See Viewing All Events Related to Discovery on Page 354. 12.1 Working with Events The Network Events view can present events in either of two ways: only those events that are associated with a specific device. all events, including device events for all devices. 345
- 346. Issue 3 WM Release 4.0 User Guide May 2012 12.1.1 Viewing All Events for a Specific Device You can launch the Network Events view to include only events that are associated with a specific device in either of the following ways: In a Inventory view, right‐click the target device and select Go ToEvents from the drop‐ down list of options. In the physical map, click the target device, click the Manage tab, and then click the Go to Events link in that tab. While viewing the events of a specific device, to switch to viewing all events in the system, click the Show All button in the upper right corner of the view frame. To view the details or alarms that are associated with an individual event, see Viewing Event Details on Page 350. Figure 248: Network Events view, one device (Source) 346
- 347. WM Release 4.0 User Guide Issue 3 May 2012 12.1.2 Viewing All Events in the System To view all events that have been generated in the system and not yet cleared, select Fault ManagementNetwork Events from the Applications tree. The unfiltered Network Events view displays in the view frame. Figure 249: Network Events view, all Sources While viewing the full set of events, you can click on any column heading to sort or reverse sort the events by the data in that column. Typical table view operations apply to this view. To view the details or alarms that are associated with an individual event, see Viewing Event Details on Page 350. 347
- 348. Issue 3 WM Release 4.0 User Guide May 2012 12.1.3 Interpreting Event Messages The following table lists various default messages generated by WM (without any configuration) along with their severities and their significance. Table 15: Preconfigured event messages and their severities Message Signifies Severity Network added to database Network Addition Info Node Added to Database Node Addition Info Interface Added to Database Interface Addition Info Port Object Added to Database Port Addition Info Port Added in disable state Port Failure Major At least one node in this Network Failure Major network is in failure state No nodes failed in this network Network Clear Clear This probably means one or Status Poll failed (Node Failure) Major more interfaces have failed Status Poll failed Status Poll failed (Interface Failure) Major No failures in this node Status Poll Clear (Node Clear) Clear Interface clear Status Poll Clear (Interface Clear) Clear Discovery Events Discovery event messages are available in the Network Events view among the other network event messages. The Discovery module in WM may generate any of the following events. Table 16: General discovery events Event Meaning Discovery started discovery has begun for the device. attribute(s) were not read means that SNMP GET timeouts resulted in some configuration attributes not due to time out error being read during discovery. This could mean that communication with the device is not consistent, or the device’s agent is not responding consistently, some OIDs being requested are not supported by the device, etc. CLEAR ‐ all attributes that indicates that after reading attributes failed due to timeout error (see other event timed out were read above), a later attempt to read the attributes succeeded, and all configuration successfully data has been read for the device. 348
- 349. WM Release 4.0 User Guide Issue 3 May 2012 Event Meaning not added since the means that a node was initially discovered but then discarded due to the fact that AdventNet license limit is the node limit for the WM license in use was already reached. To remedy the exceeded situation, one can obtain a license with a higher node count and then rediscover. Configuration differences only seen during rediscovery of an already‐discovered device – indicates that the detected during configuration of the rediscovered device does not match what the database rediscovery showed as being the configuration prior to rediscovery. Generally this will happen when the configuration of the device is changed outside of WM, e.g. via the device URL. applied profile only during initial discovery, indicates that a configuration template was applied as a profile upon completion of discovery. This happens only when WM has been explicitly set up to apply a template for a specific device type upon initial discovery. No empty sysName the check for an empty sysName property (device name) during discovery has passed. No duplicate sysName the check for a sysName property (device name) that's already in use has passed. No special characters in the check for a sysName property (device name) that has special characters in it sysName has found none. Changed sysName of the sysName was changed because it is a duplicate of one already in use. <device name> from <old Duplicates get a suffix added to them to make them unique. To make the sysName sysName> to <new on the device match the altered name WM has stored, it is necessary to use either sysName>. Please update the configuration feature in WM or the device's own management URL to change the device accordingly. the sysName on the device. The sysName must be unique in WM. When it is not unique, WM assigns a provisional sysName that is stored in only WM, not also in the device. Whenever WM rediscovers or refreshes the configuration for the device that has a provisional sysName, it will throw this error again, since the response from the device will not match it. To suppress this error, the operator must use the direct management interface of the device to write this provisional, or any other unique, sysName into the device. Removed special the sysName was changed due to special characters, which have been removed. characters from sysName To make the sysName on the device match the altered name WM has stored, it is of <mac address>. Please necessary to use either the configuration feature in WM or the device's own update the device management URL to change the sysName on the device. accordingly. Changed sysName of this means that the sysName property was changed due to having been null <device name> to <new (empty). To make the sysName on the device match the altered name WM has sysName>. Please update stored, it is necessary to use either the configuration feature in WM or the the device accordingly. device's own management URL to change the sysName on the device. 349
- 350. Issue 3 WM Release 4.0 User Guide May 2012 Table 17: Multi-agent discovery events Event Meaning Complete discovery all NEs have been successfully resolved (linked) into a multi‐agent device. Indicates of multi‐agent successful completion of multi‐agent discovery for one multi‐agent device and all of its device component NEs. Incomplete generated for an NE when it is properly part of a multi‐agent device, but was not discovery of multi‐ successfully resolved into a multi‐agent device during discovery. This event will always agent device be generated at least once for each multi‐agent device in the ordinary course of events, since one agent is always discovered before the others, and therefore has no way to resolve into a combined multi‐agent device. As a result of this event, which is a Major alarm, the NE will go into Major status, but that status should clear once other components of the multi‐agent device are discovered and they are all resolved into a multi‐agent device. Table 18: Single-agent discovery event Event Meaning Discovery finished discovery has been successfully completed for a single‐agent device. In addition to these event messages, certain more specific discovery‐related events are listed in the Discovery Events view. See Viewing All Events Related to Discovery on Page 354. CSV File Import Events WM may generate the following event for an import of a geo‐location file. Table 19: File import event Event Meaning modified the location information generated during a CSV location file import, indicating that the location of for device a device was changed by the import. 12.1.4 Viewing Event Details Event details provide information on each of the properties of an event. Procedure 55: To view event details 1. In the Applications tree, select Fault ManagementNetwork Events. 2. Right‐click to highlight the row that contains the event whose details you want to view. 3. From the drop‐down list of options, select Event Details. An Event Details window opens. 350
- 351. WM Release 4.0 User Guide Issue 3 May 2012 Figure 250: Event Details window The field of this window are described in Table 20. Table 20: Event details Property Description Index Specifies a unique ID created for each of the events that are generated. Severity Specifies the severity of the event, such as Critical, Major, Minor, Clear, Warning, Info. Message Specifies the message associated with the event. Category Specifies the category to which the event belongs. Example: Topology. Specifies the domain‐specific information which is based on physical location, functional Domain categorization, or logical categorization of the source of the event. Network Specifies the network to which the event belongs to. Specifies the node to which the event belongs to. For example, if the event is for an interface, Node the node value is specified as interface parent node. Specifies the specific entity (in the source) that has failed and is primarily responsible for the Failure Object event. See Failure Object on Page 352. 351
- 352. Issue 3 WM Release 4.0 User Guide May 2012 Property Description Source Specifies the exact source (network, node name, interface) of the event. Specifies the URL for locating the help documentation on clicking the Help button in the same Help URL dialog box. Date/Time Specifies the date and time when the event was generated. GroupName Specifies the group name to which the event belongs. If the value is 3, then this alarm is eligible to be cleared by the AlarmClearingPolicy. Any other AlarmClear value is ignored. SourceIP Specifies the IP address of the element that generated the event. Failure Object The failure object of an event is a correlation field that indicates that events are related. Most often, the failure object identifies a network element and includes a label that indicates the kind of event. This provides linkage between events for the same network element and events for the same problem. A failure object contains but is not limited to the identifier (WM name) of the network element that was affected by the event, except in the case of an event that is triggered before the element is fully discovered. In this case, the failure object may contain a string from another field, a field whose contents WM was able to read before the discovery halted. Yet another string is sometimes prepended or appended to the other contents of a failure object. For example, if the event occurred during discovery of a node whose IP address is 10.24.1.1, then the failure object may be Disc‐ 10.24.1.1. A failure object correlates events, and this results in WM suppressing events to avoid multiple copies for the same event in the same network element. If you create a failure object for a trap parser, select a value unused by other events, so that their clear events and alarms do not affect how the incoming trap is handled. You can view failure objects in either the Network Events view or the Alarms view. You can also see it, among other fields, when you right‐click on an event or alarm and select Details from the drop‐down list of options. Be aware that a clear event will clear the associated alarm on the network element, meaning the alarm that bears the same failure object. 352
- 353. WM Release 4.0 User Guide Issue 3 May 2012 12.1.5 Finding an Event The search option is useful when you are looking for events associated with a particular network element. This search operation is performed in the database and is not restricted to only the events that are currently listed in the Network Events view. Searchable criteria are severity, source (Name (ID of the device), date, message, and IP address of the device. Procedure 56: To find an event 1. Open the Event Viewer. 2. Perform any of the following: ◦ From Edit menu, select Search. ◦ From the toolbar, click Find button. ◦ Press Ctrl+F. 3. The Search dialog box is displayed. Figure 251: Search window for event criteria 4. If you want to perform a search operation that satisfies any of the matching criteria that you specify, uncheck Match All of the Above Criteria. If you need all the matching criteria to be satisfied, leave Match All of the Above Criteria checked. 5. To add criteria, click the More button. 6. For each criterion, click the down arrow associated with Severity and select from among the following properties: ◦ Severity ◦ Source ◦ Date ◦ Message ◦ IPAddress 7. For each criterion, type a search expression into the text box. 353
- 354. Issue 3 WM Release 4.0 User Guide May 2012 8. For each of these text entries, click the down arrow associated with starts with. 9. When you are finished setting the criteria for the search, click the Search button to launch it. The Network Events view is filtered to only those that satisfy the search criteria. 12.1.6 Viewing Related Alarms Since Failure Object is not one of the properties that the Search utility supports, this procedure is needed for finding all events that have the same Failure Object. This is the best way to determine what alarm was cleared by a clear event, or what clear event cleared an alarm. Procedure 57: To view other events that have the same Failure Object 1. Open the Network Events view. 2. Click a row whereby you select an event. 3. Perform any of the following procedures. ◦ From View menu, choose Alarms. ◦ Right‐click the row and choose Alarms. ◦ Press Ctrl+L. 4. The Alarms view opens with only the alarms that have the same Failure Object as the selected event does. 5. Right‐click on one of the listed alarms. 6. From the drop‐down list of options, select Events. 7. The Network Events view opens with all events that have the same Failure Object as the alarm does. 12.1.7 Viewing All Events Related to Discovery The Network Events node of the Applications tree open a view of all network events, only some of which are related to discovery, and these events are generalized as listed in the following tables under the section Interpreting Event Messages on Page 348. Typically, the messages associated with these events provide information about the results of discovery attempts but not about the causes of failed discovery events: Table 16: General discovery events on Page 348 Table 17: Multi‐agent discovery events on Page 350 Table 18: Single‐agent discovery event on Page 350 Beneath the Network Events node, WM provides the node Discovery Events, which opens a view of only events that are related to discovery attempts. An example of this view is shown in Figure 252. 354
- 355. WM Release 4.0 User Guide Issue 3 May 2012 Figure 252: Discovery Events view Throughout normal operations, this view includes events that are regularly thrown to the discoveryLogs.txt file (and to the Discovery Log panel in the Discovery Configurator), plus irregular events such as − ICMP Ping failed for device − SNMP Ping failed for device − No parent node present for Ifc specific irregular events such as failures that occur − in querying a device. − when an unsupported device type is encountered. − during rediscovery for a database‐related reason. because of device type changes made while this process is running. The privilege to view the Discovery Events table is not limited to administrator‐level users, but it is subject to custom view scope configuration. See Using Custom View Scopes on Page 459. As with the set of Network Events, the set of Discovery Events become the input data for the operations ActionsExport Events. See Exporting Events to a CSV File on Page 362. ActionsPrint. See Printing Events on Page 363. 355
- 356. Issue 3 WM Release 4.0 User Guide May 2012 12.1.8 Defining an Events Custom View You can configure an unlimited number of custom views of events. These views are filters. They are not static, but rather are updated as new events are generated in the system, even while you are examining the view. In the Applications tree, each custom view will be either a direct child of the Network Events view. For example, by beginning the view creation process with the default Network Events view in front, you can create a child view that displays events in only one specific network. the child of a child view. For example, by beginning the view creation process with that example (one network) view in front, you can create a child view that displays only critical events in that network. Another useful custom view would be to populate the Failure Object match field with the expression Disc* so that the view is limited to all discovery‐related events. Whenever the front view in the frame is a Network Events view, WM opens an event filter criteria dialog in response to selection of ViewCustom ViewsAdd Custom View from the main menu. Figure 253: Event filter custom view criteria dialog, Properties tab 356
- 357. WM Release 4.0 User Guide Issue 3 May 2012 The meanings of these fields are as follows. Table 21: Event filter custom view criteria fields Field Description Specify name for the custom view you are creating or modifying. If no value is specified in Filter View this field, the custom views are created with default values, such as Network Events0, Name Network Events1, Network Events2. Choose the parent tree node under which your custom view has to be placed in the tree from the drop‐down box. ParentName The criteria set for the parent custom view will be automatically used for child custom view. Hence, it is enough to specify only additional criteria for the child custom view. Choose the severity of the event based on which you need to filter events in your custom view from the editable drop‐down box. Severity For multiple severities, type the severity as comma separated values. For example, Major,Info. Specify all or part of a message associated with the events you want to view. Message Example: If the message is specified as Interface failure. Status poll failed., then only events with this message are displayed in the custom view. Category Specify the category of the events you want to view. For example, Topology. Specify the domain name of the events to be displayed in this view. The domain‐specific Domain information is based on physical location, or functional categorization, or logical categorization of the source of the event. Network Specify the network to which the source of the event belongs. Node Specify the name of the node based on which the events are to be filtered. Specify the name of the failed entity (that is primarily responsible for the event) based on Failed Object which the events are to be filtered. Source Specify the source of the event based on which the events are to be filtered. From The events occurred after the time specified in this field [Month, Date, Year, Hour, Min, Date/Time Sec, AM/PM] are displayed in the custom view. To The events occurred up to the time specified in this field [Month, Date, Year, Hour, Min, Date/Time Sec, AM/PM] are displayed in the custom view. 357
- 358. Issue 3 WM Release 4.0 User Guide May 2012 Field Description Specify age of the event based on which the events are to be filtered. Age of an event denotes the time lapsed since the last modification of the event in the Web NMS system. By default, the value specified is Any, whereby events of all age is displayed. Other options are: minutes, hours, days, today, and, yesterday. Example: Age in hrs > 1 displays all the events that are less than an hour old. After this Event Age custom view is created, the events are dynamically added to the view as they satisfy the criteria of being less than an hour old. In this case, the old events remain in the view. If you require to delete the old events and need to view only those currently satisfying the criteria, set the minutes in which the custom view should be refreshed in Refresh period in minutes (by default, it is set as 1 minute). On setting this, the server sends data automatically at the time interval specified. These fields supports wild card characters as follows: Table 22: Wild card characters for criteria fields Character Description Matches zero or more characters. Examples: * To view all objects that begin with test, enter test*. To view all objects that end with com, enter *com. Filters the search through the NOT operator. Examples: ! To view all objects that do not begin with test, enter !test*. To view all alarms except alarms with Critical and Major severity, enter either !war*,!cle* or !warning,!clear. Separates multiple criteria for the same property. , Example: To view objects named mems‐server1, mems‐server2, and mems‐server3, enter mems-server1,mems-server2,mems-server3. Returns objects where a single value matches many patterns. && Example: To find all objects whose names begin with abc and end with xyz, enter abc*&&*xyz*. 358
- 359. WM Release 4.0 User Guide Issue 3 May 2012 Character Description Escapes the special meaning of the character that follows. The character that follows is then literal in the search string. Example: To find a,b, enter a,b. Separates values that constitute a range. <between> Example: To find object names with a poll interval value in the range of 300 to 305, enter <between> 300 and 305. Enter the smaller number first. Values including and between the two numbers are returned. NOTES: Most of the properties listed while adding a custom view are string based. Additionally, properties to be specified as Boolean are given in drop‐down box with values all, true, and false. Selecting all removes the property from consideration. Selecting true or false yields the expected behavior. For string‐based properties, the string value is absolutely matched. For example, the string Router matches only the exact word. Words like Status and Severity are also treated as strings. For a filter of Alarms with severity critical, enter crit*. In Alarms and Events views, filtering based on time can be done by specifying the starting time and the ending time. Leave blank any field this is part of the filter criteria but not to be considered. The time required for filtering varies because it depends on the number of objects/elements, the complexity of the criteria, and the mode of storage. Custom views continue to be updated and navigable for additions/deletions until you close your session. You can either save your views or remove them. Event and Alarm filter criteria dialogs include an Additional Criteria button. If you click this button, WM opens an additional criteria dialog. See Figure 254. Figure 254: Additional custom view criteria dialog, Properties tab The More button in this window adds a single Property Name/Match Criteria correlated pair of fields each time you click it. To add three pairs, for example, click the More button three times. 359
- 360. Issue 3 WM Release 4.0 User Guide May 2012 Figure 255: Criteria dialog with three properties The Fewer button removes a pair. To specify what columns your new custom view should include, click the Select Props To View button. Figure 256: Select Table Columns dialog for event filter view note ............. These fields are read-write as well as selectable. However, you cannot reorder the columns by overwriting the default contents of their text boxes. Moreover, the system will determine the initial column arrangement regardless of the order that you see here. In the actual view, you will be able to rearrange columns for only the current view session. To specify more columns, click the Additional table columns button. 360
- 361. WM Release 4.0 User Guide Issue 3 May 2012 Figure 257: User defined table columns window The More, Fewer, and Remove buttons in this window work the same as in the Criteria Dialog window above. When you are satisfied with the construction of your table, click OK in these table columns windows. Back in the Show object with these Properties window, click the Tree Node Properties tab. Figure 258: Tree Node Properties tab for event filter custom view 361
- 362. Issue 3 WM Release 4.0 User Guide May 2012 The meanings of these fields are as follows. Table 23: Tree node properties for event filter view Field Description Frame Title Specify the name to be displayed on the title bar of the custom view. Menu File Specify the panel‐specific menu file name. If this field is left blank, the default menu is Name displayed. Specify the icon name (in WM_ Home/images directory) to use for the custom view. This Icon File icon is visible in the tree as well as in the title bar of the custom view. Table Specify the file name of the menu used to display a contextual menu for the objects Popup displayed in the table of the new custom view. Menu Tree Popup Specify the file name of the menu used to display a contextual menu for the new custom Menu view node in the Navigation tree. Specify the position of the custom view in relation to previously added views. If this field is Node Index left blank, the view will be appended to the end of the current list of custom views. When you are satisfied with the view filter that you have constructed, click the Apply Filter button. See also the following other sections of this guide: Modifying a Custom View on Page 91 Renaming a Custom View on Page 91 Resizing Columns in a Custom View on Page 91 Removing a Custom View on Page 92 12.1.9 Exporting Events to a CSV File The Export Events option can be used to save the Event Custom View data as a CSV (comma‐ separated values) file in the WM server. An option is provided to export either all of the data that marches the Custom View criteria only the data of the current scrollable Custom View page. 362
- 363. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 58: To export events 1. Either ◦ from the main menu, select ActionsExport Events. ◦ press Ctrl+Shift+E. The Export Data dialog box is displayed. Figure 259: Export Data dialog 2. Select the desired option from the radio buttons: Export Entire Custom View Data or Export Displayed Data. 3. Enter the file name in File name field. 4. Click Export. A status message is displayed. The exported custom view data file is saved in the WM_Home/server directory, as shown in the following example from MS‐Excel. 12.1.10 Printing Events If a printer is both connected to the WM server device and configured in WM for printing, then you can send the currently viewed list of events to that printer from the client. Procedure 59: To print events to the server printer 1. Perform any of the following: ◦ From the main menu, select ActionsPrint. ◦ In the toolbar, click the Print button. ◦ Press Ctrl+P. 363
- 364. Issue 3 WM Release 4.0 User Guide May 2012 2. If the system returns either the following error or a TimedOutException, inform the administrator of the WM server file system: tip ................ You can customize the Event Viewer by adding or removing columns using the Custom View options, order the events by sorting, or by creating new custom views. See also Resizing Columns in a Custom View no Page 91. After customization, you may want to use the print option to get a printed version of your customized view. 12.2 Handling Alarms The Alarms view can present alarms in either of two ways: only those alarms that are associated with a specific device. all alarms, including device alarms for all devices. Alarms views include an Owner column. For any picked alarm, the owner is shown. For any unpicked alarm, there is no entry in this column. So, a glance down, or a sort of, this column reveals the alarms that still require at least initial attention (picking). See Picking Up / Unpicking an Alarm on Page 368. note ............. To limit the number of minor alarms for Authentication failure triggered by rediscovery with multiple default read community strings, see the workarounds described in Table 40: SNMP configuration parameters on Page 412. 12.2.1 Viewing All Alarms for a Specific Device To view only alarms that are associated with the specific device, you can either type a distinctive portion of the IP address into the Search text box above the Applications tree. In the Results tab, click the number link (2 in the example below) next to the Alarms heading: 364
- 365. WM Release 4.0 User Guide Issue 3 May 2012 right‐click the device and select Go ToAlarms. In either case, an Alarms view opens to the alarms of only that device. Figure 260: Alarms view, one device (IPAddress) In a more circuitous flow that can be advantageous, you can select Go ToPhysical Map instead. In the map, where you can see from icon colors the health of devices that are in link with the target device, right‐click the target and select ManageAlarms. While viewing the alarms of a specific device, to switch to viewing all alarms in the system, click the Show All button in the upper right corner of the view frame. To view the details or events that are associated with an individual alarm, see Viewing Related Events on Page 368. 12.2.2 Viewing All Alarms in the System To view all alarms that have been generated in the system, select Fault ManagementAlarms from the Applications tree. The unfiltered Alarms view displays in the view frame. 365
- 366. Issue 3 WM Release 4.0 User Guide May 2012 Figure 261: Alarms view, all devices (all IPAddresses) While viewing the full set of alarms, you can click on any column heading to sort or reverse sort the events by the data in that column. Typical table view operations apply to this view. To view the details or events that are associated with an individual alarm, see Viewing Related Events on Page 368. 12.2.3 Viewing Alarm Details Alarm details provide information on each of the properties of an alarm. Procedure 60: To view alarm details 1. Open the Alarms view. 2. Perform any of the following: ◦ Click a row in the table and from the main menu, select Alarm Details. ◦ Right‐click a row in the table and select Details from the drop‐down list of options. ◦ Click a row in the table and press Alt+D. ◦ Double‐click a row in the table. The Alarms details for Source window opens, displaying all information that is currently available about the alarm. 366
- 367. WM Release 4.0 User Guide Issue 3 May 2012 Figure 262: Alarms details window For information on each of the properties explained in this dialog box, refer to Table 24. Table 24: Alarm details properties Property Description Message Specifies the message associated with the alarm. Specifies the specific entity (in the source) that has failed and is primarily Failure object responsible for the alarm. Source Specifies the source of the alarm. Owner Specifies the owner associated with the alarm. Category Specifies the category to which the alarm belongs. Created Specifies the date and time when the alarm was created. Modified Specifies the date and time when the alarm was last modified. Group Specifies the group name to which the alarm belongs. 367
- 368. Issue 3 WM Release 4.0 User Guide May 2012 Property Description Specifies the current severity of the alarm, such as Critical, Major, Minor, Severity Warning. Specifies the previous severity of the alarm. For example, if the alarm is of Previous severity Clear severity, this value might be Major, indicating that a Clear event was associated with and cleared an earlier Major alarm. Specifies other alarms belonging to the same group. Other alarms in this group Double‐click alarms in this field to view its details. tip ................ To instantly update the alarm details, click the Refresh button in this window. 12.2.4 Searching Alarms The procedure to search alarms is the same as explained in Finding an Event on Page 353. 12.2.5 Viewing Related Events Procedure 61: To view related events 1. Perform any of the following: ◦ From the main menu, select ViewGo ToEvents. ◦ Right‐click the row and select Go ToEvents from the drop‐down list. ◦ Click the target alarm and press Ctrl+E. A Network Events view opens with only events that have the same Failure Object as the selected alarm. 12.2.6 Picking Up / Unpicking an Alarm Pick Up is a mechanism that helps in assigning a particular alarm/fault of a device to a work group or user. When an alarm is picked up, but not cleared, it indicates that work on resolving the alarm is in progress but not yet completed. It is also possible to Unpick an Alarm that has already been assigned to a user or work group. An alarm annotation entry is entered with the name of the user who has picked up or unpicked the alarm and the time it was performed. Procedure 62: To pick up an alarm from the Alarms view 1. Click the row to select the alarm. 2. From the main menu, select EditPick Up / UnPick, or press Ctrl+U. The alarm sorts to the bottom of the Alarms view list and has your username in its Owner column entry. 368
- 369. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 63: To pick up an alarm from the Alarms details dialog 1. Click the row to select the alarm. 2. From the main menu, select ViewAlarm Details, or press Alt+D. The Alarms details for Source dialog opens. 3. Click the Pick Up button. The Owner box in the window is populated with your username and the Annotations box includes a comment for Picked up, with the associated date and time and your username. Figure 263: Owner and Annotation in Alarm detail Procedure 64: To unpick an alarm from the Alarms view important ........... In the first step, ensure that you select the intended alarm and that it has already been picked up. 1. Click the row to select the alarm. 2. From the main menu, select EditPick Up / UnPick, or press Ctrl+U. Procedure 65: To unpick an alarm from the Alarm details dialog 1. Click the row to select the alarm. 2. From the main menu, select ViewAlarm Details, or press Alt+D. The Alarm details for Source dialog opens. 369
- 370. Issue 3 WM Release 4.0 User Guide May 2012 3. Click the UnPick button. Your username is removed from the Owner box in the window, and a comment for Unpicked is added to the Annotations box, with the associated date and time and your username. 12.2.7 Adding Comments to an Alarm It is important to track any action you have taken to fix an alarm or any new information you have gathered about the alarm. You can use the Annotate option to add notes to the alarm for future reference. For example, you can enter the solution for a problem that you resolved, using the Annotate option. This may enable other users to solve the same problem in the future with less effort, after having read your annotation, or may be used to review the remedy applied to the alarm. Procedure 66: To add comments to an alarm 1. Click a row whereby you select the alarm. 2. From the main menu, select ViewAlarm Details, or press Alt+D. The Alarm details for Source window opens. important ........... Review the alarm to ensure that it is the intended alarm. 3. Click Annotate button. The SMF Add Notes Dialog opens. 4. Type your comments into the text field. 5. Click the Update button. You can view your comment in the read‐only Annotations field back in the Alarm details for Source window. 370
- 371. WM Release 4.0 User Guide Issue 3 May 2012 12.2.8 Viewing Alarm History The history of an alarm provides complete information on its status, for example including when it was added and updated. When an alarm is generated, the Alarms view displays the current status of the alarm. When the problem that led to the alarm has been fixed, an alarm with clear severity updates the one with greater severity. Procedure 67: To view the history of an alarm 1. Click the row to select the alarm. 2. From the main menu, select ViewAlarm Details, or press Alt+D. The Alarm details for Source dialog opens. 3. Click the View History button. The Annotations for this alarm box converts to the History for this alarm box, which displays the history of that alarm, from first last alarm (for example, the time at which the problem occurred, the fix time, and severity change). This is the history of events that led to the current status of the alarm. Keep in mind that a clear event will clear an alarm only if its Failure Object matches. 12.2.9 Viewing Both Annotation and History of an Alarm Procedure 68: To view both annotation and history of an alarm 1. Click the row to select the alarm. 2. From the main menu, select ViewAlarm Details, or press Alt+D. The Alarm details for Source dialog opens. 3. Click the Merge button. The bottom box converts to the Merged history and annotations for this alarm box. 371
- 372. Issue 3 WM Release 4.0 User Guide May 2012 12.2.10 Defining an Alarms Custom View You can configure an unlimited number of custom views of alarms. These views are filters. They are not static, but rather are updated as new alarms are generated in the system, even while you are examining the view. Whenever the front view in the frame is Alarms, WM opens an alarm filter criteria dialog in response to selection of ViewCustom ViewsAdd Custom View from the main menu. See Figure 264. Figure 264: Alarm filter custom view criteria, Properties tab 372
- 373. WM Release 4.0 User Guide Issue 3 May 2012 The meanings of these fields are as follows. Table 25: Alarm filter custom view criteria fields Field Description Specify name for the custom view you are creating or modifying. If no value is Filter View Name specified in this field, default values, such as Alarms0, Alarms1, Alarms2 are created. Choose the parent tree node under which your custom view has to be placed in the tree from the drop‐down box. ParentName The criteria set for the parent custom view will be automatically used for child custom view. Hence, it is enough to specify only additional criteria for the child custom view. Choose the severity of the alarm based on which you need to filter alarms in your custom view from the editable drop‐down box. Severity tip…………………For multiple severities, type the severity as comma separated values. For example, Major,Minor. In the drop‐down list, choose the previous severity of the alarms you want to view from the editable drop‐down box. For example, if you want to view alarms that Previous severity were previously minor and then became critical, select Minor is this field. tip…………………For multiple severities, type the severity as comma separated values. For example, Major,Minor. Specify the name of the owner with whom the alarm is associated. tip…………………To create a custom view for alarms that are un-owned by any user, set the value as null. For multiple Owner owners, specify owner names as comma separated values. Example: If the value is set as "Ed", then only the alarms owned by "Ed" are displayed in the custom view. Category Specify the category of the alarms you want to view. For example, Topology. Specify the group based on which the alarms are to be filtered. Group Example: If the group is specified as it‐test, then only alarms forming a part of this group id are displayed in custom view. Specify all or part of a message associated with the alarms you want to view in the created custom view. Message Example: If the message is specified as Node Clear., then only alarms with this message are displayed in the custom view. Specify the name of the failed entity (that is primarily responsible for the alarm) Failure Object based on which the alarms are to be filtered. Source Specify the source of the alarm based on which the alarms are to be filtered. From Date/Time The alarms modified after the time specified in this field [Month, Date, Year, Hour, (modified) Min, Sec, AM/PM] are displayed in the custom view. 373
- 374. Issue 3 WM Release 4.0 User Guide May 2012 Field Description To Date/Time The alarms modified up to the time specified in this field [Month, Date, Year, Hour, (modified) Min, Sec, AM/PM] are displayed in the custom view. From Date/Time The alarms generated after the time specified in this field [Month, Date, Year, Hour, (created) Min, Sec, AM/PM] are displayed in the custom view. To Date/Time The alarms generated up to the time specified in this field [Month, Date, Year, Hour, (created) Min, Sec, AM/PM] are displayed in the custom view. Choose the mode in which you need to group the alarms in a custom view from the drop‐down box. max – the alarms of maximum severity are grouped and displayed at the GroupViewMode beginning of the list. latest – the newest alarms are grouped and displayed at the beginning of the list. none – the alarms are not grouped. Specify age of the alarm based on which the alarms are to be filtered. Age of an alarm denotes the time lapsed since the last modification of the alarm in the Web NMS system. By default, the value specified is Any, whereby alarms of all age is displayed. Other options are: minutes, hours, days, today, and, yesterday. Alarm age Example: Age in hrs > 1 displays all the alarms that are less than an hour old. After (modified time) this custom view is created, the alarms are dynamically added to the view as they satisfy the criteria of being less than an hour old. In this case, the old alarms remain in the view. If you require to delete the old alarms and need to view only those currently satisfying the criteria, set the minutes in which the custom view should be refreshed in Refresh period in minutes (by default, it is set as 1 minute). On setting this, the server sends data automatically at the time interval specified. Event and Alarm filter criteria dialogs include an Additional Criteria button. If you click this button, WM opens an additional criteria dialog. See Figure 254 on Page 359. The More button in this window adds a single Property Name/Match Criteria correlated pair of fields each time you click it. To add three pairs, for example, click the More button three times. The Fewer button removes a pair. To specify what columns your new custom view should include, click the Select Props To View button. 374
- 375. WM Release 4.0 User Guide Issue 3 May 2012 Figure 265: Select Table Columns dialog for alarm filter view note ............. These fields are read-write as well as selectable. However, you cannot reorder the columns by overwriting the default contents of their text boxes. Moreover, the system will determine the initial column arrangement regardless of the order that you see here. In the actual view, you will be able to rearrange columns for only the current view session. To specify more columns, click the Additional table columns button. The More, Fewer, and Remove buttons in the resulting User defined table columns window work the same as in the Criteria Dialog window. When you are satisfied with the construction of your table, click OK in these table columns windows. Back in the Show object with these Properties window, click the Tree Node Properties tab. 375
- 376. Issue 3 WM Release 4.0 User Guide May 2012 Figure 266: Tree Node Properties tab for alarm filter custom view The meaning of these fields are the same as those described in Table 23: Tree node properties for event filter view on Page 362. When you are satisfied with the view filter that you have constructed, click the Apply Filter button. See also the following other sections of this guide: Modifying a Custom View on Page 91 Renaming a Custom View on Page 91 Resizing Columns in a Custom View on Page 91 Removing a Custom View on Page 92 12.2.11 Saving Alarms The procedure to save alarms is the same as explained in Exporting Events to a CSV File on Page 362. 376
- 377. WM Release 4.0 User Guide Issue 3 May 2012 12.2.12 Exporting Alarms The procedure to export alarms is the same as explained in Exporting Events on Page 362. 12.2.13 Printing Alarms The procedure to print alarms is the same as explained in Printing Events on Page 363. 12.2.14 Clearing an Alarm Some alarms automatically clear when the condition that caused the alarm ends (for example, when a device was temporarily off‐line due to a power outage, but power is now restored and the unreachable condition clears without intervention. Other alarms require manual clearing. Clearing these may indicate that work has been done, that diagnostics have been performed, or that the condition that caused the alarm is deemed inconsequential. For example, sometimes the agent sends a trap when there is a crisis and does not send a trap when that crisis is resolved. In this scenario, you may want to clear the alarm. Procedure 69: To clear a triggered alarm 1. In the Applications tree, select Fault ManagementAlarms. 2. In the Alarms view, click to highlight the alarm that you want to clear. 3. From the main menu, select EditClear, or press Ctrl+L. 12.2.15 Deleting an Alarm See Deleting an Alarm on Page 534. 377
- 379. WM Release 4.0 User Guide Issue 3 May 2012 13 Monitoring Performance WM monitors the performance of your network by periodically collecting performance data based on various factors, such as number of bytes of data received/sent over a period by a particular interface of a device and the current bandwidth in bits per second for the interface. After discovery, WM begins to collect data from each of the devices in the network and add it to the database. From that point forward, data collection occurs on a configured, regular basis. (See the next section.) WM refers to the performance data collected from a device in the network as statistics. You can view performance data using not only the table format in the view frame, but also graphs and reports. The set of performance data statistics that WM collects for a device is determined during discovery by the device definition template for the device type. This template file resides in the WM server file system. Practically all performance statistics available from each device are collected by default. 13.1 Adjusting the Performance Polling Intervals From the main menu, the ToolsPolling Configuration opens the Polling Configuration dialog to its Performance Polling tab. Figure 267: Polling Configuration dialog, Performance Polling tab 379
- 380. Issue 3 WM Release 4.0 User Guide May 2012 To avoid polling traffic congestion throughout the network, WM defaults to a 15‐minute SNMP statistics polling interval to get values that the network element‐level dashboard and the physical map require, but disables performance polling for all other attributes (Others). has an initial configured interval of 12 hours for Others, for all and for each specific device type. If you wish, you can leave this configuration in force by not using this tab in the client interface. However, this tab allows you to set performance polling of some or all of these other attributes to occur for all device types (Enable checked for Others in this tab). This setting can cause congestion, especially in large networks, so is not recommended as a permanent configuration. not occur for any device types (Enable returned to unchecked for Others in this tab). occur at a user‐configured interval for each specific device types whose Others box is checked in a Configure Specific Type Polling dialog (See Procedure 70 below.) important ........... If you manage a number of devices that approaches the maximum WM inventory count, do not reduce polling intervals from their default values, and consider increasing the intervals for Dashboard and PhysicalMap polling. If you enable Others, then WM will allow you to optionally disable polling for PhysicalMap or Reports but will not allow you to disable polling for Dashboard. If you attempt to do so, the client returns the following error: To set some or all device types that you specify to be polled for values that the network element‐level dashboard and the physical map do not require, perform the following steps. Procedure 70: To set performance polling of a specific device type for its extraneous values 1. Click the Add button associated with the Specific Type Based Polling Configuration block of the Polling Configuration dialog. The Configure Specific Type Polling dialog opens. 380
- 381. WM Release 4.0 User Guide Issue 3 May 2012 Figure 268: Configure Specific Type Polling dialog for performance polling 2. In the Specific Type field, use the drop‐down list to select the specific device type. 3. If you want to disable any polling group (Dashboard, Reports, PhysicalMap, or Others) for the device type that you selected, uncheck the Enable check box. 4. If you want polling of your selected device type for any polling group to occur at an interval that differs from the current setting, check the Enable check box if it is not already checked, double‐click the Interval field, type the number of minutes or hours into the Interval text box, and use the Unit drop‐down list as needed to select Minutes or Hours. The following rules apply to resetting polling intervals: The smallest accepted polling interval is 1 minute. The largest accepted polling interval is 24 hours (1440 minutes). 5. When you are finished either disabling polling or specially setting the polling interval for the selected device type, click the OK button. The device type with its newly set polling status (disabled or special interval) is displayed in the Specific Type Based Polling Configuration block of the Polling Configuration dialog. note ............. If you attempted to apply an illegal interval, the client throws a pop-up error. for a value too small: for a value too large: note ............. If you attempted to apply an interval identical to the global polling settings, the client asks for confirmation. 381
- 382. Issue 3 WM Release 4.0 User Guide May 2012 6. Back in the Polling Confirmation dialog, you can use ◦ the Remove button to return a highlighted device type to global polling treatment ◦ the Modify button to change the settings (in a dialog like that shown in Figure 268 above, but with the device type preselected and not changeable) that you previously made by the procedure. ◦ the Reset to Defaults button to restore all polling intervals for all device types to their defaults. 13.2 List of Available Performance Statistics (Configured Collection) WM collects data from a device based on the statistics that are defined for each device in the network. This section provides information on viewing those statistics. Procedure 71: To view performance data collection details 1. In the Applications tree, select PerformanceConfigured Collection. The Configured Collection view opens in the view frame. Figure 269: Configured Collection panel 382
- 383. WM Release 4.0 User Guide Issue 3 May 2012 The Hosts column of this view displays the devices available for data collection in the network. The name displayed in the Hosts column is the same as in the Device Name column of the Inventory view. 2. Click a host for which you want to view data collection details (statistics). The data for the selected host is displayed in the next column as a table. Each row of performance data represents one performance data Statistic (as shown in Figure 269 above). that is collected at regular intervals. For a definition each column, see Table 26. Table 26: Configured Collection properties Property Description A string to identify the statistic. The three categories for statistics are Node, Interface, and Multiple (indicated by the icon). Statistic Name The rows are highlighted in green to indicate that data is being collected for those devices. If data collection for a device is temporarily disabled, then that specific row is depicted in blue. Poll Id A unique number generated automatically and associated with each Statistic. DNS Name Host name (device name) with which this Statistic is associated. A unique identification number of the device interface from which data about Data Identifier the device is to be collected. For SNMP polling, the SNMP OID. The SNMP v1/v2 Community String to be used when sending the SNMP request Community for collecting the Statistic. The interval at which data should be collected for the Statistic. For example, the Interval value 600 indicates that after every 600 seconds, data has to be collected. Specifies whether data collection for the selected device is active or not. The Active possible values are true or false. If it is false, data collection is not performed for that device. Multiple Specifies the type used to poll columnar value of the tables. Based on the types of statistics in the setup configuration, WM collects data automatically and stores it in the database. Data collected per day is stored separately: the data for each day is stored in separate database tables. The current date is appended to the table name. 3. To view the object details of a statistic, double‐click a row. The ObjectDetails dialog is displayed. The object details of a statistic describe how it is collected from the device. To see the collected values, you will use the Plot feature as described below. tip ................ Next to the statistic name an icon is displayed indicating the category of the statistic. There are three categories: node (with a single branch and leaf as its icon), multiple (with a triple branch icon), and interface. Nodes have one value, whereas multiple statistics can return more than one value per collection cycle (for example, when the statistic is a column in an SNMP table. When the statistic name is highlighted in green, data is scheduled to be collected for that statistic; if the name is highlighted in blue, then data collection for that statistic has been disabled. 383
- 384. Issue 3 WM Release 4.0 User Guide May 2012 4. Right‐click an entry in the table and select Reports or Plot from the drop‐down menu. The Plot option supports graphs to display of both Collected Statistics and Current Statistics. 13.3 Performance Data Viewing Alternatives WM provides multiple ways to view the values of a statistic: running values beginning now (Current Statistic) a history of values collected over a specified length of time (Collected Statistic) an overview of historical values (Report) WM handles current and historical performance data differently in some respects. The differences are described in the following table. Table 27: Differentiating Current and Historical Data Current Performance Data Historical Performance Data (Current Statistic) (Collected Statistic) WM collects current performance data on demand, at very short intervals, to provide a view of the WM automatically collects data from devices in a predefined values of a statistic as they change over short time interval and stores it in the database. This data is called periods. WM displays the results in a continuously historical performance data. You can view this data using updated strip chart or other optional displays. The graphs as well as reports. data collected for the current statistic feature is not stored in the database. Collected performance data when displayed in Current performance data when viewed in graphs/reports is not updated or the plotting does not occur graph/tables are updated (based on predefined as you view it. You need to reopen the graph or click Plot interval) as you view it. Chart time and again to view updated data. The following table summarizes the formats that these alternatives provide. Table 28: Alternatives for viewing the values of a statistic Data Format Command Type Graph Style Options See Page Option Table Line Area Bar Scatter XYstep Current Current Statistic 385 Historical Collected Statistic 386 384
- 385. WM Release 4.0 User Guide Issue 3 May 2012 13.3.1 Viewing a Current Performance Statistic The current view of a performance statistic is useful for troubleshooting, when you want to gather the data on demand and monitor it in real time for a while. To launch the current graph viewer, right‐ click on the target statistic in the Configured Collection view and select PlotCurrent Statistic from the drop‐down list of options. When the Current statistics window opens, the graph requires about 30 seconds as the first poll goes out and the response is received, and then begins to plot freshly collected data. In the upper left, you are able to drive up or down the polling interval, but you will typically find the default 15‐second interval sufficient. The interval that you set here has no effect on any other interval in the system. To change the interval, click the Stop Poller icon, use the up or down arrow to change the number of seconds for the Polling Interval and then click the Start Poller icon. Figure 270: Current statistics window At the end of each interval, WM plots a new data point. The graph style options for this view are summarized in Table 28 on Page 384. This view supports zooming, auto‐ranging, printing, and saving as a PNG file. These options are available through a right‐click anywhere in the graph area. 385
- 386. Issue 3 WM Release 4.0 User Guide May 2012 note ............. If the graph displays only a zero value for a count type of statistic, this is because a constant value was received from the agent as a result of the first two observations. The difference is zero, and this is shown. This scenario can happen as the saveAbsolutes property value of a statistic is set to false by default, causing the displayed value to be the difference between successively collected values. If the saveAbsolutes value was set to true, then the absolute value would be plotted and a zero value would not occur often. The following messages are possible when you launch the Current statistics window. Table 29: Possible messages in a current performance data graph Message Reason Fetching Data.... The data is being collected from the device. No Response from agent This is no response from the agent running in the device. This could indicate that the element is down. Cannot plot [Data is String type] The collected data from the device is of string type and the graph can not be plotted. The table view of the collected statistic can be remarkably useful, since it calls out each historical value in a table where you can read individual numbers. The table view is also the only way to view non‐numeric values. When you dismiss this window, WM will discard the values that it collected and will not save them in the database. 13.3.2 Viewing a Collected Performance Statistic The collected view of a performance statistic shows historical data collected in the past and is useful for identifying trends or focusing on time frames, such as blocks of time during which problems tend to arise. To launch the collected graph viewer, right‐click on the target statistic in the Configured Collection view and select PlotCollected Statistic from the drop‐down list of options. The Collected statistics graph opens in a separate window. This window provides not only the graph style options that are summarized in Table 28 on Page 384, but also data options in the right panel, headed Data Range Settings. The default range is the last previous 24 hours. If you switch the setting to another, click the Plot Chart button at the bottom of the panel to effect the change. 386
- 387. WM Release 4.0 User Guide Issue 3 May 2012 Figure 271: Collected statistics window, line graph The following messages are possible when you launch the Collected statistics window. Table 30: Possible messages for a Collected statistics window Message Reason No data available By default, automatic data collection starts 5 minutes after the WM Server is started and any devices are discovered. In addition, data collection for a newly added statistic also starts after 5 minutes. However, the delay is configurable and can be set according to your network requirements. note………………For Counter type OIDs, the initial data collected is not stored. When data is collected for the second time, the difference between the two values is calculated and stored. Depending on the polling interval set, the data will be collected a second time. Therefore, it is possible that there will be more delay in plotting the graph data when working with Counter type OIDs. Cannot plot [Data is The collected data from the device is of string type, therefore a graph will not be String type] plotted. Date Range Setting The From date and To date that you set in Custom Date Range Settings are incorrect. incorrect Check for the date/time values set and click Plot Chart again. [From‐Date is greater than To‐Date] The graph options for this view are summarized in Table 28 on Page 384. This view supports zooming, auto‐ranging, printing, and saving as a PNG file. These options are available through a right‐click anywhere in the graph area. 387
- 388. Issue 3 WM Release 4.0 User Guide May 2012 The following is an example of a bar graph in this viewer. Figure 272: Collected statistics window, bar graph The table view of the collected statistic can be remarkably useful, since it calls out each historical value in a table where you can read individual numbers. The table view is also the only way to view non‐numeric values. The date range settings on the right side of the dialog allow you to display values from the last 24 hours, the past week, or an arbitrary date range. 13.4 Using System Reports WM includes various reports that are each preconfigured to deliver current values of important sets of performance statistics in all devices of a particular category: AP (see Table 31: AP performance reports on Page 389) PMP 320 AP (see Table 32: PMP 320 AP performance reports on Page 389) SM (see Table 33: SM performance reports on Page 390) PMP 320 CPE (see Table 34: PMP 320 CPE performance reports on Page 391) PMP Backhaul (see Table 35: PMP Backhaul performance reports on Page 392) PTP (see Table 36: PTP performance reports on Page 392) 388
- 389. WM Release 4.0 User Guide Issue 3 May 2012 Table 31: AP performance reports System Report Name Statistic Values Reported AP Bridge Table [per Device Name (Device ID)] Summary SM MAC, ocal UID, Age, Extension [timeout extension flag] , Hash L Device ID, Device Name AP Ethernet Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards , Rx Errors , Tx Bytes Tx Broadcast, x , , , T Multicast , Tx Discards Tx Errors , Device ID, Device Name Type, ite Contact , Site Location, Software Version Platform Version, FPGA Version , S , AP General Status Uptime, Regulatory, hannel Bandwidth , Cyclic Prefix, egistered SM Count , Color C R Code Region Code, Temperature , Device ID, Device Name AP QOS Summary Uplink Sustained Rate, Downlink Sustained Rate, Uplink Burst Allocation, Downlink Burst Allocation, Downlink Rate, Broadcast Downlink CIR Device ID, Device Name AP Radio Statistics Rx Bytes Rx Broadcast Rx Multicast, Rx Discards Rx Errors , Tx Bytes Tx Broadcast, x , , , , T Multicast , Tx Discards Tx Errors , [per Device Name (Device ID)] AP Session Table MAC, Session Uptime, Session State, Reg Count, Re‐reg Count, Average Jitter, Summary RSSI (dBm), Air Delay (nsec) [25 highest with total bytes] AP Top 25 Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated Errors Device ID, Device Name AP VLAN Configuration Enabled, Local Setting Enabled, Allow Only Tagged Frames, Dynamic Learning, Ageing Summary Timeout, Management VID PMP AP Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab] Summary Report Graphs and/or tables [optionally specified in Input Data tab] Table 32: PMP 320 AP performance reports System Report Name Statistic Values Reported PMP 320 AP Ethernet Device ID, Device Name Statistics Rx Bytes , Rx Discards , Rx Errors , Tx Bytes Tx Discards Tx Errors , , Device ID, Device Name PMP 320 AP General Type , Site Name, Site Contact , Site Location, Software Version Device Version Uptime , , , Status Center Frequency , Base Station ID PMP 320 AP Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab] Summary Report Graphs and/or tables [optionally specified in Input Data tab] 389
- 390. Issue 3 WM Release 4.0 User Guide May 2012 System Report Name Statistic Values Reported Index, Service Class Name PMP 320 AP QOS MIR, Min Reserved Rate, Max Latency, Data Delivery Type, Unsolicited Grant Interval, Summary Unsolicited Poll Interval Device ID, Device Name PMP 320 AP Radio Uplink CINR (0), plink RSSI (0), ownlink CINR (0) , Downlink RSSI (0) , Uplink CINR (1) , U D Statistics Uplink RSSI (1) , Downlink CINR (1), ownlink RSSI (1) D PMP 320 AP Service SM MAC, SF Index Flow Summary Direction, QoS Profile ID, Classification Rule ID [25 highest with total bytes] PMP 320 AP Top 25 Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated Report Errors Table 33: SM performance reports System Report Name Statistic Values Reported PMP FSK SM Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab] Summary Report Graphs and/or tables [optionally specified in Input Data tab] PMP OFDM SM [for number of days back specified in Input Data tab, devices specified in Devices tab] Graphical Summary Graphs and/or tables [optionally specified in Input Data tab] Report SM Bridge Table [per Device Name (Device ID)] Summary Device MAC, ocal UID, Age, Extension [timeout extension flag], Hash L Device ID, Device Name SM Ethernet Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards , Rx Errors , Tx Bytes Tx Broadcast, x , , , T Multicast , Tx Discards Tx Errors , Device ID, Device Name Type , Site Contact Site Location , Software Version , Platform Version, FPGA Version , , SM General Status Uptime, Channel Bandwidth , Cyclic Prefix , Registered To , Color Code, Channel Frequency Transmit Power Level, Region Code Temperature , Air Delay, itter , , J Device ID, Device Name Uplink Sustained Rate, Downlink Sustained Rate, Uplink Burst Allocation, Downlink SM QOS Summary Burst Allocation, Broadcast MIR, High Priority Channel Enabled, High Priority Uplink CIR, High Priority Downlink CIR, Low Priority Uplink CIR, Low Priority Downlink CIR Device ID, Device Name SM Radio Statistics Rx Bytes Rx Broadcast Rx Multicast , Rx Discards Rx Errors , Tx Bytes Tx Broadcast, x , , , , T Multicast , Tx Discards Tx Errors , 390
- 391. WM Release 4.0 User Guide Issue 3 May 2012 System Report Name Statistic Values Reported [25 lowest with value] Receive power [25 highest with value] SM Top 25 Report Jitter [25 highest with total bytes] Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated Errors Device ID, Device Name SM VLAN Configuration Allow Only Tagged Frames, Dynamic Learning, Ageing Timeout, Management VID, SM Summary Management Pass‐through VID, Untagged Ingress VID Table 34: PMP 320 CPE performance reports System Report Name Statistic Values Reported PMP 320 CPE Ethernet Device ID, Device Name Statistics LAN Rx Bytes, LAN Tx Bytes WAN Rx Bytes , WAN Tx Bytes , Device ID, Device Name PMP 320 CPE General Type , Site Name, Site Contact , Site Location , Software Version , Hardware Model, Status Center Frequency (kHz), evice Bandwidth (kHz), p Link Data Rate (Kbps) , D U Up Link Modulation Type Down Link Data Rate (Kbps), Down Link Modulation Type , PMP 320 CPE Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab] Summary Report Graphs and/or tables [optionally specified in Input Data tab] PMP 320 CPE Radio Device ID, Device Name Statistics Rx Bytes Rx Discards Rx Errors , Tx Bytes Tx Discards Tx Errors , , , , Device ID, Device Name PMP 320 CPE Service SFID, CID, BCID, Type, State, Direction, Enabled, Scheduling, Max Rate (bps), ARQ Flow Summary Enable, HARQ Enable, Rules [25 lowest with value] RSSI [25 highest with value] PMP 320 CPE Top 25 CINR Report [25 highest with total bytes] Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated Errors 391
- 392. Issue 3 WM Release 4.0 User Guide May 2012 Table 35: PMP Backhaul performance reports System Report Name Statistic Values Reported PMP Backhaul Bridge [per Device Name (Device ID)] Table Summary SM MAC, ocal UID, Age, Extension [timeout extension flag] , Hash L Device ID, Device Name PMP Backhaul Ethernet Rx Rate(bytes/sec) , Rx Broadcast Rate(packets/sec), x Multicast Rate(packets/sec), R Statistics Rx Discards, x Errors , Tx Rate(bytes/sec), x Broadcast Rate(packets/sec) , Tx Multicast R T Rate(packets/sec) Tx Discards, Tx Errors , Device ID, Device Name PMP Backhaul General Type, ite Contact , Site Location, Software Version Platform Version, FPGA Version , S , Status Uptime, Channel Bandwidth , Color Code Region Code, Registered SM Count, , Temperature PMP Backhaul Graphical [for number of days back specified in Input Data tab, devices specified in Devices tab] Summary Report Graphs and/or tables [optionally specified in Input Data tab] Device ID , Device Name PMP Backhaul Radio Rx Rate(bytes/sec), x Broadcast Rate(packets/sec), x Multicast Rate(packets/sec), R R Statistics Rx Discards, x Errors , Tx Rate(bytes/sec) , Tx Broadcast Rate(packets/sec) , Tx Multicast R Rate(packets/sec) Tx Discards Tx Errors , , PMP Backhaul Top 25 [25 highest with total bytes] Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Errors Device ID, Device Name PMP Backhaul VLAN Enabled, Local Setting Enabled, Allow Only Tagged Frames, Dynamic Learning, Ageing Configuration Summary Timeout, Management VID Table 36: PTP performance reports System Report Name Statistic Values Reported PTP VLAN Configuration Device ID, Device Name Summary Enabled, Management Priority, Allow Only Tagged Frames, Management VID Device ID, Device Name PTP Ethernet Statistics Rx Bytes, x Non Unicast Rx Unicast , Rx Discards Rx Errors, x Bytes , Tx Non Unicast R , , T , Tx Unicast , Tx Discards Tx Errors , Device ID, Device Name Type, ite Contact , Site Location, Software Version PGA Version , Uptime, Region S ,F PTP General Status Code Bandwidth RF Receive Channel RF Receive Frequency, RF Receive Modulation , , , Mode , RF Receive Power , RF Transmit Channel , RF Transmit Frequency RF Transmit , Modulation Mode , RF Transmit Power PTP Graphical Summary [for number of days back specified in Input Data tab, devices specified in Devices tab] Report Graphs and/or tables [optionally specified in Input Data tab] Device ID, Device Name PTP Radio Statistics Rx Bytes, Rx Discards, Rx Errors, Tx Bytes, Tx Discards, Tx Errors 392
- 393. WM Release 4.0 User Guide Issue 3 May 2012 System Report Name Statistic Values Reported [25 highest with total bytes] PTP Top 25 Report Rx Bandwidth, Rx Errors, Tx Bandwidth, Tx Errors, Aggregated Bandwidth, Aggregated Errors PTP VLAN Configuration Device ID, Device Name Summary Enabled, Management Priority, Allow Only Tagged Frames, Management VID WM also provides preconfigured reports of Inventory Summary (see Figure 273) Device Uptime (see Figure 274 on Page 394) Figure 273: Inventory Summary report 393
- 394. Issue 3 WM Release 4.0 User Guide May 2012 Figure 274: Device Uptime report These reports are available on demand as preconfigured (as described in the next section). The preconfigured versions and slimmer versions of them (described under Customizing a System Report on Page 397) are also available through scheduled tasks. See Scheduling a One‐Time or Periodic Task on Page 647. By default, all system reports are accessible to the Groups Admin and Users. This access continues unless the administrator removes the permission for a specific user. They are initially inaccessible to user groups that the operator creates. As shown below in a portion of the Permissions tree hierarchy, permissions for system reports are individually assignable per report as well as categorically assignable. 394
- 395. WM Release 4.0 User Guide Issue 3 May 2012 Some system reports, for example the WimaxCpeGraphicalSummaryReport.php, include the option to view their data in graphical form. Any desired system report must be imported into the client application as described in the next section. 395
- 396. Issue 3 WM Release 4.0 User Guide May 2012 13.4.1 Importing System Reports To import any or all of the available system reports, perform the following steps: Procedure 72: To import system reports 1. In the Applications Tree, right‐click the System Reports node. 2. From the drop‐down list of options, select Import System Report(s). 3. Browse to the target path where the system reports exist within reach of the client. note ............. If you are browsing in the server file system, this path is C:CambiumWMserverDefault TemplatesSystem Reports or /usr/local/cambium/wm/server/Default Reports/System Reports/. 4. Use ◦ Ctrl+click to individually select a set of templates. ◦ Shift+click to individually select the first and last of a set of templates that are sequentially displayed in the browser, then Ctrl+click to subtract any from in between. ◦ Click to select a single template. 5. After you have highlighted (selected) all of the desired template files, click the Open button. 6. All of the imported reports will be useable for user (whose default permissions to use them have not been optionally removed in Security Administration). 13.4.2 Using a System Report As Preconfigured note ............. Access to these reports require that they are imported into a client that is networked to the WM server file system. To access any of these reports, select System Reports from the Applications tree. This opens the System Reports view in the view panel (Figure 246 on Page 342). note ............. When you execute a report, the system may respond with Error occurred while printing report. This error occurs only rarely and when system resources are being used at a relatively high rate, such as during status polling and rediscovery. If you encounter this error, launch the report execution again. Cambium Networks tracks this issue under Item ID 0015217 and 0010672. To open the desired report, either double‐click in the row or right‐click in it and select Execute Report. When you do, the report opens as HTML content. You can reshape the HTML window, but not resize its columns or sort by their content. However, you can export most of the entire reports as CSV for use in another application or print any of them on any networked printer. For reports that WM formats into multiple vertical blocks, the report dialog does not include an export option. However, to dump a portion (such as the contents of a block) of the HTML data that the report returns to a file type that an another application can read or a script can use, you can mark the portion of interest and copy it out. You can reshape the HTML window, but not manually resize its columns or sort by their content. However, you can export the entire report as CSV for use in another application or Print the entire report on any networked printer. Running a device summary report is a schedulable task in the WM client. See Scheduling a One‐Time or Periodic Task on Page 647. 396
- 397. WM Release 4.0 User Guide Issue 3 May 2012 As soon as you launch a system report, WM automatically saves it into a repository that contains, in list form, all previously launched reports that have not been deleted from the list. You can access this repository by selecting System ReportsReport Results from the Applications Tree. This list is sortable by any of its columns: Result File Name (in the format ReportName_SequentiallyAssignedReportNumber, so that within each alpha sort of report name, the order is chronological) User (who launched the report) Time (date and time) Report Name Report Type See Figure 162 on Page 226. Since the reports in the list are not searchable, and since the list of stored reports tends to grow over time, sorting is useful. Secondary sorting is achievable by sorting the secondary sort column first, then the primary sort column. To view an individual report in the Report Results view, right click on the target report and select View Report. This opens the report in the exact format and window size that the report opened in when you originally launched it. 13.4.3 Customizing a System Report For a system report that otherwise runs on all devices of a category, you can customize the report to run on a subset of those devices if you set the report as a scheduled task and filter that task for devices and optionally for their configuration and performance values. See Table 86: Configurable task prerequisites, requirements, and options on Page 648. 13.5 Launching an Operator-defined Report If the administrator of the WM server file system has added operator‐defined reports to the system (as described in the server administration guide) and if they have been imported into a client that has network access to the WM file server, then these are available when you select System Reports from the Applications tree, which opens a list of all of them in the view frame. In the WM client, you cannot modify any of these reports, but you can execute any of them either on demand or as a scheduled task, at your option. See Scheduling a One‐Time or Periodic Task on Page 647. 397
- 399. WM Release 4.0 User Guide Issue 3 May 2012 14 Administering Discovery This chapter explains how to use the Discovery Configurator to discover your network and how to perform discovery‐related administrative tasks. Wireless Manager default settings enable automatic discovery of network elements on the same local network as the server itself. WM can be configured to discover devices on an arbitrary network or at an arbitrary IP address, with configurable SNMP authentication. Various parameters affect the speed and efficiency of the discovery process and are accessed through the Discovery Configurator. As WM discovers devices, it adds their device type names into the applications tree: under Inventory. This section displays no device types before the first‐ever discovery is performed. It shows only non‐ device entries. 14.1 Importing Device Discovery Information WM allows you to import properly formatted device discovery information from another management system, such as Prizm. In general terms, the proper format exported from the other system has the following pattern. Table 37: Format for device discovery information import Column Column Position Data 1 Range of IP address. Entries in this column can any either of the following formats: NetworkIP for example, n.n.n.0 IP-IP;SubnetIP range then semicolon delimiter then subnet IP individual address 2 Any of the following syntaxes: Network if the first column data is NetworkIP Range if the first column data is IP-IP;SubnetIP Node if the first column data is an individual address 3 The default subnet mask to be used. The default subnet mask to use for node discovery is 255.255.255.255. 4 The SNMP version. Must be v1, v2c, or v3. 5 The SNMP agent port. The default that WM will use is 161 for any record whose fifth column does not contain a valid port number. 6 The SNMP read community string. Null is not allowed if the fourth column of the record contains v2c. 399
- 400. Issue 3 WM Release 4.0 User Guide May 2012 Column Column Position Data 7 The SNMP write community string. 8 Context name 9 Username 10 Priv Protocol These columns are for contents only where the fourth 11 Priv Password column of the record is populated by v3. 12 Auth Protocol 13 Auth Password Beware of saving the file in a program, such as MS‐Excel, that deposits its own end‐of‐line characters into it. The following is an example of a parsing error that points to the first line that ends with such an end‐of‐line character: An import file must exist within file browser range of the client when the import operation is invoked. To perform the import operation, see Importing Data Files Into WM on Page 105. As soon as the operation is executed in the client, user account management under the imported user configuration begins. 14.2 Using the Discovery Configurator The discovery process can be configured to cause the auto discovery of remote nodes or to prevent the discovery of specific nodes or a local network. At startup of the wmserver service, the WM server reads the values of the parameters that have been set in the Discovery Configurator. The server also reads them and immediately launches rediscovery when a change is made in the Node Discovery tab of the Discovery Configurator but does not, however, similarly launch rediscovery when a change is made in the Network Discovery tab. This difference is by design, to conserve system resources. 400
- 401. WM Release 4.0 User Guide Issue 3 May 2012 14.2.1 Opening the Discovery Configurator The Discovery Configurator is available as a runtime administration tool. Procedure 73: To invoke the Discovery Configurator 1. From the main menu, select ToolsDiscovery Configurator. The Discovery Configurator tool is displayed. Figure 275: Discovery Configurator, General tab 401
- 402. Issue 3 WM Release 4.0 User Guide May 2012 14.2.2 Discovering Mixed Networks When using Wireless Manager to manage networks that contain SNMPv3 devices as well as PMP and/or PTP devices, the following process should be used. To discover the SNMPv3 generic devices, use Network Discovery. The SNMPv3 credentials must be entered in the Network Discovery form. By default, WM uses SNMP broadcasts to discover devices via Network Discovery, so the switches or routers that control traffic in the specified network must be configured to allow SNMP Broadcast. To discover PMP and/or PTP devices, use Node Discovery. If all devices use the same SNMP credentials, then the credentials must be entered only once (create the first device, then create the rest of devices by changing the IP address of the first one and clicking Add). note ............. WM discovers PMP and PTP devices only if they have IP addresses. Assign IP addresses to them before you configure their discovery. 14.2.3 Configuring General Automatic Discovery This section explains the options available in the General tab of the Discovery Configurator. Enabling/Disabling Auto-discovery By default, when the WM server is started, discovery automatically starts against any networks or nodes that are configured for discovery and not individually disabled. This is the auto discovery feature, which itself can be enabled or disabled. Since discovery uses system resources, it can be useful in some situations to turn off auto discovery. However, discovery and rediscovery are the only ways for WM to find new devices in any specified subnets or IP ranges, and to refresh the database copies of configuration parameters that were read from previously discovered devices. Procedure 74: To disable auto-discovery 1. In the General tab of the Discovery Configurator, deselect the AutoDiscovery checkbox. By default, this option is enabled. A warning message is displayed. Figure 276: Confirmation for deselection of AutoDiscovery 2. Click Yes to disable auto‐discovery. 3. Click the Apply button. important ........... When this option is disabled, auto-discovery does not occur when the Wireless Manager server restarts. If you disable and then later re-enable the auto discovery option, discovery will be initiated using the node, network, and other parameters previously specified in the other parts of the discovery configurator. To re‐enable auto‐discovery, recheck the box. 402
- 403. WM Release 4.0 User Guide Issue 3 May 2012 Rediscovering Already Discovered Devices As is shown below, rediscovery is the re‐execution of discovery using existing discovery parameters, usually on the basis of a schedule. Rediscovery defaults to a 24 hour schedule. One main purpose of rediscovery is to find new devices in the configured IP subnets or IP ranges, or at the IP addresses (nodes) previously configured for discovery. Another purpose of rediscovery is to refresh the configuration parameters for each previously discovered device, and compare them to previously polled or previously configured values. important ........... It is advisable to have the Rediscover Already Discovered option enabled (checked) because WM depends on rediscovery to check for network device configuration changes that have been made outside of the Wireless Manager application (using the web user interface of the device, for example). We refer to this as a Consistency Check. However, in addition or as an alternative, you can the configuration refresh capability in WM to poll (separate from rediscovery) to detect these changes. (See Adjusting Configuration Polling Intervals on Page 321.) By default, this refresh occurs once in each 12-hour period. When WM detects a difference between a network device's setting and the corresponding value in the database, WM updates the database value to match. Procedure 75: To rediscover previously discovered nodes 1. In the General tab of the Discovery Configurator, select the Rediscover Already Discovered checkbox, if it is not already selected. 2. Click the Apply button. When the discovery process reschedules itself, this parameter decides the functionality of the discovery process. When it is enabled, all devices (discovered and undiscovered) are rediscovered. note ............. The above parameter does not control the behavior for nodes that obtain their IP addresses via DHCP. Those nodes are rediscovered every time the objects in the database are updated with the latest information. Preventing a Local Network from Being Discovered By default, the local network and all its nodes are not discovered. Since discovery takes up system resources and can slow down other operations, it is important to keep local network discovery disabled when there are no devices to discover on some or all of the local network. It is most efficient to directly specify each network you want to discover and leave local discovery turned off. Procedure 76: To prevent local network discovery 1. In the General tab of the Discovery Configurator, deselect Discover LocalNet. By default, this option is disabled. 2. Click the Apply button. Setting the Discovery Interval The interval between the attempt to discover at one address in a network and the attempt to discover at the next address in a network can be set in the Discovery Interval option. The value set for this parameter determines the performance (CPU utilization and network traffic) of the discovery process, since it determines the rate at which WM performs its discovery work and therefore the rate at which it uses system resources for discovery. 403
- 404. Issue 3 WM Release 4.0 User Guide May 2012 Procedure 77: To set the discovery interval 1. In the General tab of the Discovery Configurator, enter the interval value (in seconds) in the Discovery Interval field. The value can be greater than or equal to zero and the default value is 1 second. note ............. very long intervals can result in a failure to complete discovery within the rediscovery period. 2. Click the Apply button. Configuring Initial Discovery The first discovery process is started as soon as the Wireless Manager server is started (in cold start or warm start mode). The available settings in the Initial Parameters dialog determine the speed of the initial discovery process. It is not necessary to set the values for all the parameters. Initial discovery is unique because WM performs many operations during its initial startup, and because a significant amount of initialization is possibly being done in other software packages on your system during initial startup. So, it may be useful to change the timing of initial discovery to something different from the steady state parameters of discovery. The Initial Parameters settings apply to only the initial discovery. For subsequent discoveries, the configuration values provided in the General tab are used. When no parameters are set in the Initial Parameters section, Wireless Manager, by default, takes up the values set for the parameters in General tab, which is applicable both to the initial discovery process and for the subsequent discoveries. 404
- 405. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 78: To set initial discovery parameters 1. In the General tab of the Discovery Configurator, select the Initial Parameters button. The Initial Parameters dialog box is displayed. Figure 277: Initial Parameters contents from the Discovery Configurator 2. Enter the desired values and click OK. 3. Click the Apply button. The Initial Parameters screen options are listed in the following table. 405
- 406. Issue 3 WM Release 4.0 User Guide May 2012 Table 38: Initial discovery parameters Parameter Description Interval (in seconds) between the discovery of any two devices in the Discovery Interval network. Default value: 1 second Interval (in hours) between two complete discoveries of a network. Default value: 48 hours If a negative value is given, it is replaced by 48. Rediscovery Interval important….…...For a large network, a rediscovery interval of at least 48 hours and a less-busy rediscovery launch time such as 1:00 a.m. are recommended. Threshold value, in seconds, for all the SNMP requests. This value is the maximum time that the requesting process waits for the first response, before attempting a retransmission. It is useful when the discovery engine is discovering a remote network where the response time could be more. SNMP Timeout Default value: 2 seconds This value grows exponentially for each retries. This value is doubled for each retry. For example, if the timeout value is set to 5 seconds and retries set as 2, the first retransmission will happen after 5 seconds. The second after 15 seconds and so on. Number of SNMP retries for discovery, status polling, and data collection. SNMP Retries Default value: 0 (i.e., retry is performed only once) If you set the value as 1, then retry is done twice. Setting this value at minimum gives better performance. Scheduling Rediscovery You can specify the scheduled interval (in hours) between two complete network discoveries. When the task of pinging all of the IP addresses in a network is completed, Wireless Manager will wait for the specified interval before beginning a network rediscovery. Wireless Manager depends on rediscovery to check for network device configuration changes that may have been made outside of the Wireless Manager application (such as changes made using a device web interface). We refer to this feature as a Consistency Check. When discovery detects a difference between the network device's settings and the corresponding value in the database, Wireless Manager updates the database values to match. You can schedule the rediscovery process by specifying the rediscovery interval in hours. You can alternatively configure the rediscovery process to run at a specific hour on a specific day of the month or a specific day of the week. 406
- 407. WM Release 4.0 User Guide Issue 3 May 2012 You can set the Rediscovery Interval using one of the following procedures: Procedure 79: To set the rediscovery at Regular Interval Procedure 80: To set rediscovery on specific dates Procedure 81: To set rediscovery on specific days Procedure 79: To set the rediscovery at Regular Interval The time interval between two complete network discoveries can be configured using the Regular Interval option. When a regular time interval for rediscovery is configured, the Wireless Manager discovery engine, after discovering the IP Addresses in the network, waits for the specified number of hours before starting to rediscover the network again. 1. Click General tab in the Discovery Configurator. 2. Click the Rediscovery button. The Rediscovery Scheduler dialog is displayed. 3. From within the Rediscovery Scheduler dialog, select the Regular Interval option (top). Figure 278: Rediscovery Scheduler dialog 4. Specify the rediscovery interval in Hours, Minutes, and Seconds (as required). By default, the interval is set at 4 hours. You can set any value from 1 to 24 in the hours field. When you specify ‐1, rediscovery will be based on the entries configured in the User's Schedule option. When you select a negative value other than ‐1, the rediscovery interval will be taken as 24. For a large network, a rediscovery interval of 48 hours is recommended. 5. Click OK. 407
- 408. Issue 3 WM Release 4.0 User Guide May 2012 note ............. If the Rediscovery Interval is set using Regular Interval option, then the values set for Specific Dates and Days of Week options will not take effect. Procedure 80: To set rediscovery on specific dates 1. Click General tab in the Discovery Configurator. 2. Click the Rediscovery button. The Rediscovery Scheduler dialog is displayed. 3. Click the Specific Dates option. Figure 279: Rediscovery Scheduler, Specific Dates 4. To choose a specific date on which the rediscovery occurs, click the appropriate date option: ◦ All: Selects all the dates of a month and indicates rediscovery occurs every day. ◦ Specific: Constitutes a range of days. For example, if you select 5 and 15, then the rediscovery will take place from the 5th to 15th of every month. When a particular month does not have the specified date, the rediscovery will occur based on the “number of days” difference between the current month and the next month. For example, if the specified date is 31 and the current month is October. As per this configuration, the rediscovery should occur after a range of 31 days. But the next month, November, does not have 31. In this case, rediscovery will be scheduled for December 1st (i.e., current month date 31 + specified date [31]). This is because all these calculations are in terms of milliseconds. Similarly if the date is specified as 31 and the current month is February (28 days), then the rediscovery will be scheduled for March 3. 408
- 409. WM Release 4.0 User Guide Issue 3 May 2012 5. Select one of the Hour options. All selects all the hours in a day. Specific selects one or more specific hours of the day. note ............. For the least impact on system resources and network traffic, select an hour when WM and the network are least busy (for example, 1:00 a.m.). 6. Click OK after you select the option. Procedure 81: To set rediscovery on specific days 1. Click General tab in the Discovery Configurator. 2. Click Rediscovery. The Rediscovery Scheduler dialog box is displayed. 3. Click the Days of Week option. Figure 280: Rediscovery Scheduler, Days of Week 4. To choose a specific day on which rediscovery occurs, click the appropriate day option. All selects all the days of the week. Specific selects one or more specific days of the week. For example, if you select Tue and Fri, the rediscovery occurs only on those days, every week. 5. Select one of the Hour options. All Hours selects all the hours in a day. Specific Hours sets a specific hour. 6. Click OK after you select the option. 409
- 410. Issue 3 WM Release 4.0 User Guide May 2012 note ............. When both dates and days are configured, the precedence is given to dates and not weekdays. When the dates or days are configured, the rediscovery interval is set as -1 in the User's Schedule. If the Hour field is not specified, 10 will be assigned as the default value. So, if you specify only the days or dates without specifying the hours, rediscovery will happen at the 10th hour of that particular day or date. The combinations of configurations for rediscovery interval are listed in the table below. Table 39: Discovery interval parameters Rediscovery Category Hour Dates Days Interval Any entry here will Any entry here will Any entry here will Default 24 not take effect not take effect not take effect No value should be No value should be Particular Hour(s) ‐1 Desired hour configured configured Particular Day for No value should be No value should be ‐1 Desired days every week configured configured Particular Date for No value should be No value should be ‐1 Desired dates every month configured configured Particular Hour on No value should be ‐1 Desired hour Desired day a Particular Day configured Particular Hour on No value should be ‐1 Desired hour Desired date a Particular Date configured Protocol Configuration Various device types support the various protocols. The discovery process identifies the device, and the protocol supports processes based on these parameters. The Protocol tab of the Discovery Configurator helps you configure the SNMP Protocol parameters. The SNMP authentication configured in this tab applies to initial SNMP broadcasts, when SNMP broadcast is enabled and when network discovery is used. Once a device responds to the SNMP broadcast for a network (subnet or IP range), further communication with the responding device uses the SNMP authentication information specified for that network in the Network Discovery tab of the Discovery Configurator. All discovered PMP and PTP devices use the write community string that is specified in the global SNMP Properties dialog (Figure 282 on Page 411), regardless of their IP address or subnet. In contrast, some generic devices may negotiate their own write community string with WM and ignore this string. 410
- 411. WM Release 4.0 User Guide Issue 3 May 2012 Configuring SNMP Protocol The goal is to match the settings to those on some generic devices being discovered via SNMP broadcast, if any exist. The exception is the write community string, which should match the write community of the PTP devices being discovered (broadcast or not), if any exist. Procedure 82: To configure SNMP Properties 1. Select the Protocol tab in the Discovery Configurator. Figure 281: Discovery Configurator, Protocol tab 2. Click on the word SNMP from the Protocols list. 3. Select the Properties button to display the SNMP Properties dialog. Figure 282: SNMP Properties selected from the Protocol tab 411
- 412. Issue 3 WM Release 4.0 User Guide May 2012 4. Configure the properties that are described in the table below. Table 40: SNMP configuration parameters Option Description Select this check box to enable or disable SNMP‐based discoveries. By SNMP Discovery default, SNMP discovery is enabled. Specify the number of retries to be made to query a device. Default SNMP Retries value: 0 (i.e., only one attempt is made to query a particular node) Specify the timeout (in seconds) to wait for the first response before SNMP Timeout attempting a retransmission. Default value: 2 seconds. Specify a list of communities/community strings, such as private or public can be given to discover the devices when an SNMP request is given. Multiple values can be given separated by space. To limit the number of minor alarms for Authentication failure triggered by rediscovery with multiple default read community strings, one of the following workarounds is required: Read Community Discover nodes individually. Move the community strings of devices that send wrong string traps up to the top of the list of strings. Subdivide the discovery networks such that each entry in the Network Discovery tab has the community string that applies to the nodes within its range of IP addresses. Default value: public Specify the community, such as private or public (for example) to set the Write write community property for all SNMP‐enabled devices. Community Default value: private Specify the ports while trying to communicate to the SNMP agents on SNMP Ports each node. Multiple ports can be specified either as space‐separated values or as a range of values. Example: 161 8001‐8005 9099. 5. Click OK. SNMPv3 Discovery Use one of the following procedures to configure discovery of SNMPv3 devices: For devices that support and are configured to allow access via both v1 and v3, use Procedure 83. For devices that support and are configured to allow access via only v3, use Procedure 84. 412
- 413. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 83: To configure discovery for a network of devices set to allow SNMPv1 and v3 access 1. Ask your server file system administrator to enable the broadcast discovery feature according to the procedure provided in the server administration guide section titled "Enabling Broadcast Discovery." note ............. Ensuring that the feature is enabled is important for efficiency of the discovery process, since devices that are configured for both v1 and v3 respond to the initial v1 broadcast ping before they provide further information to WM based on its ability to authenticate in v3 (as a result of the remaining steps in this procedure). 2. After receiving confirmation that the feature is enabled, use the Network Discovery tab (Figure 283 on Page 415) to define the network as follows: a. Use Procedure 89: To discover SNMPv3 devices in a network on Page 418 to set the SNMPv3 properties that will allow the WM discovery engine to authenticate into the devices. b. Optionally, use Procedure 90: To set a network‐specific SNMPv3 configuration for discovery on Page 420 to override the common User Name and Context Name specified in Procedure 89. note ............. The values of these settings are essential for authenticating the WM discovery engine to query the bulk of discovery information from the device. 3. Select the Protocol tab in the Discovery Configurator (Figure 281 on Page 411). 4. In the Protocols list, click on the word SNMP. 5. Select the Properties button to display the SNMP Properties dialog (Figure 282 on Page 411). 6. In the Read Community field, type in an SNMPv1/v2c read community string. note ............. This string is necessary for the initial ping in v1, which ignores the v3 security settings. 7. Check the check box for SNMPv3 Discovery. note ............. This check mark is necessary for having the v3 security settings read (for authenticating the WM discovery engine) to query the bulk of discovery information from the device. Procedure 84: To configure discovery for a network of devices set to allow only SNMPv3 access 1. Ask your server file system administrator to disable the broadcast discovery feature according to the procedure provided in the server administration guide section titled "Disabling Broadcast Discovery." 2. After receiving confirmation that the feature is disabled, use either ◦ the Network Discovery tab (Figure 283 on Page 415) to define the network as follows: a) Use Procedure 89: To discover SNMPv3 devices in a network on Page 418 to set the SNMPv3 properties that will allow the WM discovery engine to authenticate into the devices. b) Optionally, use Procedure 90: To set a network‐specific SNMPv3 configuration for discovery on Page 420 to override the common User Name and Context Name specified in Procedure 89. 413
- 414. Issue 3 WM Release 4.0 User Guide May 2012 ◦ the Node Discovery tab (Figure 288 on Page 422) to define the network as follows: a) Use Procedure 94: To discover specific SNMPv3 devices on Page 424 to set the SNMPv3 properties that will allow the WM discovery engine to authenticate into the devices. b) Optionally, use Procedure 95: To set a device‐specific SNMPv3 configuration for discovery on Page 424 on Page 420 to override the common User Name and Context Name specified in Procedure 94. 3. Select the Protocol tab in the Discovery Configurator (Figure 281 on Page 411). 4. In the Protocols list, click on the word SNMP. 5. Select the Properties button to display the SNMP Properties dialog (Figure 282 on Page 411). 6. In the Read Community field, type in an SNMPv1/v2c read community string. 7. Check the check box for SNMPv3 Discovery. Network Specific Discovery Configuring Discovery of Remote Networks By default, the Discover LocalNet flag in the General tab of the Discovery Configurator (shown in Figure 275 on Page 401) is not checked, and the local network (to which the management station running WM server is connected) therefore is not discovered by default. When it is checked, WM adds to the topology any other network that it detects through the router and makes that network object unmanaged. If you want to add a remote network and also perform discovery on that network, this can be done using the Network Discovery option in the Discovery Configurator. note ............. Configuring discovery means that WM is set to attempt discovery in a specified network. WM cannot actually be forced to successfully discover a device at a given IP address. Discovery fails under any of the following conditions: if no device with that address exists if the SNMP authentication fails for that device if the authentication is correct but the device is not supported by WM if there is some kind of communications problem due to errors in the data path between WM and the device. 414
- 415. WM Release 4.0 User Guide Issue 3 May 2012 Procedure 85: To enable discovery of remote networks 1. Select the Network Discovery tab in the Discovery Configurator. Figure 283: Discovery Configurator, Network Discovery tab 2. Select Discover. 3. Select Entire Network. 4. Enter the network address in the IPAddress field and the sub‐netmask of the network in the NetMask field. 5. Click the Add button. The IPAddress and NetMask are added to the screen with the Discover column enabled (checked), and their discovery is now enabled. 6. Click the Apply button. note ............. This procedure uses the global SNMP authentication properties, but in most cases you will want to enter in the specific SNMP properties of the devices on the specified network. To do so, use Procedure 88: To discover SNMPv1 or v2c devices in a network on Page 417. 415
- 416. Issue 3 WM Release 4.0 User Guide May 2012 Discovering a Range of IP Addresses in a Network Procedure 86: To discover only a range of addresses in a network important ........... This procedure involves using the Set of Nodes option. With this option, discovering SNMP v3 devices can slow your system performance where there are more networks to discover. The workaround, wherever feasible, is to specify the range of SNMP v3 device IP addresses using the Entire Network option instead of Set of Nodes. 1. Click the Network Discovery tab in the Discovery Configurator. 2. Select Discover. 3. Select Set of Nodes. The Start IP and the End IP text boxes become enabled. 4. Enter the network address in the IP Address field and the sub‐netmask of the network in the NetMask field. 5. In Start IP and End IP, enter the starting IP address and the ending IP address in the range of ip addresses to be discovered, respectively. 6. Click the Add button. A multiple range of IP addresses in a single network can also be configured. note ............. If any of the node properties are specified in the Disallow Criteria field, the range of IP addresses specified here will not be discovered and added. Because of this, ensure that the properties of the devices specified using Set of Nodes are not specified in the Disallow Criteria field. 7. Click the Apply button. Configuring DHCP Support for Discovery DHCP discovery is the default for the Network Discovery and Node Discovery tabs. WM supports DHCP and non‐DHCP discovery: With DHCP discovery, discovered devices have their MAC address or (failing that) the DNS name for their IP address as their primary identifier (their Name, the first column in the Inventory view). If a device's IP address changes (for example, due to DHCP reassignment of its IP address by the switch that provides DHCP), WM can − use the DHCP server to obtain the new IP address of the device. − maintain its records moving forward under the new IP address. With non‐DHCP discovery, the Name of the device is its IP address. Procedure 87: To enable DHCP support 1. Perform Procedure 86: To discover only a range of addresses in a network. 2. Select DHCP. When the Start IP and End IP are specified, and the DHCP option is disabled, only the IP addresses in the specified range is attempted for discovery. If the Start IP and End IP are specified, but the DHCP option is enabled, the entire network is discovered, but the addresses within the range are discovered using DHCP discovery, whereas the addresses outside the range are attempted using non‐DHCP discovery. 3. Click the Add button. 4. Click the Apply button. 416
- 417. WM Release 4.0 User Guide Issue 3 May 2012 Performing Network Specific Discovery of SNMP Devices Wireless Manager discovery module facilitates discovering the SNMP (v1, v2c, and v3) devices in a specific network or a range of devices in a network. Discovering SNMPv1 and v2c Devices in a Network The Wireless Manager discovery engine, by default, uses the community string public and the agent Port 161 while discovering SNMP devices. But some devices in the network could use a different port and community. Procedure 88: To discover SNMPv1 or v2c devices in a network 1. Click the Network Discovery tab in the Discovery Configurator. 2. Check the Discover check box. 3. Check the SNMP check box. The SNMP Properties button becomes active. 4. Click the SNMP Properties button. The Snmp Properties dialog box is displayed. Figure 284: Snmp Properties window for network discovery 5. Click V1 or V2 version as required. The SNMP Properties tab is enabled. 417
- 418. Issue 3 WM Release 4.0 User Guide May 2012 6. Enter the read and write community of the nodes in the Read/Write Community fields. note ............. You can enter multiple read/write community strings, separated by space(s). However, doing so will slow discovery. Each string entered is sequentially attempted until a match is detected. So, enter them in the order of most common to least common. 7. Enter the port number in the SNMP Agent Port field. 8. Click OK. 9. Back in the Network Discovery tab, click the Add button, or click the Modify button if you are updating an existing entry. 10. Click the Apply button. On performing this, the discovery engine discovers those SNMP devices in the specified network with the configured community and port. Discovering SNMPv3 Devices in a Network SNMPv3 discovery for specific networks is useful under the following two situations: When only a certain network has SNMPv3 devices, sending v3 queries for all the networks to be discovered is redundant. Only specific networks should be configured for v3 discovery. The following are the configurations for this situation. Procedure 89: To discover SNMPv3 devices in a network 1. Open the Protocol tab of the Discovery Configurator. 2. Click to highlight SNMP. 3. Click the Properties button. 4. Disable SNMPv3 Discovery option in SNMP Properties dialog box (see Figure 282 on Page 411). This turns off the global SNMP v3 parameters. 5. Click the Network Discovery tab of the Discovery Configurator. 6. Select Discover. 7. Specify the IP Address and NetMask of the network that should be discovered as v3. 8. Select SNMP. 9. Click SNMP Properties. The Snmp Properties dialog window is displayed. 10. Select V3. The SNMP V3 Properties tab is enabled. 418
- 419. WM Release 4.0 User Guide Issue 3 May 2012 Figure 285: SNMP V3 Properties tab 11. Click the Add button. The SNMP V3 Properties dialog window is displayed. Figure 286: Snmp V3 Properties window, General tab 12. In the General tab, enter the security User Name, Context Name, and Agent Port number. 13. Click the Security tab. 419
- 420. Issue 3 WM Release 4.0 User Guide May 2012 Figure 287: Snmp V3 Properties window, Security tab 14. In the Security Level combo box, select from among NoAuthNoPriv, AuthNoPriv, and AuthPriv. 15. Enter the authentication protocol name and authentication password in the Auth Protocol and Auth Password fields, respectively. 16. For the AuthPriv security level, enter the privacy protocol and privacy password in Priv Protocol and Priv Password fields, respectively. 17. Click OK. 18. Back in the Network Discovery tab, click the Apply button. In this setup, the discovery engine sends SNMP v3 queries to only the specific configured networks or set of nodes. If the v3 queries sent to the specific devices in the specific network fail, then WM sends v2 and v1 queries to the devices. If any of these queries succeeds, then WM adds the successfully queried device to the appropriate SNMP version set. If the common User Name and Context Name specified should not be used, and you want to override the common configurations specified for this network, set the following network‐specific SNMP configuration. Procedure 90: To set a network-specific SNMPv3 configuration for discovery 1. Perform Procedure 82: To configure SNMP Properties on Page 411. 2. Click the Network Discovery tab of the Discovery Configurator. 3. Select Discover. 4. Specify the IP Address and NetMask for the network whose v3 configurations should be overridden. 5. Select SNMP. 6. Click SNMP Properties. The Snmp Properties dialog box is displayed. 7. Select V3. The SNMP V3 Properties tab is enabled. 420
- 421. WM Release 4.0 User Guide Issue 3 May 2012 8. Click Add. The SNMP V3 Properties dialog is displayed. 9. In the General tab, override the common configurations: ◦ For overriding user name, use the User Name option. ◦ For overriding context name, use the Context Name option. ◦ For overriding SNMP port, use the Agent Port option. 10. Click the Security tab. 11. Select the security level from Security Level combo box. 12. Enter the authentication protocol name and authentication password in Auth Protocol and Auth Password fields, respectively. 13. For AuthPriv security level, enter the privacy protocol and privacy password in the Priv Protocol and Priv Password fields, respectively. 14. Click OK. 15. Back in the Network Discovery tab, click the Apply button. It is enough to override the necessary properties alone. The values of those properties that are not specified in the Network Discovery tab will be taken from the common values. note ............. During discovery, sometimes the SNMPv3 devices are discovered as SNMPv2 devices. This occurs when the timeout or retries value is less. To avoid this scenario, set the SNMP Timeout or the SNMP Retries to more than the default optimal value based on your agent's performance. These values can be configured in the Initial Parameters dialog. See Figure 277 on Page 405. Setting Up Node-specific Discovery The discovery mechanism enables you to configure the discovery of specific devices or to discover devices with a specific port and agent, before discovering any other devices in the network. note ............. Configuring discovery means that WM is set to attempt discovery in a specified network. WM cannot actually be forced to successfully discover a device at a given IP address. Discovery fails under any of the following conditions: if no device with that address exists if the SNMP authentication fails for that device if the authentication is correct but the device is not supported by WM if there is some kind of communications problem due to errors in the data path between WM and the device. 421
- 422. Issue 3 WM Release 4.0 User Guide May 2012 Configuring Discovery of IP Addresses in a Network Follow the procedure below to configure the discovery of specific nodes before discovering any other device in the network. Procedure 91: To configure discovery of a specific IP address 1. Click the Node Discovery tab in the Discovery Configurator. Figure 288: Discovery Configurator, Node Discovery tab 2. Select the Discover checkbox. 3. Enter the IPAddress. 4. Select the SNMP Version from the drop‐down list. 5. Enter the read and write community of the nodes in the Read/Write Community fields. 6. Enter the SNMPAgentPort. 7. Click the Add button. The IP Address will be added to the table above the fields with the Discover column set to enabled (checked). This means that discovery of those specific nodes will be enabled. If the checkbox is unchecked, then the node will be ignored/undiscovered. Multiple IP addresses can be configured. 422
- 423. WM Release 4.0 User Guide Issue 3 May 2012 8. Click the Apply button. note ............. If the network corresponding to the given address is not available in the topology database, then the discovery engine will first add the network object to the database and will discover the specified IP before adding any other node in the network. Discovering Nodes from a Local Network Disabled for Discovery There is a provision to discover nodes from a local network, where the discovery of local network option is disabled (Discover LocalNet is disabled in the General tab of the Discovery Configurator). This is the same procedure as is used to discover any individual node. To set up discovery for these nodes, perform the following steps. If Discover LocalNet is off, this procedure is irrelevant. Procedure 92: To discover nodes where LocalNet is disabled 1. Click the Node Discovery tab in the Discovery Configurator. 2. Check the Discover option. 3. Configure the IPAddress according to the node you want WM to discover. 4. Enter the Community. 5. Enter the SNMPAgentPort. 6. From the drop‐down list, select the SNMP Version. 7. Configure the other data in this form. The UserName and ContextName fields are context sensitive and not enabled unless you select v3 from the drop‐down list associated with SNMP Version. 8. Click the Add button. See Figure 288: Discovery Configurator, Node Discovery tab on Page 422. 9. Click the Apply button. The above configuration can be performed to discover and add the local network and the node 192.168.4.10 (if the local network is 192.168.4.0 and is disabled). Discovering SNMP Devices with Specific Community and Agent Port By default, Wireless Manager discovery uses the community string named public and the agent port 161 while discovering SNMP devices. It is possible that some devices in the network might be using a different port and community. Procedure 93: To discover SNMP devices with specific community and port 1. Click the Node Discovery tab in the Discovery Configurator. 2. Select the Discover checkbox. 3. Enter the IP address of the device that is to be discovered. 4. Select v1, v2, or v3 from the SNMP Version field drop‐down list. 5. Enter the read community of the device into the Read Community field. The default value is public. 6. Enter the write community of the device into the Write Community field. The default value is private. 423
- 424. Issue 3 WM Release 4.0 User Guide May 2012 7. Enter the SNMP agent port of the device in SNMPAgentPort field. The default value is 161. 8. Click the Add button. 9. Click the Apply button. Discovering Specific SNMPv3 Devices SNMPv3 discovery for specific devices is useful in the following two situations. In a network where only selected devices are SNMPv3 devices, sending v3 queries for all the devices would be redundant. In this case, only selective devices should be configured for v3 discovery. The following are the configurations to be made for this situation. Procedure 94: To discover specific SNMPv3 devices 1. Click the Protocol tab in the Discovery Configurator. 2. Select SNMP and click Properties. The SNMP Properties dialog box is displayed. 3. Disable SNMPv3 Discovery if already enabled. 4. Click OK. 5. Click the Node Discovery tab in the Discovery Configurator. 6. Select the Discover check box. 7. Enter the IP address and subnet mask of the device that is to be discovered. 8. Choose v3 from SNMP Version drop‐down box. 9. Enter the security user name, context name and the port number in the UserName, ContextName, and SNMPAgentPort fields, respectively. 10. Click the Properties button. The SNMP v3 Properties dialog is invoked. 11. Enter appropriate values in the fields. 12. Click OK. 13. Back in the Node Discovery tab, click the Add button. 14. Click the Apply button. In this setup, the discovery engine will send SNMP v3 queries only to the devices that are specified in the IP Address field with the SNMP Version set to v3. If the v3 queries to these devices fail, then v2 and v1 queries are sent to the devices. If any of these queries succeed, then these devices will be added to their appropriate SNMP versions. Also for a particular device, if the common UserName and ContextName specified should not be used and you want to override the common configuration specified for this device, you can use the following device‐specific v3 configuration example. Procedure 95: To set a device-specific SNMPv3 configuration for discovery 1. Click the Protocol tab in the Discovery Configurator. 2. Click to highlight SNMP. 3. Click the Properties button. The SNMP Properties dialog is displayed. 424
- 425. WM Release 4.0 User Guide Issue 3 May 2012 4. Check (enable) SNMPv3 Discovery if it is disabled. 5. Enter the User Names, Context Name, and SNMP_Ports. 6. Click OK. 7. Click the Node Discovery tab in the Discovery Configurator. 8. Select the Discover check box. 9. Enter the IP address whose v3 configurations should be overridden. 10. Choose v3 from SNMP Version drop‐down box. 11. Override the common configurations by entering values for UserName, ContextName, and SNMPAgentPort fields. 12. Click Properties. The SNMP v3 Properties dialog is invoked. 13. Enter appropriate values in the fields available. 14. Click OK. 15. Click the Add button. 16. Click the Apply button. It is enough if you override the necessary properties alone. The values of those properties that are not specified in the Node Discovery tab will be taken from the common values. note ............. During discovery, sometimes the SNMPv3 devices are discovered as SNMPv2 devices. This occurs when the timeout or retry value is less than expected. To avoid this from occurring, set the SNMP Timeout or the SNMP Retries to more than the default optimal value based on your agent's performance. Preventing Discovery Preventing Network Discovery This procedure provides a way to exclude a network from discovery, even though it would otherwise have been discovered due to the enablement of the Discover LocalNet setting. If Discover LocalNet is off, this procedure is irrelevant. Procedure 96: To prevent the discovery of a specific network Important ........... When you uncheck the Discover option and click Apply, as this procedure does, WM discards some of the data that was configured in the Discovery Configurator for this particular network. For example, it discards the values for StartIP, EndIP, SNMP Version, Read Community, and SNMP Agent Port. So, before unchecking this option, you may want to note these values to identically populate them at some future time for re-enabling the discovery of this network. 1. Click the Network Discovery tab in the Discovery Configurator. By default, the Discover option is selected. 2. Disable (uncheck) this option. 3. Select Entire Network. 4. Configure the IPAddress and NetMask of the network that is to be bypassed by auto‐ discover. 5. Click the Add button. 425
- 426. Issue 3 WM Release 4.0 User Guide May 2012 6. Click the Apply button. note ............. This tag will not add the specified network, even if the network is reachable from the host in which Wireless Manager is running. 7. To prevent other networks from being discovered and added to the topology database, repeat this procedure for each of those networks. Preventing Discovery of a Specific Device This procedure provides a way to exclude a node from discovery, even though it would otherwise have been discovered due to the enablement of the Discover LocalNet setting. If Discover LocalNet is off, this procedure is irrelevant. Procedure 97: To prevent the discovery of an unlisted device Important ........... When you uncheck the Discover option and click Apply, as this procedure does, WM discards some of the data that was configured in the Discovery Configurator for this particular network. For example, it discards the values for SNMP Version, Read Community, and SNMPAgentPort. So, before unchecking this option, you may want to note these values to identically populate them at some future time for re- enabling the discovery of this network. 1. Click the Node Discovery tab in the Discovery Configurator. 2. Deselect the Discover checkbox (not selected). 3. Enter the IP address of the device. 4. Click the Add button. 5. Click the Apply button. You can configure the discovery engine to prevent the discovery of an element that is already known to Wireless Manager. To do so, perform the following steps. Procedure 98: To prevent the discovery of a listed device 1. Click the Node Discovery tab in the Discovery Configurator. Figure 289: Disabling discovery for a listed device 2. In the table, select the row that represents the device. The individual Discover check box in this table is read only. 3. Click the Delete button. 4. Click the Apply button. Preventing Discovery of Devices with Specific Properties The discovery engine can be configured to prevent the discovery of devices with specific properties. You can either disable the already added criteria or enter new criteria with the Allow Criteria option disabled (unchecked). 426
- 427. WM Release 4.0 User Guide Issue 3 May 2012 Example When the value of properties type is set to SUN and name set to A, discovery engine will prevent the discovery of devices whose type property is SUN and its name starts with the letter A. This example is depicted below. Procedure 99: To disallow discovery where type is SUN and name is A (example) 1. Click the Criteria tab in the Discovery Configurator. 2. From the Property Name drop‐down list, select type. 3. In the Property Value text box, type in SUN. 4. Above Property Name, uncheck Allow Criteria. 5. Click the Add button. 6. From the Property Name drop‐down list, select name. 7. In the Property Value text box, type in A. 8. Above Property Name, uncheck Allow Criteria. 9. Click the Add button. Figure 290: Criteria tab, disallow discovery for type SUN and name A 427
- 428. Issue 3 WM Release 4.0 User Guide May 2012 10. Click the Apply button. When either of the properties matches in a found managed object, the object will not be discovered. Deleting Network Entries In the Network Discovery tab of the Discovery Configurator, you can delete a specific network entry by clicking the Delete button and then the Apply button. However, deleting an entry in the Discovery Configurator does not delete that network from the database. When you restart the server without reinitializing it, the particular network will be discovered again. Similarly, when the discovery engine is scheduled for rediscovery, that network will be rediscovered (if rediscovery is enabled). Changes done in the Discovery Configurator do not delete already‐discovered networks from the database. To delete an already‐discovered network from the database, find the network in the Applications tree under InventoryNetworks and right‐click the network name. From the drop‐down list of options, select Delete Object and Traces. 14.2.4 Configuring Criteria-based Automatic Discovery To configure discovery based on Managed Object (MO) properties, the Criteria tab of the Discovery Configurator can be used. This configuration facility is used to allow or disallow the discovery of only those objects whose properties match with the specified match criteria. The Allow Criteria option is to be enabled when only those objects that satisfy the specified criteria should be discovered. If it is unchecked, then only those objects that do not satisfy the specified criteria will be discovered. The Allow Criteria contents are read as if the AND operator should apply. When multiple properties are configured in the Allow Criteria field, the objects are discovered only if all the specified properties match with those of the object found. The Disallow Criteria contents are read as if the OR operator should apply. When multiple properties are specified in the Disallow Criteria field, even if only one of the properties matches with that of the object found, the object will not be discovered. note ............. Only the name, type, ipAddress, sysOID, and the isSNMP attributes of the ManagedObject (and their derivatives) can be used with the Allow Criteria and Disallow Criteria specifications. Although you can enter other attributes in the Property Name field, the system behavior with other attributes is not tested or assured. See Figure 290 on Page 427. 428
- 429. WM Release 4.0 User Guide Issue 3 May 2012 Discovering Devices with Specific Properties Only Procedure 100: To discover devices with specific properties 1. Click the Criteria tab in the Discovery Configurator. Figure 291: Discovery Configurator, Criteria tab 2. Above Property Name, select the Allow Criteria checkbox. 3. From Property Name drop‐down list, select the property. By default, five of the Managed Object Properties (name, type, ipAddress, sysOID, isSNMP) are available. The MO property name can be any of the fields in the ManagedObject class or one of its derived classes. Multiple values can be entered, separated by spaces. 4. In the Property Value field, enter the value for the selected property. 5. Click the Add button. The property name and its respective value are added in the table above the fields. 6. Click the Apply button. Example: The following depicts the Allow Criteria set for specific name and sysOID properties. 429
- 430. Issue 3 WM Release 4.0 User Guide May 2012 Figure 292: Criteria tab, allow discovery for specific name and OID This will add only those objects whose names are x and sysOID property as .1.3.6.1.4.1.311.1.1.3.2. All other objects will be filtered out—not added to the database. Discovering Only SNMP Nodes Procedure 101: To discover only SNMP nodes 1. Click the Criteria tab in the Discovery Configurator. 2. Select Allow Criteria. 3. From the Property Name drop‐down list, select isSNMP. 4. In the Property Value field, enter true. 5. Click the Add button. 430
- 431. WM Release 4.0 User Guide Issue 3 May 2012 Figure 293: Criteria tab, allow discovery for only SNMP nodes 6. Click the Apply button. When this procedure is performed, only the SNMP nodes are discovered and added to the database. Ensure that the SNMP nodes are present and reachable from the host that runs the Wireless Manager server. Discovering an Object with a Specific IP Address Procedure 102: To discover only the object corresponding to a specific IP 1. Click the Criteria tab in the Discovery Configurator. 2. Select Allow Criteria. 3. From the Property Name drop‐down list, select ipAddress. 4. In the Property Value text box, enter the IP address. 5. Click the Add button. 6. Click the Apply button. Discovering Objects with Multiple Properties When multiple properties are specified as criteria, the objects are discovered only if all of the specified properties match with that of the incoming managed object. 431
- 432. Issue 3 WM Release 4.0 User Guide May 2012 14.2.5 Closing the Discovery Configurator When you leave the Discovery Configurator, WM opens a confirmation window: The leading statement is indicating that, after making some change, you did not click the Apply button. The message about applying to the server is asking whether you want the discovery configuration changes that you made (during this configurator session) to be used for any discovery that comes due between now and the next restart of the wmserver service on the server device: If you select No, then the next restart of the service is when WM read those changes. If you select Yes, then WM will read those changes now and apply them at the very next auto‐discovery interval. If you select Cancel, the Discovery Configurator remains open, and you have the opportunity to review changes and apply them. 14.3 Configuring Manual Discovery Network elements are discovered automatically by Wireless Manager and the discovery process is carried out in a predetermined way. Manual rediscovery would likely be useful for you only when you want to free up the node count for immediate licensing of a device. If you need to discover a node manually instead of waiting for WM to discover it automatically, see Refreshing Device Data on Page 248. 14.4 Stages of Discovery During basic discovery, WM authenticates itself to the device via SNMP and obtains a relatively small number of values from the device. Immediately following that basic discovery, WM launches deep discovery, during which it sets up such operations as performance data polling and trap handling. When you manually start or stop discovery, this typically causes WM to rediscover already‐discovered devices. During this rediscovery, WM performs deep discovery. However, deep discovery as part of rediscovery omits certain redundant aspects, such as setting up performance data polling. It does obtain fresh values for the configuration parameters. 432
- 433. WM Release 4.0 User Guide Issue 3 May 2012 14.5 Viewing the Discovery Log The Discovery Configurator includes a Discovery Log tab, where important events in the discovery process are captured with their results. Figure 294: Discovery Log These are success examples. The following are examples of discovery failure events that the log calls out. Figure 295: Failure events in the Discovery Log [02 Aug 2010 13:25:43:774] DISCOVERY(10.60.2.43:254): Unable to write to device while testing Write Community. Device is currently not writeable. Device's Write Community must be set manually. [02 Aug 2010 13:27:55:562] PING: [THREAD:: Thread-138] SNMP Ping failed for device 10.60.2.15.Snmp Properties:: ,RemotePort=161,SnmpRetries=0,TimeOut=1 [07 Aug 2010 24:22:45:483] PING: [THREAD:: statuspoll-2] SnmpPing failed for device 10.50.7.253.SnmpPing Properties:: Community=public,RemotePort=0,SnmpRetries=3,TimeOut=1 Version=v2 [06 Aug 2010 20:04:56:015] PING: [THREAD:: pool-5-thread-3] ICMP Ping failed for device 192.168.101.1 433
- 435. WM Release 4.0 User Guide Issue 3 May 2012 15 Administering Wireless Manager Security This chapter describes the various elements associated with security, such as permissions assigned to groups, users, and operations. A WM administrator can manage the following functions: provide group‐based authorization where users can be assigned to groups that have configured levels of authorization and offer specific user authorizations. provide fine‐grained access control for specific groups, views, and operations. limit the access for some users to specific sub‐sets of objects or instances (for example, user access can be limited to a specific kind of device). important ........... The order in which user permissions are set determine which permissions are allowed and which are disallowed. When users are added to a group and the later certain permissions are removed for that group, those users retain the permissions that were previously configured for them and those permissions cannot be removed from them. Similarly, when users are added to a group and then later certain permissions are added for that group, those users do not have the new permissions and cannot be granted them. Further, users who are configured for membership in more than one group whose sets of permissions differ from each other, the system should warn the administrator that a conflict exists, but the system does not. You can restrict a user from accessing specific data, as well as from viewing and working on specific network topology information. The Security Administration tool provides security‐related operations that can be configured. You can specify permission for users for only certain security operations and restrict the users from others. For example, you can allow a user to create a new group but deny that user the option to delete that group. Procedure 103: To launch the Security Administration tool 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 435
- 436. Issue 3 WM Release 4.0 User Guide May 2012 Figure 296: Initial Security Administration Tool Screen In the left panel, the Security Administration window displays a Security tree that has Groups and Users nodes. Associated with the groups and users who belong to these nodes are icons that provide immediate information about the status of the particular group or user. The following defines the range of icons that the system may display. Table 41: User icons Icon Description User account is enabled. User is disabled and cannot log in until he/she is re‐ enabled. User account has expired. User password has expired. User has been forced out and cannot log in to the server. This is similar to the disabled user status. User login is denied due to continuous unsuccessful login attempts. 436
- 437. WM Release 4.0 User Guide Issue 3 May 2012 15.1 Importing User Account Information WM allows you to import properly formatted user account data from another management system, such as Prizm or a parent instance of WM. The format is comma‐delimited CSV, with specifically allowed escape (Text Qualifier) characters. See Importing Data Files Into WM on Page 105. Table 42: Format for user account information import Column Column Position Data 1 LoginID Mandatory. 2 Group Name Optional, but the column (position) must be present. Separate multiple group names with semicolons. 3 Password The third column (position) may be null or populated. 4 Status Mandatory. Allowed content is enabled, disabled, or passwordExpired. 5 Password Age The fifth column entry of each row (record) should be the number of days in which WM should allow/prompt the user to enter a password. For security reasons, exporting systems may set this field to 0 for all exported records. Where this is the case, edit these entries to a practical number of days. Beware of saving the file in a program, such as MS‐Excel, that deposits its own end‐of‐line characters into it. Both of the following example files are as displayed in MS‐Notepad. The following is an example of a parsing error that points to the first line that ends with such an end‐of‐line character: The next example is of a file that will encounter no parsing error and of the successful Results window from the system response: Version: 1.0 Create Date: 08/17/2010 # User Account Information LoginID,Group Name,Password,Status,Password Age Mutt,test;Users,,enabled,0 Jeff,Users,,enabled,0 Batman,Admin;Users,,enabled,0 Robin,Users,,enabled,0 437
- 438. Issue 3 WM Release 4.0 User Guide May 2012 A file without the problematic end‐of‐line characters may generate other errors, such as that a user of the same name as in one of the records is already a configured user, but this kind of error would be stated in the normal Results window. An import file must exist within file browser range of the client when the import operation is invoked. To perform the import operation, see Importing Data Files Into WM on Page 105. As soon as the operation is executed in the client, user account management under the imported user configuration begins. note ............. For any entries in the Group Name (second column) that did not exist in WM before the import, WM creates a new group name, but initially assigns no privileges to it. Every user who was imported with a null password will be allowed a first login, in which they will be prompted for a new password. 15.2 Managing Users A user is an individual entity that logs into the WM and is configured to perform only a set of WM functions. Before anyone has access to WM, he or she must be added as a user to the database. After you have created users, you can add them to groups, and/or give them specific permissions unrelated to the group. 15.2.1 Limiting a User to Read Only The following sections describe both how to provision WM users as individual accounts, whose permissions will be limited by unchecked boxes in the permissions tree hierarchy (alternatively called the Operation Tree). how to associate them with the names of user groups, whose permissions to see things can be limited by custom view scopes that you define. 438
- 439. WM Release 4.0 User Guide Issue 3 May 2012 By unchecking the following items in the permissions tree hierarchy (shown in Figure 300 on Page 444), you effectively keep a user from being able to write to the system or any of the devices that the system manages: Policy Poll Filters Polling Object User Administration Polling Units AlertsAlert Filters AlertsAlert User OperationsClear Alerts AlertsAlert User OperationsAlert Pickup AlertsDelete Alerts Threshold Object TopologyModify Object TopologyDelete Object Trap Parsers and Filters Configuration Administrative Operation 15.2.2 Adding a User You can add a user whenever you need to provide someone a certain level of access to WM. By default, the new user has only login permission. You provide access to various modules by making the user a member of pre‐configured groups or by directly assigning permissions to the user. Procedure 104: To add a new user 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security Administration window, do any of the following: ◦ Select FileNewAddUser. ◦ Press Ctrl+Shift+U. ◦ Click to highlight the main branch Users in the Security tree, then right‐click it and select AddUser. tip ................ Do not click on the Users node that belongs to groups by mistake. Click on the Users node that is highlighted in this example: 439
- 440. Issue 3 WM Release 4.0 User Guide May 2012 The User Administration wizard opens to its User Description panel. Figure 297: User Administration wizard, User Description panel 3. Type the user name and password in appropriate fields. note ............. If no password is specified, the user name is set as the password. 4. Click the Next button. The wizard switches to its account panel. 440
- 441. WM Release 4.0 User Guide Issue 3 May 2012 Figure 298: User Administration wizard, account and password expiry 5. In the User account expiry section, do either of the following: (By default, the user account never expires.) ◦ If you are providing access for a limited number of days, type the number of days in which the account expires into the Day(s) field. ◦ If the account should not expire, leave the Account never expires check box checked. 6. In the Password expiry section, do either of the following: (By default, the password never expires.) ◦ If the password should expire, type the number of days in which the password expires into the Day(s) field. ◦ If the password should not expire, leave the Password never expires check box checked. note ............. User account expiry and password expiry are two different entities. This is why you can separately specify a user name and a password expiry. Password expiry is examined only when the user tries to log in. The user account expiry is examined at a regular time interval. 7. Click the Next button. The wizard switches to its permissions panel. 441
- 442. Issue 3 WM Release 4.0 User Guide May 2012 Figure 299: User Administration wizard, permissions 8. If you are associating the user with an existing group, complete the following steps: a. Check the Group based permissions check box. b. In the Assign groups for the user block, select the check boxes next to the groups to which you want to assign the user. 442
- 443. WM Release 4.0 User Guide Issue 3 May 2012 note ............. Click the arrow in the dialog to display a pop-up window that lists the corresponding permissions for the group. Based on the permissions you can assign groups to the user. ..................... This pop-up is read only. This wizard provides no opportunity to broaden or narrow the permissions of an existing group. 9. If you want to create a new group to which you want to associate the user, complete the following steps: a. In the Enter the new group name field, type a name for the new group. b. Click the Add Group button. The name of the new group is added to the Group names(s) list in the Assign groups for the user block. c. In the Group name(s) list, check the check box of the new group. d. To directly assign permissions to the user, complete the following steps: 1) Select the Direct assignment check box. 2) Click the Permissions button. The Assign Permissions dialog opens. note ............. The operations assigned to the user are specific to only that particular user. 443
- 444. Issue 3 WM Release 4.0 User Guide May 2012 Figure 300: Assign Permissions dialog continued… 444
- 445. WM Release 4.0 User Guide Issue 3 May 2012 a. Assign permissions by checking appropriate check boxes. tip ................ To select or deselect all permissions under a given node, check or uncheck the check box of that node. To initially collapse all of the main nodes, click the button in the upper right corner of the window. To re-expand them, you can click the button at any time. b. When you have finished assigning permissions (checking check boxes), click the Done button. 10. Back in the wizard, click the Finish button. The new user is displayed under the Users node in the Security tree. 15.2.3 Changing a User Profile You can change a user’s profile when necessary. You might want to change a profile to change the expiration of an account or password. Procedure 105: To change a user profile 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window is displayed. 2. Under Users in the Security tree, click to highlight the user whose profile you want to change. The security administration tabs are displayed on the right‐side. 445
- 446. Issue 3 WM Release 4.0 User Guide May 2012 Figure 301: Security administration tabs 3. Click the User Profile tab. Figure 302: User Profile tab 4. Click the Setting Profile button. The User Profile dialog opens. 446
- 447. WM Release 4.0 User Guide Issue 3 May 2012 Figure 303: User Profile dialog 5. To enable or disable the user, uncheck No change in status check box and from the drop‐ down box, select enable or disable. To re‐enable an expired user, perform the following steps: a. In the Status for the user block, uncheck the No change in status check box. b. For Select the status to be set for this user, select enable from the drop‐down list. c. Proceed with the following steps. 6. To make changes to expiration of the account or the associated password, use those areas of this form. 7. When you are finished changing the user profile, click Ok. 15.2.4 Assigning Groups to a User You can assign the users that you have created to already existing groups. Procedure 106: To assign groups to a user 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 447
- 448. Issue 3 WM Release 4.0 User Guide May 2012 2. In the Security Administration window, click to highlight the user whom you want to assign to a group. The security administration tabs are displayed on the right‐side. note ............. It is not possible to select (highlight) multiple users for this operation. 3. Click the Member Of tab. See Figure 301 on Page 446. 4. Click the Setting Groups button. The Select Groups window opens. Figure 304: Select Groups window 5. In the All Groups list, click to highlight the group name (or Ctrl+Click or Shift+Click to highlight multiple group names) to which you want to assign the user. 6. Click the button. The group name(s) are added to the Selected Groups list, and the user is assigned to those group(s) in the system. tip ................ To unassign one or more of the other groups, select (highlight) the group(s) in the Selected Groups list and click the button. 7. Click Ok. The groups that are now assigned to the user are listed in the Groups for list of the Member Of tab. 15.2.5 Changing a User Password Procedure 107: To change a user password 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 448
- 449. WM Release 4.0 User Guide Issue 3 May 2012 2. In Users node of the Security tree, click to highlight the user whose password you want to change. The security administration tabs are displayed. 3. Perform any of the following steps: ◦ Select EditChange Password. ◦ Press Ctrl+Shift+C. ◦ Under the Users node of the Security tree, right‐click the user name select Change Password from the drop‐down list. caution............... If you right-click on a user name when another user name is highlighted, the highlight does not move. However, the Change Password pop-up does not refer to the user by name. If you use the right-click access to the Change Password option, use it on only a highlighted user name. The Change Password dialog opens. Figure 305: Change Password dialog 4. Type the new password into both fields. 5. Click Ok. The new password is saved to the WM server. 15.2.6 Deleting a User You can delete a user to deny access. caution............... Do not delete the root user, or restrict its permissions or (most important) its permissions that govern the administration of other users, unless you have first created another user who has the same capabilities. If the root user is deleted, ask the WM server administrator to perform the steps under the section titled "Restoring a Deleted superuser Account" in the server administration guide. Then use Changing a User Password on Page 448 in this user guide to make any change in any account (new password, for example) so that the Security manager in WM is properly updated and the restored supersuser account reappears in the Security tree of the user interface. If the root user and all others who are allowed to edit user permissions are deleted or lose those permissions, you will not be able to create another user who has those permissions, except with the assistance of Cambium customer support staff. 449
- 450. Issue 3 WM Release 4.0 User Guide May 2012 Procedure 108: To delete a user 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. Under the Users node in the Security tree, click to highlight the user you want to delete. 3. Do any of the following: ◦ Select EditDelete. ◦ Press Alt+D. ◦ Right‐click user node on the tree and click Delete. important ........... If you right-click on a user name when another user name is highlighted, the highlight does not move. If you then select the Delete option, the confirmation pop-up does not identify the user. To ensure that you view the delete the intended user, right-click on only a highlighted user name. The system prompts for confirmation. Figure 306: Warning for user deletion 4. Click Yes. 15.2.7 Using Audit Trails If you have administrative permission in the Security area of WM, then audit trails enable you to view the operations that have been performed by a user. The audit trail identifies all operations that have been performed, the time, whether it was successful, category, and audited object. The most common use of audit trails is to examine the history of device configuration changes. You should periodically clear the trails after having reviewed them. You can view the audit trail details of all the users or a single user. sort the details by user, operation, time, status, category, and audited object by clicking the appropriate column heading. search for audit details based on the properties. clear the audit trails when you no longer need to manage them. 450
- 451. WM Release 4.0 User Guide Issue 3 May 2012 Viewing Audit Trails Procedure 109: To view audit trails of all users 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In Security Administration window, perform any of the following steps: ◦ Select ViewAuditTrails. ◦ Press Ctrl+Shift+A. ◦ Click the AuditTrails button in the toolbar. The Auth Audit Screen is displayed. 451
- 452. Issue 3 WM Release 4.0 User Guide May 2012 Figure 307: Auth Audit screen Various operations performed by the users along with the status of whether the operation was a success or failure are displayed. The operation category such as Fault, Topo, Provisioning, Configuration, Authentication, or DEFAULT is also displayed. In the case of an operation that involves any objects, the object detail is displayed. 3. View the audit trails. As needed, refer to the following sections: ◦ Interpreting Audit Entries on Page 453 ◦ Searching Audit Trails on Page 454 ◦ Viewing Audit Details on Page 455 4. To sort or reverse‐sort the list by the data in a particular column, click the heading of that column. 452
- 453. WM Release 4.0 User Guide Issue 3 May 2012 5. To clear an audit trail, click to highlight the row and click the Clear Audit button. 6. To resume viewing, click the Show All button. tip ................ To select a single audit trail, click it. For contiguous audit trails, press and hold Shift key while clicking the rows, and to select non-contiguous audit trails, press and hold the Ctrl key while clicking the rows. Procedure 110: To view audit trails of a single user 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. Under the Users node in the Security tree, click to highlight the user whose audit trail you want to view. 3. Right‐click that user name and select Audit Trails from the drop‐down list of options. important ........... If you right-click on a user name when another user name is highlighted, the highlight does not move. If you then select the Audit Trail option, the system opens displays the audit trail of the user you right-clicked on, not of the highlighted user. To ensure that you view the intended audit trail, either pay special attention to the User Name column when the Auth Audit Screen opens or right-click on only a highlighted user name. 7. View the audit trails in the Auth Audit Screen. See Figure 307 on Page 452. As needed, refer to the following sections: ◦ Interpreting Audit Entries (the next section) ◦ Searching Audit Trails on Page 454 ◦ Viewing Audit Details on Page 455 4. To sort or reverse‐sort the list by the data in a particular column, click the heading of that column. 5. To clear an audit trail from the list, click to highlight the row and click the Clear Trails. 6. To resume viewing, click the Show All button. Interpreting Audit Entries The Event Logging Extension feature in WM provides a distinctive audit entry every time that a user opens a session in the management web interface of a network element. configures the device. The audit entries for these events are listed in Table 43. Table 43: Audit entries for user activity events Event Audit Entry Launching management interface Invoked the web page URL Adding a configuration template Created template TemplateName 453
- 454. Issue 3 WM Release 4.0 User Guide May 2012 Event Audit Entry Editing a configuration template Updated template TemplateName Deleting a configuration template Deleted template TemplateName Applying a configuration template UserName executed TemplateName Searching Audit Trails 1. Press Ctrl+S. Figure 308: Search dialog for audit trails 2. In the left drop‐down menu, select from the following properties the one on which you want the search performed: 3. In the right drop‐down menu, select from the following conditions the one with which you want the search performed: 4. In the text box, type in the value. 5. To slim the search by adding another property, click the More button. 6. Repeat Steps 2 through 4 for the new property. 7. To initiate the search, click the Search button. 454
- 455. WM Release 4.0 User Guide Issue 3 May 2012 note ............. After viewing the audit details based on the Search results, you can view all the details again in the same page by clicking the Show All button in the top right corner of the Auth Audit Screen. Viewing Audit Details Some audit trails have audit details available. You can access these by 1. clicking to highlight the row of the audit trail whose details you want to view. 2. selecting ViewAudit Details from the menu. When details are available, the AlertAudit window opens to the read‐only values of the properties of the selected audit trail. Figure 309: AlertAudit window, with properties of an audit trail 15.3 Managing Groups A group is a logical collection of users grouped together to access common information or perform similar tasks. Thus, any administration done for the group is reflected in the individual members (or users) of the group. WM enables you to organize different types of users into groups so they can be classified by a set of common operations. By providing specific permissions to various groups, you can save time when creating new users. Also, the use of groups ensures consistent enforcement of access control policies that govern various classes of users. 455
- 456. Issue 3 WM Release 4.0 User Guide May 2012 caution............... This group provides the permissions to the default "root" user. Do not delete the default "Admin" group or remove user permission editing from the permitted operations for this group unless you have created another group and user with these permissions. Otherwise, you will not be able to create any new users or edit existing users. 15.3.1 Adding Groups You can add new groups when you want to provide a set of permissions that are different from those provided to an existing group. Procedure 111: To add a group 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In Security Administration window, perform any of the following: ◦ Select FileNewAddGroup. ◦ Press Ctrl+Shift+G. ◦ Right‐click the Groups node on the Security tree (located at the left side of Security Administration window) and click AddGroup. The Groups Wizard opens. 456
- 457. WM Release 4.0 User Guide Issue 3 May 2012 Figure 310: Groups Wizard, Group Description panel 3. Type the group name and click Next. The Operation Tree is displayed. Figure 311: Groups Wizard, Operations Tree 457
- 458. Issue 3 WM Release 4.0 User Guide May 2012 This tree provides the expanded list of all functional areas in WM, each of which can be assigned or disallowed for the group. 4. To collapse a parent node in the tree and hide its child nodes, click the circle to the left of its check box. 5. Check the check box of all nodes for which you want the group to have permissions. Selecting a parent node automatically selects all of its child nodes. For detailed information about the nodes, see Managing Operations on Page 467. 6. Click Finish. note ............. After a delay as WM updates its Security module, the new group is added under the Groups node of the Security tree. 15.3.2 Assigning Users to Groups By assigning users to groups, you can limit access to specific sub‐sets of the WM clients. For example, user access can be limited to specific types of devices. To provide group‐based permissions, users are assigned to specific groups. These groups provide specific permissions and levels of permissions to the assigned users. Procedure 112: To assign a user to a group 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click the group to which you need to assign users. 3. Click the Members tab. 4. Click the Setting Users button. The Select Users window is displayed. Figure 312: Select Users window 458
- 459. WM Release 4.0 User Guide Issue 3 May 2012 5. In the All Users list, click the user in All Users and click the button. 6. Click Ok. The users assigned to the group are displayed in the Members for list on the Members tab. 15.3.3 Deleting Users from Groups caution............... Do not delete the root user from the Admin group, unless you have first created another user who has the same capabilities. Procedure 113: To delete a user from a group 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click the group from which you want to remove users. 3. Click the Members tab. 4. Click Setting Users. The Select Users window is displayed. 5. Click the user to be deleted in Selected Users and click the button. 6. Click Ok. 15.3.4 Using Custom View Scopes Setting a custom view scope for a group enables you to filter the objects that are to be displayed and on which a user is permitted to do the respective authorized operations. By specifying the custom view scope criteria, you can ensure that users can view only the data for which they have authorization to perform operations. A custom view scope is as an additional layer of access control, imposed on a short list of major WM features that, without a custom view scope, would show lists or maps of all network elements, events, or alarms (for example) that are known to WM. A custom view scope is to be applied in addition to any other, perhaps more specific, user permissions. The following are the supported custom view scopes: Events Network Database Alerts Stats Admin WM checks custom view scope of a user before executing the following kinds of reports: created with user‐specified device selection, such as a device summary report on a selected device or a system report that filters devices and runs as a scheduled task. created with system‐selected devices, such as a configuration summary report or other system report that runs on demand. 459
- 460. Issue 3 WM Release 4.0 User Guide May 2012 These reports are described under Viewing a Device Summary Report on Page 223 Using Configuration Summary Reports on Page 339 Using System Reports on Page 388 Scheduling a One‐Time or Periodic Task on Page 647 Adding a Custom View Scope You can add an authorized custom view scope to a group to ensure the members of the group can view only the certain data. Procedure 114: To add a custom view scope 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click to highlight the group to whom you want to assign a custom view scope. 3. Click the Custom View Scope for Group tab. 4. From the Custom View Scope Name drop‐down menu, select the scope. 5. Click the Add AuthorizedScope button. The Scope Settings dialog opens. 460
- 461. WM Release 4.0 User Guide Issue 3 May 2012 Figure 313: Scope Settings dialog 6. In the upper Name field, type in a unique Authorized Scope Name. 7. For the Name field associated with Value, select a property name from among the following drop‐down menu choices: note ............. These are specific to each of the Custom View Scope. For instance, selecting the Events Custom View Scope and clicking Scope Settings, provides you with the property names of Event Objects. note ............. The recommended way to limit the scope to a subnet is to select network in the Name field and type in a Value that is identical to what was entered in the Network Discovery tab of the Discovery Configurator. See Figure 283: Discovery Configurator, Network Discovery tab on Page 415. note ............. To set a network for a Network Database scope, do not select parentNetwork as the property name and set the associated value to x.x.x.0. Instead, select ipAddress as the property name and set the associated value x.x.x.*. 8. In the Value field, enter the value for the property. To identify more than one property value, separate each value according to the appropriate operator in the following value operators table. 461
- 462. Issue 3 WM Release 4.0 User Guide May 2012 Table 44: Authorized Custom View Scopes value operators Value Operator Description Use an asterisk to filter on a match of zero or more characters. * (Asterisks) Example: To view all objects starting with the name test, set the property key as name and the value as test*. Use an exclamation mark to filter the search using the NOT operator. ! (Exclamation Mark) Example: To view all objects whose names do not start with test, set the property key as name and value as !test*. Use a comma to filter objects where a single property key has different values. , (Comma) Example: To view all objects with names starting with abc or xyz, set the property key as name and the value as abc*,xyz*. Use an ampersand to filter objects where a single value should be matched with many patterns. && (Ampersand) Example: To view all objects with names starting with abc and ending with xyz, set the property key as name and value as abc*&&*xyz. Use a back slash to filter objects when the name of the object itself contains a comma. This character is called an escape sequence because it avoids searching for objects, as if they (Back Slash) had two different names. Example: To view an object with name a,b, set the property key as name and the value as a,b. Use a greater than and less than signs to filter objects with numeric values within a specific range. <between> value1 Example: If object names with a poll interval value ranging between or including 300 and and value2 305 are required, set the property key as pollinterval and the value as <300 and 305>. Note that the first number is smaller than the second number. Only the values in between the given values, including the limits, are matched. 9. Click the Add button. This adds the Authorized Scope for the selected Custom View Scope of the group. You can add more than one property criteria based on your requirements. 10. Click Ok to store the custom view scope for future use. 462
- 463. WM Release 4.0 User Guide Issue 3 May 2012 Assigning an Authorized Scope for CV After you have created an authorized Custom View Scope for a group, you can assign an authorized scope in it to other groups as necessary. Procedure 115: To assign an authorized custom view scope 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click to highlight the group to which you want to assign the custom view scope. 3. Click the Custom View Scope for Group tab. note ............. The group must have permissions in the operations area in which the custom view scope was created. You can check whether it does by clicking on the Permitted Operations for Group tab. For example, if you want to assign an authorized scope for groupname2 for which the custom view scope was created in the Alerts operation area, then Alerts should be listed in that tab: 4. Click the Assign AuthorizedScope button. The Select AuthorizedScopes window is displayed. 463
- 464. Issue 3 WM Release 4.0 User Guide May 2012 Figure 314: Select AuthorizedScopes window 5. In the All Authorized Scopes list, click to highlight the scope that you want to assign. 6. Click the button. The scope is listed in both the All AuthorizedScopes list and the Selected AuthorizedScopes list. important ........... If this group has not been assigned permissions in the specific operations area of the target authorized scope, then the scope is not copied to the Selected AuthorizedScopes list, and the custom view scope is not applied to the group. When this is the case, use Procedure 120 on Page 482 to assign the operation to the group, then repeat this present procedure. 7. Click Ok. Removing a Custom View Scope from a Group You can remove an authorized Custom View Scope from a group when it is no longer valid for that group. By removing the Custom View Scope, the properties are not changed and the Custom View Scope is not deleted from the database. Procedure 116: To remove an authorized custom view scope 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click the group for whom you want to remove the custom view scope. 3. Click Custom View Scope for Group tab. 4. Click the Assign AuthorizedScope button. The Select AuthorizedScopes window opens. See Figure 314 on Page 464. 5. In the Selected AuthorizedScopes list, click to highlight the scope that you want to remove. 6. Click the button. Now the scope is listed in only the All AuthorizedScopes list. 7. Click Ok. 464
- 465. WM Release 4.0 User Guide Issue 3 May 2012 Changing Custom View Scope Properties After you have added properties to an authorized Custom View Scope, you can make changes as appropriate. note ............. If you have assigned the authorized Custom View Scope to other groups, any changes to the Custom View Scope will affect those groups as well. Procedure 117: To change the properties of an authorized scope 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click to highlight any group to whom the target authorized scope is currently assigned. 3. Click the Custom View Scope for Group tab. 4. In the AuthorizedScopes for CV list, click to highlight the Authorized Scope to be modified. Figure 315: AuthorizedScopes for CV panel 5. Click the Set Scope Properties button. The Scope Settings dialog opens. note ............. You can add a new property/value combination, remove a property, or click to highlight a property and then click the Edit button to modify its value. In this last case, the value disappears from the Value text box when you click the Edit button. If you want to restore the value but you do not remember its exact syntax, you can read it from table above the Name/Value configuration section of the dialog window. 6. Click Ok. Deleting a Custom View Scope When an authorized custom view scope is no longer valid, you can delete it from the database. After this action, you must recreate it if you ever need it again. Procedure 118: To delete an authorized custom view scope 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. In the Security tree, click to highlight any group to whom the target authorized scope is currently assigned. 3. Click the Custom View Scope for Group tab. 465
- 466. Issue 3 WM Release 4.0 User Guide May 2012 4. Click to highlight the authorized scope that you want to delete. 5. Right‐click the Authorized Scope to be deleted from AuthorizedScopes for CV list and click Delete AuthorizedView. The system prompts for confirmation. Figure 316: Warning for authorized scope deletion 6. To confirm that you want to delete it, click Yes. The authorized scope is deleted from the database and from any group to which it was assigned. 15.3.5 Deleting a Group Procedure 119: To delete a group 1. Do either of the following: ◦ Select ToolsAdministrationSecurity Administration. ◦ Press Alt+S. The Security Administration window opens. 2. From the Security tree, click to highlight the group that you want to delete. 3. Do any of the following: ◦ Select EditDelete. ◦ Press Alt+D. ◦ Right‐click the group on the tree and click Delete. The system prompts for confirmation. Figure 317: Warning for group deletion 466
- 467. WM Release 4.0 User Guide Issue 3 May 2012 caution............... If you right-click on a group when another group is highlighted, the highlight does not move and the Delete option pops up. However, neither the Delete pop- up nor the Warning pop-up refer to the group by name. If you use the right-click access to the Delete option, use it on only a highlighted group. 4. To confirm the deletion, click Yes. The group is removed from the database. 15.4 Managing Operations The Operation Tree contains a list of operations (also referred to as permissions) that WM provides by default. The operations are logically arranged in a tree structure with parent and child operations. You can add new operations when you need them and delete obsolete operations. Permission to use operations can be granted, denied, or unspecified. A typical use of unspecified permissions is to allow inherited permissions to take precedence. Another typical use of unspecified permissions is to set up an arrangement of groups, each of which specifies permissions for a particular subsystem but leaves the permissions for other subsystems to be specified by other groups, where each user is part of multiple groups. 467
- 468. Issue 3 WM Release 4.0 User Guide May 2012 15.4.1 Default Operations Assigning different operations to different users is an administrative function. The following nodes are present in the Operation Tree. This tree is presented in the wizard when a group is being configured. Figure 318: Operation Tree nodes showing default user permissions In the Permissions tree hierarchy, each major node has an associated circle. A click on the circle collapses all of the contents of the node. A check mark specifies Allowed. An X specifies Not allowed. A check in the check box of any parent node automatically checks the check boxes of all of the child nodes of that parent node. However, the checks of the child nodes are individually undoable. 468
- 469. WM Release 4.0 User Guide Issue 3 May 2012 This is for efficiency. For example, if you want to give a group all permissions under Alert User Operations except Clear Alerts, you can 1. check the checkbox of 2. click in the check box for Alert User Operations. Clear Alerts to disallow it. The following sections provide details about the nodes of the Operation Tree. 15.4.2 Configuration Table 45: Configuration options Operation Description Disabling this operation prevents the user from uploading a AAA Upload AAA Certificate certificate for a PMP 320 CPE device. Execute Task Disabling this operation prevents the user from executing tasks. Create Task Disabling this operation prevents the user from creating new tasks. Disabling this operation prevents the user from using the Audit Audit node of the Applications tree. Disabling this operation prevents the user from launching the Install Software Upgrades software upgrade tool interface. 469
- 470. Issue 3 WM Release 4.0 User Guide May 2012 15.4.3 Events Table 46: Events options Operation Description Disabling this operation prevents the user from printing the list of Print Event View Event User events. Operations Disabling this operation prevents the user from saving the events Save Events To File in file. Disabling this operation prevents the user from viewing the Get Event Parsers existing event parsers in Wireless Manager server. Disabling this operation prevents the user from modifying or Set Event Filters Event Filters adding a new event filter. and Parsers Disabling this operation prevents the user from viewing the Get Event Filters existing event filters in Wireless Manager server. Disabling this operation prevents the user from modifying or Set Event Parsers adding a new event parser. 15.4.4 Policy Table 47: Policy options Operation Description Disabling this operation prevents the user from updating an existing Update Policy policy. Add Policy Disabling this operation prevents the user from adding a new policy. Delete Policy Disabling this operation prevents the user from deleting an existing policy. 470
- 471. WM Release 4.0 User Guide Issue 3 May 2012 Operation Description Execute Policy Disabling this operation prevents the user from executing any policy. Disabling this operation prevents the user from modifying the schedule of Schedule Policy a any policy. 15.4.5 Poll Filters Table 48: Poll Filters options Operation Description Disabling this operation prevents the user from viewing the existing poll filters in Get Poll Filters Runtime Administration interface. Disabling this operation prevents the user from updating existing poll filters using Update Poll Filters Runtime Administration interface. Disabling this operation prevents the user from reloading the poll filters using Reload Poll Filters Runtime Administration interface. 15.4.6 Polling Object Table 49: Polling Object options Operation Description Disabling this operation prevents the user from viewing the existing polling Get Polling Objects objects. Change Polling Object Disabling this operation prevents the user from changing the status of a Status polling object. Delete Polling Object Disabling this operation prevents the user from deleting polling objects. Disabling this operation prevents the user from modifying existing polling Modify Polling Object objects. 471
- 472. Issue 3 WM Release 4.0 User Guide May 2012 Operation Description Add Polling Object Disabling this operation prevents the user from adding new polling objects. 15.4.7 Polling Units Table 50: Polling Units options Operation Description Disabling this operation prevents the user from adding polling units or Add Polling Units statistics. Disabling this operation prevents the user from removing an existing polling Remove Polling Units unit or statistic. Disabling this operation prevents the user from viewing the details of the Get Polling Unit polling unit or statistic. Disabling this operation prevents the user from modifying an existing polling Modify Polling Units unit or statistic. 15.4.8 Provisioning Table 51: Provisioning options Operation Description Disabling this operation prevents the user from viewing the results of a View TemplateResult provisioning operation in the ActivityList view. 472
- 473. WM Release 4.0 User Guide Issue 3 May 2012 15.4.9 Administrative Operation Services Table 52: Administrative Operation, Services options Operation Description This operation is performed to resume all Wireless Manager schedulers if Resume NMS the backup process has some errors. This operation is to start the Wireless Manager backup process. This operation suspends all the Wireless Manager schedulers. Start Backup Disabling this operation prevents the user from starting the backup process. The discovery process may be stopped due to some unforeseen problems. The Clear Discovery operation is used to resume the discovery process. Clear Discovery Disabling this option prevents the user from resuming the discovery process from the Web Client. 473
- 474. Issue 3 WM Release 4.0 User Guide May 2012 Security Administration Security Administration provides the following security‐related operations that can be configured. You can provide permission for users only for certain security operations and restrict the others. For instance, you can provide permission for a user to create a new group but he might not have the option to delete the same. caution............... it is important to always have at least one user, either direct or through groups, who has all security administration permissions. Otherwise, no one can change the permissions of another user, and the permissions structure will be frozen as it exists. 474
- 475. WM Release 4.0 User Guide Issue 3 May 2012 Table 53: Administrative Operation, Security options Operation Description Disabling this operation prevents the user from clearing Clear Audit Trails audit trails in the client. Disabling this operation prevents the user from setting Set User Profile profiles for existing users. Disabling this operation prevents the user from setting Set User Permission operations or permissions for existing users. Disabling this operation prevents the user from viewing Get List Of Users the list of users added. This applies to only the web client (the link to access the list if disabled). Disabling this operation prevents the user from User Change Password changing the password of a user. Administration Disabling this operation prevents the user from Remove User From Group removing a user from a group. Disabling this operation prevents the user from Remove Users removing a user. Disabling this operation prevents the user from Assign User To Group assigning a user to a group. Disabling this operation prevents the user from adding Add Users new users. Disabling this operation prevents the user from User Configuration accessing User Configuration link in Web Client. Disabling this operation prevents the user from Modify Group Scope Relation assigning a scope to a group in the Custom View Scope Scope for Group UI. Settings Disabling this operation prevents the user from adding a Create Scope For Group new scope or setting the properties of a scope. Disabling this operation prevents the user from adding a Add Group new group. Group Disabling this operation prevents the user from Remove Group Operations removing a group. Disabling this operation prevents the user from setting Set Group Permission permissions or operations to groups. 475
- 476. Issue 3 WM Release 4.0 User Guide May 2012 Operation Description Disabling this operation prevents the user from Remove Operation Operation removing existing operations from the Operations tree. Settings Disabling this operation prevents the user from creating Add Operation new operations in the Operations UI. Other Administrative Operations Table 54: Other Administrative Operations options Operation Description Disabling this operation prevents the user from executing any of the Template Configuration ConfigurationConfiguration Templates options for any device. Disabling this operation prevents the user from launching the Add Relationship Add Relationship utility for any device. Disabling this operation prevents the user from launching the Polling Configuration ToolsPolling Configuration interface. Disabling this operation prevents the user from launching the Log Settings HelpLog Settings interface. Configure and Receive Disabling this operation prevents the user from launching the License Notification ToolsLicense Notifications interface. Disabling this operation prevents the user from working in the Runtime Administration Discovery Configurator. Disabling this operation prevents the user from configuring the log Configure Log Levels levels (applies to only the web client). Disabling this operation prevents the user from shutting down the Shutdown Web NMS Server Wireless Manager server. Disabling this operation prevents the user from launching the Broadcast Message FileBroadcast Message interface. 476
- 477. WM Release 4.0 User Guide Issue 3 May 2012 15.4.10 Reports Configuration Reports Table 55: Configuration Reports options Operation Description Disabling this operation prevents the user running a defined Execute Configuration Report configuration report. Create or Modify Configuration Disabling this operation prevents the user from adding any new Report Template configuration report template and from changing any that already exists. Delete Configuration Report Disabling this operation prevents the user from removing a defined Template configuration report template. System Reports You can only categorically authorize or deny the permission to execute reports of these categories. 15.4.11 Threshold Object Table 56: Threshold Object options Operation Description Disabling this operation prevents the user from invoking the Thresholds and Get Threshold Object Associations dialog in the client, hence disables all of the above operations for the user. Delete Threshold Object Disabling this operation prevents the user from removing threshold objects. 477
- 478. Issue 3 WM Release 4.0 User Guide May 2012 Operation Description Disabling this operation prevents the user from modifying existing threshold Modify Threshold Object objects. Disabling this operation prevents the user from adding new threshold Add Threshold Object objects. 15.4.12 Topology Table 57: Topology options Operation Description Manage And Unmanage Disabling this operation prevents the user from managing or unmanaging Modify Objects an object or a network element. Object Disabling this operation prevents the user from starting or stopping the Start And Stop Discovery discovery process of Wireless Manager server. Disabling this operation prevents the user from executing the Export Topology Data ActionsExport Topology Data command option from the main menu. Disabling this operation prevents the user from launching the dashboard View NE Dashboard for any managed device. Refresh Node Disabling this operation prevents the user from refreshing a node. Disabling this operation prevents the user from deleting an object or a Delete Object network element. Disabling this operation prevents the user from adding a new node in the Add Node network manually. Disabling this operation prevents the user from adding a new network Add Network manually. 478
- 479. WM Release 4.0 User Guide Issue 3 May 2012 15.4.13 Trap Parsers and Filters Table 58: Trap Parsers and Filters options Operation Description Get Trap Filters Disabling this operation prevents the user from viewing the existing trap filters. Set Trap Filters Disabling this operation prevents the user from setting new trap filters. Reload Trap Filters Disabling this operation prevents the user from reloading the trap filters. Set Trap Parsers Disabling this operation prevents the user from setting new trap parsers. Get Trap Parsers Disabling this operation prevents the user from viewing the existing trap parsers. 15.4.14 Alerts 479
- 480. Issue 3 WM Release 4.0 User Guide May 2012 Table 59: Alerts options Operation Description Disabling this operation prevents the user from picking up an Alert Pickup alarm. Disabling this operation prevents the user from viewing the Get Alert Details details of an alarm. Disabling this operation prevents the user from annotating an Set Alert Annotation alarm. Disabling this operation prevents the user from saving the list Save Alerts To File Alert User of alarms in a file. Operations Disabling this operation prevents the user from viewing the Get Alert History history of an alarm. Disabling this operation prevents the user from viewing the Get Alert Annotation annotation of an alarm. Disabling this operation prevents the user from clearing the Clear Alerts alarms. Disabling this operation prevents the user from printing the Print Alert View alarms. Disabling this operation prevents the user from setting new Set Alert Filters alert filters. Alert Filters Disabling this operation prevents the user from viewing Get Alert Filters existing alert filters. Disabling this operation prevents the user from deleting an Delete Alerts alarm. 480
- 481. WM Release 4.0 User Guide Issue 3 May 2012 15.4.15 Task Scheduler Operation Table 60: Task Scheduler Operation options Operation Description Disabling this operation prevents the user from creating any Create Schedule Task task in the task scheduler utility.