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. With Operations Cloud, you can configure end-to-end data services and managed services quickly using streamlined templates, and automate day-today operations for your network.

With an integrated view from the access edge to the Wi-Fi antenna, Operations Cloud continuously gathers unified data from your network infrastructure. For the network operator, this translates to increased visibility to:

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 22.4:

Feature Category

New Feature/Enhancement


Health Monitoring and Predictive Maintenance


Alarm usability enhancements

  • Ability to set the default severity of alarm names per organization.
  • Support for excluding alarms from the real time view by default per organization, while allowing the exclusions to be overridden by the user with persistence.
  • Ability to manually acknowledge/un-acknowledge alarm instances, where acknowledged alarms are filtered out from the real time alarm feed only.
  • Ability to manually suppress (shelve) alarm instances from the real time and active alarms lists.
  • Alarm table displays the number of impacted subscribers for ont-missing and loss-of-pon alarms.
  • Geo Map View:
    • Supports filtering alarms by region, location, system, FSAN, and system type.
    • Provides a toggle switch to hide healthy systems, allowing the BSP to view all systems or only systems with alarms.
    • Includes a legend to distinguish OLT, ONU, and other devices.

Configurable health monitoring thresholds

  • Supports ability to set OLT interface and ONT health monitoring threshold crossing alerts (TCAs) per organization.
  • Displays notifications for threshold crossing events, viewable from the Issues > Historical reports page.

Network and Services Automation Workflow

Workflow enhancements

  • Supports ability to:
    • Reorder existing workflow operations via drag-and-drop, facilitating easy updates of on-discovery workflows including software upgrade tasks.
    • Export workflow results to a CSV file, allowing the BSP to act on results outside Calix Cloud.
    • Delete system groups that still contain member systems, simplifying workflow group management.
    • Automatically apply voice profiles to discovered systems without using a workflow—even when voice service is not pre-provisioned on a system.

Managed EDGE Suites

SmartTown Wi-Fi services

  • Delivers authenticated Passpoint 2.0 Wi-Fi access throughout neighborhoods and public spaces for:
    • Service Provider Wi-Fi: serving BSP wireline subscribers and/or invited non-wireline end users.
    • Organizations: serving associations or mobile workers of municipalities.
    • Events: serving end users attending fairs, conventions, festivals, concerts, etc.
  • Connects end users of participating academic institutions to the native global Eduroam (education roaming) Wi-Fi network.

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 R21.4.x


E9-2 ASM

  • E9-2 ASM3001 aggregation service manager card

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


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

See CMS Release Notes2, 3

E7-20 OLT


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


Systems Management

Min. Software


Calix Management System (CMS)



CMS Probe for Operations Cloud


1 Supports operation as an Active Ethernet OLT.
2 For EXA, the minimum software version to support IPFIX is R3.4.40 (GPON only).
3 The Access Analyze Lite Probe requires a minimum EXA software version of R3.4.30.
4 For CMS, the minimum software version to support IPFIX is R15.1.621.
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.

Calix Subscriber Systems

Product Family



Min. Firmware

GigaSpire BLAST4
Edge Systems

  • u8xe (GS4237)




  • u6e (GS2037E)7




  • u6x (GS4227)7
  • u6xw (GS4227W)7



(R22.2.0 for XGS-PON ONT SFP+ only)


  • u6me (GM2037)




  • u6.1 (GS4220E)7
  • u6.2 (GS4227E)7
  • u4 (GS2028E)7





  • u4m (GM1028)



  • u4g (GS2128G)7



GigaPro Edge Systems


  • u6he (GPR2032H)7

RG or Mesh Outdoor PoE



  • GPR8802x

ONT + PoE switch



  • 844GE
  • 854G
  • 844G





  • 844E


GigaPoint4 ONTs


  • 801Gv1
  • 803Gv1



  • GP1100X
  • GP1101X
  • GP1000X
  • GP4200XH



  • 801Gv2



GigaHub4 ONTs


  • GH3200X



  • 813G
  • 812G




P-Series ONTs5

  • 700GE SFUs



1 GPON ONT (or GPON mode for auto-detect)
3 everyPON ONT (SFP+ WAN optics)
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 Supports SmartTown Wi-Fi

Note: Operations Cloud communicates directly with AXOS OLTs via the Netconf/YANG interface, with IPFIX for telemetry. Therefore, no interface with SMx is required for Operations Cloud management of AXOS OLT systems.

Important Considerations

Unsupported Functionality

Known Anomalies

The following table lists known anomalies in Operations Cloud.

Issue Number



For AE ports, transmit counters reflect the downstream direction and receive counters reflect the upstream direction.


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.


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.


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 transform alarm detail provides the user ID information rather than the ONT location.


When the service provisioning process triggers a delete or update of a VLAN membership, a "ReadTimeout:while POST" error may display and the service may not successfully complete for a long period of time.


If an EXA OLT is disconnected within 4 hours after syncing with CCO, IPFIX does not sync until the daily inventory sync occurs.


Performing a manual redundancy switchover from an E7 OLT immediately after establishing a Call Home connection with Operations Cloud may cause ONT service provisioning in a pending state to fail.


After connecting to a CMS/EXA OLT and syncing all existing active alarms, the current OLT alarms do not display in the Geo Map.


In transform alarm reports, the source strings include internal values.


After deleting the CMS from Operations Cloud, EXA systems associated with the CMS may show a communication status of DELETE_IN_PROGRESS continuously.


If the region or location is changed after pausing an alarm notification schedule, the notification trigger sets to immediate and cannot be updated.


After moving an integrated ONT from an AXOS OLT to an EXA OLT, the ONT is not deleted from AXOS and therefore the ONT status does not update in Operations Cloud.


Operations Cloud does not support querying ONT health data by ONT ID.


Operations Cloud does not support configuring a static IP address on a single-system ONT such as an 844G or u6x.


From the Health > ONT tab, the ONTs With Low Light Levels KPI and corresponding charts do not display data.


Operations Cloud does not support service configuration via RG profiles.


From the Traffic > Locations page, selecting 'All' for the location filter generates different results for real time traffic and reports.


Operations Cloud does not support using the same VLAN across different service templates.


The Traffic Usage Insights API call does not return the correct schema.

Open Issues

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

Issue Number



Deploying a new end-to-end service in Operations Cloud causes the original service from the billing data to be overridden, affecting subscriber visibility in Calix Marketing Cloud and Calix Support Cloud.


After increasing the flow configuration real-time delay, the Top 5 Endpoints chart displays no data and the rate drops to zero in Traffic > Real Time page until refreshed.


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 alarm notification email report does not reflect that an alarm has been manually acknowledged and shelved.


After acknowledging and clearing an EXA alarm, a new instance of the same alarm will be auto-acknowledged in the detailed alarm summary available from the Issues > Active Reports page.


After setting a custom alarm severity, the Alarms by Severity historical report shows an incorrect alarm count.


Operations Cloud VLAN interface provisioning may fail due to a time-out if the target AXOS system software version is AXOS-R22.2.0 or earlier. Workaround: Manually pre-provision the VLAN interface from the AXOS system CLI and then trigger a Force Sync from Operations Cloud.


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.


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.


After provisioning services from Operations Cloud, the NGPON2-4 card has very slow speed test results due to the IP policy map not allowing the expected throughput.


The numbers of OLT alarms in the Geo Map View does not update after an alarm is shelved.


The Ethernet port loss-of-signal alarm does not trigger the subscriber impact field to be populated (when attached to an AE ONT). As a result, the subscriber impact chart in the landing page may be off for AE ONTs.


The "New Connected and Synchronized Systems" counter on the Home page shows a frequent change in connection status due to SOAP fault tolerance control issues.


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


From the Issues page, the AE ONT Dropped and NTWK Dropped alarms do not display for the:

  • Real Time > Exclude Alarms filter.
  • Active Reports > Alarm Name filter.


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.


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.


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.


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.


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


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.


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


When 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 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.


It is not possible to provision a service where the VLAN is tagged between the ONT and RG when the ONT and RG are two separate systems.


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.


For services to come up, AXOS OLTs must bring up the l2-dhcp-profile name as CCO_L2_DHCP_PROFILE before calling home.


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-01879, Rev 10)