calix cms release notes 15.0 - paul t clarkpaultclark.com/network/calix/cms r15.0.174 release...

December 20, 2017

Proprietary Information. Not for use or disclosure except by written agreement with Calix.

© Calix. All Rights Reserved. Part # 240-01199-11

CMS R15.0.174 Release Notes

Preface

This document constitutes the release notes for Calix Management System (CMS) version 15.0.174. These notes provide specific information regarding functionality of this release. For information about using CMS and/or managing Calix network elements (B6, C7, E-Series, F-Series, and AE ONT), see the Calix user documentation, accessible from My Calix.

CMS 15.0.174 supports full FCAPS management of E7 R3.2 firmware, which provides incremental feature support on E7-2 and E7-20, and derivative platforms such as the E3-48C and E5-48.

See the New Features or Enhancements below for details about what is introduced in this release.

https://www.calix.com/my-calix/home.html

Calix CMS R15.0.174 Release Notes of 25



What’s New in CMS Release 15.0

The new features and enhancements in CMS 15.0 are listed below.

New Features or Enhancements

Calix

Platform

CMS Support Introduced in 15.0

E7 For E7 R3.2

Platform Features

• Merge of E7 R2.6.60 and R3.1.20 feature sets and software release streams

• DHCP Hot Swap

• E7 Security Profiles

• DHCP Option 82 insertion across all platforms

VDSL2 Features

• DELT support on CLI and Embedded Web Interface

• CAT3 Power Shutdown for E3-48 r2 Overlay

• SNMP Bonded MIB support for TOLLGRADE

GPON Features

• Profile and Product support for ONT 823G (GPON, 4 GE, 2 POTS, Wi-Fi, RF)

For E7 R3.1

Platform Hardware

• Introduces E7-20 GPON-16x line card

• Support for E7-20 FTA2 in E7-20 systems without SCP2 control

Platform Features

• Merge of E7 R2.6 and R3.0 feature sets and software release streams

• Introduces a DHCP Authentication Test

• Introduces a PPPoE Authentication Test

• Support for creating PPPoE and DHCP data services on a single VLAN/port

• Support of IP-based hashing for LAG

• Introduces a description option for external alarm input/output pins




Calix

Platform

CMS Support Introduced in 15.0

Platform Changes

• P-Series 700GE/GX ONT firmware is no longer bundled with E7 system software

VDSL2 Features

• Supports voice ports returning to service after foreign voltage detection

GPON Features

• Support for T063G, T063G II ONTs

• Support for viewing multicast channels that an ONT has joined

• Packet Cable support

• Unique MAC address per eSAFE device associated on a per interface basis supported on 800 GigaCenters

• E7-20 GPON-16x line cards support:

o Downstream CIR for individual services on E7-20 GPON-16x PON interfaces

o Up to 1:128 split ratio on the GPON-16x PON interfaces

o Up to 2048 ONTs supported per GPON-16x line card




CMS Network Element Support Matrix

CMS R15.0.174 supports network management for the following Calix network elements running the related platform software releases:

Supported Calix

Network Elements

Platform Software

Versions Supported

Calix B6 8.0, 7.3, 7.2 [*][†]

Calix C7 9.0, 8.0.3xx, 8.0, 7.2

Calix E7 3.2,3.1, 3.0‡, 2.6, 2.5, 2.4, 2.3

Calix E5-30x, E5-520 1.1, 1.0

Calix E5-400 2.1, 2.0

Calix E3-48C 2.6, 2.5, 2.4, 2.3

Calix E5-48, E5-48C 2.6, 2.5, 2.4, 2.3

E3-48 r2, E3-48C r2 2.6

Calix E5-120, E5-121, E3-12C 4.1, 3.1

Calix E5-110, E5-111 4.0, 3.0

Calix E3-48 2.0, 1.0

Calix 700/800 Active Ethernet ONTs 3.1, 3.0, 2.2

Calix 2300 Active Ethernet ONTs 4.1, 4.0

Calix F5 4.0, 3.1

[*] Refer to Managing a B6 Network from CMS for instructions to perform a database migration of managed B6 elements from OccamView to CMS. (B6 nodes must be running R7.1 or higher.) [†] CMS supports limited management for some legacy B6 line units running software versions 6.2R4, R5.5, 5.2R2, on a per model basis, where support requires the latest software version supported per B6 model. Units on release R6.2R4 and below require manual trap registration. For units on R5.5 & R5.2, CMS provides alarm aggregation and topology management only. ‡ For E7-20 products only.




Installations and Upgrades CMS R15.0 supports new installations and upgrades, as described in the following table.

As a general best practice for CMS, Calix recommends using the latest GA software version to assure full FCAPS support for the latest features and enhancements on managed Calix network elements, as well as to leverage the latest CMS features and software robustness.

If you are upgrading, determine the upgrade path and then the required CMS installer files from the required CMS installer files from the Calix Software Center. For upgrade instructions, refer to the CMS Installation and Upgrade Guide for Linux or Solaris, depending on your host server operating system. (For older versions of CMS on the upgrade path, you may need to request access to the software.)

Current CMS Version

Upgrade Path

CMS R15.0.xxx

CMSR14.1.xxx

CMS R14.0.xxx

Perform a full upgrade to R15.0.174.

CMS R13.1.xxx

CMS R13.0.xxx

Perform a full upgrade to R14.0.xxx before upgrading to R15.0.174.

CMS R12.1.xxx or below

Review this Quick Tip for further assistance.

https://calix.wistia.com/medias/63cy6tkl23

https://calix.wistia.com/medias/63cy6tkl23

https://www.calix.com/bin/calix/servlets/docdownload?fileId=/content/dam/calix/doc-library/software/cms/bulletins/quick-tips/qt-16-002/cms-qt-16-002-cms-versions-upgrade-paths.pdf




CMS Server System Requirements

Before proceeding with upgrades or installation, note the following:

• Very Important! For CMS R11.2 and higher, Calix increased the server specs to require a minimum 6GB of RAM, with 12GB recommended.

To ensure acceptable performance standards, Calix introduced a semantic check that blocks software upgrades to CMS R12.0.217 and higher if the CMS server is not equipped with at least 6GB of RAM. Attempts to upgrade on servers with less than 6GB of RAM will be prevented. For more information, reference this service bulletin.

• Carefully review the Hardware Recommendation for CMS Server table below before upgrading or installing to ensure optimal CMS performance.

• For medium and large deployments using an Oracle database, Calix recommends optimizing the database tablespaces by creating separate tablespaces for PM and Log data. For instructions, see the Calix Management System (CMS) Installation and Upgrade Guide.

• Calix offers CMS installation packages for both 32-bit and 64-bit Linux servers. These independent CMS versions are optimized for the Linux OS on which CMS is installed. Thus, Calix recommends installing the appropriate version of CMS per server OS.

If you need assistance in determining if your Linux OS is 32-bit or 64-bit, please refer to this KB article or contact the Calix Technical Assistance Center.

• RHEL server operating system must have an active subscription.

• Running multiple CMS applications on the same server is not supported.

• A minimum of 4 virtual CPU are required for virtual machine (VM) installation.

https://www.calix.com/bin/calix/servlets/docdownload?fileId=%2Fcontent%2Fdam%2Fcalix%2Fdoc-library%2Fsoftware%2Fcms%2Fbulletins%2Fservice-bulletins%2FCMS%20SB-14-002%2FCMS_SB-14-002_12.x_minRAM.pdf

http://community.calix.com/t5/CMS-Knowledge-Base/How-to-determine-whether-a-given-Linux-is-32-bit-or-64-bit/ta-p/30211

http://community.calix.com/t5/CMS-Knowledge-Base/How-to-determine-whether-a-given-Linux-is-32-bit-or-64-bit/ta-p/30211




Recommendations for CMS Server:

Calix Recommends

Small Deployment (32bit)

Small Deployment

(64bit)

Medium Deployment

Large Deployment (64bit only)

Network Size 1-1000 NEs 1-1000 NEs 1-2000 NEs 1-5000 NEs

AE ONTs Up to 20,000

Subscribers Up to 100,000 Up to 100,000* Up to 500,000 Up to 2,000,000

OS Platform CentOS/RHEL 6/7

x86 32bit CentOS/RHEL 6/7

x86 64bit

CentOS/RHEL 6/7 x86 64bit

Solaris

CMS Type 32bit 64bit

CPU Intel Xeon E5-2440

1 x 4 cores

Intel Xeon E5-2660,

2 x 8 cores

Intel Xeon 7500 series or E7 series,

4 x processors

SUN SPARC T4-1 SUN SPARC T4-2

Physical RAM

12GB Minimum 32GB Minimum 64GB Minimum

HDD 2 x 100GB Minimum 4 x 300GB 4 x 300GB Minimum

SWAP Size 0.5x RAM - 1x RAM size

Platform Server Example

DELL PowerEdge R430

DELL PowerEdge

R620

DELL PowerEdge R920 or

SUN SPARC T4 Series

* Small deployment server can support up to 200,000 subscribers with extra configuration enhancements. See below for details.

Small Deployment

Up to 100,000 subscriber lines

Linux Platform

Dell PowerEdge 430 Server

• One Intel Xeon E5-2440 1 x 4 cores processor

• 12 GB memory

• Two 15K RPM SAS drives, 146 GB or higher, RAID 1




RHEL Server or CentOS 6.x, 7.x

Postgres RDBMS (Bundled with CMS)

Note: Calix offers the CMS Appliance server meeting the system requirement above. For details, see the Calix CMS Appliance datasheet.

The Dell PowerEdge R430 Server can support up to 200,000 subscriber lines by upgrading these specifications:

• Up to two Intel Xeon E5-2440 1 x 4 cores processors

• 24 GB memory

• Two or four 15K RPM SAS drives, 146 GB or higher, RAID 1 or 101

Medium Deployment

Up to 500,000 subscriber lines

Linux Platform

Dell PowerEdge R620 Server

• Two Intel Xeon E5-2660eight-core processors

• 32 GB memory

• Up to fourteen 15K RPM 2.5" SAS drives or SSDs, RAID 10

RHEL Server or CentOS 6.x, 7.x, 64-bit operating system

Postgres (Bundled with CMS) or Oracle 10g/11g RDBMS (Oracle 11g recommended for managing more than 250,000 subscriber lines)

Large Deployment

Up to 2,000,000 subscriber lines

Linux Platform

Dell PowerEdge R910 Server

• Four Intel Xeon 7500 or E7 Series processors

• 64 GB memory

• Sixteen 15K RPM 2.5" SAS drives or SSDs, RAID 10

RHEL Server or CentOS 6.x, 7.x, 64-bit operating system

Oracle 10g/11g RDBMS (Oracle 11g recommended for managing more than 250,000 subscriber lines)

Solaris Platform

Sun SPARC T4 Series Server—Contact Calix for recommended configuration Oracle 10g/11g RDBMS (Oracle 11g recommended for managing more than 250,000 subscriber lines.




CMS Client System Requirements

PC/Workstation

• Intel Core 2 Duo or better processor

• 800 MB Memory required for CMS Desktop application

• 2 GB RAM or more recommended

• Display resolution of 1024 x 768 or higher recommended

Supported Operating Systems

Operating System

Supported Versions

Windows • Windows XP

• Windows 7

Solaris • Sun Solaris 10

• Sun Solaris 11

Linux* • RHEL/CentOS 6.x*

• RHEL/CentOS 7.x*

MAC OS

• V10.8 (Mountain Lion)

• V10.9 (Mavericks)

• V10.10 (Yosemite)

• V10.11 (El Capitan) * For RHEL/CentOS, the following libraries must be loaded: gtk+-1.2.10, compat-libgcc-296-2.96, compat-libstdc++-296-2.96, compat-libstdc++-33-3.2.3, and openmotif22-2.2.3.

Supported Browsers

• Internet Explorer

• Firefox

• Google Chrome

Note: CMS Desktop uses Java Runtime Environment 1.6.0, Update 17, which is included in the installation.




Ethernet Business Services (EBS) Software

Requirements

Ethernet Business Services (EBS) Software Requirements

The Calix EBS platforms require the following minimum software for interoperability.

Platform Version Requirements

E5-30x/E5-520 R1.0.9

Service Verify (SV) R2.0

CMS R14.0.144, or higher*

Upgrade the Calix EBS platforms in the following upgrade sequence:

1. Upgrade CMS to R14.0.144 or higher.

2. Upgrade SV to R2.0.

3. Upgrade E5s to R1.0.9.

Note: Upgrade all E5s with circuits monitored by SV at the same time.

Upgrading CMS before upgrading E5s to R1.0.9 maintains E5 management continuity in CMS.




Resolved Issues

Fixed in R15.0.174 (October 2017)

AE ONTs

• Resolved: The default WAN service value is not available on the ONT provisioning after upgrading CMS from 14.1 to 15.0. This affects 844GE ONTs deployed in Active Ethernet mode. The data service will be unavailable after upgrade due to the missing value for the default WAN service. (CMS-15523)

• Resolved: The AE ONT upgrade task may not show all of the ONTs in the detailed status of the task. (CMS-15150)

• Resolved: CMS does not currently allow POTS ports on GX ONTs in AE mode to be provisioned as ground start. (CMS-15147)

• Resolved: For AE ONTs, T1 alarms are not suppressed in CMS when the port set to “enabled-no-alarms”. (CMS-15072)

CMS XML NBI API

• Resolved: When creating a SIP service on a GPON ONT on an E7 using the CMS NBI API, the an “Internal Error” error message is returned when the "&" character is used in the password. (CMS-15351)

E7 OS Network Management

• Resolved: When provisioning MEGS on both the CMS GUI and the E7-20 GUI, the following error may occur: “Request Error Details: (Invalid Value) - unknown attribute admin in attr-list.” (CMS-15395)

• Resolved: When using the Ethernet Topology Provisioning tool to create new VLANs in an E7 network, you have the option to enable or disable option 82, however, you cannot configure the access-identifier profiles for Ethernet services or GPON. This causes VLAN creation to fail, requiring the Option 82 parameters (added in E7 release 2.5) to be configured by hand on each unit. (CMS-15352)

• Resolved: When creating 1M or 2M bandwidth profiles for E7 nodes, re-sync issues may occur. (CMS-15341)

• Resolved: The Inventory Snapshot may get stuck "IN-PROGRESS" when the runtime coincides with NBI workflow. (CMS-15117)

• Resolved: In the CMS Navigation Tree, the E7-20 GPON-16x card PON1 shows only 7 ONTs when there are 64 ONTs configured. (CMS-14980)

• Resolved: The inventory report for E5-400 does not show "ethernet line rate" for GE and 10GE ports. (CMS-14963)

System

• Resolved: For heatmap feature support, CMS 15.0 must be installed with CentOS 7. (CMS-15446)




• Resolved: After rescheduling scheduled tasks to provide proper timeslots to all tasks, CMS may have an issue where an SQL query will cause the database to become unresponsive and block any access to it. Thus, the inventory snapshot running displayed "IN PROGRESS" indefinitely. (CMS-15200)

• Resolved: Using Access Analyze in conjunction with CMS may cause CMS Postgres Database Disk Usage high for PM Data. (CMS-14765)

Fixed in R15.0.068 (June 2017)

AE ONTs

• Resolved: If the AE config does not sync with Consumer Connect Plus (CC+), voice provisioning may have issues. (CMS-15093)

• Resolved: After changing port state of T1 port on 766GX ONT in AE Mode, provisioning change flag not set in the CMS GUI. (CMS-15073)

Fixed in R15.0.017 (March 2017)

AE ONTs

• Resolved: For 844GE ONTs, when the fiber is pulled from the ONT and then restored, the resulting "AE ONT Dropped" alarm may take 20 minutes or more to clear. (CMS-14992)

• Resolved: When using CMS as an alarm trap aggregation point for 844GE ONTs, if an alarm trap is received from an 844GE, then the SNMP trap may be dropped, and consequently not processed. (CMS-14280)

• Resolved: CMS may set the %desc for Remote ID incorrectly. The ONT ID is set for the %desc instead of the value for the user description field. (CMS-13826)

C7 Network Management

• Resolved: After upgrading to CMS 14.1.451, creating an xDSL bonding group on C7 COMBO-24A or C7 ADSL2-24A card will not complete as expected if the xDSL group was provisioned with the packet mode set to either "Y" or "N". (CMS-14824; CMS-14845)




General Notes

Notes, Constraints, and Feature Support Considerations

AE ONTs

• Although the AE platform supports a separate IP Host per ONT port to allow each SIP port to be provisioned with a separate VLAN, CMS restricts provisioning to only a single SIP IP Host per ONT. (CMS-2481)

• Selecting one or more specific ONTs on which to perform a scheduled reset task is not supported. (CMS-2426)

• When creating service tag actions for services that are hosted on AE ONTs, such as SIP, TDM Gateway, and PWE3, the default Match List 1 must be used when creating these services. (CMS-2423)

• Although AE ONT hardware allows a bandwidth setting in a range of 0 kbps to 200000000 kbps (200 Mbps) for GX, and to 1000000000 (1 Gbps) for GE, CMS limits both AE and GPON ONTs to a bandwidth setting in a range of 0 kbps to 2048 kbps or 2 Mbps to 1000 Mbps. (CMS-2407)

• After resolving the event that raises an ONT alarm, the alarm does not clear from the CMS Alarm Table. Solution: Click Refresh at the bottom of the Alarm Table. (CMS-2406)

• When viewing the Advanced panel for ONT detailed information, you must select REFRESH to refresh the page. Navigating to another page will not refresh the page. (CMS-11371)

• After installing AE using a 766GX ONT, if there are multiple ONT profiles with “766GX” in the DESC field, a non-service affecting “ONT Model Mismatch” alarm may occur. Workaround: Rename the profile description to clear the alarm. (CMS-10781)

Alarms and Logs

• For any standing alarms visible in the CMS alarm panel, the severity can only be changed from the "default" value a single time. Any future severity modifications will only apply to any newly populated alarms. (CMS-11525)

• If alarms are generated too frequently, some emailed LOS alerts may be missing the Subscriber ID and User Description. (CMS-10874)

B6 Network Management

• If you are upgrading from OccamView to CMS, refer to the migration process in Managing a B6 Network from CMS 12.1, available in the Calix Resource Center. (CMS-12017)

• CMS manages B6 line cards via the PostgreSQL database. The Oracle database is not supported. (CMS-12016)





• The DHCP Search results (Search > C-Series > IP > DHCP Lease) may not be accurate for IRC cards. (CMS-670)

• When a video subscriber template, which has been applied to an ADLS2-24 port on which video services are provisioned, is modified, the modified parameters do not get applied to the ADSL2-24 port. Workaround: Re-provision the video services on the port to apply the modified subscriber template. (CMS-3963)

• When creating a static IP host, if the Packet Mode parameter is set to “N,” the xDSL ports do not display in the L2IFAID list in the GUI. (CMS-3086)

• If the CMS server is not fully synchronized with a C7 network and a PM download task executes near a 15-minute boundary, the downloaded PM data may shift by one bin. (CMS-151)

• Using the C7 PWE3 tool will change the Timing Mode for DS1 ports to ADAPT. Workaround: Manually build the PWE3 circuit without the PWE3 tool. (CMS-12355)

• Considerations for deploying residential gateway (RG) model video services: 1. Performing Action > Synchronize > Update C7 fails to update the servicing parameters. 2. From the Services tab, click Action > Clear Video and Data Services to remove services (service affecting) from the port. 3. Use the subscriber activation tools to activate subscriber services. (CMS-12018)

• On very rare occasions during R8.0.3xx upgrades, CUP may fail with error message, "Key exchange failed: server’s signature didn't verify". Workaround: Rerun CUP. (CMS-11660)

• When running a PM query from the Web interface, the query will fail with error message “no rows found.” Workaround: Upgrade C7 networks to R8.0.300 and higher and CMS to R13.0 and higher. (CMS-10517)

CMS Desktop

• When using external software to monitor alarms, faultclear and faultset alarms may not clear. (CMS-9988)

• CMS passwords should not include special characters such as semi-colon or colon, which would be misinterpreted by TL1 cut-through. (CMS-9738)

• In the CMS Desktop, there is no field to add User Notes for scheduled tasks created by users. (CMS-2727)

• Profile names for third-party devices cannot begin with numbers. Solution: Ensure that the profile names begin with alphabetical characters only. (CMS-1759)

• On rare occasions, the CMS snapshot task may report a failed inventory download with error messages indicating that minor errors may have occurred. This error message can usually be safely ignored. (CMS-11829)

• To run multiple CMS GUI application instances in Linux, the applications must be opened using different usernames. (CMS-11807)




• On occasion, network element provisioning or other updates do not immediately display on screen. Solution: Do one of the following: 1. If the Navigation Tree display is affected, Click Tools > Refresh All. 2. If the CMS Desktop Work Area display is affected, click Refresh, or temporarily navigate to a different Work Area tab. 3. If the Alarm Table display is affected, at the bottom of the table, click Refresh, or close and restart CMS Desktop. (CMS-107)

• After creating the first new user in a new user group, CMS may or may not display the newly created user under the Security > User > Securitydomain > Usergroup . Workaround: The user can be displayed properly after re-logging into the CMS client. (CMS-10669)

CMS Upgrades

• When upgrading CMS, PM data from scheduled tasks of the previous install are not imported into the new database. (CMS-13714)

• For CMS R13.0 and higher, when upgrading CMS, verify that no yum processes are running on the CMS server before installing the CMS software. (CMS-12182)

• When upgrading CMS server software, Calix recommends using the automatic import feature, whenever possible, to import CMS objects from the old server to the new server. (CMS-12014)

• After upgrading, download the latest set of SNMP MIB files from the Calix the Software Center or documentation portal on the Calix Customer Resource Center. (CMS-12013)

• For a checklist of upgrade tasks, refer to the CMS Installation and Upgrade Guide for Linux or Solaris, depending on your host server’s operating system. (CMS-12012)

• When installing the Linux CentOS 64-bit CMS install package, you will be prompted to install any required missing packages. (CMS-11923)

• When installing or upgrading CMS, note that: 1. If the physical memory size is less than 6G (6000000), the installer process will be quit. 2. If the swap size is less than physical memory size, CMS will prompt a warning message and the allow end user to choose "Quit" or "Continue". Choosing the “Continue” option will continue the installer process. (CMS-11906)

• During upgrades, Calix does not recommend using CMS scheduled task to activate the image if you have already downloaded an upgrade image into the E5 box. Instead, activate that image through the EWI. (CMS-11848)

• During upgrades or installation, the following physical memory size checking logic has changed from CMS R13.0: If the physical memory size is less than 12G, CMS will prompt the warning message and allow the end user to choose "Quit" or "Continue". Choosing “Continue” will allow the installer process to continue. For console mode, use parameter “-Dramcheck=false” to skip this check. After the first check, if the total amount of physical memory and swap size is less than 18G, CMS will prompt another warning message and allow customer to choose “Quit” or “Continue”. Choosing “Continue” will allow the installer process to continue. For console mode, use parameter “-Dswapcheck=false” to skip this check. For detailed information, please see the CMS Installation and Upgrade Guides. (CMS-11799)

• After upgrades, the Subscriber Search and inventory data functions may not be available for several hours. (CMS-11758)




• To install the CMS GUI on a MacOS client, change the security policy as follows: Go to System Preferences > Security&Privacy > General, then select Anywhere. The installation will be corrupted if this policy is not correct. (CMS-11418)

• After upgrades, using CMS subscriber search will only return subscribers who were turned up after the upgrade. Workaround: The full subscriber search will be available after a short period. (CMS-11317)

• Calix offers CMS installation packages for both 32-bit and 64-bit Linux servers. These independent CMS versions are optimized for the Linux OS on which CMS is installed. Thus, Calix recommends installing the appropriate version of CMS per server OS. If you need assistance in determining if your Linux OS is 32-bit or 64-bit, contact the Calix Technical Assistance Center. (CMS-11145)

• For customers using an Oracle database, Calix does not recommend using Silent Mode installation for Solaris CMS upgrades or installations. (CMS-10371)

CMS XML NBI API

• For C7 ONT XML requests, when suspending or resuming an RF Port, sometimes the correct PST will not be reported in the reply. This issue can be resolved by sending the same XML request again. (CMS-10783)

• Occasionally, when communicating with E7-2 devices, some CMS XML NBI requests may time out when multiple requests are sent in a short time period. (CMS-10462)

• For the element tag <ONTNum> for "G" ONTs, if you use a hexadecimal value, it must start with 0x. This is now enforced in R12.1.169 and higher. (CMS-10418)

E3 and E5-100 Network Management

• When provisioning E3-12C SSA Port Setup, US Ip and DS Inp are in the wrong order. (CMS-8469)

• Global E3/E5-100 profiles cannot be modified. (CMS-4294)

• When setting CMS Sync time during NTP over-ride settings, only GMT time is available. (CMS-4199)

• After a global E3/E5-100 subscriber template is created, its parameters cannot be modified. Solution: Create a new subscriber template with the updated parameters. (CMS-1980)

E5-30x and E5-520 Network Management

• When using CMS to schedule E5-30x/E5-520 upgrades, the status displays in the events tab, but the upgrade events do not appear in the CMS alarm table. (CMS-11847)


• For CMS R14.1.2xx and higher, 802.1x configuration is only supported in E7 OS releases 2.5.20 and higher. (CMS-13920)

• After upgrading to E7 R2.4, the sip-gw-profiles for the E7s may no longer be synchronized. Workaround: Change the name of the SIP GW profile and resync from CMS to the E7, then change the SIP GW profile back to the original name. (CMS-12829)




• When creating an ACS URL string under CMS > PROFILE > E3-48C/E5-48/E7/ONT > RG MANAGEMENT, strings longer than 63 characters will be truncated. CMS will warn user with error message "Please enter a string of 63 characters or less." (CMS-12559)

• For E7 R2.2.80, the global tag-action profile sync may fail with error message, "Profile Name already exists." (CMS-12319)

• After upgrading from CMS R12.1 to R13.0, some E7 Ethernet Bandwidth Profiles may be missing from CMS. Workaround: Check the E7 Ethernet Bandwidth Profiles before upgrading to R13.0 and change all of the profiles to the correct validation. (CMS-12081)

• E7 platforms using global TDM Gateway profiles must be running R1.2.60 or higher. (CMS-12020)

• Alphanumeric IDs for the ONT Smart Activate feature are currently only supported on E7 GPON platforms running E7 R2.2 and higher. (CMS-12019)

• When displaying E7 subscribers in CMS, the results in the PortSubscriber table columns may be inconsistent. (CMS-11729)

• After upgrading to CMS R13.0, E7 does not support the "Not Used" inner tag in E7 tag actions. Using the “Not Used” inner tag may cause some service tag action profiles to be missing during upgrades from previous CMS releases to R13.0. Calix recommends checking all service tag action profiles before the upgrade and correcting all illegal profiles. See the following service bulletin for further information: CMS SB-14-005 - E7 and AE ONT Service Tag Action Rule Enforcement in CMS R13.x. (CMS-11276)

• In CMS, the service name for RG is “Gateway Service,” but, in CLI, the service name is Data Service.” (CMS-10267)

• Occasionally, when viewing svc-tag-action items in the EWI, the dialog box will come up as blank. Workaround: Clear the javascript cached files and login again. (CMS-10133)

System

• Calix has discovered an issue with a default limits setting on CentOS 6.x operating systems, where it may artificially limit the CMS "max user processes" to 1024. If this issue is not remediated, it can cause some CMS processes to stop, with exception errors such as "OutofMemory," even if there is still sufficient memory available. Please reference this bulletin for instructions on how to prevent this issue. (CMS-12024)

https://www.calix.com/bin/calix/servlets/docdownload?fileId=/content/dam/calix/doc-library/software/cms/bulletins/service-bulletins/CMS%20SB-14-003/CMS_SB-14-003_CentOS_config.pdf




CMS Alarm Updates in R15.0 The following alarms have been added or changed from R14.1 to R15.0

For more alarm information, reference the platform specific maintenance and troubleshooting documentation.

Status Alarm Name Alarm Description

E7 OS Alarm Management

New pon-bandwidth-over-subscribed-downstream

PON Bandwidth Over-Subscribed Downstream




Open Issues AE ONTs

• When exporting an AE ONT query report to CSV, the error message is not quoted correctly, which causes the CSV fields to parse incorrectly. (CMS-8125)

• On the Ethernet OAM > MEPS > Remote Discovered MEP screen, the MEP interface option fails to reload after navigating to another AE ONT. WORKAROUND: Click the MEPS tab, and then navigate back to the Remote Discovered MEPs screen. (CMS-6640)

• After creating an AE ONT and running a Sync Config task, the messages in the Task Progress window display a different ONT ID than the configured ONT. (CMS-5504)

• After creating global ONT profiles, their names cannot be edited, or deleted if they are being used on other AE ONTs or E7 units. (CMS-4136)

• If an ONT profile is provisioned with an incorrect ONT model number, the ONT Model Mismatch alarm that is raised cannot be cleared unless the provisioning on the ONT is deleted and recreated. (CMS-3084)

• ONT subscriber services cannot be temporarily disabled from the Services screen. (CMS-2986)

• The following limitations apply when managing AE ONTS: A maximum of 100 ONTs can be sorted simultaneously and any changes to columns only apply to that instance in CMS Desktop. (CMS-2940)

• After running an E7 inventory snapshot on a network with DHCP snooping enabled, the AE ONTs off of the E7 are erroneously moved to same network group as the E7. (CMS-2644)

• A "Line Test" cannot be launched from within CMS. To initiate the line test feature, execute the "vtst test <port number>" command from within the CLI. (CMS-2642)

• Using the AE ONT telnet cut-through requires full Administrator privileges. (CMS-15388)

• After upgrading CMS to 14.1.471, AE ONTs may show Ethernet ports as members of an RG interface when no RG interface exists. (CMS-15234)

• After upgrading to CMS 14.1, AE ONTs may not have Ethernet ports as members of full bridge in AE config files. (CMS-15191)

• For E7-20s in large networks, some CMS inventory tasks may fail due to a response timeout. (CMS-14962)

• GigaCenter devices only support a single voice service profile. (CMS-13849)

• When changing the subscriber ID mapping, a warning message may occur “Warning: Change “Map Sunscriber ID to” will cause 844GE subscriber issue. Do you want to continue?” This message warns that the existing subscriber records within Consumer Connect Plus will NOT be updated automatically based on the new rule. However, if you perform an AE ONT sync in CMS after changing the subscriber ID mapping, the related subscriber records within Consumer Connect Plus will be created/updated by following the new rule. Calix does not recommend changing this rule once it has been set up. (CMS-13782)




• For the 844GE model in AE-mode, the RTP-eth-qos option should not be available on SIP profiles in CMS. (CMS-13584)

• From the AE ONT > SERVICES > FORM screen, selecting Apply & Sync and Reboot from the Apply drop-down may not reboot the device. (CMS-13580)

• When creating H.248 voice service, using a DHCP IP host may fail with the following error, "Host Protocol in IP Host doesn‘t match H248 profile gateway setting." WORKAROUND: Create the H.248 voice service using a Static IP host. (CMS-13454)

• When the port description is set, CMS may not write the alias information into the AE config file. (CMS-13318)

• After upgrading to R14.0, some AE ONTs may show externally provisioned = Y and no services appear in CMS. (CMS-13231)

• Occasionally after upgrading to R14.0, making changes to an ONT data service and then syncing the configuration may delete MGCP voice service provisioning, causing voice service interruption. (CMS-13087)

• The default AE service security setting aren‘t consistent between the EWI and the CLI. (CMS-12202)

• For 700GE ONTs running in RG mode, the AE ONT remote access cut through option is not available. WORKAROUND: Use the CLI for 700GE ONTs. (CMS-12200)

• For 744GE ONT profiles, CMS does not check the value of PWE3. (CMS-12136)

• After an ONT image upgrade, the AE ONT firmware version may not display correctly. (CMS-12103)

Alarms and Logs

• The high disc space use by the postgres database may raise alarms in the CMS server. Workaround: Delete logs and old files to recover disc space. (CMS-15048)

• When scheduling an inventory snapshot task, removing the check from the "stop after" box may fail to update within the task. (CMS-14955)

• Occasionally, some recurring PM download tasks may be reported as successful, but they are not complete. For Access Analyze users, this will affect the regular PM data that is shared with that application, causing Access Analyze reports to be out of date. (CMS-13918)

• When viewing link connections between devices in the CMS topology view, some of the connecting links may change color based on non-link-based alarms. (CMS-13092)

• On very rare occasions, some alarm ACK, Trouble Ticket Number, and User Notes fields may clear after 5 minutes. (CMS-12865)

• When selecting alarms in the CMS alarm table, selecting an alarm and a new alarm is set or cleared, the selection will be unselected. (CMS-12830)

• CMS Web defines the PONROGUEDETECTED alarm as Minor in the alarm redefinition table by default, while other interfaces and C7 documentation define the alarm as Major. (CMS-12518)




• From the CMS Web GUI, exporting a multiplatform subscriber search report to CSV will only report up to 10,000 entries. (CMS-12246)

• When generating an environmental alarm on an E7, and then clearing it, there are different CMS-TRAPS-MIB:cmsTrapAID.0 in the SET and CLEAR traps. (CMS-12198)

• The logFile.txt file on local PCs running CMS GUI may grow rapidly in networks where there are many devices, which may cause slow PC performance or burden the hard drive. (CMS-12148)

B6 Network Management

• Read-only provisioned CMS users have full administrative privileges to the B6 card user interface. (CMS-8264)

• The B6 subscriber database may take several minutes to repopulate after migration from OccamView to CMS. (CMS-8086)

• Clicking on a B6 line card creates a new web session, but will not close the old session. Clicking between two B6 cards 10 times in CMS will cause the B6 EWI to no longer load because the card will be out of sessions. (CMS-13145)

• When setting alarm closures for B6 line cards to receive AUX alarms and external alarms, the AUX alarms may not be received in CMS. Workaround: Change the devices to ALL and the alarms to ALL to receive all of the alarms. (CMS-12611)

• There are some alarm mismatches between CMS and B6. (CMS-10735)

• When using the alarm closure feature for B6 in iMS and delivering all network “GLASS” alarms to B6, the INFO and WARN severity alarms delivered to the B6 will have the severity modified to minor. (CMS-10510)

• When using CMS to execute the Reload Device Task, all of the listed B6 line cards will reload at the same time. (CMS-10430)


• In C7 networks, when using SSA to manage RF video ports, SSA will not show the correct port state until the page is manually refreshed. (CMS-8630)

• CUP may display the Revert button before the C7 is ready to perform a software Revert operation. Workaround: If a Revert is necessary, click the Revert button only after the local AMP has reset. If you click the Revert button too soon, close and restart CUP and then click Revert only after the local AMP resets. (CMS-781)

• The Importing Static IP Hosts topic in the Calix C7 R9.0 Broadband Data Services Guide documents the iphost attribute sequence incorrectly. The correct order is RTRAID BRIDGE, VLAN AID, L2IFAID, MAC ADDRESS, IP ADDRESS, MFFGW, HOSTTYPE, INCL. (CMS-13921)

• After upgrading to CMS R14.0, C7 inventory snapshots may fail on some rings. (CMS-13271)

• When displaying ONT performance data, CMS may open multiple Task Progress windows when all of following conditions are met: multiple ONTs are selected in the Navigation tree. one or more ONTs are expanded in the tree. * one or more ONTs are OOS-AU. (CMS-12888)




• Reprovisioning data subscribers using XML from the billing system to CMS may fail when running C7 R9.0.10 networks. (CMS-12642)

• In very large networks, manually adding an ONT to quarantine while troubleshooting a rogue ONT event using CMS may fail. Workaround: Use iMS to quarantine the ONT. (CMS-12534)

• When retrieving VLAN-IFs from an OC/DS3 port, CMS may be unresponsive if there is an abundance of VLAN-IFs on the port. (CMS-11040)

• On very rare occasions, CMS may not display line cards on certain shelves. Workaround: Use iMS or disconnect and reconnect the network to correct the issue. (CMS-10251)

CMS Desktop

• The CMS topology view does not have ample work space to work with a large amount of network devices. (CMS-13146)

• Some CMS web interface ports are susceptible to Logjam attacks. In these instances, Google Chrome and Firefox will report "Server has a weak ephemeral Diffie-Hellman public key" when trying to access the CMS web GUI securely. These web browsers may block access to the GUI because they are not secure. (CMS-13140)

• When using an outside provisioning agent that uses auto created subscriber activation, the user-descriptions may not apply to ONT Eth ports. (CMS-13124)

• When a Windows PC regional settings are set to Turkey and Turkish, CMS may be unable to create, delete or edit scheduled tasks. (CMS-12973)

• When using the SSA topology display to organize large networks, display size limitations may render topologies difficult to manipulate or read. (CMS-12474)

• Networks deleted on a Primary CMS server are retained on a Secondary server. (CMS-12025)

• Upon start-up, CMS does not warn the user if there are permission issues with the CMS directory. (CMS-10846)

• On very rare occasions, when initially signing in to the CMS client, error message “oops, gui xml not loaded yet” may occur. Solution: Click OK to clear the error. This message is not service or usability affecting. (CMS-10397)

CMS Upgrades

• When the Oracle database is running on the same host server as the CMS server software, the CMS Installer does not verify whether there is sufficient space on the Oracle database. (CMS-2657)

• After upgrading to R14.0, the Sync config and SNMP may not work as expected until CMS is restarted. (CMS-13441)

• After upgrading to CMS R14.0, some global service tag actions may go missing. (CMS-13169)




CMS XML NBI API

• For AE ONT XML requests, for non-required element tags, if the tag is not included in the XML request, the default value of the parameter will override the currently provisioned value. Calix recommends including the element tag in the XML request even if the parameter value is not changing. (CMS-1387)

• XML API, when setting up a new C7 ONT video service, the server may reply to the XML request with an "Object already exists" message. The service will still get properly provisioned, but may cause the XML client to stop other executions due to this error. WORKAROUND: Do not use the Subscriber ID field on the XML create request. (CMS-13517)

• When using the XML API to build GR303 service to a 700GX ONT, the action may fail with error “Database change counter indicates write conflict”. Workaround: Remove the <UserDesc> line from the request. (CMS-13202)

E3 and E5-100 Network Management

• When creating a CMS User Group that limits the User in the Group to applying E3-12C network level functions, the User is still able to configure CMS level profiles or subscriber templates. (CMS-8555)

• After a global E3/E5-100 subscriber template is created, its parameters cannot be modified. Workaround: Create a new subscriber template with the updated parameters. (CMS-5410)

• A warm restart alarm does not always display in the CMS Alarm Table for E5-111 and E5-121 service units; CMS may not receive the SNMP trap while it is disconnected from the unit. (CMS-2677)

• CMS allows you to create an E5-12x IPQOS profile with a PIR greater than 2x the CIR. This profile may then fail synchronization with E5-121s. (CMS-12201)


• Local E7 profiles cannot be imported to global CMS profiles from a list in Table View. Workaround: Change to Form View. (CMS-7196)

• An error results when a service match list in a service tag action is not specified. Note: CMS now prevents creating a service tag action when no service match list is specified. (CMS-5853)

• A newly added E7 shelf may not display in CMS. Workaround: Click Refresh. (CMS-1970)

• The SIP Gateway Voice Service form for xDSL shows a checkbox for T.38 Fax Relay, but the feature is not supported for xDSL subscribers. (EX-24422; EX-10143; CMS-14995)

• Deleting an E7 network and then re-adding it with a different name will result in duplicate records in a multi-chassis search. (CMS-14221)

• For Type B PON protection FFP alarms information, the CMS incorrectly shows the FFP group internal ID, rather than the name as reported by the embedded web interface. (EX-23682; CMS-14129)




• When cutting over services to an E7-20, SIP services may be mistakenly provisioned with a duplicate C-TAG, causing all of the duplicates to fail to register until all of the duplicates are removed. WORKAROUND: Locate and delete all of the duplicates. (CMS-13197)

• E7 GE port LOS alarms received via email notification do not include a populated location field. (CMS-13099)

• In CMS R14.0, the E7 RG Management profile added one new validation, ACS-URL. The configuration must start with "http:" or "https:" as the prefix. If this profile is configured in a previous version, please check the profile before upgrading. All RG Management profiles should be changed to satisfy the rule before the upgrade. Otherwise, some global profiles may go missing. (CMS-12699)

• In CMS R13.1 and higher, when upgrading an E7 system, right clicking on a box no longer brings up the UNDO/CUT/COPY/PASTE/DELETE options. Workaround: User CTRL+C to copy and CTRL+V to paste. (CMS-12446)

• When using subscriber search for an ONT off an E7, the STRAID will be inconsistent. (CMS-12393)

• When attempting to delete a Global E7 Tag Action that is in use, after attempting this a few times in a row CMS will allow it to be deleted. (CMS-12167)

• When provisioning E7 nodes, there is not an option for "mount type" in CMS. (CMS-11962)

• The E3-12C/E5-121 CSIP GUI panel does support GR-57 CSIP service provisioning. (CMS-11798)

• The Unattended Call transfer after a call is picked up using star code does not work with local flash hook service. (CMS-10877)

• CMS may not display new E3-48C bonding groups. Workaround: Restart the CMS EWI to view new E3-48C bonding groups. (CMS-10622)

• When creating a VLAN using the “Provision Ethernet Topology” feature, 4094 is allowed as a VLAN ID, but it cannot be applied. Workaround: Do not provision a VLAN ID as 4094. (CMS-10539)

• When provisioning an ONT RG interface port, entering “256” for the Config File Instance and applying will change the Config File Instance to “None.” Workaround: Do not enter “256” for the Config File Instance. Valid values are between 2 and 255. (CMS-10536)

• When creating an E3-48C upgrade task, and the Upgrade Software upgrade option is “Reset Only” with a non-existing E3-48C version, the task may take a very long time to run. (CMS-10454)

System

• After rebooting a CMS server and the CMS processes start up, the SNMP Manager may fail to start. (CMS-13859)




Calix User Documentation View or download Calix user documentation from My Calix.

The Calix Technical Assistance Center The Calix Technical Assistance Center (TAC) provides 24x7 coverage (24 hours a day, 7 days a week). Normal business hours are 5:00 a.m. to 5:00 p.m. Pacific Time, Monday through Friday (not including Calix-designated holidays), during which time you can contact the Calix TAC immediately by phone, web, or email. Outside normal business hours, phone calls to the TAC are met with an immediate response time for critical and major issues.

Online support

You can create and manage technical support cases online from the Calix Service Station. To access the Calix Service Station, log in to My Calix and then click the Calix Service Station tile to:

• Submit a new technical support case, or check/update the status of existing cases.

• Review product orders, including ship dates and tracking information.

Calix TAC Contact Information

Online Support: My Calix

Phone: 877-766-3500 (toll free) or 707-766-3500 (direct)

Calix Severity Definitions

Critical: A network, node, or key circuit is down or there is a critical impact to business operations. Calix and the Customer will work around the clock (24x7) to resolve the problem.

Major: Operation of a network, node or critical circuit is severely degraded, or significant aspects of the Customer’s business operation are being negatively impacted by unacceptable network performance. Calix and the Customer will commit full-time resources during normal business hours to resolve the problem. A plan will be developed for appropriate after-hour actions.

Minor: System operations are impaired, but with minimal performance impact. Calix and the Customer will commit resources during normal business hours to resolve the problem.

Information Request: Customer requires information or assistance on the Calix product capabilities, installation, operation, administration or configuration. There should be little or no impact to the Customer’s business operation. Calix and the Customer are willing to provide appropriate resources during normal business hours to provide information or assistance as requested.




calix cms release notes 15.0 - paul t clarkpaultclark.com/network/calix/cms r15.0.174 release...

Documents