How the DX NetOps Performance Management integration with a DX NetOps Spectrum Data Source functions for device synchronization and discovery functionality.
This Knowledge Base Article shall discuss the functionality around the DX NetOps Performance Manager and DX NetOps Spectrum integration device synchronization and discovery functionality.
All supported DX NetOps Performance Management and DX NetOps Spectrum releases
Spectrum to CAPC Integration Details
Discovery, Spectrum Global Collection and Data Aggregator (DA) Discovery Profile details
It is important to start with the fact that Spectrum does not integrate with DA directly.
We often think of it this way, because we talk about using Spectrum to seed the DA with devices and their elements, but there are some subtleties to what's going on under the hood.
There may be a misconception among some users that the contents of the special CAPC IP Domain based Global Collection models in Spectrum will result in an IP list match between the "<DomainName>" Discovery Profile in CAPC. There is not always a one to one relationship between the IP addresses of device models that are members of those special Global Collections (GC) and the "<DomainName>" Discovery Profile in CAPC DA views.
When a Spectrum OneClick server is added as a Data Source (DS) in CAPC, CAPC pushes IP Domains to Spectrum OneClick. The "integration" code in Spectrum OneClick implements this push by the creation of CAPC IP Domain based models in Spectrum. Although the CAPC IP Domain model type is derived from a Global Collection it is important to understand that it is not a Global Collection as might be normally known to Spectrum users. There are special behaviors that go along with this model type that are not available to normally created Global Collections in Spectrum.
At this point in Spectrum you should see a CAPC IP Domain based model for each IP Domain in CAPC. They will be found in the Spectrum OneClick client console under the Global Collection listings at the global level of that view, independent of other landscapes configured in Spectrum. The user can then configure search criteria or manually add devices to these CAPC IP Domain based Global Collections, the same as can be done for other standard Global Collections.
Once devices are added to those Global Collections as members, on the subsequent synchronization cycle pull phase from the Spectrum Data Source in CAPC, those devices are synchronized to CAPC. This is important for a couple of reasons:
That is the "nuts and bolts" of how Spectrum participates in Inventory synchronization with CAPC.
Independent of the above information, the DA is a special Data Source unlike the others created for integration with CAPC, such as the Spectrum Data Source.. It can be configured to discover devices from other Data Sources. Notice the terminology "other Data Sources". It is important to understand that function is not specifically limited to the Spectrum Data Source. When this switch is enabled for the DA., when the DAs next synchronization cycle arrives, any devices in CAPC which the DA does not know about are pushed to the DA.
What the DA does with them is add the IP to a system configured Discovery Profile which is maintained for each IP Domain. A key point:
Some common questions around this product functionality we are asked are: