Mapping Nokia Altiplano CIs and Relationships in CMDB

  • Release version: Australia
  • Updated March 12, 2026
  • 5 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Mapping Nokia Altiplano CIs and Relationships in CMDB

    The Service Graph Connector (SGC) for Nokia Altiplano enables ServiceNow customers to map discovered physical and logical network components from Nokia Altiplano into telecom-aligned Configuration Item (CI) classes within the CMDB. This mapping supports accurate classification, clear service modeling, and automated relationship creation across chassis-level and network layers. It leverages the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE) to ensure consistent CI insertion and classification.

    Show full answer Show less

    CI Mapping and Relationship Structure

    The connector organizes Nokia Altiplano components into defined CMDB tables representing both physical and logical layers. Key CI types include:

    • OLT CI (cmdbciopticallineterminal): Represents the optical line terminal device and contains slots and logical network interfaces.
    • ONU/ONT CI (cmdbciopticalnetworkterminal or cmdbciopticalnetworkunit): Represents ONU or ONT devices, containing network interface CIs. The specific class is set by system property snsgcaltiplano.onuciclass.
    • Slot CI (cmdbcicontainerslot): Represents main chassis slots within OLTs, containing interface cards like LT/NT, PSU, and fans.
    • Subslot CI (cmdbcicontainersubslot): Represents subcomponents within interface cards such as SFP cages, containing transceiver cards.
    • Interface Card CI (cmdbciinterfacecard): Represents line cards, transceivers, and control units, which can contain subslots and network interfaces.
    • Network Interface CI (cmdbciniinterface): Represents both physical ports (PON, Ethernet) and logical ports (VLAN), linked hierarchically under interface cards or ONU/ONTs.
    • Logical Connection CI (cmdbcinilogicalpath): Models logical paths such as PON or VLAN connections between OLT and ONU, defined by port termination attributes.
    • IP Address CI (cmdbciipaddress): Captures discovered IP addresses owned by OLT devices.

    These components are related through containment hierarchies (e.g., OLT contains slots, slots contain cards, cards contain subslots) and logical relationships (e.g., logical connections terminated by network interfaces, VLAN paths consuming PON paths).

    Supported Models and Customization

    The connector aligns discovered models with ServiceNow’s network equipment, holder, card, interface, and logical connection model tables. For example:

    • Network equipment: Default OLT model is Nokia Lightspan MF-2; ONU/ONT models combine manufacturer and device type.
    • Holder models: Include Traffic Slot, FAN Slot, Power Slot.
    • Card models: Identified by manufacturer and model number from Altiplano API data.
    • Network interfaces: Physical ports like PON Access Interface and Ethernet ports, logical ports such as VLAN or LAG interfaces.
    • Logical connections: Include PON Access Path and VLAN Path.

    If a discovered model does not match existing CMDB models, a new model is created or the CI defaults to Network Gear. Customers can customize model names and mappings via the Altiplano extension point (snsgcaltiplano.AltiplanoCustomizedModels).

    Model Transformation for Slots and Subslots

    During data ingestion, specific discovered slot and subslot model names are transformed into standard CMDB model identifiers to maintain consistent categorization. For example, "Fan Slot" or "Power Slot" models map to Slot category, while "SFP Subslot" maps to Subslot category. This transformation is embedded in the SGC data source script for Nokia Altiplano.

    Practical Outcomes for ServiceNow Customers

    • Enables comprehensive and normalized CMDB representation of Nokia Altiplano network infrastructure, including physical chassis components and logical network paths.
    • Facilitates end-to-end traceability from OLT devices through slots, cards, subslots, to connected ONU/ONT devices and their logical connections.
    • Supports automation of CI classification and relationship creation, improving CMDB accuracy and reducing manual configuration effort.
    • Provides flexibility to customize models and mappings to align with customer-specific naming conventions and infrastructure nuances.
    • Improves visibility into telecom network resources, supporting better impact analysis, service modeling, and operational decision-making.

    Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.

    To confirm accurate CI classification and insertion, the connector uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE).

    The connector classifies and relates discovered CIs using telecom-specific models based on device type, function, and chassis structure. This helps maintain a clean and normalized CMDB across vendors. Discovered model names from Nokia Altiplano are automatically transformed into ServiceNow standard model identifiers and categories for slot and subslot components.

    CI mapping and relationships

    The following tables describe how Altiplano CIs are represented in the CMDB and how they relate to each other across physical and logical layers.
    Table 1. CMDB CI Mapping and Relationships (Physical Layer)
    CI Type CMDB Table Description and Relationships
    OLT CI cmdb_ci_optical_line_terminal Represents the OLT device. Contains Slot CIs and Logical Network Interface CIs.
    ONU/ONT CI cmdb_ci_optical_network_terminal or cmdb_ci_optical_network_unit Represents ONU or ONT devices. The class is determined by the system property sn_sgc_altiplano.onu_ci_class. Contains Network Interface CIs.
    Slot CI cmdb_ci_container_slot Represents main chassis slots. Contained by OLT CIs. Contains Interface Card CIs (for example, LT/NT, PSU, fan). Model transformations are applied in the data source. For more information, see the above-mentioned Model transformation for slot and subslot CIs table.
    Subslot CI cmdb_ci_container_subslot Represents subcomponents within interface cards (for example, cages for SFPs). Contained by LT/NT cards. Contains transceiver card CIs. For more information, see the above-mentioned Model transformation for slot and subslot CIs table.
    Interface Card CI cmdb_ci_interface_card Represents LT/NT cards, transceivers, and control units. Can contain subslots and network interfaces.
    Network Interface CI cmdb_ci_ni_interface Represents both physical (for example, PON, Ethernet) and logical (for example, VLAN) ports. Contained by interface cards or ONU/ONT CIs. Logical ports are related to physical ports using Members::Member of.
    Logical Connection CI cmdb_ci_ni_logical_path Represents logical paths such as PON or VLAN between OLT and ONU. Defined with Port A and Port Z attributes referencing terminating Network Interface CIs. VLAN paths consume PON paths.
    IP Address CI cmdb_ci_ip_address Represents discovered IP addresses for OLTs. Owned by the corresponding OLT CI.

    Key Relationship Examples

    • Containment relationships
      • OLT CI → contains Slot CI
      • Slot CI → contains Interface Card CI
      • Interface Card CI → contains Subslot CI
      • Subslot CI → contains transceiver Interface Card CI
      • ONU/ONT CI → contains Network Interface CIs
    • Interface relationships:
      • Logical Connections -> terminated by Network Interfaces
      • Network Interfaces -> members of Network Interfaces
    • Logical path relationships:
      • VLAN path (parent) → consumes → PON path (child)
      • Logical paths → terminate at → Network Interface CIs via Port A and Port Z
    • Ownership: IP Address CI → owned by OLT device

    Supported models

    1. Network equipment models (sn_ent_nw_equipment_model)
      • The supported OLT is Nokia Lightspan MF-2, by default the model name is Nokia MF-2
      • ONU/ONT models are manufacturer + ONU/ONT. The system property sn_sgc_altiplano.onu_ci_class defines if ONU or ONT will be used.
      • If the model wasn’t found in the model table, a new model is created in the CI, and the CI will be created as Network gear
    2. Equipment holder models: (sn_ent_nw_holder_model)
      • Slots models: "Traffic Slot", "FAN Slot", "Power Slot"
      • Subslots models: "SFP Subslot"
      • The used model name can be customized by the customer through the Altiplano extension point (sn_sgc_altiplano.AltiplanoCustomizedModels)
      • If the model wasn’t found in the model table, a new model is created in the CI.
    3. Network card models (sn_ent_nw_card_model)
      • Card models are found by the model name, manufacturer, and model number discovered from the Altiplano API
      • If the model wasn’t found in the model table, a new model is created in the CI.
    4. Network Interface Models: (sn_ent_nw_interface_model).
      • Ethernet ports models are found by the "port bandwidth" column in the Network Interface table (sn_ent_nw_interface_model). the port bandwidth of the port CI is located by the discovered port speed in the Bandwidth table (bandwidth)
      • PON physical ports models: PON Access Interface, PON Network Interfaces
      • Logical ports models: ENET Interface, VLAN Interface, LAG Interface, PON Logical Interface
      • If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.
    5. Logical network connection models (sn_ent_logical_nw_connection_model)
      • PON Access Path
      • VLAN Path
      • If the model wasn’t found in the model table, the reference to the Model ID will remain empty.
    Note:
    • If the connector cannot match a discovered equipment to an existing model in the product model table the CI is created as Network Gear by default.
    • If demo data is installed, default models are created for OLT, ONU, ONT, Slots, Subslots, Cards, Network Interfaces, and Logical connections.
    • Equipment and Equipment holder model names can be customized using an extension point

    Model transformation for slot and subslot CIs

    During ingestion, specific discovered model names are mapped to predefined CMDB model identifiers to confirm consistent slot categorization. The transformation logic is embedded in the SGC data source script and applies to the Nokia Altiplano source.

    Slot components such as fan, power, and traffic slots are mapped to the Slot category in the CMDB. Subslot components such as SFP cages or synthetic subslots are mapped to the Subslot category in the CMDB.

    Table 2. Example: Nokia Altiplano slot and sub slot model mappings
    Source Discovered Model Name Target CMDB Model ID Model Category
    Altiplano slot-fan Fan Slot Slot
    Altiplano slot-lt Traffic Slot Slot
    Altiplano cage SFP Subslot Subslot
    Altiplano slot-nt Traffic Slot Slot
    Altiplano synthetic nt-slot SFP Subslot Subslot
    Altiplano slot-psu Power Slot Slot

    CI relationship structure

    The following infographics describes the CI relationships.

    CI relationships structureCI relationship structure

    Example: OLT to ONU Structure

    The following structure enables end-to-end traceability from OLT through its hardware layers to the connected ONU and associated logical paths.
    OLT (cmdb_ci_optical_line_terminal)
    ├── Slot
    │   ├── Interface Card (LT/NT)
    │   │   ├── Subslot
    │   │   │   └── Interface Card (Transceiver)
    │   │   │       └── Network Interface (PON port)
    ├── Logical Connections (PON/VLAN) → Connected to →
    └── ONU/ONT (cmdb_ci_optical_network_terminal)
        └── Network Interface (ONT port)