Nokia Altiplano

This guide covers the two data paths Layer 9 uses with Nokia Altiplano:

• Inventory — OLT and ONT inventory, pulled from the Altiplano NBI (RESTCONF + IndexSearch)
• Streaming — live ONT optics and alarms, consumed from the Altiplano Kafka broker

Prerequisites

• Administrator access to Altiplano, including the ability to manage API users and roles
• Your Altiplano release/service prefix (the Network Virtualizer prefix, e.g. nokia-altiplano-av)

Step 1: Create an API user for inventory

Create a dedicated API user (rather than reusing an operator login) so audit logs stay clear about which actions came from the integration. The user authenticates with HTTP Basic against the Altiplano NBI.

Grant the user a role that permits device-management and alarm read operations. The default OSS_IBN_NBI_ONLY role is not sufficient — under it the device inventory and alarm APIs return 403 access-denied. The role must allow reading device inventory, hardware/component details, and active alarms.

Step 2: Enable IndexSearch access

Layer 9 reads ONT and OLT inventory from Altiplano’s IndexSearch interface using the same NBI credentials. Confirm IndexSearch is exposed and reachable on the controller, and note its ingress path — this is altiplano-indexsearch or altiplano-elasticsearch depending on your install.

Step 3: Issue a Kafka client certificate

The Altiplano Kafka broker requires mutual TLS and will reject any connection that does not present a trusted client certificate. Provide:

• A client certificate and private key signed by the Altiplano issuerCA
• The CA chain (issuerCA and rootCA)

Also confirm Altiplano is configured to publish external change events and PM reports to Kafka. The telemetry topics Layer 9 consumes are release-prefixed, for example:

• ALTIPLANO_PM_REPORT_PON_ONT_OPTICS — ONT optical metrics
• <prefix>_ALARM — alarms
• <prefix>_STATE_CHANGE / <prefix>_DEVICE_MANAGEMENT — device state

Step 4: Share details with Layer 9

Share the following with the Layer 9 team:

• The Altiplano base URL and release/service prefix
• The API username and password from Step 1
• The IndexSearch ingress path from Step 2
• The Kafka broker address and port, and the client certificate, key, and CA chain from Step 3