...

• Rogue DHCP remediation begins with preventing established, legitimate DHCP servers, such as NIOS appliances supporting the DHCP service, from being identified as a rogue server. You compile all legitimate DHCP servers on the network into the ACM Allowed DHCP Servers list (Config Management –>  > Job Management–>  > Lists);
• Because the Rogue DHCP jobs are issue-driven, a suspected rogue device may first need to be detected by NetMRI. Ensure fingerprinting is enabled in the NetMRI system (Settings > Setup > Network Polling > Fingerprinting checkbox);
• Also ensure that the required user accounts get the appropriate notifications when Rogue DHCP events occur. Consult the topic Defining a Job Notification for specific information.
• NetMRI also scans the standard DHCP TCP and UDP ports (check settings in (Settings > Setup > Network Polling and enter "bootp" as the search string in the Port Scan List).
• The NIOS administrator account username and password should be added to Advanced Settings (Settings icon> General Settings > Advanced Settings > page to the NIOS Administrator category).

To enable the NetMRI-to-NIOS communication, you also define the NIOS administrator User ID and password that NetMRI will use to check the configuration in NIOS. If this is not yet in place, see Creating a Single-Sign-On Admin Account.

Rogue DHCP Triggering Events

...