Configuring LLDP link discovery

Description

The nim, or Network Infrastructure Management section specifies the method by which LLDP link discovery is accomplished.

In the MDM framework, NSP supports the LLDP-based discovery of physical links in the network topology. This discovery mechanism uses the MDM to read the LLDP neighbor information. NSP then adds the discovered links to the common store so that all applicable functions can access the link information. This process is controlled by the NSP network infrastructure management component by default, however, Original Service Fulfillment can be made to assume control by changing the value of the linkDiscovery parameter from “nim” to “sdn”.

Note: This function is supported only for the physical links with the Nearest Bridge transmission scope.

## nim                    - Network Infrastructure Management

     #    lldp                 - LLDP configuration

     #      linkDiscovery      - Link discovery type.  Valid values are:

     #                             "sdn" - indicates link discovery is based on LLDP AMI v1

     #                             "nim" - indicates link discovery is based on LLDP AMI v2 and onwards (default)

If upgrading from an NSP release earlier than 22.6, the linkDiscovery parameter is set to “sdn” by default. In order to change the value to “nim”, the following commands must be executed only when the lldpv2 adaptors are available or deployed for all managed devices:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config --deploy

./nspdeployerctl install --config --deploy

kubectl delete pods `kubectl get pods -A | grep lldp-app | awk '{ print $2 }'` -n $(kubectl get pods -A | awk '/lldp-app/ {print$1;exit}')`