This article applies if you are using the built-in Calix SMx Template Nodes for provisioning (released July 2026).
This article explains the fields found under Settings > Integrations > Calix > Product Mapping and how to update mappings you already had in place.
Overview
Product Mapping tells gaiia how to provision each of your products on your Calix SMx network platform. For every gaiia product mapped to Calix, you define the service template and policy map that gaiia applies when it provisions an ONT, so routed and bridged scenarios resolve automatically without custom workflow logic.
This section was previously named ONT Policy Mapping. It has been renamed to Product Mapping and now includes two new fields, Service Template and Tagged Policy Map, alongside the renamed Untagged Policy Map (formerly ONT Policy).
These fields are required. Any mapping you had configured before this change must be completed with the new values before you can save it or provision further.
Product Mapping fields
Each row maps one gaiia product to the Calix configuration used to provision it. The values you enter come from your Calix SMx configuration.
| Field | Description | Required |
|---|---|---|
| Service Template | The name of the service template configured on your Calix SMx that gaiia applies to the ONT's data service when provisioning this product. It must match the template name exactly as it appears in Calix. | Yes |
| Untagged Policy Map | The Calix policy map gaiia applies for a standard (bridge) deployment. This is the default and holds the value your previous ONT Policy field used. | Yes |
| Tagged Policy Map | The Calix policy map gaiia applies for an all-in-one (tagged or routed) deployment. gaiia selects this map instead of the untagged one when the ONT is provisioned as tagged. | Yes |
Scroll right to view the whole table on smaller screens.
Understanding tagged and untagged policy maps
gaiia now resolves the correct policy map from the ONT itself instead of relying on naming conventions or hardcoded workflow logic:
- Untagged — the standard behavior and the value your existing mappings already used. Use this for deployments where the ONT is a bridge unit where the UNI is not accepting a VLAN tag.
- Tagged — used for all-in-one (AIO/RG) units. gaiia applies the Tagged Policy Map when the ONT model is configured as tagged.
Because both maps are defined on the product, the same product can be provisioned either way without a separate mapping or custom flow.
Updating your existing mappings
If you had mappings configured before this change, complete the new required fields for each one.
Integration settings can only be edited by users with the Settings > Edit permission enabled.
- Go to Settings > Integrations > Calix > Product Mapping.
- For each mapped product, enter the Service Template name as configured on your Calix SMx.
Confirm the Untagged Policy Map value.
If the row previously used the ONT Policy field, that value carries over here. Verify it is still correct.
- Enter the Tagged Policy Map value to use for all-in-one units.
- Click the
Savebutton.
Until every required field is filled, the mapping cannot be saved and provisioning for that product will not proceed.
Related ONT Mapping fields
The neighboring ONT Mapping section (formerly ONT Profile Mapping) was updated at the same time and works together with Product Mapping:
- ONT Profile — the Calix ONT profile (formerly ONT Profile Id).
- Policy map variant — whether this ONT resolves to the Untagged or Tagged policy map.
- ONT Main Port — the main UNI port on the ONT (for example, g1 or X1).
Not sure which values apply to your network? The service template, policy map, and ONT profile names all come from your Calix SMx configuration. Coordinate with your network team, or reach out to gaiia support and we will help you confirm them.