# cnWave System Release 1.2.2.1 has been released

**URL:** https://community.cambiumnetworks.com/t/cnwave-system-release-1-2-2-1-has-been-released/94340
**Category:** cnWave 60 GHz
**Tags:** release-notes
**Created:** [July 31, 2023, 6:40pm UTC](https://community.cambiumnetworks.com/t/cnwave-system-release-1-2-2-1-has-been-released/94340 "2023-07-31T18:40:20Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Kiran\_Avva](https://d10gw3vjmzyp8.cloudfront.net/letter_avatar_proxy/v4/letter/k/cc9497/32.png) [@Kiran\_Avva](https://community.cambiumnetworks.com/u/Kiran_Avva)
#### Post date: [July 31, 2023, 6:40pm UTC](https://community.cambiumnetworks.com/t/cnwave-system-release-1-2-2-1-has-been-released/94340/1 "2023-07-31T18:40:20Z")

</div>

**cnWave 60GHz System Release 1.2.2.1** has been released. Find the firmware and full release notes at [https://support.cambiumnetworks.com/files/60ghz-cnwave/](https://support.cambiumnetworks.com/files/60ghz-cnwave/)

👉 Upgrade the External E2E controller first and then the nodes  
👉 When using onboard controller, its recommended to upgrade the whole mesh together.  
👉 Upgrading to **1.1.0-r4 OVA** is recommended (if using External E2E)

### Features introduced in System Release 1.2.2.1

- Enhanced link diagnostics - Beam angle statistics
- Additional scan scheduling option for beam adjustment
- iPerf tool for testing network throughput
- New metrics added to the Links statistics
- Monitor IPv4 Gateway
- Parameters for disabling UI and SSH access
- Interference mitigation improvement
- New remote debug commands
  1. Show Wired Interface State Changes
  2. Show ipv4 neighbors
  3. Show ipv6 neighbors

- Enhanced CN channel scanning and configuration options
- DN Channel rescan
- With upcoming cnMaestro 4.1.0 (Maps) and Release 1.2.2.1, following tools are available
  1. Node Throughput
  2. Link Throughput
  3. Trace Current best routes to PoP from a DN or CN

### Other Enhancements / Improvements in System Release 1.2.2.1

| Tracking number | Product | Description |
| --- | --- | --- |
| 60 GHz cnWave-3656 | All | The CN or DN’s reachability of Onboard Controller in a multi-PoP topology has been improved, especially when a PoP to PoP wired communication is down. |
| 60 GHz cnWave-3633 | All | Following PoP reachability-specific watchdog timers have been made configurable: envParams.CAMBIUM\_POP\_UNREACHABLE\_REBOOT\_ TIMEOUT\_INTERVAL: When a PoP that has been reachable disappears, reboot after this timeout period (seconds). envParams.CAMBIUM\_NO\_POP\_SINCE\_REBOOT\_ TIMEOUT\_INTERVAL: If there is no PoP reachable since boot, then reboot after this timeout period (seconds). |
| 60 GHz cnWave-3619 | All | Improvements have been made related to GPS stability. |
| 60 GHz cnWave-3468 | All | A configurable option has been added to disable the downlink Multicast flood. |
| 60 GHz cnWave-3416 | All | An option has been added in the UI to disable the rescan of CN channel. |
| 60 GHz cnWave-3415 | All | Following enhancements have been made for an easy access of the Recovery mode UI: Increased the time window during which the Recovery mode UI can be accessed. Improved responsiveness to HTTP requests on active Ethernet connections. |
| 60 GHz cnWave-3400 | All | The filed diags collection has been improved. |
| 60 GHz cnWave-3356 | All | The iPerf tool has been added to the Tools page of the E2E Controller device UI. |
| 60 GHz cnWave-3348 | All | Improvements have been made to Ignition algorithm for allowing all links to get a fair ignition chance. |
| 60 GHz cnWave-3344 | All | An event was added when the Gateway was unreachable. This has been enhanced now. |
| 60 GHz cnWave-3339 | All | The robustness of the link ignition has been improved. |
| 60 GHz cnWave-3317 | All | Timed out UI sessions were found, earlier, when login was disabled. This has been enhanced now. |
| 60 GHz cnWave-3260 | V2000 | The V2000 throughput has been improved when V2000 acts as relay in a Daisy Chain topology. |
| 60 GHz cnWave-3228 | All | The disableCNChannelRescan configuration parameter has been added to control the CN rescan functionality. By default, the value of this parameter is true. The CN rescans all channels if the link goes down for 120 seconds. |
| 60 GHz cnWave-3221 | All | Updates have been made to improve the link stability at MCS levels 10, 11, and 12. |
| 60 GHz cnWave-3183 | V3000 and V5000 | The stability for 1 Gbps SFP connections has been enhanced. |
| 60 GHz cnWave-3179 | All | If PoP was unreachable for an hour, the node rebooted periodically. This has been enhanced now. |
| 60 GHz cnWave-3169 | All | A support has been added for Singapore country (ROW list). |
| 60 GHz cnWave-3114 | All | An image file truncated during download, earlier. In this release, the software upgrade reliability has been enhanced. |
| 60 GHz cnWave-3090 | All | A security warning has been added if passwords are default. |

### Problems corrected in System Release 1.2.2.1

| Tracking number | Product | Description |
| --- | --- | --- |
| 60 GHz cnWave-3714 | All | In the Onboard Controller network, when seed prefix was modified, the software upgrade of CNs failed. |
| 60 GHz cnWave-3710 | All | When the antenna alignment was complete, ignition of the link stayed disabled. This was observed, occasionally. |
| 60 GHz cnWave-3687 | V2000 | V2000 did not respond to IPv4 pings that were destined to it. |
| 60 GHz cnWave-3682 | All | Stale Layer 2 tunnels were observed on PoPs. |
| 60 GHz cnWave-3613 | V3000 | When multiple relay ports were enabled on a V3000 device, the management IPv4 of CNs was not accessible. |
| 60 GHz cnWave-3530 | All | E2E controller’s memory consumption increases over time. |
| 60 GHz cnWave-2360 | V3000 and V5000 | When the SFP module was present and the SFP link was not used, the device rebooted periodically. |
| 60 GHz cnWave-2850 | All | The E2E Controller device crashed while deleting a node. |
| 60 GHz cnWave-3162 | All | The UI did not support or enable ignition ever after the antenna alignment was complete. |
| 60 GHz cnWave-3213 | V3000 and V5000 | When a node was left idle for few hours, the Management IP was not accessible while accessing the node through a main port. |
| 60 GHz cnWave-3276 | V1000 | The device type was shown as CN on enabling E2E Controller for V1000. |
| 60 GHz cnWave-3301 | All | Prevented packets from being leaked, indefinitely, when there was no link to an installed SFP. |
| 60 GHz cnWave-3322 | V5000, V3000, and V2000 | Minion continuously restarted when a V5000, V3000, or V2000 device was set to factory default and configured as DN using the local UI. |
| 60 GHz cnWave-3349 | V5000 | Toposcan stopped traffic on the neighbour V5000 sector. |
| 60 GHz cnWave-3409 | V1000 | The iPerf throughput for V1000 was low on running the iPerf tool from the device UI (Tools page). |
| 60 GHz cnWave-3423 | All | The WSEC PSK password did not allow or support the $ character. |
| 60 GHz cnWave-3427 | All | In Fig O topology deployments () with wsec enabled, one of the wireless links did not come up. |
| 60 GHz cnWave-3466 | All | Controller crashed when a non-existing node was deleted using API. |
| 60 GHz cnWave-3477 | All | The VLAN traffic was not found in the allowed list due to which it was not dropped. |
| 60 GHz cnWave-3487 | V2000 | The V2000 node rebooted while downloading the field diags. |
| 60 GHz cnWave-3502 | All | A momentary drop was observed (for 10-20 seconds) in the CN traffic when a new CN link was added to PoP. |
| 60 GHz cnWave-3505 | All | Configuration snapshots taken by E2E Controller filled the docker file system. |
| 60 GHz cnWave-3540 | All | With Onboard Controller, when a new pop was added from cnMaestro, both the PoPs were not in the same IPv6 subnet. |
| 60 GHz cnWave-3549 | All | During the heavy bidirectional UDP traffic, the onboard PoP was unresponsive. |
| 60 GHz cnWave-3550 | All | SNMPv2 MIB: The sysName OID has been corrected to use node name instead of node MAC. |
| 60 GHz cnWave-3605 | V5000 | For V5000, the EIRP values were incorrect when sector 1 was configured with channel 1 and sector 2 was configured with channel 4. |
| 60 GHz cnWave-3606 | V2000 | When a client roamed from one V2000 to the other V2000 in a PtP connection, the client experienced drop of packets up to 30s. |
| 60 GHz cnWave-3622 | V5000 | V5000 as a PoP did not onboard cnMaestro after it was upgraded. It got stuck at the time of reboot. |
| 60 GHz cnWave-3200 | All | Restarted the DHCPv6 relay on encountering errors while sending the uplink packets. |
| 60 GHz cnWave-3325 | All | Synchronized Link and Node reporting status, which stopped link up and node down reporting issues. |
| 60 GHz cnWave-3330 | All | Corrected sysDescr and sysObjectID SNMP OIDs. |
| 60 GHz cnWave-3334 | All | On adding the primary link (after deleting it), the backup link got disconnected and CN moved to the primary link. |
| 60 GHz cnWave-3344 | All | Added an event if Gateway was unreachable. |
| 60 GHz cnWave-3347 | All | All disabled links got enabled after the PoP rebooted. |
| 60 GHz cnWave-3136 | V2000 | With the Aux port negotiated to 2.5 Gbps, the Main port did not work at 1 Gbps for V2000. |
| 60 GHz cnWave-28605 | All | Sometimes, the external E2E Controller consumed high CPU and memory when it was upgraded to 1.2.2 release version. |
| 60 GHz cnWave-3272 | All | In some instances, CN lost WSEC configuration while scanning. |
| 60 GHz cnWave-3141 | All | Deleted the routes used by DHCPv6 relay when a CPE interface was down. This behaviour can be turned off by setting the CAMBIUM\_DHCPv6\_DELETE\_ASSIGNMENTS\_CPE\_DOWN parameter to false. |
| 60 GHz cnWave-3152 | All | The UI did not display the drop-down list options for Select Logs and Select Nodes parameters (on the Engineering Logs page) when the browser was refreshed. |
| 60 GHz cnWave-3182 | All | Added timestamps to the DHCPv6 relay logs. |
| 60 GHz cnWave-3191 | V2000 | The Link Uptime statistics was incorrectly updated on the UI in case of a hard reboot of the PoP node. |
| 60 GHz cnWave-3200 | All | Added a restart mechanism to DHCPv6 Relay when it was unable to relay messages to the DHCPv6 server. |
| 60 GHz cnWave-3222 | V2000 | Factory reset did not disable E2E Controller. |
| 60 GHz cnWave-3245 | All | The UI allowed configuring special characters for the Max EIRP value on an individual node. |
| 60 GHz cnWave-3250 | V2000 | The V2000 throughput was lower in Layer 3 mode or when it was a DN in a mesh topology. |
| 60 GHz cnWave-3252 | V2000 | Sometimes, the Main port of V2000 did not pass traffic even if it was linked up at 1000M (on rare occasions).This event occurred following after a 10M link transition (UP and Down). |

## Known Issues or Limitations in System Release 1.2.2.1

| Tracking Number | Product | Description |
| --- | --- | --- |
| 60 GHz cnWave-2896 | V2000, V3000, and V5000 | A node changing from DN to CN or vice versa requires reboot. |