NCM Host Configuration captures aren't recognizing config changes. As a result the Capture Time isn't updating properly and remains in the past.
Example is this image where the Capture Time should be current for 2024 but remains two years in the past.
NCM debug logging shows the info is considered "uninteresting". We see a message like this when the debug is enabled and a capture is run where there are differences.
Apr 16, 2024 19:17:09.131 (grpc-default-executor-890) - <deviceIP>: the diff was uninteresting:
The Mask Configurations defined were not working as expected.
Engineering provided the following two lines. Using these for the Mask Configuration allows the configuration differences to be found. Once found this results in the Capture Time updates, resolving the problem.
.*password\s[57]
(\s+[A-F,0=9]{8})+(\s+[A-F,0-9]{1,8})
Update the Mask Configuration to use those lines.
See the Configure Device Family Masks documentation topic for device family level masks.
See the Configure a Mask on a Single Device documentation topic for device specific masks.
If the recommended Mask Configuration doesn't resolve the issue, please open a case with the support team. Ideally include NCM debug logging while reproducing a capture and reference this KB article.
See Article Title: How to debug NCM problems in Spectrum for steps to enable debug for NCM