Ok – I’ll admit it – I’m something of a vendor snob… And my vendor of choice when it comes to Ethernet and fibre channel host connectivity is QLogic and HPE’s OEM products made by QLogic. You just can’t beat the price or performance of the offerings, and the support that QLogic’s HPE OEM team gives you – they are second to none (a huge shout out to @ToddOwens_QLGC & Jim Burton – if you guys are reading this, thanks for all the amazing support over the years!).
One of the interesting things about QLogic is their branded applications generally work hand in hand with the OEM products they offer to various system manufacturers such as HPE, Dell, and Lenovo. While I was attending a storage conference last week, I sat in on a presentation Jim and Todd were hosting. During the presentation the talk turned to QLogic’s comprehensive adapter management tools, including the Web-based QCC (QConvergedConsole), which is supported on Windows, Linux, and Solaris. QCC allows you to modify and configure your adapters (Ethernet, iSCSI, FCoE, and FC), upgrade the flash on them, perform FC ping and traceroute, and to view reports, statistics, and diagnostics of all the QLogic devices in your equipment – either locally or remote.
Given that QLogic devices are generally so bullet proof, and that the HPE Support Pack for Proliant takes care of my firmware updates, I rarely have a need to install and use QCC. But today was a little different – I had a VMware host that suffered a Purple Screen of Death overnight, and while I was in the ILO power cycling it and looking for a reason for PSOD, I noticed that ILO was complaining that the 534FLR-SFP+ adapter was degraded because it was in FCoE mode and not connected (we don’t use FCoE). Since I didn’t want to waste any more time playing around with the host before I brought it back online, I decided that I would load QCC on my management server at the site and see if I could disable FCoE mode remotely.
I never did find a way to disable the FCoE function via QCC – I only spent 3 minutes looking at it, so there may well be a way if I actually RTFM (that isn’t my style though), but this post isn’t about that. This post is all about getting QCC to co-exist (temporarily anyways) on a server that already has HPE’s 3Par SSMC and / or Veeam Backup & Recovery installed on it. QCC has been around a long time – longer that both SSMC and VBR, and as such has a few port conflicts that the guys at HPE and Veeam never took into consideration. As a result, you can’t just fire up the QCC installer and expect it co-exist and run 7/24 right out of the box along side SSMC and VBR.
Once you have the QCC installer downloaded and extracted, there are a few things we need to do before firing up the installer.
First, lets check to make sure TCP ports 8080, 8443, and 111 are not in use. We can accomplish this by opening an elevated command prompt and running: netstat -ano | find “0.0.0.0:####”
In the example above, you can see that two of the three ports are in use. Port 8443 is used by the application that has a PID of 38692, while port 111 is used by the application that has a PID of 30000. Using Task Manager, or better yet my favorite tool for the job – Process Explorer, we can easily determine the applications that are hogging these ports if we enable the PID and Path columns and then sort of the PID.
So to get started, we need to stop (temporarily) SSMC and VBR’s vPower NFS service.
Now that we have stopped these two services, lets double check to make sure TCP ports 8080, 8443, and 111 are no longer in use.
So with all three ports now free and no longer in use, we can launch the QCC installer as Administrator (note – all screen snapshots are based on Windows 2012 R2 with QCC v220.127.116.11). Click next a couple of times until you get to the “Please enter desired port number”. This defaults to TCP 8080, which as we checked already above, is free to use, so go ahead and click Install.
Eventually the installer will prompt if you wish to restrict access to localhost. No one else at my sites require access to QCC, so I’m ok with restricting access – I clicked yes (note it defaults to no, so if you just hit enter you answered no…)
Eventually, you’ll be prompted if you wish to enable security login.
Since this application is only going to be enabled temporarily when I actually need it on the management server on the management VLAN, and because I am restricting access to the localhost only, I left the checkbox cleared. That said, you may wish enable security – and if you do, make sure you make a note of the credentials you set! The default login id credentials if you didn’t change them is “QCC” with a password of “config”. Click Next to continue.
Now you are prompted if you wish to enable SSL. That is likely a good idea, even if you are restricting it to the localhost – so click yes. This will automatically set the Tomcat7 engine to use TCP 8443 and you can not change this from the installer.
Finally you will be presented with the Done button.
Now we can go ahead and install the necessary management agents. In my case I am going to install all of the management agents.
After we click Next, you’ll notice that the installer is installing the ONCPortmap service. This runs on TCP 111. If TCP 111 is already in use, the installer will hang, and hang, and hang… This is why we stopped the Veeam vPower NFS service earlier.
Eventually the management agent will complete the install process. When we install the next management agent, you’ll notice a warning about the ONCPortmap service – this is good! It means the ONCPortmap installed and started successfully.
After we have all the management agents installed that we want or require, we can go back in the command prompt and check our port status again.
Now you can see that all three ports are in use – which means QCC is likely ready to go. Sort of… As I mentioned previously, because the ports used in QCC conflict with SSMC and Veeam vPower NFS, we can’t just leave things alone and expect all three apps to work in the future after a reboot. In my environment SSMC and Veeam are more important than QCC, and I always want them to be started after a server reboot. So we need to set the follow services to be manual start instead of automatic (which they are by default) so they don’t prevent SSMC or Veeam from starting.
- ONC/RPC Portmapper
- QLogic Management Suite FastLinQ
- QLogic Management Suite Java iQAgent
Once we have changed the startup type of these services to manual, then lets login using the URL we were shown above.
Now – in the Host Selection dialog box, type in localhost and hit the connect button. You should be able to safely ignore any errors you may see.
Finally – the console is opened! Lets make a simple cosmetic change to see if it works (so something that does not affects the performance or anything of the adapters). Highlight one of the ports of one of your adapters (in my example below, Port 0 of the HP 533FLR-T) and click on the MBA Boot Cfg tab in the right hand pane. In the Hide Setup Prompt drop-down box, pick the opposite of whatever is there (it is probably already disabled, so select enabled), then click the Apply button.
You’ll be prompted for a password. This password, assuming you made no changes to the default setup will be “config”. If you aren’t sure if this is correct, clear the checkbox that says save password. If you leave it checked, and the password you put in is wrong, then you will need to log out of QCC and back in to be able to try a different password.
If you had the correct password, you’ll see a green banner advising you of a successful update!
Now all that is left is to make the changes you actually set out to do! Of course, once you are finished, you have two choices – reboot the server to apply the changes and have SSMC and VBR startup on reboot, or ignore the reboot, manually stop all the QCC services (see the list above) and manually start the SSMC and VBR services.
Now that you have QCC installed, if you need to access it in the future, you can just stop SSMC and VBR, then start the necessary QCC services. While it isn’t a perfect solution, it will allow QCC to coexist along side both SSMC and Veeam’s vPower NFS service.
As always – Use any tips, tricks, or scripts I post at your own risk.