CMS_CALIX_13.0.143

CMS R13.0.143 Release Notes Preface This document constitutes the release notes for Calix Management System (CMS) version 13.0.143. These notes provide specific information regarding functionality of this rel ease. 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 on the Calix Resource Center at www.calix.com. at www.calix.com. CMS R13.0 is designed to enable Global Market expansion for fiber and copper service deployments. By integrating T-Series ONT management into CMS R13.0, global service providers can deploy GPON base services with ONTs that meet their specific market needs. Likewise, integration of management for E7 VDLS2 line units that meeting international standards, CMS is well suited for managing global copper deployments. Management of the provisioning of unit level vectoring will provide enhanced service delivery capabilities for copper services, while suppor t for LLDP on E7, E3-48C, E5-48 and E5-48C will enhance topology top ology management capabilities of CMS, resulting in vastly improved management capabilities.

Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. Calix. All Rights Reserved. Part # 240-00750-10

Calix CMS R13.0.143 Release Notes

Page 2 of 22

What’s New in CMS Release 13 .0 New Features or Enhancements Calix Platform

CMS Support Introduced in 13.0 

B6



CMS

   



Support for ESA (Emergency Stand Alone) configuration Subscriber end point mapping enhancements 64-bit InstallAnywhere installer for 64-bit Linux Operating Systems 64-bit JVM for 64-bit Linux Linux Upgrade to Postgres 9.3 Alarm Closure Support for: E7 o E3-48C o o E5-48/E5-48C C7 o Topology Management Support for LLDP for: o E7 E3-48C o E5-48 o E5-48C o

New Features

E7



  

  

T-Series GPON ONT support for: o T071G o T072G o T073G o T076G o T077G VDSL2-48D overlay DSL enhancements for global applications – applications – 900 900  Operations enhancements: Link Layer Discovery Protocol (LLDP) o SIP server redundancy o New for CMS R13.0.139: Rogue ONT detection, isolation, and removal (E7 R2.2.90 and E7 R2.3.20 and higher only) New for CMS R13.0.140: Full FCAPS support for the 844G and 854G and RF capable GigaCenter service gateway New for CMS R13.0.143: The following new switch types have been added for E7 SIP GW profiles (SIP-GW-PROFILE): zte o huaw o syla o eric o cs2k o bell o

Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. Calix. All Rights Reserved. Part #240-00750-10

Calix CMS R13.0.143 Release Notes 

E5-48/E5-48C

  

E3-48C



Page 3 of 22

Fully integrated FCAPS support Fixed form factor IP DSLAM applications CO and RT deployments Unit level vectoring Unit level vectoring for E3-48C

CMS Network Element Support Matrix CMS R13.0.143 supports the following Calix platform software releases for managed network elements: Supported Calix Network Elements

Calix B6

Platform Software Versions Supported

7.3, 7.2, 7.1

[*][ † ]

Calix C7

8.0.3xx, 8.0, 7.2, 7.0

Calix E7

2.3, 2.2, 2.1

Calix E5-400

2.1, 2.0, 1.2

Calix E3-48C

2.3, 2.2

Calix E5-48, E5-48C

2.3

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

4.1, 3.1, 2.1

Calix E5-110, E5-111

4.0, 3.0, 2.0

Calix E3-48

2.0, 1.0

Calix 700 Active Ethernet ONTs

3.0, 2.2, 2.1

Calix 2300 Active Ethernet ONTs

4.1, 4.0

Calix F5

4.0, 3.1

Calix FD

9.0, 8.x

[*]

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. Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10


Page 4 of 22

Installations and Upgrades CMS R13.0 supports new installations and upgrades, as described in the following table. 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. Current CMS Version

Upgrade Path

CMS R12.1.xxx CMS R12.0.xxx

Perform a full upgrade to R13.0.143.

CMS R11.3.1xx CMS R11.2.xxx

Perform a full upgrade to R12.0.217 before upgrading to R13.0.143.

CMS R11.2.092 or below

Contact Calix TAC to determine the recommended upgrade path.

Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10


Page 5 of 22

CMS Server System Requirements Note the following:  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. 

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. SWAP file size: o

Recommended: Equal to the memory size

o

Minimum: 6 GB

When installing or upgrading CMS, note that: o o

If the physical memory size is less than 6G (6000000), the installer process will be quit. 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.

S m a l l D ep l o y m e n t Up to 100,000 subscriber lines

Linux Platform Dell PowerEdge 410 Server  One Intel Xeon 5600 Series processor  6 GB memory  Two 15K RPM SAS drives, 146 GB or higher, RAID 1 RHEL Server or CentOS 5.x or 6.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 R410 Server can support up to 100,000 subscriber lines by upgrading these specifications:  Up to two Intel Xeon 5600 Series processors  6 to 24 GB memory  Two or four 15K RPM SAS drives, 146 GB or higher, RAID 1 or 101



Page 6 of 22

M e d iu m D e p l o y m e n t Up to 500,000 subscriber lines

Linux Platform Dell PowerEdge R510 Server  Two Intel Xeon 5600 Series six-core processors  24 to 48 GB memory  Up to fourteen 15K RPM 2.5" SAS drives or SSDs, RAID 10 RHEL Server or CentOS 5.x or 6.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)

Solaris Platform Sun SPARC T4-1 Server — Contact Calix for recommended configuration Oracle 10g/11g RDBMS (Oracle 11g recommended for managing more than 250,000 subscriber lines)

L a r g e D e p lo y m e n t 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 5.x or 6.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)



Page 7 of 22

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   

Windows XP or Windows 7 Sun Solaris 10/11 RHEL / CentOS 5.x* * 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

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



Page 8 of 22

Resolved Issues New Feature Support Only in R13.0.143 (December 2014) Fixed in R13.0.142 (November 2014) B6 Network Management 

Resolved: Running a B6 inventory resync for the entire network may pause after a few hours while the scheduled task will remain in status of IN PROGRESS witho ut any further change. (CMS-11951)

C7 Network Management 

Resolved: When using CMS R12.1 to add a new Combo2-24V card to an existing shelf and then adding RG services, a “Video not enabled on PGAP/OLT cards” error message will occur if there is no IPVC between IRC and the subscriber port. Workaround: Provision the IPVC between the IRC and the subscriber port. (CMS-11894)

E-Series Network Management 

Resolved: For E7 and E3-12C TDM service, OSMINE TL1 agent will accept GR-57 or D4 end points. (CMS-11675)

Fixed in R13.0.140 (September 2014) Alarms and Logs 

Resolved: After upgrading to R12.1, CMS will forward the alarms to the northbound if the NB TL1 client is not OSMINE TL1. Solution: CMS will not forward the alarms if the requests come from TL1 clients. (CMS-11668)


Resolved: Occasionally, during an inventory download or a full sync with C7 networks, CMS may not properly write the C7 alarms into the CMS database, causing incomplete alarm reports. (CMS-11737)



Resolved: On rare occasions, C7 networks may go into a synchronizing state, which may cause incomplete alarm reports in the corresponding networks. (CMS-11735)



Resolved: CMS may not send the proper requests to retrieve alarm from all of the C7 shelves, which will cause incomplete alarm reports. (CMS-11733)

CMS Desktop 

Resolved: The CMS Application Layer timeout period of 90 seconds may prevent object retrieval from large networks. Solution: The timeout period has been extended to 120 seconds. (CMS-11731)



Page 9 of 22

Fixed in R13.0.139 (August 2014) B6 Network Management 

Resolved: Once the following B6 alarm types are raised, they will not clear from CMS until the alarms are synced for the affected line card: "Blacklisted dues to excessive ARP", "High water mark exceeded by IGMP", "Packets are being dropped by IGMP". (CMS-10425)


Resolved: When retrieving VLAN-IFs on an OC/DS3 port, CMS will retrieve all of the VLANIFs for the entire shelf. (CMS-11243)

CMS XML NBI API 

Resolved: Using the CMS XML NBI to query for ONTs or ONT Ethernet ports will fail with “Internal Error.” (CMS-10816)


Resolved: The E5-400 IGMP mode “Snoop-Suppress” is not present in the CMS EWI, but the cut through web feature shows this mode as an option. (CMS-10860)

Fixed in R13.0.133 (March 2014) AE ONTs 

Resolved: CMS incorrectly interprets 23xx ONTs keepalive trap as an E5-110 "Air Compressor failure" alarm. (CMS-10471)



Resolved: Using static IP addresses that end with 0 or 255 to provision ONTs are not valid and will return an error message. Solution: Provisioning ONTs with static IP addresses that end with 0 or 255 are now valid. (CMS-10464)



Resolved: In R12.0 and R12.1, the XML NBI does not apply AE ONT port defaults. (CMS-10369)



Resolved: CMS R12.1 requires a security profile for AE ONTs, which can cause an issue with upstream NBI devices that are not configured for a security profile, and the NBI will error out instead of provisioning services. (CMS-10348)



Resolved: Occasionally, when using static IPs for GPON SIP service and using SSA to provision the SIP service to the VEP, the task may fail with error message “required parameter is missing.” (CMS-9997)



Resolved: Before November of 2011, Calix 700 series ONTs configured for SIP mode may not be able to dial 911 or 411 if using the default dial plan provided with the sample configuration file version 1.15. Workaround: Download the current VoipConfig.txt file from the Calix Portal Software Download Center > Tools. (CMS-9825)



Resolved: When configuring a PWE, the Static IP Mask field is grayed out and is not provisionable. (CMS-9794)



Page 10 of 22



Resolved: The broadcast/multicast rate limiter is missing from the HB HSI and FB Video Service applications. (CMS-9728)



Resolved: In RTP timestamp mode, creating multiple PWE3 services with different RTP Mode parameters is not allowed. (CMS-9473)

B6 Network Management 

Resolved: Occasionally, B6 nodes may not be accessible using the cut-through in CMS or the B6 web interface. (CMS-10495)



Resolved: When a B6 line card port down event occurs, the port number is not included in the alarm email. (CMS-10460)



Resolved: B6 AE ONT alarm emails do not include the ONT Subscriber ID or the ONT IP. (CMS-10262)



Resolved: After upgrading from CMS R11.3 to R12.0 or higher, any previously created B6 Network Backups will fail. Workaround: To restore the network backup functionality, open any scheduled B6 network backup task and change a parameter, such as the time of the backup or the note for the backup task, and then create the update. (CMS-10136)



Resolved: After upgrading to R12.1, creating B6 chassis objects and moving B6 OLTs into these objects, will break any alarm email subscriptions created utilizing the OLTs Network group. Workaround: Move the chassis back to the previous Network group. (CMS-9999)



Resolved: CMS may appear to clear the a “Client Queue Threshold Alarm” generated by a B6 “High water mark exceeded by IGMP” alarm, but the alarm will remain in the CMS alarms pane even if the condition no longer exists. Workaround: Reset the alarms on the affected OLT. (CMS-9925)



Resolved: When creating a fiber voice service using S-VID 2 and a C-VID that is not the ONT’s management VLAN, the modified C-VID in the voice profile will be overruled by the management service creation. Workaround: Manually provision the port and ONT in OCM. (CMS-9904)



Resolved: When activating a PWE3 service package using CMS, selecting the “B6 B6 mode” will cause the activation to fail with error message “Reason - Exception during method call. error unmarshalling return; nested exception is: java.io.EOFException Details: getPppChannel : error unmarshalling return; nested exception is: java.io.EOFException.” (CMS-9674)



Resolved: When activating a new service in the Fiber Service activation view, CMS will display the wrong ONT model. (CMS-9626)


Resolved: When provisioning a T1 Cross Connect using SSA from one ONT T1 port to another ONT T1 port, the provisioning will be incorrect in the SSA pane. (CMS-10566)



Resolved: When using the filter in iMS to pull an inventory report, equipment and line units do not display. Control equipment and specific line unit type filters will display correctly. (CMS-10469)



Resolved: When manually adding static video channels using Video > Video Channel in CMS or iMS, if the VP and VC boxes are left blank the action will fail. (CMS-10370) Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10


Page 11 of 22



Resolved: When creating a bonded C7 Data Subscriber Template, MM and MM+ xDSL templates are not displayed. (CMS-10347)



Resolved: When doing an IP/MAC search for a C7 GPON ONT subscriber with an IP, the L2IFAID hyperlink will return a “Not Found” message. (CMS-10137)



Resolved: When upgrading to C7 R8.0.3xx, CUP may fail during file distribution with error message “RAP to RAP Copy Cancelled by MCS.” (CMS-9958)



Resolved: When upgrading to R8.0.3xx, CUP may fail during file distribution with error message “Exhausted LockOut attempts to some slaves.” Calix does not recommend using “fix amp file system” during CUP. Workaround: Reset AMP and run CUP again. (CMS-9939)



Resolved: When changing a C7 network name by deleting the network and adding it back, selecting YES when CMS prompts for a SSA record migration from the previous network will cause original data migration failure. (CMS-9881)



Resolved: After upgrading to R8.0.302.462, the software version incorrectly displays as R8.0.0.462. (CMS-9867)



Resolved: Upgrading to C7 R8.0 with EGW VSPs assigned to two TDMGWs on the same shelf may cause COMBO2-24v subscribers to lose SIPVCG registration. (CMS-9842)

CMS Desktop 

Resolved: Due to security enhancements in Java 7 Update 51, iMS will not launch with JRE 1.7.0_51. (CMS-10537)



Resolved: When launching CMS from Command Center using Java 7, CMS will fail to load. (CMS-10414)



Resolved: A CMS read-only user can make provisioning changes on the E7 node. (CMS-10392)



Resolved: PM stats may cause the Postgres database to have high disc space utilization. (CMS-10346)



Resolved: CMS Canned ADSL Health Reports do not report the same numerical values per port as a manual report for the same time period. (CMS-10134)



Resolved: With CMS web, when using a login email address containing an apostrophe, an invalid email address error will occur. (CMS-9797)



Resolved: In the CMS security logs, user login information reports do not show the IP address a user logs in from. (CMS-9398)



Resolved: Attempting to run an “ADSL Health Monitor” Business report will result in errors. (CMS-9263)

CMS Upgrades 

Resolved: Low swap memory can cause issues when installing or upgrading CMS. Note: See “CMS Server System Requirements” for recommended swap file sizes. (CMS-9331)



Page 12 of 22


Resolved: When sorting provisioned E7 ONTs in CMS Web, pressing the Sort tab will result in a blank table. (CMS-10547)



Resolved: A loss of JMS between SNMP and JBOSS may cause E5-1xx devices to disconnect from CMS. (CMS-10543)



Resolved: When viewing E3-48C alarms in the EWI’s Alarm Suppression section, no alarm types will be displayed after selecting E3-48C in the device list. (CMS-10492)



Resolved: For E7 alarms, in the embedded-web interface, the environmental pin alarm ID reported does not match the pin AL# provisioned in the system. (CMS-10485)



Resolved: When running a getpm.sh script to query the E-series 10GE port and GE port, 1 day/15 Min data bin report, all of the values are same, but in the CMS GUI and Web GUI, the performance report for 10GE and GE ports are different. (CMS-10237)



Resolved: When provisioning an E7 GPON ONT from the Services page, there is no option to enable or disable the RF return port (AVO). (CMS-10116)



Resolved: When running CMS inventory tasks for E7, the tasks may get stuck “in progress” and may fail or not complete. (CMS-10055)



Resolved: E7 discovered ONT reports have several blank fields. (CMS-10002)



Resolved: After upgrading to R12.1, provisioning E7-20 SIP service may fail. (CMS-9943)



Resolved: When viewing Administration > Alarm Redefinition > E7 the alarm “xdsl-port-los” is missing. (CMS-9893)



Resolved: The ONT dying gasp alarm, ONT-DYING-GASP, does not have a description in the alarm details. (CMS-9705)



Resolved: The default inventory snapshot for the E3-48C is not listed under System > Scheduled Tasks > Inventory Snapshot. The E7’s default inventory snapshot includes the E348C, even though the note for the snapshot says “Default E7 weekly inventory download task on Sunday 6am.” (CMS-9653)



Resolved: When creating a VoIP service at the Voice port level on an ONT, the svc-tag-action and host protocol are missing. (CMS-9498)



Resolved: The “Maximum Video Bandwidth” option in the E3/E5-12x Video Subscriber Template only applies to E5-11x units running R2.0 and lower and E5-12x units running R1.x. (CMS-8302)

E3 and E5-100 Node Management 

Resolved: The “About CMS” screen does not show that CMS R12.x supports the E3-48 release 2.0. CMS R12.x does support E3-48 R2.0. (CMS-10466)

F-Series Network Management 

Resolved: After upgrading to R12.1, deleting a static IP addr ess from an F5 7xx ONT is not available using the CMS client. (CMS-9974)



Page 13 of 22

System 

Resolved: Occasionally, the TL1 adapter may randomly stop working, causing failed orders on Legacy-Q CMS servers. (CMS-10459)



Resolved: On rare occasions, an extended GC (Garbage Collection) may cause the JMS connection to be lost. (CMS-10073)



Page 14 of 22

General Notes Notes, Constraints, and Feature Support Considerations AE ONTs 





In CMS R11.3 and lower, the Disable on Batt parameter on Calix 700-Series ONTs is disabled by default for FE/GE ports. As a fix for CMS-7596, for R12.0, the default is now enabled for newly discovered AE ONTs. Following an upgrade to R12.0, for any previously discovered AE ONTs, you must manually update the Ethernet port setting to Y to enable the setting. (CMS-12015) 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) In R12.1 and higher, for AE ONTs, changing the DHCP lease limit on the default Ethernet Security Profile is not allowed. (CMS-10427)



In CMS R12.1 and higher, an ONT template cannot be applied on an E7 GPON 836GE ONT via XML NBI. (CMS-8989)



In the ONT Services screen, when the subscriber ports are collapsed, typing a value in the Subscriber ID field and clicking Copy To All Ports fails to copy the information. Workaround: Expand all ONT ports before clicking Copy To All Ports. (CMS-4797)

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)


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)



Occasionally, when migrating an OccamView database to CMS R12.1 or higher, if a region relationship is changed manually, the migration process may break. Workaround: Change back the region manually in OccamView. (CMS-10180)


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) Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10


Page 15 of 22



Occasionally, when initially opening the CMS client GUI, error message “Couldn’t create socket with CMS server” may pop up and not go away until you click “OK” multiple times. (CMS-9908)



When creating a VLAN-IF from the Services tab using a Subscriber template referencing a VLAN-IF template with the setting Prio=Priority 4, it will not appear on the Services tab entry after selecting the Video subscriber template and it will not apply the Priority to the VLAN-IF when created by the Service. (CMS-9791)

CMS Desktop 

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 usin g different usernames. (CMS-11807)



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)

CMS Upgrades 

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 l ess 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)



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



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) Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10




Page 16 of 22

The following packages are needed in a freshly installed 64-bit CentOS Linux: glibc.i686, telnet, zlib.i686, libgcc.i686. (CMS-10767) 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 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)




E7 platforms using global TDM Gateway profiles must be running R1.2.60 or higher. (CMS12020) Alphanumeric IDs for the ONT Smart Activate feature are currently only supported on E7 GPON platforms running E7 R2.2 and higher. (CMS-12019)



CMS will attempt to sync dial plan profiles that no longer exist to an E7 NWTK. The sync will fail with error message “illegal character in rule.” (CMS-10886)



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)



E7 ONTs profiles are managed in the E7 firmware. CMS does not support global ONT profile creation. (CMS-9818)



When syncing MVR profiles to the E7 device, make sure the "local vlan" setting under MVR profile is set to "Y" so that the MVR profile will use the local VLAN on the E7. (CMS-9128)



Page 17 of 22

CMS XML Northbound Interface API Updates in R13.0 The following XML NBI API parameters have changed from R12.1 to R13.0

Section in CMS R13.0 NBI XML API Guide

Updates

AE Service Activation and Querying  Default Change: Element Tag XML input element tags The default changed from true to false (page 356, 470). and values (CMS-10426) 

Creating and Deleting AE ONTs

Global ONT Profile IDs Beginning in R12.0, the 741GE ONT profile has been removed, as this product is non-existent. The profile ID numbers have shifted accordingly (page 503). (CMS-7644)

C7 Service Activation and Querying 

Creating and Deleting C7 ONTs

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

E7 GPON ONT Service Activation and Querying T-Series ONT provisioning



E7 GPON ONT Profile IDs: Updated to include T-Series ONT Profile IDs (page 395).



Removed the 741GE ONT profile ID Beginning in R12.0, the 741GE ONT profile has been removed, as this product is non-existent (page 395). (CMS-7644) Requirement Change: When creating a TDM Gateway service, the OntIpHost field is required (pages 436-437). (CMS-9133)

E7 GPON ONT Profile IDs

E7 GPON ONT Voice Service Activation



E3 and E5-100 Service Activation and Querying XML input element tags



Element Tag “5-ETSI” identifier removed (no longer valid) (page 164)



Page 18 of 22

Open Issues AE ONTs 

CMS may not be able to acknowledge or assign a ticket number to AE ONT alarms. (CMS-11058)

Alarms and Logs 

For systems running E7 releases 2.3.35 and lower, there may be duplicate alarms or events. (CMS-11835)



The following alarms are not available for redefinition under Alarm Redefini tion: "SbrportBlkLstARP", "SbrportBlkLstDHCP". (CMS-10734)



When Valere rectifiers connected to CMS trigger a “TrapRegFailed” alarm, the alarm will not clear even with the correct SNMP community. (CMS-10682)



CMS currently does not support reports for C7 or E7 for the GE current port state or SFP. (CMS-10623)


The B6 alarm “vpwrSysACFSet” (AC Fail Alarm Set) will not clear even if the alarm is no longer present on the Valere. (CMS-11414)



There may be a population delay when CMS sends contact closure alarms to remote OLTs. (CMS-11295)



When creating a B6 resync inventory scheduled task to initiate Flow Analyze Endpoint mapping, if the entire network or region is selected, the task may fail or only some line cards will inventory correctly. (CMS-11012)



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



B6 AE ONT alarm emails do not include a User Description field. (CMS-10670)



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 wil l reload at the same time. (CMS-10430)


Occasionally, during an inventory download or a full sync with C7 networks, CMS may not properly write the C7 alarms into the CMS database, causing incomplete alarm reports. (CMS-11492)



The CMS EWI business report does not properly report the correct "ID" in Configuration > C7DataSubscriberTemplate > Configuration Data reports for xDSL bonded subscribers. (CMS-11155)



When retrieving VLAN-IFs on an OC/DS3 port, CMS will retrieve all of the VLAN-IFs for the entire shelf. (CMS-11041) Proprietary Information. Not for use or disclosure except by written agreement with Calix. © Calix. All Rights Reserved. Part #240-00750-10


Page 19 of 22

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



OLTG4 does not display HOST or MFFGW entries at the card level in iMS/CMS because of missing tabs. OLTG4E does not exhibit this problem. Workaround: Use rtrv-ip-host in TL1 for OLTG4 to retrieve the entries. (CMS-10366)



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 

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



When launching CMS via Command Center, a WebRenderer Pop-Up may appear. (CMS-11910)



The popup error message “Not Equipped for Retrieving Specific Info” when navigating to Network > Node > Environment does not give proper indication of the error. Solution: This popup error message has been changed to “External Control - Not equipped for retrieving specific equipment.” (CMS-11226)



On rare occasions, CMS may indicate that processes are down in the GUI when they are up on the server. (CMS-11057)



Occasionally, the CMS web interface may crash due to an OutOfMemoryError. (CMS-10751)



Some E7 and AE ONT events may display the incorrect date and time. (CMS-10526)



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 XML NBI API 









When sending the XML request to suspend traffic and services on C7 GPON ONTs, the response may be “feature not provided” when using the sample provided in the CMS XML Northbound Interface API Guide. (CMS-11745) Deleting provisioned C7 ONTs using XML is not currently supported. Workaround: Use one of the following XML NBI tags to remove specific services, then delete the ONT: , , , . (CMS-11744) When executing read command requests against an E5-111, XML execution errors may occur. (CMS-11728) Occasionally, when updating DSL services using XML NBI with a subscriber ID, the request may take up to 3 minutes to return when a subscriber ID is present in the request. (CMS-11395) The tag should never be used when the SIP GW Profile is selected. (CMS-10530)



Page 20 of 22


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-11797)



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



For E7 and E3-12C TDM service, OSMINE TL1 agent will accept GR-57 or D4 end points. (CMS-11563)



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. (CMS-11276)



When migrating to E7 GPON8 (R2.2.80.2) under the GPON that you are migrating to, the ONTs do not show ranging in. (CMS-11061)



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



The E5-400 IGMP mode “Snoop-Suppress” is not present in the CMS EWI, but the cut through web feature shows this mode as an option. (CMS-10750)



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 pro vision a VLAN ID as 4094. (CMS-10539)



W hen 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)



After upgrading to R12.1, provisioning E7-20 SIP service may fail. (CMS-10374)

 

In CMS, the service name for RG is “Gateway Service,” but, in CLI, the service name is Data Service.” (CMS-10267) T-Series ONTs do not support Native Mode as an option for the Management Mode. (CMS-9991)



CMS R12.1 or E7 R2.2 and lower does not support the “ONT dying gasp” alarm. (CMS-9704)



Using an E7-20‘s GE access port subtending to other nodes has these functional limitations: no RSTP support, no LLDP support, single point fiber link with no protection, and CMS cannot create topology links for access ports. (CMS-9208)



Page 21 of 22

When the MCC shelf view is changed from TOP/BOTTOM to BOTTOM/TOP, the changes are applied, and then after logging out and back in, the view reverts to the initial configuration. (CMS-8225)

E3 and E5-100 Network Management 

Occasionally, E5-121s may be in the disconnected state even though the web and telnet cutthrough work as expected. Workaround: Apply the JMS patch to resolve this issue. (CMS-12002)

E5-308 and E5-520 Network Management 

On rare occasions, the CMS display may temporarily show the login page of the E5 when moving between different E5 nodes in CMS. Workaround: This condition will clear itself in a few seconds. (CMS-11685)

System  

The following packages are needed in a freshly installed 64-bit CentOS Linux: glibc.i686, telnet, zlib.i686, libgcc.i686. (CMS-11481) Upon start-up, CMS does not warn the user if there are permission issues with the CMS directory. (CMS-10846)



Page 22 of 22

Calix User Documentation View or download Calix user documentation from the Calix Resource Center ( www.calix.com )

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.

O n l in e s u p p o r t You can create and manage technical support cases online from the Calix Service Station. To access the Calix Service Station, log in to the Calix Resource Center and then click the Service Station button to:  

Submit a new technical support case, or check/update the status of existing cases. Review product orders, including ship dates and tracking information.

C a li x T A C c o n t a c t i n f o r m a t i o n Online Support (Calix Resource Center) : support.calix.com Phone : 877-766-3500 (toll free) or 707-766-3500 (direct)

C a l ix S e v e r i t y D e f i n i t i o n s 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.


CMS_CALIX_13.0.143

Recommend Documents