About Operations Cloud

Calix Operations Cloud improves and accelerates your organization's goal of delivering an outstanding subscriber experience with simplified operations and intelligent insights, including:

Without engaging in swivel chair operations, Operations Cloud empowers the network operator to deliver a seamless subscriber experience.

What's New in this Release

New features or enhancements introduced in release 23.2:

Feature Category

New Feature/Enhancement


Health Monitoring and Predictive Maintenance


Health, alarm, and troubleshooting enhancements


Ability to quickly identify and assess the extent of subscriber Internet outages by:

  • Visualizing Internet service outages on a geomap.
  • Receiving an Internet Outage email notification when subscribers are impacted by an outage over a 15-minute interval.
  • Delivering a subscriber outage message on the subscriber page in Support Cloud (requires both Operations Cloud and Support Cloud entitlements).

Support for a weekly report on ONT optical light level outliers based on machine learning of potential PON service issues.

On-demand access to a real-time snapshot of OLT or ONT performance data and statistics, enabling quick troubleshooting and verification.

Ability to monitor:

  • Active Ethernet health on EXA systems CMS-managed AE ONTs.
  • PON/Ethernet on EXA systems with mixed PON and DSL cards.

Network and Subscriber Operations



Workflow enhancements

Support for access control list RG profiles to block unsolicited Internet traffic to remote management and VoIP interfaces via workflows.

Support for an on boot workflow triggered when the CPE is powered on by the user, pushing upgrades and service provisioning on boot to eliminate additional maintenance windows.

Improved management of software images, including identification of supported Calix ONU images and a sortable image table.

Notification of scheduled performance test conflicts with Calix Cloud maintenance windows.

Subscriber Services


Support for end-to-end MVR and non-MVR video service provisioning on AXOS systems, simplifying provisioning across the network.

Ability to provision all POTs voice services on a single ONT or RG.

For a summary of additional Calix Cloud enhancements in this release not specific to this application, refer to the Release Notes for the Calix Cloud Platform.

Systems Support


Calix AXOS Systems Hardware

Min. Software

E9-2 OLT


  • E9-2 CLX3001 control & aggregation switch card
  • E9-2 GP1612 line card
  • E9-2 NG1601 line card

AXOS R22.2

  • E9-2 XG3201 line card

AXOS R23.2

E9-2 ASM

  • E9-2 ASM3001 aggregation service manager card

AXOS R22.2

E7-2 OLT

  • E7-2 CE201 aggregation card1
  • E7-2 GE-24 r2 line card1
  • E7-2 10GE-12 aggregation card1
  • E7-2 GPON-8 r2 line card
  • E7-2 XG801 line card
  • E7-2 NGPON2-4 line card

E3-2 OLT

  • GP401 interface module
  • NG201 interface module


Calix EXA Systems Hardware

Min. Software

E7-2 OLT
(or DSLAM)

  • E7-2 GPON-8 line card
  • E7-2 GPON-4/ r2 line card

EXA R3.4.402

  • E7-2 GE-24 line card
  • E7-2 GE-12 aggregation line card
  • E7-2 VDSL2-48 r2 line card 3
  • E7-2 VDSL2-48C r2 line card 3

EXA R3.4.504

E7-20 OLT

  • E7-20 GPON-16x line card
  • E7-20 GPON-8x line card
  • E7-20 GPON-4x line card

EXA R3.4.402

  • E7-20 GE-24x line card

EXA R3.4.50


Systems Management

Min. Software


Calix Management System (CMS)



CMS Probe for Operations Cloud


1 Supports operation as an Active Ethernet OLT.
2 For EXA systems, the minimum EXA software version to support health data via IPFIX is R3.4.40 (GPON or VDSL only); however Calix recommends upgrading to EXA version 3.4.50 for full system and feature robustness.
3 On EXA DSL cards, IPFIX is supported for Ethernet ports only.
4 EXA R3.4.50 requires CMS R15.1.764.
5 You may download the CMS probe from the Calix Software Center for use with an earlier CMS version (other than the current production release).

Important: Calix recommends upgrading the CMS before upgrading EXA systems. If an EXA version does not show as updated in CMS following the upgrade, disconnect and reconnect the EXA system in CMS to trigger an update in the database. See the Calix Management System Guide for instructions.

Note: For automated telemetry, Operations Cloud communicates directly with AXOS OLTs via the Netconf/YANG interface.

Calix Subscriber Systems

Product Family



Min. Firmware

GigaSpire BLAST4
Edge Systems

  • u10xe (GS4237)


R23.2.0 (PON), (AE-future)


  • u4g (GS2128G)




  • u4hm (GM1028H)

Mesh satellite



  • u4xg (GS2128XG)




  • u6x (GS4227)8
  • u6xw (GS4227W)


R22.4.0 (PON, AE)


  • u6.1 (GS4220E)
  • u6.2 (GS4227E)
  • u6e (GS2037E)
  • u4 (GS2028E)




  • u6me (GM2037)
  • u4m (GM1028)

Mesh satellite


GigaPro Edge Systems and ONTs

  • p6he (GPR2032H)

Outdoor RG or mesh satellite, PoE




  • GPR8802x

ONT + PoE switch

R22.4.0 (PON), (AE-future)


  • 844GE


R12.2.13 (GPON, AE)


  • 854G
  • 844G





  • 844E



GigaPoint4 ONTs

  • GP1000G
  • GP1100G




  • GP1007X




  • GP4200AH


R23.2.0 (GPON), (AE-future)


  • GP1100X
  • GP1101X
  • GP1000X
  • GP4200XH




  • 801Gv1
  • 803Gv1




  • 801Gv2



GigaHub4 ONTs

  • GH3200X



  • 813G
  • 812G



P-Series ONTs5

  • 700GE SFUs


R10.8.110 (GPON), R10.7.122 (AE)

1 GPON ONT (or GPON mode for auto-detect)
3 everyPON or AE ONT (SFP+ ONT module in WAN port)
4 Supports optical signal levels
5 Support for optical signal levels varies by part number; for more information see the Quick Tip Identifying the Optical Signal Level (OSL) Reading at the ONT or use the CLI 'show ont [id] detail' command (CCL-44061)
6 On the 717GE, POTs ports 'pot3' and 'pot4' are not supported (CCL-39777)
7 GPON/AE auto-sense ONT
8 Does not support untagged WAN configurations if the WAN_TYPE is GPON or XGSPON

Important Considerations

Unsupported Functionality

Known Anomalies

The following table lists known anomalies in Operations Cloud.

Issue Number



When moving an ONT from one AXOS system to another without properly removing the ONT, the old AXOS system may report an ont-missing alarm against the previous ONT ID, resulting in the geomap reporting an outage.


After suppressing alarms from a config object in an AXOS OLT, newly triggered alarms from that config object do not display in the active report or history reports in Operations Cloud, causing a mismatch with the AXOS system CLI until the OLT is disconnected and reconnected.


After disabling and then re-enabling the service or updated service with another data plan for a two-box model, the service status displays an error message which changes to "Successfully Provisioned" following a retry. This can take ~10 min.


After disabling and then re-enabling service on an RG, the service status displays an error message which changes to "Successfully Provisioned" following a retry.


When selecting service type "MGCP" or "TDM GW" in the service profile, the primary and secondary DNS fields display under the ONT parameters.


When using API endpoint POST/subscribers/{subscriberId}/services to attach voice and data together, the response is error code 400. Workaround:

  • Use PUT/subscribers/{subscriberId}/services to attach voice and data together.
  • Use POST/subscribers/{subscriberId}/services to create the services one by one—first data and then voice.


For a standalone RG, after editing parameters in an existing service profile associated to a subscriber, you must disable and then re-enable the service. For a two-box deployment or standalone ONT, once the service definition template (policy map) is provisioned on the OLT, for any bandwidth to be applied you must create a new service definition template and update the service with it.


After successfully connecting to Operations Cloud via Call Home, it may take up to 5 minutes for the OLT pushpin with the total number of alarms to display in the Issues > Real Time > Map View. Workaround: Use the Table View.


The search bar on the System Groups page does not:

  • Display partial results as you type. Workaround: Click the magnifying glass to view results.
  • Provide an option to clear the search. Workaround: Manually delete text from the search bar.


When replacing a GPON RG associated with an EXA OLT, delete the old RG from the subscriber and then perform a force sync operation.


ONT auto-delete does not occur when moving an ONT from one RG to another RG. Workaround: Disconnect the ONT cable from the RG and then manually delete the ONT from the UI.


When replacing the ONT in a two box solution, you must manually disassociate and delete the ONT from the subscriber.


When both an ont-missing alarm schedule (separately or combined with other alarms) and a transform alarm schedule are created, Operations Cloud only monitors and emails an alarm report for the transformed alarm.


When the USOC for an existing subscriber service is replaced, immediately followed by a connection error with the OLT, the data plan may not be updated.


When an ONT resets, the ONT Health Timeseries chart displays gaps in the lines which may not align, as some data is binned while other data is running time.


Operations Cloud ONT health does not report ONT RX power levels for 760-series ONTs because those ONTs do not report RX power level.


When moving an existing subscriber from an Ethernet policy-map to an IP policy-map in SMx prior to provisioning services in Operations Cloud on the same VLAN, you must manually delete the Ethernet policy-map applied to the VLAN, which impacts ONTs using the VLAN.


When an ONT name that uses the account ID format is updated in Operations Cloud, the AXOS system continues using the original ONT name.


The Alarm Status displayed on the Systems > Network Systems page may not be accurate because the CMS probe synchronizes alarms irrespective of the CMS and/or EXA OLT state in Operations Cloud.


Updating the data service associated with a two box deployment from DHCPv4 to dual stack removes the default WAN setting from a GigaFamily RG.


Even if provisioning an IPv6-only service, Operations Cloud enables both IPv4 and IPv6 interfaces for TR069, so the web-UI of the RG will indicate the WAN is provisioned for both IPv4 and v6.


After adding a new ONT via CMS/EXA, the health KPIs may not display in Operations Cloud within 24 hours as expected. Workaround: Wait one more day for CMS to sync with Operations Cloud.


Operations Cloud provisions the 803Gv2 as an 844G on E7 EXA systems because there is no 803Gv2 profile in EXA.


Disabling the data service via Operations Cloud on an RG loaded with a firmware version below R21.4 affects the TR-069 connection to Calix Cloud. Workaround: Do not disable the data service from Operations Cloud. If this occurs, factory reset the RG to bring it back online.


When an ONT fiber is unplugged for less than 15 minutes with the power on, then re-connected, the AXOS OLT may report uptime continuously, causing the Health page to report an uptime larger than 900 seconds in 15 minutes.

Resolved Issues

The following table lists issues that have been resolved in this release.

Issue Number



The Top Subscribers applications report does not show data when yesterday is specified as the "From Date" and "Rate" is specified as the "Criteria."


After replacing an ONT using the same Reg ID, both the new and old ONTs are associated to the subscriber.


Operations Cloud does not support data and voice services using the default untagged WAN and the same S-VLAN.


In the subscriber record summary page, a retry button does not display to re-provision a failed RG service.


After deleting and re-adding an AXOS OLT to Operations Cloud, alarms that display in the Issues > Active Reports page may not match alarms generated via the AXOS CLI 'show alarm active' command. This occurs when alarms are raised and cleared continuously during the sync process.


Operations Cloud does not support integrated ONTs in the Active Systems Geomap.



After modifying an OLT’s region/location, both the old and new region/location display in the Top PON Interface table.


When filtering by ONT FSAN, inventory info is lost on the AE Timeseries and ONT Timeseries charts.


Operations Cloud does not support provisioning two voice services on a single ONT or RG.


Operations Cloud will not configure the secondary DNS on a static data service if the primary DNS isn't also configured.


When configuring a voice service with an ONT line and an RG line, only one IP addressing field displays in the UI.


The geomap alarm count does not update for an ONT that is not associated with a Reg ID or FSAN (serial number and vendor ID).


After deleting the RG association from a two-box model where Operations Cloud auto-mapped the ONT to the subscriber record, the subscriber record cannot be deleted.


The OLT/ONT alarm number in the Issues > Alarm Map View updates after a delay of ~5 minutes following a newly triggered alarm, causing a mismatch with the Active Reports.


Configuring a subscriber data service with a L2 static host does not enable IP Source Verification on the VLAN. Workaround: After configuring the static host, manually configure the source-verify VLAN setting from the network system CLI.


Any port/any service (APAS) is an RG feature that detects the OUI of the device plugged into the RG's Ethernet port, and if it matches a set-top box OUI, the RG applies the full bridge video service to that port. Otherwise, the ONT applies the RG data service to the port. Operations Cloud does not support any port/any service (APAS).

Open Issues

The following table lists the open issues that are applicable to this release.

Issue Number



EXA system alarms that have been acknowledged or shelved in Operations Cloud will reset when resynchronized via the Alarms Force Sync operation.


Alarms from an EXA system continue to synchronize with Operations Cloud when the CMS is disconnected. Workaround: To stop the alarms from synchronizing with Operations Cloud, delete the CMS.


After rebooting a connected and synchronized EXA OLT, an alarm count mismatch may occur between the OLT CLI and Operations Cloud.


After adding a service address to an existing OLT, the geomap alarm count does not update.


After associating an ONT with an existing ont-missing or loss-of-pon alarm to a subscriber, the geomap may take up to 12 hours to indicate an Internet outage.


After successfully upgrading the CMS and re-installing the CMS probe, EXA alarms are duplicated or mismatched in Operations Cloud. Workaround: Manually trigger an alarm force sync.


After suppressing and unsuppressing alarms, the alarm history report in Operations Cloud does not match alarms displayed in the AXOS CLI due to an AXOS alarm handling issue.


When an ONT is auto-mapped to a subscriber with existing services (an associated RG and/or pre-provisioned services), the ONT will be managed by Operations Cloud.


For the two-box model, the "option82-action-pass" command cannot be set causing IPv4 DHCP to fail.


The following API endpoint may not properly update a SIP service:
PUT API /subscribers/{subscriberId}/services/{serviceId}


The "notification_device_disconnected" alarm from CMS does not display in the alarm notification email when expected.


If the IPFIX flow record is missed for a PON port, Ethernet port, or an ONT that has a threshold crossing alarm, then the alarm will be cleared. Upon arrival of the next IPFIX flow record, if the condition for the threshold crossing alarm is still true, then a new alarm will be generated.


After deleting and re-adding a device/region, the device/region name displays in health report charts with an extra five characters appended to the name.


After drilling down to the location level in the Health > PON > Reports page, the System filter field is empty.


Operations Cloud will not provision voice services with static IP addresses on RG interfaces. Workaround: Provision voice services that require static IP addresses on an ONT POTs interface.


The duplicate-ont-reg-id notification is an event in AXOS systems and an alarm in EXA systems, and therefore reported differently in Operations Cloud.


Data does not display in the one-minute Network Traffic report for a flow that arrives late.


For a GPON ONT connected to an E7-2 XG801 line card, the ONT/OLT "Rx Light Level for GPON" thresholds do not work but the ONT/OLT "Rx Light Level for XGS-PON" thresholds work.


The AXOS E9-2 ASM3001 system does not display in the Geo Map View.


On occasion, an AXOS PON interface that does not exceed the 40% throughput threshold may be counted as a PON capacity hit.


The multiple-ONTs-down-network alarm report does not list all affected regions/locations under the Resource field.


When replacing or connecting a new AE ONT, more than one timeseries chart displays in the Health page for the same ONT.


Service provisioning is incompatible with type-B PON protection on both EXA and AXOS systems. Service provisioning will not complete and Operations Cloud will not update the PON port name on the status page when a type-B PON failover occurs.


Service provisioning cannot be deleted when associated to an XGS ONT with a Reg ID longer than 10 characters. Workaround: Configure a Reg ID consisting of 10 or fewer characters.


After updating the bandwidth tier profile for an existing data service via the API or GUI, the new bandwidth is not applied.


The length of the ONT Reg ID is limited to 10 or fewer characters.


On the Health page, the Total PON and Total ONT counts do not immediately change after adding or deleting and EXA/ONT in an existing CMS region. Workaround: Wait 24 hours or perform an on-demand inventory sync from CMS.


After changing the transport type on an interface from PON to GPON, the Health page displays upstream/downstream capacity for a PON interface rather than a GPON interface.

Web Browser Requirements

Using Calix Cloud requires the following minimum web browser versions:

Technical Support

Create and manage technical support cases online. Log in to My Calix, click the Calix Community tile, and then click Calix Service Station.

(Part # 240-01934)