---
sourceDocument: Yokohama Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/telecom-service-ops

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Service Graph Connector for Nokia Altiplano

# Service Graph Connector for Nokia Altiplano {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read

Use the Service Graph Connector for Nokia Altiplano Access Network SDN Controller to pull in data from the Nokia Altiplano software into your ServiceNow instance using REST APIs.

The Service Graphs Connector for Nokia Altiplano pulls in asset inventory data (physical network resources) from the Nokia Altiplano database.

## Request apps on the Store {#service-graph-connector-for-nokia-altiplano__section_irz_2lk_zdc}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#service-graph-connector-for-nokia-altiplano__inline-send-to-store}

## Nokia Altiplano SGC Architecture {#service-graph-connector-for-nokia-altiplano__section_tdk_v1g_12c}

Data Source defined as the following:

* Custom load by script
* Data in single column

{#service-graph-connector-for-nokia-altiplano__ul_avf_z1g_12c}For a general overview of Service Graph Connector technology, see [Getting started with Service Graph Connectors](https://www.servicenow.com/docs/access?context=cmdb-sgc-intro&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

## Supported versions {#service-graph-connector-for-nokia-altiplano__section_opc_cbg_12c}

Supported Nokia Altiplano Controller minimum versions: 24.6.

## Use cases {#service-graph-connector-for-nokia-altiplano__section_snt_jbg_12c}

The following are examples on how you can use the Nokia Altiplano Service Graph Connector:

* **The Nokia Altiplano Service Graph Connector** can be used to pull data from the Nokia Altiplano Access Controller via REST API (through a MID Server), confirming that the CMDB is populated with accurate, up-to-date information about physical network resources such as OLTs and ONTs, among others. This integration provides a telecom-model-aligned view of network resources and their relationships.
* **Future Capabilities**: In upcoming releases, the Nokia Altiplano Service Graph Connector expands its capabilities to discover physical resources, logical resources, and services/connections. This expansion enables a more comprehensive view of both the physical and logical aspects of the network. The connector will also support event-driven discovery. In this mode, the Altiplano Controller notifies the ServiceNow instance (via the MID Server) about a change and sequentially triggers a discovery task.
* Ability to configure and save synchronization schedules.
{#service-graph-connector-for-nokia-altiplano__ul_xpq_1dg_12c}

## Guided setup {#service-graph-connector-for-nokia-altiplano__section_bcc_hdg_12c}

The guided setup for the Service Graphs Connector for Nokia Altiplano provides an organized sequence of tasks to configure the integration on your instance. To access the guided setup, see [Configure Service Graph Connector for Nokia Altiplano](https://servicenow-prod.fluidtopics.net/apjvQ1LaZ1EysUpIAFG59Q#configuring-service-graph-connector-nokia-altiplano "Configure the Service Graph Connector for Nokia Altiplano using Guided setup to integrate network resource data from the Nokia Altiplano Access Controller (REST API) into the ServiceNow CMDB. The setup includes authentication and scheduling steps.").

## CMDB Integrations Dashboard {#service-graph-connector-for-nokia-altiplano__section_r14_jdg_12c}

The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. You can see metrics for all integration runs. You
can filter the view to a specific integration, a specific time duration, or a specific integration run. For more details about monitoring SolarWinds integrations in the CMDB Integrations Dashboard, see [Integration Commons for CMDB](https://www.servicenow.com/docs/access?context=integration-commons-for-cmdb&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

## Import Sets {#ariaid-title2}

The Import Sets are the input for the IntegrationHub ETL, where the transformation maps create and model relationships. When data is loaded into the Import Set, the transformation process is triggered.

### Before you begin

Role required: admin

### Procedure

Navigate to AllSystem Import setsAdministrationImport Sets.  
The Data Source script automatically creates staging tables.

## Data Mapping {#ariaid-title3}

Data from data sources in the Nokia Altiplano software is mapped and transformed into ServiceNow CMDB tables using the Robust Transform Engine (RTE). Data is inserted into ServiceNow CMDB using the Identification and
Reconciliation Engine (IRE).

When you complete the guided setup, you can configure the integration to periodically pull data from the SolarWinds software.

The data is loaded into staging tables, then inserted into the following CMDB target tables with the following relationships:

### Mapping CMDB CIs and CI Relationships (Physical Layer) {#data-mapping__section_ihp_thg_12c}

{#data-mapping__table_dfm_5hg_12c__entry__2}

| CIs | CI Relationships |
|-|-|
| OLT CI | OLT Device is represented by the OLT CI. Table name: ****cmdb_ci_optical_line_terminal**** OLT CI contains Slot CIs. |
| ONT CI | ONT Device is represented by the ONT CI. Table name: ****cmdb_ci_optical_network_terminal**** ONT CI contains Network Interface CIs. ONT Network Interface CIs is contained by the ONT CI. |
| Slot CI | Chassis slots are represented by the Slot CI. Table name: **cmdb_ci_container_slot** Slot CI is contained by OLT CI. Slot CI contains the Interface Card CI (LT/NT cards, Fan/PSU units). |
| Subslot CI | LT/NT card cages are represented by the Subslot CI. Table name: **cmdb_ci_container_subslot** Subslot CI is contained by OLT LT card CI. Subslot CI is contained by OLT NT card CI. Subslot CI contains the Interface Card CI (transceiver cards). |
| Interface Card CI | LT and NT cards are represented by the Interface Card CI. Transceiver cards are represented by the interface Card CI. Fan and Power Supply Units are represented by the Interface Card CI. (Special cards, Fan, and Power Supply Units CI might be changed in the next releases). Table name: **cmdb_ci_interface_card** LT Card contains the Subslots CIs. NT Card contains the Subslots CIs. NT cards CIs contains Network Interface CIs LT/NT transceiver cards CIs contains Network Interface CIs. LT/NT Card CI is contained by the LT/NT Slots CI. LT transceiver Card CI is contained by the subslot CI (LT Card). NT transceiver Card CI is contained by the Subslot CI (NT card). |
| Network Interface CI | LT card PON access ports as well as NT card network ports are represented by the Network Interface CI. Table name: **cmdb_ci_ni_interface** Network Interface CIs contained by LT transceiver/NT transceiver/NT cards CIs. ONT Network Interface CI is contained by ONT CIs. |
[ ]

{#data-mapping__table_dfm_5hg_12c}

You can use the **IntegrationHub ETL** application to view and manage data maps.

For more information, see [IntegrationHub ETL](https://www.servicenow.com/docs/access?context=integrationhub-etl&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

### Supported xNFs {#data-mapping__section_jpy_shg_12c}

* Lightspan MF-2 (OLT)
* Lightspan ISAM FX-4 (OLT)
* Lightspan XS-010X-Q (ONT)
* Lightspan XS-010X-R (ONT)
{#data-mapping__ul_gjk_skg_12c}

## Special System properties {#ariaid-title4}

Service Graph Connector for Nokia Altiplano installs special system properties that control various behaviors of the application.

### Before you begin

Role required: admin

### Procedure

Navigate to AllService Graph ConnectorsNokia AltiplanoProperties.  
You can also access these properties by entering **sys_properties.list** and filtering by the name '\*altiplano'.  
{#special-system-properties__table_xyy_pwg_12c__entry__3}

| Property Name | Recommended / Default Value | Description |
|-|-|-|
| sn_sgc_altiplano.olt_batch_size | 300 | The OLT Datasource batch size for REST Calls. The number represents number of Altiplano response entities. (Increasing may cause failure in the REST actions execution) |
| sn_sgc_altiplano.onu_batch_size | 3 | The ONU Datasource batch size for REST Calls. The number represents number of LT cards related ONU data. (Increasing may cause failure in the REST actions execution) |
| sn_sgc_altiplano.onu_ci_class | ONT | ONU CI Class, Valid values: ONU or ONT |
[Table 1. Nokia Altiplano SGC System Properties]

{#special-system-properties__table_xyy_pwg_12c}

## Retrieving Data from Nokia Altiplano via REST API {#ariaid-title5}

Examples of Retrieving Data from Nokia Altiplano via REST API.

### URL format {#retrieving-data-nokia-altiplano-API__section_in5_c43_12c}

Versioned URL: POST: altiplano-indexsearch/latestcompleted-inv/_search  

### For OLT {#retrieving-data-nokia-altiplano-API__example_cb1_2p3_12c}


    {
        "_source": [
            "deviceAVmetadata",
            "inventorymetadata",
            "inventorydata.ietf-hardware:hardware",
            "inventorydata.ietf-hardware:hardware-state",
            "inventorydata.nokia-state:state"
        ],
        "sort": [{"_id": {"order": "asc"}}],    
        "from": 0,  
        "size":300
    }

### For ONU {#retrieving-data-nokia-altiplano-API__example_ccz_gp3_12c}


    {
          "query": {
                "bool": {
                    "should": [
                        {
                            "exists": {
                                "field": "inventorydata.ietf-interfaces:interfaces-state.interface.bbf-xponvani:v-ani.onu-present-on-this-olt.detected-serial-number"
                            }
                        }
                    ]
                }
        },
        "_source": [
             "inventorydata.ietf-interfaces:interfaces-state.interface.bbf-xponvani:v-ani.onu-present-on-this-olt.detected-serial-number",
            "inventorydata.bbf-fiber-onu-emulated-mount:onus.onu.root.ietf-hardware-mounted:hardware-state",
            "inventorydata.bbf-fiber-onu-emulated-mount:onus.onu.name"
         ],
        "sort": [{"_id": {"order": "asc"}}],    
        "from": 0,  
        "size": 3
    }

*[\>]: and then