Technical Note: Profiled Devices Show Incorrect Rule Name in Multi-pod Environment with NCM
Description
Scope
Version: Network Sentry 8.0.1 and 7.3.2 and above
Solution
Profiled Devices Show Incorrect Rule Name in Multi-pod Environment with NCM
Scope
Version: Network Sentry 8.0.1 and 7.3.2 and above
Solution
Version: Network Sentry 8.0.1 and 7.3.2 and above.
Issue: Profiled devices show an incorrect Rule Name in a multi-pod environment that is managed by a Network Sentry Control Manager (NCM).
In Network Sentry versions 8.0.0, 7.3.1 and lower, the Rule Name's DBID for Profiled Device was copied across the NCM to other Network Sentry pods. This created the mismatch or blank Rule Names. This is no longer the case is later releases, but the data corruption can still exist from before.
Solution: To fix existing data corruption, contact Bradford Support and reference case 50636 for a FixDpcHosts script that should rematch some of the Profiled Devices to their proper rule.
