DX NetOps

 View Only
  • 1.  Change detection completion status

    Posted Feb 02, 2023 10:02 AM
    All,

     We have enabled change detection for metric families for every 24hrs once ,How can i confirm in PM whether it has validated for all discovered devices/interfaces/other components .


  • 2.  RE: Change detection completion status

    Broadcom Employee
    Posted Feb 02, 2023 10:17 AM
    There should be an event on each device for each MF run through change detection (CD), describing is there was any changes or not.

    Note: CD randomizes all the devices across the 24 hrs, so we are not doing all the work during a small period.  CD starts 24 hrs after it's configured, or DA restarts.

    Note: You will only see MF/VC Last discovered time change when a new VC is determined.  You will only see Last discovered time change on a component if it was discovered new or updated during CD.


  • 3.  RE: Change detection completion status

    Posted Feb 02, 2023 10:26 AM
    Yes i agree with you ,but i have 10 K devices and CD is set to 24hrs .. I hope only few devices/interfaces are picked in those cycle and some are skipped . My plan to extend the CD 3 days once so it can cover all devices. There is any limitations on number of devices for run?


  • 4.  RE: Change detection completion status

    Broadcom Employee
    Posted Feb 02, 2023 04:18 PM
    CD is default to 24 Hours and I don't think it can be changed.


  • 5.  RE: Change detection completion status

    Broadcom Employee
    Posted Feb 02, 2023 04:24 PM

    CD schedules for locked default Monitoring Profiles are not configurable.

    CD schedules for custom user created Monitoring Profiles are configurable.

    Extending CD schedules to a 3 day time frame wouldn't necessarily be recommended. It would likely result in a longer delay than desired for device update changes being found and made in NetOps.

    I wonder why the concern. Are there problems you suspect are related to this area?




  • 6.  RE: Change detection completion status

    Posted Feb 03, 2023 07:41 AM
    Yes @Michael Poller there was an alias name update in Interface and it didn't picked for 3 days ,once after manual update it got updated . There are any logs captured for CD somewhere in DA?​


  • 7.  RE: Change detection completion status

    Broadcom Employee
    Posted Feb 03, 2023 09:22 AM

    Changing CD to address that type of problem isn't what we'd recommend.

    I believe Jeff answered that question in his post above re:

    "There should be an event on each device for each MF run through change detection (CD), describing is there was any changes or not."

    Do you see Events for that device around the time of the problem that indicates CD failing or having issues for the Interface MF CD cycles?




  • 8.  RE: Change detection completion status

    Posted Feb 03, 2023 09:41 AM
    Michael - I dint see those events on specific device when the change is made and even after 2 days , events got updated after a manual MF update only.


  • 9.  RE: Change detection completion status

    Broadcom Employee
    Posted Feb 03, 2023 09:29 AM
    So CD can be disabled if it tries to create not present items incorrectly.  And the only way to re-enable CD is to run update MF.

    You should check the DA karaf.log* files and see if you can find a message like:
    Change detection for MF <mf internal name> on device <itemID> is disabled.

    So get the itemid of the device you ran update MF on, and search karaf.log* files for that itemid and see if returns a message like above.