Infoblox’s global team of threat hunters uncovers a DNS operation with the ability to bypass traditional security measures and control the Great Firewall of China. Read about “Muddling Meerkat” and the many other threat actors discovered by Infoblox Threat Intel here.

Trending KB Articles


#5645: NetMRI Device Support

Device Support is similar to Device Baselining or Device Verification.  Infoblox makes every effort to support as many devices as possible.



An updated Device Support List is regularly published.  For an updated list, select the following link and goto Tech Docs > Network Infrastructure Device Support List (NetMRI and Network Insight) > Device Support List

Infoblox recommends to always check the newest list to verify if device in question is supported in newer versions of NetMRI.

NetMRI identifies devices using Vendor Model & Software version.

Infoblox uses industry standard probing methods to identify devices.  For the various processes used to discover and identify devices, please see KB #4380

NetMRI will make every effort to discover each device it encounters, even if it is NOT yet fully supported and/or verified.

If a device is discovered, that is not fully supported and/or verified by Infoblox "Device Support Process", it is not unusual that this device could be discovered without issues.  It is also possible that a device that is not fully supported and/or verified, could experience incomplete discovery, or problems parsing the data that is discovered.  For these cases, be sure to verify that this device is not on Infoblox's most current Device Support List (as referenced above).

Once it is verified that the device is NOT yet supported and/or verified, open a case with support and request an RFE for the specific device support viability.

Please note that once RFE is created, our Product Management team will review and update within 2 weeks whether submitted device support RFE is accepted or not. As soon as an update is received from Product Management, Support will notify you status of RFE [ETA within 2 weeks].

The following data is needed for Infoblox to further determine what customizations need to occur to properly collect data from this device. The data collected will help Infoblox to simulate the behavior. 

The required data is:

  • Completed Device Support Request

  • Discovery Diag

  • MIb Files

  • Vendor Documentation

NetMRI has an automated device support request collection tool.

To execute the process of device support collection, do the following:

  1. Go to Tools icon -> Device -> Device Support Request.
  2. Click New at the top of the table. Click Next to proceed to the first data input step.
  3. Enter the IP address in the Device IP field, and press Enter on your keyboard. This value is required to initiate the gathering of device information.

After entering the IP address, the Description fields may update with previously discovered information from the device, including the Vendor Name, Model, OS Version, the Device Type and the configured Capabilities for the device.
If no data exists in Network Automation for the device, you will need to enter the values for the Description fields. Because you are building a Device Support Request, it is likely that you will need to do so.
Also make sure to choose the correct Capabilities for the device.
A device may support more than one Capability, or a given device may be known as a specific Device Type but be configured for a different Capability. Press the CTRL key and click to select multiple Capabilities for the given device.

  1. Define the Access values for the device, which determine the protocols to be used for CLI and SNMP access:

  2. Preferred SNMP: Choose the recommended SNMP protocol for device access: SNMPv1, SNMPv2 or SNMPv3. Based on the chosen protocol, enter the following:
    − Community String: Enter the read community string for the SNMPv1 or SNMPv2 device;
    − (If you select SNMPv3 only): Enter the admin user account name, and the authentication and privacy password/protocol tuples for the SNMPv3-compliant device. Note that some devices may use only the authentication or privacy settings, but not both.

  3. Preferred CLI: Choose SSH, Telnet, or Other. After you enter the login information and click Next to go to the next step, Network Automation tests the specified connection to the device to ensure reachability. Also note that if CLI is a data collection method, you may need to enter a sequence of command-line functions from the operating system of the device.
    − SSH: Add the admin User Name and Password.
    − Telnet: Add the admin User Name and Password.
    − Other: Choose this value if you expect to use SNMP as the primary means of device access. CLI access through SSH or Telnet will not be attempted if you choose this option.
    If you do not select Other, you enter the device's CLI admin credentials in the terminal screen.

  4. Methods to Support Infoblox Testing: Infoblox Support requires access to your device, using your chosen method, to verify the new device support information. Choose from the following:
    − VPN to Device.
    − Access Through Network Automation.
    − Loan of Device.
    − Other (requires a directive by the user to make arrangements for the testing).

  5. Click Next. If you are using SNMP, you will receive a message as follows:

SNMP data for the device will be collected in background and this process may take time.
This message also indicates establishment of successful SNMP communication. CLI reachability is not tested. Click OK to proceed.


     9. In this step, CLI Capture, the page divides into two panes: a scrolling list of configuration tasks on the left that you perform for the device in question; and a terminal window on the right pane showing the SSH or Telnet interactive session to the device.


− The list in the left pane provides a list of key tasks to perform a full configuration capture of important command-line processes in the device. This list of tasks changes according to the device type, and to the capabilities chosen by the user.

The first task, Configure Device to send Syslogs to Network Automation, is automatically selected. For many devices, some descriptions may not be relevant.
Most, such as Display Device's IPv4 ARP information or Display Device's IPv4 Route information, are relatively straightforward. All commands are mandatory except for the ones that you explicitly skip by clicking Not Applicable and choosing from the following options:

− Device does not support this function;
− Current configuration does not support this function;
− I'm not permitted to do this function;
− Other.

(Network Automation collects the responses to each command as you enter them.)

− Log in to the device using the terminal window on the right pane. Enter each configuration command in the sequence listed on the left. After each command and its displayed results (assuming the results are satisfactory), click the Done button. A green checkmark appears by the selected command and the Wizard selects the next list item.
− If a command is not relevant for the device type, or is not available, click Not Applicable to go to the next one, and enter that command in turn. Continue until you have finished entering all the commands that you will send in the Device Support Request package.
You can return to any listed command function to correct an error.


     10. Click Next. Doing so compiles the command sequences into an encrypted data file. (This does not apply if you are using only SNMP.) In Step 4 of the tool, the Document Attachments phase, you upload any documents that may be available for the device in question. Clicking the Add sign allows loading for the following:

− Device Admin Guide: Vendor documentation for the network device.
− Vendor MIBs: typically a text-format file that contains the complete listings of the vendor-defined SNMP Object IDs and other information required to interact with the device using an SNMP-compliant management system (such as, of course, Infoblox Network Automation).
− Device Change Syslog: Upload a text or word processing file listing a series of Syslog messages that appear when interacting with the device.
− Screenshot: Any screen capture graphics that may prove useful in support development.
− SNMP Logs: A text or word processing document listing the series of SNMP logs that appear when the device is probed by Network Automation through the SNMP protocol.


      11. Click Next. The tool offers a chance to remove any sensitive account data (accounts and passwords, community strings) from the sent Support Request. Any credentials that you previously provided for the initial testing and device interaction can be removed in this step.

− Click Show Strings to verify the contents of the values you enter.
− Click Add to add and enter more strings to the list that you want excluded from the Device Support Request.


     12. Click Next. The tool now provides a list of the items provided for the Device Support Request: Device Information, Document Attachments, CLI Command Capture, Change Detection Syslog, Discovery Test and SNMP Data Capture. Some items may show a status of Complete or Missing. Click on the Document Attachments or CLI Command Capture links to return to their respective tool pages.


If necessary, click the links to perform any of the following:

− Rerun SNMP Walk: Execute another SNMP probe to the device using the credentials you supplied, to perform data collection.
− Rerun Discovery: Execute the Network Automation discovery process on the device to perform data collection.
− Refresh Status: Refresh the contents of the Step 6 tool page to verify if a particular task completes.


     13. Click Next. The tool will request the means of Device Support request delivery to Infoblox:


− Secure Transfer to Infoblox: Chooses automatic secure file transfer to Infoblox Support. The Infoblox Support FTP server must be reachable by Network Automation. You can test connectivity and settings in the Network Automation command line using the steps in External server import/export using FTP.
− Email: Chooses automatic email attachment to Infoblox Support, with the option to enter other email addresses.
− Download to Local Machine: Save locally to allow the user to manually send the package file.

     14. Click Next and click Finish. After a moment, the Device Support Request table reappears, displaying the status Finalizing Request. The Request entry will eventually refresh to show Complete status. If you choose Automatic Secure Transfer to Infoblox or Email, the bundle request file is sent to Infoblox Support. Otherwise, the Wizard saves the bundle request file to your hard drive.

You can click the Action icon for any Request entry, and choose Edit or Delete.

Showing results for 
Search instead for 
Did you mean: