...

All installed MIBs are listed in the MIB Manager page. To import a new MIB file, do the following:

1. Go to the Settings icon –> > Setup –> > MIB Management.
2. At the top of the table, click Import to open the Import file requester.
3. Click Browse and navigate to the location where you have saved the MIB file.

4. Select the MIB file and click Import. The file is added to the MIB table.

   Note
   title Note

...

1. System MIBs cannot be exported by the MIB manager. MIBs that have previously been installed by the operator may be exported.

   
   

Reloading MIBs into the NetMRI system can take several minutes. If a MIB or DSB is imported or removed, the procedure requires several minutes to complete.

Anchor
Working With Device Support Bundles Working With Device Support Bundles

Anchor
bookmark834 bookmark834

Working With Device Support Bundles

A Device Support Bundle (DSB) is a small collection of files designed specifically to enable installed to discover, communicate with and manage new types and models of network devices that may not be included in the substantial universe of device support already offered by NetMRI. Features in the appliance enable editing, validation, and testing against managed devices for Device Support Bundles that you create. (Make sure to refer to the Infoblox Device Support Guide document under Additional Documentation for more information on DSB creation.)

Note
title Note

...

The text-based DSB file containing the XML code for the bundle must be in native XML format. Use a text editor that directly supports saving in the .XML file format. A plain-text file. with the file extension .TXT, that contains XML code will not be visible to the import feature.

To begin working with installed's Device Support Bundles feature set, go to the Settings icon –> > Setup –> > Device Support Bundles.

Note
title Note

...

Support bundle operations require the SysAdmin role.

The Device Support Bundles page appears, displaying a table of information for any existing device support bundles. The columns in this table indicate that a given DSB explicitly supports the given data elements (not all fields will necessarily be defined):

...

To create a new Device Support Bundle, do the following:

1. Go to Settings icon –> > Setup –>  > Device Support Bundle.
2. At the top of the table, click New to create a new Device Support Bundle from the UI. A prompt appears, requesting entry of a name for the new bundle.
3. Enter the name and click OK or press Enter. The DSB Editor window appears. A new DSB is created out of a set of built-in templates. The DSB bundle XML file, in which you write your support file for the bundle, contains a series of XML tags that are documented in each of the development steps. Typically, a device support bundle also will include vendor MIB files, and CCS or Perl scripts to handle configuration file collection. Vendor MIB files may also be imported separately.
   See the supplementary document Infoblox Device Support Guide in Additional Documentation in the online Help for much more detail on XML DSB tags and writing DSB files, and Job Scripting for much more detail on Perl and CCS scripting.

To import a previously created Device Support Bundle, do the following:

1. Go to Settings icon –> > Setup –>  > Device Support Bundle.
2. Click Import to open the Import file requester.
3. Click Browse and navigate to the location where you have saved the Zip file with the XML file and the directory containing the needed MIB files.
4. Select the Zip file and click Import.
5. An Import Status dialog box showing the import file output appears. The import may take several minutes to complete, and will display the results of each import function. Click Close when the process completes.

...

Anchor
Validating and Testing Imported Device S Validating and Testing Imported Device S

Anchor
bookmark838 bookmark838

Validating and Testing Imported Device Support Bundles

Note
title Note

...

If a device of the desired type is not currently discovered by NetMRI, the Test option in Device Support Bundles is disabled.

Users You can test new or currently installed Device Support Bundles. Validation functions, which test the bundled files for syntax errors and for well-formed XML syntax, include the following:

...

Examples in this section assume a bundle is already installed. To validate a Device Support Bundle, do the following:

1. Go to Settings icon –> > Setup –> > Device Support Bundles.
2. In the Actions column, click the Actions icon for the bundle you want to test.
3. From the drop-down menu, choose Validate.
   Two validation tests are run: one against the XML, and one against the Perl or CCS script.
4. Click Close when finished.

...

A wide variety of devices exist in enterprise networks. NetMRI offers the ability to create a complete and detailed Device Support Request package for network devices, or device OS versions, that are not directly supported by NetMRI.

Note
title Note

...

You may use a standalone NetMRI appliance or an Operations Center (OC) system to perform Device Support Request data collection. If you are using an OC, discovery and data collection is automatically delegated to the correct appliance.

You may have devices in your managed network that are part of NetMRI's list of officially supported devices. NetMRI provides a simplified tool for creating a comprehensive Device Support Request for dispatching to Infoblox to develop a full Device Support Bundle for unsupported devices.

...

This feature, called CLI Capture, leverages NetMRI's CLI command capturing, configuration collection, and built-in SSH client features to allow a detailed breakdown of the most obscure and unusual devices and their command systems. All you need is a successful SSH or Telnet connection, and the admin login tuples (including Enable passwords) required to establish a working command-line session. Knowledge of the command line for the device in question is also necessary.
If a device is reachable, the device support request process uses both SNMP and CLI data collection features in tandem.

Note
title Note

...

In some cases, completing a Device Support Request will require the availability of vendor SNMP MIBs. If NetMRI cannot access the device by Ping (thereby knowing the IP address) or by SNMP, automated device data collection is not possible; you may still manually enter device support information.

The information comprising an automated support bundle includes the following:

...

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 NetMRI 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.

   Note
   title Note

...

1. 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.

   
   

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

...

• • • Preferred Contact: Specify the preferred method of contact. Select E-mail to contact customer through email message or select Phone to contact customer by phone.
    • Customer Name: Enter the customer name.
    • Contact Name: Enter the name of the contact person.
    • Email Address: Enter the email address. This field is displayed if you select E-mail as preferred method of contact. You can enter up to 50 characters.

    • Phone Number: Enter the phone number. This field is displayed if you select Phone as preferred method of contact. You can enter up to 50 characters.

      Note
      title Note

...

• • • The customer name will be included in the file name that is downloaded to the local machine or when it is uploaded to external servers through FTP and other methods.

      
      

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.

6. In Step 3 of the tool, 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.

...

Anchor
Defining and Using Custom Fields Defining and Using Custom Fields

Anchor
bookmark840 bookmark840

Anchor
bookmark841 bookmark841

Defining and Using Custom Fields

The Custom Fields page (Settings icon –> > General Settings –> > Custom Fields) enables you to define custom data fields for uncovering and recording any information about network devices, changes and jobs. For devices, custom fields are useful for recording important c

Anchor
bookmark842 bookmark842

ontextual data such as asset tag numbers and physical location — information that NetMRI does not gather on its own.
Administrators can add extensible data in the following contexts, with examples suggested for each:

• Interfaces — Creates : Creates Interface Custom Fields. Update and augment information on interfaces with usage codes, or allowing usage designation of interfaces for Tier 1 tracking;.
• Components — Creates Components Custom Fields. Update information for components such as line cards with serial numbers that are collected by custom CLI interrogation or asset tag numbers;.
• Jobs — Creates Job Custom Fields. Update job definitions with custom information, including trouble ticket values or simple 'notes';
• Devices — Creates Device Custom Fields. Custom data can apply to almost any phenomenon involving devices, such as provisional IPv6 values for devices whose kernels do not yet support IPv6; custom output messages, different identification fields, and other information. You may use device custom fields in device group definitions to help match discovered and managed devices against logically named device groups. For information on how do so, see Understanding Device Group Membership Criteria and its subsection Device Group Criteria and Device Custom Fields;
• Changes — Creates Change Custom Fields. Add new fields to help keep track of changes in the network.

The entire Custom Fields feature set enables association of NetMRI to other operational systems and operational data, for better integration into organizational processes for asset management and other purposes.

Note

...

For jobs and changes, custom fields can be used to record information such as ticket numbers.

Custom fields you define in this page can be populated with data in the following locations:

• For devices: Device Viewer –> > Device/Network Explorer section –>> Custom Data.
  • As noted, you can edit the Device Group Criteria field for any device group to enable the use of custom fields as matching criteria in devices;
• For jobs: In the Job Wizard available via the New button; and the Edit button in Configuration Management –> > Job Management –> > Scheduled Jobs.
• For changes: In Network Analysis –> > Changes.
• For Interfaces: Interface Viewer –>  > Interface –> >Custom Data.
• For Components: Device Viewer –>Viewer > Device/Network Explorer –> > Component Inventory.

To create a custom data field, do the following:

1. In the upper left corner of the Settings icon –> > General Settings –>  > Custom Fields page, open the Type menu and select a custom data type (Changes, Devices, Interfaces, Jobs or Components). For device group matching, for example, choose Devices.
2. Click New. The Add custom field value dialog appears.
3. Enter a new Name for the field.Open the Type list and select a field type (Date, Number or String) appropriate for the kind of data to be recorded in the field.
4. To create more than one field, click Save. The new field is added to the table in the background. You can enter another custom field using steps 4 & 5.
5. When finished, click Save & Close.

...

1. In the upper left corner of the Settings icon –> > General Settings –> > Custom Fields page, open the Type menu and select a custom data type: Changes, Devices, Interfaces, Jobs or Components.
2. Click the Edit button for the field. The Edit custom field definition dialog appears.
3. Change the Name and/or  or Type as needed.
4. Click Save & Close.

To delete a custom data field, do the following:

Note
title Note

...

Deleting a custom field deletes all data stored in that field. Deleted data cannot be restored. The related custom fields will also be deleted from the contexts in which they are used.

1. In the upper left corner of the Settings icon –> > General Settings –>  > Custom Fields page, open the Type menu and then select a the custom data type.
2. Click the Delete button Action icon for the field and then choose Delete.
3. Confirm the deletionClick Yes.

Anchor
Importing Custom Field Data Importing Custom Field Data

Anchor
bookmark843 bookmark843

Importing Custom Field Data

Anchor
bookmark844 bookmark844

...

1. In the upper left corner of the Settings icon –> > General Settings –>  > Custom Fields page, open the Type menu and choose Devices, Interfaces or Components depending on the application. These are the only three Custom Field categories that support
2. Click Import. The Import Custom Field Data dialog opens.
3. Click Browse, then locate and select the bulk data CSV file.
4. Click Import.
5. Under Network Analysis –>> Changes, view the table of recent changes to devices in the network.
6. Move the mouse over any column in the table, and click the down arrow at the right end of the column heading.
7. In the drop-down menu, hover over Columns.
8. In the Columns submenu, check the custom field column(s) you want to appear in the table. The table will update to display the new column of data.

...

NetMRI enables custom information to be applied to the Inventory pages for any category within Network Explorer – > Inventory –>  > (Devices, Interfaces, OSs and Models.).

...

To add custom fields into tables within Network Explorer's Inventory pages, do the following:

1. Under Network Explorer –>  > Inventory, select any of the four categories of information (Devices, Interfaces, OSs or Models.)
2. Choose any of the sub-categories of information and the corresponding table appears. For example, under Devices, choose Device Components (you are not limited to this choice).
3. Move the mouse over any column in the table, and click the down arrow at the right end of the column heading.
4. In the drop-down menu, hover over Columns.
5. In the Columns submenu, check the custom field column(s) you want to appear in the table. The table will update to display the new column of data.

...

1. In the upper left corner of the Settings icon –>GeneralSettings–>Custom> General Settings > Custom Fields page, open the Type menu and select the Jobs custom data type.
2. Click New at the bottom right of the Custom Fields page.In the Add Custom Field dialog.
3. In the Create Custom Field dialog box, select the Type type (Date, Number, or String) and , enter the Name name for the new data field. Save your work.
4. To create more than one field, click Save. The new field is added to the table in the background. You can then enter another new field.
5. When finished, click Save Save & Close.
   Custom fields can be displayed in on the Scheduled Jobs page of Job Management (ConfigurationManagement–>JobManagement tab –>ScheduledJobs tab(Config Management > Job Management > Scheduled Jobs).
6. Move the mouse over any column in the table, and click the down arrow at the right end of the column heading.
7. In the drop-down menu, hover over Columns.
8. In the Columns submenu, check the custom field column(s) columns you want to appear in the table. The table will update to display the new column of data.

...

To add custom fields onto the Changes page, do the following:

1. Under NetworkAnalysis–>Analysis > Changes, view the table of recent changes to devices in the network.
2. Move the mouse over any column in the table, and click the down arrow at the right end of the column heading.
3. In the drop-down menu, hover over Columns.
4. In the Columns submenu, check the custom field column(s) you want to appear in the table. The table will update to display the new column of data.

...

To add custom field editing privileges to a non-Admin account, the admin user does the following:

1. (For Admin users) Ensure you have the needed non-

   Admin

   admin account in your user database.

   Note
   title Note

...

1. Check assigned Roles for the user in the Settings icon

...

1. > User Admin

...

1. > Users page.

...

1. 
   

2. To open the role for the non-

...

1. admin user account

...

1. , go to the Settings icon

...

1. > User Admin

...

1.  > Roles page.

...

1. To begin editing the

...

1. role, click its Action

...

1.  icon and

...

1. then choose Edit from the menu.

...

1.  For example, a user 'jsmith' manages the Routing and Switching device groups, and possesses the

...

1. ConfigAdmin and Switch Port Administrator roles. For custom data editing,

...

1. add the Custom Data: Input Data privilege to one or more

...

1. roles for the non-

...

1. admin user.

...

1. Click the Privileges tab in the Edit Role dialog

...

1. box and then click Add.

...

1. Select the Custom Data: Input Data privilege

...

1. and click OK.

...

1. Click Save & Close. NetMRI saves the new custom data privilege into the Role.The new Privilege automatically applies to any user accounts to which the Role is bound. (You will note that custom Roles can be defined in the Roles page.)

As an example, consider a case where an interface on a high-end distribution switch is dedicated to a particular department circuit, and you want the non-Admin user to add notes to its records. Do the following:

1. Have the non-Admin user log in to the NetMRI instance.
2. Open the Go to Network Explorer –> > Inventory –>  > Interfaces –>  > Interface Config and then click an Interface interface identifier. The Interface Viewer appears for the chosen port.
3. Open Go to the Interface –>  > Custom Data page.
4. At the bottom of the page, click New. ( This indicates that the non-Admin user can work with this data set. ) The Add Custom Field dialog box appears.
5. From In the Name: dropdown field, choose the desired Custom Field custom field to be added to the port information display.
6. In the Value field, enter the notes or other information for the custom field.
7. Click Save & Close.
   The custom field is applied on a granular per-interface level. In the Device Viewer, you apply custom fields from the Device/Network Explorer

...

1. >Custom Data page.

If a non-Admin user does not find an active Add New button at the bottom of a feature set's Custom Data page (for example, in the Interface Viewer, in the Device Viewer, or for a Job), two possible issues may apply:

1. • The Custom Data: Input Data Privilege  privilege has not been properly added to the user's Rolerole;
   • Custom Field field definitions have not been defined by the holder of the admin account. As noted above, five types of custom fields may be defined: Changes, Devices, Components, Interfaces, and Jobs. For more information, see Defining and Using Custom Fields and its subsections for details of all five custom field types available in the system.

The Device Viewer's Device/Network Explorer –> > Custom Data page is not enabled for non-Admin users unless the admin creates a Custom Field for the type Devices; and adds the Custom Data: Input Data privilege to the user's Role.

For Jobs and Changes types, custom fields could be used to record data such as trouble ticket numbers. Admin users may define new Custom Fields in the Settings icon –> > General Settings –> > Custom Fields page.

Anchor
Verifying Field Content In Device Viewer Verifying Field Content In Device Viewer

Anchor
bookmark850 bookmark850

Anchor
bookmark851 bookmark851

Verifying Field Content In Device Viewer & Interface Viewer

Anchor
bookmark852 bookmark852

After any custom data fields have been created in the Settings icon –> > General Settings –> > Custom Fields page, you can verify them and begin using them in the appliance by doing the following:

1. In Network Explorer, click the IP address of a device. The Device Viewer opens.
2. Under Device Viewer –> > Device/Network Explorer–> Explorer > Custom Data, check the list of custom fields in the device context.
   The Custom Data fields in this section will differ from those in other sections of the Device Viewer, such as Component Inventory. These fields are created under Settings icon –> General Settings –> Custom Fields –> and selecting the Devices type.
3. In the Device Viewer –> > Device/Network Explorer –> > Component Inventory, select a row in the Component Inventory table for the selected device.
4. Click the Edit Custom Fields button just above the Component Inventory table in the Device Viewer.
   The Edit Custom Fields dialog appears, displaying the list of one or more custom fields (defined under Settings) for this data set. Remember, these fields are defined under the Components type in Settings icon –> General Settings –> Custom Fields and all fields you define in this category will appear in the Edit Custom Fields dialog box only in this context.
5. Enter the necessary values in the custom fields for the selected inventory row.
6. Click Save & Close to save changes and return to the Component Inventory. Or, click Save to select another custom field and enter another value.
7. Filter the table of inventory information by clicking Filters above the Component Inventory table, and select the desired fields/columns by which the table is filtered. Any custom fields you have created for this category will appear here.

To check Custom Data field configuration in the Interface Viewer and use custom fields therein, do the following:

1. Under Device Viewer > Interfaces –> Interfaces–> Configuration, click an entry in the Interface column. The Interface Viewer appears in a separate popup window.
2. Under Interface–> Interface > Custom Data, click New. The Edit Custom Field Value dialog box appears.
3. Click the Name dropdown list. The custom data fields for the Interface context will appear in the dropdown.
4. Select In the Name filed, select the desired custom field and enter the correct value for the field.
5. Click Save & Close to save changes and return to the Interface Viewer. Or, click Save to To select another custom field and enter another value.

...

1. , click Save.

Custom Fields information can be deleted locally in the Interface Viewer context without removing the Custom Fields configuration from the entire system.
Under Interface Viewer –> Interface –> Custom DataTo delete locally-used custom fields from the Interface Viewer, do the following:

1. Go to Interface Viewer > Interface >Custom Data.
2. In the table, click the Delete icon

...

1. for the field information you want to remove.

...

2. Click Yes.