blog

blog

rConfig Search Functionality

Finding IP addresses, ACL entries or advanced BGP configurations for your network devices can take time without a fast and accurate Configuration Management tool. rConfig takes 'fast' & 'accurate' to a new level on its search feature. Of all Network Configuration management tools available (at high costs), rConfig has by far the fastest search functionality available. In my experience operating and architecting networks, I do want the information I require to do my work immediatley and without fuss. Lets take a look at how rConfig's search feature performs. 

 

 

Simple IP Address Search:

Below is a screenshot of rConfig's search page. In this case we want to search for the IP Address '172.16.1.1'. I have chosen the category of 'Routers' which in turn will list all commands tied to that category in the next select box. I have also left the Device Field blank, which means all devices in the 'Routers' category will be searched for the Search Term and command specified. 

search1

Now, lets take a look at the results to understand what was searched, what was returned, and how quick it was. 

search2

Couple of things to take note of. First being the Search Time. A whoppping 0.78 seconds to search through nearly 13,000 files. Thats Fast! Next thing you may notice, is that the actual results are not what we searched for. Well! actually they are. You see, the search is carried out using Regular Expressions. We may have assumed that we searched for the literal of '172.16.1.1', when in fact we searched for 172[*]16[*]1[*]1 - the . is a wildcard in regex terms. See here for more information http://regexone.com/lesson/wildcards_dot. As per Regex rules, to search for a dot as part of a literal string we must escape it with a '\'. This means our new search string should be '172\.16\.1\.1'. Take a look at the new results below.

search6

search3

The difference now is that we only see the literal search term results. In other words, we searched for 172.16.1.1 (using escapes to present the dots as literal strings), and our search results only returned lines containing 172.16.1.1. 

As a last example, what if we wanted to see the lines before or after a search term? Take an example where we wanted to search for the BGP configuration for a paticular devices. Lets look at the search parameters. 

search4

Ok, so nothing to fancy here. Simple 'router bgp 1' search term with no special regex charachters... just spaces (though you could use regex '\s' to present whitespace - please read up on regex!). We are going to search on the routers category and on the 'show run' command files as well as on an individual device - headend.lab.rconfig.com. Wait!, one more thing before we hit 'search'. This time, instead of a single result, we want to see up to 30 lines after the search term. Lets put 30 into our 'No. Lines' box and set the 'Leading/Trailing' select to 'Trainling'. What is returned?

search5

This is great! 0.3 Seconds to search 306 files and return the results... So Fast! But also, now we have something really valuable. Without logging on to a single device, and running all sorts of awkward commands - we have our full BGP running config for this device in a flash. The possibilites are endless. Think of other examples, perhaps where you want to search for an IP address, and also want to know which interface or ACL it is configured on... very powerful!

To wrap it up... some great features in rConfig that we covered are;

1. Extremely fast search
2. Regex search feature
3. Search all sorts of command outputs such as 'show run' 'show ip access-list' etc...
4. Lead and Trailing config for search terms
5. Very fast search (did I already say that!)

Facebook LinkedIn Twitter RSS