System Level Information New Version: R1.2.1 Old Version: R1.2.0 Upgrade Model: N/A

Transcription

1 Acronyms API - Application Programming Interface CFP Contention Free Period CIDR - Classless Inter-Domain Routing DHCP Dynamic Host Configuration Protocol DNS Domain Name Server EWR Enhanced Wireless Router GPIO General Purpose Input / Output GUI Graphical User Interface HAS Hardware Authentication Server IAP Intelligent Access point IVSC Intelligent Video Surveillance & Control IP Internet Protocol MAC Media Access Control MEA- Mesh Enable Architecture MIB Management Information Base MiSC Mobile Internet Switching Control MPA-Mesh Positioning Application MWR Mesh Wireless Router NMI Network Management Information (Server) P2P Peer to Peer PCMCIA PR Problem Report PSK Pre Shared Key PWR Personal Wireless Router QDMA - Quad-Division Multiple Access RMM-Ruggedized Mobile Modem SBC Single Board Computer SD Subscriber Device (WMC6300/WMC7300) SNMP Simple Network Management Protocol UDP User Datagram Protocol VMM Vehicular Mounted Modem (VMM6300/VMM7300) WEP -Wired Equivalent Privacy WMB-Wireless Mesh Broadband WMC Wireless Modem Card WR Wireless Router WSM Wireless Serial Modem

2 System Level Information New Version: R1.2.1 Old Version: R1.2.0 Upgrade Model: N/A System Level 8076 Abstract: Specific version numbers of software and firmware included in this release for each system component. Reference Number: System Platforms Affected: MOTOMESH User Symptom: Description: This release includes the following components and version numbers: MEA Firmware Atheros Firmware MEA SBC SBC_ MEA Client Installation MeshTray MeshAPI Network Driver Serial Driver MeshManager MeshFlash Installation MeshFlash MeshView Installation MeshView LinkMonitor Installation LinkMonitor MPA Installation MPA Location Analyzer Installation Location Analyzer License Key Generator Installation License Key Generator Pocket PC Install MeshTray Network Driver Serial Driver MeshAPI

3 New Feature Abstract: Added subnet option with third party tools installation Reference Number: None System Platforms Affected: MOTOMESH Description: When running the Windows third party tools installation script, the user will be prompted to install either the old style subnets (10.3,10.4) or the new ones (10.24,10.49), or skip them entirely. version. Model numbers: Engineering Details: 9784 Abstract: File system corruption after Single Board Computer (SBC) upgrade on Intelligent Access Point (IAP), Enhanced Wireless Router (EWR), Ruggedized Mobile Modem (RMM), or Vehicle Mounted Modem (VMM). Reference Number: PR 1262, 1672, Severity C User Symptom: After upgrading the SBC software of an IAP, EWR, or VMM device, either locally or over the air, the user may have noticed that they have lost the ability to manage the device with Device Manager or SNMP. The user may also notice that the SBC's Sirius file system did not exist, or that files contained in the Sirius file system are corrupted. Description: Engineering Details: Customer lost the ability to manage a VMM device with Device Manager. Discovered that most of the files in the Sirius file system had become corrupted which prevented the SNMP agent from starting. The problem has been resolved with the implementation of a new file system on all devices that include an SBC (IAP, EWR, or VMM) Abstract: RedHat Linux MiSC Server experienced lockup Reference Number: FRB 3921, FRB 3987, PR 638, Severity B System Platforms Affected: MOTOMESH R1.0.1, R1.1.1, R1.1.2 None User Symptom: MiSC server becomes unresponsive and does not accept keyboard or mouse inputs. This condition can only be recovered from by physically rebooting the server hardware. Description:

4 Work Around: Upgrade to RedHat Linux ES 3 update 6 resolves this error. Upgrade procedures are now part of MiSC setup and configuration process and documentation. This update can be accomplished for existing deployed MiSC using the procedure described in the MOTOMESH 1.2 Field Upgrade Procedures manual. Replaces/Substitutes: N/A Engineering Details: The MiSC running Redhat Linux ES 3 update 3 experienced a system lockup in the field. This was due to a memory leak bug in that RedHat Linux release. This is corrected in RedHat Linux ES 3 update Abstract: Use of WEP with PSK causes Atheros Access Point to restart. Reference Number: FRB 4853, PR 1172, Severity B None User Symptom: Atheros Access Point went into exception and rebooted after client with WEP/PSK enabled tried to associate. Description: Patch from Atheros was applied to address this issue in the Atheros Access Points. WEP now functions as designed. Work Around: Replaces/Substitutes: N/A Engineering Details: 8790 Abstract: Frequency in Device Manager mislabeled Reference Number: FRB 3931, PR 1121, Severity D None User Symptom: The center channels are incorrect for the 4.9 control channel management tool. The user would notice the 2.4 and and QDMA frequencies have incorrect labels. Center channels should be listed as 4.950, 4.960, and The total frequency band is from to Description: Label is corrected to display proper frequency in Device Manager. Work Around: Replaces/Substitutes: N/A Engineering Details: 8791 Abstract: Unable to configure CIDR on VMM Reference Number: FRB CR5764, PR 1221, Severity C

5 None User Symptom: When attempting to apply CIDR IP subnet addressing the user was not able to assign subnets outside of classful range of 8, 16, and 24 bit subnets. The VMMs are now able to implement CIDR functionality. Description: Bug was fixed and now application of CIDR functions as expected. VMM can now be configured for full CIDR classless subnetting. Replaces/Substitutes: N/A Engineering Details: Bug in the algorithm was making the loop execute one less time then required, hence the problem. Bug was fixed and now application of CIDR functions as expected Abstract: TFTP upgrade fails to stop after operator aborts task via Device Manager Interface. Reference Number: PR 867, Severity C None User Symptom: TFTP session does not abort on the MEA transceiver when the abort command via SNMP is sent to the device while an upgrade is in progress. Description: The issue is fixed and now the TFTP session stops when an operator aborts the task. Engineering Details: Added ABORT support for tftp via snmp 8605 Abstract: Transceiver reset initiated by Device Manager loops several times Reference Number: PR 935, Severity C System Platforms Affected: MOTOMESH R1.0.1 None. User Symptom: Selecting the Reset option in the SD drop-down box causes the device to reset indefinitely. This behavior occurs in the SD only. Description: The bug is fixed and the SD no longer resets indefinitely Engineering Details: There will now only be a single reset command sent to a device Abstract: MeshView is reporting the wrong information of the network Reference Number: PR 926, Severity None

6 User Symptom: MeshView is representing the wrong information of the network. All the 4.9 GHz MEA transceivers of IAP's are being represented by MeshView as a Wireless router. Work Around: None. Description: The issue is closed as a non-bug issue since the behavior described is the appropriate one for a MOTOMESH device. Engineering Details: For an explanation on how to properly interpret the MeshView display, refer to the Chapter 2 - "Associated IAP" Icon description and Figure 2-2 of the MeshView User's Guide. A MOTOMESH infrastructure device consists of two QDMA (MEA 2.4 and 4.9) and two (2.4 and 4.9) components co-existing internally within one physical device. When viewing a network from the perspective of a local MOTOMESH subscriber device (either from a 2.4 or a 4.9), connectivity to the device will be via the respective QDMA component (2.4 or 4.9). Under these conditions, the route to an IAP will be displayed as passing through a QDMA component. For routing purposes in MOTOMESH, each device component is viewed as a logical device and not as a physical device of a MWR or an IAP Abstract: Device status in tree changes all devices to red when running template Reference Number: PR 940, Severity C None User Symptom: Running a template which resets the boot counts to zeros turns all devices in the tree to red. This will only happen if QDMA host components are included in the template. Description: The issue is fixed; resetting the boot counts to zero does not cause an abnormal behavior. Engineering Details: The problem was that the QDMA host component does not have the OID to set system boot counts. When all 6 components of a device where in the table, then the fact that the QDMA host did not have a value saved to it caused the confusion. Applying the reset system boot count variable will no longer cause the device icon in the tree to become red 8617 Customer/Internal: I Abstract: EWR is being represented as a WR on MeshView and on MeshTray Reference Number: PR 27, Severity D None User Symptom: EWR is being represented as a WR on MeshView and on MeshTray Description: Issue is closed; the application is behaving correctly. This is operating as designed. There is currently no difference in icons between a EWR and an MWR in MeshTray or MeshView. The EWR product is named in MEA (or WMB) only; in

7 MOTOMESH, it's simply identified as an enabled "Ethernet" service on an MWR device. If a customer is attempting to locate devices that have the Ethernet service enabled, they can use Device Manager to run a custom report to locate them. They can also look at the device configuration, General panel, "Enabled Services" field to see if the "Ethernet" service is enabled. Engineering Details: Application functions as designed Abstract: Cannot set DNS address or DNS suffix using VMM web page Reference Number: PR 819, Severity C None User Symptom: Attempting to use the VMM web page to set DNS address or DNS suffix does not work. Description: The issue is fixed, setting DNS address and suffix using VMM web page works now Abstract: Device Manager: Once a device is moved to a new device group, no option is available to move the device back to its original standard group such as Wireless Router, IAP etc. Reference Number: PR 950, Severity C None User Symptom: Once a device is moved to a new device group, no option is available to move the device back to its original standard group such as Wire Router, IAP etc. These standard groups are not available in the Move to Device Group drop-down list. Description: The issue is fixed; the option to move a device back to its original device group is added and works correctly. Abstract: Slow route change under unidirectional traffic when the link is bad. Reference Number: Severity C User Symptom: Difficulty getting data through to the when running unidirectional traffic. Description: The issue is resolved; the data gets through when running unidirectional traffic.

8 Engineering Details: Improved route change responsiveness under unidirectional traffic by enhancing link quality computation and synchronization. Abstract: Data packets fail to reach the WR mea transceiver when the packet size is between 1459 and 1472 bytes. Reference Number: PR 1285, Severity C User Symptom: In some instances, traffic traversing over the quad box side and destined to a mea device won t reach the destination. An example of this is downloading to a MEA SD data that happens to have a size between 1459 and 1472 bytes - the operation will fail. Description: The issue is resolved; packets of sizes 1459 through 1472 coming form the side reach their mea destination now.. Abstract: The IAP reboots when it s connected to a CISCO switch. Reference Number: Severity C User Symptom: When connected a CISCO switch, an IAP seems to be dysfunctional and station communication over the air or via Ethernet fails. Description: The issue is resolved; an IAP connects to CISCO switch and operates normally.. Abstract: Multicast subscription is broken when there s no IGMP router. Reference Number: Severity C User Symptom: If there is no IGMP router, the multicast subscription expires after the lifetime period has passed and the multicast subscription is lost. Description: The issue is resolved; the multicast subscription is extended before it expires and it now works as expected..

9 Abstract: 4.9 GHz backhaul uplink data rate gets stuck at 3Mbps. Reference Number: PR 1278, Severity C User Symptom: Uplink throughput is lower than expected. Description: The issue is resolved; the data rate is no longer stuck at 3Mbps but rather the higher data rates are more dominantly exercised.. Abstract: Windows 2003 Server MeshManager process failure on log out Reference Number: PR 1287, Severity C User Symptom: MeshManager Processes are stopped after logout of any administrative account from the system. Description: The issue is fixed, the services do not stop anymore after a logout and remote MeshManeger is operable.. Abstract: MOTOMESH VMM user guide needs to reflect the correct local DHCP address range. Reference Number: PR 1258, Severity C User Symptom: when using the range of DHCP addresses specified in the VMM user guide, clients attached to the MotoMesh network via the VMM fail to the reach the MiSC and hence the Internet. Description: The issue is fixed, The VMM user guide has been updated with the accurate DHCP address range Abstract: SBC web interface software upgrade does not perform reset automatically Reference Number: PR 904, Severity C None

10 User Symptom: Using the web interface to perform a firmware upgrade uploads the new firmware then brings up a page that just closes the browser. It does not reset the SBC. When the user brings the web interface back up, it displays the old firmware number and does not indicate to the user that the device needs to be reset for the new firmware to take effect. Work Around: User must reset SBC manually after upgrading via the web interface. This will be addressed in a follow on release Abstract: The "QDMA Transceiver MAC Address" is displayed incorrectly on the QDMA Host's configuration panel. Reference Number: PR 803, Severity C Applies to Device Manager's QDMA Host Configuration panel (2.4 and 4.9) User Symptom: The "QDMA Transceiver MAC Address" that is displayed in the QDMA Host's configuration panel is not the transceiver's MAC address; it's the Host's MAC address. Work Around: The QDMA Transceiver's MAC address is properly displayed in the QDMA Transceiver Status Panel. Users should ignore the value that is displayed in the QDMA Host's configuration panel. This will be addressed in a follow on release Customer/Internal: I Abstract: During heavy traffic MeshManager can't retrieve information from SD Reference Number: PR 918, Severity C None User Symptom: When very heavy traffic is being sent to a subscriber device, MeshManager may not be able to retrieve information from the SD. Heavy traffic is defined as 1000 Kbit/sec or greater. Work Around: One of the following can be applied to help solve the issue. 1. Enable QoS in the firmware. 2. Reduce or stop the traffic to the SD. 3. Retry the query. Engineering Details: This issue was only seen when an extreme amount of data was being sent to a subscriber device during a throughput stretch test. It should not be a chronic issue. If customers are reporting chronic network-wide occurrences of this issue, it should be reported to engineering (level 3 service) if none of the work arounds solve the problem.

11 8690 Abstract: MEA security password (infrastructure) and group password (P2P) are exposed. Reference Number: PR 925, Severity C None User Symptom: The MEA security password and group password on web page are not protected on WR and VMM. They are being displayed in clear text. Work Around: None 8691 Abstract: PDA - Security settings are not set on transceiver after a Reboot. Reference Number: PR 961, Severity C Only applies to transceivers in PDA devices. User Symptom: After the transceiver was rebooted, MeshTray/MeshAPI did not detect the reboot. Therefore, MeshTray was not able to send security information down to the transceiver. Work Around: To get around this problem t exit the MeshTray application and then restart it Customer/Internal: I Abstract: MeshTray shows an invalid IAP MAC address on status tab, and/or routing table in the routing tab shows invalid MAC for the IAP and next hop. This in the PDA MeshTray only. Reference Number: PR 958, Severity C None User Symptom: MeshTray for PDA may go into an invalid state where the IAP MAC address in the status tab is invalid (00:00: FF: 00:00:00) and the routing table in the routing tab shows invalid MAC for the IAP and next hop (all zeros). This issue has only been seen when receiving constant data traffic for a period of time (approximately 6 ~ 7 hours) Work Around: Follow these steps: 1. Exit MeshTray 2. Eject the PCMCIA card from the PDA 3. Reset the PDA 4. Re-insert the PCMCIA card after the PDA has restarted.

12 8699 Abstract: Authentication mode changes made via IAP web page does not take effect Reference Number: PR834, Severity C None. (IAP7300) User Symptom: Authentication mode changes made via the IAP web page does not take effect. When a change to authentication mode is made via the web page, it just goes back to the Home screen. Work Around: The change has been saved but the IAP needs to be restarted for the change to take effect Abstract: Wireless routers will not perform routing properly when used in ad-hoc infrastructure mode Reference Number: PR 959, Severity C MWR7300 User Symptom: Wireless routers will not perform routing properly when used in ad-hoc infrastructure mode. The user symptom will be poor performance when a multi-hop is used between two or more MWR7300 devices. This symptom will only occur when wireless routers are using in pure ad-hoc mode (no IAPs present) Work Around: The MWR7300 should not be deployed for use in an ad-hoc networking scenario. Where connectivity to an Ethernet-based IP host is required in ad-hoc mode, a VMM6300/7300 subscriber device should be used. Engineering Details: The sales and field engineering teams need to ensure that an MWR7300 is not deployed for use in an ad-hoc mode of operation. The transceiver will still operate without the presence of an infrastructure (e.g., without an IAP present), but performance where an ad-hoc multi-hop is possible through two or more MWR7300s will be substantially degraded. In general, the MOTOMESH system is not designed for MWR7300s to operate in ad-hoc mode, unlike the MEA 2.4 GHz network Abstract: User traffic may fail to route between a core network and a subscriber upon a failure of backhaul connectivity from an IAP Reference Number: PR 147, Severity C None (applies to IAP7300) User Symptom: User traffic may fail to route between a core network and a subscriber upon a failure of backhaul connectivity from an IAP.

13 Description: Work Around: Use backhaul devices that provide element management capabilities, and ensure an adequate fault management strategy is in place for the network operator. Status poll capabilities should be enabled using either SNMP status poll or ICMP status poll - this will ensure any loss of connectivity is immediately detected. Replaces/Substitutes: N/A Engineering Details: The IAP7300 does not presently provide the ability to disable the radio transceiver when Ethernet connectivity is lost for the IAP Customer/Internal: I Abstract: Deployment quality for location analyzer may be misleading Reference Number: PR 803, Severity D None (applies to WMC7300, Location Analyzer) User Symptom: Deployment quality indication may appear low even though all deployment conditions are optimal. Work Around: Field engineers should not rely solely on the deployment quality indication metric. The other metrics such as data rate signal level, link reliability, and IAP link quality will all be reported correctly. Engineering Details: The formula describing the "abstracted" deployment quality metric will need to be updated based on input from on-going field installation and assessment activities. This problem will be fixed in a subsequent system release Abstract: Need to enter an encryption key to provide WPA authentication Reference Number: PR 691, Severity C WPA security enabled in network. User Symptom: When configuring an IAP/MWR7300 to use WPA security for client access, a "dummy" encryption key will need to be entered to enable WPA Work Around: In order to successfully provision the devices to use WPA, the network operator must insert a dummy encryption key as part of the security baseline configuration Customer/Internal: I Abstract: Multicast transmission not supported on devices when moving to a different AP (mobile clients) Reference Number: PR 458, Severity C

14 Multicast traffic to mobile clients User Symptom: Mobile (a, b, g) clients are not able to receive multicast traffic when roaming from one AP to another AP. When a station subscribes to multicast traffic, a message is sent from the AP to which the station is associated to inform the network of the subscription. If the station re-associates to a new AP, then the network doesn t know the location until a new subscription message is sent from the new AP. Currently, once a station is subscribed the subscription messages are resent every 10 minutes. Because of this, use of multicast in non-stationary devices is not recommended. Work Around: None. The use of multicast in non-stationary devices is not recommended Abstract: 802.1p is not supported between IAP or inter switches/routers Reference Number: PR 916, Severity C Using 802.1p User Symptom: 802.1p is not supported when data traffic traverses from wireless domain through multiple switches/routers; the 802.1p tag is removed. Work Around: None Engineering Details: The Atheros WLAN driver strips the 802.1p tag before the packet is sent to the stations. Abstract: Files saved with Link Monitor v will not be usable Reference Number: Severity C User Symptom: Files saved with the older version of LinkMonitor will not be usable with this version. Work Around: None. Abstract: The help option doesn t work in LinkMonitor installer menu. Reference Number: Severity C User Symptom: The LinkMonitor.chm file is not yet included in the installer and selecting help from the menu won t do anything until it is.

15 Work Around: None. Abstract: Docking doesn t work correctly in LinkMonitor when loading a workspace Reference Number: Severity C User Symptom: When loading a workspace, any docked windows will be visible but will be in their default positions and not the position they were in when the workspace was saved. Work Around: None Abstract: A device attached via Ethernet to a MWR becomes unreachable after a certain period of time. Reference Number: PR 1289, Severity B User Symptom: Unable to reach a device attached via Ethernet to a MWR after a certain period of time. Work Around: This problem is attributed to the lack of traffic flowing between the attached device and the MWR. To eliminate the problem, traffic has to constantly flow between them. One way of achieving this is to generate constant ping traffic between the two devices. Another way to achieve it is to shorten the DHCP lease time if the attached device is using DHCP. Abstract: Static Provisioning Procedures in Mesh Camera Users Manual are incorrect. Reference Number: PR 1271, Severity B User Symptom: Current addressing procedures in the Mesh Camera User's Manuals are incorrect, the camera won t function correctly. Work Around: None

16 Abstract: MeshManager displays the wrong IP address for a Sony Camera. Reference Number: PR 1275, Severity C User Symptom: In MeshManager, when a user selects Current IP address for a device that has a static Host address, the Host DHCP address is displayed instead. Work Around: None Abstract: Pinging the SBC from the side fails when the packet size is 1427 or 1428 bytes. Reference Number: PR 1298, Severity C User Symptom: In some instances, traffic traversing over the quad box side and destined to a mea device won t reach the destination. An example of this is downloading to a mea SD data that happens to have a size of 1427/1428 bytes - the operation will fail. Work Around: None