Está en la página 1de 24

AP 7181 3.2.3.

0-005MR Release Notes


The AP 7181 Release 3.2.3.0-005MR is a general release for the Motorola AP 7181 product. This release includes the following components and version numbers: AP 7181 Firmware 3.2.3.0-005MR These release notes are separated into 2 categories: 1) Known Issue: This is a known issue that has a workaround and may exist in a previous release. 2) Updated issue: These are issues that were noted in previous releases but have been fixed in this release.

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes

General Note:
The release 3.2.3.0-005MR or higher is the pivot image for upgrading AP 7181 to WiNG 5.4 or higher version, for more details please refer to the 7181 firmware upgrade downgrade document.

Known Issues:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

1. Undoing changes on the web interface may alter the displayed value of the Country field CCMPD01388897 AP 7181 The displayed value in the Country field is altered and incorrect In the web interface, undoing changes in the "Quick Setup" or the "System Settings" pages may cause the displayed value of the Country field to be altered. The actual country selected does not change, only what is displayed. Refresh the page by navigating to a different screen and coming back to the current one.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

2. The web interface may get disconnected after applying a new configuration CCMPD01230129 AP 7181 The web interface is disconnected and the user is logged out. When a configuration change is made via the web interface and is applied, the web interface may get disconnected and the user gets logged out. Re-launch the web interface and log back in to gain access.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: 3. Incorrect Settings are displayed for GE2 when it is configured as a LAN CCMPD01388910 AP 7181 GE2 is configured as a LAN Wrong IP address and subnet mask are displayed instead of being hidden. On the Quick Setup page in the web interface, the WAN tab is active instead of being grayed out When the GE2 port is configured as a LAN port, some of the settings that apply to the WAN will still be displayed although they do not apply to a LAN port. More specifically, the default IP address and subnet mask for GE2 are incorrectly displayed. Also, on the Quick setup page in the web interface the WAN tab is active instead of being grayed out when GE2 is configured as a LAN. Modifications on this tab may cause GE2 to unintentionally be changed back to a WAN port. When GE2 is configured as a LAN: Ignore the IP address and mask settings Avoid making modifications in the WAN tab in the Quick Setup page.

Description:

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Work Around:

4. The Security Configuration web page may become dysfunctional. CCMPD01247607 AP 7181 The AP 7181 Security Configuration has been modified and the user has logged out and logged back in without closing the web browser. Policies on the Security Configuration page cannot be created, edited, or deleted. The AP 7181 security configuration web page may fail to be modified again after altering a policy (creating, editing, or deleting it), logging out, and logging back in without closing the web browser. Close the web browser, re-open it, and modify the Security Configuration page.

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 5. SNMP OID apMeshBridgeStatsAvgMuSignal sometimes returns 0. CCMPD01253634 AP 7181 Channel Selection Setting: User selected The wrong average value is reported when using SNMP OID apMeshBridgeStatsAvgMuSignal. On occasion, apMeshBridgeStatsAvgMuSignal for an AP 7181 device returns 0. If retrieved immediately after returning 0, it usually returns a typical RSSI value. Retrieve the SNMP OID again immediately after apMeshBridgeStatsAvgMuSignal returns 0. This usually returns a typical signal value.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

6. Setting the date/time manually does not always work. CCMPD01254861 AP 7181 The date/time fields do not change after manually setting them. Old values are displayed instead. When manually setting the date/time fields using the web applet, the new values may not take effect and the old values are displayed instead. Use NTP (Network Time Protocol)

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Work Around:

7. Setting AP 7181 to factory defaults via SNMP may cause the device to get stuck in a bad state. CCMPD01276174 AP 7181 A Mesh Point (MP) is enabled and the device is set to factory defaults via SNMP. After resetting to factory defaults, the device is unreachable and unmanageable. When AP 7181 with an enabled Mesh Point (MP) is set to factory defaults, it is possible that the device gets stuck in a bad state and the only way to recover it is to power cycle it. - Disable the MP or delete it before resetting to factory defaults. - Power cycle the device when the symptom is exhibited.

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 8. It may take an idle Mesh Point (MP) few minutes to detect an interface configuration change. CCMPD01277271 AP 7181 The MP interface configuration is modified while the MP is in idle or low utilization state. The MP tables do not reflect the interface configuration change instantaneously and may display stale information for few minutes. When a MP is configured to operate on multiple interfaces, it may take few minutes for interface configuration changes (such as disabling an interface) to be detected if the MP is in idle or low utilization state. Wait for few minutes for the change to be reflected or drive more traffic through the MP.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations:

User Symptom: Description:

Work Around:

9. The Config Import/Export Status field may display a wrong status. CCMPD01289670 AP 7181 1. An Import/Export operation has been performed. 2. A configuration change has been applied. 3. AP 7181 is rebooted. 4. The Config Import/Export screen is visited. The Status field on the web applet Config Import/Export screen displays a wrong status. The Status field in the web applet Config Import/Export screen may display a stale status when the screen is visited right after the device is rebooted and an import/export operation has not been performed yet. In contrast, the Status field displays the correct status after an import/export operation has been performed. On AP 7181, the Config Import/Export Status field should be used to assess the completion of the import/export operation only immediately after the execution of the operation.

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 10. The MP/WLAN field may be blank in the show mesh command output. CCMPD01290141 AP 7181 MP is configured with multiple interfaces. The MP/WLAN field is blank in the output of the "show mesh" command. If a Mesh Points (MP) is configured with multiple interfaces and the show mesh command is run from the Command Line Interface (CLI), the MP/WLAN value may be left blank for one of the neighbor interfaces. The value of the blank MP/WLAN field can be assumed to be a MP.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

11. The "Root MPID" is incorrectly displayed in CLI. CCMPD01290613 AP 7181 The root MPID is incorrectly displayed in the CLI. After executing the "show mcx" command in the stats menu in the Command Line Interface (CLI), the "Root MPID" field is displayed as "00:00:00:00:00:00" as opposed to the actual MPID value of the MP Root that this device is connected to. The correct Root MPID can be obtained from the "Status & Statistics" page of the web interface.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Work Around:

12. A configuration change of a Mesh Point device causes neighboring Mesh Points to lose it for 60 seconds CCMPD01298498 AP 7181 AP 7181 is configured as Mesh Point. The MP is removed from the neighbor table of nearby devices and no communication can be established for 60 seconds. When the configuration is changed on a Mesh Point, the nearby devices are notified of the change; the devices remove the altered MP from their neighbor table, and they block it for 60 seconds. Wait for 60 seconds after the MP has been configured for neighboring MPs to re-establish communication with it.

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 13. Basic rate set differences may cause AP 7181 Mesh Point devices to not communicate CCMPD01298521 AP 7181 AP 7181 is configured as Mesh Point. Communication cannot be established between AP 7181 Mesh Point devices. If two AP 7181 Mesh Point devices are configured similarly but with different basic rate sets, they may not be able to establish communication. Make sure that the basic rate set matches on all of the AP 7181 Mesh Point devices.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

14. Windows style paths are not supported by firmware upgrade CCMPD01298295 AP 7181 Cannot enter backslash (\) character into firmware upgrade web page. The AP 7181 does not support path names that contain a backslash character (Windows style path names). As a result, the web page will not allow the user to enter the backslash into the path field. Move the firmware image to the root directory

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom:

Description: Work Around:

15. Number of Associated Clients on 5GHz radio is too high CCMPD01305944 AP 7181 AP 7181 is configured as a Mesh Point that uses the 2.4GHz radio The radio stats field "Number of Associated Clients" for the 5GHz radio shows a higher number of clients than are actually connected to the 5GHz radio. The amount of Mesh Points that are connected to the 2.4GHz radio is also counted as connected to the 5GHz radio in error. None

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 16. Disabled Mesh Points use up a BSSID CCMPD01319076 AP 7181 WLAN occupies the same BSSID as a Mesh Point. Unable to create a WLAN. The AP 7181 supports 4 BSSIDs per radio that are used by both the Mesh Points and WLANs. A Mesh Point, when configured to use a radio (2.4GHz or 5GHz), will be the exclusive user of one of the BSSIDs. The Mesh Point will occupy that BSSID even if it is disabled. Reconfigure any disabled Mesh Points such that they are not using any radio resources.

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

17. Incorrect reported Bit Rate when using 40 MHz channels CCMPD01323978 AP 7181 The average bit rate reported on the radio stats page is 1/2 of the actual value The average bit rate is always calculated based on data rates of a 20 MHz channel regardless of whether the actual transmissions were using 20 or 40 MHz data rates. None

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom:

18. WLANs on 2.4GHz radio appear on stats for 5GHz radio CCMPD01324826 AP 7181 If a user creates a WLAN and assigns it to the 802.11 b/g/n radio it will appear as an active WLAN under the Radio2[802.11 a/n] Statistics branch. None

Description: Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes


Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: 19. Changing country code results in incorrect placement setting CCMPD01338048 AP 7181 Country code is initially set to one of the following countries: Colombia, Indonesia, Israel, Kazakhstan, Kuwait, Namibia, South Africa, Tunisia, or Turkey. The 5 GHz radio does not function properly after changing the country code. Certain countries have regulations that forbid the AP 7181 from operating in the 5GHz band. The AP 7181 can be configured to operate in one of these countries, however, there is a known issue if the country code is changed from one that doesnt support the 5 GHz radio to a country code that does support the 5 GHz radio. In such situation the placement setting will use the incorrect default of Indoor. The AP 7181 will need to be manually set to the desired placement in order for the 5 GHz radio to function properly. The AP 7181 will need to be manually set to the desired placement in order for the 5 GHz radio to function properly.

User Symptom: Description:

Work Around:

Known Issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Work Around:

20. Cant configure Dual STP Mesh CCMPD01289217 AP 7181 Spanning Tree Protocol based Mesh. LAN1 and LAN2 are both configured to use a different STP Mesh. No IP address is assigned to the AP 7181. A Spanning Tree Protocol based Mesh can be configured to use either LAN1 or LAN2. The AP 7181 will allow the user to configure an STP mesh on both LAN1 AND LAN2, however, the AP 7181 does not support having two STP meshes active at the same time. None

AP 7181 Release Notes 3.2.3.0-005MR

AP 7181 3.2.3.0-005MR Release Notes

Updated Issues:
Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Aug-12 1 Mesh AP 7181: - AP becomes un responsive and not manageable, shows down state from wireless manager CCMPD01672081/CCMPD01655082 AP 7181

Due to a buffer leak over a period of time AP would become unresponsive to WM queries. The issue has been fixed.

Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Aug-12 2 11n clients have intermittent TCP connectivity problem with AP 7181. CCMPD01676551 AP 7181

Certain Intel 11n wireless clients would repeatedly get associated and disassociated intermittently from an AP causing slow and sluggish connection. A QoS null data was found to cause the problem. This issue has been fixed.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

10

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Aug-12 3 Update regulatory table entries for select Latin American countries CCMPD01681420 AP 7181

Regulatory settings for the following countries are now as mentioned. Colombia 1-11 Channel 36 dBm EIRP 149-161, 165 Channel 36 dBm EIRP Brazil 1-11 Channel 30 dBm EIRP 100-140 Channel 30 dBm EIRP, TPC and 27 dBm EIRP, No TPC 149-161, 165 Channel 36 dBm EIRP Haiti 1-11 Channel 36 dBm EIRP 149-161, 165 Channel 36 dBm EIRP Mexico 1-11 Channel 30 dBm EIRP 149-161, 165 Channel 36 dBm EIRP

Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

Aug-12 4 Both radios are stuck in scanning mode on country specific SKU at boot up after default config. CCMPD01683820 AP 7181 After defaulting the config the radios wont pick a channel and start beaconing On factory defaulting a device with country specific SKU, the device should select a channel and start beaconing, instead the device gets stuck in scanning state and would not enable the default wlan. The issue has been fixed

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

11

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 5 Radio Range CCMPD01383745 AP 7181

A feature has been added that allows the user to configure the range of the AP. This feature works by altering the MAC timeout values to match the time needed for messages to travel across the configured distance value. Note: The radios will still need to have adequate signal quality in order to communicate at these extended ranges. The configuration setting can be found on the web page under the heading of Extended AP Range on the Radio1 or Radio2 menu. The configuration setting can be found in the CLI under network.wireless.radio.radio1 or network.wireless.radio.radio2. The command is set range. In both cases, the range value is specified in kilometers.

Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

6 Multicast Data Rate CCMPD01461859 AP 7181

A feature has been added that allows the user to control how multicast packets are transmitted. The user can choose between range and throughput. The range option will transmit multicast packets using the lowest base data rate while the throughput option will use the highest base data rate. The configuration setting can be found on the web page under the heading of Multicast Throughput on the Radio1 or Radio2 menu. The configuration setting can be found in the CLI under network.wireless.radio.radio1 or network.wireless.radio.radio2. The command is set bcmc-tx-speed with either throughput or range as the setting. The configuration can also be found on the web page under the radio configuration per radio section

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

12

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 7 Disable IP Multicast over the Mesh CCMPD01461859 AP 7181

A feature has been added that allows the user to control how multicast packets are transmitted over the mesh. The user can choose not allow IP Multicast subscriptions from being sent over the MeshConnex Mesh. This option is only valid for IP multicast subscriptions in the range of 224.0.1.0 to 239.255.255.255. Disabling this option on a root Mesh Point will prevent IP multicast packets from being sent to any Mesh Point bound to that root Mesh Point. Disabling this option on a Mesh Point will prevent delivery of multicast packets from the mesh to any MU or Ethernet attached device. The Mesh Point will still be able to forward multicast packets to other Mesh Points. The configuration setting can be found in the CLI under network.meshconnex.edit. The command is set MC-Subscription with either enable or disable as the setting. It also can be found on the web page under Edit MeshPoint with a Multicast Subscription checkbox.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

13

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 8 Send IP multicast traffic as unicast over the mesh network CCMPD01461859 AP 7181

A feature has been added that allows the user to control how multicast packets are transmitted over the mesh. The user can choose to convert IP Multicast data to unicast data when its sent over the MeshConnex Mesh. This option increases the opportunity for packet aggregation and using higher data rates. The configuration setting can be found in the CLI under network.meshconnex.edit. The command is set mcast-as-unicast with either enable or disable as the setting. It also can be found on the web page under Edit MeshPoint with a Mulitcast as Unicast checkbox.

Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

9 5.8 GHz frequency band for Spain CCMPD01480950 AP 7181 5.8 GHz frequency band is available for use when country code is set to Spain. Support for the 5.8 GHz frequency band has been added in this release when the country code is set to Spain. This will allow the user to chose from the following channels: 5.725-5.825(channel 149-161): Max 2W EIRP. DFS & TPC. 5.825-5.850(channel 165): Max 2W EIRP. DFS & TPC. 5.850-5.875(channel 173): Max 2W EIRP. No DFS & No TPC.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

14

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Work Around: 10 SSH to AP does not work when using external RADIUS authentication CCMPD01400422 CR15085 AP 7181 The user cannot log in to the CLI when the authorization scheme is using an external RADIUS server. This issue has been fixed

Updated issue Note #: Abstract: Reference Number:

System Platforms Affected: Special Configurations: User Symptom:

11 Loss of communication with Meshed Devices CCMPD01405075 CCMPD01454733 22519683 AP 7181 Occasionally a Mesh Point could get into a state where it wouldnt allow user data to be sent even though the Mesh Point would still show up in the path table as being bound to a root. This issue has been fixed

Description: Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Work Around:

12 Nessus scan reports vulnerabilities CCMPD01415736 CR15107 AP 7181 A security scan with the NESSUS scanning tool reports medium level security risks This issue has been fixed

AP 7181 Release Notes 3.2.3.0-005MR

15

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Work Around: 13 Channel 161 is not allowed in the UK CCMPD01415922 AP 7181 The user is able to select channel 161 when the country code is set to United Kingdom. This issue has been fixed

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

14 Roam Notification always goes out with Mgmt VLAN Tag CCMPD01450187 22522881 AP 7181 MAC addresses show up on two VLANs. The AP sends out a roaming notification message when a new device associates with the AP. This message will have the source MAC address of the new device. When trunking is enabled, the message should have the VLAN tag of the WLAN, however, there was an issue where this message was being tagged with the management VLAN. This issue has been fixed

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

16

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 15 Maximum attached Mobile Unit (MU) capacity is reached unexpectedly CCMPD01490329 22620718 AP 7181 Failure to associate a client card with AP 7181 access point. Rebooting the AP may fix the issue for a period of time. Sometimes client cards will fail to associate with the AP 7181 access point for no apparent reason. The system logs may indicate the MU capacity has been reached although there are no or low number of clients attached to the AP. This issue has been fixed. Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

16 Miss-configured power limits for Mexico CCMPD01481549 CR16181 AP 7181 Country code is set to Mexico and device is operating in the 2.4 GHz frequency band. - Wrong power limits are displayed - Transmit power cannot be set to maximum regulatory power. When the country code is set to Mexico and the device is operating in the 2.4 GHz frequency band, the transmit power configuration and display reflect the wrong limits causing the device to be limited to much lower transmit power than what is allowed by regulation. This issue has been fixed.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

17

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: 17 Low transmit power for New Zealand and Malaysia CCMPD01416267 CCMPD01490332 22590205 AP 7181 Country code is set to New Zealand or Malaysia Set power is less than configured power. When the country code is set to Malaysia or New Zealand and the requested radio power is set to a value higher than 14 dBm, the transmit power will not exceed 14 dBm despite the fact that the regulatory maximum radio power, the regulatory maximum EIRP, and the radio maximum TX power are all higher than 14dBm. This issue has been fixed Work Around:

System Platforms Affected: Special Configurations: User Symptom: Description:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: Work Around:

18 The AP 7181 does not support the radar signatures required for Japan in the 5.4 GHz band and only the 2.4 GHz band is currently supported. CCMPD01499491 AP 7181 Country code is set to Japan DFS is not working correctly in 5GHz Channels. The AP 7181 does not support the radar signatures required for Japan in the 5.4 GHz band. As a temporary solution, the 5GHz Radio is disabled when the country code Japan is selected. DFS implementation will be improved in future software releases.

AP 7181 Release Notes 3.2.3.0-005MR

18

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: 19 Passphrase entered on 120-MR GUI is not compatible with other entry methods. CCMPD01474787 AP 7181 PSK Passphrase configured with GUI and CLI When using different interface (CLI or GUI) to create Mesh points on APs, even if user enters the same key, the keys will not be compatible. The device will fail to form a mesh link with other devices that share the same mesh and security configuration. An issue existed in firmware 3.2.1.0-120MR with PSK key generation when the passphrase was entered through the Web GUI (see CCMPD01474787). The issue has been fixed in 3.2.1.1-15MR and higher, however, any network that was created using firmware 3.2.1.0-120MR using the Web GUI for PSK generation is at risk. One scenario goes like this: - Network initially configured using 120MR using PSK passphrase through the GUI. - Network is upgraded to 15MR. - New device is added to the network. - The network does not recognize the key generated by the new device This issue has been fixed for 3.2.1.1-15MR or higher releases on a new deployment/re-deployment. The work around exists for existing deployment prior to the fix. Export the configuration file from any node on the existing network and copy the PSK key from the configuration file. After copying the PSK key from the configuration file paste it to a temporary text file for later use. Export the configuration from the proposed new node for the network. Replace the PSK key in the proposed new nodes configuration file with the PSK key saved to the temporary file above by pasting the PSK key into the nodes configuration file. Import the modified configuration file into the proposed new node. This procedure and a description of the issue are both covered in more detail in FSB9026.

Description:

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

19

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: 20 AP 7181 must not be used in Bolivia, Dutch Antilles, Peru, and Macedonia CCMPD01497538 CCMPD01497661 CCMPD01498242 CCMPD01497679 AP 7181 Country code is set to Bolivia, Dutch Antilles, Peru, or Macedonia The transmit power of the AP 7181 will exceed the allowed maximum regulatory transmit power for some bands in Bolivia, Dutch Antilles, Peru, and Macedonia. AP 7181 must not be used in these countries. The issue has been fixed Work Around:

System Platforms Affected: Special Configurations: User Symptom: Description:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

21 Malaysia 2.4 & 5.x displayed value for "Regulatory Max Radio Power" is incorrect CCMPD01506575 AP 7181 Country code set to Malaysia Regulatory Max Radio Power is displayed incorrectly. CLI shows incorrect value for Regulatory Max Radio Power. This discrepancy is only in the display and has no impact on the actual power setting of the radio. The issue has been fixed

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

20

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: 22 Regulatory issues corrected for listed countries (in description) CCMPD01507248,CCMPD01507271 CCMPD01507276,CCMPD01498242 CCMPD01507256,CCMPD01507647 CCMPD01506579,CCMPD01506575 CCMPD01507667,CCMPD01497531 CCMPD01497137,CCMPD01497534 CCMPD01497139,CCMPD01497614 CCMPD01497615,CCMPD01497621 CCMPD01497630,CCMPD01497633 CCMPD01497658,CCMPD01497665 CCMPD01497667,CCMPD01497669 CCMPD01497515,CCMPD01497671 CCMPD01497675,CCMPD01497678 CCMPD01507279,CCMPD01507288 CCMPD01497689,CCMPD01497693 CCMPD01497694,CCMPD01497639 CCMPD01507242,CCMPD01507251 CCMPD01497538,CCMPD01497679 CCMPD01497661 AP 7181 Regulatory Wrong max/min power values, wrong channels Various regulatory issues fixed for the following countries Argentina, Australia, Barbados, Bolivia, Brazil, British Virgin Islands, China, Christmas Island, Columbia, Costa Rica, Dominican Republic, Dutch Antilles, Ecuador, El Salvador, Falkland Islands, Guatemala, Honduras, Hong Kong, India, Indonesia, Israel, Japan, Macedonia, Malaysia, Norfolk, Pakistan, Peru, Singapore, Thailand, Trinidad, Turkey, Ukraine, Venezuela This issue has been fixed. Work Around:

System Platforms Affected: Special Configurations: User Symptom: Description:

AP 7181 Release Notes 3.2.3.0-005MR

21

AP 7181 3.2.3.0-005MR Release Notes


Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description: 23 AAA : Transferred, Received Pkts and bytes count are showing zero in Accounting STOP message CCMPD01572733 AP 7181 Wrong accounting information. Accounting STOP message will have zero for packets received and packets sent. This issue has been fixed. Work Around:

Updated issue Note #: Abstract: Reference Number: System Platforms Affected: Special Configurations: User Symptom: Description:

24 Webpage redirect feature is not working. CCMPD01547434 AP 7181 Broken hotspot functionality MU connected to a Hotspot wlan wont get the login page. This issue has been fixed.

Work Around:

AP 7181 Release Notes 3.2.3.0-005MR

22

AP 7181 3.2.3.0-005MR Release Notes AP 7181 Firmware Upgrade Procedure


PERFORM THIS UPGRADE PROCEDURE FROM THE WEB GUI. The Web GUI upgrade procedure is the only upgrade method supported for the AP 7181. Motorola does not recommend or support upgrading the AP 7181 from the command line interface.

Follow this procedure to upgrade the firmware on the AP 7181 using the Web GUI: 1. Navigate to System Configuration->Firmware Update from the AP 7181 Web GUI menu tree. 2. Enter the file name of the firmware file that will be used to perform this upgrade into the field titled Filename. 3. If the firmware file that will be used for this upgrade is located in a directory other than the TFTP or FTP root directory, enter the complete path for the file into the field titled Filepath (optional) below the Filename field. 4. Enter the IP address for the FTP or TFTP server that will be used to perform the upgrade into the field titled FTP/TFTP Server IP Address. 5. Select either the FTP or TFTP radio button to define if the firmware will be uploaded using an FTP or a TFTP server. If TFTP is selected enter the TFTP port number in the text entry box that will appear below the TFTP radio button (port 69 is the default TFTP port number). 6. Confirm the check box located next to the Reboot After Download caption is unchecked. 7. Enter the following FTP parameters if FTP was chosen in step 5 above (if TFTP was chosen, username and password are not required): a. Username - Specify a username for the FTP server login. b. Password - Specify a password for FTP server login. 8. Click the button titled Apply located below the Status window at the bottom of the Web GUI to set all of the above parameter changes.

AP 7181 Release Notes 3.2.3.0-005MR

23

AP 7181 3.2.3.0-005MR Release Notes


9. Click the button titled Perform Update located above the Status window to begin the upgrade. 10. A dialogue will appear requesting you to select Yes or No to the following question: Uploading of the firmware image may take up to 3 minutes. After successful upload of the image you must restart the device for the uploaded firmware to take effect. Do you want to continue? click Yes, the upgrade will now begin. Be careful there is no power interruption to the AP 7181 during this and the following steps of this procedure. 11. The Status window above the Apply button will display the firmware file transfer progress, it will then display Completed when the firmware file is completely transferred to the AP 7181 from the TFTP or FTP server. If the firmware file upload is unsuccessful an error message describing the reason for the failure will be shown in the Status window. If a error message is shown to indicate the upload failed please check steps 2 thru 7 above. 12. Navigate to theSystem Configuration->System Settings dialogue and click the button titled Restart AP-71XX at the bottom of the page. A dialogue confirming that you wish to restart the AP 7181 will appear, click Yes. The AP 7181 will now reboot. The firmware upgrade process will now take place during the reboot process, it can take several minutes for this process to complete while rebooting. 13. After the AP 7181 completes the firmware upgrade and is fully rebooted, the Web GUI will be available. Clear the browser cache and login to the AP 7181 and navigate to the System Configuration->Firmware Update dialogue. Next to the line titled AP-71XX Version the new firmware version should be displayed.

AP 7181 Release Notes 3.2.3.0-005MR

24

También podría gustarte