DX NetOps

 View Only
  • 1.  PM synchronization with Spectrum

    Broadcom Employee
    Posted Nov 13, 2019 07:53 AM
    HI
    We are seeing devices (including alarms and events) in CA PC which are NOT in the IP domain being synchronized from Spectrum.
    • Spectrum 10.3.2
    • PM 3.7.4
    Any suggestions what causing this behavior.

    Regards
    Klaus


  • 2.  RE: PM synchronization with Spectrum

    Posted Nov 13, 2019 08:07 AM
    Some other data sources registered with PC?

    ------------------------------
    Senior Consultant
    SolvIT Networks
    ------------------------------



  • 3.  RE: PM synchronization with Spectrum

    Broadcom Employee
    Posted Nov 13, 2019 10:40 AM
    HI

    Only 2 data sources
    CA PM & NFA

    Alarms from pingable devices comes through which are not in the IP Domain.

    Regards
    Klaus


  • 4.  RE: PM synchronization with Spectrum

    Posted Nov 13, 2019 10:55 AM
    How do you know the alerts are generated on the SPECTRUM side?

    In 3.7 it was changed the way that elements from different datasources are discovered by the DA. There's a tick on each datasource that tells the DA to discover/manage inventory provided by that specific data source.

    For Spectrum, there are specific settings.

    ------------------------------
    Senior Consultant
    SolvIT Networks
    ------------------------------



  • 5.  RE: PM synchronization with Spectrum

    Broadcom Employee
    Posted Nov 13, 2019 02:28 PM
    Hi

    Spectrum are the only data source that generate pingable devices alerts and they all appear in CA PM which should not be.
    These pingable devices are NOT in the IP Domain global collection.

    Regards
    Klaus


  • 6.  RE: PM synchronization with Spectrum
    Best Answer

    Posted Nov 14, 2019 07:46 AM
    Hi 
    The devices most likely are synced from the NFA data source. They probably show as pingable because the PM Data Collectors are not in the device's snmp acl. A 3.6.1 feature controls whether a source's inventory is added to the DA when configuring a data source:
    (3.6.1 and higher only) Select Contribute inventory to the Data Aggregator. If selected, all new data source inventory contributes to the Data Aggregator. If unselected, the existing inventory remains the same, and no new data source inventory contributes to the Data Aggregator."

    Another common issue with NFA sourced devices is mismatched device IP addresses. NFA devices are usually identified by the loopback IP address (source of netflow). The devices will not reconcile in PM if the device is discovered in PM or Spectrum by a different interface.