---
title: Mapping Fortinet CIs and relationships
description: The Service Graph Connector \(SGC\) for Fortinet SD-WAN maps discovered physical and logical network resources to telecom-aligned configuration item \(CI\) classes in the Configuration Management Database \(CMDB\). Service Graph Connectors support consistent service modeling, provide visibility into chassis-level components, and automate the creation of logical and physical relationships.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/telecom-service-ops/telecommunications-service-operations-management/map-fortinet-cis-and-relationships.html
release: australia
product: Telecommunications Service Operations Management
classification: telecommunications-service-operations-management
topic_type: concept
last_updated: "2026-10-09"
reading_time_minutes: 3
breadcrumb: [Configure Fortinet SGC, Configure Telecom Visibility, Configure, Telecommunications Service Operations Management]
---

# Mapping Fortinet CIs and relationships

The Service Graph Connector \(SGC\) for Fortinet SD-WAN maps discovered physical and logical network resources to telecom-aligned configuration item \(CI\) classes in the Configuration Management Database \(CMDB\). Service Graph Connectors support consistent service modeling, provide visibility into chassis-level components, and automate the creation of logical and physical relationships.

The connector uses the Robust Transform Engine \(RTE\) and Identification and Reconciliation Engine \(IRE\) to confirm accurate CI classification and insertion.

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

## CI mapping and relationships

The following table lists the CI object types in the CMDB that can be discovered, along with their representations in the CMDB and how they relate to one another.

<table id="table_m5l_m1b_wfc"><thead><tr><th>

CMDB CI Class

</th><th>

CMDB CI Table

</th><th>

CMDB Hierarchy

</th><th>

Object types/models

</th><th>

Description and Relationships

</th></tr></thead><tbody><tr><td>

Network site

</td><td>

`cmdb_ci_ni_site`

</td><td>

CI → Site →Network Site

</td><td>

Organization network

</td><td>

-   Represents the physical location of IP routers by longitude, latitude, and address.
-   Network site contains IP routers and network interfaces.
-   Network site is a member of a group.

</td></tr><tr><td>

IP router

</td><td>

`cmdb_ci_ip_router`

</td><td>

CI → HW →NG → IP router

</td><td>

SD-WAN Edge/ network or service router is represented by the IP router

</td><td>

-   Represents the FortiGate device.
-   Contains network interface CIs.
-   Contained by network sites and network service instances.
-   IP router is a member of a group.

</td></tr><tr><td>

Slot

</td><td>

`cmdb_ci_container_slot`

</td><td>

HW → Equipment → holder → Slot

</td><td>

Slot

</td><td>

-   Slot is the main device in the network hierarchy.
-   Contains slots for IP routers, IP switches, power supply units, and fans.

</td></tr><tr><td>

Subslot

</td><td>

`cmdb_ci_container_subslot`

</td><td>

HW → Equipment → holder → Slot

</td><td>

Subslot

</td><td>

-   Network card is the main device in the network hierarchy.
-   Contains IP router, IP switch sublots \(small form-factor pluggable or child cards\).

</td></tr><tr><td>

Network Interface CI

</td><td>

`cmdb_ci_ni_interface`

</td><td>

Port → Network Port → Network interface

</td><td>

The list of support port models is defined in the vendor-specific network physical information.

</td><td>

-   IP router, IP switch, or wireless access point is the main device in the network hierarchy.
-   Network card within the IP router or IP switch is the primary component.
-   Represents the physical ports contained within the device \(IP router\).

</td></tr><tr><td>

Network service instance

</td><td>

`cmdb_ci_network_service_instance`

</td><td>

CI → Service instance → Network service instance

</td><td>

Network service instance

</td><td>

-   Network service instance includes IP routers and network interfaces.
-   Network site is a member of a group.

</td></tr><tr><td>

Group

</td><td>

`cmdb_ci_group`

</td><td>

CI → Group

</td><td>

Represents organization

</td><td>

Network sites and network service instance are members.

</td></tr><tr><td>

IP Address CI

</td><td>

`cmdb_ci_ip_address`

</td><td>

CI → IP address

</td><td>

Represents discovered IP addresses for CIs.

</td><td>

Owned by the corresponding CI.

</td></tr></tbody>
</table>## Discovered logical interfaces

In addition to physical ports, the SGC discovers logical interfaces, such as tunnel and VPN interfaces \(for example, `Hub1-inetVPN`, `inetVPN`, and `mplsVPN`\), from the Fortinet inventory. Each logical interface is created as a network interface CI \(`cmdb_ci_ni_interface`\) and related to its parent device \(IP router\) CI.

A CMDB CI exists for each logical interface. Metrics that report against a logical interface name are mapped to the corresponding logical interface CI rather than to the parent device CI. This mapping enables interface-level metric correlation and reporting for tunnel and VPN interfaces.

## Firmware version calculation

When the SGC discovers an IP router, it sets the firmware version on the `cmdb_ci_ip_router` CI by joining the device `os_ver`, `mr`, and `patch` fields from the Fortinet inventory with periods. For example, a device with `os_ver=7`, `mr=4`, and `patch=11` resolves to `7.4.11`. This matches the value shown in the Fortinet GUI. If any of these fields is missing, the firmware version is left empty. The firmware value is also left empty if the major version is not a whole number.

Override the default with the `sn_sgc_fortinet.FortinetCustomizedFirmwareVersion` extension point to calculate the firmware version differently. Create an implementation that defines a formatFirmwareVersion\(\) handler, where **device** is the Fortinet device object returned by the API. Return your own version string from the handler. A custom firmware handler's return value is used exactly as returned, including an empty result; the built-in calculation is used only when no custom handler is active.