New firmware version 2.1.2-r3 is now available. The release notes are attached with this note.
cnRanger Release Notes_System Release 2.1.2.pdf (819.5 KB)
Warning:
If cnRanger 800 BBU is not running on any 2.1.1 beta build before upgrading to 2.1.1-r1, please make a note of following warning:
Before upgrading cnRanger SM to 2.1.1-r1 from earlier releases, validate if the correct PCI is configured on all cnRanger SM. After upgrade, cnRanger SM gets attached to the PCI configured by the user in the Cell Priority List. If the Cell Priority List is empty, cnRanger SM gets attached to any PCI.
New Features
SIM Export
The sim card file can be exported from the BBU GUI page which helps to download the SIM card entries with IP addresses and data rates for data backup.
cnRanger BBU can support 5000 LTE SIM card entries/details.
To export the SIM card file, navigate to Configuration → SIM Credentials → SIM Export.
BBU supports 96 SMs per sector
BBU can support up to 96 SMs per sector. A total of 288 SMs can be supported in three sectors. Sometimes the BBU reboots with a TADD error and silent reboots are observed.
Link Test feature
This feature enables the user to run traffic between BBU and SM and report throughput and latency.
To configure Link Test feature, navigate to Tools → Link Test.
Multiple Interface Support for BBU
The Multiple Interface Support feature for BBU can enable both RJ-45 and SFP interfaces together, one for data traffic and the other interface for management traffic.
It can allow the separation or segregation of Data and Management traffic with two different interfaces. The data and management interfaces can be mapped to two different interfaces RJ-45 and SFP or both data and management interfaces can be mapped with the same interface RJ-45 or SFP interface. If data and management interfaces are mapped with the same interface RJ-45 or SFP, the IP addresses should be the same IP subnet otherwise it should be different subnet IP addresses. The configuration for multiple interfaces are shown below.
- The multi-interface configuration can allow the following configuration options.
- Both data and management interfaces mapped with RJ-45
- The data interface mapped with RJ-45 and management interface with SFP
- Both data and management interfaces mapped with SFP
- The data interface mapped with SFP and the management interface with RJ-45
- The data Interface configuration is set as Management as shown in the following figure:
The data interface configuration is set as the management interface configuration.
The multi-interface configuration feature is supported from 2.1.2.0-r3 onwards. The following steps are to be followed for upgrade or downgrade.
Upgrade to R3 or upward builds from the beta build:
Once upgraded, continue to support the single interface (RJ-45 or SFP) configuration for both
- Management and Data interface, same as beta builds.
- Configure required multi-interface configuration for Management and Data interfaces.
Upgrade to R3 or upward builds from beta build b13:
- Once upgraded, BBU configuration will be updated with the single interface configuration for both Management and Data interface same as the Management interface configuration, to have common behavior for all the beta builds.
- Configure required multi-interface configuration for Management and Data interfaces.
Downgrade from R3 or upward builds to beta builds:
- Set the single interface configuration for both Management and Data interfaces.
- Reboot the BBU and downgrade with the required beta build.
Fixed Issues
| Tracking | Product | Description |
|---|---|---|
| FURY-2794 | BBU | BBU allocated the same static IP address to two SMs. Note: While configuring the Static IP, check for the existing entries of IP addresses to avoid duplication. |
| FURY-2554 | BBU | SMs were getting dropped and not connecting back to the BBU. |
| FURY-2592 | BBU | Connected Subscriber display support 200 SMs. |
| FURY-2573 | BBU | Factory reset functionality was not working in the 2.1.2.0 builds. |
| FURY-2566 | BBU | Change of IP address from dynamic to static in SIMLIST during BBU upgrade/downgrade. |
| FURY-2683 | BBU | BBU displayed stale SMs details. |
| FURY-2688 | SM | SM sends truncated ECGI values to the domain proxy. |
| FURY-2668 | SM | SM was not connecting to the PCI of the cell priority list when the PCI lock was enabled. |
| FURY-2662 | BBU | BBU HSS database got corrupted in 2.1.2.0-build. |
| FURY-2743 | SM | CAT4 SM Syslog exiting. |
| FURY-2742 | SM | SM displayed wrong information in CLISH and GUI. |
| FURY-2755 | BBU | SM drops off possible due to MME Dynamic memory allocation failure. |
Known Issues and Limitations
| Tracking | Product | Description | Workaround |
|---|---|---|---|
| FURY-2749 | BBU | High CPU utilization is observed in CPU 0 for some time. | None |
| FURY-2433 | BBU | Core 7 crash and reboot observed with VERSION=2.1.1.0-b6 due to uplink packet handler. | None |
| FURY-2396 | BBU | Silent reboot observed after 5 days. | None |
| FURY-2788 | SM | DL MDAB errors in phy_cli due to this SM is not seeing PCELL PCI. | None |
| FURY-2280 | BBU | BBU stops transmitting and all sectors/SMs go down due to CVMX_L2C_TAD errors. | None |
| FURY-2821 | BBU | Some times statistics page of BBU GUI is taking more time to access. | None |