Using HP Intelligent Management Center (IMC) to push out configuration changes to your Network Switches

, ,

I’m currently consulting out at a school and implementing some changes for their environment, one of which is tightening up their networking environment seeing as I don’t want to remote into 60 odd switches to make changes to each of them we can use HP’s Intelligent Management Center (which schools generally get on the cheap).  The task of adding the switches into IMC had already been done by the guys at the school already and is fairly quick to complete using the discovery wizard if everything on the switches is left at their default settings. Any kind of configuration can be pushed out via IMC apart from VLAN and ACL management which happens under the Services menu in their respective options.   For this example I’m configuring NTP for their switches, using the below CLI, replace xxx with your IPs;

5406R (config) # time timezone 600 
5406R (config) # time daylight-time-rule southern-hemisphere 
5406R (config) # timesync sntp 
5406R (config) # sntp unicast 
5406R (config) # sntp server priority 1 172.16.xxx.xxx 
5406R (config) # sntp server priority 2 172.16.xxx.xxx

Now firstly we need to define a configuration template to push out.  Go to Service > Configuration Center > Configuration Templates optionally create a separate folder.  Go into your newly created folder and click Add > Manual Add.  Give the Template a Name and optionally select the switch models our configuration will apply to.  In the content window is where we enter our configuration and once done, hit OK to save.

IMC Deploying Device Config

Now that we have our configuration ready, we navigate to Service > Configuration Center > Deployment Guide in the page that presents you select the configuration template that we made earlier. Then go in and select the devices we will be deploying this config to.  Once we have that we can also optionally select different deploy strategy options to do things like backup the existing config and save the running config after deployment. In our case I have asked IMC to backup the running configuration before deployment and then save the running config after deployment.  On the next page we can give our specific task a name and schedule a type and time, for this example I have set to run immediately.  After clicking next again we are presented with all of the options that we chose earlier to review.  If everything looks good we can hit finish and it will begin deploying the script (a window will pop up showing the status).

And that’s it.  You can use this feature to do all sorts of things such as pushing out other settings like DNS, SSH or improved security configurations.

 


One response to “Using HP Intelligent Management Center (IMC) to push out configuration changes to your Network Switches”

  1. Keith Avatar
    Keith

    If you already have SNTP configured you must remove that configuration before putting down the new config.
    If you don’t you get the following error:
    SNTP Server Address or Priority already configured.

    As an example if you were changing from 172.17.xxx.xxx to 172.16.xxx.xxx

    time timezone 600
    time daylight-time-rule southern-hemisphere
    timesync sntp
    sntp unicast
    no sntp server priority 1 172.17.xxx.xxx
    no sntp server priority 2 172.17.xxx.xxx
    sntp server priority 1 172.16.xxx.xxx
    sntp server priority 2 172.16.xxx.xxx

    If anyone knows how to remove all the SNTP configuration with a single generic command (aside from erase start) that would be useful.

Leave a Reply

More Posts

A note about Veeam and Guest Indexing

So I was asked to help out in a situation where a Backup Server had begun to run out of space. One of the first things you look at doing is cutting down retention rates.  In this particular setup Veeam had its Database and other associated files sitting on a 30GB disk, which also happened […]

Troubleshooting 4.3.1 Insufficient System Resources Error for External Mail Flow on Exchange 2013

I’ve recently been contracting out to an educational organisation assisting with their BAU work as well as helping them modernising some of their processes and server environment. I was recently given a trouble ticket where I had to troubleshoot slow external mail flow. They have an ancient spam filtering appliance coupled with an Exchange 2013 […]

Time Hierarchy in Active Directory

Time is more critical in Active Directory than many admins realise. Time inaccuracy can cause logs to mismatch or things like license failures for anything with DRM. Larger time differences can begin to cause authentication failures since Keberos relies on accurate time or affect replication health. By default, all AD member machines synchronise with any […]