NNM Support Tip: about 'Dynamic Sync" and "Full Topology Synchronization"

Issue:

NNM and OBM integration

Customers add many new nodes on the NNM side and found that the synchronization could not go to OBM

Use commands to check the status of synchronization

“%nnminstalldir%support\nnmtwiddle.ovpl invoke com.hp.ov.nnm.bsm.im:mbean=NnmBsmModule reportStatus

E.g

   Total nodes being synchronized: 12061

   Nodes left to synchronize: 10351

Default，"Topology Synchronization Interval (hrs):" is 24 hrs.

whenever "Full Topology Synchronization" task is in-progress, pushing of a new node（Dynamic Sync） may get delayed.

Note :

1. What is the logic of synchronizing the interval size setting?

It depends on number of other topology objects being pushed!

Like Interfaces, Subnets, Addresses, Cards, Ports, Connections, VLANs etc.

For ex: Some of the devices may contains few 100s of interfaces, but some may contain 1000s of interfaces.

Sometimes there could be 1000s to lakhs of VLANs.

Based on our experience & interactions

For 10k - 15k nodes, the recommended "Topology Synchronization Interval (hrs):" is 168 hrs.

2. 'Dynamic Sync" and "Full Topology Synchronization"

In general, the 'Dynamic Sync" task pushes the new node to OBM quickly!

But, whenever "Full Topology Synchronization" task is in-progress, pushing of a new node may get delayed.

So, if delayed, try to ask customer to increase "Topology Synchronization Interval (hrs)

which helps "Dynamic Task" to push newly discovered topology objects quickly.

3. Can We pause "Full Topology Synchronization" to prioritize 'Dynamic Sync'?

This is not facilitated to avoid conflict in updating the same object by both full sync and dynamic sync.

So, we can pause "Full Topology Synchronization" to prioritize 'Dynamic Sync'

Hiro

Customer Support Engineer, APJ NNMi