Guest post by Praveen Kumar, Software Test Engineer
HP Network Automation software tracks, regulates, and automates configuration and software changes across globally distributed, multivendor networks. It is classified as CCC which is Change detection, Configuration management and Compliance. We can automate many use cases using the flow mentioned in the below diagram.
Click for larger image
1. Device management IP migration from IPv4 to IPv6
The management of IP address change is a time consuming and error prone activity. Using Network Automation (NA) you can perform this activity quickly and without any burden. This activity is executed as shown in the steps below.
The NA Server reads the NA device ID, IPv6 Address and Management interface ID from the .CSV file.
The NA Server connects to the NA Proxy
The NA Proxy will contact the device using the NA Device ID
The device will get configured per the requirement.
2. Change enable secret/password on network devices
There are times when you get into a situation where you need to change the enable secret/password of large set of devices. Manually logging into the each device and changing the password is a time consuming and cumbersome activity especially when thousands of devices present in an enterprise. Using NA you can simplify this activity. As mentioned in the diagram, you can specify the NA device ID which needs the password changed and the new password in the .CSV file. NA then absorbs the .CSV file and pushes the changes to all the devices mentioned in the .CSV file.
3. SNMP Read and Read-Write Community String change and SNMPv3 activation
There are a few times when you run into an issue where you need to change the SNMP community strings for thousands of devices within a short time period because of security issues/concerns. Manually doing this is a very costly operation. Using NA you can simplify this operation. You have to provide the NA device with ID and new community strings in the .CSV file. NA reads it and inserts the new community strings quickly for all the devices mentioned in the .CSV. The same holds true if the you have to configure the SNMP v3 for all the devices, they can simply follows the steps mentioned above.
4. SNMP sysLocation, sysName and sysContact
In a few scenarios, there will be a situation where you need to change the System Location, System contact and System name of a large set of devices. Manually performing this is a very time intensive operation. As mentioned in the diagram, you can automate the same using Network Automation. You have to provide the device ID followed by the sysLocation, sysName and sysContact in the .CSV file. NA processes this information and changes them one by one. There is another advantage: if NA and NNMi are integrated into the setup, these changes get pushed to NNMi and NNMi triggers the re-discovery of the devices and will get updated with latest SNMP system information.
5. Interface description change
An interface name change is a common activity performed in Enterprises or in the service provided network. Take a case where you have to change the interface description, say the “Backbone connection” for 100 device interfaces. It will be a costly to perform this operation manually. Using NA, as mentioned in the above diagram, you can provide the NA device ID, interface name/type and the new description in the .CSV file. NA reads the same and executes it for the devices listed in the file.
6. VTP Domain and Password change
If you find that both the domain and password is not secure, you have to change them manually for all of the switches. This manual task is time consuming and cumbersome. Using NA this task can be simplified. As mentioned in the diagram, the customer can provide the device ID, new VTP domain name and VTP password in the .CSV file. Network Automation reads them one by one and changes them quickly.
7. Enabling routing protocol for the router
Enabling routing protocol on the router is one-time activity. If the same has to be done on thousands of devices, it is a huge activity. Using NA can simplify this process. You have to provide the device ID, interface name/type and routing protocol name (OSPF, EIGRP, BGP etc.) in the .CSV file. NA takes the input from the file, logs into the device and enables the routing protocol for the specified interface.
I hope you have found the information and guidance within this blog post helpful.
About the author: Praveen Kumar has been in HP NMC team for over 9.5 years with experience in testing different products in NMC portfolio like NNM and different iSPIs. Apart from the testing experience Praveen has expertise in computer network administration, networking devices setup and configurations. He is presently working in the NA (Network Automation) group.
Praveen Kumar has Master of Science (MSc) degree from Kuvempu University, Shimoga and M.Tech degree in Information technology (IT) from Karnataka State Open University (KSOU), Mysore.