How is inventory synchronized?

Synchronizing inventory

NSP requires inventory information for certain features. On startup, an initial synchronization is triggered that pages through the RESTCONF inventory find API and synchronizes inventory information. From there, ongoing synchronization consumes kafka messages from the nsp-yang-model.change-notif kafka topic. This handles the management, unmanagement, and modification of new NEs after NSP startup.

Note: The openconfig logical inventory adaptors - such as sros-oc-logical-inventory - must be installed in MDM to enable it to synchronize openconfig interface information from the managed NE.

Xpaths

For inventory synchronization to work, the following xpaths must be populated in NSP by either MDM or NFM-P for each node being managed. You can confirm that this data is being populated using the NSP RESTCONF inventory find API. For more information, see the Network Developer Portal.

Xpath: /nsp-equipment:network/network-element

Xpath: openconfig-interfaces:interfaces/interface/subinterfaces/subinterface

The following is an example of a POST call using the NSP RESTCONF inventory find API:

POST /restconf/operations/nsp-inventory:find

{

"input": {

"xpath-filter": "/nsp-equipment:network/network-element",

"fields": "ne-id;ne-name;type;version;mac-address;ip-address;admin-state;oper-state",

"limit": 10

}

Manual inventory synchronization

If synchronization is lost on either the NSP side or on the MDM side, the below APIs may be used to return to a synchronized state.

If NSP is out of sync, use the following API to trigger an initial synchronization again:

GET /sdn/api/v4/system/resync-nms

Note: This also triggers re-synchronization for the Original Service Fulfillment application. If your network is large, or contains many services, this could potentially be a time-consuming operation.

If MDM is out of sync, use the following API to force MDM to re-synchronize logical inventory data from the node:

POST /restconf/operations/nsp-admin-resync:trigger-resync

{

"nsp-admin-resync:input": {

"plugin-id": "mdm",

"network-element": [

{

"ne-id": "11.50.150.51",

"sbi-classes": [

{ "class-id": "openconfig-interfaces:/interfaces/interface/subinterfaces/subinterface/openconfig-if-ip:ipv4/addresses/address"

}

]

}

]

}

Lastly, you can use the following API to set up a polling policy for a specific path (also known as re-synchronization policy):

PATCH /restconf/data/nsp-admin-resync:resync-policies/mdm/resync-policy=default%20policy/node=SR-7750/version=22.7.R1/entity=openconfig-interfaces%3A%2Finterfaces%2Finterface%2Fsubinterfaces%2Fsubinterface%2Fopenconfig-if-ip:ipv4%2Faddresses%2Faddress

{

"entity": [

{

"entity-type": "openconfig-interfaces:/interfaces/interface/subinterfaces/subinterface/openconfig-if-ip:ipv4/addresses/address",

"period": 1,

"admin-state": "enabled",

"description": "Network Interface Polling modify"

}

]

}

Use subject to agreed restrictions on disclosure and use.