The device driver properties contain the following tabs of information.

Note: Contact NetBrain Support Team first before you make any changes in the following tabs.

 

Live Access Tab

The Live Access tab specifies the login and monitor settings.

▪Device CPU/Memory Usage OID — specify the OIDs used for monitoring CPU and memory usage of a device.

▪Multi page prompt — specify the prompt to display the next line/screen of output. By default, the prompt is "-more-".

▪The command to exit — the command used to exit from the current command mode to the next highest command mode.

▪Yes/No prompt string — a prompt string to confirm or cancel. By default, the prompt string includes "Yes or NO||Y/N||Yes/NO".

▪Interval to pause before entering password — specify the time in milliseconds that the system waits before entering the password. Generally, the system enters the password immediately after receiving the password prompt. But for a catalyst switch device, the system has to wait for some time to enter the password before the password is recognized as a valid input. This default value is 0 except for the catalyst switch type device.

▪Invalid return — determine whether a command return is invalid.

oIf the number of characters contained in the show command result is larger than the specified value (180 by default), the result will be treated as valid.

oIf the number of characters contained in the show command result is less than or equal to the specified value (180 by default), the system will further check whether the returned result contains the specified keywords. If yes, it will be recognized as an invalid result, indicating that it is failed to execute the command.

▪Standard login process — input the command such as enable to enter the privileged mode as well as the command (such as terminal length 0) to stop the CLI paging.

▪Customized login script — configure a login script to access a device. See CLI login script for more details.
Config File Tab

The Config File tab is used to specify how the system retrieves and parses the configuration file. The system uses both SNMP and CLI commands to build configuration files. When discovering a device, the system will firstly use SNMP to retrieve its hostname, vendor, and model information, and then try to enter the non-privilege and privileged mode to obtain its full configurations file with the CLI commands. If the CLI commands works, then the contents obtained via SNMP will be overwritten. Therefore both of the methods are selected by default.

▪CLI Command — type the CLI commands to retrieve the configuration file, such as show run.

▪Identify device type and driver by keywords in config file — click the hyperlink to configure the keywords in the configuration file to identify the device type and driver of the device.

The process of parsing CLI config file can be divided into two phrases:

1.Transform config file to known format — if you specify an existing driver for a new device type, the format of the configuration file to be parsed might be little different with an existing configuration file in the system. In this case, you can either use the Replacing equivalent keywords or Python Script method to transform the configuration file to a known format.

▪Replacing equivalent keywords — in the Keyword column, enter the keyword used in the new format of the configuration file. In the Known equivalent keyword column, enter the known keyword used in the existing format of the configuration file that the system can parse. In this case, when the system uses the driver to parse the new configuration file, it will first replace the keywords in the configuration file with the equivalent keywords configured in this table.

▪Python Script — select the python script and design a parser to translate the keywords to a known format.

1)Enter the python script in the Parsing Script pane.

2)Click Test Script, and copy the configuration file to the Sample Data pane.

3)Click Test to view the test results.

4)Click OK to save the Python script.

2.Parse transformed config file by predefined parser — select a predefined parser to parse the transformed configuration file.

▪Use MBI-2 default — use the built-in script to build SNMP configuration file.

▪Python Script — design a configuration file parser in the following window.

1.Enter the python script in the Python Script pane and click Test Script.

2.Enter or select the testing parameters in the Test Script dialog and click Test to test whether the configuration files can be parsed successfully.

3.Click OK to save the python script.

1.Click Define comparison logic.

2.In the pop-up dialog, enter the number in the Skip from top field to specify which lines can be skipped during the comparison. The lines are counted from the top of the configuration files.  

3.Enter the regular expressions in the Option field to specify which lines can be ignored during the comparison. You can click Add Option to add more items.

4.Click OK.
Table Tab

This Table tab is used to specify how the system retrieves and parses Route Table, MAC Table, ARP Table, NDP Table, and BGP Route Table. By default, the system retrieves these data tables by SNMP and you can also set to retrieve them by executing CLI commands.

Take Route Table for example:

▪Retrieve route table by CLI command — select this check box to retrieve route table by issuing CLI commands.

oUp to pages — specify the maximum routing table pages that the system can retrieve. The default value is 500. If the route table pages exceed the maximum value, the system will discard the exceeded pages.

oCLI command for global route table — enter the CLI command to retrieve the global routing table, such as show ip route.

oCLI command for VRF route table — enter the CLI command to retrieve the VRF route table, such as show ip route vrf $VrfName.

Note: The $VrfName variable represents a vrf name.

oParse CLI route table by script — enter script to retrieve and parser route table.

▪Build route entry by SNMP — select this check box to calculate live path and retrieve routing table entries via SNMP.

oMIB-2 route default — use the route MIB files to retrieve the routing table.

oMIB-2 forwarding MIB — use the forwarding MIB files to retrieve the routing table.

oCustomized script — design a Python script to retrieve the route table.

oBuild route table by SNMP (Up to lines) — select this check box to retrieve the entire route table via SNMP and specify the maximum lines of route entries to be retrieved from a device.
Advanced Tab

The Advanced tab specifies the python scripts used to retrieve device information (such as serial number, and software version) and interface data (such as interface speed, and duplex) of the same device type.

1.Click Add and the Retrieve Data dialog opens.

2.Select one data type from the drop-down menu.

3.Enter the scripts used to retrieve the data.

4.Enable the settings and click OK.

Tip: You can edit a built-in driver and refer to its built-in python scripts to define your own ones here.

 

See also:

▪Live Access Settings