--- title: Telecom Discovery via Nokia Altiplano description: The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/telecom-service-ops/telecommunications-service-operations-management/service-graph-connector-for-nokia-altiplano.html release: australia product: Telecommunications Service Operations Management classification: telecommunications-service-operations-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 5 breadcrumb: [Indirect Discovery with SGCs, Telecom Discovery, Telecom Visibility, Explore, Telecommunications Service Operations Management] --- # Telecom Discovery via Nokia Altiplano The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB. Designed for service providers and telecom enterprises, this connector enables complete visibility, control, and synchronization of your physical and logical network infrastructure. This integration uses REST APIs and a MID Server to deliver a telecom-model-aligned view of your network, enabling more accurate service modeling, inventory management, and operational efficiency. ## Key benefits - Accurate inventory synchronization: Automatically populate the CMDB with up-to-date physical and logical inventory from Nokia Altiplano using secure, REST API-based ingestion. This includes OLTs, ONUs/ONTs, interface cards, ports, slots, and logical connections. - Telecom-Aware CI modeling: Model your network infrastructure in a telecom-aligned format using purpose-built CI classes and relationships. The connector ensures the accurate representation of devices and their dependencies—mirroring your actual network topology. - Simplified and Guided Setup: Reduce time-to-value with a built-in guided setup that walks you through connection configuration, data source management, and import scheduling with ease. - Flexible discovery options: Choose how and when to run discovery based on your needs—whether it’s full bulk loads, targeted filtered discovery, or phased OLT-only imports. Apply custom filters by device IP or name. - Multi-Instance support: Scale effortlessly by onboarding multiple Altiplano instances independently. Configure connection aliases and define import schedules per instance for complete operational flexibility. **Note:** Supported Nokia Altiplano Controller minimum version is 24.6. For a general overview of Service Graph Connector technology, see [Getting started with Service Graph Connectors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/cmdb-sgc-intro.md). ## Nokia Altiplano SGC Architecture The following table illustrates the architecture of Nokia Altiplano service graph connector.
| \# | Stage | Location | Components or sub-flow | Description |
|---|---|---|---|---|
| 1 | Source | Network/IT | Altiplano Controller \(REST\) | External system holding OLT and ONU data. REST is the active protocol for this connector. |
| 2 | Altiplano data source \(custom script\) | MID Server | - REST action \(get access token\) - REST action \(get list of OLT devices\) - REST sub-flow \(get OLT and its related ONUs, physical and logical details\) - Bulk data source - Filtering data source - Filter devices list | REST actions run on the MID Server to get the access token, retrieve the device list, and get device details. |
| 3 | Import sets | ServiceNow instance | Altiplano import set | Imports data from external sources, triggered by *Scheduled Data Import*. The bulk data source pulls all Altiplano data; the filtering data source pulls only data for OLTs that match the filter criteria. *Use Connection* selects the Altiplano connection alias. The import set includes: - OLT physical and logical - ONU physical and logical - Logical ports relationships - Logical connections between OLTs and ONUs |
| 4 | IH-ETL RTE | ServiceNow instance | - Clean, transform, enrich data - Map to CMDB classes and add relationships - Prepare payloads for IRE | Determines which classes are populated based on discovered data and models. Handles transform maps, references of models and BW, CI relationships, and CI references. |
| 5 | IRE | ServiceNow instance | - IRE rules execution - CMDB integration | RTE output is automatically passed to the IRE as a payload. The IRE matches to existing CIs based on identification rules and creates new CIs if no match is found. |
| 6 | CMDB compliance | ServiceNow instance | - Audit - Follow-on tasks - Remediation \(writes to CMDB and TNI\) | Detects CMDB discrepancies, such as relationship mismatches or CIs present in the CMDB but not discovered. Creates a discrepancy report. Resolves discrepancies automatically or manually through the remediation workflow. |